From: Andrew Morton <akpm@zip.com.au>
To: Kees Bakker <kees.bakker@altium.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3c59x: LK1.1.17 gives No MII transceivers found
Date: Tue, 07 May 2002 02:14:34 -0700 [thread overview]
Message-ID: <3CD79AFA.F3B11E95@zip.com.au> (raw)
In-Reply-To: <3CD78BDC.B6ED1BA5@zip.com.au> <15575.38538.231057.425097@koli.tasking.nl>
Kees Bakker wrote:
>
> >>>>> "Andrew" == Andrew Morton <akpm@zip.com.au> 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!"
> 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...
> 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?
-
next prev parent reply other threads:[~2002-05-07 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 7:03 Kees Bakker
2002-05-07 8:10 ` Andrew Morton
2002-05-07 8:32 ` Xavier Bestel
2002-05-07 8:55 ` Kees Bakker
2002-05-07 9:14 ` Andrew Morton [this message]
2002-05-07 9:33 ` Kees Bakker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CD79AFA.F3B11E95@zip.com.au \
--to=akpm@zip.com.au \
--cc=kees.bakker@altium.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®