From: Dominik Karall <dominik.karall@gmx.net>
To: Daniele Venzano <webvenza@libero.it>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: problem with sis900
Date: Thu, 13 May 2004 20:02:56 +0200 [thread overview]
Message-ID: <200405132002.56402.dominik.karall@gmx.net> (raw)
In-Reply-To: <20040513151759.GA27382@gateway.milesteg.arr>
On Thursday 13 May 2004 17:17, Daniele Venzano wrote:
> On Wed, May 12, 2004 at 12:30:12AM +0200, Dominik Karall wrote:
> [...]
>
> > nvidia: module license 'NVIDIA' taints kernel.
> > 0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336 Wed
> > Jan 14 18:29:26 PST 2004
>
> [...]
>
> Your kernel is tainted, but I'm willing to think that you can reproduce
> the problem without binary modules loaded. Please confirm this.
Yes, I'm using the kernel nv driver now.
>
> > Let me know if you need more infos!
>
> It seems that the driver is confused by the on chip informations it
> reads and detects some 'ghost' transceivers, then decides to use one of
> those, instead of taking the real one.
>
> The following patch is a guess in this direction, it should make the
> driver get the PHY at address 1, the one detected correctly for you.
> Obviously, if it works, I'll need to make the patch a bit more
> general before submission...
Sorry, but the patch does not help, same error messages in log, and can't
change to full-duplex mode.
sis900.c: v1.08.07 11/02/2003
eth0: Unknown PHY transceiver found at address 0.
eth0: Realtek RTL8201 PHY transceiver found at address 1.
eth0: Unknown PHY transceiver found at address 2.
eth0: Unknown PHY transceiver found at address 3.
eth0: Unknown PHY transceiver found at address 4.
eth0: Unknown PHY transceiver found at address 5.
eth0: Unknown PHY transceiver found at address 6.
eth0: Unknown PHY transceiver found at address 7.
eth0: Unknown PHY transceiver found at address 8.
eth0: Unknown PHY transceiver found at address 9.
eth0: Unknown PHY transceiver found at address 10.
eth0: Unknown PHY transceiver found at address 11.
eth0: Unknown PHY transceiver found at address 12.
eth0: Unknown PHY transceiver found at address 13.
eth0: Unknown PHY transceiver found at address 14.
eth0: Unknown PHY transceiver found at address 15.
eth0: Unknown PHY transceiver found at address 16.
eth0: Unknown PHY transceiver found at address 17.
eth0: Unknown PHY transceiver found at address 18.
eth0: Unknown PHY transceiver found at address 19.
eth0: Unknown PHY transceiver found at address 20.
eth0: Unknown PHY transceiver found at address 21.
eth0: Unknown PHY transceiver found at address 22.
eth0: Unknown PHY transceiver found at address 23.
eth0: Unknown PHY transceiver found at address 24.
eth0: Unknown PHY transceiver found at address 25.
eth0: Unknown PHY transceiver found at address 26.
eth0: Unknown PHY transceiver found at address 27.
eth0: Unknown PHY transceiver found at address 28.
eth0: Unknown PHY transceiver found at address 29.
eth0: Unknown PHY transceiver found at address 30.
eth0: Unknown PHY transceiver found at address 31.
eth0: Using transceiver found at address 30 as default
eth0: SiS 900 PCI Fast Ethernet at 0xdc00, IRQ 19, 00:10:dc:8f:a9:ac.
next prev parent reply other threads:[~2004-05-13 17:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 18:28 problem with sis900 driver 2.6.5 + mike
2004-05-11 18:41 ` Luiz Fernando N. Capitulino
2004-05-11 21:40 ` Daniele Venzano
2004-05-12 9:37 ` mike
2004-05-11 19:01 ` problem with sis900 Dominik Karall
2004-05-11 21:45 ` Daniele Venzano
2004-05-11 22:30 ` Dominik Karall
2004-05-13 15:17 ` Daniele Venzano
2004-05-13 18:02 ` Dominik Karall [this message]
2004-05-15 7:12 ` Daniele Venzano
2004-05-15 12:12 ` Dominik Karall
2004-05-15 16:56 ` Daniele Venzano
2004-05-16 11:21 ` Dominik Karall
2004-05-17 11:35 ` Dominik Karall
2004-05-12 0:50 ` problem with sis900 driver 2.6.5 + Aristeu Sergio Rozanski Filho
2004-05-12 10:18 ` mike
2004-05-12 10:19 ` mike
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=200405132002.56402.dominik.karall@gmx.net \
--to=dominik.karall@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=webvenza@libero.it \
/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®