Ian K wrote:
> To be honest, the best thing I can do is probably forward you to the
> forum thread, and ask
> you to reply here. The URL is here:
>
Ok, so from the forum, I found this, which is I am guessing about where
you got stuck:
> Yenta: Cardbus bridge found at 0000:00:03.0 [10f7:832f]
> Yenta: ISA IRQ mask 0x0830, PCI irq 9
> Socket status: 30000820
> irq 9: nobody cared!
> lots of hexidecimal stuff, tabbed a little after 'irq 9: nobody
> cared'. If you need this, Ill type it out for you.
>
> handlers:
> omitting some modules because they are ALSA related, and not relevant
> [<c89978a0>] (yenta_interrupt+0x0/0x40 [yenta_socket])
> Disabling IRQ #9
What I get is:
Jun 20 07:12:51 carcharias PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
Jun 20 07:12:51 carcharias ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
Jun 20 07:12:51 carcharias PCI: setting IRQ 11 as level-triggered
Jun 20 07:12:51 carcharias ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 11
(level, low) -> IRQ 11
Jun 20 07:12:51 carcharias Yenta: CardBus bridge found at 0000:03:00.0
[1558:0500]
Jun 20 07:12:51 carcharias Yenta: Using CSCINT to route CSC interrupts
to PCI
Jun 20 07:12:51 carcharias Yenta: Routing CardBus interrupts to PCI
Jun 20 07:12:51 carcharias Yenta TI: socket 0000:03:00.0, mfunc
0x00001002, devctl 0x44
Jun 20 07:12:51 carcharias Yenta: ISA IRQ mask 0x0000, PCI irq 11
With nothing after that about dropped interrupts or anything.
Ok, so let's talk about your kernel configuration. Do you have ACPI
enabled in your kernel? If so, what ACPI options do you have? (grep
_ACPI .config).
Also, looking at the yenta driver, it seems there are two options you
can try if yenta is built as a module. Try one or both of these:
rmmod yenta_socket
insmod yenta_socket [override_bios=1] [disable_clkrun=1]
-Richard
--
gentoo-user@gentoo.org mailing list
