AW: [eepro100-bug] 82559ER on eepd board
Fri Aug 23 01:54:01 2002
I suffer from the same problems. I talked a lot with the EEPD people. One
the Video Interupt is shown in the Bios message, but there is no hardware
IRQ line attached to the video controller, because modern VGA chips don't
use it. So, there is no problem with shared IRQs.
"The system runs fine with windows" is also what the EEPD (developer) people
say. So what is the difference between the windows and eepro100 driver????
My next step in this tale is to try an external card with 559 or 558 chip.
We now from other PCs that this chips seem to have less problems.
basysPrint GmbH, Guelzer Str. 15, 19258 Boizenburg, Germany
Tel.: ++49-38847-99-150, Fax:++49-38847-99-192
> -----Ursprungliche Nachricht-----
> Von: firstname.lastname@example.org
> [mailto:email@example.com]Im Auftrag von
> Gesendet: Donnerstag, 22. August 2002 18:16
> An: firstname.lastname@example.org
> Cc: email@example.com
> Betreff: [eepro100-bug] 82559ER on eepd board
> Hi Parvan,
> I've read your mail dd 2002/08/09 on the eepro100bug list.
> I'm also using a PC104 board from eepd (Profive C3VE, Celeron 400Mhz)
> with the 82559ER. I experienced the same problem: Tx buffer timeout.
> I've tested the same driver/chip combination on another eepd board (with
> Pentium MMX 266Mhz) and it runs quite well. The difference I saw were
> the irq's. On the Celeron board the ethernet (PCI 0, dev 10) shares an
> irq with the video driver (PCI 1 Dev 0). On the MMX board they
> had separated irq's. Unfortunatly there is no way to change the
> irq assignment,
> their bios doesn't allow it. I've read somewhere on the web, that changing
> the irq's can only be done in the bios...
> My testsw generates messages (with random-but-limited length) that are
> send back and forth between 2 pc's. I've noticed if you send small
> messages (<500bytes) things improve: during ~13hours messages were send
> and recevied succesfully. With big messages the timeout occurs after a
> few seconds...
> I was thinking of changing the MTU size as a workaround, but I'm
> not sure
> if this is ok. Ethernet is not really my cup of tea...
> Changing the #define PKT_BUF_S from 15365 to 536 wasn't enough,
> errors occured
> for messages >536bytes... Hints are very welcome...
> I've contacted eepd via a local reseller, but they weren't too
> cooperative: they said it worked fine for windows :(
> Steven Krekels Email: firstname.lastname@example.org
> Alcatel Bell Space N.V. Phone: +32 3 829 51 75
> Berkenrodelei 33 Fax: +32 3 829 55 02
> B-2660 Hoboken
> Belgium http://www.alcatel.be/space
> eepro100-bug mailing list