Incorrect lilo.conf = kernel panic...help!

overlook1977 · 05-24-2007, 09:24 PM

filesystem is ext3, its a standard 7200 rpm IDE drive.

i tried the append but running 'lilo' doesnt like this.

overlook1977 · 05-24-2007, 09:42 PM

just a thought...how does it know where the tux icon is? AND, is it possible the resolution of this icon, if its even trying to load it, is somehow not matching all the screen resolutions ive tried so far? I dont understand how the stupid login console has issues but X runs fine.

H_TeXMeX_H · 05-24-2007, 10:07 PM

So, lemme get this straight, just so I know where we are at here:

You can boot just fine now, right ? Everything works fine, but you want to boot with the framebuffer set to a higher resolution, right ?

That append that I suggested goes in your lilo.conf somewhere after 'image='.

JohnKFT · 05-25-2007, 04:38 AM

I seem to remember reading somewhere (can't remember where) that 'Using a VESA framebuffer console in lilo.conf gives you finer graphics and a nice penguin logo but can cause problems .... '. Can't remember what the problems were, or even if they were described.

Not helpful I know, nor even explanatory, but at least indicates that you are probably not actually doing anything wrong as such, although perhaps cannot for some reason get your tux back. My lilo.conf gives these options :

# 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

vga=769 is presumably the least demanding of the system, so perhaps it is worth experimenting, beginning with that one. If that works you can move up till it complains. If, however, I am talking rubbish, hopefully someone will say so.

overlook1977 · 05-25-2007, 07:05 AM

Quote:

You can boot just fine now, right ? Everything works fine, but you want to boot with the framebuffer set to a higher resolution, right ?

Exactly. I can boot with vga=normal. I have also cycled thru all the other options, and it only will take vga=normal. It drives me particularly crazy b/c it worked in 2.4, and something changed with the new kernel.

So would I put vga=773 (what it was in 2.4) at the top, and the put append="vga=normal" at the bottom below the image line?

overlook1977 · 05-25-2007, 07:11 AM

OK, so let me ask this. How can I find out if I have framebuffer support in the kernel? I know the driver is good b/c X works and it booted nice and pretty in 2.4.

H_TeXMeX_H · 05-25-2007, 11:49 AM

Check your .config, look for vesafb. Typically vesafb may have problems with higher resolutions on some cards. That's why one uses nvidiafb or rivafb if one has an nvdia card. Unfortunately, these two modules conflict with the proprietary nvidia driver ... oh well.

overlook1977 · 05-26-2007, 10:33 AM

i did a search for 'vesafb' in the .config file and that text is not in there. Do I need to recompile the kernel?

overlook1977 · 05-26-2007, 10:42 AM

Code:

# Graphics support
#
CONFIG_FIRMWARE_EDID=y
# CONFIG_FB is not set

hmmm....this was in the config file. Perhaps this is why I do not have framebuffer support? If so, what would be the procedure to fix?

MannyNix · 05-26-2007, 12:10 PM

Hi, not sure what's your video card, as for kernel video options check this Gentoo Nvidia guide Very helpfull imo.
As for kernel compiling take a look at Alien Bob's kernel guide. You can probably start reading from "Downloading and configuring".
I believe everything you're looking for is there, if not, ask the slackers around

overlook1977 · 05-26-2007, 12:24 PM

the card is a nvidia geforce4 mx 420, 64 MB

I had to use a legacy 1.0-96xx driver...if this helps.

H_TeXMeX_H · 05-26-2007, 12:38 PM

Well, here's my graphics support section:

Code:

#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_FIRMWARE_EDID is not set
# CONFIG_FB_MODE_HELPERS is not set
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set

Note things in red.

overlook1977 · 05-26-2007, 12:42 PM

H_TeXMeX_H: Thanks for the input, I would suspect that is the problem also. If I change the .config file, do I have to recompile the kernel or anything to make the change effective?

H_TeXMeX_H · 05-26-2007, 02:21 PM

Of course. The .config file is configuration file used to build the kernel. It dictates what is going to be built-in to the kernel, what as a module, and what should not be built at all.

gnashley · 05-29-2007, 09:12 AM

A couple of pointers: using vga=normal disables the frame buffer and allows you to use the real driver for your video card with whatever acceleration features, etc.
The 'icon' is contained in a header file within the kernel sources and gets compiled into the kernel, but if you are using vga=normal you will not see the icon.