Bug#922008: wct4xxp: fails to initialize card, Unknown symbols
I found some workaround for this problem from https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1703711: Add these lines to /usr/src/dahdi-2.11.1.0.20170917~dfsg-5/dkms.conf: BUILT_MODULE_NAME[32]="oct612x" BUILT_MODULE_LOCATION[32]="drivers/dahdi/oct612x/" DEST_MODULE_LOCATION[32]="/kernel/drivers/telephony/dahdi" and rebuild/reinstall modules: # dkms build dahdi/2.11.1.0.20170917~dfsg-5 # dkms install dahdi/2.11.1.0.20170917~dfsg-5 p.s. Also had to correct the scripts in /usr/sbin/dahdi* changing $device/spantype to $device/dahdi_spantype: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916577
Bug#922008: wct4xxp: fails to initialize card, Unknown symbols
12.02.2019 21:02, Jakob Haufe wrote: I just did a quick test on a buster box which revealed to following problem: dahdi-dkms is building BUT NOT INSTALLING oct612x.ko which is containing those symbols. OTOH dahdi-source via module-assistant is installing it, making it possible to load wct4xxp. So it seems oct612x (and maybe others, didn't verify) need to be added to dkms.conf to make it on-par with dahdi-source. It looks like it is: # grep oct612x /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/4.19.0-2-amd64/x86_64/log/make.log CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_adpcm_chan.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_open.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_stats.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_conf_bridge.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_debug.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_events.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_interrupts.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_memory.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_miscellaneous.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_mixer.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_phasing_tsst.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_playout_buf.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_remote_debug.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tlv.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tone_detection.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsi_cnct.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsst.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/apilib/bt/octapi_bt0.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/apilib/largmath/octapi_largmath.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/apilib/llman/octapi_llman.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/oct612x-user.o LD [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/oct612x.o CC /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/oct612x.mod.o LD [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-5/build/drivers/dahdi/oct612x/oct612x.ko # ls -1 /usr/lib/modules/4.19.0-2-amd64/updates/dkms/ | grep oct612x | wc -l 0
Bug#922008: wct4xxp: fails to initialize card, Unknown symbols
On Tue, 12 Feb 2019 17:25:00 +0100 Geert Stappers wrote: > > [359317.396908] dahdi: Telephony Interface Unloaded > > [359362.752504] dahdi: Version: 2.11.1.0.20170917 > > [359362.753365] dahdi: Telephony Interface Registered on major 196 > > [359362.755683] wct4xxp: Unknown symbol > > Oct6100ApiGetCapacityPinsDef (err -2) [359362.755719] wct4xxp: > > Unknown symbol Oct6100EventGetTone (err -2) [359362.755763] > > wct4xxp: Unknown symbol Oct6100ChannelModify (err -2) > > [359362.755799] wct4xxp: Unknown symbol Oct6100EventGetToneDef (err > > -2) > > That seems references to other DAHDI hardware I just did a quick test on a buster box which revealed to following problem: dahdi-dkms is building BUT NOT INSTALLING oct612x.ko which is containing those symbols. OTOH dahdi-source via module-assistant is installing it, making it possible to load wct4xxp. So it seems oct612x (and maybe others, didn't verify) need to be added to dkms.conf to make it on-par with dahdi-source. Cheers, sur5r pgpyEDEFVaEAn.pgp Description: OpenPGP digital signature
Bug#922008: wct4xxp: fails to initialize card, Unknown symbols
On Tue, Feb 12, 2019 at 11:16:43AM +0300, Ilya Demyanov wrote: > 12.02.2019 9:56, Geert Stappers wrote: > > And what is the relevant part in dmesg ? > > The same as in the original message: Sorry, I have missed that. > [359317.396908] dahdi: Telephony Interface Unloaded > [359362.752504] dahdi: Version: 2.11.1.0.20170917 > [359362.753365] dahdi: Telephony Interface Registered on major 196 > [359362.755683] wct4xxp: Unknown symbol Oct6100ApiGetCapacityPinsDef (err -2) > [359362.755719] wct4xxp: Unknown symbol Oct6100EventGetTone (err -2) > [359362.755763] wct4xxp: Unknown symbol Oct6100ChannelModify (err -2) > [359362.755799] wct4xxp: Unknown symbol Oct6100EventGetToneDef (err -2) That seems references to other DAHDI hardware
Bug#922008: wct4xxp: fails to initialize card
12.02.2019 9:56, Geert Stappers wrote: And what is the relevant part in dmesg ? The same as in the original message: [359317.396908] dahdi: Telephony Interface Unloaded [359362.752504] dahdi: Version: 2.11.1.0.20170917 [359362.753365] dahdi: Telephony Interface Registered on major 196 [359362.755683] wct4xxp: Unknown symbol Oct6100ApiGetCapacityPinsDef (err -2) [359362.755719] wct4xxp: Unknown symbol Oct6100EventGetTone (err -2) [359362.755763] wct4xxp: Unknown symbol Oct6100ChannelModify (err -2) [359362.755799] wct4xxp: Unknown symbol Oct6100EventGetToneDef (err -2) [359362.755841] wct4xxp: Unknown symbol Oct6100ToneDetectionEnable (err -2) [359362.755881] wct4xxp: Unknown symbol Oct6100ApiGetCapacityPins (err -2) [359362.755918] wct4xxp: Unknown symbol Oct6100InterruptServiceRoutineDef (err -2) [359362.755947] wct4xxp: Unknown symbol Oct6100ChipOpenDef (err -2) [359362.755974] wct4xxp: Unknown symbol Oct6100GetInstanceSizeDef (err -2) [359362.756002] wct4xxp: Unknown symbol Oct6100InterruptServiceRoutine (err -2) [359362.756062] wct4xxp: Unknown symbol Oct6100ChannelModifyDef (err -2) [359362.756098] wct4xxp: Unknown symbol Oct6100GetInstanceSize (err -2) [359362.756139] wct4xxp: Unknown symbol Oct6100ChipCloseDef (err -2) [359362.756171] wct4xxp: Unknown symbol Oct6100ChannelOpenDef (err -2) [359362.756198] wct4xxp: Unknown symbol Oct6100ChipClose (err -2) [359362.756234] wct4xxp: Unknown symbol Oct6100ChipOpen (err -2) [359362.756271] wct4xxp: Unknown symbol Oct6100ToneDetectionEnableDef (err -2) [359362.756300] wct4xxp: Unknown symbol Oct6100ChannelOpen (err -2)
Bug#922008: wct4xxp: fails to initialize card
On Mon, Feb 11, 2019 at 03:24:49PM +0300, Ilya Demyanov wrote: > # modprobe wct4xxp > modprobe: ERROR: could not insert 'wct4xxp': Unknown symbol in module, or > unknown parameter (see dmesg) > # And what is the relevant part in dmesg ?
Bug#922008: wct4xxp: fails to initialize card
On Mon, 11 Feb 2019 11:04:28 +0200 Tzafrir Cohen wrote: > Hi, > I'm not really sure what the problem is, but just to rule out one thing: maybe you have old and incompatible modules loaded? Hello. This is a fresh install from testing image. No other version dahdi has been installed before. > Try: > /usr/share/dahdi/dahdi-modules unload # hopefully no typo here > modprobe wct4xxp # ls -1 /usr/share/dahdi/ astribank_hook dahdi_auto_assign_compat dahdi_handle_device dahdi_span_config handle_device.d init_card_1_30 init_card_2_30 init_card_3_30 init_card_4_30 init_card_5_30 init_card_6_30 span_config.d waitfor_xpds XppConfig.pm xpp_fxloader # # lsmod | grep dahdi dahdi 245760 0 crc_ccitt 16384 1 dahdi # rmmod dahdi # lsmod | grep dahdi | wc -l 0 # modprobe wct4xxp modprobe: ERROR: could not insert 'wct4xxp': Unknown symbol in module, or unknown parameter (see dmesg) #
Bug#922008: wct4xxp: fails to initialize card
Hi, I'm not really sure what the problem is, but just to rule out one thing: maybe you have old and incompatible modules loaded? Try: /usr/share/dahdi/dahdi-modules unload # hopefully no typo here modprobe wct4xxp -- Tzafrir
Bug#922008: wct4xxp: fails to initialize card
Package: dahdi-linux Version: 1:2.11.1.0.20170917~dfsg-5 Severity: important Dear Maintainer, Debian Buster fails to initialize span digital card: $ lspci | grep Digium 1b:08.0 Communication controller: Digium, Inc. Wildcard TE820 octal-span T1/E1/J1 card 3.3V (PCI-Express) (rev 02) $ sudo modprobe wct4xxp modprobe: ERROR: could not insert 'wct4xxp': Unknown symbol in module, or unknown parameter (see dmesg) dmesg: [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100EventGetTone (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100ChannelModify (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100EventGetToneDef (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100ToneDetectionEnable (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100ApiGetCapacityPins (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100InterruptServiceRoutineDef (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100ChipOpenDef (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100GetInstanceSizeDef (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100InterruptServiceRoutine (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100ChannelModifyDef (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100GetInstanceSize (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100ChipCloseDef (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100ChannelOpenDef (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100ChipClose (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100ChipOpen (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100ToneDetectionEnableDef (err -2) [Mon Feb 11 10:59:55 2019] wct4xxp: Unknown symbol Oct6100ChannelOpen (err -2) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dahdi-linux depends on: ii dahdi-dkms 1:2.11.1.0.20170917~dfsg-5 ii fxload 0.0.20081013-1+b2 ii procps 2:3.3.15-2 dahdi-linux recommends no packages. dahdi-linux suggests no packages. -- no debconf information