Quoting Peter Hardy <[EMAIL PROTECTED]>:
Thanks Peter!
> It's not telling you it's using devfs. That's the kernel trying to find
> an initrd image, and not being able to. It can't boot any further
> because the modules it needs to mount the root partition are in the
> initrd image. :-)
Oops!
> A default debian installation has a line like
> initrd = /initrd.img
>
> in lilo.conf. Like the /vmlinuz files, /initrd.img is then a symlink to
> /boot/initrd.img-kernel-version . Do you have an initrd line in
> lilo.conf, and does it point to a valid initrd image?
I haven't been using the Debian default ones so that I can try multiple kernels
at a time.
My lilo.conf points straight to the initrd image (which is still there) so I
don't know it can't find it?!
There was a message after upgrading that kept saying that I neede to reboot ASAP
so I didn't think to check lilo etc before doing it :-(
My lilo.conf is:
# Global Variables
boot=/dev/hda
root=/dev/hda5
bitmap=/boot/sid.bmp
bmp-colors=1,,0,2,,0
bmp-table=120p,173p,1,15,17
bmp-timer=254p,432p,1,0,0
install=/boot/boot.b
map=/boot/map
vga=normal
lba32
compact
prompt
delay = 20
timeout = 100
default = Debian-2.4x
image=/boot/vmlinuz-2.4.25-1-686
label=Debian-2.4x
optional
read-only
initrd=/boot/initrd.img-2.4.25-1-686
append="hdc=ide-scsi apm=on apm=power-off acpi=off"
--
Simon Wong <[EMAIL PROTECTED]>
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
