[asterisk-users] No hardware timing source found in /proc/dahdi

John Millican jmillican at sentinelcommunications.com
Sun Mar 15 18:19:44 CDT 2009


Shaun Ruffell wrote:
> John Millican wrote:
>  > # /etc/init.d/dahdi start
>  > Loading DAHDI hardware modules:
>  >   wctdm:  modprobe wctdm
> 
> What is the output of the 'dmesg' command at this point?
> 
>  >
>  > No hardware timing source found in /proc/dahdi, loading dahdi_dummy
>  > Running dahdi_cfg:  /usr/sbin/dahdi_cfg
> 
> If the dmesg shows that the driver found the card and there were not any 
> conflicts, and dahdi_dummy is still loaded, this could be the result of 
>   an open reference to the old /proc/dahdi directory.
> 
> i.e., you can force this to happen if you
> 
> 'modprobe dahdi && cd /proc/dahdi && modprobe -r dahdi && 
> /etc/init.d/dahdi start'
> 
> 
> Cheers,
> Shaun
All I see in dmesg is:
dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.1.0.4
dahdi_dummy: RTC rate is 1024


-- 
JohnM




More information about the asterisk-users mailing list