[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#497392: e1000e driver does not initialize correctly



On Mon, Sep 01, 2008 at 02:22:00PM +0200, Bastien Durel wrote:
> The e1000e kernel module does not initialize correctly, then the network cannot initialize.

Please explain, the attached log does not show strange e1000 related
messages.

> 00:19.0 Ethernet controller [0200]: Intel Corporation 82562V-2 10/100 Network Connection [8086:10c0] (rev 02)
> 	Subsystem: Dell Device [1028:0238]

Which sort of controller is this?

> 	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
> 	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> 	Latency: 0
> 	Interrupt: pin A routed to IRQ 222
> 	Region 0: Memory at fdfc0000 (32-bit, non-prefetchable) [size=128K]
> 	Region 1: Memory at fdfff000 (32-bit, non-prefetchable) [size=4K]
> 	Region 2: I/O ports at fe00 [size=32]
> 	Capabilities: <access denied>
> 	Kernel driver in use: e1000e
> 	Kernel modules: e1000e

Mine is know to work.

02:00.0 Ethernet controller [0200]: Intel Corporation 82573L Gigabit Ethernet Controller [8086:109a]
        Subsystem: Lenovo Device [17aa:207e]
        Flags: bus master, fast devsel, latency 0, IRQ 218
        Memory at ee000000 (32-bit, non-prefetchable) [size=128K]
        I/O ports at 2000 [size=32]
        Capabilities: <access denied>
        Kernel driver in use: e1000e
        Kernel modules: e1000e

Bstian

-- 
Too much of anything, even love, isn't necessarily a good thing.
		-- Kirk, "The Trouble with Tribbles", stardate 4525.6



Reply to: