From: Randy Dunlap <rdunlap@xenotime.net>
To: Marc Perkel <marc@perkel.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Frustrated with Linux, Asus, and nVidia, and AMD
Date: Wed, 25 Oct 2006 13:45:16 -0700 [thread overview]
Message-ID: <20061025134516.7645d92b.rdunlap@xenotime.net> (raw)
In-Reply-To: <453FB661.3020607@perkel.com>
On Wed, 25 Oct 2006 12:09:21 -0700 Marc Perkel wrote:
>
>
> Andi Kleen wrote:
> > Marc Perkel <marc@perkel.com> writes:
> >
> >
> >> Ok - I had a bad day today struggling with hardware. Having said that
> >> I'm somewhat frustrated with the lack of progress of Linux getting it
> >> right with Asus, nVidia, and AMD processors right.
> >>
> >> I still have to run pci=nommconf to keep the server from locking
> >> up. That's with both 939 pin and AM2 motherboards.
> >>
> >> This bug remains unresolved:
> >>
> >> http://bugzilla.kernel.org/show_bug.cgi?id=6975
> >>
> >> So what's up with the no progress?
> >>
> >
> > The bug report only references ancient kernels (2.6.15, 2.6.17) How do you know there is no
> > progress?
> >
> > -Andi
> >
> As of the 2.6.18 released kernel I still had to modify the source code
> to keep the kernel from locking up on boot. I haven't tried it with
> 2.6.19rcx yet.
Have you posted your needed patches?
If so, please do it again.
---
~Randy
next prev parent reply other threads:[~2006-10-25 20:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 4:55 Marc Perkel
2006-10-25 9:56 ` Oleg Verych
2006-10-25 14:01 ` Lee Revell
2006-10-25 14:51 ` Gianluca Alberici
2006-10-25 18:57 ` Andi Kleen
2006-10-25 19:09 ` Marc Perkel
2006-10-25 20:45 ` Randy Dunlap [this message]
2006-10-26 18:05 ` Andi Kleen
2006-10-26 18:31 ` Marc Perkel
2006-10-26 18:42 ` Andi Kleen
2006-10-29 0:30 ` Bill Davidsen
[not found] <fa.nWSYbiDM13Z4b2OlxoSzmqud/lI@ifi.uio.no>
[not found] ` <fa.NxAEaSXPSQSEviWvGDBmTZn07UE@ifi.uio.no>
[not found] ` <fa.i/oIAoig46I/apLGccQ0BesB0W8@ifi.uio.no>
2006-10-29 4:49 ` Robert Hancock
2006-10-30 2:10 ` Bill Davidsen
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=20061025134516.7645d92b.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@perkel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®