[asterisk-users] dahdi-2.2.1 & kernel-2.6.32: working for anyone?

[Eckhard Jokisch]

Tzafrir Cohen schrieb:
> On Sat, Mar 06, 2010 at 10:18:13PM -0500, sean darcy wrote:
>   
>> I have a TDM400. Just updated Fedora 12 to kernel 2.6.32. Rebuilt and 
>> installed dahdi-2.2.1.
>>
>> kernel modules loaded.
>> lsmod | grep wctdm
>> wctdm                  37233  0
>> dahdi                 194985  1 wctdm
>>
>>   lsmod | grep dahdi
>> dahdi                 194985  1 wctdm
>> crc_ccitt               1549  2 dahdi,isdnhdlc
>>
>> dmesg:
>>
>> dahdi: Telephony Interface Registered on major 196
>> dahdi: Version: 2.2.1
>> .....
>> dahdi_dummy: Trying to load High Resolution Timer
>> dahdi_dummy: Initialized High Resolution Timer
>> dahdi_dummy: Starting High Resolution Timer
>> dahdi_dummy: High Resolution Timer started, good to go
>>     
>
> Are you sure wctdm was loaded?
>
> What happens if you manually rmmod it and modprobe it back?
>
>   
>> which is much less dmesg on 2.6.31:
>>
>> dahdi: Telephony Interface Registered on major 196
>> dahdi: Version: 2.2.1
>> ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
>> wctdm 0000:01:05.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16
>> Freshmaker version: 73
>> Freshmaker passed register test
>> Module 0: Installed -- AUTO FXS/DPO
>> Module 1: Installed -- AUTO FXS/DPO
>> Module 2: Not installed
>> Module 3: Installed -- AUTO FXO (FCC mode)
>> Found a Wildcard TDM: Wildcard TDM400P REV I (3 modules)
>>     
>
>   

Don't know if it helps but:maybe it's a hint
on Gentoo there where problems even compiling DAHDI against kernel 
2.6.32 which turnded out to be due to some changes in linux-headers 
between 2.6.31 and 2.6.32. That might trun out to recompile glibc with 
the new er kernel

eckhard