2009/3/27 Holger Levsen <hol...@layer-acht.org>: > Hi Eddy, > > On Freitag, 27. März 2009, Eddy Petrișor wrote: >> I agree this was user error. Still, recovering from it should be possible. >> That's what the BR is about. > > Well, the problem seems to be that your kernel was installed incorrectly... > >> How is it user error when I try to update the initramfs and rerun lilo from >> the rescue environment? I *wasn't* manually assigning that major number, >> nor did I pass "root=fd00" in lilo.conf. > > I assume the user error was in the way the initrd was updated, you did that > manually...
update-initrd -u -k 2.6.28-1-686 >> I'll try to reproduce the issue today when I get to work, now that I know >> how to fix it (and have a backup initrd with the hack). > > Cool. I reproduced this with both the Ubuntu 8.04 Install CD in repair mode and with Debian Lenny's install CD. In both cases the hack I made was used (I added some huge warning sign when is used) after updating the initrd in the repair environment. In the light of what Bastian said, I would like to know if lilo adds the device numbers somehow during its run since the /proc/cmdline contains 'root=fd00' and there's no append line which adds root= (except my new hacked backup entry). If it does, then this entire behaviour is explained. -- Regards, EddyP ============================================= "Imagination is more important than knowledge" A.Einstein -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
