From: Erik Mouw <erik@harddisk-recovery.com>
To: Cesar Eduardo Barros <cesarb@nitnet.com.br>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 1284] New: Asus P5AB broken BIOS reading ESCD
Date: Tue, 30 Sep 2003 11:18:36 +0200 [thread overview]
Message-ID: <20030930091836.GA31527@bitwizard.nl> (raw)
In-Reply-To: <20030929222218.GE27908@flower.home.cesarb.net>
On Mon, Sep 29, 2003 at 07:22:18PM -0300, Cesar Eduardo Barros wrote:
> On Mon, Sep 29, 2003 at 07:41:27PM +0200, Erik Mouw wrote:
> > FWIW: I used to have a similar board (Asus P5A, it actually died a week
> > ago, so I can't check anything anymore). Never tried 2.6 on it, but I
> > know it had a flakey PnPBIOS implementation: if you put in a Sound
> > Blaster AWE64 Gold, you couldn't use the floppy drive anymore. The
> > latest "Y2K compliant" BIOS (revision 1.005 IIRC) fixed that, it might
> > also fix this particular bug.
> >
>
> The latest BIOS (a beta one) still has the same problem. Also, it breaks
> the main timer (for instance, vmstat 1 takes 2-3 seconds between lines,
> and the kernel complains about a broken TSC on boot).
As far as I remember I didn't try the beta BIOS, the latest stable one
fixed my problems with the Sound Blaster and the floppy drive. I only
used the board with 2.4 (last kernel I ran was 2.4.20-rmap15i) and that
worked OK. If that still doesn't solve your problem, I agree the BIOS
has to be blacklisted so we can work around it.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
| Data lost?!
| Stay calm and contact Harddisk-recovery.com!
prev parent reply other threads:[~2003-09-30 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 15:50 [Bug 1284] New: Asus P5AB broken BIOS reading ESCD Martin J. Bligh
2003-09-29 17:41 ` Erik Mouw
2003-09-29 17:59 ` Cesar Eduardo Barros
2003-09-29 22:22 ` Cesar Eduardo Barros
2003-09-30 9:18 ` Erik Mouw [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=20030930091836.GA31527@bitwizard.nl \
--to=erik@harddisk-recovery.com \
--cc=cesarb@nitnet.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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.