Wow, I guess I hadn't tried using the timing device under -current recently! I found the problem, though - NetBSD 2.99.16 and later use EMOVEFD instead of ENXIO as the 'special in-kernel return code' for moving a descriptor while cloning... I'd changed the fdclone() call, but none of the other bits in zaptel.c. This is now fixed. :-)
Please download the latest (zaptel-netbsd-20050404.tar.bz2) and try again. Thanks for the feedback! +j Tom Ivar Helbekkmo wrote: >Jeff Rizzo <[EMAIL PROTECTED]> writes: > > > >>The NetBSD zaptel drivers currently support wcfxo, wcfxs and ztdummy >>on NetBSD 2.0 and up. They are available separately at >>http://www.tastylime.net/netbsd/zaptel/ >> >> > >I've tried to get this working on my machines, currently running >NetBSD 3.99.1, but with no luck: > >dejah# /sbin/modload -s -p /usr/local/sbin/zaptel_postinstall >/usr/local/lkm/mod_zaptel.o >Module loaded as ID 0 >dejah# /sbin/modload -s /usr/local/lkm/mod_ztdummy.o >Module loaded as ID 1 >dejah# cat /usr/local/etc/zaptel.conf >loadzone=no >defaultzone=no >dejah# /usr/local/bin/ztcfg >Keyword: [loadzone], Value: [no] >Keyword: [defaultzone], Value: [no] >dejah# dmesg >[...] >Zapata Telephony Interface Registered on major 196 >Registered Span 1 ('ZTDUMMY/1') with 0 channels >Span ('ZTDUMMY/1') is new master >ztdummy: init() finished >ztdummy: loaded >Registered tone zone 8 (Norway) >dejah# ls -l /dev/zap >total 0 >crw-r--r-- 1 root wheel - 196, 254 Apr 4 09:12 channel >crw-r--r-- 1 root wheel - 196, 0 Apr 4 09:12 ctl >crw-r--r-- 1 root wheel - 196, 255 Apr 4 09:12 pseudo >crw-r--r-- 1 root wheel - 196, 253 Apr 4 09:12 timer >dejah# zttest >Unable to open zap interface: Device not configured >dejah# > >Am I doing it wrong? Or do you have any ideas for how I can figure >out why it isn't working for me? > >-tih > > _______________________________________________ Asterisk-BSD mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-bsd
