You are not logged in.
- Topics: Active | Unanswered
#201 Re: Hardware & System Configuration » [SOLVED] Suspend lockup lately » 2025-01-13 15:14:25
Late follow up on the problem: looks like the problem is due to a combination of a Toshiba Transmemory USB3 stick connected to a Sempre UP33-I19 USB3-card with a NEC 720201 chipset that is installed in my PC case to serve an Akasa USB-C output.
pm-hibernate as root
2025-01-13T14:38:03.015716+01:00 rh060 kernel: [18658.266669] PM: hibernation: hibernation entry
2025-01-13T14:38:03.015733+01:00 rh060 kernel: [18658.267856] Filesystems sync: 0.000 seconds
2025-01-13T14:38:03.015733+01:00 rh060 kernel: [18658.267940] Freezing user space processes
2025-01-13T14:38:03.015795+01:00 rh060 kernel: [18658.269309] Freezing user space processes completed (elapsed 0.001 seconds)
2025-01-13T14:38:03.015797+01:00 rh060 kernel: [18658.269311] OOM killer disabled.
2025-01-13T14:38:03.015799+01:00 rh060 kernel: [18658.269853] PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
2025-01-13T14:38:03.015800+01:00 rh060 kernel: [18658.269856] PM: hibernation: Marking nosave pages: [mem 0x000a0000-0x000fffff]
2025-01-13T14:38:03.015800+01:00 rh060 kernel: [18658.269859] PM: hibernation: Marking nosave pages: [mem 0x09d1f000-0x09ffffff]
2025-01-13T14:38:03.015800+01:00 rh060 kernel: [18658.269874] PM: hibernation: Marking nosave pages: [mem 0x0a200000-0x0a20dfff]
2025-01-13T14:38:03.015801+01:00 rh060 kernel: [18658.269876] PM: hibernation: Marking nosave pages: [mem 0xc3273000-0xc3273fff]
2025-01-13T14:38:03.015801+01:00 rh060 kernel: [18658.269877] PM: hibernation: Marking nosave pages: [mem 0xc8a4f000-0xc8a4ffff]
2025-01-13T14:38:03.015801+01:00 rh060 kernel: [18658.269879] PM: hibernation: Marking nosave pages: [mem 0xc9f76000-0xcb9fefff]
2025-01-13T14:38:03.015802+01:00 rh060 kernel: [18658.270001] PM: hibernation: Marking nosave pages: [mem 0xcd000000-0xffffffff]
2025-01-13T14:38:03.015802+01:00 rh060 kernel: [18658.271592] PM: hibernation: Basic memory bitmaps created
2025-01-13T14:38:03.015803+01:00 rh060 kernel: [18658.272090] PM: hibernation: Preallocating image memory
2025-01-13T14:38:03.015803+01:00 rh060 kernel: [18660.242343] PM: hibernation: Allocated 1215042 pages for snapshot
2025-01-13T14:38:03.015803+01:00 rh060 kernel: [18660.242347] PM: hibernation: Allocated 4860168 kbytes in 1.97 seconds (2467.09 MB/s)
2025-01-13T14:38:03.015804+01:00 rh060 kernel: [18660.242350] Freezing remaining freezable tasks
2025-01-13T14:38:03.015804+01:00 rh060 kernel: [18660.243553] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
2025-01-13T14:38:03.015804+01:00 rh060 kernel: [18660.297203] printk: Suspending console(s) (use no_console_suspend to debug)
2025-01-13T14:38:03.015804+01:00 rh060 kernel: [18660.503010] xhci_hcd 0000:05:00.0: PM: pci_pm_freeze(): hcd_pci_suspend [usbcore] returns -16
2025-01-13T14:38:03.015805+01:00 rh060 kernel: [18660.503027] xhci_hcd 0000:05:00.0: PM: dpm_run_callback(): pci_pm_freeze returns -16
2025-01-13T14:38:03.015805+01:00 rh060 kernel: [18660.503032] xhci_hcd 0000:05:00.0: PM: failed to freeze async: error -16
2025-01-13T14:38:03.015805+01:00 rh060 kernel: [18660.527764] amdgpu 0000:0c:00.0: amdgpu: MODE1 reset
2025-01-13T14:38:03.015806+01:00 rh060 kernel: [18660.527767] amdgpu 0000:0c:00.0: amdgpu: GPU mode1 reset
2025-01-13T14:38:03.015806+01:00 rh060 kernel: [18660.527841] amdgpu 0000:0c:00.0: amdgpu: GPU psp mode1 reset
2025-01-13T14:38:03.015806+01:00 rh060 kernel: [18661.042508] [drm] psp mode1 reset succeed
2025-01-13T14:38:03.015807+01:00 rh060 kernel: [18661.360235] usb usb3: root hub lost power or was reset
2025-01-13T14:38:03.015807+01:00 rh060 kernel: [18661.360239] usb usb4: root hub lost power or was reset
2025-01-13T14:38:03.015807+01:00 rh060 kernel: [18661.360310] usb usb5: root hub lost power or was reset
2025-01-13T14:38:03.015808+01:00 rh060 kernel: [18661.360313] usb usb6: root hub lost power or was reset
2025-01-13T14:38:03.015808+01:00 rh060 kernel: [18661.360367] usb usb7: root hub lost power or was reset
2025-01-13T14:38:03.015808+01:00 rh060 kernel: [18661.360369] usb usb8: root hub lost power or was reset
2025-01-13T14:38:03.015809+01:00 rh060 kernel: [18661.370639] nvme nvme0: D3 entry latency set to 10 seconds
2025-01-13T14:38:03.015809+01:00 rh060 kernel: [18661.371566] nvme nvme0: 8/0/0 default/read/poll queues
2025-01-13T14:38:03.015809+01:00 rh060 kernel: [18661.371873] nvme nvme0: Ignoring bogus Namespace Identifiers
2025-01-13T14:38:03.015810+01:00 rh060 kernel: [18661.392492] nvme nvme1: 24/0/0 default/read/poll queues
2025-01-13T14:38:03.015810+01:00 rh060 kernel: [18661.654600] usb 5-4: reset full-speed USB device number 2 using xhci_hcd
2025-01-13T14:38:03.015810+01:00 rh060 kernel: [18661.654603] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
2025-01-13T14:38:03.015810+01:00 rh060 kernel: [18661.654606] usb 7-4: reset full-speed USB device number 6 using xhci_hcd
2025-01-13T14:38:03.015821+01:00 rh060 kernel: [18661.834233] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T14:38:03.015822+01:00 rh060 kernel: [18661.834262] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T14:38:03.015823+01:00 rh060 kernel: [18661.834353] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T14:38:03.015823+01:00 rh060 kernel: [18661.834380] ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T14:38:03.015823+01:00 rh060 kernel: [18661.834674] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015824+01:00 rh060 kernel: [18661.835016] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015824+01:00 rh060 kernel: [18661.835141] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015825+01:00 rh060 kernel: [18661.835858] sd 8:0:0:0: [sdb] Starting disk
2025-01-13T14:38:03.015825+01:00 rh060 kernel: [18661.835866] sd 5:0:0:0: [sdc] Starting disk
2025-01-13T14:38:03.015826+01:00 rh060 kernel: [18661.835962] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015826+01:00 rh060 kernel: [18661.836033] sd 9:0:0:0: [sdd] Starting disk
2025-01-13T14:38:03.015826+01:00 rh060 kernel: [18661.836133] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015827+01:00 rh060 kernel: [18661.836693] ata6.00: configured for UDMA/133
2025-01-13T14:38:03.015827+01:00 rh060 kernel: [18661.836864] ata10.00: configured for UDMA/133
2025-01-13T14:38:03.015828+01:00 rh060 kernel: [18661.837367] ata9.00: configured for UDMA/133
2025-01-13T14:38:03.015828+01:00 rh060 kernel: [18661.838231] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T14:38:03.015829+01:00 rh060 kernel: [18661.838259] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T14:38:03.015829+01:00 rh060 kernel: [18661.839512] sd 4:0:0:0: [sda] Starting disk
2025-01-13T14:38:03.015829+01:00 rh060 kernel: [18661.839728] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015830+01:00 rh060 kernel: [18661.841066] ata4.00: configured for UDMA/133
2025-01-13T14:38:03.015830+01:00 rh060 kernel: [18661.841448] ata3.00: configured for UDMA/100
2025-01-13T14:38:03.015830+01:00 rh060 kernel: [18661.844526] ata5.00: configured for UDMA/133
2025-01-13T14:38:03.015831+01:00 rh060 kernel: [18661.854762] ata5.00: Enabling discard_zeroes_data
2025-01-13T14:38:03.015831+01:00 rh060 kernel: [18661.930270] usb 7-1: reset high-speed USB device number 2 using xhci_hcd
2025-01-13T14:38:03.015831+01:00 rh060 kernel: [18661.930483] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd
2025-01-13T14:38:03.015832+01:00 rh060 kernel: [18662.100380] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
2025-01-13T14:38:03.015832+01:00 rh060 kernel: [18662.100413] amdgpu 0000:0c:00.0: amdgpu: PSP is resuming...
2025-01-13T14:38:03.015832+01:00 rh060 kernel: [18662.206308] usb 7-3: reset full-speed USB device number 3 using xhci_hcd
2025-01-13T14:38:03.015833+01:00 rh060 kernel: [18662.255679] amdgpu 0000:0c:00.0: amdgpu: reserve 0x900000 from 0x81fd000000 for PSP TMR
2025-01-13T14:38:03.015833+01:00 rh060 kernel: [18662.298741] amdgpu 0000:0c:00.0: amdgpu: RAS: optional ras ta ucode is not available
2025-01-13T14:38:03.015833+01:00 rh060 kernel: [18662.304815] amdgpu 0000:0c:00.0: amdgpu: RAP: optional rap ta ucode is not available
2025-01-13T14:38:03.015834+01:00 rh060 kernel: [18662.304816] amdgpu 0000:0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
2025-01-13T14:38:03.015834+01:00 rh060 kernel: [18662.304819] amdgpu 0000:0c:00.0: amdgpu: SMU is resuming...
2025-01-13T14:38:03.015834+01:00 rh060 kernel: [18662.304858] amdgpu 0000:0c:00.0: amdgpu: use vbios provided pptable
2025-01-13T14:38:03.015834+01:00 rh060 kernel: [18662.304860] amdgpu 0000:0c:00.0: amdgpu: smc_dpm_info table revision(format.content): 4.5
2025-01-13T14:38:03.015835+01:00 rh060 kernel: [18662.336805] amdgpu 0000:0c:00.0: amdgpu: SMU is resumed successfully!
2025-01-13T14:38:03.015835+01:00 rh060 kernel: [18662.483338] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
2025-01-13T14:38:03.015835+01:00 rh060 kernel: [18662.582272] usb 7-1.4: reset high-speed USB device number 5 using xhci_hcd
2025-01-13T14:38:03.015836+01:00 rh060 kernel: [18662.759659] [drm] kiq ring mec 2 pipe 1 q 0
2025-01-13T14:38:03.015837+01:00 rh060 kernel: [18662.761300] amdgpu 0000:0c:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
2025-01-13T14:38:03.015837+01:00 rh060 kernel: [18662.761302] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
2025-01-13T14:38:03.015837+01:00 rh060 kernel: [18662.761303] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
2025-01-13T14:38:03.015838+01:00 rh060 kernel: [18662.761304] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
2025-01-13T14:38:03.015838+01:00 rh060 kernel: [18662.761305] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
2025-01-13T14:38:03.015838+01:00 rh060 kernel: [18662.761306] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
2025-01-13T14:38:03.015839+01:00 rh060 kernel: [18662.761307] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
2025-01-13T14:38:03.015839+01:00 rh060 kernel: [18662.761308] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
2025-01-13T14:38:03.015839+01:00 rh060 kernel: [18662.761309] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
2025-01-13T14:38:03.015839+01:00 rh060 kernel: [18662.761310] amdgpu 0000:0c:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
2025-01-13T14:38:03.015840+01:00 rh060 kernel: [18662.761311] amdgpu 0000:0c:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
2025-01-13T14:38:03.015840+01:00 rh060 kernel: [18662.761312] amdgpu 0000:0c:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
2025-01-13T14:38:03.015840+01:00 rh060 kernel: [18662.761312] amdgpu 0000:0c:00.0: amdgpu: ring vcn_dec uses VM inv eng 0 on hub 8
2025-01-13T14:38:03.015840+01:00 rh060 kernel: [18662.761313] amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 1 on hub 8
2025-01-13T14:38:03.015841+01:00 rh060 kernel: [18662.761314] amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 4 on hub 8
2025-01-13T14:38:03.015841+01:00 rh060 kernel: [18662.761315] amdgpu 0000:0c:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
2025-01-13T14:38:03.015841+01:00 rh060 kernel: [18662.762324] usb 7-1.2: reset full-speed USB device number 4 using xhci_hcd
2025-01-13T14:38:03.015842+01:00 rh060 kernel: [18662.866598] snd_hda_intel 0000:0c:00.1: CORB reset timeout#2, CORBRP = 65535
2025-01-13T14:38:03.015842+01:00 rh060 kernel: [18662.922449] PM: hibernation: Basic memory bitmaps freed
2025-01-13T14:38:03.015842+01:00 rh060 kernel: [18662.922562] OOM killer enabled.
2025-01-13T14:38:03.019240+01:00 rh060 kernel: [18662.922563] Restarting tasks ... done.
2025-01-13T14:38:03.019249+01:00 rh060 kernel: [18662.923108] PM: hibernation: hibernation exit
2025-01-13T14:38:03.419377+01:00 rh060 kernel: [18663.323104] usb 7-1.2: usbfs: process 3842 (pcscd) did not claim interface 0 before use
2025-01-13T14:38:04.234946+01:00 rh060 ntpd[3872]: IO: Deleting interface #3 eth0, 10.6.6.60#123, interface stats: received=819, sent=820, dropped=0, active_time=18628 secs
2025-01-13T14:38:04.234961+01:00 rh060 ntpd[3872]: PROTO: 78.47.249.55 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234964+01:00 rh060 ntpd[3872]: PROTO: 51.75.67.47 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234967+01:00 rh060 ntpd[3872]: PROTO: 148.251.5.46 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234970+01:00 rh060 ntpd[3872]: PROTO: 79.133.44.137 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234972+01:00 rh060 ntpd[3872]: PROTO: 185.252.140.125 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234975+01:00 rh060 ntpd[3872]: PROTO: 78.47.56.71 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234977+01:00 rh060 ntpd[3872]: PROTO: 10.6.6.1 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234982+01:00 rh060 ntpd[3872]: IO: Deleting interface #7 eth0, fe80::6d9:f5ff:fef7:e393%2#123, interface stats: received=0, sent=0, dropped=0, active_time=18625 secs
2025-01-13T14:38:04.387263+01:00 rh060 kernel: [18664.291086] igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
2025-01-13T14:38:04.492192+01:00 rh060 NetworkManager[3754]: <info> [1736775484.4921] device (eth0): carrier: link connected
2025-01-13T14:38:06.235158+01:00 rh060 ntpd[3872]: IO: Listen normally on 8 eth0 10.6.6.60:123
2025-01-13T14:38:06.235188+01:00 rh060 ntpd[3872]: IO: Listen normally on 9 eth0 [fe80::6d9:f5ff:fef7:e393%2]:123
2025-01-13T14:38:06.235276+01:00 rh060 ntpd[3872]: IO: new interface(s) found: waking up resolver
Enable Hibernation 5min in Power Settings, no reset
2025-01-13T15:01:13.570268+01:00 rh060 dbus-daemon[4639]: [session uid=1000 pid=4637] Activating service name='org.cinnamon.ScreenSaver' requested by ':1.117' (uid=1000 pid=4803 comm="/usr/bin/python3 /usr/bin/cinnamon-screensaver-com")
2025-01-13T15:01:13.660005+01:00 rh060 dbus-daemon[4639]: [session uid=1000 pid=4637] Successfully activated service 'org.cinnamon.ScreenSaver'
2025-01-13T15:01:13.686837+01:00 rh060 x-session-manager[4580]: WARNING: t+20007,36655s: Detected that screensaver has appeared on the bus
2025-01-13T15:01:13.980097+01:00 rh060 NetworkManager[3754]: <info> [1736776873.9800] manager: sleep: sleep requested (sleeping: no enabled: yes)
2025-01-13T15:01:14.063242+01:00 rh060 kernel: [20053.972322] PM: suspend entry (deep)
2025-01-13T15:01:15.143872+01:00 rh060 kernel: [20053.979809] Filesystems sync: 0.007 seconds
2025-01-13T15:01:15.143886+01:00 rh060 kernel: [20053.980366] Freezing user space processes
2025-01-13T15:01:15.143915+01:00 rh060 kernel: [20053.981758] Freezing user space processes completed (elapsed 0.001 seconds)
2025-01-13T15:01:15.143921+01:00 rh060 kernel: [20053.981760] OOM killer disabled.
2025-01-13T15:01:15.143922+01:00 rh060 kernel: [20053.981761] Freezing remaining freezable tasks
2025-01-13T15:01:15.143922+01:00 rh060 kernel: [20053.982365] Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
2025-01-13T15:01:15.143923+01:00 rh060 kernel: [20053.982383] printk: Suspending console(s) (use no_console_suspend to debug)
2025-01-13T15:01:15.143923+01:00 rh060 kernel: [20054.074417] sd 5:0:0:0: [sdc] Synchronizing SCSI cache
2025-01-13T15:01:15.143923+01:00 rh060 kernel: [20054.074593] ata6.00: Entering standby power mode
2025-01-13T15:01:15.143924+01:00 rh060 kernel: [20054.078380] sd 8:0:0:0: [sdb] Synchronizing SCSI cache
2025-01-13T15:01:15.143924+01:00 rh060 kernel: [20054.078753] ata9.00: Entering standby power mode
2025-01-13T15:01:15.143925+01:00 rh060 kernel: [20054.086362] sd 9:0:0:0: [sdd] Synchronizing SCSI cache
2025-01-13T15:01:15.143925+01:00 rh060 kernel: [20054.086541] ata10.00: Entering standby power mode
2025-01-13T15:01:15.143926+01:00 rh060 kernel: [20054.090369] sd 4:0:0:0: [sda] Synchronizing SCSI cache
2025-01-13T15:01:15.143926+01:00 rh060 kernel: [20054.090627] ata5.00: Entering standby power mode
2025-01-13T15:01:15.143927+01:00 rh060 kernel: [20054.234346] xhci_hcd 0000:05:00.0: PM: pci_pm_suspend(): hcd_pci_suspend [usbcore] returns -16
2025-01-13T15:01:15.143927+01:00 rh060 kernel: [20054.234363] xhci_hcd 0000:05:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -16
2025-01-13T15:01:15.143927+01:00 rh060 kernel: [20054.234368] xhci_hcd 0000:05:00.0: PM: failed to suspend async: error -16
2025-01-13T15:01:15.143928+01:00 rh060 kernel: [20054.855196] PM: Some devices failed to suspend, or early wake event detected
2025-01-13T15:01:15.143928+01:00 rh060 kernel: [20054.860801] nvme nvme0: D3 entry latency set to 10 seconds
2025-01-13T15:01:15.143928+01:00 rh060 kernel: [20054.861745] nvme nvme0: 8/0/0 default/read/poll queues
2025-01-13T15:01:15.143929+01:00 rh060 kernel: [20054.862081] nvme nvme0: Ignoring bogus Namespace Identifiers
2025-01-13T15:01:15.143929+01:00 rh060 kernel: [20054.885984] nvme nvme1: 24/0/0 default/read/poll queues
2025-01-13T15:01:15.143930+01:00 rh060 kernel: [20054.959228] snd_hda_intel 0000:0c:00.1: CORB reset timeout#2, CORBRP = 65535
2025-01-13T15:01:15.143930+01:00 rh060 kernel: [20055.054817] OOM killer enabled.
2025-01-13T15:01:15.147256+01:00 rh060 kernel: [20055.054819] Restarting tasks ... done.
2025-01-13T15:01:15.147261+01:00 rh060 kernel: [20055.055356] random: crng reseeded on system resumption
2025-01-13T15:01:15.147262+01:00 rh060 kernel: [20055.055360] PM: suspend exit
2025-01-13T15:01:15.147263+01:00 rh060 kernel: [20055.055417] PM: suspend entry (s2idle)
2025-01-13T15:01:15.423267+01:00 rh060 kernel: [20055.330670] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T15:01:15.423281+01:00 rh060 kernel: [20055.330671] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:15.423282+01:00 rh060 kernel: [20055.330705] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:15.423282+01:00 rh060 kernel: [20055.330710] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T15:01:15.423285+01:00 rh060 kernel: [20055.330736] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:15.423285+01:00 rh060 kernel: [20055.330766] ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:15.423286+01:00 rh060 kernel: [20055.331358] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.423286+01:00 rh060 kernel: [20055.331448] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.423286+01:00 rh060 kernel: [20055.331690] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.423287+01:00 rh060 kernel: [20055.332045] sd 8:0:0:0: [sdb] Starting disk
2025-01-13T15:01:15.423287+01:00 rh060 kernel: [20055.332470] sd 5:0:0:0: [sdc] Starting disk
2025-01-13T15:01:15.423288+01:00 rh060 kernel: [20055.332583] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.423288+01:00 rh060 kernel: [20055.332641] sd 9:0:0:0: [sdd] Starting disk
2025-01-13T15:01:15.423294+01:00 rh060 kernel: [20055.332740] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.423295+01:00 rh060 kernel: [20055.333344] ata9.00: configured for UDMA/133
2025-01-13T15:01:15.423295+01:00 rh060 kernel: [20055.333368] ata6.00: configured for UDMA/133
2025-01-13T15:01:15.423295+01:00 rh060 kernel: [20055.333397] ata6.00: Entering active power mode
2025-01-13T15:01:15.423295+01:00 rh060 kernel: [20055.333415] ata9.00: Entering active power mode
2025-01-13T15:01:15.423296+01:00 rh060 kernel: [20055.333477] ata10.00: configured for UDMA/133
2025-01-13T15:01:15.423296+01:00 rh060 kernel: [20055.333500] ata4.00: configured for UDMA/133
2025-01-13T15:01:15.423296+01:00 rh060 kernel: [20055.333947] ata3.00: configured for UDMA/100
2025-01-13T15:01:15.427250+01:00 rh060 kernel: [20055.336285] sd 4:0:0:0: [sda] Starting disk
2025-01-13T15:01:15.427255+01:00 rh060 kernel: [20055.336497] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.431247+01:00 rh060 kernel: [20055.341294] ata5.00: configured for UDMA/133
2025-01-13T15:01:15.443248+01:00 rh060 kernel: [20055.351586] ata5.00: Enabling discard_zeroes_data
2025-01-13T15:01:18.896987+01:00 rh060 kernel: [20055.356135] Filesystems sync: 0.300 seconds
2025-01-13T15:01:18.897006+01:00 rh060 kernel: [20055.356412] Freezing user space processes
2025-01-13T15:01:18.897035+01:00 rh060 kernel: [20055.482804] Freezing user space processes completed (elapsed 0.126 seconds)
2025-01-13T15:01:18.897035+01:00 rh060 kernel: [20055.482811] OOM killer disabled.
2025-01-13T15:01:18.897038+01:00 rh060 kernel: [20055.482813] Freezing remaining freezable tasks
2025-01-13T15:01:18.897038+01:00 rh060 kernel: [20055.484402] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
2025-01-13T15:01:18.897039+01:00 rh060 kernel: [20055.484408] printk: Suspending console(s) (use no_console_suspend to debug)
2025-01-13T15:01:18.897039+01:00 rh060 kernel: [20057.767244] igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
2025-01-13T15:01:18.897040+01:00 rh060 kernel: [20057.874382] sd 4:0:0:0: [sda] Synchronizing SCSI cache
2025-01-13T15:01:18.897040+01:00 rh060 kernel: [20057.874384] sd 5:0:0:0: [sdc] Synchronizing SCSI cache
2025-01-13T15:01:18.897041+01:00 rh060 kernel: [20057.874411] sd 8:0:0:0: [sdb] Synchronizing SCSI cache
2025-01-13T15:01:18.897041+01:00 rh060 kernel: [20057.874411] sd 9:0:0:0: [sdd] Synchronizing SCSI cache
2025-01-13T15:01:18.897042+01:00 rh060 kernel: [20057.874704] ata5.00: Entering standby power mode
2025-01-13T15:01:18.897042+01:00 rh060 kernel: [20057.874751] ata9.00: Entering standby power mode
2025-01-13T15:01:18.897043+01:00 rh060 kernel: [20057.875206] ata6.00: Entering standby power mode
2025-01-13T15:01:18.897044+01:00 rh060 kernel: [20057.875368] ata10.00: Entering standby power mode
2025-01-13T15:01:18.897044+01:00 rh060 kernel: [20058.034207] xhci_hcd 0000:05:00.0: PM: pci_pm_suspend(): hcd_pci_suspend [usbcore] returns -16
2025-01-13T15:01:18.897045+01:00 rh060 kernel: [20058.034223] xhci_hcd 0000:05:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -16
2025-01-13T15:01:18.897046+01:00 rh060 kernel: [20058.034228] xhci_hcd 0000:05:00.0: PM: failed to suspend async: error -16
2025-01-13T15:01:18.897046+01:00 rh060 kernel: [20058.508340] PM: Some devices failed to suspend, or early wake event detected
2025-01-13T15:01:18.897047+01:00 rh060 kernel: [20058.518054] nvme nvme0: D3 entry latency set to 10 seconds
2025-01-13T15:01:18.897047+01:00 rh060 kernel: [20058.518998] nvme nvme0: 8/0/0 default/read/poll queues
2025-01-13T15:01:18.897048+01:00 rh060 kernel: [20058.519304] nvme nvme0: Ignoring bogus Namespace Identifiers
2025-01-13T15:01:18.897048+01:00 rh060 kernel: [20058.538917] nvme nvme1: 24/0/0 default/read/poll queues
2025-01-13T15:01:18.897049+01:00 rh060 kernel: [20058.807923] OOM killer enabled.
2025-01-13T15:01:18.897141+01:00 rh060 ntpd[3872]: IO: Deleting interface #8 eth0, 10.6.6.60#123, interface stats: received=9, sent=9, dropped=0, active_time=1390 secs
2025-01-13T15:01:18.897154+01:00 rh060 ntpd[3872]: PROTO: 10.6.6.1 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897157+01:00 rh060 ntpd[3872]: PROTO: 78.47.56.71 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897160+01:00 rh060 ntpd[3872]: PROTO: 185.252.140.125 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897163+01:00 rh060 ntpd[3872]: PROTO: 79.133.44.137 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897165+01:00 rh060 ntpd[3872]: PROTO: 148.251.5.46 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897168+01:00 rh060 ntpd[3872]: PROTO: 51.75.67.47 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897171+01:00 rh060 ntpd[3872]: PROTO: 78.47.249.55 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897175+01:00 rh060 ntpd[3872]: IO: Deleting interface #9 eth0, fe80::6d9:f5ff:fef7:e393%2#123, interface stats: received=0, sent=0, dropped=0, active_time=1390 secs
2025-01-13T15:01:18.899242+01:00 rh060 kernel: [20058.807924] Restarting tasks ... done.
2025-01-13T15:01:18.899246+01:00 rh060 kernel: [20058.808548] random: crng reseeded on system resumption
2025-01-13T15:01:18.899247+01:00 rh060 kernel: [20058.808558] PM: suspend exit
2025-01-13T15:01:19.071283+01:00 rh060 kernel: [20058.978687] ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:19.071294+01:00 rh060 kernel: [20058.978688] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T15:01:19.071295+01:00 rh060 kernel: [20058.978722] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:19.071296+01:00 rh060 kernel: [20058.978723] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T15:01:19.071296+01:00 rh060 kernel: [20058.978754] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:19.071298+01:00 rh060 kernel: [20058.978789] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:19.071298+01:00 rh060 kernel: [20058.979358] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.071299+01:00 rh060 kernel: [20058.979623] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.071299+01:00 rh060 kernel: [20058.979639] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.071299+01:00 rh060 kernel: [20058.979956] sd 8:0:0:0: [sdb] Starting disk
2025-01-13T15:01:19.071300+01:00 rh060 kernel: [20058.980613] sd 5:0:0:0: [sdc] Starting disk
2025-01-13T15:01:19.071300+01:00 rh060 kernel: [20058.980627] sd 9:0:0:0: [sdd] Starting disk
2025-01-13T15:01:19.071301+01:00 rh060 kernel: [20058.980728] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.071301+01:00 rh060 kernel: [20058.980736] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.071301+01:00 rh060 kernel: [20058.981253] ata9.00: configured for UDMA/133
2025-01-13T15:01:19.071302+01:00 rh060 kernel: [20058.981321] ata9.00: Entering active power mode
2025-01-13T15:01:19.071302+01:00 rh060 kernel: [20058.981455] ata10.00: configured for UDMA/133
2025-01-13T15:01:19.071302+01:00 rh060 kernel: [20058.981523] ata4.00: configured for UDMA/133
2025-01-13T15:01:19.071303+01:00 rh060 kernel: [20058.981536] ata6.00: configured for UDMA/133
2025-01-13T15:01:19.071313+01:00 rh060 kernel: [20058.981565] ata6.00: Entering active power mode
2025-01-13T15:01:19.071314+01:00 rh060 kernel: [20058.981970] ata3.00: configured for UDMA/100
2025-01-13T15:01:19.075238+01:00 rh060 kernel: [20058.984345] sd 4:0:0:0: [sda] Starting disk
2025-01-13T15:01:19.075240+01:00 rh060 kernel: [20058.984558] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.079235+01:00 rh060 kernel: [20058.989351] ata5.00: configured for UDMA/133
2025-01-13T15:01:19.091249+01:00 rh060 kernel: [20058.999602] ata5.00: Enabling discard_zeroes_data
2025-01-13T15:01:21.655274+01:00 rh060 kernel: [20061.563217] igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
2025-01-13T15:01:21.760159+01:00 rh060 NetworkManager[3754]: <info> [1736776881.7601] device (eth0): carrier: link connected
2025-01-13T15:01:23.235138+01:00 rh060 ntpd[3872]: IO: Listen normally on 10 eth0 10.6.6.60:123
2025-01-13T15:01:23.235168+01:00 rh060 ntpd[3872]: IO: Listen normally on 11 eth0 [fe80::6d9:f5ff:fef7:e393%2]:123
2025-01-13T15:01:23.235268+01:00 rh060 ntpd[3872]: IO: new interface(s) found: waking up resolver
Illuminated keyboard shortly goes off, comes on again, screen saver is back, PC is working.These messages made me wonder:
2025-01-13T14:38:03.015804+01:00 rh060 kernel: [18660.503010] xhci_hcd 0000:05:00.0: PM: pci_pm_freeze(): hcd_pci_suspend [usbcore] returns -16
2025-01-13T14:38:03.015805+01:00 rh060 kernel: [18660.503027] xhci_hcd 0000:05:00.0: PM: dpm_run_callback(): pci_pm_freeze returns -16
2025-01-13T14:38:03.015805+01:00 rh060 kernel: [18660.503032] xhci_hcd 0000:05:00.0: PM: failed to freeze async: error -16The stick was present for some decryption experiments in a VBox VM I started some months ago. I never would have thought that leaving the stick connected to the Sempre adapter could cause suspend to hang. Anyhow, at least pm-hibernate now does its job, lets see how the Cinnamon based energy settings mechnism performs.
#202 Re: Off-topic » Thoughts on Pipewire » 2025-01-12 16:40:57
Just switched to Pipewire on my Daedalus workstation re-install. Works fine, easy start, same on my travelling laptop. I can't complain about any sound change or deficiency. Audacious immedialtely played my ripped CD files (wav), I can't say anything bad about quality.
Edith: pulse wasn't installed.
#203 Re: Other Issues » [SOLVED] Mounting HDD in a USB cradle » 2025-01-12 14:17:45
Yes, LVM is an additional layer. But as it looks like you have not really seen any issues for many years with it, so what? Ok it has its own terms you need to get used to like physical volume, volume group, logical volume, etc. Can be learned, there is a LVM HowTo in the internet. Just look for it. BTW: I am using LVM for many many years by now, no real issues with it.
#204 Re: Other Issues » [SOLVED] Mounting HDD in a USB cradle » 2025-01-11 21:13:28
vgchange -a y will do the job. Quote the output here please.
#205 Re: Hardware & System Configuration » [SOLVED] Entry in fstab but Authentication is still required to mount partition » 2025-01-08 17:09:12
When you write a partition table on a device no matter if its new or used already, create a new partition, format a partition, all of these are root tasks. There is no automatic permission for user access past that process.
To allow unprivileged user access to new drives/partitions, you will have to (as root again) change the ownership of the mount point in a single user case or for multiple users to create new directories on the device and assign individual user ownership with e.g. chown.
In addition, all modern desktops like Mate, Cinnamon, Gnome, KDE ... have automounter features that mount for example any USB stick with user rights to the desktop. At least for vfat, exfat drives. It becomes a bit more complicated with ntfs or Linux file systems like ext2/3/4.
You see its complex, depending on.
If you want that device LinuxDataExt-4TB to be permanently connected, I would first of all suggest to use a dedicated subdirectory under /mnt for that drive. Then it makes sense to create a fstab entry like:
Dev-UUID /mnt/xyz ext4 defaults 0 2
The 2 on the end makes sure the file system on the device is checked regularly. Nothing else is required.
In case its an external drive via USB, I do not use any fstab entry, I'll leave opening/mounting when connected to the automounter. They usually create something like /media/$USER/LinuxDataExt-4TB assuming "LinuxDataExt-4TB" is the label that is set on the device.
During the installation it is not directly possible to create/partition/include something like backup drives not really related to the system setup. That's a task for past the first successful boot of the system.
#206 Re: Installation » new installation with iso Devuan i386 Daedalus » 2025-01-07 09:35:04
Sorry, you sound like you take my comment very personally. Don't do that please. I try to help ...
I have seen these temporary failures myself every now and then. A simple repetition of the apt command worked fine for me. I never had a consistent blockage like several others. And yes, I have a mirror close by my location, but I stick to deb.devuan.org.
Some background: http://deb.devuan.org/merged does not represent a single dedicated server but stands for a list of servers all around the world that host a Devuan mirror. Somewhere on the Devuan website (you can find a link on top of this website) you can find this list:
https://www.devuan.org/get-devuan. Resolving this "round robin" scenario seems to cause issues in certain locations and with certain providers.
You have the following choices:
1.) Repeat the command until it works.
2.) Use another DNS like 8.8.8.8 or Quad Nine or anything you like.
3.) Try something like de.deb.devuan.org in your sources.list. Its not recommended by Devuan, but it may be worth a try.
4.) Select one of mirrors from the available ones and enter this into your sources.list.
Good luck
#207 Re: Installation » after the new installation, all my old entries in grub are erased! » 2025-01-06 21:19:31
Do you mean access to other operating systems? If yes that normal now ith Bookworm/Daedalus. Refer to the release notes. os-prober has been de-activated by default. To get that back you have to enable os-prober again and perform an update-grub.
#208 Re: Installation » new installation with iso Devuan i386 Daedalus » 2025-01-06 21:16:44
Why? DNS issues:
Temporary failure resolving 'deb.devuan.org'
Check your network settings and try again. Worked for me here in Germany with a German internet provider.
If it does not work, use a different DNS provider/resolver. Recently there have been several issues. Search the forum for threads.
#209 Re: Installation » [SOLVED] cannot boot netinstall iso » 2025-01-02 09:55:03
Well, a Ryzen 7700 is something pretty new. Maybe the CPU is not supported by the kernel that comes with Daedalus. The stick should boot.
Anyhow, CSM support has been removed for every new computer design past about 2020 based on a decision by the big industry protagonists. It will not come back. I also own an Acer laptop bought in 2020 that is UEFI only.
About writing the iso image to the stick: make sure you use the raw device, not any partition. Example: of=/dev/sda is correct, of=/dev/sda1 is wrong, won't work. Also make sure to use the 5.01 version.
Also Ventoy is useless since Daedalus.
Good luck.
#210 Re: Installation » [SOLVED] Sources.list hates me! » 2024-12-31 13:01:38
... the initial attempt was made as root and it came up in Libre Office Writer when moused ...
Take this as learning. Never ever attempt to modify any Linux conf or script file with anything else but a pure text editor. These kinda files are pure ASCII text, no control characters allowed but CR LF and maybe TAB. LO and like as Windows editors add characters that are not welcome in the Linux world.
Opposite to steve_v's opinion I am using geany as a gui multi-tab text editor to edit my confs and scripts as root for convenience. I am setting up a root terminal and a policy kit policy to enable to do that. When I call up geany from this root terminal I am getting all the files I ever fooled with on my system (unless I did not remove them from the list of files). This setup also allows easy copy/paste into the files.
#211 Re: Installation » [SOLVED] Sources.list hates me! » 2024-12-31 12:50:35
whatever happened to gksudo and kdsudo for elevated privileges in gui applications(i.e. mousepad, synaptic, etc.)?
gksu and so on have been replaced by pkexec and polkit policies some time ago. Somewhere in the release notes should be a note telling that gksu is depracated and removed from the distribution (inherited from Debian).
#212 Re: Hardware & System Configuration » Instructions for installing lightdm on new Devuan 5 installation? » 2024-12-30 11:07:29
Apt also provides a log, refer to /var/log/apt/history.log.
#213 Re: Freedom Hacks » Amazon mydedia » 2024-12-29 19:25:15
My private suggestion: look into free tools and devices instead of that proprietary stuff. You will be much happier.
I have a file server in the basement where I store my music files. And I use Audacious and a play list to play that music over my network on my PC.
#214 Re: Hardware & System Configuration » Instructions for installing lightdm on new Devuan 5 installation? » 2024-12-29 10:29:31
The command I gave installs all required dependencies. I never drilled any deeper. You may look them up with Synaptics if you like.
To the conf file: the default is that user names are hidden. You need to enable that line and set it to false.
BTW: the conf file is confusing. In the beginning there is a lot of comments to all the settings. The relevant line is some way down the file under the [seats] section.
#215 Re: Hardware & System Configuration » Instructions for installing lightdm on new Devuan 5 installation? » 2024-12-29 09:42:10
I am a long term user of Lightdm on amd64, but I see no reason why it shouldn't work on i386.
Simple instructions:
# apt install lightdm
# nano /etc/lightdm/lightdm.confEdit under Seats, remove the hash before greeter_hide_users
#216 Re: Hardware & System Configuration » [SOLVED] I can't install hplip on Excalibur » 2024-12-22 07:00:20
I recommend strongly to put a hash # before the ceres line.
#217 Re: Installation » [SOLVED] Help needed to install Devuan Beowulf on Asus Mini-PC » 2024-12-22 06:58:14
I would say: wrong approach.
1.) Do not use Beowulf, use Daedalus. Beowulf is too old for that hardware and no more maintained.
2.) Do not try i386, use amd64. i386 on a modern UEFI PC may not boot at all.
Forget about this FAT32 formatting of the USB stick, this is nonsense. What you show is basically correct, unfortunately just the i386 version. The iso is loaded onto the bare stick.
Get a Daedalus netinstall amd64 and write it to the stick the same way as the Beowulf version. When you boot from the stick use that entry in the boot menu that has the (U)EFI-Prefix.
Good luck
#218 Re: Hardware & System Configuration » [SOLVED] I can't install hplip on Excalibur » 2024-12-21 15:50:03
For completeness you should add non-free-firmware to your sources.list.
Using Ceres: it may work, it also can brick your system.
Procedure:
Add this line to your sources.list
deb http://deb.devuan.org/merged/ ceres main contrib non-free non-free-firmwareRun the following commands
# apt update
# apt -t ceres install hplipThen comment out Ceres in your sources.list and run another apt update.
No warrenty.
#219 Re: Hardware & System Configuration » [SOLVED] I can't install hplip on Excalibur » 2024-12-21 14:15:54
Wait until it comes back.
#220 Re: Installation » [SOLVED] Always the latest kernel » 2024-12-11 20:45:27
This question was raised before and answered:
The meta-package takes care for upgrading the kernel. No matter if you run the stock kernels, or the backports kernels.
Its a matter of which meta-package you have installed: the stock version (which you have) or the backports version (apt -t daedalus-backports install linux-image-amd64). You have to make up your mind which kernel series you would like to have updated.
#221 Re: Installation » Remote directory for updates deb.devuan.org not work !!! » 2024-12-10 22:18:41
Wait a moment, you used deb.devuan.com. Thats not correct. Please use deb.devuan.org to ping.
On the other hand: this is my result:
~$ ping -c 1 deb.devuan.org
PING deb.rr.devuan.org (131.188.12.211) 56(84) bytes of data.
64 bytes from ftp.rrze.uni-erlangen.de (131.188.12.211): icmp_seq=1 ttl=52 time=32.9 ms
--- deb.rr.devuan.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 32.882/32.882/32.882/0.000 ms
~$ ping -c 1 deb.devuan.com
PING deb.devuan.com (199.59.243.227) 56(84) bytes of data.
64 bytes from 199.59.243.227 (199.59.243.227): icmp_seq=1 ttl=248 time=14.8 ms
--- deb.devuan.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 14.752/14.752/14.752/0.000 msNo loss on both.
You should blame it to your internet provider. They are filtering/blocking stuff they do not understand. Talk to them why you can't get even a ping to a software site.
#222 Re: Installation » Remote directory for updates deb.devuan.org not work !!! » 2024-12-10 16:53:24
So close by ...
Have you tried the other three mirrors on the list?
#223 Re: Installation » Remote directory for updates deb.devuan.org not work !!! » 2024-12-10 12:41:31
Welcome Phil.
I think you are slightly off track, the server called deb.devuan.org just works fine. Just did an apt update on my Daedalus, it worked here in Germany via the Telekom network. I can also switch to the devuan.org web page via the link on the right hand corner at the top of this page.
There were various events like this in the past, typically apt update not working against deb.devuan.org. You may search this forum for posts about this issue.
None of them was a server failure. It always boiled down to DNS issues. Various approaches are possible: use another DNS, look for a close by suitable mirror via this page https://www.devuan.org/get-devuan, talk to your network provider ...
Good luck
#224 Re: Installation » Has anyone got Devuan to run on HP + Intel RST? » 2024-12-10 08:59:05
No matter what I do though, I can’t get the RST option to light up; it’s hard disabled in firmware even though it’s there.
Maybe you need to set a supervisor password in the Bios?
#225 Re: Hardware & System Configuration » Swapon bash:command not found ? » 2024-12-03 22:00:49
You should have been trapped in any release including Beowulf and later. The only way around is a dedicated root terminal.
The problem itself is inherited from Debian. In Buster there was a move of the su command from one package to another (I don't know exactly the names, can be found in the internet). They told me now the su command behaves as in any other Unix/Linux. Not that I like it, I see that very often the "normal" user stumbles across this behaviour. Not really user friendly. Not a bug, works as intended by the people knowing better.
Board footer
