Page 1 of 1

Scratch Install Issues with lilo.confi

PostPosted: Thu Oct 09, 2008 4:11 am
by joeadkins
Quick question, probably simple and I'm just overlooking something. On the Scratch Install i'm stuck on the lilo.conf and keep getting the same error. I've reloaded from scratch 4 times now and need a little guidance. Here is what I'm putting when vi /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 @ 640x480x256
vga = 769
# 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/bzImage-1234
label=test-1234
root=/dev/hda1
read-only
# Linux bootable partition config ends

Then when I run /sbin/lilo I get this:

Warning: LBA32 addressing assumed
Added test-1234 *
One warning was issued.


I'm following the scratch install exactly up to this point. I tried rebooting anyways and when it starts to boot up i get a blank/black screen and a freeze up. Any suggestions? Thanks

PostPosted: Thu Oct 09, 2008 8:48 am
by mflorell
What Slackware version and kernel version are you using?

PostPosted: Thu Oct 09, 2008 12:17 pm
by joeadkins
Slackware version 12.0 and Kernel 2.6.17 as recommended in the scratch install. I don't mind re-installing with a different version is that's the issue.

PostPosted: Thu Oct 09, 2008 6:24 pm
by mflorell
I'm not really a kernel debugger, it can take a while to fix this kind of problem depending on your hardware and the kernel options you have selected.

PostPosted: Fri Oct 10, 2008 9:58 am
by gerski
just put 'lba32' anywhere in the config,

example:

# VESA framebuffer console @ 640x480x256
vga = 769
lba32

then save, then type /sbin/lilo

Re: Scratch Install Issues with lilo.confi

PostPosted: Sat Oct 11, 2008 5:24 pm
by Nortelguy
joeadkins wrote:Quick question, probably simple and I'm just overlooking something. On the Scratch Install i'm stuck on the lilo.conf and keep getting the same error. I've reloaded from scratch 4 times now and need a little guidance. Here is what I'm putting when vi /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 @ 640x480x256
vga = 769
# 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/bzImage-1234
label=test-1234
root=/dev/hda1
read-only
# Linux bootable partition config ends

Then when I run /sbin/lilo I get this:

Warning: LBA32 addressing assumed
Added test-1234 *
One warning was issued.


I'm following the scratch install exactly up to this point. I tried rebooting anyways and when it starts to boot up i get a blank/black screen and a freeze up. Any suggestions? Thanks


I am using slackware too and I get that same message don't worry about it.. I bet I can guess your problem .. LOL are you on a USB keyboard ? :lol: I had this SAME problem, go into your BIOS turn on legacy USB. Goto your Kernel options enable USB support (Disabled by default ARFH!) .. Redo it presto. :shock: :o