Package: dahdi-source
Version: 1:2.10.0.1~dfsg-1
Severity: important
Dear Maintainer,
i recently upgraded upgraded the kernel. this got me from
dahdi-modules-3.2.0-4-486 1:2.6.1+dfsg2-1+3.2.63-2+deb7u2
to
dahdi-modules-3.16.0-4-586:i386 1:2.10.0.1~dfsg-1+3.16.7-ckt2-1
as far as i can tell nothing else has changed.
now my hardware (and asterisk) refuses to work with 3.16, while everything is
still fine after rebooting to 3.2.
00:0c.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN
interface
Subsystem: OpenVox Communication Co. Ltd. OpenVox A400P 4-port analog
card
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (250ns min, 32000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 1800 [size=256]
Region 1: Memory at fe038000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA
PME(D0+,D1-,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: wctdm
a problem is reported when loading the module. during boot i get
[ 251.981207] dahdi: Version: 2.10.0.1
[ 251.999619] dahdi: Telephony Interface Registered on major 196
[ 252.461238] dahdi: Warning: Span WCTDM/4 didn't specify a spantype. Please
fix driver!
upon "/etc/init.d/dahdi restart" i get the same messages again. i do not know
what a spantype is, or how to fix the driver. anyway, the location of the
source is drivers/dahdi/dahdi-base.c
[..]
if (span->spantype == SPANTYPE_INVALID) {
module_printk(KERN_NOTICE,
"Warning: Span %s didn't specify a spantype. "
"Please fix driver!\n", span->name);
}
[..]
dahdi_scan does not print anything (i think it should know about the card),
dahdi_cfg -vvv prints
"""
DAHDI Tools Version - 2.10.0.1
Timeout waiting for all spans to be assigned.
DAHDI Version: 2.10.0.1
Echo Canceller(s): OSLEC
Configuration
======================
Channel map:
Channel 01: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 01)
Channel 02: FXO Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 02)
Channel 03: FXO Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 03)
Channel 04: FXO Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 04)
4 channels to configure.
DAHDI_CHANCONFIG failed on channel 1: Invalid argument (22)
Selected signaling not supported
Possible causes:
FXS signaling is being used on a FXS interface (use a FXO signaling
variant)
RBS signaling is being used on a E1 CCS span
Signaling is being assigned to channel 16 of an E1 CAS span
"""
and in the log i get
[ 5857.734447] dahdi_ioctl_chanconfig: No channel for number 1
the span related "Timeout" looks related to the missing spantype...
i'd be happy to provide more information. i do not know where to look right
now.
thanks
felix
-- System Information:
Debian Release: 6.0.5
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i586)
Kernel: Linux 3.16.0-4-586
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages dahdi-source depends on:
ii bzip2 1.0.5-6+squeeze1
ii debhelper 9.20120909
ii module-assistant 0.11.7
Versions of packages dahdi-source recommends:
ii dahdi-linux 1:2.10.0.1~dfsg-1
dahdi-source suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
