From: Ruth Ivimey-Cook <ruth.ivimey-cook@ivimey.org>
To: jh@oobleck.astro.cornell.edu
Cc: solt@dns.toxicfilms.tv, linux-kernel@vger.kernel.org
Subject: Re: Via KT600 support?
Date: Wed, 12 Nov 2003 23:00:14 +0000 [thread overview]
Message-ID: <3FB2BB7E.7090905@ivimey.org> (raw)
In-Reply-To: <200311121509.hACF9HG20967@oobleck.astro.cornell.edu>
Joe Harrington wrote:
>Yes, thanks, I did that before I posted. The problem exists with both
>the original BIOS (1004) and the latest (1005).
>
>Is anyone aware of similar problems with other manufacturers' KT600
>boards that were fixed in recent BIOS updates? Perhaps Asus has a
>BIOS bug they haven't fixed yet.
>
>By the way, I also underclocked both the CPU and the memory as far
>down as they would go, just to check, and the problem persisted.
>
>
I have an A7V600 too, with a Athlon 2100+. I found that the 2.4 kernel
support (2.4.20 ... 22) was not up to it also, and switched to try the
2.6.0-t9 kernel; this has, so far, proved fairly stable, with the
exception of a might_sleep problem on the plug-in PCI IEEE1394 card I have.
I noticed that, with 2.4, the kernel was treating the KT600 chipset as a
KT400 chipset: I don't know if this has changed in later editions of
2.4, but it seemed to be an undesireable thing to do, which partly
prompted my shift to 2.6
I too tried updating the BIOS to 1005; it does seem to fix a power-up
problem (originally the BIOS would sometimes claim that a hardware fault
had happened which hadn't hapened) but there still seem to be issues
with the SATA ports: drives on them are never listed in the BIOS boot
sequence, and unless I do a cold-boot (i.e. cable-unplugged, not just
'off') the SATA drives aren't visible at all to the BIOS or to Linux.
One of these days I'll get around to filing a bug report about the SATA
stuff with ASUS. Should it make a difference, the drives I@m using are
Seagate 7200.7 120GB/8MB.
Regards,
Ruth
next prev parent reply other threads:[~2003-11-12 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 19:21 Via KT600 support? Joe Harrington
2003-11-12 9:19 ` Maciej Soltysiak
2003-11-12 15:09 ` Joe Harrington
2003-11-12 23:00 ` Ruth Ivimey-Cook [this message]
2003-11-13 7:56 ` Stefan Smietanowski
2003-11-14 0:09 ` Kristian Lyngstøl
-- strict thread matches above, loose matches on Subject: below --
2003-11-12 17:13 Cory Bell
2003-11-12 23:12 ` Joe Harrington
2003-11-13 8:02 ` Stefan Smietanowski
2003-11-13 8:16 ` Stefan Smietanowski
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=3FB2BB7E.7090905@ivimey.org \
--to=ruth.ivimey-cook@ivimey.org \
--cc=jh@oobleck.astro.cornell.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=solt@dns.toxicfilms.tv \
/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