linux-kernel - Re: Frustrated with Linux, Asus, and nVidia, and AMD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061025134516.7645d92b.rdunlap@xenotime.net>
Date:	Wed, 25 Oct 2006 13:45:16 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Marc Perkel <marc@...kel.com>
Cc:	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: Frustrated with Linux, Asus, and nVidia, and AMD

On Wed, 25 Oct 2006 12:09:21 -0700 Marc Perkel wrote:

> 
> 
> Andi Kleen wrote:
> > Marc Perkel <marc@...kel.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/