Tantilov, Emil S wrote: > > Also check dmesg after loading the driver - that should give some > messages about not being able to obtain MSI interrupts. These types of > issues are usually kernel/config related.
On loading the module, I get: ACPI: PCI interrupt for device 0000:0f:00.1 disabled ACPI: PCI interrupt for device 0000:0f:00.0 disabled ACPI: PCI interrupt for device 0000:04:00.1 disabled ACPI: PCI interrupt for device 0000:04:00.0 disabled ACPI: PCI interrupt for device 0000:03:00.1 disabled ACPI: PCI interrupt for device 0000:03:00.0 disabled e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0 e1000e: Copyright (c) 1999-2007 Intel Corporation. ACPI: PCI Interrupt 0000:03:00.0[B] -> GSI 17 (level, low) -> IRQ 17 PCI: Setting latency timer of device 0000:03:00.0 to 64 eth0: (PCI Express:2.5GB/s:Width x4) 00:15:17:75:e1:6d eth0: Intel(R) PRO/1000 Network Connection eth0: MAC: 0, PHY: 4, PBA No: d72468-003 ACPI: PCI Interrupt 0000:03:00.1[A] -> GSI 16 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:03:00.1 to 64 eth1: (PCI Express:2.5GB/s:Width x4) 00:15:17:75:e1:6c eth1: Intel(R) PRO/1000 Network Connection eth1: MAC: 0, PHY: 4, PBA No: d72468-003 ACPI: PCI Interrupt 0000:04:00.0[B] -> GSI 18 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:04:00.0 to 64 eth2: (PCI Express:2.5GB/s:Width x4) 00:15:17:75:e1:6f eth2: Intel(R) PRO/1000 Network Connection eth2: MAC: 0, PHY: 4, PBA No: d72468-003 ACPI: PCI Interrupt 0000:04:00.1[A] -> GSI 17 (level, low) -> IRQ 17 PCI: Setting latency timer of device 0000:04:00.1 to 64 eth3: (PCI Express:2.5GB/s:Width x4) 00:15:17:75:e1:6e eth3: Intel(R) PRO/1000 Network Connection eth3: MAC: 0, PHY: 4, PBA No: d72468-003 ACPI: PCI Interrupt 0000:0f:00.0[A] -> GSI 18 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:0f:00.0 to 64 eth4: (PCI Express:2.5GB/s:Width x4) 00:e0:81:b0:80:d4 eth4: Intel(R) PRO/1000 Network Connection eth4: MAC: 3, PHY: 5, PBA No: ffffff-0ff ACPI: PCI Interrupt 0000:0f:00.1[B] -> GSI 19 (level, low) -> IRQ 19 So I guess the next thing would be to try the latest sourceforge driver. Regards, Richard ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
