• GDM won't start with nvidia-libgl


    So I have two systems

    System 1:

    CPU: I7 4790K
    RAM: 32G
    HDD: 2 SSDs
    Video: GTX 970

    System 2:

    CPU: I5 4400
    Ram: 16G
    HDD: 2 SSDs
    Video: GTX 660

    System 1 works as expected. System 2 GDM crashes whenever nvidia-libgl is installed.

    They both have the intel-ucode, they both have

    [daemon]
    # Uncoment the line below to force the login screen to use Xorg
    WaylandEnable=false
    

    And

    MODULES="nvidia"
    
    

    In /etc/mkinitcpio.conf

    They both have have

    initrd	/boot/intel-ucode.img /boot/initramfs-linux.img
    

    In their grub settings

    They both show this:

    dmesg | grep microcode
    [    0.000000] microcode: CPU0 microcode updated early to revision 0x1e, date = 2015-08-13
    [    0.123754] microcode: CPU1 microcode updated early to revision 0x1e, date = 2015-08-13
    [    0.137474] microcode: CPU2 microcode updated early to revision 0x1e, date = 2015-08-13
    [    0.151183] microcode: CPU3 microcode updated early to revision 0x1e, date = 2015-08-13
    [    0.663116] microcode: CPU0 sig=0x306c3, pf=0x2, revision=0x1e
    [    0.663158] microcode: CPU1 sig=0x306c3, pf=0x2, revision=0x1e
    [    0.663202] microcode: CPU2 sig=0x306c3, pf=0x2, revision=0x1e
    [    0.663222] microcode: CPU3 sig=0x306c3, pf=0x2, revision=0x1e
    [    0.663467] microcode: Microcode Update Driver: v2.01 <[email protected]>, Peter Oruba
    
    

    At this point I am kind of at a loss. I have run

     mkinitcpio -p linux
    

    and rebooted numerous times. Any help will be greatly appreciated

  • I wanted to bump this up.

    I fiddled and fiddled with this and couldnt get it to work. I reverted to the known-working 340xx driver and I don’t have the problem. I am not sure what the problem is with the latest drivers. I may try again when newer drivers come out

    Everything seems to point to a microcode problem but I just can’t put my finger on it

libgl3 gdm33 nvida2 Posts 2Views 654
Log in to reply