From: Roberto Sanchez <rcsanchez97@yahoo.es>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.6.0-testX show stoppers
Date: Tue, 09 Dec 2003 00:52:48 -0500 [thread overview]
Message-ID: <3FD56330.6040506@yahoo.es> (raw)
In-Reply-To: <3FD4B250.8010402@nishanet.com>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
Bob wrote:
> Craig Bradney wrote:
>
>> For the Athlon, keep in touch with the nforce thread on here.. There are
>> patches due to timing issues with the nforce chipset.
>> For me, so far, just using this one works:
>> http://www.kernel.org/pub/linux/kernel/people/bart/2.6.0-test11-bart1/broken-out/nforce2-apic.patch
[SNIP]
> The patch works for a lot of people. I've seen those drive
> errors, irq7 disabled, spurious 8259a messages with a
> bios and acpi and apic and lapic and linux acpi handling
> conflict usually related to nforce2 and amd cpu's are
> usually involved.
>
> My nforce2 amd system got to working with apic and lapic
> and acpi when I did a bios flash update.
I also tried flashing the BIOS, but that was a complete disaster.
I have a BioStar motherboard (M7NCD Pro), and when I flashed to the 1007
BIOS, I started getting segfaults during init, was unable to log in most
times, and the machine was generally unusable.
When I reflashed to the (old) 0630 BIOS, the above patch worked its
magic.
Incidentally, everyone should stay away from the 1007 BIOS for the
M7NCD Pro.
-Roberto
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2003-12-09 5:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 15:28 Kernel 2.6.0-testX show stoppers Roberto Sanchez
2003-12-08 15:40 ` Craig Bradney
2003-12-08 15:45 ` Roberto Sanchez
2003-12-08 17:18 ` Bob
2003-12-09 5:52 ` Roberto Sanchez [this message]
2003-12-09 5:48 ` Roberto Sanchez
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=3FD56330.6040506@yahoo.es \
--to=rcsanchez97@yahoo.es \
--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.