![]() Something tells me that a race is going on somewhere, maybe because nvidia assumes that the GPU is completely powered off (D3cold) when it’s not actually off, but after some time Linux’s runtime PM powers off the GPU which coincidentally happens before the time X starts. That line just prevents it from being loaded automatically, though it still gets loaded by the time X starts. The theory of the WA is that nvidia driver must be loaded later and that the “modprobe.blacklist=nvidia” on the kernel command line does not actually disable/prevent loading the nvidia driver. Add “modprobe.blacklist=nvidia” on the kernel command line before it boots. I am still testing this out but there’s that one workaround that allowed me to use the laptop. I tried nvidia 450.57 to test out the newer PM features on GeForce GTX 1650, and every reboot I got this error preventing me from actually using the laptop. xhci_hcd 0000:3e:00.0: USB bus 3 deregistered xhci_hcd 0000:3e:00.0: Host not accessible, reset failed. usb usb3: USB disconnect, device number 1 xhci_hcd 0000:3e:00.0: USB bus 4 deregistered usb usb4: USB disconnect, device number 1 ![]() xhci_hcd 0000:3e:00.0: HC died cleaning up xhci_hcd 0000:3e:00.0: Controller not ready at resume -19 xhci_hcd 0000:3e:00.0: can't change power state from D3hot to D0 (config space inaccessible) xhci_hcd 0000:3e:00.0: can't change power state from D3cold to D0 (config space inaccessible) pcieport 0000:07:02.0: can't change power state from D3cold to D0 (config space inaccessible) thunderbolt 0-0: ignoring unnecessary extra entries in DROM usb usb4: Manufacturer: Linux 5.5.86_64 xhci-hcd ![]() usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.05 xhci_hcd 0000:3e:00.0: Host supports USB 3.1 Enhanced SuperSpeed xhci_hcd 0000:3e:00.0: new USB bus registered, assigned bus number 4 Though I’m seeing similar dmesg info at boot: xhci_hcd 0000:3e:00.0: xHCI Host Controller I’m experiencing the same problem, however, it appears that my nvidia card isn’t showing up in lspci: sudo lspci |grep -E "VGA|3D"Ġ0:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) Init: systemd v: 242 Compilers: gcc: 9.2.1 Shell: zsh v: 5.8 System Temperatures: cpu: 46.0 C mobo: 27.8 C Size: 931.51 GiB speed: 6.0 Gb/s rotation: 7200 rpm serial: ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS721010A9E630 Vendor: Micro-Star MSI driver: alx v: kernel port: d000 bus ID: 03:00.0 V: 4.6 Mesa 19.3.4 compat-v: 3.0 direct render: Yesĭevice-1: Intel CM238 HD Audio vendor: Micro-Star MSIĭriver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:a171ĭevice-1: Intel Dual Band Wireless-AC 3168NGW ĭriver: iwlwifi v: kernel port: e000 bus ID: 02:00.0 chip ID: 8086:24fbĭevice-2: Qualcomm Atheros QCA8171 Gigabit Ethernet OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) Vendor: Micro-Star MSI driver: nvidia v: 440.59 bus ID: 01:00.0ĭisplay: x11 server: X.Org 1.20.7 driver: modesetting,nvidiaĪlternate: fbdev,intel,nouveau,nv,vesa compositor: kwin_x11 Topology: Quad Core model: Intel Core i7-7700HQ bits: 64 type: MT MCPĪrch: Kaby Lake rev: 9 L2 cache: 6144 KiBįlags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Volts: 12.2/10.8 model: MSI BIF0_9 type: Li-ion serial: N/A UEFI: American Megatrends v: E16J9IMS.324 date: Mobo: Micro-Star model: MS-16J9 v: REV:1.0 serial: Type: Laptop System: Micro-Star product: PE62 7RD v: REV:1.0 Host: manjaro Kernel: 5.5.6-1-MANJARO x86_64 bits: 64 compiler: gcc But 5.6rc3 is the only one which displays an error, which says - nvidia 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible) I can reproduce the issue on all 3 kernels. It is a fresh linux install, unmodified, so I have not configured anything on it. ![]() And rebooting by pressing the power button makes it usually boot in the next try. But every 5-6 boots, the booting process randomly hangs after tlp system startup shutdown. Originally asked here - where I was told about this being a possible nvidia driver bug.īasically, I recently installed manjaro latest including latest nvidia hybrid driver, and prime (I have nvidia optimus).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |