Re: problem with eth0 and 3Com

Hi Robert,

It seems that quite a few people have been having this problem. While I
haven't found the solution yet, I can tell you that I had no success after
charging both the internal battery, and the pcmcia sleeve battery.

You can monitor my progress from this thread:

http://www.handhelds.org/pipermail/familiar/2001-August/001284.html

I'll be working on the problem this weekend, and hopefully, will find a
solution. If anyone else reading this thread has experienced this
problem, and would like to pitch in, it would be much appreciated.
Many options have been exhausted at this point.

On a side note, the following Google search turned up some rather
interesting possibilities regarding "enable_wol", in 2.4.6.

http://www.google.com/search?q=%22eth0%3A+command+0x5800+did+not+complete%21%22+

I haven't had time yet to look into this, but it seems promising.
I'll be in #familiar on openprojects if anyone wants to discuss this.

mowse@mowse.ne.mediaone.net

On Fri, 10 Aug 2001, Robert Percival wrote:

> Apologies if this has been answered before; I can find a couple of the
> same questions but the only answer is to charge the sleeve battery and
> this has been done.
>
> When I insert my 3Com 589 LAN card into a single card PCMCIA jacket I
> keep getting the following:
>
> ====
> # cardmgr[59]: + Operation failed.
> cardmgr[59]: shutting down socket 1
> cardmgr[59]: executing: './network stop eth1'
> cardmgr[59]: + Operation failed.
> cardmgr[59]: executing: 'modprobe -r 3c589_cs'
> cardmgr[59]: + modprobe: Can't open dependencies file
> /lib/modules/2.4.3-rmk2-np
> 1/modules.dep (No such file or directory)
> cardmgr[59]: modprobe exited with status 255
> cardmgr[59]: initializing socket 0
> cardmgr[59]: socket 0: 3Com 589 Ethernet
> bitsy_pcmcia_configure_socket: socket=0 vcc=50 vpp=0 reset=0
> bitsy_pcmcia_configure_socket: socket=0 vcc=50 vpp=0 reset=0
> eth0: 3Com 3c589, io 0xf6000300, irq 42, hw_addr 00:80:00:81:00:82
> 8K FIFO split 5:3 Rx:Tx, auto xcvr
> cardmgr[59]: executing: './network start eth0'
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out!
> irq status 0801, rx status 0801, tx status 08 tx free 0801
> diagnostics: fifo 0804 net 0804 ethernet 0804 media 0804
> eth0: command 0x5800 did not complete!
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out!
> irq status 0801, rx status 0801, tx status 08 tx free 0801
> diagnostics: fifo 0804 net 0804 ethernet 0804 media 0804
> eth0: command 0x5800 did not complete!
> ====
>
> with the NETDEV repeated over and over.
>
> Has anyone managed to fix this? Have I done something silly? The
> 2.4.3-rmk2-np error concerns me a little .. I installed the 'lazy' set ..
>
> Thanks!
>
> ~robp
> ... ...
> ...please send plain text mail if possible...
> ... ...
> /******************************************************************\
> | Robert Percival RiverSoft Support |
>
>
> _______________________________________________
> Familiar mailing list
> Familiar@handhelds.org
> http://handhelds.org/mailman/listinfo/familiar
> irc://irc.openprojects.net #familiar
>
Received on Fri Aug 10 10:22:45 2001