Richard Fish wrote: >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). > > > For my own typing ease, I will place everything in uppercase. CONFIG_ACPI=Y CONFIG_ACPI_BOOT=Y CONFIG_ACPI_INTERPERETER=Y CONFIG_ACPI_SLEEP=Y CONFIG_ACPI_SLEEP_PROC_FS=Y CONFIG_ACPI_AC=Y CONFIG_ACPI_BATTERY=Y CONFIG_ACPI_BUTTON=Y CONFIG_ACPI_VIDEO=M CONFIG_ACPI_FAN=Y CONFIG_ACPI_PROCESSOR=Y CONFIG_ACPI_THERMAL=Y # CONFIG_ACPI_ASUS IS NOT SET # CONFIG_ACPI_IBM IS NOT SET # CONFIG_ACPI_TOSHIBA IS NOT SET CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG IS NOT SET CONFIG_ACPI_BUS=Y CONFIG_ACPI_EC=Y CONFIG_ACPI_POWER=Y CONFIG_ACPI_PCI=Y CONFIG_ACPI_SYSTEM=Y # CONFIG_ACPI_CONTAINER IS NOT SET # CONFIG_HOTPLUG_PCI_ACPI IS NOT SET # CONFIG_SERIAL_8250_ACPI IS NOT SET
>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 > > ERROR: Module yenta_socket does not exist in /proc/modules # ***It does however work when I modprobe it regularly though.*** > insmod yenta_socket [override_bios=1] [disable_clkrun=1] > > insmod: can't read 'yenta_socket': No such file or directory >-Richard > > > Thanks for your continued help. Its midnight where I am, so Im going to sleep, but I will look forward to your reply in less than 12 hours. Ian
begin:vcard fn:Ian K n:K;Ian email;internet:[EMAIL PROTECTED] note;quoted-printable:Pentium 3=0D=0A= 500mHz=0D=0A= 256MB RAM=0D=0A= 80.0GB HDD=0D=0A= ATI Radeon 7000 Evil Wizard 64MB=0D=0A= Computer name: "PentaQuad"=0D=0A= x-mozilla-html:TRUE version:2.1 end:vcard
