Sounds like this issue needs describing in the release notices.
Ted You wrote: > Hi Aubrey, > > The following is the original information from Intel: > > ---------------------- > A long time ago we produced a Windows driver that erroneously supported > device ID 0x10be, but as a device completely unrelated to ICH9. Since > it was an error, the use of id 10be was not recorded properly, so when > ICH9 did come along, the team at first assigned 10be to ICH9. > > When the multiple errors were discovered, we decided to retire id 10be > entirely and 0x10f5 is the correct one. Unfortunately, during the time > this was happening, some systems did go out into the world with the 10be > device id. > > If you encounter one of these systems (sounds like Sun has, somewhere) > the right thing to do is tell them to upgrade the NVM image. That is, > the flash non-volatile memory which contains our eeprom image and the > device ID. > ---------------------- > > I don't think we should support an incorrect device id in the e1000g > driver. I would still suggest you to update the NVM of the NIC to solve > this problem. Please contact Intel, they should be able to help you > update the image. And I'll also check what we can do to help you on > this. > > > Thanks, > Ted _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
