asterisk users - Mar 2009 - No hardware timing source found in /proc/dahdi

Hello all,
Ok it is Sunday afternoon and I am going crazy.  I have been running in
circles so long that I can't think straight.  As an example, I sent this
message to the wrong address the first try, AAARRRRGGGGGGHHHHH.  I have
Asterisk 1.6.0.6 and DAHDI Tools Version - 2.1.0.2,
DAHDI Version: 2.1.0.4, OpenSuSE 10.3 x86_64, tdm422
at the end of installing dahdi-linux and dahdi-tools I get:
install -D dahdi.init /etc/init.d/dahdi
/sbin/chkconfig --add dahdi
dahdi                     0:off  1:off  2:on   3:on   4:on   5:on   6:off
DAHDI has been configured.

If you have any DAHDI hardware it is now recommended you
edit /etc/dahdi/modules in order to load support for only
the DAHDI hardware installed in this system.  By default
support for all DAHDI hardware is loaded at DAHDI start.

I think that the DAHDI hardware you have on your system is:
pci:0000:03:08.0     wctdm-       e159:0001 Wildcard TDM400P REV E/F

so it is seeing the card

/etc/dahdi/system.conf:
loadzone   = us
defaultzone=us
fxoks=1,2
fxsks=3,4
echocanceller=mg2,1-4
channels=1-4

/etc/dahdi/init.conf:
MODULES="$MODULES wctdm"

/etc/dahdi/modules
# Digium TDM400P: up to 4 analog ports
wctdm

# /etc/init.d/dahdi start
Loading DAHDI hardware modules:
  wctdm:  modprobe wctdm

No hardware timing source found in /proc/dahdi, loading dahdi_dummy
Running dahdi_cfg:  /usr/sbin/dahdi_cfg

# /usr/sbin/dahdi_cfg -vvvvvvvv
DAHDI Tools Version - 2.1.0.2

DAHDI Version: 2.1.0.4
Echo Canceller(s):
Configuration
=====================

Channel map:

Channel 01: FXO Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01)
Channel 02: FXO Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 02)
Channel 03: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 03)
Channel 04: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 04)

4 channels to configure.

DAHDI_CHANCONFIG failed on channel 1: No such device or address (6)


*CLI> dahdi show status
Description                              Alarms  IRQ    bpviol CRC4
Fra Codi Options  LBO
DAHDI_DUMMY/1 (source: RTC) 1            UNCONFI 0      0      0
CAS Unk  YEL      0 db (CSU)/0-133 feet (DSX-1)

I am really hoping that I am just missing something stupid. Anyone have
any suggestions?

TIA
JohnM

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
-- 
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
direct: +1 256-428-6022
fax: +1 256-428-6062
Check us out at: www.digium.com & www.asterisk.org