lkml.org 
[lkml]   [2000]   [Jul]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.4.0-test4 no boot?


My "dokernel" upgrade alias automatically runs lilo after putting
the kernel in /boot/vm.test, just so I won't forget.

Thus spake Michael Borrelli (mike@cc237069-b.brick1.nj.home.com):

> Coy A Hile said...
> > Robert L. Harris sez....
> > > I just compiled 2.4.0-test4. When I go to boot the box, I get
> > > "uncompressing kernel" and that's it.
> > >
> > > Thoughts?
> > >
> > > Robert
> >
> > I have the same problem. Has anyone else seen this?
>
> I've had this sort of thing happen to me when I didn't re-run lilo (or
> other boot loader) after doing make install, even if the kernel is in the
> same physical location. I assumed that it had something to do with the
> starting offset in the kernel changing, but this is just a wild stab by a
> newbie. (Why does this happen in reality?)
>
> Good luck!
> -mike



:wq!
---------------------------------------------------------------------------
Robert L. Harris | Micros~1 :
Senior System Engineer | For when quality, reliability
at RnD Consulting | and security just aren't
\_ that important!
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
FYI:
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:57    [W:0.091 / U:0.176 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site