All of lore.kernel.org
 help / color / mirror / Atom feed
From: dek_ml@konerding.com
To: john slee <indigoid@higherplane.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: test10 dies very early in boot
Date: Wed, 01 Nov 2000 18:11:37 -0800	[thread overview]
Message-ID: <200011020211.SAA14543@konerding.com> (raw)
In-Reply-To: Your message of "Wed, 01 Nov 2000 20:00:36 +1100." <20001101200036.D655@higherplane.net>

john slee writes:
>hardware:
>	*	abit be6-2 mainboard
>	*	533 celeron (not overclocked)
>	*	192mb sdram
>	* 	seagate 20gb ide disk (not on ata66 port)
>
>compiler: gcc version 2.95.2 20000220 (Debian GNU/Linux)
>
>it gets as far as uncompressing the kernel and trying to boot it.  no
>further.  (doesn't get as far as displaying the 'Linux version ...'
>message).  sysrq doesn't work (not suprising),  ctrl-alt-delete doesn't
>work either.  reset button does work :-)


Um, I had the same problem with the kernel when I first downloaded it to try it out.
I was stumped for a while, turning of a number of features in the kernel,
before I figured it out.  You need to switch the processor type the kernel is compiled
for from "P-III"  to whatever is apropriate for your Celeron (I used a P-II, which
is basically the same instruction set as Celeron in Linux's view).

I didn't look at the source, but I bet early on the kernel tries to execute a P-III
instruction when compiled for P-III, and the P-II or Celeron gets confused and shuts down.

Once I compiled with P-II, kernel booted A-OK to multiuser :-)

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

      reply	other threads:[~2000-11-02  2:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-01  9:00 test10 dies very early in boot john slee
2000-11-02  2:11 ` dek_ml [this message]

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=200011020211.SAA14543@konerding.com \
    --to=dek_ml@konerding.com \
    --cc=indigoid@higherplane.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.