From: "Mirko Caserta" <mirko@mcaserta.com>
To: "Linux Kernel ML" <linux-kernel@vger.kernel.org>
Subject: 8139too not working in 2.6
Date: Mon, 26 Apr 2004 13:35:27 +0200 [thread overview]
Message-ID: <opr62ahdvlpsnffn@mail.mcaserta.com> (raw)
Yes, I know, it's a damn cheap eth card and I should get it replaced :)
Besides that, this card works just fine with 2.4.25 while it refuses to
work on a recent 2.6 kernel. I tried 2.6.5 and even
2.6.5-rc2-mm2-broken-out with no luck.
The card is correctly recognized but the kernel refuses to transmit any
packet:
8139too Fast Ethernet driver 0.9.27
eth0: RealTek RTL8139 at 0xe0821000, MAC_ADDR_REMOVED, IRQ 5
eth0: Identified 8139 chip type 'RTL-8139C'
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: Transmit timeout, status 0c 0005 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 0008a03c. (queue head)
eth0: Tx descriptor 1 is 0008a03c.
eth0: Tx descriptor 2 is 0008a03c.
eth0: Tx descriptor 3 is 0008a03c.
Someone told me to play around with the driver options but the machine is
in production and I cannot play much with reboots :/
Any help would be very appreciated.
Mirko
next reply other threads:[~2004-04-26 11:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 11:35 Mirko Caserta [this message]
2004-04-26 11:41 ` 8139too not working in 2.6 David Johnson
2004-04-26 12:14 ` MNH
2004-04-26 13:29 ` Gene Heskett
2004-04-26 14:26 ` David Johnson
2004-04-26 15:53 ` OGAWA Hirofumi
2004-04-26 12:05 ` Jorge Bernal (Koke)
2004-04-26 12:13 ` David Johnson
2004-04-26 16:01 ` Jorge Bernal
2004-04-26 12:41 ` Derek Chen-Becker
2004-04-26 12:58 ` OGAWA Hirofumi
2004-04-26 14:46 ` Mirko Caserta
2004-04-26 15:14 ` OGAWA Hirofumi
2004-04-26 15:37 ` 8139too not working in 2.6 (works now) Mirko Caserta
2004-04-26 16:11 ` OGAWA Hirofumi
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=opr62ahdvlpsnffn@mail.mcaserta.com \
--to=mirko@mcaserta.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.