On Tue, 2013-06-04 at 01:32 +0000, Bjarni Ingi Gislason wrote: > On Fri, May 31, 2013 at 02:50:11AM +0100, Ben Hutchings wrote: > > Now I see this is a rather old computer (BIOS dated 1999), so I'm not so > > surprised that ACPI is not supported! > > > > Does the kernel in linux-image-3.2.0-4-486 work? > > > > Can you send a boot log and output of 'lspci -s 0000:01.2' from a > > working kernel (old or new)? > > > > "lspci -s 0000:01.2": > > 00:01.2 USB controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
Oops, sorry, I meant 'lspci -v -s 0000:01.2'. Anyway, I don't think that's needed as the boot log shows enough information. [...] > Jun 3 02:21:21 jeti kernel: [ 0.108491] pci 0000:00:01.2: reg 20 io port: > [0x00-0x1f] [...] > Jun 3 02:21:21 jeti kernel: [ 0.124483] pci 0000:00:01.2: enabling device > (0000 -> 0001) > Jun 3 02:21:21 jeti kernel: [ 0.124657] PCI: setting IRQ 5 as > level-triggered > Jun 3 02:21:21 jeti kernel: [ 0.124674] pci 0000:00:01.2: assigned PCI > INT D -> IRQ 5 [...] So there's the IRQ it should get. Now, IRQ routing is done in the file arch/x86/pci/irq.c. Add '#define DEBUG' to the top of that file to enable more detailed log messages. Since your machine doesn't have an IO-APIC, the relevant code should be in pcibios_lookup_irq(). If the log messages still aren't sufficient to work out where it fails, you could add more dev_dbg() calls there. Ben. -- Ben Hutchings Sturgeon's Law: Ninety percent of everything is crap.
signature.asc
Description: This is a digitally signed message part
