On Wed, 15 Mar 2006, Manuel Bilderbeek wrote: > Hi, resending because of wrong address.
thanks sorry for the typo > 2006/3/15, maximilian attems <[EMAIL PROTECTED]>: > > do you use lilo? > > Yes I do. ok so that's the bug you hit, it's closed by 0.55b lilo doesn't grog that the initd.img changed without beeing rerun grub is much friendlier in those regards. > > if yes fetch 0.55 from incoming.debian.org or unstable. > > But, will it be able to update my initrd.img via the chroot? > As you have read, I'm having loads of trouble with that. yes you need a) proc from outside the chroot or maybe it's enough from inside mount /proc /chroot/proc -t proc b) the devices from inside the chroot /etc/init.d/udev start now run lilo > > did you get dropped to a shell, > > No, I got a system freeze. yes because of the lilo bug. > > i would need the last 2 lines above RAMDISK, what's there? > > I can check again, but AFAIK it is something about ACPI or so. I can > check again, but rebooting takes a lot of time. don't need this as the bug itself is nailed. > > which busybox are your running? > > dpkg -l busybox > > I only did this via the chroot from the Knoppix cd. > > But I have 1.01-4 if you want to know. ok good. > I have no idea how to get my system running again... :((( if lilo doesn't work out for you use from knoppix (adapt to your device) grub-install --root-directory=/mnt/hda1 /dev/hda again good luck -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
