9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
* [9fans] i82547EI; bad EEPROM checksum
@ 2011-02-28  9:43 visof
  2011-02-28 10:53 ` Sergey Zhilkin
  0 siblings, 1 reply; 5+ messages in thread
From: visof @ 2011-02-28  9:43 UTC (permalink / raw)
  To: 9fans

hello
i'm using 9atom on my pc but i have a problem with ethernet card, i
have these lines when the system start
 igbe: SPI EEPROM access not implemented
igbe: bad EEPROM checksum - 0x0000
igbe: SPI EEPROM access not implemented

i tried to compile the kernel and try again but with the same error
pci | grep net  ===> 2.1.0: net 02.00.00 8086/1019 10 0:e0100000
131072 2:000040 01 32
grep 1019 /sys/src/9/pc/etherigbe.c  ====>    i82547ei = (0x1019<<16)|
0x8086,

is there anyone have the same problem ? and how can i fix that if
possible

Thanks



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] i82547EI; bad EEPROM checksum
  2011-02-28  9:43 [9fans] i82547EI; bad EEPROM checksum visof
@ 2011-02-28 10:53 ` Sergey Zhilkin
  2011-02-28 12:23   ` erik quanstrom
  0 siblings, 1 reply; 5+ messages in thread
From: Sergey Zhilkin @ 2011-02-28 10:53 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

2011/2/28 visof <abdullahibra@gmail.com>

> hello
> i'm using 9atom on my pc but i have a problem with ethernet card, i
> have these lines when the system start
>  igbe: SPI EEPROM access not implemented
> igbe: bad EEPROM checksum - 0x0000
> igbe: SPI EEPROM access not implemented
>
> i tried to compile the kernel and try again but with the same error
> pci | grep net  ===> 2.1.0: net 02.00.00 8086/1019 10 0:e0100000
> 131072 2:000040 01 32
> grep 1019 /sys/src/9/pc/etherigbe.c  ====>    i82547ei = (0x1019<<16)|
> 0x8086,
>
> is there anyone have the same problem ? and how can i fix that if
> possible
>
> Thanks
>
>
Hello !

I have gotten  "igbe: bad EEPROM checksum" message on my IBM (Lenovo) T61
Tablet.
I've took a look at NetBSD kernel sources (if_wm.c), that recommends to read
EEPROM twice :)

Comment from if_wm.c:

/*
		 * Read twice again because some PCI-e parts fail the
		 * first check due to the link being in sleep state.
		 */


Maybe helpful :)

-- 
С наилучшими пожеланиями
Жилкин Сергей
With best regards
Zhilkin Sergey

[-- Attachment #2: Type: text/html, Size: 1530 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] i82547EI; bad EEPROM checksum
  2011-02-28 10:53 ` Sergey Zhilkin
@ 2011-02-28 12:23   ` erik quanstrom
  2011-02-28 13:34     ` Sergey Zhilkin
  0 siblings, 1 reply; 5+ messages in thread
From: erik quanstrom @ 2011-02-28 12:23 UTC (permalink / raw)
  To: 9fans

> I have gotten  "igbe: bad EEPROM checksum" message on my IBM (Lenovo) T61
> Tablet.
> I've took a look at NetBSD kernel sources (if_wm.c), that recommends to read
> EEPROM twice :)

did you try the patch i sent you?

- erik



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] i82547EI; bad EEPROM checksum
  2011-02-28 12:23   ` erik quanstrom
@ 2011-02-28 13:34     ` Sergey Zhilkin
  0 siblings, 0 replies; 5+ messages in thread
From: Sergey Zhilkin @ 2011-02-28 13:34 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

[-- Attachment #1: Type: text/plain, Size: 588 bytes --]

2011/2/28 erik quanstrom <quanstro@quanstro.net>

> > I have gotten  "igbe: bad EEPROM checksum" message on my IBM (Lenovo) T61
> > Tablet.
> > I've took a look at NetBSD kernel sources (if_wm.c), that recommends to
> read
> > EEPROM twice :)
>
> did you try the patch i sent you?
>
> - erik
>
>
No.

I've done a dirty hack (temporary workaround), this helped me to solve
problem with connectivity.
This was temporary work and I've lost all changes. :(

-- 
С наилучшими пожеланиями
Жилкин Сергей
With best regards
Zhilkin Sergey

[-- Attachment #2: Type: text/html, Size: 990 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] i82547EI; bad EEPROM checksum
       [not found] <357b5591-4883-4d9c-9ecc-b0e5afc6f609@p24g2000vbl.googlegroups.co>
@ 2011-02-28 12:27 ` erik quanstrom
  0 siblings, 0 replies; 5+ messages in thread
From: erik quanstrom @ 2011-02-28 12:27 UTC (permalink / raw)
  To: 9fans

On Mon Feb 28 04:55:15 EST 2011, abdullahibra@gmail.com wrote:
> hello
> i'm using 9atom on my pc but i have a problem with ethernet card, i
> have these lines when the system start
>  igbe: SPI EEPROM access not implemented
> igbe: bad EEPROM checksum - 0x0000
> igbe: SPI EEPROM access not implemented
> 
> i tried to compile the kernel and try again but with the same error
> pci | grep net  ===> 2.1.0: net 02.00.00 8086/1019 10 0:e0100000
> 131072 2:000040 01 32
> grep 1019 /sys/src/9/pc/etherigbe.c  ====>    i82547ei = (0x1019<<16)|
> 0x8086,
> 
> is there anyone have the same problem ? and how can i fix that if
> possible

now that this has leaked onto the list,
the intel manual seems to indicate that the
check that's being tripped is using an undefined
bit in the register.*

i think the first change to try would be to comment
out the check, so 

static int
at93c46r(Ctlr* ctlr)
{
	ushort sum;
	char rop[20];
	int addr, areq, bits, data, eecd, i;

	eecd = csr32r(ctlr, Eecd);
	if(eecd & Spi){
		print("igbe: SPI EEPROM access not implemented\n");
//		return 0;
	}
[...]

- erik

---
* PCI/PCI-X Family of Gigabit Ethernet Controllers
Software Developer's Manual (SDM) 82540EP/EM,
82541xx, 82544GC/EI, 82545GM/EM, 82546GB/EB, and 82547xx
version 4.0, §13.4.3 p. 232.



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2011-02-28 13:34 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-28  9:43 [9fans] i82547EI; bad EEPROM checksum visof
2011-02-28 10:53 ` Sergey Zhilkin
2011-02-28 12:23   ` erik quanstrom
2011-02-28 13:34     ` Sergey Zhilkin
     [not found] <357b5591-4883-4d9c-9ecc-b0e5afc6f609@p24g2000vbl.googlegroups.co>
2011-02-28 12:27 ` erik quanstrom

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).