Lol, I'd say this was wrong answer:
"What's the output of: lsmod | grep ^dahdi" you could simply check /proc/interrupts to see if the driver is bound to the IRQ ... kernel 2.6 allows any module to load even if it doesn't use the hardware so your lspci shows all the dahdi modules as expected He didn't post much of any information to show anything related to the driver itself (dmeg, /proc/interrupts, /dev/dahdi/1 etc ...) So the driver can be loaded or not. Martin On Sat, Apr 4, 2009 at 7:07 AM, Tzafrir Cohen <tzafrir.co...@xorcom.com> wrote: > On Thu, Apr 02, 2009 at 07:03:42PM -0500, Martin wrote: >> Then you need to edit /etc/dahdi/system.conf >> >> manually and add >> >> fxsks=1 > > Wrong answer. The driver has failed to identify and use the card. > > -- > Tzafrir Cohen > icq#16849755 jabber:tzafrir.co...@xorcom.com > +972-50-7952406 mailto:tzafrir.co...@xorcom.com > http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
