I got a reply from Digium support. They knew about this problem and are trying to find a fix in hardware. Meanwhile, the only solution right now is to find out what the subsystem ID has changed to and add those new ID's to the wcte11xp.c source code so that they will be recognized by the driver.
On Fri, 14 Jan 2005 15:08:25 -0800, Asterisk List <[EMAIL PROTECTED]> wrote: > I encountered the same problem today. 'lspci -nvv' showed that the > subsystem ID of the TE110p changed from 79fe to 79fa or 797e. > Powering off/on the machine restored the subsystem ID to 79fe and the > wcte11xp module could then load. I already emailed digium support for > this. > > > On Mon, 20 Dec 2004 11:32:15 +0100, Tamas J <[EMAIL PROTECTED]> wrote: > > > > > > Hello! > > > > I discovered, that I'm unable to load ther kernel module under 2.4.28. > > Before that I had 2.4.26 and tryed to upgrade the kernel to 2.4.28. > > After restart (reboot - soft restart) I can't load the module. When I > > go back to 2.4.26 and try to load the module, I'm getting the same > > problem. > > Only turning off/on helps. What can I do? It's very annoying because > > the box is in hosting and not easy to just restart. > > > > The wct1xxp worked fine in the same box (with restarts also). > > > > Any idea, hint? > > > > Kind regards, > > Tamas > > > > modprobe wcte11xp > > /lib/modules/2.4.28-magic/misc/wcte11xp.o: init_module: No such device > > Hint: insmod errors can be caused by incorrect module parameters, including > > invalid IO or IRQ parameters. > > You may find more information in syslog or the output from dmesg > > /lib/modules/2.4.28-magic/misc/wcte11xp.o: insmod > > /lib/modules/2.4.28-magic/misc/wcte11xp.o failed > > /lib/modules/2.4.28-magic/misc/wcte11xp.o: insmod wcte11xp failed > > _______________________________________________ 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
