Summary: | ASTERISK-03462: missing subsystem id in wcte11xp.c ? | ||
Reporter: | Ryan Courtnage (rcourtna) | Labels: | |
Date Opened: | 2005-02-09 11:38:46.000-0600 | Date Closed: | 2011-06-07 14:10:27 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Installed a TE110P. After boot, lspci -v: 05:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Subsystem: Unknown device 79fe:0001 .. and I was able to modprobe wcte11xp. However, the system was rebooted (hard-boot). I was then unable to modprobe wcte11xp: [root@asterisk src]# /sbin/modprobe wcte11xp /lib/modules/2.4.21-27.0.2.EL/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.21-27.0.2.EL/misc/wcte11xp.o: insmod /lib/modules/2.4.21-27.0.2.EL/misc/wcte11xp.o failed /lib/modules/2.4.21-27.0.2.EL/misc/wcte11xp.o: insmod wcte11xp failed [root@asterisk zaptel]# lspci -nvv ... 05:00.0 Class 0280: e159:0001 Subsystem: 795e:0001 I noticed that 795e is not listed on line 1527 of wcte11xp.c. I tried simply adding 0x795e to that line and recompiled, but I still could not modprobe (same error). Luckily, after another hard boot, the TE110P got supsystem 79fe back. ****** ADDITIONAL INFORMATION ****** Using latest -r v1-0 of zaptel. RHEL [root@asterisk zaptel]# uname -r 2.4.21-27.0.2.EL | ||
Comments: | By: Serge Vecher (serge-v) 2005-02-09 14:02:31.000-0600 Did you 'modprobe zaptel' prior to 'modprobe wcte11xp'? Serge By: Ryan Courtnage (rcourtna) 2005-02-09 14:56:59.000-0600 No I didn't - AFAIK, that is not necessary. FYI, this is the _exact_ same issue that was reported by somebody else a few weeks ago: http://www.mail-archive.com/asterisk-users@lists.digium.com/msg71100.html According to that thread, Digium has acknowledged the problem exists. By: Mark Spencer (markster) 2005-02-09 15:06:45.000-0600 This is a technical support issue, please pursue this through support@digium.com. |