Kernel Compiling Nightmares- Framebuffer in SlackWare

[jay_murr]

I am having a nightmare of a time with my kernel compilation in slackware 12 with the 2.6.21.5 kernel. I run an IBM ThinkPad T-42, and as soon as I recompile, I lose all console video (linux framebuffer, I'm assuming). The OS still loads, and I can log in (starting X without being able to see a thing). X comes up and i'm okay from there. As long as I don't drop out of X I'm cool. Besides that, the system is fast and stable. What am I doing wrong? Am I neglecting to compile something in?

[daark.child]

It seems like you are missing out the part that includes framebuffer support in the kernel. This article will help lead you in the right direction. Its for gentoo, but parts of it are relevant to any distro.

[jay_murr]

I did that. Everyting framebuffer related that I can see that relates has been enabled.

[Dapper Dan]

Can you post the results of:

ls /boot

And:

joe /etc/lilo.conf

[Segfault]

You may want to read Documentation/fb (in kernel source directory) for your card to get the syntax correct.

[jay_murr]

An ls on /boot is as follows:

A computer lets you make more mistakes faster than any other invention,
with the possible exceptions of handguns and Tequilla.
-- Mitch Ratcliffe

root@Thinker-IV:~# ls /boot
README.initrd@ config-generic-smp-2.6.21.5-smp
System.map config-huge-2.6.21.5
System.map-generic-2.6.21.5 config-huge-smp-2.6.21.5-smp
System.map-generic-smp-2.6.21.5-smp diag1.img
System.map-huge-2.6.21.5 map
System.map-huge-smp-2.6.21.5-smp vmlinuz
System.old vmlinuz-generic-2.6.21.5
boot.0300 vmlinuz-generic-smp-2.6.21.5-smp
boot_message.txt vmlinuz-huge-2.6.21.5
bzImage vmlinuz-huge-smp-2.6.21.5-smp
config@ vmlinuz.old
config-generic-2.6.21.5
root@Thinker-IV:~#

Pico of /etc/lilo.conf reveals:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 120
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = Linux
read-only

image = /boot/vmlinuz.old
root = /dev/hda1
label = Old.Kernel
read-only
# Linux bootable partition config ends



The lilo here (video section anyway) reveals the system default. I CAN make VGA = Normal here, and I wil be able to see my system boot... but without the penguin and in 640x480, as opposed to the nice framebuffered 1024x768... What gives? It didn't happen until after I compiled, but now it happens whenever I recompile a kernel for this system. THAT tells me I'm missing something...

[Dapper Dan]

I see you still have your old kernel as a choice in Lilo. Can you boot to it still? When you do, do you get the framebuffered penguin still as you want it? Did you use your old .config file from the previous kernel and just changed some things? Or did you compile a new kernel from scratch creating your own new configuration?

[jay_murr]

Well... Hmm... First I:

make mrproper
Then I make menuconfig (been using xconfig lately,for the verbose help)
Then, I edit and save ".config"...
then I go into lilo and add the .old kernel...
THEN, I make, make modules, make install, make modules_install, and reboot...

Whether I start from a fresh kernel or not, the result is the same... No console video after lilo starts booting the kernel. If I boot my old kernel, it works just fine, but of course I don't have all of the cool **** that I compiled in... and I NEED my battery monitor!
There has to be something that doesn't compile by default when doing the kernel, but loads, either as a module, or hard-kernel-code, in the default kernel. What do you guys think?

[Segfault]

I think you should read the kernel documentation, as I already suggested fb docs for your video card, and overall.
make modules is not necessary for instance, make builds kernel image and modules.

[Dapper Dan]

If I boot my old kernel, it works just fine...

I'd have to agree with daark.child. I think you may have inadvertently left something out or changed something when configuring for your new kernel. That's why I usually start from my previous kernel's .config and include or take away things from there.