Re: 3c59x: LK1.1.17 gives No MII transceivers found
Andrew Morton (firstname.lastname@example.org)
Tue, 07 May 2002 02:14:34 -0700
Kees Bakker wrote:
> >>>>> "Andrew" == Andrew Morton <email@example.com> writes:
> Andrew> Kees Bakker wrote:
> >> 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
> Andrew> It's just random debug code.
> Is that also true for the "***WARNING*** No MII transceivers found!"
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...
> 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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/