From: Seth Goldberg <bergsoft@home.com>
To: Gordon Sadler <gbsadler1@lcisp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.5pre1 will not boot
Date: Fri, 04 May 2001 20:05:14 -0700 [thread overview]
Message-ID: <3AF36DEA.86330307@home.com> (raw)
In-Reply-To: <20010504215535.A25868@debian-home.lcisp.com>
Gordon Sadler wrote:
>
> On Fri, May 04, 2001 at 01:28:23AM -0700, Seth Goldberg wrote:Seth Goldberg <bergsoft@home.com>
> > Gordon Sadler wrote:
> > >
> > > On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote:
> > > > Hi,
> > Hi,
> >
> > Have you tried compiling ther kernel with Athlon optimiztions turned
> I've seen some others reporting some success with K6-II[I] or
> Pentium-II[I] configurations. I haven't tried it here as 2.2.19 is
> running fine for me. -) I just keep trying the new 2.4.x and reporting
> here with hopes someone will find the problem and be able to resolve it.
> There could very well be something wrong with my/our hardware. I'm at a
> loss as to why none of the developers can reproduce this? Is it possible
> none of the 'core' developers have/have access to this hardware? It
> isn't all that unusual I think.
Yep. I think it's just the fact that the KT133A chipset is so new
that
very few people have it. And of the people who have it, I think a great
majority are running on distributions of Linux whose kernels are
NOT athlon optimized.
I'd like to ask everyone who has a KT133A to please try a 2.4.x kernel
with Athlon optimizations and let us know what percentage are displaying
this problem.
Thank you!
--Seth
prev parent reply other threads:[~2001-05-05 3:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 7:12 PROBLEM: 2.4.5pre1 will not boot Gordon Sadler
2001-05-04 7:43 ` Seth Goldberg
2001-05-04 8:01 ` Gordon Sadler
2001-05-04 8:28 ` Seth Goldberg
2001-05-05 2:55 ` Gordon Sadler
2001-05-05 3:05 ` Seth Goldberg [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=3AF36DEA.86330307@home.com \
--to=bergsoft@home.com \
--cc=gbsadler1@lcisp.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 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.