LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   LILO question (https://www.linuxquestions.org/questions/slackware-14/lilo-question-35373/)

jamaso 11-13-2002 10:09 AM

LILO question
 
I have a third entry(hda1) on my LILO prompt that is useless (don't know how come it got there),and also i would like to ask you why do i get :

Boot : linux
Loading : linux...
you just passed an undefined mode press <space> or <return>... (how can i fix this to be abble to just load it )

BTW : Mephisto said on athread i started :

"We probably want to get you off the vesa framebuffer before we worry about the monitor resolution." why is that ? I looked on vga and vesa man pages but they tell about the same thing , is there any problem running a vesa driver ?

here is my /etc/lilo.conf file :

bash-2.05a# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot="/dev/hda"
message = /boot/boot_message.txt
prompt
timeout="1200"
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x32k
# 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
# DOS bootable partition config begins

other = /dev/hda1
label="DOS"
table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins

image="/dev/hda1"

image="/dev/hda1"

image="/dev/hda1"

image = /boot/vmlinuz
root = /dev/hda5
label = Linux
read-only
# Linux bootable partition config ends

thanks

acid_kewpie 11-13-2002 10:21 AM

that's a bizarre file you have there, what are all those image=/dev/hda1 lines doing? get rid of them, that may well be what's giving you problems.

jamaso 11-13-2002 10:07 PM

it's time to get some glasses eheh . thanks

jamaso 11-14-2002 11:03 AM

unfortunately that didn't help (erasing the 3 (image="/dev/hda1")lines) but i'm having the same problem . i already uncommented # VESA framebuffer console @ 1024x768x256 too but it make no difference . sorry for not posting earlier .

LNXman 11-14-2002 11:59 AM

LILO does not know which resolution to load with, so . . .

- You can try letting your vga=normal, or. . .
- You can play around with the vga resolution codes starting from the lowest (640x480) to the highest until you find a suitable one.

GL

wonderpun 11-14-2002 02:54 PM

Try uncommenting the "vga = normal" line. Good luck!

Half_Elf 11-15-2002 12:10 AM

I got the same problem when I try to activate SVGA text mode with the old GeForce1/Riva Frame Buffer support. It Seems that new Nvidia graphic cards are not supporting VESA 2.0 mode, tell me if I'm wrong.

If I use "Vesa frame buffer" in my kernel, my screen shutdown...
I suppose I will have to wait for a real GeForce2 chipset support before playing with SVGA :(

Can it be your problem too Jamaso?

jamaso 11-15-2002 01:21 PM

well i would like to help but have a diamond stealth III S540, sorry .
I uncommented sva=normal and also others but nothing changed , BTW i can get X running ok but there's this problem i told you before , anyways i promise not to take more of your time , so here's my uncommented /etc/lilo.conf file (after some trimming) :
-----------------------------------------------------------------------
boot="/dev/hda"
message = /boot/boot_message.txt
prompt
timeout="1200"
change-rules
reset
label="DOS"
table = /dev/hda
image = /boot/vmlinuz
root = /dev/hda5
label = Linux
read-only
--------------------------------------------------------------------------

thank you


All times are GMT -5. The time now is 09:03 PM.