From: Jesse Allen <the3dfxdude@hotmail.com>
To: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
Cc: B.Zolnierkiewicz@elka.pw.edu.pl, linux-kernel@vger.kernel.org
Subject: Re: nforce2 bios fix
Date: Mon, 19 Jan 2004 20:07:35 -0700 [thread overview]
Message-ID: <20040120030735.GA764@tesore.local> (raw)
In-Reply-To: <40092D69.3070005@gmx.de>
On Sat, Jan 17, 2004 at 01:41:13PM +0100, Prakash K. Cheemplavam wrote:
> [from Bart]
> If BIOS upgrade helped please send 'lspci -vvv -xxx' output from system
> after/before BIOS upgrade, so we can try to catch the problem and add a fix
> to kernel (there is no BIOS update for some motherboards).
>
>
> Can't you try above?
>
> Prakash
OK I flashed back and got both. The message you refer to is at:
http://marc.theaimsgroup.com/?l=linux-kernel&m=107434138423359&w=2
The other guy has an a7n8x. Remember that I have a Shuttle AN35N and the BIOS
as of 12-5-2003 fixes the lockup. The change log for this BIOS even includes
the related "Add C1 disconnect option". I'm still running the pre-Dec-5 BIOS
so if there is anything else to try I can do it now.
Jesse
parent reply other threads:[~2004-01-20 3:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <40092D69.3070005@gmx.de>]
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=20040120030735.GA764@tesore.local \
--to=the3dfxdude@hotmail.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=PrakashKC@gmx.de \
--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