Summary: | DAHLIN-00086: DAHDI Module Fails to Load | ||
Reporter: | swarga (swarga) | Labels: | |
Date Opened: | 2009-03-31 12:24:38 | Date Closed: | 2009-06-29 16:16:42 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | dahdi (the module) |
Versions: | 2.1.0.4 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Attachments: | ( 0) dmesg | |
Description: | dahdi-linux 2.1.0.4 compiles and installs correctly, but when the init script tries to load the module I see the following error: -bash-3.2# /etc/init.d/dahdi start Loading DAHDI hardware modules: dahdi_dummy: [ OK ] Error: missing /dev/dahdi! ****** ADDITIONAL INFORMATION ****** The system is an embedded PPC (MPC8349EA). The Linux kernel is 2.6.26.5 build with ELDK 4.2. The system has no Digium hardware (I need dahdi_dummy for MeetMe timing). | ||
Comments: | By: Shaun Ruffell (sruffell) 2009-03-31 12:43:41 what is the output of dmesg? By: Shaun Ruffell (sruffell) 2009-03-31 12:44:51 also, I see that you are using the ELDK. Is udev enabled in the ELDK now? By: Shaun Ruffell (sruffell) 2009-03-31 12:49:30 Assuming that udev isn't running, you may need to hand create the following special files: crw-rw---- 1 asterisk asterisk 196, 254 Mar 31 12:45 channel crw-rw---- 1 asterisk asterisk 196, 0 Mar 31 12:45 ctl crw-rw---- 1 asterisk asterisk 196, 255 Mar 31 12:45 pseudo crw-rw---- 1 asterisk asterisk 196, 253 Mar 31 12:45 timer i.e. mknod /dev/dahdi/channel c 196 254 mknod /dev/dahdi/ctl c 196 0 mknod /dev/dahdi/pseudo c 196 255 mknod /dev/dahdi/timer c 196 253 By: Shaun Ruffell (sruffell) 2009-03-31 12:57:00 Also, if that resolves your issue...could you do me a favor and try out the patch on Issue #0013930 on your PPC platform for me? I would be curious to know the results. By: swarga (swarga) 2009-04-02 13:23:13 Re: dmesg, the output is attached. Re: udev, you're right, it's not running (ELDK apparently disables it by default). I tried creating the special files manually using the commands you suggested but they fail, e.g. -bash-3.2# mknod /dev/dahdi/channel c 196 254 mknod: `/dev/dahdi/channel': No such file or directory Apparently it's failing because there is no /dev/dahdi directory on my target - do I have to create that manually, as well? FWIW, "196 dahdi" is listed in /proc/devices. Thanks! By: Shaun Ruffell (sruffell) 2009-04-02 13:29:44 yes...you will need to create the /dev/dahdi directory first. By: swarga (swarga) 2009-04-02 15:34:30 Thanks, I've never had to muck around in the /dev directory before, so I wasn't sure if there was some special procedure required to make the /dev/dahdi directory. I created it the normal way using mkdir, then created the 4 special files using mknod, and everything strated working fine when I rebooted it. dahdi_test reports 99.9875% accuracy. Regarding the patch, it seems that dahdi_dummy is "ticking" just fine, so I'm not sure of what sort of results you're looking for. Can you elaborate? Thanks again for all your help! By: Shaun Ruffell (sruffell) 2009-04-02 15:38:25 Glad to hear that everything is working for you. Regarding the patch, I'm interested in if there were any differences in the timer accuracy between the patched and unpatched versions. Was 99.9875% with or without the patch? By: swarga (swarga) 2009-04-03 12:21:03 I have not applied any patches thus far - "if it ain't broke, don't fix it." :) Issue 13930 appears to have 3 patch files associated with it. It's not clear to me which of these would apply to the 2.1.0.4 release that I am using. I would also need clear instructions on how to apply the patch(es). I'll be happy to help you out if I can. By: Shaun Ruffell (sruffell) 2009-06-29 16:16:42 Well...the dahdi_dummy changes are already committed, so there isn't any reason for any additional testing here. Thanks for the offer though. |