Wednesday, June 26. 2019
GiMP
pigz: abort: write error on <stdout> (No space left on device)
On Debian Buster, even when cleaned of all older kernels, my /boot directory seems to be short of space now. I can't seem to update when just one kernel is present:
# ls -alt /boot total 42733 drwxr-xr-x 5 root root 1024 Jun 26 01:02 . -rw-r--r-- 1 root root 34752610 Jun 26 01:01 initrd.img-4.19.0-5-amd64 drwxr-xr-x 5 root root 1024 Jun 25 23:29 grub drwxr-xr-x 1 root root 234 Jun 3 18:06 .. -rw-r--r-- 1 root root 206223 May 15 16:07 config-4.19.0-5-amd64 -rw-r--r-- 1 root root 3370661 May 15 16:07 System.map-4.19.0-5-amd64 -rw-r--r-- 1 root root 5217520 May 15 16:07 vmlinuz-4.19.0-5-amd64 drwx------ 2 root root 12288 Jul 25 2018 lost+found drwx------ 3 root root 4096 Dec 31 1969 efi
My problem, is when adding or installing packages, I end up with:
Building cpio /boot/initrd.img-4.19.0-5-amd64.new initramfs pigz: abort: write error on(No space left on device) E: mkinitramfs failure pigz 28 update-initramfs: failed for /boot/initrd.img-4.19.0-5-amd64 with 1.
The solution is to mv or remove initrd.img-4.19.0-5-amd64.
I can then rebuild the file with:
# update-initramfs -cvk `uname -r`
or removing the file prior to installing updates:
~/initramfs# rm /boot/initrd.img-4.19.0-5-amd64 ~/initramfs# apt install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 140 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up initramfs-tools (0.133) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.133) ...
On watching the build, there must be a bunch of firmware files going in there. I wonder how to tone that down (mostly nuc8i7hvk01 special purpose display).
A bunch here -- will need to tone that down I think -- will need to go back to my installation notes to see why they are there:
# du -h --max-depth=1 /lib/firmware/amdgpu/ 25M /lib/firmware/amdgpu/
For simpler jobs, some commands to keep in mind:
- sudo apt-get autoclean
- sudo apt-get clean
- sudo apt-get autoremove
- sudo apt-get purge
2019/08/12 Most of the firmware size issue is resolved by:
- removing the firmware-misc-nonfree package, most of which seems to be included with no descretion
- keeping the firmware-amd-graphics package, but moving the /lib/firmware/amdgpu and /lib/firmware/radeon directories elsewhere, and 'mv firmware/amdgpu/vegam* /lib/firmware/' back again as the only files needed based upon 'dmesg|grep firmware'.
# lshw -short |grep Polaris /0/100/1/0 /dev/fb0 display Polaris 22 XT [Radeon RX Vega M GH] /0/100/1/0.1 multimedia Polaris 22 HDMI Audio
# dmesg|grep firmware [ 0.229009] Spectre V2 : Enabling Restricted Speculation for firmware calls [ 1.313160] amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/vegam_pfp.bin [ 1.313171] amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/vegam_me.bin [ 1.313179] amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/vegam_ce.bin [ 1.313188] amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/vegam_rlc.bin [ 1.313224] amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/vegam_mec.bin [ 1.313261] amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/vegam_mec2.bin [ 1.314058] amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/vegam_sdma.bin [ 1.314069] amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/vegam_sdma1.bin [ 1.314167] amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/vegam_uvd.bin [ 1.314170] [drm] Found UVD firmware Version: 1.130 Family ID: 16 [ 1.314786] amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/vegam_vce.bin [ 1.314789] [drm] Found VCE firmware Version: 53.21 Binary ID: 3 [ 1.314987] amdgpu 0000:01:00.0: firmware: direct-loading firmware amdgpu/vegam_smc.bin [ 3.772379] iwlwifi 0000:06:00.0: firmware: direct-loading firmware iwlwifi-8265-36.ucode [ 3.775171] iwlwifi 0000:06:00.0: loaded firmware version 36.8fd77bb3.0 op_mode iwlmvm
# ls -alt /lib/firmware/amdgpu/ total 1284 drwxr-xr-x 1 root root 290 Aug 13 09:36 . -rw-r--r-- 1 root root 16660 Aug 13 09:36 vegam_rlc.bin -rw-r--r-- 1 root root 12692 Aug 13 09:36 vegam_sdma1.bin -rw-r--r-- 1 root root 12692 Aug 13 09:36 vegam_sdma.bin -rw-r--r-- 1 root root 130964 Aug 13 09:36 vegam_smc.bin -rw-r--r-- 1 root root 375424 Aug 13 09:36 vegam_uvd.bin -rw-r--r-- 1 root root 166816 Aug 13 09:36 vegam_vce.bin -rw-r--r-- 1 root root 8852 Aug 13 09:36 vegam_ce.bin -rw-r--r-- 1 root root 17044 Aug 13 09:36 vegam_me.bin -rw-r--r-- 1 root root 262824 Aug 13 09:36 vegam_mec2.bin -rw-r--r-- 1 root root 262824 Aug 13 09:36 vegam_mec.bin -rw-r--r-- 1 root root 17044 Aug 13 09:36 vegam_pfp.bin drwxr-xr-x 1 root root 2740 Aug 13 09:31 ..
Epson Perfection V39 Scanner on Linux
I came across a Epson Perfection V39 and thought I'd try getting it to work on Linux Debian.
I have installed xsane, gscan2pdf and sane-utils.
When plugging into USB, /var/log/messages has:
Jun 25 23:16:04 usb 1-1: new full-speed USB device number 22 using xhci_hcd Jun 25 23:16:05 usb 1-1: new high-speed USB device number 23 using xhci_hcd Jun 25 23:16:05 usb 1-1: New USB device found, idVendor=04b8, idProduct=013d, bcdDevice= 1.00 Jun 25 23:16:05 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 25 23:16:05 usb 1-1: Product: Epson Perfection V39 Jun 25 23:16:05 usb 1-1: Manufacturer: EPSON Jun 25 23:16:05 usb 1-1: SerialNumber: VCFY057184
I tried creating the following file:
# cat /etc/udev/hwdb.d/epson-v39.hwdb # Epson Perfection V39 usb:v04B8p013D* libsane_matched=yes
and running 'systemd-hwdb update', but no luck
From a different perspective, Epson Drivers can be used to find the drivers. Put 'V39' only as the search criteria. One of the versions shown is 1.0.1, but v1.0.4 is actually available at v1.0.4. I wish there was a directory to browse as I found that one by trial and error on the url line.
However, skipping all that, this is the one that worked with xsane on Debian Buster: Image Scan! for Linux 1.0.1.
The scanner is seen:
iscan-gt-s650-bundle-1.0.1.x64.deb# scanimage -L device `epkowa:interpreter:001:025' is a Epson (unknown model) flatbed scanner
As a side note, the 1.0.4 version provided a mechanism of seeing network based scanners such as an HP multifunction.
For future reference, find a scanner which is compatible: SANE - Supported Devices
Monday, June 24. 2019
Links For The Day
- Grey Noise - At GreyNoise, we tell you all of the things not to be worried about. Think of us as "anti-threat intelligence".
- FTTH Parts List - fusion splicers, light meter, fault locator, enclosures
- Stack OverFlow JSON Hijacking
- Haacked JSON Hijacking
- TrustWave JSON Hijacking
- WebAssembly’s post-MVP future: A cartoon skill tree - from Mozilla
Sunday, June 23. 2019
Cassandra
- Cassandra vs. MongoDB
- About Deletes and Tombstones in Cassandra
- Cassandra anti-patterns: Queues and queue-like datasets
- Is it possible to use a cassandra table as a basic queue
- Redis::JobQueue
- Transactionally Staged Job Drains in Postgres
- Scylla Summit 2017: Planning Your Queries for Maximum Performance
- High performance queues with Cassandra
- Counting Keys In Cassandra
- Cassandra anti-patterns: Queues and queue-like datasets
Monday, June 17. 2019
CSS Tooling
- Comparison of browser engines (CSS support) - from wikipedia
Linux Diagnostic Tools
Some examples from my PC:
nuc8i7hvk01:~/$ sudo lshw -c cpu *-cpu description: CPU product: Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz vendor: Intel Corp. physical id: 37 bus info: cpu@0 version: Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz serial: To Be Filled By O.E.M. slot: U3E1 size: 3941MHz capacity: 4200MHz width: 64 bits clock: 100MHz capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d cpufreq configuration: cores=4 enabledcores=4 threads=8
nuc8i7hvk01:~/$ sudo lshw -c display *-display description: VGA compatible controller product: Polaris 22 XT [Radeon RX Vega M GH] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@0000:01:00.0 version: c0 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=amdgpu latency=0 resources: iomemory:200-1ff iomemory:210-20f irq:132 memory:2000000000-20ffffffff memory:2100000000-21001fffff ioport:e000(size=256) memory:db500000-db53ffff memory:c0000-dffff
Sunday, June 16. 2019
Firefox Memory Diagnostics
As a user with far too many FireFox open tabs, memory seems to disappear far too quickly. Knowing which of my many tabs contributes the most to the memory consumption would be helpful. But it seems as though Firefox doesn't make troubleshooting for that very easy. Here are a few tools which might help in narrowing my focus to determine granular memory consumption.
With recent versions of Firefox, there are some built-in tools which help to diagnose cpu and memory issues:
- about:performance - shows memory and cpu consumption
- about:memory?verbose - shows detailed memory consumption - not easily to digest
- about:cache?device=memory
Add-ons which provided in-tab memory consumption have been obsoleted. But one add-on which itemizes tabs: Tab Stats
Limiting the amount of RAM a program can use shows how on a Linux system to use cgroups to limit an application's memory footprint. The old 'ulimit' command is deprecated, and may not work.
Regarding the about:memory tool, more details can be found at Limit memory usage per Tab without blocking things? which points to about:memory and Memory.
Based upon How to Reduce Firefox Memory Usage using about:config it is possible to reduce memory caching with:
- 'about:config' in the address bar
- right click and create a 'new' -> 'integer'
- variable name is: browser.cache.memory.capacity (which is maximum RAM in KB) (further details at Browser.cache.memory.capacity) via About:config entries.