[changed driver] close the x server get blank screen with vesa driver.

rm_win · 2013-01-24 17:32:09

I have not been able to come to find a work around for this. But I have a usb thumb drive with Arch base, x and a two window managers installed. Only installed the xf86 vesa driver. In hopes to plug the thumb into different machines. After exiting the window manager x server closes but does not release the screen (black). I can type in shutdown or startx and the command will exec I just can't see console.

I loaded the xf86 intel driver and x server closes and releases the screen back to console on an intel machine. Removed intel drivers and black screen again after x closes. Same for the ati machine.

Is there a way to tell x to release the screen with the vesa drivers? Or is this a kernal module issue?

The install is all offical repository no built packages. both twm and dwm have same results.

edited: changed driver to fbdev.

Last edited by rm_win (2013-01-25 16:31:27)

nomorewindows · 2013-01-24 20:59:14

You can have all the X servers installed and it will pick the right one. I wouldn't really leave vesa installed however.

Last edited by nomorewindows (2013-01-24 20:59:25)

ConnorBehan · 2013-01-24 21:39:26

This is a problem with some of the less popular drivers. I've noticed that I can get back to a console just fine if I run uvesafb underneath X. Without uvesafb, it seems to make a difference whether I tell the BIOS to use my "native resolution". By that I mean that the tty underneath X should not be fullscreen for best results.

nomorewindows · 2013-01-25 00:09:46

ConnorBehan wrote:

This is a problem with some of the less popular drivers. I've noticed that I can get back to a console just fine if I run uvesafb underneath X. Without uvesafb, it seems to make a difference whether I tell the BIOS to use my "native resolution". By that I mean that the tty underneath X should not be fullscreen for best results.

There could be arguments for and against staying in video mode for the tty. To get the high text mode, the video mode is set high, but may cause problems. I don't know where the dri mode attachment to X windows is, but it seems to be causing some problems.

rm_win · 2013-01-25 00:54:34

nomorewindows wrote:

You can have all the X servers installed and it will pick the right one. I wouldn't really leave vesa installed however.

That was going to be my solution. I was thinking less is better for a usb drive. vesa driver works the displays without hwa and small disk space installed. Next solution was just shutdown from wm.

@connorBehan

uvesafb is frame buffering. so when using the way I have it and x server is shutdown it does not release the screen or the tty does not resume its resolution. I just can not figure out which is the problem child.

@nomorewindows

so the console video mode is not restored after x quits?

ConnorBehan · 2013-01-25 01:31:33

rm_win wrote:

I just can not figure out which is the problem child.

Restoring the console when you quit X or press Ctrl+Alt+F1 is handled by the DDX. So in xf86-video-vesa, the function is called VESALeaveVT(). But I don't know what's wrong with it. Some tty video modes must be easier to restore than others.

Arch Linux

#1 2013-01-24 17:32:09

[changed driver] close the x server get blank screen with vesa driver.

#2 2013-01-24 20:59:14

Re: [changed driver] close the x server get blank screen with vesa driver.

#3 2013-01-24 21:39:26

Re: [changed driver] close the x server get blank screen with vesa driver.

#4 2013-01-25 00:09:46

Re: [changed driver] close the x server get blank screen with vesa driver.

#5 2013-01-25 00:54:34

Re: [changed driver] close the x server get blank screen with vesa driver.

#6 2013-01-25 01:31:33

Re: [changed driver] close the x server get blank screen with vesa driver.

Board footer