Re: [gentoo-user] changed motherboard, no AHCI

[Dale <rdalek1967@gmail.com>]

Philip Webb wrote:
> My motherboard went on the blink earlier this week.
> I've now successfully installed a new one,
> but now can't get the kernel to find the SATA hard disk ("803 etc").
> 
> The problem seems to be that the kernel has AHCI enabled,
> which was necessary for the old mobo,
> but the new one's BIOS doesn't have an option to select AHCI.
> The Ubuntu + Mandriva partitions start properly, as does System Rescue,
> so the problem has to be in the Gentoo kernel configuration.
> 
> (1) Can I simply drop AHCI from the kernel or do I need to do something else ?
> (2) Can I recompile the kernel without going thro' a partial re-install
> or do I need to do a change-root etc to get it to work ?
> 
> Can anyone advise ?
> 


If you need to rebuild the kernel, try this.  Boot into you other
distro, Mandrive or Ubuntu should work fine.  You just need the chroot
command.  Mount the Gentoo partitions just like you would during the
install.  Just mount them tho, NO file system or disk formatting stuff.
 ;-)  Once mounted, just follow the chroot instructions just like in the
install.  These are the current ones:

cd /
mount -t proc proc /mnt/gentoo/proc
mount --rbind /dev /mnt/gentoo/dev
cp -L /etc/resolv.conf /mnt/gentoo/etc/
chroot /mnt/gentoo /bin/bash
env-update && source /etc/profile

Once you are in there, cd to /usr/src/linux and make the needed changes,
recompile, copy the new kernel over, edit grub.conf if needed and then
reverse things so you can reboot.  Don't forget to run env-update just
before exiting.  Also, I sometimes have trouble unmounting some
partitions.  Just unmount all you can before you reboot.  I usually
can't get the dev and root ones unmounted.  It appears that something
gets busy and can't be stopped.  Your mileage may vary tho.

You should be able to reboot Gentoo and hopefully the new kernel will
work.  Also, check into options you can add to the grub line when
booting.  Remember, you can edit grub and change the boot process.  I'm
assuming you are using grub instead of lilo.

Hope that helps.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"