Physically? I'd have to drive 60 miles to answer that question. Obviously, since it's hardware, I've got no easy way to disable it in the config. I suppose I could ditch the VPMADT032 firmware file, though I don't see it in /lib/firmware any more. Is it no longer in userspace?
Tom > -----Original Message----- > From: Darrick Hartman [mailto:[email protected]] > Sent: 07 April 2010 18:22 > To: Tom Chadwin; AstLinux Users Mailing List > Subject: Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash > > Just to narrow this down, what happens if you pull the echo > module off the card? > > On 04/07/2010 12:15 PM, Tom Chadwin wrote: > >>> A major issue with 0.7.1 seems to have transpired. I > >> upgraded six or > >>> so boxes last week, two of which use DAHDI. Asterisk > seems to have > >>> failed to run. When I try to start it from the command > line, I get: > >>> > >>> [Apr 7 09:40:18] ERROR[2705]: asterisk.c:3099 main: Asterisk has > >>> detected a problem with your DAHDI configuration and will > >> shutdown for your protection. > >>> You have options: > >>> 1. You only have to compile DAHDI support into > >> Asterisk if you > >>> need it. One option is to recompile without DAHDI support. > >>> 2. You only have to load DAHDI drivers if you > want to take > >>> advantage of DAHDI services. One option is to unload DAHDI > >> modules if > >>> you don't need them. > >>> 3. If you need Zaptel services, you must correctly > >> configure DAHDI. > >>> > >>> DAHDI was working on these boxes in 0.7.0, and Zaptel on > >> them in 0.6. > >> > >> This is related to "/dev/dahdi/timer" in DAHDI. The > calling code in > >> asterisk.c is below. > >> > >> What is your variable DAHDIMODS set to? > > > > haltwhistlepbx ~ # cat /mnt/kd/rc.conf.d/user.conf |grep DAHDI > > DAHDIMODS="wctdm24xxp" > > > >> What is "cat /etc/rc.modules" ? > > > > haltwhistlepbx ~ # cat /etc/rc.modules # These modules get > modprobe'd > > when the system starts up. > > rtc > > #Comment out the modules you don't need, and change the > order to #move > > eth0 to eth1, etc. > > #Ethernet support > > #10/100 first, then Gigabit > > #3c59x > > #typhoon > > #tulip > > #eepro100 > > #natsemi > > via-rhine > > #forcedeth > > #8139cp > > #8139too > > #pcnet32 > > #acenic > > #e1000 > > #ns83820 > > #r8169 > > #tg3 > > #padlock > > geode-aes > > geode-rng > > geodewdt > > cryptodev > > cryptosoft > > > > I think this is an unmodified net5501 image. > > > >> Are you dong any modprobes in a rc.local or such? > > > > Nope. I do seem to have a /mnt/kd/rc.elocal, but it's empty. > > > >> For fun, try "modprobe dahdi_dummy" then "service asterisk > start" as > >> Michael suggested, and see if asterisk starts. > > > > haltwhistlepbx ~ # modprobe dahdi_dummy haltwhistlepbx ~ # asterisk > > -vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvc > > Asterisk 1.4.30, Copyright (C) 1999 - 2010 Digium, Inc. and others. > > Created by Mark Spencer<[email protected]> Asterisk comes with > > ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. > > This is free software, with components licensed under the > GNU General > > Public License version 2 and other licenses; you are welcome to > > redistribute it under certain conditions. Type 'core show > license' for > > details. > > > ============================================================== > =========== > > == Parsing '/etc/asterisk/asterisk.conf': Found > > == Parsing '/etc/asterisk/extconfig.conf': Found > > == Parsing '/etc/asterisk/logger.conf': Found Asterisk > Event Logger > > Started /var/log/asterisk/event_log [Apr 7 18:13:08] ERROR[2375]: > > asterisk.c:3099 main: Asterisk has detected a problem with > your DAHDI > > configuration and will shutdown for your protection. > > You have options: > > 1. You only have to compile DAHDI support into Asterisk if > > you need it. One option is to recompile without DAHDI support. > > 2. You only have to load DAHDI drivers if you want to take > > advantage of DAHDI services. One option is to unload DAHDI > modules if > > you don't need them. > > 3. If you need Zaptel services, you must correctly > configure DAHDI. > > haltwhistlepbx ~ # service asterisk start Starting Asterisk... > > > > WARNING WARNING WARNING > > > > YOU STILL HAVE NOT CHANGED YOUR ASTERISK MANAGER PASSWORD > ANYONE THAT > > KNOWS YOU ARE USING ASTLINUX CAN DESTROY YOUR SYSTEM. PLEASE CHANGE > > THIS IN /etc/asterisk/manager.conf IMMEDIATELY! > > > > WARNING WARNING WARNING > > > > haltwhistlepbx ~ # asterisk -rvvvvc > > Asterisk 1.4.30, Copyright (C) 1999 - 2010 Digium, Inc. and others. > > Created by Mark Spencer<[email protected]> Asterisk comes with > > ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. > > This is free software, with components licensed under the > GNU General > > Public License version 2 and other licenses; you are welcome to > > redistribute it under certain conditions. Type 'core show > license' for > > details. > > > ============================================================== > =========== > > == Parsing '/etc/asterisk/asterisk.conf': Found > > == Parsing '/etc/asterisk/extconfig.conf': Found Unable > to connect > > to remote asterisk (does /var/run/asterisk/asterisk.ctl > > exist?) > > > > Seems the same to me. > > > > Tom > > > > > > > > > >> #ifdef HAVE_DAHDI > >> { > >> int fd; > >> int x = 160; > >> fd = open(DAHDI_FILE_TIMER, O_RDWR); > >> if (fd>= 0) { > >> if (ioctl(fd, DAHDI_TIMERCONFIG,&x)) { > >> ast_log(LOG_ERROR, "You have " > >> DAHDI_NAME > >> " built and > >> drivers loaded, but the " > >> DAHDI_NAME " > >> timer test failed to set DAHDI_TIMERCONFIG to %d.\n", x); > >> exit(1); > >> } > >> if ((x = ast_wait_for_input(fd, 300))< 0) { > >> ast_log(LOG_ERROR, "You have " > >> DAHDI_NAME > >> "built and > >> drivers loaded, but the " > >> DAHDI_NAME " > >> timer could not be polled during the " > >> DAHDI_NAME " > >> timer test.\n"); > >> exit(1); > >> } > >> if (!x) { > >> const char dahdi_timer_error[] = { > >> "Asterisk has detected > >> a problem with your " DAHDI_NAME > >> " configuration > >> and will shutdown for your protection. You have options:" > >> "\n\t1. You only have > >> to compile " DAHDI_NAME > >> " support into > >> Asterisk if you need it. One option is to recompile without " > >> DAHDI_NAME " support." > >> "\n\t2. You only have > >> to load " DAHDI_NAME " drivers if you want to take advantage of " > >> DAHDI_NAME " > >> services. One option is to unload " > >> DAHDI_NAME " > >> modules if you don't need them." > >> "\n\t3. If you need > >> Zaptel services, you must correctly configure " DAHDI_NAME "." > >> }; > >> ast_log(LOG_ERROR, "%s\n", > >> dahdi_timer_error); > >> exit(1); > >> } > >> close(fd); > >> } > >> } > >> #endif > >> > >> > >> > >> > >> > > > > > > > ---------------------------------------------------------------------- > > -------- Download Intel® Parallel Studio Eval Try the new > > software tools for yourself. Speed compiling, find bugs > proactively, > > and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Astlinux-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via > PayPal to [email protected]. > > > -- > Darrick Hartman > DJH Solutions, LLC > http://www.djhsolutions.com > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
