> Yep, that's my next step. I'll possibly need to ask some 
> questions about
> how to do that at this point. I don't want to do a complete
> reinstallation just to do that, and I doubt I have to. Can I not just
> mount the installation CD and then somehow mount and build the kernel
> from what's already on my drive?
> 
> I've managed to reboot from the installation CD.The boot 
> sequence that I
> see when booting from the CD:
> 
> NFORCE2: IDE controller at PCI slot 00:09.0
> NFORCE2: chipset revision 162
> NFORCE2: not 100% native mode: will probe irqs later
>       ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
>       ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
> SiL3112 Serial-ATA: IDE controller at PCI slot 01:0b.0
> SiL3112 Serial-ATA: chipset revision 2
> SiL3112 Serial-ATA: not 100% native mode: will probe irqs later
>       ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
>       ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
> 
> At this point the machine happily goes on, finds all the drives on all
> the controllers and boots, but in my case the Serial-ATA stuff never
> shows up and the machine's hung.
> 
> I should (hopefully) know later this evening if genkernel is the
> culprit. As a starting point, if I can find the config file for the
> kernel on my Athlon-XP CD then I'll probably get a working box.
> 
> Now, what do I need to know about building a kernel by hand in the
> middle of the reboot and remount stuff I'm going through?

what kernel are you compiling anyway?? gentoo-sources I thought compiles exactly like 
the live-cd from what I hear. Have you tried that too?? My guess is your probably 
didn't compile that driver internally, and its not finding it in initrd..

compiling a kernel is make menuconfig;make dep;make clean;make bzImage;make 
modules;make modules_install..

I have never done the initrd thing on my own.. So someone else would have to help you 
do that. I compile anything I need to get root up, internally..

--
[EMAIL PROTECTED] mailing list

Reply via email to