3Com 3c905B

3Com 3c905B

Post by Ethan Trewhit » Thu, 13 Jun 2002 07:44:20



Hello all,

Pre-Info: RedHat 7.3, Kernel 2.4.18-4, included 3Com driver.

I'm having problems with a 3c905b. It was working fine at home on a little
10Mbps DLink hub, and now I have taken it to a friend's dorm room to serve
stuff. Now when the machine boots (in the dorm), the 3com card will not
properly autonegotiate, and there is no link light. The dorm's hubstack is
10Mbps, half-duplex. BUT...when I disconnect and reconnect the net cable,
all is well - the 10M link led turns on and the card works fine.

What would be the difference between the card's detection processes at boot
and those when the link is severed and reconnected? I am fine forcing
10baseT-HD all the time, but how can I do this to insure the card will work
fine straight from bootup?

Here are my diagnostic results:

--- mii-tool ----------------------------------------

eth0: 10 Mbit, half duplex, link ok
  product info: vendor 00:00:00, model 0 rev 0
  basic mode:   10 Mbit, half duplex
  basic status: link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  link partner: 10baseT-HD

--- vortex-diag -ee ---------------------------------

Index #1: Found a 3c905B Cyclone 100baseTx adapter at 0xc400.
EEPROM format 64x16, configuration table at offset 0:
    00: 0010 4b36 f9f4 9055 c44a 0036 424e 6d50
  0x08: 2970 0000 0010 4b36 f9f4 0020 0000 0000
  0x10: 32a6 0000 0000 0380 0000 0004 0000 10b7
  0x18: 9055 000a 0000 0000 0000 0000 0000 0000
  0x20: 004e 0000 0000 0000 0000 0000 0000 0000
      ...

 The word-wide EEPROM checksum is 0x9005.
Saved EEPROM settings of a 3Com Vortex/Boomerang:
 3Com Node Address 00:10:4B:36:F9:F4 (used as a unique ID only).
 OEM Station address 00:10:4B:36:F9:F4 (used as the ethernet address).
  Device ID 9055,  Manufacturer ID 6d50.
  Manufacture date (MM/DD/YYYY) 2/10/1998, division 6, product NB.
  No BIOS ROM is present.
 Options: negotiated duplex, link beat required.
  Vortex format checksum is incorrect (0026 vs. 10b7).
  Cyclone format checksum is correct (0x4e vs. 0x4e).
  Hurricane format checksum is correct (0x4e vs. 0x4e).

--- vortex-diag -aa ---------------------------------

Index #1: Found a 3c905B Cyclone 100baseTx adapter at 0xc400.
The Vortex chip may be active, so FIFO registers will not be read.
To see all register values use the '-f' flag.
Initial window 7, registers values by window:
  Window 0: 0000 0000 0000 0000 0000 00bf 0000 0000.
  Window 1: FIFO FIFO 0000 0000 0000 0000 0000 2000.
  Window 2: 1000 364b f4f9 0000 0000 0000 0002 4000.
  Window 3: 0000 0380 05ea 0000 000a 0800 0800 6000.
  Window 4: 0000 00d2 8000 0cc0 0001 88a0 0000 8000.
  Window 5: 1ffc 0000 0000 0600 0807 06ce 06c6 a000.
  Window 6: 0000 0a00 0000 a800 0000 441f 1dc3 c000.
  Window 7: 0000 0000 0000 0000 0000 0000 0000 e000.
Vortex chip registers at 0xc400
  0xC410: **FIFO** 00000000 00000029 *STATUS*
  0xC420: 00000020 00000000 00080000 00000004
  0xC430: 00000000 5425abdb 167f60b0 00080004
 Indication enable is 06c6, interrupt enable is 06ce.
 No interrupt sources are pending.
 Transceiver/media interfaces available:  100baseTx 10baseT.
Transceiver type in use:  Autonegotiate.
 MAC settings: half-duplex.
 Station address set to 00:10:4b:36:f9:f4.
 Configuration options 0002.

--- vortex-diag -mm ---------------------------------

Index #1: Found a 3c905B Cyclone 100baseTx adapter at 0xc400.
 MII PHY found at address 24, status 780d.
 MII PHY 0 at #24 transceiver registers:
   0000 780d 0000 0000 01e1 0020 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.

--
ethanT
http://eplanet.cjb.net
aim: courtarro
(fix spam block before sending email)

 
 
 

3Com 3c905B

Post by Ethan Trewhit » Fri, 14 Jun 2002 01:26:37




> post-install 3c59x mii-tool -F 10baseT-HD eth0

I added that, and still no dice. Card has no link lights at boot, but
disconnecting and reconnecting the net cable makes all work fine.

