[asterisk-users] No hardware timing source found in /proc/dahdi
Shaun Ruffell
sruffell at digium.com
Mon Mar 16 10:49:45 CDT 2009
John Millican wrote:
> Well,
> lsmod | grep hisax returns nothing
>
> plain lsmod:
> Module Size Used by
> dahdi_dummy 22472 0
> dahdi 215776 1 dahdi_dummy
> crc_ccitt 18944 1 dahdi
> af_packet 57100 2
> snd_pcm_oss 67456 0
> snd_mixer_oss 34176 1 snd_pcm_oss
> snd_seq 74992 0
> snd_seq_device 25620 1 snd_seq
> vmnet 72992 3
> parport_pc 58456 0
> parport 56588 1 parport_pc
> vmmon 158908 0
> sunrpc 198600 1
> iptable_filter 19840 0
> ip_tables 37848 1 iptable_filter
> ip6table_filter 19584 0
> ip6_tables 31944 1 ip6table_filter
> x_tables 37000 2 ip_tables,ip6_tables
> ipv6 372344 29
> cpufreq_conservative 24968 0
> cpufreq_userspace 23680 0
> cpufreq_powersave 18560 0
> powernow_k8 31504 0
> apparmor 58672 0
> loop 36356 0
> dm_mod 77152 0
> ohci1394 51272 0
> ieee1394 115800 1 ohci1394
> i2c_nforce2 22784 0
> snd_hda_intel 368804 0
> i2c_core 43648 1 i2c_nforce2
> snd_pcm 108680 2 snd_pcm_oss,snd_hda_intel
> snd_timer 42632 2 snd_seq,snd_pcm
> snd 84984 7
> snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer
> k8temp 22656 0
> hwmon 20232 1 k8temp
> button 26400 0
> usblp 30976 0
> forcedeth 65416 0
> rtc_cmos 25016 0
> rtc_core 38156 1 rtc_cmos
> rtc_lib 19968 1 rtc_core
> sr_mod 33444 0
> cdrom 52392 1 sr_mod
> usb_storage 102816 0
> soundcore 25360 1 snd
> snd_page_alloc 27280 2 snd_hda_intel,snd_pcm
> ide_core 165648 1 usb_storage
> sg 53304 0
> usbhid 58160 0
> hid 43776 1 usbhid
> ff_memless 22536 1 usbhid
> sd_mod 45824 6
> ohci_hcd 38020 0
> ehci_hcd 50572 0
> usbcore 155560 6 usblp,usb_storage,usbhid,ohci_hcd,ehci_hcd
> edd 26760 0
> ext3 156688 3
> mbcache 26248 1 ext3
> jbd 89192 1 ext3
> fan 22792 0
> sata_nv 38404 4
> pata_amd 31876 0
> libata 164096 2 sata_nv,pata_amd
> scsi_mod 176536 5 sr_mod,usb_storage,sg,sd_mod,libata
> thermal 34576 0
> processor 59592 2 powernow_k8,thermal
Looking at the lsmod output, it appears that the wctdm module is not
loaded. So either the /etc/dahdi/modules has the wctdm module commented
out, or something is wrong with the /etc/init.d/dahdi that it isn't
viewing that file.
If you unload all the drivers ('/etc/init.d/dahdi stop') and make sure
they are unloaded ('lsmod | grep dahdi' should not show any output) then
just load the wctdm driver ('modprobe wctdm'), and then what does dmesg
show?
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org
More information about the asterisk-users
mailing list