Message-ID: <46C1D9CB.9040208@ufomechanic.net>
Date: Tue, 14 Aug 2007 17:35:23 +0100
From: Amin Azez <azez@ufomechanic.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org, jesse.brandeburg@gmail.com, me@privacy.net,
       hpa@zytor.com
Subject: Re: Intel 82559 NIC corrupted EEPROM 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1075
Lines: 27

Regarding the thread accessible at:
   
http://groups.google.com/group/linux.kernel/browse_frm/thread/bdc8fd08fb601c26

that ended with "looks like it is specific to your hardware",

Can I check where we are with this?

I've just had a small installation run fail on 3 boxes with the same
problems, on new hardware, which sort of suggests there is no longer a
shortage of test scenarios.

To summarise, in my case it looks as though it really was a bad
checksum, by using the eepro100 driver and the lucky-fortune eeprom tool
at http://www.hockin.org/~thockin/enet_eeprom/enet_eeprom.tgz I was able
to re-write the mac address and thus have the EEPROM checksum re-calculated.

I don't recall the original reporter (John) saying that he had tried this.

I'm still checking with my supplier to see how this could have happened.

Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/