ANA-6944A/TX (!) + AMIBIOS + linux-2.1.122; 3/4 success!
Wed Sep 30 16:12:14 1998
On Wed, 30 Sep 1998, John Kennedy wrote:
> Subject: Re: ANA-6944A/TX (!) + AMIBIOS + linux-2.1.122; 3/4 success!
> mii-diag.c:v1.03 8/4/98 Donald Becker (firstname.lastname@example.org)
> Using the default interface 'eth0'.
> SIOCGMIIPHY on eth0 failed: Operation not supported by device
> I didn't compile it or tulip-diag with libmii, so I'll have to see if
> that does anything for me (or you).
The 'mii-diag' program only works with recent driver versions that include
my ioctl() interface.
You can get the same output by compiling tulip-diag with "-DLIBMII libmii.c".
See the bottom of the source file for the compile command.
I wrote the ioctl() interface to have a device independent link setup and
> I could get interesting info out of tulip-diag. If the ordering is
> right (index #1 == eth0), then the port selection info is right.
> eth0/#1 is plugged into a junk-hub, #2 is plugged into a cisco 1924
> switch, #3 doesn't have anything plugged into it, and #4 is in limbo.
> tulip-diag.c:v1.03 5/20/98 Donald Becker (email@example.com)
> Chip Index #1: Found a DC21140 Tulip card at PCI bus 1, device 7 I/O 0xfc80.
> ***WARNING***: No MII transceivers found!
This concerns me...
> Chip Index #2: Found a DC21140 Tulip card at PCI bus 1, device 6 I/O 0xfc00.
> MII PHY found at address 1, status 0x7849.
> 3100 7849 2000 5c01 01e1 0000 0000 0000
You have no link beat here. Presumably this isn't plugged into anything.
> Chip Index #3: Found a DC21140 Tulip card at PCI bus 1, device 5 I/O 0xf880.
> MII PHY found at address 1, status 0x786f.
> 3100 786f 2000 5c01 01e1 4181 0003 0000
Good, connected to a autonegotiating 100mbps switch.
> Chip Index #4: Found a DC21140 Tulip card at PCI bus 1, device 4 I/O 0xf800.
> EEPROM transceiver/media description for the DC21140 chip.
This is the "first" interface. They saved $0.30 per port by having only one
EEPROM, and expecting the driver to assume the following ports were the
same. But since many BIOSes enumerate the devices backwards, the driver
writer's life isn't fun.
> MII PHY #1 transceiver registers:
> 3100 786d 2000 5c01 01e1 0021 0000 0000
This port is talking to a 10mbps hub (likely repeater) that doesn't
So the bottom line is that the fourth port is has a questionable MII
Donald Becker firstname.lastname@example.org
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center, Greenbelt, MD. 20771