Yes, I ran lilo (several times). As I indicated, lilo runs
correctly and starts loading the kernel before the kernel load
halts. I understand from my reading that if there is an error in
lilo running, I would see only L, LI, or LIL on the screen. Since
I get LILO loading KERNEL ....., I infer that LILO is finished and
the kernel is loading.
What is the minimum set of files that need to be accessible for a
kernel to load and boot?
Al
Joachim Fahnenmueller wrote:
>
> Did you remember to run lilo after making changes in /boot?
>
> On Fri, Jan 04, 2002 at 08:14:46AM -0800, Albert Kinderman wrote:
> > I dual boot, using another boot manager to get to lilo on my
> > debian partition.
> >
> > Everything worked fine until two days ago, when I made a new
> > kernel using make-kpkg. I used dpkg to install the resulting .deb
> > and created a boot floppy as part of the installation. I also
> > stupidly tried to clean up some cruft from old kernels that was
> > lying around in /boot (LESSON: do not make two changes at one
> > time). Now I can boot from the boot floppy, but the boot from the
> > hard disk dies after
> >
> > LILO loading <label from lilo.conf> ......
> > s
> >
> > I tried to mount the boot floppy to see what it had that wasn't in
> > /boot, but mount kept giving me wrong fs or bad superblock errors.
> >
> > What should I try next?
> >
> > Al
> >
> > --
> > Albert Kinderman California State University, Northridge
> > Department of Systems and Operations Management
> >
> >
> > --
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> >
>
> --
> Joachim Fahnenmüller
> Lehrer für Mathematik und Physik
>
> Herder-Gymnasium
> Kattowitzer Straße 52
> 51065 Köln
--
Albert Kinderman California State University, Northridge
Department of Systems and Operations Management
