Pixel wrote: >David Walluck <[EMAIL PROTECTED]> writes: > > > >>ddebug.log says nothing about why it fails, but then the bootloader fails too >>and the install is stuck in a loop. >> >>That is interesting because '/mnt/sbin/lilo -r /mnt' from the shell worked >>fine. >> >>The major bug is the install is not adding the 'initrd=' lines to >>'/etc/lilo.conf' (for any kernel!). Each kernel needs to use its own >>particular initrd in order for things to work correctly. >> >> > >no kidding! ;p >
Right, so it turned out mkinitrd worked, but was never added to lilo (since both mkinitrd and lilo portions of the install fail). One problem the install has is that I have two disks, '/dev/hda' and '/dev/hde'. '/dev/hda' is the first normal IDE disk, and '/dev/hde' is the first disk on the ATA100 controller, which is my boot drive. The install likes to try to use '/dev/hda' simply because it's the first drive, but the installation I was upgrading isn't even located on that drive. The installation resides on 'dev/hde'. > > > >>It should also take >>care not to use the '/boot/initrd.img' symlink, since this is only good for a >>particular kernel. >> >> > >i don't understand what's happening. Can you please send me the >ddebug.log? or better /root/drakx/report.bug.gz > > > The ddebug is 'tail'-ed during the install, right? I can't seem to find the messages in it that I saw on the console, but I will send you both. You will notice there are '/boot/initrd.img' everywhere in 'lilo.conf', but after the install the lines are gone. Both ways are incorrect. Then it says things like: 'renaming /boot//boot/initrd.img entry by /boot/initrd-2.4.19-8mdk.img' It looks like there's an extra '/boot/' there, but in any case these renamed entries never make it back to 'lilo.conf' >. > > > -- Sincerely, David Walluck <[EMAIL PROTECTED]>
