[vortex] docking/undocking problems with 3c59x

[john]

hi
i have a small, but annoying problem with 3c59x on my dell latitude cpx running slackware 7.1.  if i boot up in the docking station everthing is fine, here is the log:

Mar 30 10:08:32 dyn-84 kernel: 3c59x.c 15Sep00 Donald Becker and others http://www.scyld.com/network/vortex.html
Mar 30 10:08:32 dyn-84 kernel: eth0: 3Com 3c905C Tornado at 0xdc00,  00:b0:d0:57:28:f6, IRQ 10
Mar 30 10:08:32 dyn-84 kernel:   8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
Mar 30 10:08:32 dyn-84 kernel:   MII transceiver found at address 24, status 782d.
Mar 30 10:08:32 dyn-84 kernel:   Enabling bus-master transmits and whole-frame receives.

if i undock, then put it back, i cant get the network to come back up.  and if i remove the module and re-insert it, this is what i get in the log:

Mar 30 10:04:07 dyn-84 kernel: 3c59x.c 15Sep00 Donald Becker and others http://www.scyld.com/network/vortex.html
Mar 30 10:04:07 dyn-84 kernel: eth0: 3Com 3c905C Tornado at 0xdc00,  ff:ff:ff:ff:ff:ff, IRQ 10
Mar 30 10:04:07 dyn-84 kernel:   1024K word-wide RAM 3:5 Rx:Tx split, autoselect/<invalid transceiver> interface.
Mar 30 10:04:07 dyn-84 kernel:   Enabling bus-master transmits and early receives.


obviously, ff:ff:ff:ff:ff:ff is a bad hardware address and <invalid transceiver> looks bad too.  its missing the whole line about the MII transceiver.  the only way i've found to correct this problem is reboot...and thats lame.

so im wondering, is there some options i can try to make it work when i re-insert the module or am i just doomed to reboot everyday?
-j