From: Mattias Nordstrom <matta@ftlight.net>
To: linux-kernel@vger.kernel.org
Subject: Asus A7V133 BIOS Update fixed kernel crash
Date: Tue, 26 Mar 2002 15:17:09 +0200 [thread overview]
Message-ID: <3CA074D5.5080902@ftlight.net> (raw)
Hi,
I just thought I should share this with the kernel developer community.
When I was running my system (AMD Athlon XP 1700+ with Asus A7V133-C)
with the default BIOS on the motherboard (1007) I experienced several
problems when trying to run programs. Most of them either Segfaulted or
caused a bus error. The crashes where usually related to situations
where a program tried to display an animation or a video. Sometimes the
system completely froze. I tried to compile the kernel with all kinds of
different options, tried with and without athlon optimization but
nothing seemed to work. I thought it might have been related to the
"Athlon/AGP bug", but the solutions to fix the bug did not work for my
system.
Then one day I happened to check Asus homepage and found a BIOS update
for my motherboard. I flashed my BIOS with the new software (1008) and
now I haven't had any problems. The BIOS came out 8.3.2002, so it's
quite new. Anyone happen to know what changes where made in the new BIOS
which solved my problem?
--
Mattias Nordström
matta@ftlight.net
-www.ftlight.net-
reply other threads:[~2002-03-26 13:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CA074D5.5080902@ftlight.net \
--to=matta@ftlight.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.