Hi I have an Abit Nforce 2 -S revision 2.0 motherboard. It has 2 on board Serial ATA slots
which I am not using. However I seem to have a weird issue with lilo in gentoo. Before we start though, debates about lilo v's grub probably aren't very helpful, lilo is what I am working with at this time, so it would be cool to just address that.
Anyhoo the thing is I installed a clean copy of gentoo. Unfortunately I forgot to include driver support for my Nvidia onboard network card in the kernel compile, so I decided to reboot with the live CD and download the latest kernel sources and use those. (I guess what I should have don'e is just compile the kernel I had again, but I changed my mind and decided I wanted a 2.6 kernel instead - and that this was the quickest way to do it).
Well anyway, the thing is that I downloaded and compiled my new kernel via chroot from the Gentoo live CD and I configured lilo config as per the Gentoo docs, as follows:
Code:
boot=/dev/hda
prompt
timeout=50
default=gentoo
vga=788
image=/boot/kernel-2.6.7-r10
label=gentoo
read-only
root=/dev/hda3
other=/dev/hda1
label=windows
As you can see from this I have my harddisk (my only one) on the primkary master IDE channel and it is divided into three partitions, hda1, hda2 and hda3.
However when I run lilo to confirm my partition selection, I get an error message saying
Code:
Fatal: raid_setup: stat("/dev/hda")
Unfortunately I have no idea what this means. I am not using raid, I only have a single hard drive on the IDE bus - and the above lilo configuration is to the best of my knowledge accurate.
My drive configuration is as follows:
IDE 1
Primary Master: Maxtor 200GB 7200RPM HDD.
Primary Slave: empty
IDE 2
Secondary Master: Empty
Secondary Slave: Empty
SATA1: Empty
SATA2: Empty.
So you see it is really a very simple setup.
There are a couple of possible issues I can think of here. The first is that the SATA on this motherboard is confusing the hell out of lilo and it thinks I am trying to configure it for a raid setup.
Two I am doing this via chroot, so maybe somehow that is a factor.
But beyond that I'm stuck.
The problem is, now I'm in chroot and now I have compiled my kernel and overwitten my old lilo.conf, I won't be able to boot my new kernel (or anything) until I can get lilo to play ball.
Does anyone have any clue what is going on here?
If you do, your input would be very much appreciated.
Kind regards,
GJ
