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 Aubrey Li : > On Thu, Sep 18, 2008 at 8:53 AM, chenlu chen - Sun Microsystems - > Beijing China <[EMAIL PROTECTED]> wrote: >> Hi Aubrey, >> >> This is because the device id of 0x10be is changed to 0x10f5 since e1000g >> Ver 5.2.8 (CR6687947.). >> So this is not a bug of e1000g. >> >> Because of some reasons Intel has decided to retire id 10be entirely and >> 0x10f5 is the correct one. >> But some systems did go out into the world with the 10be device id. >> E1000g driver since 5.2.8 will not work on this chip 0x10be. >> As Intel's suggestion, the right thing to do is upgrading the NVM image. >> >> Milan, >> Thank you for forwarding this mail. >> >> Thanks >> Chenlu >> > That is probably not the right way. > That means network will be missed on some systems. > You know, on ACPI related work, we are keeping fix weird > BIOS bug to make solaris work on the more platforms. I guess it's not > difficult for e1000 driver to support this device id, right? I > personally strongly > suggest e1000 driver support this device id, otherwise I have to buy a new > network card, :-) You know, updating NVM image is painful for the common > users. > > Thanks, > -Aubrey _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
