NForce Chipset support in which kernels?
Was considering the purchase of a Asus A7N266-VM AA with the following chipsets. What kernel is needed to support all features? (onboard video/audio/nic)?
Thanks.
North Bridge
Chipset Name:
nForce 220D Manufacturer: nVidia AGP FSB: 4X (Build-In) CPU Type: AMD Athlon XP and Duron CPU FSB: 200/266 Memory Type: DDR Memory FSB: DDR 200/266 Max Memory: N/A
Sourth Bridge
Chipset Name:
nForce MCP-D
Manufacturer:
nVidia Number Of USB: 6 Version Of USB: 1.1 Support IDE Data: ATA 33/66/100 AMR/CNR/ACR* : CNR/ACR
Quoted 3 lines · Hanasaki JiJi
Was considering the purchase of a Asus A7N266-VM AA with the following
chipsets. What kernel is needed to support all features? (onboard
video/audio/nic)?
AGP isnt supported
IDE is vaguely supported as of 2.4.21pre Audio is partially supported (no audio accelerator) NIC is not supported (no docs)
Its very much a 'winputer'
Unless you get the drivers from nVIDIA website.
Quoted 17 lines · Hanasaki JiJi
Quoted 3 lines
Was considering the purchase of a Asus A7N266-VM AA with the following
chipsets. What kernel is needed to support all features? (onboard
video/audio/nic)?AGP isnt supported
IDE is vaguely supported as of 2.4.21pre Audio is partially supported (no audio accelerator) NIC is not supported (no docs)Its very much a 'winputer'
-
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 1 line · Matthew D. Pitts
Unless you get the drivers from nVIDIA website.
Note that the nVidia NIC driver, at least, continues to have open reports of crashing net drivers that get reported to me :/ Since nVidia will not provide documentation, who knows if this will ever get fixed.
I would recommend sticking a 3rd party NIC in the board, and avoiding the nVidia on-board NIC like the plague.
It is also worth noting that many nForce boards come with 8139 on-board. I guess some board makers don't trust the nVidia NIC hardware either...
Jeff
Jeff,
Quoted 3 lines
It is also worth noting that many nForce boards come with 8139 on-board. I guess some board makers don't trust the nVidia NIC hardware either...
Some nForce 2 boards will ship with a 3Com nic chip that is inbeded in the system.
I'm using an ASUS A7N8X (nForce2 chipset) with linux-2.4.21-pre3-ac4 + the patch for the __free_pages_ok oops, Subject: "[patch] 2.4.21-pre3-ac oops". I also added the latest nForce drivers for both it's nic and audio, but they load with symbol mismatches. I am using the nVidia NIC with the nvnet driver. I haven't used sound yet as something isn't configured correctly yet, haven't tracked it down yet as that is low priority. The system just became stable with the oops patch. I have the 3Com NIC recognised, but not used. Sofar the nVidia NIC is transmitting and receiving fine. I transfered data to the system over the network in 100MBit full duplex mode on a switched network and it didn't hicup at all. The transfer saturated the network for a few hours so it got a good workout. The new copy md5sumed identicle to the original so there weren't hidden issues in the transfer. For the long term, who knows how it will hold up. I don't have any IEEE 1394, or serial IDE devices so they haven't been tested. I haven't used USB yet, but it is recognised. As of right now I'm doing testing for stability assesment and all looks good.
- Bryan
Quoted 7 lines
Quoted 3 lines
It is also worth noting that many nForce boards come with 8139 on-board. I guess some board makers don't trust the nVidia NIC hardware either...
Some nForce 2 boards will ship with a 3Com nic chip that is inbeded in the system.
Quoted 1 line · Matthew D. Pitts
Unless you get the drivers from nVIDIA website.
Which are binary only. So its still best avoided
Quoted 4 lines · Alan Cox
Quoted 1 line · Matthew D. Pitts
Unless you get the drivers from nVIDIA website.
Which are binary only. So its still best avoided
For someone with far too much time on their hands, the 20KB binary object (complete with symbols) shouldn't be too much work to reverse engineer 8)
Although Jeff seems to be think that the chip is a clone of another existing NIC, so it may not be worth the effort if $driver can be made to work with it by adding some IDs..
Dave
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 6 lines · Dave Jones
Quoted 4 lines · Alan Cox
Quoted 1 line · Matthew D. Pitts
Unless you get the drivers from nVIDIA website.
Which are binary only. So its still best avoided
Quoted 7 lines
For someone with far too much time on their hands, the 20KB binary object (complete with symbols) shouldn't be too much work to reverse engineer 8)
Although Jeff seems to be think that the chip is a clone of another existing NIC, so it may not be worth the effort if $driver can be made to work with it by adding some IDs..
Well, the IDE part in nForce certainly is a clone of another IDE, so it's likely the NIC is as well. An idea comes to mind which one it could be ...
Signature · 2 lines
Vojtech Pavlik SuSE Labs
Quoted 4 lines · Vojtech Pavlik
Well, the IDE part in nForce certainly is a clone of another IDE, so it's likely the NIC is as well. An idea comes to mind which one it could be ...
For more nvidia nforce speculations have a look at:
http://sourceforge.net/mailarchive/message.php?msg_id=2947226
Signature · 1 line
Anders Gustafsson - [email protected] - http://0x63.nu/