Joey Hess wrote: > Scarletdown wrote: >> initrd /boot/initrd.img-2.6.32-3-486 >> [Linux-initrd @ 0x10b3000, 0x76cdf9 bytes] >> >> After that, she's locked up tight, and all I can do is power off. >> >> This is obviously a problem with initrd. Set too large for such a low >> memory system perhaps? > > I doubt it, since your initrd is only 7 mb. > > This seems more likely to be a problem with your bootloader. Quite > possibly grub is not configured to read the initrd from the correct disk > device. It can be hard to get that right when preparing an disk image on > another machine. > > Or possibly, given the age of the hardware, the initrd is not located > near enough to the front of the drive for grub to be able to access it. > (Which is why having a separate /boot partition first used to be a good > idea.) >
I would take a live-cd or usb disk (there are images available). Avoid using gnome or kde - your system wont make it. I've had always problems with initrd when not installing from cd. But I'm good in debugging it. I.e. you should edit /etc/modules and put the disk relevant modules there and recreate the initrd image. This is happening when you install different kernel after basic install. Or if you install with debootstrap and swap the drives. You could actually easy debug it if you add the kernel option init=/bin/sh and then check what's wrong. I.e. wrong disk drives or not loaded or not available modules. regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hqs72f$9e...@dough.gmane.org
