I decided to compile the 2.6.11 kernel in Slackware 10.1. Well all goes dandy until its time to reboot. I choose Slackware020611 from LILO and I get a black screen. NOTHING happens. Why? :P

You must compile in VESA Framebuffer support

And how does 1 do that?

My questions are: how did you comile it? was it a Slack compiled kernel or from kernel.org? Can you post your lilo.conf?

Device Drivers > Graphics support ->
Console display driver support ->
Edit: choose all those selections as built-in not modules

I used the kernel.org kernel.

Thanks all.

So did it boot correctly now?

Well thats my next question. I did the way by using bzImage and vmlinuz. Will I have to do ll that stuff again or can I just edit the config, remake the modules and reinstall them?

You have to redo the kernel compilation and install to enable framebuffer
as built-in in kernel (as any feature you mark as built-in in config is to be
compiled in the kernel, so bzImage, vmlinuz)

So I take it I do have to do the vmlinuz and bzImage thing again.


ps.

Didn't understand your post. My brain has been off today.

Sorry, I find it not so clear too...

- You want framebuffer support so you run the configure step
enabling the options I mentioned above, as built-in
(there are 2 ways to add a feature in the kernel, built-in
and module)

- Because the framebuffer feature is enabled as built-in into
the kernel, the kernel will be recompiled so you have to
install the kernel image after the compilation
(cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.11 or
/boot/vmlinuz, up to you)

- there is a way to enable framebuffer as module and make
an initrd to load it at boot, but I never tested that

Still does not work.

What I did:

Enabled options as built in kernel.
make vmImage
make modules
make install_modules
/sbin/lilo

It should be: make modules_install
Anyway, it should've worked since you don't need that stuff as module. A quick way to get your console again is to set vga=normal in your lilo.conf and then run lilo. You won't get a "graphical" resolution in your console but you'll be able to see the messages, and if you're always on X you won't notice the difference.

Of course, if you really want to solve this (I personally prefer this ) you can try using the options in this thread (you can see/change them by editing the .config manually): http://www.linuxquestions.org/questi...postid=1655489
They're almost equal to the ones keefaz said, recheck them.

did you copy the bzImage you made to /boot ?

egag

Yes.
I found the problem. LILO says /vmlinuz is not found even though I'm staring right at it.