lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 22 Feb 2011 20:59:07 +0100
From:	Maciej Kotliński <makotlinski@...il.com>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
CC:	Karsten Keil <kkeil@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: e1000e EEPROM corruption

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.
>

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