--
ethanT
http://eplanet.cjb.net
to email: remove all capital letters from given address

 
 
 

3Com 3c905B

Post by Ethan Trewhit » Sat, 15 Jun 2002 00:15:35



Quote:> Did you run "depmod -a" after the change?

  No, I will try that later today when I have console access again

Quote:> Is this the only way to make the card work? I understood your
> first article like running the mii-tool command after booting
> would fix the problem without disconnecting the cable. The above
> command doesn't do anything but doing that automatically.

  Sorry if I misspoke, but the reconnection method is the only one
  I can get to work. When I say "I am fine forcing 10baseT-HD all
  the time" - it means I'm willing to give up any autonegotiation
  features if it means I'll be able to make this connection work.
  mii-tool hasn't been able to do it yet, but I'll try the depmod
  later today.

--
ethanT
http://eplanet.cjb.net
to email: remove all capital letters from given address

 
 
 

3Com 3c905B

Post by Toad » Sat, 15 Jun 2002 10:24:46


I do believe i've had a similar problem once before with a 3Com NIC (I can't
remember as to which one it was).  Regardless of what I tried, the only
solution seemed to be disconnecting the CAT-5 from the hub and reconnecting
it...


Quote:> Hello all,

> Pre-Info: RedHat 7.3, Kernel 2.4.18-4, included 3Com driver.

> I'm having problems with a 3c905b. It was working fine at home on a little
> 10Mbps DLink hub, and now I have taken it to a friend's dorm room to serve
> stuff. Now when the machine boots (in the dorm), the 3com card will not
> properly autonegotiate, and there is no link light. The dorm's hubstack is
> 10Mbps, half-duplex. BUT...when I disconnect and reconnect the net cable,
> all is well - the 10M link led turns on and the card works fine.

> What would be the difference between the card's detection processes at
boot
> and those when the link is severed and reconnected? I am fine forcing
> 10baseT-HD all the time, but how can I do this to insure the card will
work
> fine straight from bootup?

> Here are my diagnostic results:

> --- mii-tool ----------------------------------------

> eth0: 10 Mbit, half duplex, link ok
>   product info: vendor 00:00:00, model 0 rev 0
>   basic mode:   10 Mbit, half duplex
>   basic status: link ok
>   capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
>   advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
>   link partner: 10baseT-HD

> --- vortex-diag -ee ---------------------------------

> Index #1: Found a 3c905B Cyclone 100baseTx adapter at 0xc400.
> EEPROM format 64x16, configuration table at offset 0:
>     00: 0010 4b36 f9f4 9055 c44a 0036 424e 6d50
>   0x08: 2970 0000 0010 4b36 f9f4 0020 0000 0000
>   0x10: 32a6 0000 0000 0380 0000 0004 0000 10b7
>   0x18: 9055 000a 0000 0000 0000 0000 0000 0000
>   0x20: 004e 0000 0000 0000 0000 0000 0000 0000
>       ...

>  The word-wide EEPROM checksum is 0x9005.
> Saved EEPROM settings of a 3Com Vortex/Boomerang:
>  3Com Node Address 00:10:4B:36:F9:F4 (used as a unique ID only).
>  OEM Station address 00:10:4B:36:F9:F4 (used as the ethernet address).
>   Device ID 9055,  Manufacturer ID 6d50.
>   Manufacture date (MM/DD/YYYY) 2/10/1998, division 6, product NB.
>   No BIOS ROM is present.
>  Options: negotiated duplex, link beat required.
>   Vortex format checksum is incorrect (0026 vs. 10b7).
>   Cyclone format checksum is correct (0x4e vs. 0x4e).
>   Hurricane format checksum is correct (0x4e vs. 0x4e).

> --- vortex-diag -aa ---------------------------------

> Index #1: Found a 3c905B Cyclone 100baseTx adapter at 0xc400.
> The Vortex chip may be active, so FIFO registers will not be read.
> To see all register values use the '-f' flag.
> Initial window 7, registers values by window:
>   Window 0: 0000 0000 0000 0000 0000 00bf 0000 0000.
>   Window 1: FIFO FIFO 0000 0000 0000 0000 0000 2000.
>   Window 2: 1000 364b f4f9 0000 0000 0000 0002 4000.
>   Window 3: 0000 0380 05ea 0000 000a 0800 0800 6000.
>   Window 4: 0000 00d2 8000 0cc0 0001 88a0 0000 8000.
>   Window 5: 1ffc 0000 0000 0600 0807 06ce 06c6 a000.
>   Window 6: 0000 0a00 0000 a800 0000 441f 1dc3 c000.
>   Window 7: 0000 0000 0000 0000 0000 0000 0000 e000.
> Vortex chip registers at 0xc400
>   0xC410: **FIFO** 00000000 00000029 *STATUS*
>   0xC420: 00000020 00000000 00080000 00000004
>   0xC430: 00000000 5425abdb 167f60b0 00080004
>  Indication enable is 06c6, interrupt enable is 06ce.
>  No interrupt sources are pending.
>  Transceiver/media interfaces available:  100baseTx 10baseT.
> Transceiver type in use:  Autonegotiate.
>  MAC settings: half-duplex.
>  Station address set to 00:10:4b:36:f9:f4.
>  Configuration options 0002.

