What is the meaning of these error messages in the system log, when I plug in [a 2.5" spinning-disk SATA drive](https://www.seagate.com/files/staticfiles/support/docs/samsung-ds/100698122c.pdf) that I _know_ works, using a [USB-to-SATA adapter](https://web.archive.org/web/20230401071626/https://sabrent.com/products/ec-ss31) ? Jun 25 16:08:07 hostname kernel: [181603.928983] scsi 6:0:0:0: Direct-Access SABRENT 2210 PQ: 0 ANSI: 6 Jun 25 16:08:07 hostname kernel: [181603.931640] sd 6:0:0:0: Attached scsi generic sg1 type 0 Jun 25 16:08:07 hostname kernel: [181603.938380] sd 6:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK Jun 25 16:08:07 hostname kernel: [181603.938391] sd 6:0:0:0: [sdb] Sense Key : Illegal Request [current] Jun 25 16:08:07 hostname kernel: [181603.938398] sd 6:0:0:0: [sdb] Add. Sense: Invalid command operation code Jun 25 16:08:07 hostname kernel: [181603.939443] sd 6:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B) Jun 25 16:08:07 hostname kernel: [181603.939449] sd 6:0:0:0: [sdb] 0-byte physical blocks Jun 25 16:08:07 hostname kernel: [181603.942357] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled Jun 25 16:08:07 hostname kernel: [181603.943386] sd 6:0:0:0: [sdb] Asking for cache data failed Jun 25 16:08:07 hostname kernel: [181603.943393] sd 6:0:0:0: [sdb] Assuming drive cache: write through Jun 25 16:08:07 hostname kernel: [181603.944506] sd 6:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes) Jun 25 16:08:07 hostname kernel: [181603.948248] sd 6:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK Jun 25 16:08:07 hostname kernel: [181603.948255] sd 6:0:0:0: [sdb] Sense Key : Illegal Request [current] Jun 25 16:08:07 hostname kernel: [181603.948257] sd 6:0:0:0: [sdb] Add. Sense: Invalid command operation code Jun 25 16:08:07 hostname kernel: [181603.960998] sd 6:0:0:0: [sdb] Attached SCSI disk Specifically: […] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK […] Sense Key : Illegal Request [current] […] Add. Sense: Invalid command operation code The device spins up fine mechanically with no unusual noises, but none of the partitions are being detected, and as a result, they don't show up in the file manager. I don't think this matters much, but just to provide some context, it's an Ubuntu 20.04-based distribution (elementary OS 6.1 Jólnir) running on a Samsung Series 9.

I got an IBM x3850 type 8864 machine, I can successfully boot using a 2.6.32 kernel but when I try to use a 3.10 kernel or newer the kernel fails to initialize all PCI slots (I can fix this (manually), see below): pci 0000:19:00.0: BAR 14: can't assign mem (size 0x1a00000) pci 0000:19:00.0: BAR 13: can't assign io (size 0x3000) pci 0000:19:00.0: BAR 14: can't assign mem (size 0x1600000) pci 0000:19:00.0: BAR 13: can't assign io (size 0x3000) pci 0000:1a:00.0: BAR 14: can't assign mem (size 0x1600000) pci 0000:1a:00.0: BAR 13: assigned [io 0x7000-0x8fff] pci 0000:1b:02.0: BAR 14: can't assign mem (size 0xa00000) pci 0000:1b:04.0: BAR 14: can't assign mem (size 0xa00000) pci 0000:1b:02.0: BAR 13: assigned [io 0x7000-0x7fff] pci 0000:1b:04.0: BAR 13: assigned [io 0x8000-0x8fff] ... Which causes that my network card is not successfully loaded as the PCI bus is obviously not correctly instantiated. lspci yields the following: 00:00.0 Host bridge: IBM Calgary PCI-X Host Bridge (rev 04) 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV100 [Radeon 7000 / Radeon VE] 00:03.0 USB controller: NEC Corporation OHCI USB Controller (rev 43) 00:03.1 USB controller: NEC Corporation OHCI USB Controller (rev 43) 00:03.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 04) 00:0f.0 Host bridge: Broadcom CSB6 South Bridge (rev a0) 00:0f.1 IDE interface: Broadcom CSB6 RAID/IDE Controller (rev a0) 00:0f.3 ISA bridge: Broadcom GCLE-2 Host Bridge 01:00.0 Host bridge: IBM Calgary PCI-X Host Bridge (rev 04) 01:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 10) 01:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 10) 01:02.0 RAID bus controller: Adaptec AAC-RAID (rev 02) 02:00.0 Host bridge: IBM Calgary PCI-X Host Bridge (rev 04) 06:00.0 Host bridge: IBM Calgary PCI-X Host Bridge (rev 04) 0a:00.0 PCI bridge: IBM CalIOC2 PCI-E Root Port (rev 01) 0f:00.0 PCI bridge: IBM CalIOC2 PCI-E Root Port (rev 01) 14:00.0 PCI bridge: IBM CalIOC2 PCI-E Root Port (rev 01) 19:00.0 PCI bridge: IBM CalIOC2 PCI-E Root Port (rev 01) 1a:00.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES12N3A PCI Express Switch (rev 0c) 1b:02.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES12N3A PCI Express Switch (rev 0c) 1b:04.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES12N3A PCI Express Switch (rev 0c) 1c:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 1c:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 1d:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 1d:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) # FIX # I can actually fix it by removing the root PCI bus 19:00.0 PCI bridge: IBM CalIOC2 PCI-E Root Port (rev 01) via echo 1 > /sys/bus/pci/devices/0000\:19\:00.0/remove and a rescan afterwards: echo 1 > /sys/bus/pci/rescan which causes the following output: pci _bus 0000:1c: busn_res: [bus 1c] is released pci _bus 0000:1d: busn_res: [bus 1d] is released pci _bus 0000:1b: busn_res: [bus 1b-1d] is released pci _bus 0000:1a: busn_res: [bus 1a-1d] is released pci 0000:19:00.0: [1014:0308] type 01 class 0x060401 pci 0000:19:00.0: supports D1 D2 pci 0000:19:00.0: PME# supported from D0 D1 D2 D3hot D3cold pci 0000:1a:00.0: [111d:8018] type 01 class 0x060400 pci 0000:1a:00.0: PME# supported from D0 D3hot D3cold pci 0000:19:00.0: pci bridge to [bus 1a-1d] (subtractive decode) pci 0000:19:00.0: bridge window [mem 0xea800000-0xea9fffff 64bit pref] pci 0000:19:00.0: bridge window [mem 0xea800000-0xebcfffff] (subtractive decode) pci 0000:19:00.0: bridge window [io 0x7000-0x8fff] (subtractive decode) pci 0000:1b:02.0: [111d:8018] type 01 class 0x060400 pci 0000:1b:02.0: PME# supported from D0 D3hot D3cold pci 0000:1b:04.0: [111d:8018] type 01 class 0x060400 pci 0000:1b:04.0: PME# supported from D0 D3hot D3cold pci 0000:1a:00.0: pci bridge to [bus 1b-1d] pci 0000:1a:00.0: bridge window [io 0x7000-0x8fff] pci 0000:1a:00.0: bridge window [mem 0xea800000-0xea9fffff 64bit pref] .... pci 0000:1b:04.0: bridge window [mem 0xea900000-0xea9fffff 64bit pref] pci 0000:1b:02.0: bridge window [mem 0x00100000-0x001fffff 64bit pref] to [bus 1c] add_size 100000 pci 0000:1b:04.0: bridge window [mem 0x00100000-0x001fffff 64bit pref] to [bus 1d] add_size 100000 pci 0000:1b:02.0: res=[mem 0x00100000-0x001fffff 64bit pref] get_res_add_size add_size 100000 pci 0000:1b:04.0: res=[mem 0x00100000-0x001fffff 64bit pref] get_res_add_size add_size 100000 pci 0000:1a:00.0: bridge window [mem 0x00100000-0x002fffff 64bit pref] to [bus 1b-1d] add_size 200000 pci 0000:19:00.0: bridge window [io 0x1000-0x2fff] to [bus 1a-1d] add_size 1000 pci 0000:1a:00.0: res=[mem 0x00100000-0x002fffff 64bit pref] get_res_add_size add_size 200000 pci 0000:19:00.0: bridge window [mem 0x00100000-0x002fffff 64bit pref] to [bus 1a-1d] add_size 200000 pci 0000:19:00.0: bridge window [mem 0x00200000-0x015fffff] to [bus 1a-1d] add_size 200000 pci 0000:19:00.0: res=[mem 0x00200000-0x015fffff] get_res_add_size add_size 200000 pci 0000:19:00.0: res=[mem 0x00100000-0x002fffff 64bit pref] get_res_add_size add_size 200000 pci 0000:19:00.0: res=[io 0x1000-0x2fff] get_res_add_size add_size 1000 pci 0000:19:00.0: BAR 14: can't assign mem (size 0x1600000) pci 0000:19:00.0: BAR 15: assigned [mem 0xea800000-0xeabfffff 64bit pref] pci 0000:19:00.0: BAR 13: can't assign io (size 0x3000) pci 0000:19:00.0: BAR 14: assigned [mem 0xea800000-0xebbfffff] pci 0000:19:00.0: BAR 15: can't assign mem pref (size 0x200000) pci 0000:19:00.0: BAR 13: assigned [io 0x7000-0x8fff] pci 0000:19:00.0: BAR 14: can't assign mem (size 0x1400000) pci 0000:19:00.0: failed to add 200000 res=[mem 0xea800000-0xebbfffff] pci 0000:19:00.0: BAR 13: can't assign io (size 0x2000) pci 0000:19:00.0: failed to add 1000 res=[io 0x7000-0x8fff] pci 0000:1a:00.0: res=[mem 0x00100000-0x002fffff 64bit pref] get_res_add_size add_size 200000 pci 0000:1a:00.0: BAR 14: assigned [mem 0xea800000-0xebbfffff] pci 0000:1a:00.0: BAR 15: can't assign mem pref (size 0x400000) pci 0000:1a:00.0: BAR 13: assigned [io 0x7000-0x8fff] pci 0000:1a:00.0: BAR 14: assigned [mem 0xea800000-0xebbfffff] pci 0000:1a:00.0: BAR 15: can't assign mem pref (size 0x200000) pci 0000:1b:02.0: res=[mem 0x00100000-0x001fffff 64bit pref] get_res_add_size add_size 100000 pci 0000:1b:04.0: res=[mem 0x00100000-0x001fffff 64bit pref] get_res_add_size add_size 100000 pci 0000:1b:02.0: BAR 14: assigned [mem 0xea800000-0xeb1fffff] pci 0000:1b:04.0: BAR 14: assigned [mem 0xeb200000-0xebbfffff] pci 0000:1b:02.0: BAR 15: can't assign mem pref (size 0x200000) pci 0000:1b:04.0: BAR 15: can't assign mem pref (size 0x200000) pci 0000:1b:02.0: BAR 13: assigned [io 0x7000-0x7fff] pci 0000:1b:04.0: BAR 13: assigned [io 0x8000-0x8fff] pci 0000:1b:02.0: BAR 14: assigned [mem 0xea800000-0xeb1fffff] pci 0000:1b:04.0: BAR 14: assigned [mem 0xeb200000-0xebbfffff] pci 0000:1b:02.0: BAR 15: can't assign mem pref (size 0x100000) pci 0000:1b:04.0: BAR 15: can't assign mem pref (size 0x100000) pci 0000:1c:00.0: reg 184: [mem 0xea800000-0xea803fff 64bit pref] pci 0000:1c:00.0: reg 190: [mem 0xea820000-0xea823fff 64bit pref] pci 0000:1c:00.0: reg 184: [mem 0xea800000-0xea803fff 64bit pref] pci 0000:1c:00.0: reg 184: [mem 0xea800000-0xea803fff 64bit pref] pci 0000:1c:00.0: reg 190: [mem 0xea820000-0xea823fff 64bit pref] pci 0000:1c:00.0: reg 184: [mem 0xea800000-0xea803fff 64bit pref] pci 0000:1c:00.0: reg 190: [mem 0xea820000-0xea823fff 64bit pref] pci 0000:1c:00.1: reg 184: [mem 0xea840000-0xea843fff 64bit pref] pci 0000:1c:00.0: reg 184: [mem 0xea800000-0xea803fff 64bit pref] pci 0000:1c:00.0: reg 190: [mem 0xea820000-0xea823fff 64bit pref] pci 0000:1c:00.1: reg 190: [mem 0xea860000-0xea863fff 64bit pref] pci 0000:1c:00.0: reg 184: [mem 0xea800000-0xea803fff 64bit pref] pci 0000:1c:00.0: reg 190: [mem 0xea820000-0xea823fff 64bit pref] pci 0000:1c:00.1: reg 184: [mem 0xea840000-0xea843fff 64bit pref] pci 0000:1c:00.0: res=[mem 0xea800000-0xea7fffff 64bit pref] get_res_add_size add_size 20000 pci 0000:1c:00.0: res=[mem 0xea820000-0xea81ffff 64bit pref] get_res_add_size add_size 20000 pci 0000:1c:00.1: res=[mem 0xea840000-0xea83ffff 64bit pref] get_res_add_size add_size 20000 pci 0000:1c:00.1: res=[mem 0xea860000-0xea85ffff 64bit pref] get_res_add_size add_size 20000 pci 0000:1c:00.0: BAR 1: assigned [mem 0xea800000-0xeabfffff] pci 0000:1c:00.1: BAR 1: assigned [mem 0xeac00000-0xeaffffff] pci 0000:1c:00.0: BAR 0: assigned [mem 0xeb000000-0xeb01ffff] pci 0000:1c:00.1: BAR 0: assigned [mem 0xeb020000-0xeb03ffff] pci 0000:1c:00.0: BAR 3: assigned [mem 0xeb040000-0xeb043fff] pci 0000:1c:00.0: reg 184: [mem 0xea800000-0xea803fff 64bit pref] pci 0000:1c:00.0: BAR 7: assigned [mem 0xeb044000-0xeb063fff 64bit pref] pci 0000:1c:00.0: reg 190: [mem 0xea820000-0xea823fff 64bit pref] pci 0000:1c:00.0: BAR 10: assigned [mem 0xeb064000-0xeb083fff 64bit pref] pci 0000:1c:00.1: BAR 3: assigned [mem 0xeb084000-0xeb087fff] pci 0000:1c:00.1: reg 184: [mem 0xea840000-0xea843fff 64bit pref] pci 0000:1c:00.1: BAR 7: assigned [mem 0xeb088000-0xeb0a7fff 64bit pref] pci 0000:1c:00.1: reg 190: [mem 0xea860000-0xea863fff 64bit pref] pci 0000:1c:00.1: BAR 10: assigned [mem 0xeb0a8000-0xeb0c7fff 64bit pref] pci 0000:1c:00.0: BAR 2: assigned [io 0x7000-0x701f] pci 0000:1c:00.1: BAR 2: assigned [io 0x7020-0x703f] pci 0000:1b:02.0: pci bridge to [bus 1c] pci 0000:1b:02.0: bridge window [io 0x7000-0x7fff] pci 0000:1b:02.0: bridge window [mem 0xea800000-0xeb1fffff] pci 0000:1d:00.0: reg 184: [mem 0xea900000-0xea903fff 64bit pref] pci 0000:1d:00.0: reg 190: [mem 0xea920000-0xea923fff 64bit pref] pci 0000:1d:00.0: reg 184: [mem 0xea900000-0xea903fff 64bit pref] pci 0000:1d:00.0: reg 184: [mem 0xea900000-0xea903fff 64bit pref] pci 0000:1d:00.0: reg 190: [mem 0xea920000-0xea923fff 64bit pref] pci 0000:1d:00.0: reg 184: [mem 0xea900000-0xea903fff 64bit pref] pci 0000:1d:00.0: reg 190: [mem 0xea920000-0xea923fff 64bit pref] pci 0000:1d:00.1: reg 184: [mem 0xea940000-0xea943fff 64bit pref] pci 0000:1d:00.0: reg 184: [mem 0xea900000-0xea903fff 64bit pref] pci 0000:1d:00.0: reg 190: [mem 0xea920000-0xea923fff 64bit pref] pci 0000:1d:00.1: reg 190: [mem 0xea960000-0xea963fff 64bit pref] pci 0000:1d:00.0: reg 184: [mem 0xea900000-0xea903fff 64bit pref] pci 0000:1d:00.0: reg 190: [mem 0xea920000-0xea923fff 64bit pref] pci 0000:1d:00.1: reg 184: [mem 0xea940000-0xea943fff 64bit pref] pci 0000:1d:00.0: res=[mem 0xea900000-0xea8fffff 64bit pref] get_res_add_size add_size 20000 pci 0000:1d:00.0: res=[mem 0xea920000-0xea91ffff 64bit pref] get_res_add_size add_size 20000 pci 0000:1d:00.1: res=[mem 0xea940000-0xea93ffff 64bit pref] get_res_add_size add_size 20000 pci 0000:1d:00.1: res=[mem 0xea960000-0xea95ffff 64bit pref] get_res_add_size add_size 20000 pci 0000:1d:00.0: BAR 1: assigned [mem 0xeb400000-0xeb7fffff] pci 0000:1d:00.1: BAR 1: assigned [mem 0xeb800000-0xebbfffff] pci 0000:1d:00.0: BAR 0: assigned [mem 0xeb200000-0xeb21ffff] pci 0000:1d:00.1: BAR 0: assigned [mem 0xeb220000-0xeb23ffff] pci 0000:1d:00.0: BAR 3: assigned [mem 0xeb240000-0xeb243fff] pci 0000:1d:00.0: reg 184: [mem 0xea900000-0xea903fff 64bit pref] pci 0000:1d:00.0: BAR 7: assigned [mem 0xeb244000-0xeb263fff 64bit pref] pci 0000:1d:00.0: reg 190: [mem 0xea920000-0xea923fff 64bit pref] pci 0000:1d:00.0: BAR 10: assigned [mem 0xeb264000-0xeb283fff 64bit pref] pci 0000:1d:00.1: BAR 3: assigned [mem 0xeb284000-0xeb287fff] pci 0000:1d:00.1: reg 184: [mem 0xea940000-0xea943fff 64bit pref] pci 0000:1d:00.1: BAR 7: assigned [mem 0xeb288000-0xeb2a7fff 64bit pref] pci 0000:1d:00.1: reg 190: [mem 0xea960000-0xea963fff 64bit pref] pci 0000:1d:00.1: BAR 10: assigned [mem 0xeb2a8000-0xeb2c7fff 64bit pref] pci 0000:1d:00.0: BAR 2: assigned [io 0x8000-0x801f] pci 0000:1d:00.1: BAR 2: assigned [io 0x8020-0x803f] pci 0000:1b:04.0: pci bridge to [bus 1d] pci 0000:1b:04.0: bridge window [io 0x8000-0x8fff] pci 0000:1b:04.0: bridge window [mem 0xeb200000-0xebbfffff] pci 0000:1a:00.0: pci bridge to [bus 1b-1d] pci 0000:1a:00.0: bridge window [io 0x7000-0x8fff] pci 0000:1a:00.0: bridge window [mem 0xea800000-0xebbfffff] pci 0000:19:00.0: pci bridge to [bus 1a-1d] pci 0000:19:00.0: bridge window [io 0x7000-0x8fff] pci 0000:19:00.0: bridge window [mem 0xea800000-0xebbfffff] # QUESTION # Is it somehow possible to tell the kernel (e.g. via a parameter) to automatically do this? What is causing this issue in the first place? Thank you in advance! ## Update ## As the described fix fails on a 4.x system (actually starting with 3.12 I suppose), I had a look at the kernel and found that if I disable PCI ASPM (which was already disabled by ACPI (t can also be forced by pcie_aspm=off in kernel boot parameter)), the following small fix (on a 4.4.0) resolves a kernel null pointer dereference: --- a/drivers/pci/pcie/aspm.c +++ b/drivers/pci/pcie/aspm.c @@ -552,11 +552,12 @@ static struct pcie_link_state *alloc_pcie_link_state(struct pci_dev *pdev) void pcie_aspm_init_link_state(struct pci_dev *pdev) { struct pcie_link_state *link; - int blacklist = !!pcie_aspm_sanity_check(pdev); - + int blacklist; if (!aspm_support_enabled) return; + blacklist = !!pcie_aspm_sanity_check(pdev); + if (pdev->link_state) return; Kind of odd that a sanity check is performed if the feature itself is deactivated, the actual null pointer dereference happend in pcie_aspm_sanity_check in this line list_for_each_entry(child, &pdev->subordinate->devices, bus_list) {. Is this a kernel bug?

I'm running a fully up-to-date Fedora on a Macbook Pro. To get WiFi working in the first place, I installed akmods-wl as recommended. The WiFi works, but the connection keeps dropping. I've noticed this is especially true when there are several devices on my WiFi (when I'm the only person in the house it's usually OK although it still drops on occasion, when roommates come in with their laptops + their phones, the drop rate increases). When connection drops it's usually down for 30 seconds-1 minute before reconnecting. In worst cases this happens every couple of minutes. I have another laptop running Fedora and the WiFi is fine on there, even when there are many devices in the network. My wireless card is Broadcom BCM4331: $ lspci | grep Broadcom 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) 01:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card Reader (rev 10) 02:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) iwconfig on my wireless interface: $ iwconfig wlp2s0 wlp2s0 IEEE 802.11abg ESSID:"WINDRUSH" Mode:Managed Frequency:2.412 GHz Access Point: 44:E9:DD:0E:7F:00 Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off dmesg shows lots of these two errors: ... [11387.414926] ERROR @wl_cfg80211_get_tx_power : error (-1) [11507.449435] ERROR @wl_dev_intvar_get : error (-1) [11507.449440] ERROR @wl_cfg80211_get_tx_power : error (-1) [11627.486001] ERROR @wl_dev_intvar_get : error (-1) [11627.486008] ERROR @wl_cfg80211_get_tx_power : error (-1) [11631.113431] ERROR @wl_dev_intvar_get : error (-1) ... Couldn't find any solutions for Fedora regarding this issue. Found some from Arch Wiki and Ubuntu but they didn't work and were also dealing with different versions of the Broadcom wireless card. *(Even if no one has any clear tips for me, can someone explain what those two errors in dmesg mean?)*

I'm using transmission-gtk 4.1.0-beta.2 on Devuan GNU/Linux Excalibur. My dmesg log is spammed with the following kind of message:

[Jul 4 14:47] audit: type=1400 audit(1751629628.491:75895): apparmor="ALLOWED" operation="open"
class="file" profile="transmission-gtk" name="/proc/sys/net/ipv6/conf/all/disable_ipv6"
pid=20126 comm="transmission-gt" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

` (originally all in one line, I broke it here for readability.) My network connection does have an IPv6 address (along with IPv4), even though I'm not intentionally making use of it. Anyway, I would like to have transmission-gtk stop trying to mess with it. Is that possible? If not, can I at least silence the repeating log message? Or get to only show up just once? --- FYI, on my system, I have:

# ls -la /proc/sys/net/ipv6/conf/all/disable_ipv6 
-rw-r--r-- 1 root root 0 Jul  4 13:59 /proc/sys/net/ipv6/conf/all/disable_ipv6

I installed Debian 12 without GUI, on a computer using console port. This computer is also with a VGA port. After installation, It can output everything on console emulator, Tera Term, but on VGA during booting it is a black screen with a cursor after GRUB menu and before login prompt. I did remove "**quiet**" in **GRUB_CMDLINE_LINUX**. Simply put, I can see all outputs on console emulator, but black screen with a cursor on VGA after GRUB menu and before login prompt. For example on console emulator, I can see messages like these, but nothing on VGA. On VGA, it's only black screen with a cursor until login prompt shows. [ 0.000000] microcode: microcode updated early to revision 0x3e, date = 2023-10-05 [ 0.000000] Linux version 6.1.0-34-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.135-1 (2025-04-25) [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-6.1.0-34-amd64 root=/dev/mapper/Deb160--vg-root ro ipv6.disable=1 console=ttyS0,115200n8 ipv6.disable=1 nomodeset [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable [ 0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003e2dffff] usable I searched the internet and added nomodeset, GRUB_GFXPAYLOAD_LINUX, and GRUB_GFXMODE in /etc/default/grub and did update-grub. However, it didn't work. Here is the /etc/default/grub： GRUB_DEFAULT="1>4" GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=lsb_release -i -s 2> /dev/null || echo Debian GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 nomodeset" GRUB_CMDLINE_LINUX="ipv6.disable=1 console=ttyS0,115200n8" GRUB_GFXPAYLOAD_LINUX=keep GRUB_GFXMODE=1920x1080@60 GRUB_TERMINAL=console GRUB_SERIAL_COMMAND="serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1" GRUB_DISABLE_OS_PROBER=false This is the /boot/grub/grub.cfg： # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then set have_grubenv=true load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="1>4" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } terminal_input console terminal_output console if [ "${recordfail}" = 1 ] ; then set timeout=30 else if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=5 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=5 fi fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/05_debian_theme ### set menu_color_normal=cyan/blue set menu_color_highlight=white/blue ### END /etc/grub.d/05_debian_theme ### ### BEGIN /etc/grub.d/10_linux ### function gfxmode { set gfxpayload="${1}" } set linux_gfx_mode=keep export linux_gfx_mode menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-46 7-79250697ca96' { load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 9ba31 cdfb2f651f0 else search --no-floppy --fs-uuid --set=root 9ba31d3b-9da0-46b8-b3e2-5cdfb2f651f0 fi echo 'Loading Linux 6.6.69 ...' linux /vmlinuz-6.6.69 root=/dev/mapper/Deb160--vg-root ro ipv6.disable=1 console=ttyS0,115200n8 ipv6.disable=1 nomo echo 'Loading initial ramdisk ...' initrd /initrd.img-6.6.69 } submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-46c62618-08ec-4836-a087-79250697ca96' menuentry 'Debian GNU/Linux, with Linux 6.6.69' --class debian --class gnu-linux --class gnu --class os $menuentry_id 6.69-advanced-46c62618-08ec-4836-a087-79250697ca96' { load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt 8-b3e2-5cdfb2f651f0 else search --no-floppy --fs-uuid --set=root 9ba31d3b-9da0-46b8-b3e2-5cdfb2f651f0 fi echo 'Loading Linux 6.6.69 ...' linux /vmlinuz-6.6.69 root=/dev/mapper/Deb160--vg-root ro ipv6.disable=1 console=ttyS0,115200n8 ipv6.disabl echo 'Loading initial ramdisk ...' initrd /initrd.img-6.6.69 } menuentry 'Debian GNU/Linux, with Linux 6.6.69 (recovery mode)' --class debian --class gnu-linux --class gnu --class ion 'gnulinux-6.6.69-recovery-46c62618-08ec-4836-a087-79250697ca96' { load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt 8-b3e2-5cdfb2f651f0 else search --no-floppy --fs-uuid --set=root 9ba31d3b-9da0-46b8-b3e2-5cdfb2f651f0 fi echo 'Loading Linux 6.6.69 ...' linux /vmlinuz-6.6.69 root=/dev/mapper/Deb160--vg-root ro single ipv6.disable=1 console=ttyS0,115200n8 echo 'Loading initial ramdisk ...' initrd /initrd.img-6.6.69 } menuentry 'Debian GNU/Linux, with Linux 6.6.69.old' --class debian --class gnu-linux --class gnu --class os $menuentr x-6.6.69.old-advanced-46c62618-08ec-4836-a087-79250697ca96' { load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt 8-b3e2-5cdfb2f651f0 else search --no-floppy --fs-uuid --set=root 9ba31d3b-9da0-46b8-b3e2-5cdfb2f651f0 fi echo 'Loading Linux 6.6.69.old ...' linux /vmlinuz-6.6.69.old root=/dev/mapper/Deb160--vg-root ro ipv6.disable=1 console=ttyS0,115200n8 ipv6.di echo 'Loading initial ramdisk ...' initrd /initrd.img-6.6.69 } menuentry 'Debian GNU/Linux, with Linux 6.6.69.old (recovery mode)' --class debian --class gnu-linux --class gnu --cl _option 'gnulinux-6.6.69.old-recovery-46c62618-08ec-4836-a087-79250697ca96' { load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt 8-b3e2-5cdfb2f651f0 else search --no-floppy --fs-uuid --set=root 9ba31d3b-9da0-46b8-b3e2-5cdfb2f651f0 fi echo 'Loading Linux 6.6.69.old ...' linux /vmlinuz-6.6.69.old root=/dev/mapper/Deb160--vg-root ro single ipv6.disable=1 console=ttyS0,115200n8 echo 'Loading initial ramdisk ...' initrd /initrd.img-6.6.69 } menuentry 'Debian GNU/Linux, with Linux 6.1.0-34-amd64' --class debian --class gnu-linux --class gnu --class os $menu linux-6.1.0-34-amd64-advanced-46c62618-08ec-4836-a087-79250697ca96' { load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt 8-b3e2-5cdfb2f651f0 else search --no-floppy --fs-uuid --set=root 9ba31d3b-9da0-46b8-b3e2-5cdfb2f651f0 fi echo 'Loading Linux 6.1.0-34-amd64 ...' linux /vmlinuz-6.1.0-34-amd64 root=/dev/mapper/Deb160--vg-root ro ipv6.disable=1 console=ttyS0,115200n8 ipv t echo 'Loading initial ramdisk ...' initrd /initrd.img-6.1.0-34-amd64 } menuentry 'Debian GNU/Linux, with Linux 6.1.0-34-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu y_id_option 'gnulinux-6.1.0-34-amd64-recovery-46c62618-08ec-4836-a087-79250697ca96' { load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt 8-b3e2-5cdfb2f651f0 else search --no-floppy --fs-uuid --set=root 9ba31d3b-9da0-46b8-b3e2-5cdfb2f651f0 fi echo 'Loading Linux 6.1.0-34-amd64 ...' linux /vmlinuz-6.1.0-34-amd64 root=/dev/mapper/Deb160--vg-root ro single ipv6.disable=1 console=ttyS0,11520 echo 'Loading initial ramdisk ...' initrd /initrd.img-6.1.0-34-amd64 } menuentry 'Debian GNU/Linux, with Linux 6.1.0-32-amd64' --class debian --class gnu-linux --class gnu --class os $menu linux-6.1.0-32-amd64-advanced-46c62618-08ec-4836-a087-79250697ca96' { load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt 8-b3e2-5cdfb2f651f0 else search --no-floppy --fs-uuid --set=root 9ba31d3b-9da0-46b8-b3e2-5cdfb2f651f0 fi echo 'Loading Linux 6.1.0-32-amd64 ...' linux /vmlinuz-6.1.0-32-amd64 root=/dev/mapper/Deb160--vg-root ro ipv6.disable=1 console=ttyS0,115200n8 ipv t echo 'Loading initial ramdisk ...' initrd /initrd.img-6.1.0-32-amd64 } menuentry 'Debian GNU/Linux, with Linux 6.1.0-32-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu y_id_option 'gnulinux-6.1.0-32-amd64-recovery-46c62618-08ec-4836-a087-79250697ca96' { load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt 8-b3e2-5cdfb2f651f0 else search --no-floppy --fs-uuid --set=root 9ba31d3b-9da0-46b8-b3e2-5cdfb2f651f0 fi echo 'Loading Linux 6.1.0-32-amd64 ...' linux /vmlinuz-6.1.0-32-amd64 root=/dev/mapper/Deb160--vg-root ro single ipv6.disable=1 console=ttyS0,11520 echo 'Loading initial ramdisk ...' initrd /initrd.img-6.1.0-32-amd64 } menuentry 'Debian GNU/Linux, with Linux 6.1.0-29-amd64' --class debian --class gnu-linux --class gnu --class os $menu linux-6.1.0-29-amd64-advanced-46c62618-08ec-4836-a087-79250697ca96' { load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt 8-b3e2-5cdfb2f651f0 else search --no-floppy --fs-uuid --set=root 9ba31d3b-9da0-46b8-b3e2-5cdfb2f651f0 fi echo 'Loading Linux 6.1.0-29-amd64 ...' linux /vmlinuz-6.1.0-29-amd64 root=/dev/mapper/Deb160--vg-root ro ipv6.disable=1 console=ttyS0,115200n8 ipv t echo 'Loading initial ramdisk ...' initrd /initrd.img-6.1.0-29-amd64 } menuentry 'Debian GNU/Linux, with Linux 6.1.0-29-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu y_id_option 'gnulinux-6.1.0-29-amd64-recovery-46c62618-08ec-4836-a087-79250697ca96' { load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt 8-b3e2-5cdfb2f651f0 else search --no-floppy --fs-uuid --set=root 9ba31d3b-9da0-46b8-b3e2-5cdfb2f651f0 fi echo 'Loading Linux 6.1.0-29-amd64 ...' linux /vmlinuz-6.1.0-29-amd64 root=/dev/mapper/Deb160--vg-root ro single ipv6.disable=1 console=ttyS0,11520 echo 'Loading initial ramdisk ...' initrd /initrd.img-6.1.0-29-amd64 } } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/30_uefi-firmware ### menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' { fwsetup } ### END /etc/grub.d/30_uefi-firmware ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg fi ### END /etc/grub.d/41_custom ### Anyone knows how to fix this? Thank you.

This is for Linux Mint. On my laptop, I have tried many *many* different methods in fixing this problem, the problem impacts my boot speed too as now it takes like 4 minutes to boot. During shutdown, the same error pops up. Hell, even when I go to a different TTY like TTY6 instead of my GUI in TTY7, the same message appears, it's everywhere. Specifically, after I type in dmesg to display messages during startup I get this: :d6:07:41:e8 [ 14.449973] usb 1-4: new full-speed USB device number 13 using xhci_hcd [ 14.450114] usb 1-4: Device not responding to setup address. [ 14.659080] usb 1-4: Device not responding to setup address. [ 14.866957] usb 1-4: device not accepting address 13, error -71 [ 14.867011] usb 1-4: WARN: invalid context state for evaluate context command. [ 15.182924] usb 1-4: new full-speed USB device number 14 using xhci_hcd [ 15.183137] usb 1-4: Device not responding to setup address. [ 15.387200] usb 1-4: Device not responding to setup address. [ 15.594975] usb 1-4: device not accepting address 14, error -71 [ 15.595048] usb 1-4: WARN: invalid context state for evaluate context command. [ 15.595096] usb usb1-port4: attempt power cycle [ 15.974932] usb 1-4: new full-speed USB device number 15 using xhci_hcd [ 16.088968] usb 1-4: device descriptor read/64, error -71 [ 16.309007] usb 1-4: device descriptor read/64, error -71 [ 16.524986] usb 1-4: new full-speed USB device number 16 using xhci_hcd [ 16.638952] usb 1-4: device descriptor read/64, error -71 [ 16.860890] usb 1-4: device descriptor read/64, error -71 [ 16.962940] usb usb1-port4: unable to enumerate USB device I tried a couple of solution (I say most of them are quite old), one was this https://urukrama.wordpress.com/2009/01/27/usb-drive-not-recognised-error-71/ , that I found in this forum , which did nothing since there was no options.conf in my /etc/modprobe.d/ directory, even after making it, nothing happened. Next solution I tried was this forum solution which also did not work. For now i'm just waiting and trying my best to debug this with only like 3 months experience using Linux, got any tips or guides? lsusb Produces this result: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 036: ID 062a:5918 MosArt Semiconductor Corp. 2.4G Keyboard Mouse Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Creating a udev.rules file (so far): Update after I tried setting a udev file: Status of dmesg currently (23/05/2025): [ 6.691017] usb 1-4: device not accepting address 9, error -71 [ 6.691164] usb 1-4: WARN: invalid context state for evaluate context command. [ 7.006924] usb 1-4: new full-speed USB device number 10 using xhci_hcd [ 7.007139] usb 1-4: Device not responding to setup address. [ 7.212243] usb 1-4: Device not responding to setup address. [ 7.419012] usb 1-4: device not accepting address 10, error -71 [ 7.419168] usb 1-4: WARN: invalid context state for evaluate context command. [ 7.419290] usb usb1-port4: attempt power cycle [ 7.687218] systemd[1] : systemd-rfkill.service: Deactivated successfully. [ 7.798993] usb 1-4: new full-speed USB device number 11 using xhci_hcd [ 7.914183] usb 1-4: device descriptor read/64, error -71 [ 8.134176] usb 1-4: device descriptor read/64, error -71 [ 8.358922] usb 1-4: new full-speed USB device number 12 using xhci_hcd [ 8.474175] usb 1-4: device descriptor read/64, error -71 [ 8.694175] usb 1-4: device descriptor read/64, error -71 [ 8.803197] usb usb1-port4: unable to enumerate USB device Some other outputs from dmesg (could be totally unrelated): [ 0.134524] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134535] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 0.134537] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.134540] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134543] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 0.134545] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.134669] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134672] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 0.134673] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.134675] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134678] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 0.134679] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.134682] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134685] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) [ 0.134686] ACPI: Skipping parse of AML opcode: Method (0x0014) [ 0.134688] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326) [ 0.134690] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) BIOS HP Utility Setup:

My dmesg is full of apparmor="ALLOWED" messages. I want to get rid of them, and only be told in the logs about "DENIED" apparmor events. How do I do that... * universally? * for a specific app's profile?

I am compiling my own monolithic kernel for my Lenovo laptop. I am using the CONFIG_EXTRA_FIRMWARE= to specify which firmware files should be build into my kernel staticlly. with my older laptops, it used to be that usually only the wifi driver needed to load external firmware. But now with new laptops, everything needs firmware. When I boot my kernel, even my display does not work. last message I see is loading vmlinuz After that, the display tries to switch to some framebuffer mode, and because there is no firmware driver for my GPU, the display does not work. And because wifi does not work either, I cannot connect vie ssh. Anyways, I have booted Debian Live CD (trixie) which uses same kernel versions that I am compiling (6.12.). I was hoping when the system boots, I will be able to see in dmesg which firmware has been loaded. But that is not the case: it only shows messages which firmware it could not find. So, my question is: **how can I get list of firmware that is being loaded on my Debian laptop? I need exact file name / path**

My dmesg log is littered with the following kind of lines:

[  +0.000009] audit: type=1400 audit(1745688898.020:223710): apparmor="ALLOWED" operation="getattr" class="file" profile="someapp//null-/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop//null-/usr/bin/nemo" name="/usr/local/share/icons/hicolor/" pid=24956 comm="nemo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[  +0.000004] audit: type=1400 audit(1745688898.020:223711): apparmor="ALLOWED" operation="getattr" class="file" profile="someapp//null-/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop//null-/usr/bin/nemo" name="/usr/share/icons/hicolor/" pid=24956 comm="nemo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[  +0.000016] audit: type=1400 audit(1745688898.020:223712): apparmor="ALLOWED" operation="getattr" class="file" profile="someapp//null-/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop//null-/usr/bin/nemo" name="/usr/share/nemo/icons/hicolor/" pid=24956 comm="nemo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[  +0.000004] audit: type=1400 audit(1745688898.020:223713): apparmor="ALLOWED" operation="getattr" class="file" profile="someapp//null-/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop//null-/usr/bin/nemo" name="/home/joeuser/.local/share/icons/" pid=24956 comm="nemo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
[  +0.000003] audit: type=1400 audit(1745688898.020:223714): apparmor="ALLOWED" operation="getattr" class="file" profile="someapp//null-/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop//null-/usr/bin/nemo" name="/home/joeuser/.icons/" pid=24956 comm="nemo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
[  +8.605953] kauditd_printk_skb: 40 callbacks suppressed
[  +0.000002] audit: type=1400 audit(1745688906.628:223755): apparmor="ALLOWED" operation="getattr" class="file" profile="someapp//null-/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop//null-/usr/bin/nemo" name="/home/joeuser/.local/share/mime/mime.cache" pid=24956 comm="nemo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1

Am I correct in assuming that this is nothing to worry about? And if that's the case - how do I suppress these gratuitous messages?

At the moment, I'm mounting a USB hard drive running HFS+ on a Raspberry Pi 3 at boot to be writable. Not 100% sure what I did, but the drive is suddenly throwing up errors such as Buffer I/O error on dev sda2, logical block 18266273, async page read while I'm trying to stream via Plex. Following up on the suggestion from dmesg I installed and ran fsck.hfsplus, but fsck is simply returning The volume Tom's Disk appears to be OK. every time. I've also run it through First Aid on Disk Utility on my Mac, and got similar results. I'm kind of at a loss because the drive seems to be fine, but I can't stop Filesystem was not cleanly unmounted, running fsck.hfsplus is recommended. mounting read-only. messages. Is there any way of telling Ubuntu that the drive is fine? Seems to be the only reason why Plex won't play my media right now...

I am looking for an approach to overcoming an error with some wireless modules on USB in Linux. I have three USB2 WiFi modules on a USB3 hub. I only care about using these modules in Monitor mode. If I only have one or two modules plugged in, everything looks ok. With the third module plugged in, I get dmesg logs: [63460.856556] usb 1-3.3.2: Not enough bandwidth for new device state. [63460.856574] usb 1-3.3.2: can't set config #1, error -28 As a result of this, the driver does not get loaded and I only end up with two wireless interfaces instead of three. After some research, I think I understand why this might be the case. Looking at the USB descriptors for each WiFi module, amongst other smaller bandwidth endpoints there are two high bandwidth endpoints like this: Endpoint Descriptor: 646- bLength 7 647- bDescriptorType 5 648- bEndpointAddress 0x01 EP 1 OUT 649- bmAttributes 3 650: Transfer Type Interrupt 651- Synch Type None 652- Usage Type Data 653- wMaxPacketSize 0x0400 1x 1024 bytes 654- bInterval 1 655- Endpoint Descriptor: 656- bLength 7 657- bDescriptorType 5 658- bEndpointAddress 0x81 EP 1 IN 659- bmAttributes 3 660: Transfer Type Interrupt 661- Synch Type None 662- Usage Type Data 663- wMaxPacketSize 0x0400 1x 1024 bytes 664- bInterval 1 If I'm doing my math correctly, each of those endpoints is effectively asking for 65 Mbps of bandwidth. Since there are two of these endpoints per WiFi module, then each is asking for 130 Mbps of bandwidth total. My guess here, based on the endpoint descriptions (EP 1 IN and EP 1 OUT) is that one is for transmit direction and one is for receive direction. I believe Linux and/or the host controller itself enforces a limit of 80% of the 480 Mbps available, or 384 Mbps. I suspect this is why two modules are happy (260 Mbps 384 Mbps). Since I only care to use these in Monitor mode and don't really need much/any transmit bandwidth, I am wondering if I could somehow manipulate things to my advantage. Possibly some udev rules that change these descriptors or something? Would those kick in before the bandwidth limits are evaluated? Or would I need to actually get down into the firmware/drivers for these modules to have a chance of changing these descriptors before the bandwidth limits are imposed?

I have a question regarding the ports in Linux. If I connect my device via USB and want to check its port I can't do it using the command lsusb, which only specifies bus number and device number on this bus: [ziga@Ziga-PC ~]$ lsusb Bus 003 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC **Is there a command that tells me the port the device is connected to directly?** Only way to do this until now was to disconect and reconnect and using the command: [ziga@Ziga-PC ~]$ dmesg | grep tty [ 0.000000] console [tty0] enabled [ 0.929510] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 4.378109] systemd: Starting system-getty.slice. [ 4.378543] systemd: Created slice system-getty.slice. [ 8.786474] usb 3-4.4: FTDI USB Serial Device converter now attached to ttyUSB0 In the last line it can be seen that my device is connected to **/dev/ttyUSB0**.

This question is a follow-up to [this answer](https://unix.stackexchange.com/a/671093/286615) . In general, my objective is to learn if my system (Debian/Raspberry Pi 5 'bookworm') is updating my RTC/hardware clock from the system time. Please note that the RPi 5 (unlike its Pi ancestors) does have an *in-built* RTC/hardware clock. Here's what I've been able to determine so far: ##### 1. I feel I've established that the system clock is being updated from the hwclock:

$ dmesg | grep "system clock" 

[    1.588793] rpi-rtc soc:rpi_rtc: setting system clock to 2025-02-18T04:59:13 UTC (1739854753)

After some searching in dmesg however, I can find no indication that the hwclock is being updated from system time. However, I **did** find a reference to a fake-hardware clock (which seems *odd*). :

[    4.037230] systemd: Starting fake-hwclock.service - Restore / save the current clock...

##### 2. The kernel is apparently configured to do clock updates in "both directions":

$ cat /boot/config-$(uname -r) | grep -i HCTOSYS
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"  

$ cat /boot/config-$(uname -r) | grep -i SYSTOHC
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_SYSTOHC_DEVICE="rtc0"

It's occurred to me that the kernel ***may be*** performing the SYSTOHC sync only during shutdown, and maybe not being captured by dmesg... but that's a WAG. **Can someone explain how to confirm that the kernel is (or is not) updating the hwclock/RTC?**

**Dear friends and college** we have VM machines with rhel 7.2 version - 3.10.0-327.el7.x86_64 we noticed about the following messages ( from /var/log/messages ) e1000 0000:02:01.0 eth0: Detected Tx Unit Hang#012 Tx Queue #012 TDH #012 TDT and from dmesg we get that [21519947.519425] e1000 0000:02:01.0 eth0: Detected Tx Unit Hang Tx Queue TDH TDT next_to_use next_to_clean buffer_info[next_to_clean] time_stamp next_to_watch jiffies next_to_watch.status [21519949.521583] e1000 0000:02:01.0 eth0: Detected Tx Unit Hang Tx Queue TDH TDT next_to_use next_to_clean buffer_info[next_to_clean] time_stamp next_to_watch jiffies next_to_watch.status [21519949.811366] e1000 0000:02:01.0 eth0: Reset adapter [21519949.855081] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None we try to search the solution for the problem above and we see post about the following fixing set following in /etc/sysctl.conf, and reboot machine

pcie_aspm=offet

( https://serverfault.com/questions/193114/linux-e1000e-intel-networking-driver-problems-galore-where-do-i-start ) or ethtool -K eth0 tso off gso off or changed the network adapters tor VMNETX3. and so on .... so we are confuse about the right solution please advice what is the right approach for our problem ?

After unlocking disk the usual verbiage changed and there was a message about downloading firmware. I want to find out what was going on so I tried dmsg -

% sudo dmsg
[    0.000000] microcode: microcode updated early to revision 0xf8, date = 2023-09-28
[    0.000000] Linux version 6.1.0-30-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.124-1 (2025-01-12)

The microcode message is very vague. Is it unusual? How can I determine what firmware I have, what I should have, and what is available? ------------------ Edit: top of changelog.Debian

intel-microcode (3.20241112.1~deb12u1) bookworm; urgency=medium

  * Build for bookworm
  * All trixie-only changes (from 3.20240813.2) are reverted on this branch

 -- Henrique de Moraes Holschuh   Sat, 07 Dec 2024 14:49:05 -0300

intel-microcode (3.20241112.1) unstable; urgency=medium

  * New upstream microcode datafile 20241112 (closes: #1086483)
    - Mitigations for INTEL-SA-01101 (CVE-2024-21853)
      Improper Finite State Machines (FSMs) in the Hardware logic in some
      4th and 5th Generation Intel Xeon Processors may allow an authorized
      user to potentially enable denial of service via local access.
    - Mitigations for INTEL-SA-01079 (CVE-2024-23918)
      Potential security vulnerabilities in some Intel Xeon processors
      using Intel SGX may allow escalation of privilege.  Intel disclosed
      that some processor models were already fixed by a previous
      microcode update.
    - Updated mitigations for INTEL-SA-01097 (CVE-2024-24968)
      Improper finite state machines (FSMs) in hardware logic in some
      Intel Processors may allow an privileged user to potentially enable a
      denial of service via local access.
    - Mitigations for INTEL-SA-01103 (CVE-2024-23984)
      A potential security vulnerability in the Running Average Power Limit
      (RAPL) interface for some Intel Processors may allow information
      disclosure.  Added mitigations for more processor models.
  * Updated Microcodes:
    sig 0x000806f8, pf_mask 0x87, 2024-06-20, rev 0x2b000603, size 588800
    sig 0x000806f7, pf_mask 0x87, 2024-06-20, rev 0x2b000603
    sig 0x000806f6, pf_mask 0x87, 2024-06-20, rev 0x2b000603
    sig 0x000806f5, pf_mask 0x87, 2024-06-20, rev 0x2b000603
    sig 0x000806f4, pf_mask 0x87, 2024-06-20, rev 0x2b000603
    sig 0x00090672, pf_mask 0x07, 2024-05-29, rev 0x0037, size 224256
    sig 0x00090675, pf_mask 0x07, 2024-05-29, rev 0x0037
    sig 0x000b06f2, pf_mask 0x07, 2024-05-29, rev 0x0037
    sig 0x000b06f5, pf_mask 0x07, 2024-05-29, rev 0x0037
    sig 0x000906a3, pf_mask 0x80, 2024-06-03, rev 0x0435, size 223232
    sig 0x000906a4, pf_mask 0x80, 2024-06-03, rev 0x0435
    sig 0x000a06a4, pf_mask 0xe6, 2024-08-02, rev 0x0020, size 138240
    sig 0x000b06a2, pf_mask 0xe0, 2024-05-29, rev 0x4123, size 220160
    sig 0x000b06a3, pf_mask 0xe0, 2024-05-29, rev 0x4123
    sig 0x000b06a8, pf_mask 0xe0, 2024-05-29, rev 0x4123
    sig 0x000c06f2, pf_mask 0x87, 2024-06-20, rev 0x21000283, size 560128
    sig 0x000c06f1, pf_mask 0x87, 2024-06-20, rev 0x21000283
  * source: update symlinks to reflect id of the latest release, 20241112
  * Update changelog for 3.20240910.1 and 3.20240813.1 with new information:
    INTEL-SA-1103 was addressed by 3.20240813.1 for some processor models,
    and not by 3.20240910. INTEL-SA-1079 was addressed by 3.20240910.1 for
    some processor models.

 -- Henrique de Moraes Holschuh   Thu, 14 Nov 2024 15:37:40 -0300

Does anyone know where the output from dmesg is located? I ask because when I invoke dmesg I have numerous items added to my log that look like tracing information: p2p: selectChannelForRoam ChannelCount 2 init:SelChannel 11 SelRssi -52 SelRefs 1

Any help would be deeeeeeply appreciated. I've dealt with this for 3-4 years now and I'm finally wanting to fix this once and for all. **System info:** - Device: Lenovo Thinkpad E14 Gen 2 - Linux Kernel: 6.13 - Current OS: NixOS - Past OS's used: Ubuntu, Debian, Arch, Kali & openSUSE. - (Windows 10/11 seems to be the only OS that works with my USB ports.) **Issue:** Like the title states, all my USB ports are non-functional across multiple Linux distributions. The issues I've encountered are as follows. 1. No power delivery to devices 2. No device recognition in the system 3. No response when plugging in/unplugging devices (other than a USB or keyboard light turns on for a split second, then off) **System Logs:** Here are some of the outputs I get when I run dmesg & lsusb. (After I've plugged in and unplugged a USB/USB device). lsusb output:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:c123 Realtek Semiconductor Corp. Bluetooth Radio
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

dmesg output:

[ 1724.098991] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
[ 1724.547011] amdgpu 0000:04:00.0: amdgpu: reserve 0x400000 from 0xf41f800000 for PSP TMR
[ 1724.614838] amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
[ 1724.623063] amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode is not available
[ 1724.623065] amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[ 1724.623068] amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
[ 1724.623369] amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
[ 1724.623790] amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
[ 1724.625244] [drm] kiq ring mec 2 pipe 1 q 0
[ 1724.628977] [drm] DMUB hardware initialized: version=0x0101002B
[ 1724.632546] amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[ 1724.632549] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 1724.632550] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 1724.632552] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 1724.632553] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 1724.632554] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 1724.632555] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 1724.632556] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 1724.632557] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 1724.632559] amdgpu 0000:04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[ 1724.632560] amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
[ 1724.632562] amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
[ 1724.632563] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
[ 1724.632564] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
[ 1724.632565] amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
[ 1724.639212] OOM killer enabled.
[ 1724.639214] Restarting tasks ... 
[ 1724.639750] pci_bus 0000:01: Allocating resources
[ 1724.639763] pcieport 0000:00:02.1: bridge window [io  0x1000-0x0fff] to [bus 01] add_size 1000
[ 1724.639772] pcieport 0000:00:02.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 01] add_size 200000 add_align 100000
[ 1724.639784] pci_bus 0000:02: Allocating resources
[ 1724.639790] pcieport 0000:00:02.2: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000 add_align 100000
[ 1724.639800] pci_bus 0000:03: Allocating resources
[ 1724.639818] pcieport 0000:00:02.1: bridge window [mem 0x430200000-0x4303fffff 64bit pref]: assigned
[ 1724.639823] pcieport 0000:00:02.2: bridge window [mem 0x430400000-0x4305fffff 64bit pref]: assigned
[ 1724.639832] pcieport 0000:00:02.1: bridge window [io  0x4000-0x4fff]: assigned
[ 1724.640081] pci_bus 0000:04: Allocating resources
[ 1724.640218] done.
[ 1724.640242] random: crng reseeded on system resumption
[ 1724.642680] PM: suspend exit
[ 1724.645235] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822
[ 1724.646861] Bluetooth: hci0: RTL: rom_version status=0 version=3
[ 1724.646871] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
[ 1724.646960] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin
[ 1724.646985] Bluetooth: hci0: RTL: cfg_sz 6, total sz 37346
[ 1724.692451] Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
[ 1724.844497] r8169 0000:02:00.0 enp2s0: Link is Down
[ 1724.972239] Bluetooth: hci0: RTL: fw version 0xaed66dcb
[ 1725.073443] Bluetooth: MGMT ver 1.23
[ 1729.587480] wlp3s0: authenticate with ac:2a:a1:a5:f4:8c (local address=f8:89:d2:59:ff:83)
[ 1729.647555] wlp3s0: send auth to ac:2a:a1:a5:f4:8c (try 1/3)
[ 1729.650936] wlp3s0: authenticated
[ 1729.651402] wlp3s0: associate with ac:2a:a1:a5:f4:8c (try 1/3)
[ 1729.674019] wlp3s0: RX AssocResp from ac:2a:a1:a5:f4:8c (capab=0x1101 status=0 aid=5)
[ 1729.674466] wlp3s0: associated
[ 1729.744202] wlp3s0: Limiting TX power to 13 dBm as advertised by ac:2a:a1:a5:f4:8c

I'm getting these errors in dmesg (Debian Linux 12): Jan 03 19:02:21 asus kernel: ucsi_acpi USBC000:00: unknown error 0 Jan 03 19:02:21 asus kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5) But this didn't happen before and I didn't change any hardware. I guess it has something to do with USB-C, where I have connected: power to one USB-C, and an external SSD to the other USB-C, which is the same setup I had before. I've searched online but the cases I've seen seem to be from different setups. How could I at least tell which of the two USB-C ports has the problem? (kernel 6.12.7-x64v3-xanmod1) **EDIT:** For some reason, it only happens a few minutes after resuming from hibernation and then it stops

The comand dmesg --level=emerg,alert,crit,err lists all error messages with a high severity. I wondered for monitoring purposes whether the count of messages is somehow exposed in the /proc filesystem. It would be great to give an indication of hardware issues.

I know that dmesg and journalctl record commands logs invoked by my operating-system. From the manpages: > dmesg is used to examine or control the kernel ring buffer. > > The default action is to display all messages from the kernel ring buffer. > journalctl may be used to query the contents of the systemd journal as written by systemd-journald.service > > [...] > > -k, --dmesg Show only kernel messages. **Why do 2 recorders exist**, what types of messages should I expect to see within each of them, and what are the differences in their life cycles?