Terminal resolution after kernel upgrade???

Southpaw76 · 09-09-2006, 03:03 PM

Hello all,
I was wondering if anyone else has come across this problem. I originally did a Slackware-Current (11-rc2) installation using the bareacpi.i kernel image. After having done some post install configuration activities, I upgraded my kernel to linux-2.6.17.11 from kernel.org. However, after having finished everything I rebooted and my terminal resolution had changed from a smaller font size and the little penguin in the upper left hand corner to a larger font size and no penguin at all, does this sound familiar???

Btw, nothing changed in my /etc/lilo.conf, my screen resolution setting is set to 1024x768x64k....

uselpa · 09-09-2006, 03:19 PM

That usually means that you forgot to compile framebuffer support into your kernel.

Southpaw76 · 09-09-2006, 08:14 PM

Of course I do, I have an ATI Rage128 Pro Ultra TF AGP card. These are my kernel settings for it...

Code:

Linux Kernel v2.6.17.11 Configuration
Device Drivers --->
>>Character Devices
<*> /dev/agpgart (AGP Support)
<*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
<*> ATI Rage 128
>>Graphics Support
<*> Support for frame buffer devices
<*> ATI Rage128 display support

drkstr · 09-09-2006, 11:31 PM

What about this one?

Console display driver support --->

You didn't list, that you turned it on there as well.
...drkstr

Southpaw76 · 09-10-2006, 01:55 PM

My Bad, heres what I got for that...

Code:

Console display driver support--->
--- VGA text console
[*] Video mode selection support
<*> Frambuffer Console Support

...sorry about that.

drkstr · 09-11-2006, 01:32 AM

Hmm, strange. The only thing I can think of is that your graphic device might need to be set as a module if you use DRI. From the help menu in the kernel config:

Quote:

Kernel-level support for the Direct Rendering Infrastructure (DRI)introduced in XFree86 4.0. If you say Y here, you need to selectthe module that's right for your graphics card from the list below. These modules provide support for synchronization, security, and DMA transfers.

It seems to indicate that it like modules instead of hard coding. You also might want to be careful for the "chain effect" when making some parts modular, and some not. Sound support is a perfect example of breakage when device drives are made modular and the support for them is not.

Try switching all options to modular to see if that changes anything, and if not, see if the modules are actually loading with 'lsmod'.

regards,
...drkstr

stabu · 09-11-2006, 11:58 AM

I know you say nothing changed in lilo.conf, as in kernel boot parameters, but that exactly the effect I get when I leave out "vga=791".

alienmagic · 09-11-2006, 11:00 PM

I had the same issue, but it's been long enough that I don't remember which option exactly that it was the corrected the issue. In addition to what you have listed for framebuffer options, I just checked my config and I also have:

GRAPHICS SUPPORT --->
-VGA 16-color graphics support
-VESA VGA graphics support (it seems like this may have been the one that got my console back to smaller text w/ the boot-time penguin)
-Virtual Frame Buffer Support

and under Logo Configuration --->
-Bootup logo
-Standard 16-color Linux Logo
-Standard 224-color Linux Logo

Like I said, I don't remember for sure which it was, or what combination it was, but I know that until I compiled the kernel with all of those options, I either had large fonts with no penguin, or just a black screen.