From: "compulan" <astilley@compulan.de>
To: "Axel Siebenwirth" <axel@hh59.org>, "Axel" <axel@rayfun.org>
Cc: "Kernel Ml" <linux-kernel@vger.kernel.org>,
"Realtek Ml" <realtek@scyld.com>
Subject: Re: [realtek] Realtek 8139C: NETDEV WATCHDOG transmit timeout
Date: Thu, 23 Aug 2001 14:37:24 +0200 [thread overview]
Message-ID: <003001c12bd0$b5b64da0$ce01a8c0@CPL01> (raw)
In-Reply-To: <Pine.LNX.4.33.0108231414350.16256-100000@neon.hh59.org>
Could you stop sending this to this address, it would be greatly
appreciated. thank you. it has been going on for two days now, and we have
no use for this information. thank you.
----- Original Message -----
From: Axel Siebenwirth <axel@hh59.org>
To: Axel <axel@rayfun.org>
Cc: Kernel Ml <linux-kernel@vger.kernel.org>; Realtek Ml <realtek@scyld.com>
Sent: Thursday, August 23, 2001 2:16 PM
Subject: Re: [realtek] Realtek 8139C: NETDEV WATCHDOG transmit timeout
> I got myself the latest version of rtl8139-diag and it gave me different
> output in the chip registers! there are different values at 0x040.
>
> axel
>
> rtl8139-diag.c:v2.04 8/08/2001 Donald Becker (becker@scyld.com)
> http://www.scyld.com/diag/index.html
> Index #1: Found a RealTek RTL8139 adapter at 0xf800.
> The RealTek chip appears to be active, so some registers will not be read.
> To see all register values use the '-f' flag.
> RealTek chip registers at 0xf800
> 0x000: 26843000 0000470b 80040000 40000000 9008a03c 9008a054 9008a054
> 9008a03c
> 0x020: 03096000 03096600 03096c00 03097200 02f80000 0d0a0000 42dc42cc
> 0000c07f
> 0x040: 74000600 0e00f78e 951264c7 00000000 000d1000 00000000 008cd108
> 00100000
> 0x060: 1000f00f 01e1782d 00000000 00000000 00000005 000f77c0 b0f243b9
> 7a36d743. No interrupt sources are pending.
> The chip configuration is 0x10 0x0d, MII half-duplex mode.
> The RTL8139 does not use a MII transceiver.
> It does have internal MII-compatible registers:
> Basic mode control register 0x782d.
> Basic mode status register 0x1000.
> Autonegotiation Advertisement 0x01e1.
> Link Partner Ability register 0x0000.
> Autonegotiation expansion 0x0000.
> Disconnects 0x0000.
> False carrier sense counter 0x0000.
> NWay test register 0x0005.
> Receive frame error count 0x0000.
>
>
>
>
> _______________________________________________
> realtek mailing list
> realtek@scyld.com
> http://www.scyld.com/mailman/listinfo/realtek
>
prev parent reply other threads:[~2001-08-23 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 12:04 Realtek 8139C: NETDEV WATCHDOG transmit timeout Axel
2001-08-23 12:16 ` [realtek] " Axel Siebenwirth
2001-08-23 12:37 ` compulan [this message]
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='003001c12bd0$b5b64da0$ce01a8c0@CPL01' \
--to=astilley@compulan.de \
--cc=axel@hh59.org \
--cc=axel@rayfun.org \
--cc=linux-kernel@vger.kernel.org \
--cc=realtek@scyld.com \
/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