> I've got a machine with an nForce3 250 chipset. The > Ethernet controller isn't seen on install by either > Sol10 03/05 or Nevada b.24
"NForce3 250" or "NForce3 250 Gb"? The difference is that the "Gb" chipset does Gigabit ethernet and works just fine with the nge driver in Nevada. If it isn't the "Gb" version, then the nge will still see it, but the driver doesn't work, or at least didn't work with Nevada b23. If it is the "Gb" version, then it does work fine once you make the alias point to the nge driver properly. I've blogged about it a few times, http://blogs.sun.com/relling > I follow the instructions in the HCL (download the > driver from SysKonnect, add to machine, run > "update_drv -a -i "pci1297,c231" skge...) > But still no luck. I know the ethernet card works > under Windows, and while I can't be sure that > prntconf -v show it (I have several entries with > "driver not attached" in the output there), I know > that scanpci (called from /usr/X11/bin/scanpci) shows > that I have what it calls an "nVidia ethernet > controller" at a specific PCI slot #. > > My guess is that the cryptic message "driver loaded > but could not attach" that I get when installing the > sysconnect driver means something along the lines of > "can't find the address of the specific card this > driver goes to on any known local bus". How close am > I with that? skge is definitely the wrong driver, hence the "could not attach" message. Note: the Sun X2100 server and Ultra-20 workstation use the NForce4 chipset and the nge driver for the builtin GbE. This driver is developed by NVidia and is not open sourced, so you might pester them about support for the older, slower MCP networks. IMHO, the driver is pretty close to working, so it might just need a little tweek. -- richard This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
