From: Ricardo Bugalho <ricardo.b@zmail.pt>
To: jbenc@suse.cz
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [BUG] Tulip for ULi M5263: No packets transmitted
Date: Mon, 25 Jul 2005 19:46:11 +0100 [thread overview]
Message-ID: <1122317171.7713.9.camel@localhost> (raw)
In-Reply-To: <20050725141644.66ba4021@griffin.suse.cz>
Hello,
yes it does help. Thanks.
Still not perfect though, it gives a warning, reports to be working on
half-duplex and I can't use mii-tool with it.
Here's the dmesg output (2.6.12.3 + patch):
Linux Tulip driver version 1.1.13 (May 11, 2002)
ACPI: PCI Interrupt 0000:00:0d.0[A] -> GSI 17 (level, low) -> IRQ 17
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1)
block.
tulip0: Index #1 - Media 10baseT (#0) described by a <unknown> (128)
block.
tulip0: Index #2 - Media 10baseT (#0) described by a 21140 non-MII (0)
block.
tulip0: Index #3 - Media 10base2 (#1) described by a 21140 non-MII (0)
block.
tulip0: Index #4 - Media 10baseT-FDX (#4) described by a 21140 non-MII
(0) block.
tulip0: Index #5 - Media 100baseTx-FDX (#5) described by a 21140
non-MII (0) block.
tulip0: ***WARNING***: No MII transceiver found!
eth0: ULi M5261/M5263 rev 64 at f884cc00, 00:0B:6A:D1:FC:B9, IRQ 17.
...
eth0: Setting half-duplex based on MII#1 link partner capability of
ffff.
...
When I try to run mii-tool, it yields:
# mii-tool eth0
SIOCGMIIPHY on 'eth0' failed: No such device
On Mon, 2005-07-25 at 14:16 +0200, Jiri Benc wrote:
> Does tulip-fixes-for-uli5261.patch from -mm tree help?
>
--
Ricardo
next prev parent reply other threads:[~2005-07-25 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 19:22 [BUG] Tulip for ULi M5263: No packets transmitted Ricardo Bugalho
2005-07-25 12:16 ` Jiri Benc
2005-07-25 18:46 ` Ricardo Bugalho [this message]
2005-08-01 17:01 ` Ricardo Bugalho
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=1122317171.7713.9.camel@localhost \
--to=ricardo.b@zmail.pt \
--cc=jbenc@suse.cz \
--cc=jgarzik@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.