mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pedro Soria Rodriguez <psoria@hispafuentes.com>
To: Linux Kernel Maillist <linux-kernel@vger.kernel.org>
Subject: Re: CRC errors decompressing kernel on boot
Date: 27 Mar 2003 11:15:41 +0100	[thread overview]
Message-ID: <1048760140.6984.11.camel@queen.pelusa.net> (raw)
In-Reply-To: <1047567911.3419.17.camel@queen.pelusa.net>

I ended up finding a solution to my problem myself, so I will post it
here for the record.
First, a summary of the problem I had with kernel 2.4.20-ac2 and
2.4.21-pre5-ac2 and Lilo 22.4:

On Thu, 2003-03-13 at 16:05, Pedro Soria Rodriguez wrote:
> I am getting a CRC error when the kernel is being decompressed after
> loading.  It is intermitent, but I can force it to occur on every boot
> if I type on the keyboard while the kernel is loaded (before being 
> decompressed). 
> It happens on a certain machine, 
> with USB keyboard, and not with a PS2 keyboard.
> It does not happen on other machines with USB or PS2 keyboards.

The problem turned out to be a combination of LILO and an apparently
buggy BIOS. 

I switched from using LILO to using GRUB as a boot loader, and the
problem went away.  I found that loading a kernel with SYSLINUX (from
CDROM), LoadLin (from DOS), PXE (over the net) all works fine.  It is
only when loading it with LILO when the CRC error appears.  I read
somewhere on the net that the problem may be related to a buggy BIOS in
the machine.   

The problem was the USB keyb + buggy BIOS + LILO + large kernel    
(apparently this does not happen on small kernels, as I read somewhere
else on the net).

cheers,

--
Pedro Soria-Rodríguez



  reply	other threads:[~2003-03-27 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13 15:05 Pedro Soria Rodriguez
2003-03-27 10:15 ` Pedro Soria Rodriguez [this message]
2003-03-27 10:48   ` Martin Schlemmer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1048760140.6984.11.camel@queen.pelusa.net \
    --to=psoria@hispafuentes.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome