Hello,
I just recently upgraded the hard drive on my Debian machine (an intel box
running potato), and while everything copied successfully, I could not get
the new hard disk to boot. I then changed my lilo.conf to point to
/boot/vmlinuz-2.2.14 instead of the symlink at /vmlinuz, and
everythinig
Hello,
I just recently upgraded the hard drive on my Debian machine (an intel box
running potato), and while everything copied successfully, I could not get
the new hard disk to boot. I then changed my lilo.conf to point to
/boot/vmlinuz-2.2.14 instead of the symlink at /vmlinuz, and
everythinig
Actually, come to think of it, even though the new drive wouldn't boot at
first, it still got as far as Loading Linux, so I guess it might not be
a lilo problem after all. The boot process got to Loading Linux, but
not to Uncompressing Linux. Changing the image= in my lilo.conf from
/vmlinuz to
On 19 May 2000, Karl M. Hegbloom wrote:
Had you run `lilo' on the new drive before you tried to reboot? If
not, then what it was is that the kernel isn't at the same block
address as it was on the other disk...
Yes, I followed the instructions at
4 matches
Mail list logo
