[tlinux-users:08166] Re: Intel PRO/100 VE bad EEPROM checksum?

Christopher R. Maden wrote:
> 
> According to Windows, the Ethernet adapter is at PCI 7, and under lspci -v
> looks like:
> 
> 0000:07:08.0 ffff: Intel Corp.: Unknown devie 1092 (rev ff) (prog-if ff)
>         !!! Unknown header type 7f
> 
> For comparison, the wireless adapter at PCI 5 says:
> 
> 0000:05:00.0 Network controller: Intel Corp.: Unknown device 4222 (rev 02)
>         Subsystem: Intel Corp.: Unknown device 1040
>         Flags: bus master, fast devsel, latency 0, IRQ 10
>         Memory at da000000 (32-bit, non-prefetchable) [size=4K]
>         Capabilities: [c8] Power Management version 2
>         Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0
> Enable-
>         Capabilities: [e0] #10 [0011]
> 
> The muddled output from lspci makes me more sure that there's a problem
> reading the EEPROM... but I wonder how Windows works with it.
> 
> ~Chris
Yes, that is strange. At a guess, I would say that the Windows
driver is only looking at the first line, and ignores the rest. It
can get away with that if it is a driver for a specific NIC, and not
a family of NICs. But with Linux, there are less drivers, and each
driver covers a lot more NICs. I have a few 802.11b wireless cards
that all use the same Linux driver, but have different Windows
drivers. (Though I cheated and used the Compaq driver for a MS
MN-520 card under Windows 95.)

If it is indeed an EEPROM, then I wonder if there is an update for
it that would reprogram it? Then again, the updater may balk on the
bad EEPROM.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!