All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej Kotliński" <makotlinski@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Karsten Keil <kkeil@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: e1000e EEPROM corruption
Date: Tue, 22 Feb 2011 20:59:07 +0100	[thread overview]
Message-ID: <4D64158B.6010807@gmail.com> (raw)
In-Reply-To: <20110222180611.GA724@khazad-dum.debian.net>

I found the way to run my network card without writing anything to EEPROM.

I removed NVM and MAC address checks from e1000e driver source.
The module loads fine. Ethernet adapter have MAC 00:00:00:00:00:00.
Than I change MAC to correct one by ifconfig eth0 hw ether.
Network works fine. I could even read correct data by ethtool -e.
It makes the problem more strange. The correct EEPROM is there but...



W dniu 22.02.2011 19:06, Henrique de Moraes Holschuh pisze:
> On Tue, 22 Feb 2011, Maciej Kotliński wrote:
>> I had such problem few times earlier but it used to disappear after
>> few hours.
> Looks like a hardware issue to me. Cold/broken solders (reflowing the board
> could fix it), for example.
>
>> I have access to the same laptop, so I can get correct EPROM contents.
>> Still I don't know how to put this to my card.
>>
>> Could you tell me how to reprogram my card?
> That would only help if the problem is a "weak programming" of the EEPROM,
> which is something I have never seen before.  Writing to it with flacky
> circuitry is probably going to crap it for good.
>


      reply	other threads:[~2011-02-22 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 13:59 e1000e EEPROM corruption Karsten Keil
2008-10-18 17:06 ` Pierre Ossman
2011-02-22 14:46 ` Maciej Kotliński
2011-02-22 18:06   ` Henrique de Moraes Holschuh
2011-02-22 19:59     ` Maciej Kotliński [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D64158B.6010807@gmail.com \
    --to=makotlinski@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.