People,
I occasionally start a second X display from a console login with:
"xinit -- :1
but after upgrading to F21 it just hangs with an underscore in the top left of the screen and I have to do a remote log in and kill the process. I attach the log but I am not sure if it indicates what the problem is . .
Thanks,
Phil.
On Wed, 17 Dec 2014 20:40:33 +1100 Philip Rhoades phil@pricom.com.au wrote:
I occasionally start a second X display from a console login with:
"xinit -- :1
but after upgrading to F21 it just hangs with an underscore in the top left of the screen and I have to do a remote log in and kill the process. I attach the log but I am not sure if it indicates what the problem is . .
I'd try to look into the cause of these:
[268529.443] (II) intel(0): switch to mode 1440x900@60.0 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none [268529.449] (EE) intel(0): failed to set mode: Permission denied [13] [268529.450] (WW) intel(0): failed to restore desired modes on VT switch [268529.450] (EE) intel(0): sna_mode_check: invalid state found on pipe 0, disabling CRTC:7
The "permission denied" piece smells bad... :-)
HTH, :-) Marko
Marko,
On 2014-12-17 21:22, Marko Vojinovic wrote:
On Wed, 17 Dec 2014 20:40:33 +1100 Philip Rhoades phil@pricom.com.au wrote:
I occasionally start a second X display from a console login with:
"xinit -- :1
but after upgrading to F21 it just hangs with an underscore in the top left of the screen and I have to do a remote log in and kill the process. I attach the log but I am not sure if it indicates what the problem is . .
I'd try to look into the cause of these:
[268529.443] (II) intel(0): switch to mode 1440x900@60.0 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none [268529.449] (EE) intel(0): failed to set mode: Permission denied [13] [268529.450] (WW) intel(0): failed to restore desired modes on VT switch [268529.450] (EE) intel(0): sna_mode_check: invalid state found on pipe 0, disabling CRTC:7
The "permission denied" piece smells bad... :-)
It appears that the process is waiting for the other X process to terminate - I think it might have something to do with F21 now running X as rootless and maybe Kernel Mode Setting? I found that the following now works (and does what I want - where it didn't before):
startx -- :1
Regards,
Phil.
-
Marko Vojinovic -
Philip Rhoades