Closing x-windows causes my CLI resolution to change

thewizkid · 01-13-2010, 05:27 AM

Hi, I am running Slackware 13.0 x86 kernel 2.6.29.6. I have a NVIDIA 8800 GT graphics card.

Here is my situation. If I start x-windows using a windows manager such as KDE or blackbox ( or just load x with an xterm ) and later try to exit it and return to my CLI, the CLI resolution does not go back to what it normally was. The screen is smaller and bottom lines are cut off..so I can't see what I type.

If I attempt to enter a command I have to type enter a few times to bring my prompt into view to see if I even entered what I wanted correctly. So basically is really annoying lol.

I tried searching Google, but it is difficult to enter in a query that will return the answers I need.

If I restart my resolution goes back to normal.

Why does my resolution not return back to normal?

Is there a way to change the CLI resolution from the command line, without having to restart?

And lastly, how can I solve the problem?

This may lead to an answer:

When I installed Slackware I only use one physical CD, d1. My CD/DVDRRW drive no longer reads DVDs and I don't want to waste any more CDs. I installed only the first CD ( a, ap, d, l, e, and n ) during setup and the rest afterwards ( including x and xap ). I didn't get any errors or anything because I used the install-packages script included in the iso images that I mounted to install all of the packages.

If any more information is required I will be glad to provide it. Thanks in advance.

I wanted to include my /var/log/Xorg.0.log but the post character count was reached. If need be I will include it in another post, although, there were no errors cited in it. Just just 3 warnings which seem unrelated.

Code:

(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0

ozanbaba · 01-13-2010, 06:15 AM

you can use fbset for setting framebuffer modes.

and what you are experiencing is probably framebuffer problem

thewizkid · 01-14-2010, 05:54 AM

Thanks for your input. You set me on the right track. It was indeed a framebuffer console issue.

Before my system loaded up, I would be present with a message telling me that there was an:

Code:

Undefined video mode number: 317

Through Google, I came across a post that mentioned the framebuffer mode values are converted to hex from the decimal values that are set in the lilo.conf file. Knowing this..I whipped out a pen and paper lol. Slackware would have failed a couple of tests I had to take on converting between binary/hex/dec for sure.

Oddly, the hex value ( mode number ) that the above error gave me did not equal the decimal value in my lilo.conf. I took the decimal value for the resolution I wanted and converted it to hex and set with "vga=" preceded with "0x".

Code:

vga=0x305

instead of

Code:

vga= 773

The above line in lilo.conf solved my framebuffer problem. I now have the resolution I want in the initial CLI and after exiting x-windows..it reverts back to my selection. Thanks again for your help and I hope this helps someone else.

Edit: I tried to reproduce the error by editing my /etc/lilo.conf and setting the vga back to what it was and it still loaded the correct framebuffer console mode. Oh well..I don't really know why 100% it didn't work but it does now, so moving on.