Re: Where to look into when system crashes
On 2023-02-22 02:05-0500, Felix Miata wrote: Qiming Ye composed on 2023-02-22 12:34 (UTC+0800): I have a Debian box running for 280+ days without rebooting, recently it crashes pretty much everyday. Where should I look for the reason of crashing? If you're running Bullseye from that external HD, I'd suspect the external HD's power supply. Who made it? When? When was that HD made? How many hours are on it? smartctl -x /dev/sdb will report its power on hours. Hi Felix, Actually /dev/sdb is an mSata drive. Here's output of smartctl: smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-21-amd64] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: SanPin-mSATA-128GB Serial Number:J4TTC7C20102103 LU WWN Device Id: 0 00 0 Firmware Version: SBFM91.2 User Capacity:128,035,676,160 bytes [128 GB] Sector Size: 512 bytes logical/physical Rotation Rate:Solid State Device Form Factor: mSATA TRIM Command: Available Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-4 (minor revision not indicated) SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Wed Feb 22 15:24:42 2023 CST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Unavailable === START OF READ SMART DATA SECTION == SMART overall-health self-assessment test result: PASSED [64/429] General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection:(65535) seconds. Offline data collection capabilities:(0x79) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 30) minutes. Conveyance self-test routine recommended polling time:( 6) minutes. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGSVALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 100 100 050-0 9 Power_On_Hours -O--C- 100 100 000-15975 12 Power_Cycle_Count -O--C- 100 100 000-69 168 Unknown_Attribute -O--C- 100 100 000-0 170 Unknown_Attribute PO 085 085 000-167 173 Unknown_Attribute -O--C- 100 100 000-852018 192 Power-Off_Retract_Count -O--C- 100 100 000-56 194 Temperature_Celsius PO---K 067 067 000-33 (Min/Max 33/33) 218 Unknown_Attribute PO-R-- 100 100 050-0 231 Unknown_SSD_Attribute PO--C- 100 100 000-99 241 Total_LBAs_Written -O--C- 100 100 000-884 ||_ K auto-keep |__ C event count ___ R error rate ||| S speed/performance ||_ O updated online |__ P prefailure warning General Purpose Log Directory Version 1
Re: Where to look into when system crashes
Qiming Ye composed on 2023-02-22 12:34 (UTC+0800): > I have a Debian box running for 280+ days without rebooting, recently it > crashes > pretty much everyday. Where should I look for the reason of crashing? If you're running Bullseye from that external HD, I'd suspect the external HD's power supply. Who made it? When? When was that HD made? How many hours are on it? smartctl -x /dev/sdb will report its power on hours. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: Where to look into when system crashes
It's running Debian 11, the last updates were applied few weeks ago. This is the output of inxi -Faz % inxi -Faz System:Kernel: 5.10.0-21-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-21-amd64 root=UUID=ea7c90dc-d8f0-4641-ba37-5e329cbcf385 ro quiet Console: tty 2 Distro: Debian GNU/Linux 11 (bullseye) Machine: Type: Laptop Mobo: INTEL model: MAHOBAY serial: BIOS: American Megatrends v: 4.6.5 date: 10/18/2017 CPU: Info: Dual Core model: Intel Core i3-3120M bits: 64 type: MT MCP arch: Ivy Bridge family: 6 model-id: 3A (58) stepping: 9 microcode: 17 L2 cache: 3 MiB flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 19954 Speed: 1688 MHz min/max: 1200/2500 MHz Core speeds (MHz): 1: 1688 2: 1894 3: 1803 4: 1757 Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported Type: l1tf mitigation: PTE Inversion Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable Type: meltdown mitigation: PTI Type: mmio_stale_data status: Unknown: No mitigations Type: retbleed status: Not affected Type: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0166 class ID: 0300 Display: server: X.org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa tty: 272x64 Message: Advanced graphics data unavailable in console. Try -G --display Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 class ID: 0403 Sound Server: ALSA v: k5.10.0-21-amd64 Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel port: e000 bus ID: 02:00.0 chip ID: 10ec:8168 class ID: 0200 IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: IF-ID-1: br-b13d540ee75c state: down mac: IF-ID-2: docker0 state: down mac: IF-ID-3: wg0 state: unknown speed: N/A duplex: N/A mac: N/A Drives:Local Storage: total: 3.76 TiB used: 1.73 TiB (46.2%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/sda maj-min: 8:0 type: USB vendor: Seagate model: ST3000VX000-1CU166 size: 2.73 TiB block size: physical: 4096 B logical: 512 B rotation: 7200 rpm serial: rev: 0414 scheme: GPT ID-2: /dev/sdb maj-min: 8:16 model: SanPin-mSATA-128GB size: 119.24 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: rev: 91.2 scheme: MBR ID-3: /dev/sdc maj-min: 8:32 type: USB model: Mass Storage Device size: 931.51 GiB block size: physical: 512 B logical: 512 B serial: scheme: GPT Partition: ID-1: / raw size: 118.29 GiB size: 115.87 GiB (97.96%) used: 47.23 GiB (40.8%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 Swap: Kernel: swappiness: 60 (default) cache pressure: 100 (default) ID-1: swap-1 type: partition size: 976 MiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb5 maj-min: 8:21 Sensors: System Temperatures: cpu: 29.8 C mobo: 27.8 C Fan Speeds (RPM): N/A Info: Processes: 156 Uptime: 5h 57m wakeups: 0 Memory: 3.74 GiB used: 571.2 MiB (14.9%) Init: systemd v: 247 runlevel: 5 Compilers: gcc: 10.2.1 alt: 10 Packages: apt: 2397 lib: 1234 Shell: Zsh v: 5.8 running in: tty 2 inxi: 3.3.01 On 2023-02-22 01:21-0500, Felix Miata wrote: Qiming Ye composed on 2023-02-22 12:34 (UTC+0800): I have a Debian box running for 280+ days without rebooting, recently it crashes pretty much everyday. Where should I look for the reason of crashing? Which Debian is installed? When were updates last applied? When was its hardware made? What hardware is included? inxi -Faz would report. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: Where to look into when system crashes
Qiming Ye composed on 2023-02-22 12:34 (UTC+0800): > I have a Debian box running for 280+ days without rebooting, recently it > crashes > pretty much everyday. Where should I look for the reason of crashing? Which Debian is installed? When were updates last applied? When was its hardware made? What hardware is included? inxi -Faz would report. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Where to look into when system crashes
Hello, I have a Debian box running for 280+ days without rebooting, recently it crashes pretty much everyday. Where should I look for the reason of crashing? Thank you, - Tim
Re: Evolution doesn't receive messages in Debian 11.
On Tue, Feb 21, 2023 at 12:09:30PM -0800, Van Snyder wrote: > I just upgraded to Debian 11. I had been using Debian 10. I've used > Evolution for many years. The version in Debian 11 is 3.48. > > I use KDE Plasma version 5.26.90. The KDE Frameworks version is > 5.102.0. > > I get pop-up notes from KDE that evolution has received new messages. Possibly a secondary thing: no messages -> no popup. > But the messages don't appear in Evolution [...] Since the thread is trying to derail into whether "safe upgrade" is somehow safer or not (spoiler: sometimes, but here most probably irrelevant; alas, that's how we nerds are ;)... I have no clue with Evolution, but it might help those helping you to tell us how Evolution is "getting" its mails. My hunch would be that it is set up to fetch its mails from the server (how? IMAP? POP3?). It would be useful to try to debug this process. Again, I've never touched Evolution in my life, but here [1] is a nice debugging guide which might help getting things started. Now let's hope to get back on topic and perhaps some Evolution guru chimes in. Cheers [1] https://wiki.gnome.org/Apps/Evolution/Debugging -- t signature.asc Description: PGP signature
Re: KDE Frameworks 5.103.0 and KDE Plasma 5.27
On Tue, Feb 21, 2023 at 6:35 PM Patrick Franz wrote: > Hej, > > Am Dienstag, 21. Februar 2023, 20:09:13 CET schrieb Timothy M > Butterworth: > > Is Bookworm going to get Frameworks 5.103.0 and is there any estimated > > time when Bookworm will get Plasma 5.27? > > Bookworm already has Plasma 5.27 beta (it's officially called 5.26.90), > but both the Frameworks 5.103 and Plasma 5.27.0 have been uploaded to > unstable and will be available in bookworm unless something weird > happens. > > The Frameworks 5.103 will migrate to bookworm towards the end of the > week, while Plasma 5.27.0 will migrate in the middle of next week. > Thanks Patrick > We hope we can get Plasma 5.27.2 in before the next freeze. > -- > Med vänliga hälsningar > > Patrick Franz > > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: KDE Frameworks 5.103.0 and KDE Plasma 5.27
Hej, Am Dienstag, 21. Februar 2023, 20:09:13 CET schrieb Timothy M Butterworth: > Is Bookworm going to get Frameworks 5.103.0 and is there any estimated > time when Bookworm will get Plasma 5.27? Bookworm already has Plasma 5.27 beta (it's officially called 5.26.90), but both the Frameworks 5.103 and Plasma 5.27.0 have been uploaded to unstable and will be available in bookworm unless something weird happens. The Frameworks 5.103 will migrate to bookworm towards the end of the week, while Plasma 5.27.0 will migrate in the middle of next week. We hope we can get Plasma 5.27.2 in before the next freeze. -- Med vänliga hälsningar Patrick Franz
Re: Debian installer chooses the wrong NVidia driver
On Tue, 2023-02-21 at 22:45 +0100, Mario Marietto wrote: > If I dont get wrong,nvidia created one single driver which works for > every gpu or almost ? it means that if I install the 525 driver for > my RTX 2080 ti will it work also for my old gpu,GTX 1060 ? The 470 driver that the Debian installer chose doesn't work with GF108. Only the 390 driver works. If you look at one of the alternative text screens (not X) the load process is complaining about that -- but it took me a week to find that. > > Il mar 21 feb 2023, 22:28 Georgi Naplatanov ha > scritto: > > On 2/21/23 23:16, Van Snyder wrote: > > > On Tue, 2023-02-21 at 22:41 +0200, Georgi Naplatanov wrote: > > >> On 2/21/23 22:13, Van Snyder wrote: > > >>> I have an NVidia GF108 video card. It works just fine, so I > > don't see a > > >>> reason to replace it. > > >>> > > >>> It needs the nvidia-legacy-390xx-driver. > > >>> > > >>> But when I installed Debian 11, it chose the 470 driver, which > > doesn't > > >>> work with GF108. > > >>> > > >>> Maybe that was caused by selecting "install all the drivers" > > instead of > > >>> "install only the relevant drivers." I thought that meant > > "download them > > >>> all in case you install some new hardware." > > >>> > > >>> Shouldn't the installer install only the drivers for the > > relevant > > >>> hardware, even if it downloads all of them? > > >>> > > >>> I'm not going to re-install just to do an experiment to see if > > the > > >>> installer does it right if I tell it to install only the > > relevant > > >>> drivers. > > >>> > > >> > > >> > > >> Hi! > > >> > > >> It seems that nvidia-legacy-390xx-driver is available in Debian > > 11 > > >> (bullseye). You have just to install it. If you have problems > > again, > > >> then try to use open source driver for NVidia's cards - Nouveau. > > it's > > >> installed by default and you have just to uninstall NVidia's > > proprietary > > >> drivers - nvidia-*. > > > > > > I did install it, but it took me a week to find that that was the > > > problem. I had expected Debian's installer to choose to use the > > correct > > > driver even if all the drivers it has in its entire achive are > > downloaded. > > > > > > There is a package nvidia-detect > > > > it tells you which driver is appropriate for your NVidia's video > > card. > > > > Kind regards > > Georgi > >
Re: Debian installer chooses the wrong NVidia driver
its not easy for me,because I have those GPUs on a single system. The OS that im running is freebsd and I tried to virtualize debian 11 with bhyve (hypervisor for freebsd). Well,debian accept the 2080 ti and I can use it within debian guest,but the 1060 does not work. it is not initialized. I tried to use the 525 for both. I cant use the 390 for both the GPU. Il mar 21 feb 2023, 23:27 Mario Marietto ha scritto: > its not easy for me,because I have those GPUs on a single system. The OS > that im running is freebsd and I tried to virtualize debian 11 with bhyve > (hypervisor for freebsd). Well,debian accept the 2080 ti and I can use it > within debian guest,but the 1060 does not work. it is not initialized. I > tried to use the 525 for both. I cant use the 390 for both the GPU. > > Il mar 21 feb 2023, 22:57 Georgi Naplatanov ha scritto: > >> On 2/21/23 23:45, Mario Marietto wrote: >> > If I dont get wrong,nvidia created one single driver which works for >> > every gpu or almost ? it means that if I install the 525 driver for my >> > RTX 2080 ti will it work also for my old gpu,GTX 1060 ? >> > >> >> AFIK, NVidia offers different driver generations and my understanding is >> that package nvidia-detect recommends which driver generation is the >> best for your video card. >> >> Kind regards >> Georgi >> >>
Re: Debian installer chooses the wrong NVidia driver
On 2/21/23 23:45, Mario Marietto wrote: If I dont get wrong,nvidia created one single driver which works for every gpu or almost ? it means that if I install the 525 driver for my RTX 2080 ti will it work also for my old gpu,GTX 1060 ? AFIK, NVidia offers different driver generations and my understanding is that package nvidia-detect recommends which driver generation is the best for your video card. Kind regards Georgi
Re: Test ECC memory
krys...@ibse.cz wrote: > Dan Ritter wrote: > > The kernel announces readiness during boot with: > > dmesg:[ 18.331561] EDAC amd64: Node 0: DRAM ECC enabled. > > > > and then an event looks like this: > > Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... > > kernel:[5964975.397283] [Hardware Error]: Corrected error, no > > action required. > > > > Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... > > kernel:[5964975.406226] [Hardware Error]: CPU:0 (15:2:0) > > MC4_STATUS[-|CE|MiscV|-|AddrV|-|-|CECC]: 0x9c04400040080a13 > > > > Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... > > kernel:[5964975.418574] [Hardware Error]: Error Addr: > > 0x001ed405ef50 > > > > Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... > > kernel:[5964975.426919] [Hardware Error]: MC4 Error (node 0): > > DRAM ECC error detected on the NB. > > > > Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... > > kernel:[5964975.437370] [Hardware Error]: cache level: L3/GEN, > > mem/io: MEM, mem-tx: RD, part-proc: RES (no timeout) > > Do you keep track of how often these errors occur? Yes, but I'm not allowed to give much more precision than I've already said. Rare, unless you have a failing DIMM. -dsr-
Re: Evolution doesn't receive messages in Debian 11.
On Tue, 2023-02-21 at 15:42 -0600, David Wright wrote: > On Wed 22 Feb 2023 at 06:34:27 (+1000), David wrote: > > On Tue, 2023-02-21 at 12:09 -0800, Van Snyder wrote: > > > > > > When I installed Debian 11, I didn't destroy Debian 10. I still > > > have > > > Debian 10 on a different drive. In attempting to repair an > > > entirely > > > different problem, I had done > > > > > > apt-get update; apt-get upgrade > > > > One of the reasons I prefer aptitude's `safe-upgrade'. > > That's the equivalent command, and would not protect you. That's what many think: aptitude safe-upgrade upgrades currently installed packages and can install new packages to resolve new dependencies. apt-get upgrade upgrades currently installed packages. > It will > upgrade everything that doesn't involve a new package, but nothing > else, hence the mish-mash of Debian 10 and 11. > > If you want keep an old system around, you need to make sure that the > sources.list has the correct version's proper name in it, ie buster > in your case. And if you're later going to use it at all, you need > to keep it updated with those two commands. > > > > Does anybody have any suggestions to repair it? > > As others have suggested, the easiest is probably to: > > # apt-get update; apt-get dist-upgrade > > which will take it up to stable ≡ bullseye. > > Then edit the sources.list and change stable → bullseye. > And do the same edit to the system that was already Debian 11. > > In a few ?weeks, you can decide which of the two drives you want to > upgrade to Debian 12 ≡ bookworm, and leave the other as Debian 11, > upgradeable /safely/ as Debian 11. > > Cheers, > David. >
Re: Debian installer chooses the wrong NVidia driver
If I dont get wrong,nvidia created one single driver which works for every gpu or almost ? it means that if I install the 525 driver for my RTX 2080 ti will it work also for my old gpu,GTX 1060 ? Il mar 21 feb 2023, 22:28 Georgi Naplatanov ha scritto: > On 2/21/23 23:16, Van Snyder wrote: > > On Tue, 2023-02-21 at 22:41 +0200, Georgi Naplatanov wrote: > >> On 2/21/23 22:13, Van Snyder wrote: > >>> I have an NVidia GF108 video card. It works just fine, so I don't see a > >>> reason to replace it. > >>> > >>> It needs the nvidia-legacy-390xx-driver. > >>> > >>> But when I installed Debian 11, it chose the 470 driver, which doesn't > >>> work with GF108. > >>> > >>> Maybe that was caused by selecting "install all the drivers" instead of > >>> "install only the relevant drivers." I thought that meant "download > them > >>> all in case you install some new hardware." > >>> > >>> Shouldn't the installer install only the drivers for the relevant > >>> hardware, even if it downloads all of them? > >>> > >>> I'm not going to re-install just to do an experiment to see if the > >>> installer does it right if I tell it to install only the relevant > >>> drivers. > >>> > >> > >> > >> Hi! > >> > >> It seems that nvidia-legacy-390xx-driver is available in Debian 11 > >> (bullseye). You have just to install it. If you have problems again, > >> then try to use open source driver for NVidia's cards - Nouveau. it's > >> installed by default and you have just to uninstall NVidia's proprietary > >> drivers - nvidia-*. > > > > I did install it, but it took me a week to find that that was the > > problem. I had expected Debian's installer to choose to use the correct > > driver even if all the drivers it has in its entire achive are > downloaded. > > > There is a package nvidia-detect > > it tells you which driver is appropriate for your NVidia's video card. > > Kind regards > Georgi > >
Re: Evolution doesn't receive messages in Debian 11.
On Wed 22 Feb 2023 at 06:34:27 (+1000), David wrote: > On Tue, 2023-02-21 at 12:09 -0800, Van Snyder wrote: > > > > When I installed Debian 11, I didn't destroy Debian 10. I still have > > Debian 10 on a different drive. In attempting to repair an entirely > > different problem, I had done > > > > apt-get update; apt-get upgrade > > One of the reasons I prefer aptitude's `safe-upgrade'. That's the equivalent command, and would not protect you. It will upgrade everything that doesn't involve a new package, but nothing else, hence the mish-mash of Debian 10 and 11. If you want keep an old system around, you need to make sure that the sources.list has the correct version's proper name in it, ie buster in your case. And if you're later going to use it at all, you need to keep it updated with those two commands. > > Does anybody have any suggestions to repair it? As others have suggested, the easiest is probably to: # apt-get update; apt-get dist-upgrade which will take it up to stable ≡ bullseye. Then edit the sources.list and change stable → bullseye. And do the same edit to the system that was already Debian 11. In a few ?weeks, you can decide which of the two drives you want to upgrade to Debian 12 ≡ bookworm, and leave the other as Debian 11, upgradeable /safely/ as Debian 11. Cheers, David.
Re: awk not just using the Field separator as such. it is using the blank space as well ...
lbrt...@gmail.com wrote: >On 2/21/23, Greg Wooledge wrote: >> I have a funny feeling Albretch might be using Microsoft file systems >> (FAT, NTFS) for a large chunk of his system. Those have a much larger >> set of restricted characters. > > Certainly not FAT32 and definitely not FAT, but at work (I work as a >Math teacher and most schools use Microsoft) I have had to use WSL and >NTFS. I always thought that FSs used length-defined raster data >structures in order to avoid messing with points and such things. Different filesystems can vary massively here, you can't really assume anything. All of the following can vary in filesystems supported by Linux: * allowed characters in filenames * allowed filename lengths * allowed full-path lengths * character encodings for filenames * case-sensitivity * max number of files per directory * max number of files per filesystem * timestamps (minimum, maximum and resolution) * support for symlinks and hardlinks * support for extended attributes, permissions and and ACLs * ... The VFS layer does a very good job of hiding the complexity and giving you a reasonably consistent view, but it's not difficult to find edges if you look. :-) -- Steve McIntyre, Cambridge, UK.st...@einval.com < sladen> I actually stayed in a hotel and arrived to find a post-it note stuck to the mini-bar saying "Paul: This fridge and fittings are the correct way around and do not need altering"
Re: Debian installer chooses the wrong NVidia driver
On 2/21/23 23:16, Van Snyder wrote: On Tue, 2023-02-21 at 22:41 +0200, Georgi Naplatanov wrote: On 2/21/23 22:13, Van Snyder wrote: I have an NVidia GF108 video card. It works just fine, so I don't see a reason to replace it. It needs the nvidia-legacy-390xx-driver. But when I installed Debian 11, it chose the 470 driver, which doesn't work with GF108. Maybe that was caused by selecting "install all the drivers" instead of "install only the relevant drivers." I thought that meant "download them all in case you install some new hardware." Shouldn't the installer install only the drivers for the relevant hardware, even if it downloads all of them? I'm not going to re-install just to do an experiment to see if the installer does it right if I tell it to install only the relevant drivers. Hi! It seems that nvidia-legacy-390xx-driver is available in Debian 11 (bullseye). You have just to install it. If you have problems again, then try to use open source driver for NVidia's cards - Nouveau. it's installed by default and you have just to uninstall NVidia's proprietary drivers - nvidia-*. I did install it, but it took me a week to find that that was the problem. I had expected Debian's installer to choose to use the correct driver even if all the drivers it has in its entire achive are downloaded. There is a package nvidia-detect it tells you which driver is appropriate for your NVidia's video card. Kind regards Georgi
Re: Nedit opens in a different workspace
On Tue, Feb 21, 2023 at 01:20:45PM -0800, Van Snyder wrote: > > deb http://deb.debian.org/debian stable main contrib non-free > > That is indeed the line in /etc/apt/sources.list -- because that's what > the Debian installer put there. Was it a "Live" image? I bet it was.
Re: Test ECC memory
Dan Ritter wrote: > The kernel announces readiness during boot with: > dmesg:[ 18.331561] EDAC amd64: Node 0: DRAM ECC enabled. > > and then an event looks like this: > Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... > kernel:[5964975.397283] [Hardware Error]: Corrected error, no > action required. > > Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... > kernel:[5964975.406226] [Hardware Error]: CPU:0 (15:2:0) > MC4_STATUS[-|CE|MiscV|-|AddrV|-|-|CECC]: 0x9c04400040080a13 > > Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... > kernel:[5964975.418574] [Hardware Error]: Error Addr: > 0x001ed405ef50 > > Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... > kernel:[5964975.426919] [Hardware Error]: MC4 Error (node 0): > DRAM ECC error detected on the NB. > > Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... > kernel:[5964975.437370] [Hardware Error]: cache level: L3/GEN, > mem/io: MEM, mem-tx: RD, part-proc: RES (no timeout) Do you keep track of how often these errors occur?
Re: Nedit opens in a different workspace
On Tue, 2023-02-21 at 15:43 -0500, Greg Wooledge wrote: > Then your sources.list file was incorrect to begin with. I'm > guessing > you had something like this: > > > deb http://deb.debian.org/debian stable main contrib non-free > > > You should never use the "stable" alias in the sources.list file, > because > it's a moving target. That is indeed the line in /etc/apt/sources.list -- because that's what the Debian installer put there. I didn't change lines in the file, but I did add one line for the Intel OneAPI software development tools.
Re: Debian installer chooses the wrong NVidia driver
On Tue, 2023-02-21 at 22:41 +0200, Georgi Naplatanov wrote: > On 2/21/23 22:13, Van Snyder wrote: > > I have an NVidia GF108 video card. It works just fine, so I don't > > see a > > reason to replace it. > > > > It needs the nvidia-legacy-390xx-driver. > > > > But when I installed Debian 11, it chose the 470 driver, which > > doesn't > > work with GF108. > > > > Maybe that was caused by selecting "install all the drivers" > > instead of > > "install only the relevant drivers." I thought that meant "download > > them > > all in case you install some new hardware." > > > > Shouldn't the installer install only the drivers for the relevant > > hardware, even if it downloads all of them? > > > > I'm not going to re-install just to do an experiment to see if the > > installer does it right if I tell it to install only the relevant > > drivers. > > > > > Hi! > > It seems that nvidia-legacy-390xx-driver is available in Debian 11 > (bullseye). You have just to install it. If you have problems again, > then try to use open source driver for NVidia's cards - Nouveau. it's > installed by default and you have just to uninstall NVidia's > proprietary > drivers - nvidia-*. I did install it, but it took me a week to find that that was the problem. I had expected Debian's installer to choose to use the correct driver even if all the drivers it has in its entire achive are downloaded. > > Kind regards > Georgi >
Re: Nedit opens in a different workspace
Van Snyder wrote: > I was convinced to do > > apt-get update; apt-get upgrade > > to try to repair a problem in my Debian 10 installation. Now it has a > mish-mash of 10 & 11 pieces. That's not possible unless you also edited /etc/apt/sources.list (or a file in sources.list.d/). Complete your upgrade to 11; it's past time. 12 will be available in a few months. Double check the sources, run apt update and then apt dist-upgrade. Reboot with the new kernel. -dsr-
Re: Nedit opens in a different workspace
On Tue, Feb 21, 2023 at 12:33:28PM -0800, Van Snyder wrote: > I was convinced to do > > apt-get update; apt-get upgrade > > to try to repair a problem in my Debian 10 installation. Now it has a > mish-mash of 10 & 11 pieces. Then your sources.list file was incorrect to begin with. I'm guessing you had something like this: deb http://deb.debian.org/debian stable main contrib non-free You should never use the "stable" alias in the sources.list file, because it's a moving target. Doing an update/upgrade after a new version of Debian has released will try to pull in pieces of the new version, when you aren't prepared for it. Always use the codename of the Debian version that you intend to run. For example: deb http://deb.debian.org/debian buster main contrib non-free At this point, you have two basic choices: you can either finish upgrading to Debian 11, or you can reinstall Debian 10. Personally, I'd go with the first option, unless there is a compelling reason to remain on Buster. Standard advice applies -- read the Bullseye release notes and the NewInBullseye page on the wiki, make backups of your system first, and so on.
Re: Debian installer chooses the wrong NVidia driver
On 2/21/23 22:13, Van Snyder wrote: I have an NVidia GF108 video card. It works just fine, so I don't see a reason to replace it. It needs the nvidia-legacy-390xx-driver. But when I installed Debian 11, it chose the 470 driver, which doesn't work with GF108. Maybe that was caused by selecting "install all the drivers" instead of "install only the relevant drivers." I thought that meant "download them all in case you install some new hardware." Shouldn't the installer install only the drivers for the relevant hardware, even if it downloads all of them? I'm not going to re-install just to do an experiment to see if the installer does it right if I tell it to install only the relevant drivers. Hi! It seems that nvidia-legacy-390xx-driver is available in Debian 11 (bullseye). You have just to install it. If you have problems again, then try to use open source driver for NVidia's cards - Nouveau. it's installed by default and you have just to uninstall NVidia's proprietary drivers - nvidia-*. Kind regards Georgi
Re: Evolution doesn't receive messages in Debian 11.
On Tue, 2023-02-21 at 12:09 -0800, Van Snyder wrote: > I just upgraded to Debian 11. I had been using Debian 10. I've used > Evolution for many years. The version in Debian 11 is 3.48. > > I use KDE Plasma version 5.26.90. The KDE Frameworks version is > 5.102.0. > > I get pop-up notes from KDE that evolution has received new messages. > > But the messages don't appear in Evolution. I am using Evolution 3.38.3-1+deb11u1 with Stable, and Evolution 3.46.4-1 with Unstable quite successfully. > I know it's not a mail > server problem because I can read the messages in Firefox -- but > Firefox doesn't have access to my archive, so I can't save anything > (on > my own computer). If I were to work out how to get Firefox to save > them, and if I ever get Evolution working again, the messages won't > be > in Evolution's format, and the other Evolution data structures won't > be > updated. > > There was a note about "messages not appearing in Evolution" many > years > ago. It turned out to have been caused by the user's configuration > mistake. When I looked for that mistake in my configuration (which I > hadn't touched), I hadn't made it. > > Does anybody have any suggestions to get it working? > > When I installed Debian 11, I didn't destroy Debian 10. I still have > Debian 10 on a different drive. In attempting to repair an entirely > different problem, I had done > > apt-get update; apt-get upgrade One of the reasons I prefer aptitude's `safe-upgrade'. > on the advice of a posting in one of the Debian forums. Now, in > Debian > 10, there's a mish-mash of Debian 11 parts. Evolution is version > 3.46. > It works, but the user interface is now a mess. Icons are tiny and in > different places. The body has a black border between itself and the > window border. The title bar for the composer is entirely different > from the title bar of any other window -- about three times as thick, > containing several icons, including the "send" icon. > > Does anybody have any suggestions to repair it? I'd try a reinstall of the version that is standard for that Debian iteration. How Evolution presents depends very much on if it is on a laptop or desktop. I have it installed on both, and see none of the things you are describing. This applies to another version I have installed on FreeBSD, also. I have a mix of KDE and Gnome apps on an Enlightenment window manager, so doubt conflict problems between desktop apps. You will be looking at conflict between versions and desktop, with unmatched dependencies, I should say. HTH Cheers!
Nedit opens in a different workspace
I was convinced to do apt-get update; apt-get upgrade to try to repair a problem in my Debian 10 installation. Now it has a mish-mash of 10 & 11 pieces. After doing that, when I open Nedit, either from the command-line or a tool-bar icon, it opens in a random desktop, always different from the one in which it is opened. My window manager is KDE Plasma version 5.26.90. The KDE Frameworks version is 5.102.0. I tried changing the properties of the icon to use kstart5 with the -- currentdesktop option, but that had no effect. I have an installation of Debian 11, on a different disk, in which this does not occur. But that installation has other problems I mentioned recently. Does anybody have a suggestion how to repair this problem?
Debian installer chooses the wrong NVidia driver
I have an NVidia GF108 video card. It works just fine, so I don't see a reason to replace it. It needs the nvidia-legacy-390xx-driver. But when I installed Debian 11, it chose the 470 driver, which doesn't work with GF108. Maybe that was caused by selecting "install all the drivers" instead of "install only the relevant drivers." I thought that meant "download them all in case you install some new hardware." Shouldn't the installer install only the drivers for the relevant hardware, even if it downloads all of them? I'm not going to re-install just to do an experiment to see if the installer does it right if I tell it to install only the relevant drivers.
Evolution doesn't receive messages in Debian 11.
I just upgraded to Debian 11. I had been using Debian 10. I've used Evolution for many years. The version in Debian 11 is 3.48. I use KDE Plasma version 5.26.90. The KDE Frameworks version is 5.102.0. I get pop-up notes from KDE that evolution has received new messages. But the messages don't appear in Evolution. I know it's not a mail server problem because I can read the messages in Firefox -- but Firefox doesn't have access to my archive, so I can't save anything (on my own computer). If I were to work out how to get Firefox to save them, and if I ever get Evolution working again, the messages won't be in Evolution's format, and the other Evolution data structures won't be updated. There was a note about "messages not appearing in Evolution" many years ago. It turned out to have been caused by the user's configuration mistake. When I looked for that mistake in my configuration (which I hadn't touched), I hadn't made it. Does anybody have any suggestions to get it working? When I installed Debian 11, I didn't destroy Debian 10. I still have Debian 10 on a different drive. In attempting to repair an entirely different problem, I had done apt-get update; apt-get upgrade on the advice of a posting in one of the Debian forums. Now, in Debian 10, there's a mish-mash of Debian 11 parts. Evolution is version 3.46. It works, but the user interface is now a mess. Icons are tiny and in different places. The body has a black border between itself and the window border. The title bar for the composer is entirely different from the title bar of any other window -- about three times as thick, containing several icons, including the "send" icon. Does anybody have any suggestions to repair it?
Re: awk not just using the Field separator as such. it is using the blank space as well ...
On 2/21/23, Greg Wooledge wrote: > I have a funny feeling Albretch might be using Microsoft file systems > (FAT, NTFS) for a large chunk of his system. Those have a much larger > set of restricted characters. Certainly not FAT32 and definitely not FAT, but at work (I work as a Math teacher and most schools use Microsoft) I have had to use WSL and NTFS. I always thought that FSs used length-defined raster data structures in order to avoid messing with points and such things. lbrtchx
KDE Frameworks 5.103.0 and KDE Plasma 5.27
Is Bookworm going to get Frameworks 5.103.0 and is there any estimated time when Bookworm will get Plasma 5.27? -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: Remove route '169.254.0.0/16 dev ovs-system'
On Tue, Feb 21, 2023 at 01:48:58PM -0500, Jeffrey Walton wrote: > On Tue, Feb 21, 2023 at 1:26 PM Christoph Brinkhaus > wrote: > > [...] > > > But backing up... I suspect there's something wrong with your static > > > ip address assignment. The address is already taken, the netmask is > > > wrong, or the gateway is wrong. > > > > > > Looking back through this thread, I did not see where you showed your > > > static ip configuration. Maybe you should start with that. If it is > > > bad, then the APIPA is just a symptom of the [static ip address] > > > problem. > > > > This is the systemd-networkd configuration: > > > > [Match] > > Name=w* > > > > [Network] > > DHCP=no > > Address=192.168.0.62/24 > > Gateway=192.168.0.32 > > DNS=127.0.0.1 > > > > I have unbound as a DNS listening at localhost. But with > > DNS=192.168.0.32 the behaviour has been similar. > > > > I have not yet checked the address assignment using systemd-networkd. > > For doing so I have to reinstall some packages. > > I don't know what the Match section does. I am suspicious of it. > > 192.168.0.0 address block is /16, not /24. No, typically it's 24. Traditionally these were 256 /24 nets; these days we have CIDR, so you can do whatever you like -- you only have to keep it consistent across your network. So /16 isn't wrong, but /24 isn't either, meaning in that case the range 192.168.0.1..192.168.0.254, depending on what you snip away at top or bottom, that is. > I'm in the US, and I use Verizon for my ISP. Verizon gadgets, like set > top boxes and media centers, use 192.168.0.x addresses. I never put > anything on 192.168.0.x. I start with 192.168.1.x. And on the Verizon > network, I've never seen a 192.168.0.x gateway. Gateways also go on > 192.168.1.x. So I'm a bit suspicious of the network assignments. No, this is perfectly fine. Cheers -- t signature.asc Description: PGP signature
Re: Remove route '169.254.0.0/16 dev ovs-system'
On Tue, Feb 21, 2023 at 1:26 PM Christoph Brinkhaus wrote: > [...] > > But backing up... I suspect there's something wrong with your static > > ip address assignment. The address is already taken, the netmask is > > wrong, or the gateway is wrong. > > > > Looking back through this thread, I did not see where you showed your > > static ip configuration. Maybe you should start with that. If it is > > bad, then the APIPA is just a symptom of the [static ip address] > > problem. > > This is the systemd-networkd configuration: > > [Match] > Name=w* > > [Network] > DHCP=no > Address=192.168.0.62/24 > Gateway=192.168.0.32 > DNS=127.0.0.1 > > I have unbound as a DNS listening at localhost. But with > DNS=192.168.0.32 the behaviour has been similar. > > I have not yet checked the address assignment using systemd-networkd. > For doing so I have to reinstall some packages. I don't know what the Match section does. I am suspicious of it. 192.168.0.0 address block is /16, not /24. I'm in the US, and I use Verizon for my ISP. Verizon gadgets, like set top boxes and media centers, use 192.168.0.x addresses. I never put anything on 192.168.0.x. I start with 192.168.1.x. And on the Verizon network, I've never seen a 192.168.0.x gateway. Gateways also go on 192.168.1.x. So I'm a bit suspicious of the network assignments. Jeff
Re: Remove route '169.254.0.0/16 dev ovs-system'
Am Tue, Feb 21, 2023 at 01:06:01PM -0500 schrieb Jeffrey Walton: > On Tue, Feb 21, 2023 at 12:45 PM Christoph Brinkhaus > wrote: > > Am Tue, Feb 21, 2023 at 11:00:56PM +0700 schrieb Max Nikulin: > > > On 20/02/2023 21:44, Christoph Brinkhaus wrote: > > > > Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max > > > > Perhaps to > > > > get rid of 169.254.x.y addresses, it is enough to properly > > > > > configure network interface, either to ensure that DHCP server is > > > > > available > > > > > or to assign a static address. After that you may forget about > > > > > existence of > > > > > avahi-autoipd. > > > > > > > > On my system it did not help. One "issue" might be, that systemd > > > > starts services in some sequence. But it does not wait for a service > > > > to complete. At least in case of stuff I have observed on my system. > > > > > > Out of curiosity, is link-local IP address assigned during boot or later > > > when e.g. WiFi connection is temporary lost? How long does it take to get > > > response from DHCP server? Which way network is configured (ifupdown, > > > NetworkManager, systemd-networkd) in your case? > > > > The 169.254.x.y has been assigned during boot. I have not used DHCP. > > The configuration has been static. The ping to the router takes about > > 4ms. I have no idea if it is possible to estimate a DHCP response > > time. The network has been configured via systemd-networking. > > You have to supply a static ip address or a DHCP server. This is correct. > > Since you supplied a static ip address, then the fact that you are > getting an APIPA is a bug. You should file a bug report with the > package (Avahi? Systemd?) that is providing the APIPA. I assume that there might be a timing issue with systemd-networking. A comparable happened with fetchmail started by systemd. The head of the description is [Unit] Description=A remote mail retrieval and forwarding utility After=network-online.target opensmtpd.service unbound.service Requires=opensmtpd.service unbound.service But fetchmail starts before the dependencies have been finished. I am not sure if systemd monitors the services to finish or if it just starts them in a specific order. > But backing up... I suspect there's something wrong with your static > ip address assignment. The address is already taken, the netmask is > wrong, or the gateway is wrong. > > Looking back through this thread, I did not see where you showed your > static ip configuration. Maybe you should start with that. If it is > bad, then the APIPA is just a symptom of the [static ip address] > problem. This is the systemd-networkd configuration: [Match] Name=w* [Network] DHCP=no Address=192.168.0.62/24 Gateway=192.168.0.32 DNS=127.0.0.1 I have unbound as a DNS listening at localhost. But with DNS=192.168.0.32 the behaviour has been similar. I have not yet checked the address assignment using systemd-networkd. For doing so I have to reinstall some packages. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Remove route '169.254.0.0/16 dev ovs-system'
Hi. On Tue, Feb 21, 2023 at 06:44:38PM +0100, Christoph Brinkhaus wrote: > I have no idea if it is possible to estimate a DHCP response time. sudo nmap --script broadcast-dhcp-discover Reco
Re: Remove route '169.254.0.0/16 dev ovs-system'
On Tue, Feb 21, 2023 at 12:45 PM Christoph Brinkhaus wrote: > Am Tue, Feb 21, 2023 at 11:00:56PM +0700 schrieb Max Nikulin: > > On 20/02/2023 21:44, Christoph Brinkhaus wrote: > > > Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max > > > > Perhaps to > > > get rid of 169.254.x.y addresses, it is enough to properly > > > > configure network interface, either to ensure that DHCP server is > > > > available > > > > or to assign a static address. After that you may forget about > > > > existence of > > > > avahi-autoipd. > > > > > > On my system it did not help. One "issue" might be, that systemd > > > starts services in some sequence. But it does not wait for a service > > > to complete. At least in case of stuff I have observed on my system. > > > > Out of curiosity, is link-local IP address assigned during boot or later > > when e.g. WiFi connection is temporary lost? How long does it take to get > > response from DHCP server? Which way network is configured (ifupdown, > > NetworkManager, systemd-networkd) in your case? > > The 169.254.x.y has been assigned during boot. I have not used DHCP. > The configuration has been static. The ping to the router takes about > 4ms. I have no idea if it is possible to estimate a DHCP response > time. The network has been configured via systemd-networking. You have to supply a static ip address or a DHCP server. Since you supplied a static ip address, then the fact that you are getting an APIPA is a bug. You should file a bug report with the package (Avahi? Systemd?) that is providing the APIPA. But backing up... I suspect there's something wrong with your static ip address assignment. The address is already taken, the netmask is wrong, or the gateway is wrong. Looking back through this thread, I did not see where you showed your static ip configuration. Maybe you should start with that. If it is bad, then the APIPA is just a symptom of the [static ip address] problem. Jeff
Re: Remove route '169.254.0.0/16 dev ovs-system'
Am Tue, Feb 21, 2023 at 11:00:56PM +0700 schrieb Max Nikulin: > On 20/02/2023 21:44, Christoph Brinkhaus wrote: > > Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max Nikulin: Hello Max, > > > Perhaps to get rid of 169.254.x.y addresses, it is enough to properly > > > configure network interface, either to ensure that DHCP server is > > > available > > > or to assign a static address. After that you may forget about existence > > > of > > > avahi-autoipd. > > > > On my system it did not help. One "issue" might be, that systemd > > starts services in some sequence. But it does not wait for a service > > to complete. At least in case of stuff I have observed on my system. > > Out of curiosity, is link-local IP address assigned during boot or later > when e.g. WiFi connection is temporary lost? How long does it take to get > response from DHCP server? Which way network is configured (ifupdown, > NetworkManager, systemd-networkd) in your case? The 169.254.x.y has been assigned during boot. I have not used DHCP. The configuration has been static. The ping to the router takes about 4ms. I have no idea if it is possible to estimate a DHCP response time. The network has been configured via systemd-networking. In the current setup I have removed a lot of packages I did not make use of. Additionally I have switched to systemd-networkd. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Re: Remove route '169.254.0.0/16 dev ovs-system'
On 20/02/2023 21:44, Christoph Brinkhaus wrote: Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max Nikulin: Perhaps to get rid of 169.254.x.y addresses, it is enough to properly configure network interface, either to ensure that DHCP server is available or to assign a static address. After that you may forget about existence of avahi-autoipd. On my system it did not help. One "issue" might be, that systemd starts services in some sequence. But it does not wait for a service to complete. At least in case of stuff I have observed on my system. Out of curiosity, is link-local IP address assigned during boot or later when e.g. WiFi connection is temporary lost? How long does it take to get response from DHCP server? Which way network is configured (ifupdown, NetworkManager, systemd-networkd) in your case?
Re: Fw: python thinking at debian
On 20/02/2023 20:59, Vic Cekvenich wrote: ... I think that is the goal for all of us. ... I did/do apt install python3-pip and python3-venv and python ensurepip still does not work. But if I do pyenv to build, all of python works well. There is large gap between too generic goal "can develop" and too specific issue that ensurepip does not work for you. Details related to intermediate level task is missed, so it is difficult to say if it is a real problem or just a bit different way for similar actions is assumed by developers. What you consider as restrictions may help to ensure that other packages can rely on sane enough environment. Debian bug tracker or mailing list archive may contain discussion why some limitations were added and what approach (venv, etc.) allows to get work done. /usr/share/doc/python3.*-venv/README.Debian /usr/share/doc/python3/python-policy.txt.gz May contain some hints.
Re: ps and AIX field descriptors
David Wright writes:
> On Mon 20 Feb 2023 at 10:39:21 (+0100), Andreas Leha wrote:
>> Greg Wooledge writes:
>> > On Sun, Feb 19, 2023 at 12:04:22PM -0600, David Wright wrote:
>> >> But even that's not enough
>> >> because the field width is somewhat variable: try ps -eo '%c | %z |
>> >> %a'
>> >> (We can still use | to make the problem somewhat more obvious.)
>> >
>> > Oh wow. Yeah, OK, that's not really solvable.
>> >
>> > For those who don't want to try to reverse engineer David's conclusion,
>> > or who don't just happen to stumble upon it with their current process
>> > list, here's what I'm seeing:
>> >
>> > COMMAND | VSZ | COMMAND
>> > systemd | 164140 | /sbin/init
>> > kthreadd | 0 | [kthreadd]
>> > rcu_gp | 0 | [rcu_gp]
>> > rcu_par_gp | 0 | [rcu_par_gp]
>> > [...]
>> > steamwebhelper | 4631064 | /home/greg/.steam/debian-installation/[...]
>> > [...]
>> > chrome_crashpad | 33567792 |
>> > /opt/google/chrome/chrome_crashpad_handler[...]
>> > [...]
>> > kworker/3:0-eve | 0 | [kworker/3:0-events]
>> >
>> > ps appears to guess an initial maximum width for the VSZ field, but
>> > when a value comes along that exceeds the guessed maximum, it simply
>> > shoves the field barrier over. It doesn't even become the new maximum,
>> > with all of the fields aligning after that. It's just a one-time shove,
>> > breaking the current line only.
>> >
>> > Therefore, parsing the header line cannot give us enough information to
>> > insert field separators correctly in body lines after the fact.
>>
>>
>> Dear all,
>>
>> Thanks for chiming in. The example was indeed simplified and I am using
>> %a which can contain internal whitespace.
>>
>> This is the command I was using previously:
>>
>> ps -eo '%p|%c|%C' -o "%mem" -o '|%a' --sort=-%cpu
>>
>> I now replaced it with
>>
>> ps -eo '%p %c %C' -o "%mem" -o ' %a' --sort=-%cpu | sed -E 's/([0-9]+)
>> (.+) ([0-9]+.?[0-9]?) ([0-9]+.?[0-9]?) (.+)/\1|\2|\3|\4|\5/'
>>
>> This works, but is of course cumbersome to maintain.
>>
>> Again, thanks for all the comments!
>
> I think there are a few too many assumptions in there;
> in particular, numbers in %a will match patterns designed
> to match cpu and mem, because you can't prevent sed from
> being greedy (except with the [^ … … ]+ construction, to
> restrict what it matches).
>
> This version makes a few assumptions as well:
> . that the new format matches the old one (mine) if the
> delimiters given are a single space (like '%p %c %C'),
> or stripped (like "%mem" and '%a', but not ' %a').
> . the short command is always 15 chars wide even if all
> the commands in the table are shorter, eg with ps -o.
> . I don't have any of those new-fangled extra-long PIDs
> yet today.
>
> It might well break if a CPU or MEM is running at 100%.
> That's not easily tested here.
>
> I've reordered the columns on the first pass, so that the
> numeric ones (with their limited character set) come first,
> which means I can use an auxiliary character for
> correcting the spacing. (The spaces between the columns get
> comingled with the leading spaces of numbers.) The second
> pass sorts that out and processes the heading.
>
> $ ps -eo '%p %c %C' -o "%mem" -o '%a' --sort=-%cpu | sed -E 's/( *[0-9]+)
> (.{15})( +[0-9.]+ +[0-9.]+) (.*$)/\1~\3~\2\4/;' | sed -E 's/([^~]+)~
> ([^~]+)~(.{15})(.*)/\1|\3|\2|\4/;s/^( *PID) (COMMAND) /\1|\2|/;s/%MEM
> COMMAND/%MEM|COMMAND/;' | less
> $
>
> This is the same, except I deliberately chose _ for the auxiliary
> character, knowing that short commands are stuffed with underscores:
>
> $ ps -eo '%p %c %C' -o "%mem" -o '%a' --sort=-%cpu | sed -E 's/( *[0-9]+)
> (.{15})( +[0-9.]+ +[0-9.]+) (.*$)/\1_\3_\2\4/;' | sed -E 's/([^_]+)_
> ([^_]+)_(.{15})(.*)/\1|\3|\2|\4/;s/^( *PID) (COMMAND) /\1|\2|/;s/%MEM
> COMMAND/%MEM|COMMAND/;' | less
> $
>
> Examples:
>
> PID|COMMAND|%CPU %MEM|COMMAND
>9798|firefox-esr| 2.5 5.8|firefox-esr
> 16143|Isolated Web Co| 1.8 2.2|/usr/lib/firefox-esr/firefox-esr
> -contentproc -childID 11 -isForBrowser -prefsLen 47676 -prefMapSize 232307
> -jsInitLen 277276 -parentBuildID 20230214011352 -appDir
> /usr/lib/firefox-esr/browser 9798 true tab
>1242|Xorg | 1.0 1.4|/usr/lib/xorg/Xorg -nolisten tcp :0 vt1
> -keeptty -auth /tmp/serverauth.FxvBp8B7Qn
> [ … ]
> 8|mm_percpu_wq | 0.0 0.0|[mm_percpu_wq]
> 9|rcu_tasks_rude_| 0.0 0.0|[rcu_tasks_rude_]
> 10|rcu_tasks_trace| 0.0 0.0|[rcu_tasks_trace]
>
> An incestuous one, with -o rather -eo:
>
> PID|COMMAND|%CPU %MEM|COMMAND
>1694|bash | 0.0 0.1|bash
> 23486|ps | 0.0 0.0|ps -o %p %c %C -o %mem -o %a --sort=-%cpu
> 23487|sed| 0.0 0.0|sed -E s/( *[0-9]+) (.{15})( +[0-9.]+
> +[0-9.]+) (.*$)/\1~\3~\2\4/;
> 23488|sed| 0.0 0.0|sed -E s/([^~]+)~
>
Re: Test ECC memory
Anssi Saari wrote: > Dan Ritter writes: > > > We see ECC errors irregularly and infrequently on both Intel and > > AMD CPUs. > > How/where do you see those on a Debian system? I looked into this > briefly but didn't get anywhere. The kernel announces readiness during boot with: dmesg:[ 18.331561] EDAC amd64: Node 0: DRAM ECC enabled. and then an event looks like this: Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... kernel:[5964975.397283] [Hardware Error]: Corrected error, no action required. Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... kernel:[5964975.406226] [Hardware Error]: CPU:0 (15:2:0) MC4_STATUS[-|CE|MiscV|-|AddrV|-|-|CECC]: 0x9c04400040080a13 Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... kernel:[5964975.418574] [Hardware Error]: Error Addr: 0x001ed405ef50 Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... kernel:[5964975.426919] [Hardware Error]: MC4 Error (node 0): DRAM ECC error detected on the NB. Message from syslogd@HOSTNAME at Jan 25 15:05:51 ... kernel:[5964975.437370] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: RD, part-proc: RES (no timeout) If you see a bunch of these, you want to install edac-utils and run it to see if you have a bad DIMM. -dsr-
Re: awk not just using the Field separator as such. it is using the blank space as well ...
On Tue, Feb 21, 2023 at 05:19:13AM +, Tim Woodall wrote: > On Mon, 20 Feb 2023, Albretch Mueller wrote: > > > On 2/15/23, Greg Wooledge wrote: > > > > The reason why I use pipes as field delimiter is because it is an > > excellent meta character when you are working with filesystems. Pipes > > would not accepted for files or directory names for good reasons, > > anyway. > > > > tim@einstein(7):~ (none)$ touch 'i|use|pipes' > tim@einstein(7):~ (none)$ ls -l i*use* > -rw-rw-r-- 1 tim tim 0 Feb 21 05:14 'i|use|pipes' > tim@einstein(7):~ (none)$ rm i\|use\|pipes > tim@einstein(7):~ (none)$ > > AFAIR only / and nul are prohibited in file names. In Unix-like file systems, including Debian's default ext4, this is true. I have a funny feeling Albretch might be using Microsoft file systems (FAT, NTFS) for a large chunk of his system. Those have a much larger set of restricted characters.
Re: Test ECC memory
krys...@ibse.cz writes: > PS: Some commercial memtests should allegedly be able to inject ECC > errors (for example the one from passmark), have anyone tried those? I've tried Passmark's memory tester (the commercial one which includes ECC error injection), but I've had no luck. My desktop has issues with mouse and keyboard support in it and Grub as well, it's so bad it's practically impossible to do anything. It's my only "modern" system with a Ryzen 5600X and ECC RAM. My router and file server have ECC RAM but those systems are BIOS only and I can't boot Passmark's thing on them since it requires UEFI. I have an oldish Intel laptop with ECC RAM also which is apparently the only one of my computers where Passmark's thing could run. Haven't tried it though.
Re: Test ECC memory
Dan Ritter writes: > We see ECC errors irregularly and infrequently on both Intel and > AMD CPUs. How/where do you see those on a Debian system? I looked into this briefly but didn't get anywhere.
Comment configurer en dur le monitoring batterie
Bonjour J'utilise mate pour le bureau graphique de mon portable. Et je ne comprends pas pourquoi le widget de monitoring d'utilisation de la batterie apparait aléatoirement. Lorsque je suis sur le secteur, qu'il apparaisse puis disparaisse n'a pas d'importance mais sur batterie, ça peut être gênant. Savez vous comment configurer en dur, le fichier de conf de ce "widget"? A moins que vous connaissiez une alternative à me suggéré? Merci par avance. -- AI Gestionnaire d'infrastructure/ Gestionnaire de Parc. Centre d'économie S** Monero (XMR) - The secure, private, untraceable cryptocurrency that keeps your money confidential. Grassroots. Open source. Dedicated to privacy & freedom. Monero || #xmrBEGIN:VCARD VERSION:4.0 N:P.;Olivier;;; NICKNAME:Backup my Spare EMAIL;PREF=1:backup.my.sp...@gmail.com URL:https://Deployadmin.com TZ:Europe/Paris FN:Olivier P. ADR:;;;Rambouillet;;78120;France END:VCARD smime.p7s Description: Signature cryptographique S/MIME
Re: Looking for an advanced offline touch typing tutor
On Mon, Feb 20, 2023 at 9:04 AM Yassine Chaouche wrote: > > I've been thinking : > why does the space bar span 6 keys? The space originated as two keys, one on each side of the typewriter. When it was implemented, the designers decided to join the two keys into a bar. http://xahlee.info/kbd/typewriter_spacebar_history.html > should I try another layout? > I heard dvorak was optimal. > What do you think about it? Jeff
