Killing X Disables my keyboard and monitors. But I can ssh in.

matchew · 2014-07-18 04:21:29

When using multiple monitors and open source drivers if I kill my X session using bspc quit (I am using bspwm) or just manually killing the pid's I am brought to a black screen, my monitors goto power saving mode, and my keyboard and mouse is disabled. Oddly I can ssh in.

1. this only occurs when using open source drivers
2. I have tried this with two different cards. A older nvidia card and a volcanic island series (new) radeon.
3. Does not occur with proprietary drivers
4. does not occur with a single monitor
5. occurs with 2+ monitors only. No problem with a single monitor only

Ideally I would use my newer radeon card as this is will allow me to use 3+ monitors and the older nvidia is limited to two.
Furthermore, I would also prefer to use the open-source drivers. They are not officially supporting the volcanic island cards yet, however, everything seemed stable with the exception of the killing the X session

here is a tail of the Xorg.0.log for the radeon card (don't have the nvidia log any longer, but the symptons were identical)

here is my 20-radeon.conf

Section "Device"
    Identifier "Radeon"
    Driver "radeon"
EndSection

Section "Monitor"
    Identifier "DVI-0"
    Option 	"Primary" "true"
    Option	"rotate" "left"
EndSection

Section "Monitor"
    Identifier "DisplayPort-0"
    Option     "rotate" "left"
    Option  	"LeftOf" "DVI-0"
EndSection

Section "Monitor"
    Identifier "DVI-1"
    Option     "rotate" "left"
    Option  	"RightOf" "DVI-0"
EndSection

Last edited by matchew (2014-07-18 15:02:40)

ConnorBehan · 2014-07-18 05:19:44

Killing X works with closed drivers but not open? I'm confused about why you showed the log for the closed driver.

matchew · 2014-07-18 05:38:36

that was actually Xorg.0.log.old, which was from earlier today when I was using the open source drivers. At least I thought it was...I guess I Can check again when I get back to that machine in the morning.

matchew · 2014-07-18 15:05:16

Shit, ConnorBeHan you're right. I'm looking at it now with a rested set of eyes. I guess I don't have the bad log around. I went with the catalyst drivers and was going to call it a day but remembered I was having the exact same problems with the open source nvidia drivers the other week on a much older card. I thought it was the same log due to the

[   305.297] (II) evdev: Dell Dell USB Keyboard: Close
[   305.297] (II) UnloadModule: "evdev"
[   305.297] (II) evdev: Logitech Unifying Device. Wireless PID:101b: Close
[   305.297] (II) UnloadModule: "evdev"
[   305.297] (II) evdev: Sleep Button: Close
[   305.297] (II) UnloadModule: "evdev"
[   305.297] (II) evdev: Power Button: Close
[   305.297] (II) UnloadModule: "evdev"
[   305.297] (II) evdev: Power Button:

this was also in the log, and I read it as essentially disabling my montiors and keyboards as you would expect on a shutdown. but that is where it ends.

matchew · 2014-07-18 15:37:01

this bug[1] better describes my problem. I think I might try down grading

1. https://bugs.freedesktop.org/show_bug.cgi?id=75459

Last edited by matchew (2014-07-18 15:38:07)

Arch Linux

#1 2014-07-18 04:21:29

Killing X Disables my keyboard and monitors. But I can ssh in.

#2 2014-07-18 05:19:44

Re: Killing X Disables my keyboard and monitors. But I can ssh in.

#3 2014-07-18 05:38:36

Re: Killing X Disables my keyboard and monitors. But I can ssh in.

#4 2014-07-18 15:05:16

Re: Killing X Disables my keyboard and monitors. But I can ssh in.

#5 2014-07-18 15:37:01

Re: Killing X Disables my keyboard and monitors. But I can ssh in.

Board footer