public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* e1000 in 2.6.1-mm1 -- still broken?
@ 2004-01-09 20:52 Eric Whiting
  2004-01-09 21:56 ` Andrew Morton
  2004-01-09 22:03 ` Jeff Garzik
  0 siblings, 2 replies; 3+ messages in thread
From: Eric Whiting @ 2004-01-09 20:52 UTC (permalink / raw)
  To: linux-kernel; +Cc: akpm


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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: e1000 in 2.6.1-mm1 -- still broken?
  2004-01-09 20:52 e1000 in 2.6.1-mm1 -- still broken? Eric Whiting
@ 2004-01-09 21:56 ` Andrew Morton
  2004-01-09 22:03 ` Jeff Garzik
  1 sibling, 0 replies; 3+ messages in thread
From: Andrew Morton @ 2004-01-09 21:56 UTC (permalink / raw)
  To: Eric Whiting; +Cc: linux-kernel, scott.feldman, cramerj

Eric Whiting <ewhiting@amis.com> wrote:
>
> 
> 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. 

Hum, OK.  We'd better Cc the maintainers.


> 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.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: e1000 in 2.6.1-mm1 -- still broken?
  2004-01-09 20:52 e1000 in 2.6.1-mm1 -- still broken? Eric Whiting
  2004-01-09 21:56 ` Andrew Morton
@ 2004-01-09 22:03 ` Jeff Garzik
  1 sibling, 0 replies; 3+ messages in thread
From: Jeff Garzik @ 2004-01-09 22:03 UTC (permalink / raw)
  To: Eric Whiting; +Cc: linux-kernel, akpm

Eric Whiting wrote:
> 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. 


Should be fixed when akpm updates the e1000 patch to

http://www.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.6/2.6.1-netdrvr-exp1.patch.bz2
http://www.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.6/2.6.1-netdrvr-exp1.log


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-01-09 22:03 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-09 20:52 e1000 in 2.6.1-mm1 -- still broken? Eric Whiting
2004-01-09 21:56 ` Andrew Morton
2004-01-09 22:03 ` Jeff Garzik

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox