Ian K wrote: > Richard Fish wrote: > >> Ian K wrote: >> >>> 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 >> >> 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.*** >
This is normal, I just wanted to make sure the module was removed before trying the insmod. >> insmod yenta_socket [override_bios=1] [disable_clkrun=1] >> >> > insmod: can't read 'yenta_socket': No such file or directory > Sorry, I forgot you have to give the full path to the module for insmod. The following should work better. # R=`uname -r`; module=`find /lib/modules/$R -name yenta-socket.ko` # echo $module # insmod $module override_bios=1 <check dmesg to see if you still have the "nobody cared" message> # rmmod yenta_socket # insmod $module disable_clkrun=1 <check dmesg again> A couple of other things to try for kernel boot options (add these to the kernel command line in the grub config file /boot/grub/grub.conf or the grub command shell.) noapic pci=routeirq Finally, if you have dual-boot system with Windows, see what IRQ windows assigns to the bridge. -Richard -- gentoo-user@gentoo.org mailing list