"Narins, Josh" <[EMAIL PROTECTED]> wrote:

> From: Timothy Braje, Sent: Sunday, February 23, 2003 6:16 PM
> 
>  I have been having some difficulty getting a newly compiled kernel 
> to work on my system.  I have successfully compiled and installed 
> before but this problem has stumped me.
> 
> Basically, I compile (using make-kpkg) and install the kernel.  When
> I try to boot it, though, the only things that are printed to 
> the screen 
> are:
>       Loading linux
>       Bios Check Successful
> (Though the screen flashes so fast, I am not sure if it fully 
> sure if it 
> writes the whole phrase).
> 
> I have successfully installed the stock 2.4.19 kernel image from 
> sarge without problem, so I figure that I must be doing something 
> wrong in the compile.
> 
> I have a P3, 600 MHz, Dell Inspiron 5000, running sarge (+gnome 
> 2.2 from unstable).
> 
> Any help would be greatly appreciated.  
> 
> Thanks
> 

Well, the gnome from unstable has nothing to do with it.

Although it is breaking so early, it's hard to guess what is.

The stock 2.4.19 also installed a /boot/config-2.4.19 file.

Compare that with your /usr/src/kernel-source-2.4.19/.config 

Although, since you are using sarge, aren't the source for 2.4.20 available?
You'd probably be better off using the even numbered release.

HTH


Thanks for the two responses.  I have some follow-up information:

I have tried the 2.4.20 kernel.  That doesn't work either.  It fails in the
same way.  I don't think I was very clear on the details fo the failure.  When
the kernel tries to boot, it gets to the "Bios check successful" message and
then the screen goes black.  It then proceeds to alternate between a dark
black and a lighter black with a refresh rate of about 1 second.

I will try the config file from the debian stock kernel and see if that
works.

Could this be a compiler problem?  If so, how would I figure out if it is?

Thanks,

Tim


____________________________________________________________________
   

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to