Optimus, different login managers using different X configurations?

drasticraft · 2014-11-27 04:26:51

Hello all,

I've got an optimus laptop, and have bumblebee working with startx and icewm. However, when I try to start a login manager like lightdm or xdm the screen freezes and gives me an unblinking underscore, as if whatever xorg config was working for startx isn't being used.

Here's the relevant Xorg.0.log: http://ix.io/fmM

Any clues on how to force XDM to use whatever config startx is using? Am I even looking at this problem correctly?

Last edited by drasticraft (2014-11-27 04:53:36)

TheSaint · 2014-11-27 07:19:43

There aren't relevant errors in the log. The server stopped normally.
Some time X starts in a different Vt, did you try to swap by CTRL+ALT+F[1-8]?
Did you try to start X session by startx ?

drasticraft · 2014-11-27 16:49:54

TheSaint wrote:

There aren't relevant errors in the log. The server stopped normally.
Some time X starts in a different Vt, did you try to swap by CTRL+ALT+F[1-8]?
Did you try to start X session by startx ?

I cannot switch VTs when I see the unblinking underscore. The only way to get my system back is to power it off and turn it on again. When I launch xdm through startx by putting the command in my ~/.xinitrc the server started up, and then terminated, presumably because I had no permission to run XDM. When I tried putting xdm in root's xinitrc and launching it that way, I had the same result.

Here are some of the input errors:

[   200.832] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 17 paused 1
[   200.832] (II) systemd-logind: releasing fd for 13:68
[   200.867] (II) config/udev: Adding input device Video Bus (/dev/input/event11)
[   200.867] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[   200.868] (II) systemd-logind: got fd for /dev/input/event11 13:75 fd 17 paused 1
[   200.868] (II) systemd-logind: releasing fd for 13:75
[   200.887] (II) config/udev: Adding input device Video Bus (/dev/input/event10)
[   200.887] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[   200.889] (II) systemd-logind: got fd for /dev/input/event10 13:74 fd 17 paused 1
[   200.889] (II) systemd-logind: releasing fd for 13:74
[   200.920] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[   200.920] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   200.921] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 17 paused 1
[   200.921] (II) systemd-logind: releasing fd for 13:66
[   200.960] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[   200.960] (II) No input driver specified, ignoring this device.
[   200.960] (II) This device may have been added with another device file.
[   200.961] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[   200.961] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[   200.962] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 17 paused 1
[   200.962] (II) systemd-logind: releasing fd for 13:67
[   201.000] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event17)
[   201.000] (II) No input driver specified, ignoring this device.
[   201.000] (II) This device may have been added with another device file.
[   201.001] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event18)
[   201.001] (II) No input driver specified, ignoring this device.
[   201.001] (II) This device may have been added with another device file.
[   201.001] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event19)
[   201.001] (II) No input driver specified, ignoring this device.
[   201.001] (II) This device may have been added with another device file.
[   201.003] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 17 paused 1
[   201.003] (II) systemd-logind: releasing fd for 13:69
[   201.037] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event12)
[   201.037] (II) No input driver specified, ignoring this device.
[   201.037] (II) This device may have been added with another device file.
[   201.038] (II) config/udev: Adding input device HDA Intel PCH Dock Mic (/dev/input/event13)
[   201.038] (II) No input driver specified, ignoring this device.
[   201.038] (II) This device may have been added with another device file.
[   201.038] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event14)
[   201.038] (II) No input driver specified, ignoring this device.
[   201.038] (II) This device may have been added with another device file.
[   201.039] (II) config/udev: Adding input device HDA Intel PCH Dock Line Out (/dev/input/event15)
[   201.039] (II) No input driver specified, ignoring this device.
[   201.039] (II) This device may have been added with another device file.
[   201.039] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event16)
[   201.039] (II) No input driver specified, ignoring this device.

Also, here are the (WW) errors.

	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   358.177] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[   358.178] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[   358.178] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   358.187] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[   358.191] (WW) Warning, couldn't open module modesetting
[   358.192] (WW) Warning, couldn't open module fbdev
[   358.192] (WW) Warning, couldn't open module vesa
[   358.380] (WW) intel(0): failed to restore desired modes on VT switch

Last edited by drasticraft (2014-11-27 17:24:56)

Arch Linux

#1 2014-11-27 04:26:51

Optimus, different login managers using different X configurations?

#2 2014-11-27 07:19:43

Re: Optimus, different login managers using different X configurations?

#3 2014-11-27 16:49:54

Re: Optimus, different login managers using different X configurations?

Board footer