From: Roland Dreier <roland@topspin.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Michael.Waychison@Sun.COM, plars@linuxtestproject.org,
Brian.Somers@Sun.COM, linux-kernel@vger.kernel.org
Subject: Re: TG3 doesn't work in kernel 2.4.27 (David S. Miller)
Date: Fri, 03 Sep 2004 16:24:25 -0700 [thread overview]
Message-ID: <52ekljq6l2.fsf@topspin.com> (raw)
In-Reply-To: <20040903133059.483e98a0.davem@davemloft.net> (David S. Miller's message of "Fri, 3 Sep 2004 13:30:59 -0700")
David> Please make sure you try current sources, I've had nothing
David> but positive reports for IBM blades from people actually
David> using the correct current 3.9 driver.
I tried it with a full build of a BK tree pulled last night, and it
definitely didn't work. Some relevant output:
tg3.c:v3.9 (August 30, 2004)
eth0: Tigon3 [partno(none) rev 2003 PHY(serdes)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:60:1e:88:56
eth0: HostTXDS[1] RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
eth1: Tigon3 [partno(none) rev 2003 PHY(serdes)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:60:1e:88:57
eth1: HostTXDS[1] RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
and then as soon as the init scripts try to bring up the interface:
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8 done
dummy0
dummy0 No configuration found for dummy0 unused
eth0 device: Broadcom Corporation NetXtreme BCM5
system>
system> console -T system:blade[11]
SOL is not ready
(the last three lines are the management console taking over again
after the serial-over-LAN has died)
Just to be clear, I'm running a ppc64 kernel on a JS20 blade (dual PPC
970) with BCM5704S. The HS20 blade (dual Xeon) also has a BCM5703X
but I haven't tried the latest driver on one of those yet.
Thanks,
Roland
next prev parent reply other threads:[~2004-09-03 23:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040816110000.1120.31256.Mailman@lists.us.dell.com>
2004-08-16 11:51 ` TG3 doesn't work in kernel 2.4.27 (David S. Miller) Tetsuo Handa
2004-08-16 21:38 ` David S. Miller
2004-08-25 17:48 ` Mike Waychison
2004-08-25 19:08 ` David S. Miller
2004-08-25 20:04 ` Mike Waychison
2004-08-26 0:58 ` David S. Miller
2004-08-26 10:49 ` Brian Somers
2004-08-26 19:37 ` David S. Miller
2004-08-29 9:56 ` Pekka Pietikainen
2004-09-10 12:35 ` Brian Somers
2004-09-10 19:40 ` Roland Dreier
2004-09-10 20:53 ` David S. Miller
2004-09-10 21:05 ` Roland Dreier
2004-09-10 21:45 ` David S. Miller
2004-09-10 22:14 ` Brian Somers
2004-08-30 23:11 ` David S. Miller
2004-09-03 19:12 ` Paul Larson
2004-09-03 19:19 ` Mike Waychison
2004-09-03 20:18 ` Roland Dreier
2004-09-03 20:30 ` David S. Miller
2004-09-03 20:40 ` Roland Dreier
2004-09-03 23:24 ` Roland Dreier [this message]
2004-09-07 18:33 ` Jake Moilanen
2004-09-07 19:52 ` Roland Dreier
2004-09-08 12:34 ` Jake Moilanen
2004-09-08 13:07 ` Anton Blanchard
2004-09-13 22:48 ` David S. Miller
2004-09-14 22:20 ` Mike Waychison
2004-09-14 22:36 ` David S. Miller
2004-09-14 22:58 ` Jake Moilanen
2004-09-15 0:34 ` Roland Dreier
2004-09-08 13:55 ` Paul Larson
2004-09-10 16:00 ` Paul Larson
2004-09-03 20:08 ` David S. Miller
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=52ekljq6l2.fsf@topspin.com \
--to=roland@topspin.com \
--cc=Brian.Somers@Sun.COM \
--cc=Michael.Waychison@Sun.COM \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@linuxtestproject.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