From: Eric Whiting <ewhiting@amis.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org
Subject: e1000 in 2.6.1-mm1 -- still broken?
Date: Fri, 09 Jan 2004 13:52:14 -0700 [thread overview]
Message-ID: <3FFF147E.F68F246D@amis.com> (raw)
I'm having trouble with e1000 in -mm1. (works in 2.6.1) The device is detected
and shows up and can be configured, but nothing ever goes out on the wire.
Here is the device info:
07:01.1 Ethernet controller: Intel Corporation: Unknown device 1010 (rev 01)
Subsystem: Intel Corporation: Unknown device 1011
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 49
Memory at fe9e0000 (64-bit, non-prefetchable) [size=128K]
I/O ports at dc00 [size=64]
Capabilities: [dc] Power Management version 2
Capabilities: [e4] PCI-X non-bridge device.
Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable-
tcpdump shows no activity when I attempt to use the e1000 interface.
next reply other threads:[~2004-01-09 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 20:52 Eric Whiting [this message]
2004-01-09 21:56 ` e1000 in 2.6.1-mm1 -- still broken? Andrew Morton
2004-01-09 22:03 ` Jeff Garzik
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=3FFF147E.F68F246D@amis.com \
--to=ewhiting@amis.com \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox