Skip to contentSkip to conversation

3c59x: LK1.1.17 gives No MII transceivers found

DISCUSSION Kees Bakker 3 participants 6 messages May 7, 2002

lore
Share & tools
lore

Kees Bakker

author
#0 lore raw

In 2.5.8 there was an update of the 3c59x driver. I have two NICs, both use this driver, a 3c900 Boomerang and a 3c905C Tornado.

Linux 2.4.17 and 2.5.7 both report
00:08.0: 3Com PCI 3c900 Boomerang 10Mbps Combo at 0xd400. Vers LK1.1.16 00:09.0: 3Com PCI 3c905C Tornado at 0xd000. Vers LK1.1.16

However, the new driver produces:
00:08.0: 3Com PCI 3c900 Boomerang 10Mbps Combo at 0xd400. Vers LK1.1.17 phy=0, phyx=24, mii_status=0xffff
phy=1, phyx=0, mii_status=0xffff
phy=2, phyx=1, mii_status=0xffff
phy=3, phyx=2, mii_status=0xffff
phy=4, phyx=3, mii_status=0xffff
phy=5, phyx=4, mii_status=0xffff
phy=6, phyx=5, mii_status=0xffff
phy=7, phyx=6, mii_status=0xffff
phy=8, phyx=7, mii_status=0xffff
phy=9, phyx=8, mii_status=0xffff
phy=10, phyx=9, mii_status=0xffff
phy=11, phyx=10, mii_status=0xffff
phy=12, phyx=11, mii_status=0xffff
phy=13, phyx=12, mii_status=0xffff
phy=14, phyx=13, mii_status=0xffff
phy=15, phyx=14, mii_status=0xffff
phy=16, phyx=15, mii_status=0xffff
phy=17, phyx=16, mii_status=0xffff
phy=18, phyx=17, mii_status=0xffff
phy=19, phyx=18, mii_status=0xffff
phy=20, phyx=19, mii_status=0xffff
phy=21, phyx=20, mii_status=0xffff
phy=22, phyx=21, mii_status=0xffff
phy=23, phyx=22, mii_status=0xffff
phy=24, phyx=23, mii_status=0xffff
phy=25, phyx=25, mii_status=0xffff
phy=26, phyx=26, mii_status=0xffff
phy=27, phyx=27, mii_status=0xffff
phy=28, phyx=28, mii_status=0xffff
phy=29, phyx=29, mii_status=0xffff
phy=30, phyx=30, mii_status=0xffff
phy=31, phyx=31, mii_status=0xffff
***WARNING*** No MII transceivers found!
00:09.0: 3Com PCI 3c905C Tornado at 0xd000. Vers LK1.1.17 phy=0, phyx=24, mii_status=0x782d

Does anybody have a clue what can be wrong? Any help would be appreciated.

Kees

#1 lore raw
Quoted 4 lines · Kees Bakker

In 2.5.8 there was an update of the 3c59x driver. I have two NICs, both use this driver, a 3c900 Boomerang and a 3c905C Tornado.

Quoted 8 lines

Linux 2.4.17 and 2.5.7 both report
00:08.0: 3Com PCI 3c900 Boomerang 10Mbps Combo at 0xd400. Vers LK1.1.16 00:09.0: 3Com PCI 3c905C Tornado at 0xd000. Vers LK1.1.16

However, the new driver produces:
00:08.0: 3Com PCI 3c900 Boomerang 10Mbps Combo at 0xd400. Vers LK1.1.17 phy=0, phyx=24, mii_status=0xffff
phy=1, phyx=0, mii_status=0xffff

It's just random debug code. Does the 3c900 actually work correctly?

-

#2 lore raw

Speaking of MII ... I have some RTL8139(A|B|C) network cards, which can do 10/100Mbps. However the driver doesn't seem to advertise MII registers.
Do these cards have MII registers ?
Anyone knows how I can switch them to 100Mbps ?

Xav

[xav@bip:~]$ /sbin/mii-tool -v -v
eth0: 10 Mbit, half duplex, no link
  registers for MII PHY 32: 
    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 0000 0000 0000 0000 0000 0000
  product info: vendor 00:00:00, model 0 rev 0
  basic mode:   10 Mbit, half duplex
  basic status: no link
  capabilities:
  advertising:
author
#3 lore raw
In reply to Andrew Morton
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Andrew" == Andrew Morton <[email protected]> writes:

Quoted 4 lines · Andrew> Kees Bakker wrote:
Quoted 4 lines

In 2.5.8 there was an update of the 3c59x driver. I have two NICs, both use this driver, a 3c900 Boomerang and a 3c905C Tornado.

