Frustrated with Linux, Asus, and nVidia, and AMD
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?
Quoted 10 lines · Marc Perkel
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
Xref: news.gmane.org gmane.linux.kernel:460364
Archived-At: <http://permalink.gmane.org/gmane.linux.kernel/460364>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.
Please, read down this thread:
<http://article.gmane.org/gmane.linux.ports.x86-64.general/1794>
And this one may be relevant:
<http://permalink.gmane.org/gmane.linux.kernel/458769>
Maybe will give some clue about soft-"hardware".
Quoted 5 lines
This bug remains unresolved:
http://bugzilla.kernel.org/show_bug.cgi?id=6975
So what's up with the no progress?
If you are only one using that hardware and experiencing bugs, then you are on your own.
OTOH, many would help if more hardware information and erratas will be *actually published*.
____
Quoted 4 lines · Marc Perkel
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 don't know why you would buy a server from a vendor whose hardware is so closed they expect you to use a proprietary driver to have working sound, network, and video...
Lee
Marc,
2.6.16.11 works. I tell u because i got an M2E with 1GB ram on Athlon AM2 under test since a couple of week and it goes fine.
BUT notice: i boot from SATA, dont have any PATA disk.
Maybe u can use that waiting for the patch
Bye,
Gianluca
Quoted 17 lines · Marc Perkel
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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 4 lines · Marc Perkel
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.
Quoted 8 lines
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
Quoted 14 lines · Andi Kleen
Quoted 11 lines · Marc Perkel
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:
Quoted 8 lines
Quoted 2 lines
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.
Quoted 20 lines · On Wed, 25 Oct 2006 12:09:21 -0700 Marc Perkel wrote:
Quoted 17 lines · Andi Kleen
Quoted 13 lines · Marc Perkel
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?
Quoted 8 lines
Quoted 5 lines
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
Quoted 4 lines
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.
Modify in what way?
-Andi
Quoted 10 lines · Andi Kleen
Quoted 4 lines
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.
Modify in what way?
-Andi
skip_timer_override = 0
Quoted 10 lines · Marc Perkel
Quoted 7 lines · Andi Kleen
Quoted 3 lines
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.
Modify in what way?
-Andi
skip_timer_override= 0
Ah that problem. I'm still waiting for Nvidia to give us the required information to fix this properly.
-Andi
Quoted 9 lines · Andi Kleen
Quoted 7 lines · Marc Perkel
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.
Quoted 8 lines
Quoted 5 lines
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?
2.6.18 is the latest released kernel, I don't think calling one release back "ancient" is really advancing the solution. The problem seems to have been reported in August, and is still not fixed, I do understand that he would feel there is no progress.
How long will you wait before putting in the fix Marc Perkel suggested, perhaps with a warning logged that it's a band-aid? Many users will not be astute enough to find this discussion, the bug report, the fix, configure and build a kernel, etc. And not all distributions will address it either.
Signature · 5 lines
Bill Davidsen <[email protected]> Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a normal user and is setuid root, with the "vi" line edit mode selected, and the character set is "big5," an off-by-one errors occurs during wildcard (glob) expansion.