nvnet not working with acpi on.

[cko]

I purchased an Abit NF7 nforce2 main board today and tried to get the nforce-1.0-0261 drivers to work with it.

I am running SuSE 8.2 (kernel 2.4.20).

Yast2 automatically recognized the hardware and added the line

alias eth0 nvnet

to /etc/modules.conf.

However, ping reported "destination host unreachable" for all hosts on my LAN, except for localhost.

When I boot with "acpi=off", the network works fine.

Is this a known bug?

If yes, when will it be fixed?

[geowiz]

ACPI and the various Nforce2 chipsets don't play well together. ACPI is listed as "experimental" code in the kernel. My suggestion would be to pass ACPI=off to the kernel and avoid a lot of trouble.

If you don't need ACPI, give it a pass. The whole ACPI section of the kernel is being/has been reworked in 2.4.2X and in the 2.6.0 series and it doesn't appear to be ready for prime time with the Nforce2 boards.

Fix time frame - unknown by me. You can always read the kernel development threads and watch/contribute. http://hypermail.idiosynkrasia.net/linux-kernel/

[suexec]

I haven't run into problems with ACPI (and APIC/IO-APIC) with 2.4.22 and 2.6.0-test4. Both included some pci irq routing fixes.

[geowiz]

I agree with you that in 2.4.22, 2.6.0-test4 ACPI now seems to work ok with my Abit NF7-S board. When I wrote the message, neither of them was out yet (if I remember correctly).

But, many of the problems reported in the news groups seem to go back to ACPI so it is a reasonable starting point for trouble shooting (based on history).

[suexec]

Yeah, ACPI had been a big source of problems, and continue to be. Even 2.4.22/2.6.0-test4 had some issues with a nForce (1) system where it did not assign an IRQ to the integrated video though the BIOS gave it one less than 15. This required a patch that was posted to the acpi devel list to resolve.