Quoted 8 lines
Quoted 8 lines

Linux 2.4.17 and 2.5.7 both report
00:08.0: 3Com PCI 3c900 Boomerang 10Mbps Combo at 0xd400. Vers LK1.1.16 00:09.0: 3Com PCI 3c905C Tornado at 0xd000. Vers LK1.1.16

However, the new driver produces:
00:08.0: 3Com PCI 3c900 Boomerang 10Mbps Combo at 0xd400. Vers LK1.1.17 phy=0, phyx=24, mii_status=0xffff
phy=1, phyx=0, mii_status=0xffff

Andrew> It's just random debug code.

Is that also true for the "***WARNING*** No MII transceivers found!" message?

Andrew> Does the 3c900 actually work correctly?

I can't tell, because since it hangs at boot. That is, every kernel after 2.5.7 that I could build, including 2.5.13. (I'm having those hda: lost interrupt messages).

Signature · 10 lines
**************************************
Kees Bakker
Senior Software Designer
Altium - Think it, Design it, Build it
Phone  : +31 33 455 8584
Fax    : +31 33 455 5503
E-Mail : [email protected]
URL    : http://www.altium.com
**************************************
English is wonderful, used correctly
#4 lore raw
In reply to Andrew Morton
Quoted 17 lines · Kees Bakker
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

"Andrew" == Andrew Morton <[email protected]> writes:

Quoted 4 lines · Andrew> Kees Bakker wrote:
Quoted 4 lines

In 2.5.8 there was an update of the 3c59x driver. I have two NICs, both use this driver, a 3c900 Boomerang and a 3c905C Tornado.

Quoted 8 lines
Quoted 8 lines

Linux 2.4.17 and 2.5.7 both report
00:08.0: 3Com PCI 3c900 Boomerang 10Mbps Combo at 0xd400. Vers LK1.1.16 00:09.0: 3Com PCI 3c905C Tornado at 0xd000. Vers LK1.1.16

However, the new driver produces:
00:08.0: 3Com PCI 3c900 Boomerang 10Mbps Combo at 0xd400. Vers LK1.1.17 phy=0, phyx=24, mii_status=0xffff
phy=1, phyx=0, mii_status=0xffff

Quoted 4 lines

Andrew> It's just random debug code.

Is that also true for the "***WARNING*** No MII transceivers found!" message?

Not really. The driver shouldn't have gone looking for MII transceivers for a 3c900.

I'll take a look, see if I can remember how the darn driver works. 3c59x is very much in "it works, don't futz with it" mode...

Quoted 5 lines

Andrew> Does the 3c900 actually work correctly?

I can't tell, because since it hangs at boot. That is, every kernel after 2.5.7 that I could build, including 2.5.13. (I'm having those hda: lost interrupt messages).

Ouch. So 2.5.7 worked OK? What sort of controller and disks do you have?

-

author
#5 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Andrew" == Andrew Morton <[email protected]> writes:

Andrew> It's just random debug code.

Quoted 3 lines
Quoted 3 lines

Is that also true for the "***WARNING*** No MII transceivers found!" message?

Andrew> Not really. The driver shouldn't have gone looking for MII Andrew> transceivers for a 3c900.

Andrew> I'll take a look, see if I can remember how the darn driver Andrew> works. 3c59x is very much in "it works, don't futz with it" mode...

Andrew> Does the 3c900 actually work correctly?

Quoted 4 lines
Quoted 4 lines

I can't tell, because since it hangs at boot. That is, every kernel after 2.5.7 that I could build, including 2.5.13. (I'm having those hda: lost interrupt messages).

Andrew> Ouch. So 2.5.7 worked OK? What sort of controller and disks do Andrew> you have?

The 2.5.7 worked reasonably well (for a few days, I think). Except that it hung at one point and I decided to go back to 2.4.17. My plan was to try it again with a newer kernel.

My system:
- MSI MSI K7T266 Pro, with an Athlon 1.3 GHz
- IBM Deskstar 60GXP, 40Gb using onboard IDE controller
- 3c900
- 3c905C
- Adaptec 2940
- Hauppauge Win/TV Theatre
- USB: Iiyama monitor, Dlink webcam

Shall I try to build with LK1.1.16?

Signature · 10 lines
**************************************
Kees Bakker
Senior Software Designer
Altium - Think it, Design it, Build it
Phone  : +31 33 455 8584
Fax    : +31 33 455 5503
E-Mail : [email protected]
URL    : http://www.altium.com
**************************************
Evil has been dealt a serious blow, but will be back