From: jury gerold <geroldj@grips.com>
To: Gerbrand van der Zouw <g.vanderzouw@chello.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon/MSI mobo combo broken?
Date: Wed, 08 Aug 2001 19:08:48 +0200 [thread overview]
Message-ID: <3B717220.8050308@grips.com> (raw)
In-Reply-To: <20010723180201.A10557@convergence.de> <20010723183204.B27310@lightning.swansea.linux.org.uk> <3B6071F8.5090104@chello.nl>
If you have PC100 SDRAM try to replace it with PC133.
This worked for my motherboard. (Gigabyte GA-7ZXR, VIA-KT133A, Athlon
1.1MHz)
Cheers too
Gerold
Gerbrand van der Zouw wrote:
> Hi,
>
> Alan Cox wrote:
>
>> I'd be interested to know if 2.4.6-ac5 Athlon optimised works on your
>> board.
>> The reason for this is that it contains the official VIA fixes for
>> their IDE
>> corruption problem rather than our own.
>
>
> I have a MSI K7T Turbo (MS-6330) mobo (VIA-KT133A chipset) and had a
> go with the 2.4.6-ac5 kernel with Athlon optimisations on. The overall
> impression is that the combination is slightly more stable than
> kernels without the Southbridge fix. I.e. I now manage to boot in
> single user mode, however running anything as advanced as gcc is out
> of the question: oopses all over the place and also some complaints
> from the VM-system.
>
> I am in no way qualified enough to go hacking around in the kernel
> myself, but am quite willing to test any patches that might help
> towards solving the problem.
>
> Cheers,
>
> Gerbrand van der Zouw
>
next prev parent reply other threads:[~2001-08-08 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 16:02 Athlon/MSI mobo combo broken? Felix von Leitner
2001-07-23 17:32 ` Alan Cox
2001-07-23 22:05 ` Dan Hollis
2001-07-25 14:25 ` Miloslaw Smyk
2001-07-26 19:39 ` Gerbrand van der Zouw
2001-08-08 17:08 ` jury gerold [this message]
2001-08-08 21:08 ` Mark Hahn
2001-08-09 8:59 ` gjury
2001-08-09 14:55 ` Mike Frisch
-- strict thread matches above, loose matches on Subject: below --
2001-08-08 21:35 Manuel A. McLure
2001-08-08 22:14 ` Mike Frisch
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=3B717220.8050308@grips.com \
--to=geroldj@grips.com \
--cc=g.vanderzouw@chello.nl \
--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