> --- vortex-diag -mm ---------------------------------

> Index #1: Found a 3c905B Cyclone 100baseTx adapter at 0xc400.
>  MII PHY found at address 24, status 780d.
>  MII PHY 0 at #24 transceiver registers:
>    0000 780d 0000 0000 01e1 0020 0000 0000
>    0000 0000 0000 0000 0000 0000 0000 0000
>    0000 0000 0000 0000 0000 0000 0000 0000
>    0000 0000 0000 0000 0000 0000 0000 0000.

> --
> ethanT
> http://eplanet.cjb.net
> aim: courtarro
> (fix spam block before sending email)

 
 
 

3Com 3c905B

Post by Douglas Col » Tue, 18 Jun 2002 01:36:23



> Hello all,

> Pre-Info: RedHat 7.3, Kernel 2.4.18-4, included 3Com driver.

> I'm having problems with a 3c905b. It was working fine at home on a little
> 10Mbps DLink hub, and now I have taken it to a friend's dorm room to serve
> stuff. Now when the machine boots (in the dorm), the 3com card will not
> properly autonegotiate, and there is no link light. The dorm's hubstack is
> 10Mbps, half-duplex. BUT...when I disconnect and reconnect the net cable,
> all is well - the 10M link led turns on and the card works fine.

> What would be the difference between the card's detection processes at
> boot and those when the link is severed and reconnected? I am fine forcing
> 10baseT-HD all the time, but how can I do this to insure the card will
> work fine straight from bootup?

> Here are my diagnostic results:

'snipped

The specific model 3c905b has known "problems" of not autonegotiating when
running on non-plug-n-pray os's (win-nt,linux,unix etc) whereas if you use
it on a windblows 95/98/2000 it will work fine everytime .

So , whats a WHO to do ?

Well I picked up a pile of these nic's because the sysadmin who gave them to
me said they were "junk" and wouldn't work right on his isolated network
that he managed , so I said sure I'll take 'em and try to see if I can make
them work .
Well after running the 3com utility from a dos boot floppy (you can download
it from the 3com website) and forcing them to 100B-T/hd they work excellent
on my home network on my Linux boxen, without having to do your disconnect
the network cable each time I boot .

So that is most likely your solution unless someone comes up with a better
one , is to disable autonegotiation and force it to the mode that works on
your network using the dos utilities  :^}

--
Douglas Cole   N7BFS
AMSAT#26182 , K2 # 544
http://www.users.qwest.net/~cdoug3
Registered Linux user # 188922

 
 
 

3Com 3c905B

Post by Ethan Trewhit » Tue, 18 Jun 2002 03:11:58



Quote:> Well after running the 3com utility from a dos boot floppy (you can
> download it from the 3com website) and forcing them to 100B-T/hd they
> work excellent on my home network on my Linux boxen, without having to
> do your disconnect the network cable each time I boot .

Well, that has been suggested, but since you seem confident I will try to
get to the console to work on it. I have had a friend working on it from
afar while I admin remotely. I'll let you know in a few days if this works
for me. Thanks!

--
ethanT
http://eplanet.cjb.net
to email: remove all capital letters from given address

 
 
 

1. Driver for 3com 3c905b?

Does anyone know where I can get a device driver for the 3Com 3c905b
NIC? I just installed Debian 2.0 on a system with this card. The
Hardware Compatibility HOWTO mentions this card but doesn't say where to
get a driver.

-Mike

2. sendmail or something

3. 3com 3c905b & @home, Now what do I do?

4. Where to put true type fonts in latest Xfree86

5. Redhat 6.2 with Asus cuv4x-e + Ati xpert 98 + 3com 3c905b

6. Consumer graphic card in Sun SPARC ?

7. 3com 3c905B tx

8. Printer Setup

9. 3Com 3c905B and 3c90x driver troubles

10. 3Com 3C905B

11. 3com 3C905B-TX

12. 3com 3c905b Cyclone problem

13. 3Com 3C905B-TX runs at 10M instead of 100M