Allan, Bruce W wrote:
> Just because it is enabled in the kernel config file does not mean it is
> in reality enabled in the kernel. I have seen kernels from RedHat in
> which MSI is explicitly disabled no matter what CONFIG_PCI_MSI is set
> to. One method that might enable it is to add pci=msi t
[EMAIL PROTECTED] [mailto:e1000-devel-
>[EMAIL PROTECTED] On Behalf Of Richard Scobie
>Sent: Wednesday, May 21, 2008 8:59 PM
>To: Tantilov, Emil S
>Cc: e1000-devel@lists.sourceforge.net
>Subject: Re: [E1000-devel] e1000e MSI
>
>Tantilov, Emil S wrote:
>> Check your kernel conf
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 :0f:00.1 disabled
A
Tantilov, Emil S wrote:
> cat /proc/cmdline?
>
> are you using the e1000e with the kernel or from e1000.sf.net?
>
> 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
Message-
From: Richard Scobie [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 21, 2008 8:59 PM
To: Tantilov, Emil S
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] e1000e MSI
Tantilov, Emil S wrote:
> Check your kernel configuration - CONFIG_PCI_MSI should be enabled.
>
Tantilov, Emil S wrote:
> Check your kernel configuration - CONFIG_PCI_MSI should be enabled.
>
> The driver defaults to MSI.
>
> Thanks,
> Emil
Hi Emil,
Yes, this is enabled in this kernel, so that's a mystery.
cat /boot/config-2.6.25.3-18.fc9.x86_64 |grep CONFIG_PCI_MSI
CONFIG_PCI_MSI=y
R
Check your kernel configuration - CONFIG_PCI_MSI should be enabled.
The driver defaults to MSI.
Thanks,
Emil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard
Scobie
Sent: Wednesday, May 21, 2008 7:46 PM
To: e1000-devel@lists.sourceforge.net
Subje
