Lan Barnes wrote:
On Fri, November 23, 2007 3:08 pm, DJA wrote:
Still want to know laptop brand. This may also be an issue with whatever
mechanism enables the chip, e.g. ACPI or tools specific to your brand an
model.
Great Quality NX-L515
Any indication from dmesg or the logs that the card was recognized at
F8
boot up?
dmesg in its entirety
**********************
Linux version 2.6.23.1-42.fc8
([EMAIL PROTECTED]) (gcc version 4.1.2
20070925 (Red Hat 4.1.2-3
3)) #1 SMP Tue Oct 30 13:55:12 EDT 2007
[snip]
ACPI: bus type pci registered
PCI: BIOS BUG #81[00000000] found
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: EC: GPE = 0x11, I/O: command/status = 0x66, data = 0x62
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Transparent bridge - 0000:00:14.4
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PB4_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKU] (IRQs 3 4 5 7) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 10 devices
ACPI: ACPI bus type pnp unregistered
[snip]
This is absolutely bizarre. I have NEVER seen a system without PCI
interrupts being assigned when the system has a PCI bus. Possible causes
are the BIOS ACPI tables being hosed, the ACPI drivers in the Linux
kernel being buggy, or a problem with the local APIC.
What do you get when you do:
$ cat /proc/interrupts
Try modifying the boot parameters to add "noapic noacpi" and see if that
affects the interrupt assignment.
Gus
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
