From: Hanspeter Kunz <hkunz@ifi.unizh.ch>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.6.1-mm4/5 dies booting on an Athlon64
Date: Thu, 22 Jan 2004 12:41:04 +0100 [thread overview]
Message-ID: <1074771664.2638.49.camel@septumania> (raw)
In-Reply-To: <400FAA7D.1010807@freemail.hu>
Just an idea: I had similar problems in 2.6.1-mm4.
I had to disable PNP bios support.
cheers,
Hp.
On Thu, 2004-01-22 at 11:48, Boszormenyi Zoltan wrote:
> Hi,
>
> > Boszormenyi Zoltan writes:
> > > Hi,
> > >
> > > mainboard is MSI K8T Neo, Athlon64 3200+.
> > > It does not boot successfully without the "nolapic"
> > > option. "noapic" does not make any difference, "nolapic" does.
> > > Kernel is compiled on a 32bit Fedora,
> > > K7/Athlon and Hammer/Opteron/Athlon64
> > > are selected under CPU support.
> >
> > 1. "does not boot successfully" is extremely vague.
> > Please supply a boot log or decoded kernel oops.
>
> Uncompressing kernel... and then nothing. Even the screen is emptied,
> cursor blinks in column 0 of line approx. 8, at about 1/3 of the screen.
>
> > 2. Does this also occur with 2.6.1 or 2.6.2-rc1?
> > If so, what was the last standard 2.6 kernel that worked?
> > 3. Does 2.4.25-pre6 work?
>
> I will try these. FC1 2.4.22-2149 definitely works.
>
> > 4. Try a minimal .config w/o any non-essential features.
> > (Where non-essential mean anything not needed to boot
> > and get to a login prompt.)
>
> OK.
--
Hanspeter Kunz
Artificial Intelligence Lab
Dept. of Information Technology
University of Zurich
+41 1 635 43 06 work
+41 1 635 68 09 fax
www.ifi.unizh.ch/~hkunz
next prev parent reply other threads:[~2004-01-22 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 10:48 Boszormenyi Zoltan
2004-01-22 11:41 ` Hanspeter Kunz [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 8:24 Boszormenyi Zoltan
2004-01-22 10:33 ` Mikael Pettersson
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=1074771664.2638.49.camel@septumania \
--to=hkunz@ifi.unizh.ch \
--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
all inboxes | Powered by JetHome®