Well. That means pci_register_driver probably not ding what it supposed to do. In newer kernels pci_module_init should be replaced with pci_register_driver as pci_module_init doesn't it what it supposed to. How brave are you at getting a new kernel on your system? I'm currently running on 2.6.13 on 955X chipset and it works really well. At first I had all sorts of problems with interrupts but with couple of patches to wct4xxp all working just fine with close to 3-5K of calls per day.
What is the model of the motherboard you have? See if you can force a particular IRQ on a slot where your TE406P is. Some motherboards do allow this, so you can assign IRQ bellow 15 to the card. That could help as well. For now, revert the changes back. If you can, try new kernel (in parallel) with the pci_register_driver. Regards > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:asterisk-users- > [EMAIL PROTECTED] On Behalf Of Jason Kim > Sent: Monday, 12 September 2005 11:28 > To: asterisk-users@lists.digium.com > Subject: RE: [Asterisk-Users] TE406p no interrupts > > I modified wct4xxp.c and installed it. > This is the message for 'modprobe wct4xxp' > > -------------------------------------------------- > FATAL: Error inserting wct4xxp > (/lib/modules/2.6.9-1.667smp/extra/wct4xxp.ko): No > such device > FATAL: Error running install command for wct4xxp > astpbx kernel: Oops: 0000 [1] SMP > astpbx kernel: CR2: ffffffffa0362081 > > Regards, > Jason _______________________________________________ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users