Manjaro hanging at 'Starting systemd-udevd version 252.10-2-manjaro' when booting newer kernel

Support Graphics & Display
,
1

So, I’m at a loss!

I’m running 5.15.112-1-MANJARO and I’ve installed kernel 6.2. But when booting that kernel, it indefinitely hangs at Starting systemd-udevd version 252.10-2-manjaro.

I’ve tried uninstalling and installing different kernels. I’ve tried uninstalling and installing the video drivers (even forcibly). Every time I boot a different kernel than 5.15 it hangs.
I’ve tried almost all combinations of mhwd-gpu and mhwd commands from Configure Graphics Card.

Output of mhwd -li:

> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
video-hybrid-intel-nvidia-prime            2023.03.23               false            PCI
     video-modesetting            2020.01.13                true            PCI
           video-linux            2018.05.04                true            PCI


Warning: No installed USB configs!

I don’t even think my nvidia card is ‘installed’ - glxinfo | grep OpenGL only returns my Intel UHD 630 Graphics. I’ve tried doing sudo modprobe nvidia.

I must admit, I don’t quite remember everything, and I have suspicions that the issue originates with me reinstalling video drivers at one point.

Any help in troubleshooting the issue is greatly appreciated!! TIA.

2

I should say, I’m on a laptop with a discrete GeForce GTX 1050 Ti and an integrated Intel UHD Graphics 630,

3

So why not use kernel 5.15?

Its supported until 2026.

6.2 is EOL soon anyways.

It looks like it is, and using PRIME. And thats expected. Do

prime-run glxinfo | grep OpenG
4

Thank you.

I could, I’d like to update though. And I definitely want the option :wink:

6.2 is just the one I ended with now, I’ve tried with 6.1 and 6.3 as well - Same result, so I don’t think it’s a kernel issue.

Hmm… prime-run glxinfo | grep OpenGL returns the following:

X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  50
  Current serial number in output stream:  51
5

Well it makes it appear as though prime-run is broken somehow.

Heres what the script does expanded into the separate env vars:

__NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep OpenGL

There was recently an example of it working when prime-run didnt. How, I do not know.

6

Hmm… Yeah. I think it might be an X misconfiguration somewhere, however I cannot seem to pin it down. Again, thank you.

7

Check in /etc/X11/{mhwd,xorg.conf}.d/*

8

In /etc/X11/mhwd.d/intel.conf I’ve got:

##
## Generated by mhwd - Manjaro Hardware Detection
##
 
 
Section "Device"
    Identifier  "Device0"
    Driver      "intel"
    BusID       "PCI:0:2:0"
    Option      "AccelMethod" "sna"
	Option      "DRI"    "true"
EndSection
 
 
Section "DRI"
        Group  "video"
        Mode   0666
EndSection
 
 
Section "Extensions"
    Option "Composite" "Enable"
    Option "RENDER"    "Enable"
EndSection
 
 
Section "InputClass"
    Identifier          "Keyboard Defaults"
    MatchIsKeyboard        "yes"
    Option              "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection

In /etc/X11/mhwd.d/nvidia.conf I’ve got:

##
## Generated by mhwd - Manjaro Hardware Detection
##

Which seem wrong…?

In /etc/X11/xorg.conf.d/90-mhwd.conf I’ve got:

##
## Generated by mhwd - Manjaro Hardware Detection
##

Finally /etc/X11/xorg.conf contains:

# nvidia-xconfig:  version 530.41.03

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    VendorName     "NVIDIA Corporation"
    ChipId          0x0
    ChipRev         0x0
    IRQ             0
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
9

This one looks like it shouldnt be there. Or at least … its worth removing it for now.
We can back it up…

sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

Then lets go ahead and pull a reinstall:

sudo mhwd -f -i pci video-hybrid-intel-nvidia-prime

(afterwards look again … config files might be populated)

10

I tried it, the intel.conf, nvidia.conf and 90-mhwd.conf have the same content as above. A restart produces the same described result…

11
  1. Switch to a different console by pressing CTRL+ALT+Fn (Where Fn is F2 and higher)
  2. Check your system logs using journalctl and/or dmesg for errors wrt to your graphics card drivers…
12

Hmm… dmesg -L --level err shows no relevant errors.

I’m having a hard time parsing the output of journalctl, the following might have some relevance?

Working (5.15) journalctl output:

May 22 23:00:31 myhost kernel: bbswitch: loading out-of-tree module taints kernel.
May 22 23:00:31 myhost kernel: bbswitch: module verification failed: signature and/or required key missing - tainting kernel
May 22 23:00:31 myhost kernel: bbswitch: version 0.8
May 22 23:00:31 myhost kernel: bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
May 22 23:00:31 myhost kernel: bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
May 22 23:00:31 myhost kernel: bbswitch: detected an Optimus _DSM function
May 22 23:00:31 myhost kernel: pci 0000:01:00.0: enabling device (0006 -> 0007)
May 22 23:00:31 myhost kernel: bbswitch: disabling discrete graphics
May 22 23:00:31 myhost kernel: bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is off

Not working (6.2) journalctl output:

May 22 22:59:10 myhost kernel: bbswitch: loading out-of-tree module taints kernel.
May 22 22:59:10 myhost kernel: bbswitch: module verification failed: signature and/or required key missing - tainting kernel
May 22 22:59:10 myhost kernel: bbswitch: detected an Optimus _DSM function
May 22 22:59:10 myhost kernel: pci 0000:01:00.0: enabling device (0006 -> 0007)
May 22 22:59:10 myhost kernel: bbswitch: disabling discrete graphics
May 22 22:59:10 myhost systemd[1]: Started Simple Desktop Display Manager.
May 22 22:59:10 myhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sddm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 22 22:59:10 myhost systemd[1]: Reached target Graphical Interface.
May 22 22:59:10 myhost kernel: bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is off
May 22 22:59:10 myhost bumblebeed[531]: /usr/bin/bumblebeed 3.2.1-21-g0851da6 started

The relevant output seems to be largely equal, however, bumblebeed is not started in the working kernel startup…?

13

In the working one, I also get May 22 23:00:29 myhost kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) which isn’t present in the non-working one…

15

After trying pretty much everything, every kernel, all grub kernel parameters, uninstalling drivers, reinstalling drivers, rebuilding boot images, etc. etc. I solved the issue by disabling bumblebee and bbswitch (uninstalling and rebooting).

…

  • I’m using PRIME now.
    See here.
16

Bumblebee conflicts with PRIME and should have never been on the system.

It also wasnt mentioned anywhere in the thread.

mhwd reported prime.

Not anything like

Thanks for letting us know though.

17

Yeah, you’re right. Somehow it seemed ‘default’? mhwd didn’t report any bumblebee, but the repo-package was installed for some reason, and it seemed that, that alone caused the issue (maybe along with some other setting I myself might have done long ago).

18

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.