On Sunday 29 November 2009 03:07:14 BRM wrote: > > If not, fixing it is quite trivially easy: Get a copy of any recent > > liveCD or rescue image that you can boot, and boot into it. It will find > > your drives using whatever conventions it uses, and let you mount your > > gentoo partitions just like you would do with installs. chroot lets you > > test stuff and you can also use the compiler on the rescue disk to build > > a new kernel and store it in /boot > > Then boot into that new kernel, everything ought to start properly, and > > immediately rebuild that kernel using your gentoo system compiler. Along > > the way you might have to edit your fstab to use sda devices instead of > > hda ones. > > Thanks! That seems to be a good plan. I built it earlier, but for some > reason grub won't boot it - perhaps b/c I gzip compress the kernel (kernel > option)? Not sure. Going to figure it out though. >
More likely you got the chipset drivers wrong. There's been a lot of changes in that area over the past 18 months or so. gzip is the default compression for the kernel, I can't think of any reason why a kernel cannot decompress itself. As a side note: I always keep a rescue USB disk handy in my box of tricks. I use RIPLinux (there are many alternatives) as it supports all imaginable disk hardware, plus software raid, lvm and who knows what else. I keep it up to date with latest current version, this little gadget has saved many a machine from a reinstall and data loss. -- alan dot mckinnon at gmail dot com
