According to the #asterisk team, Zaptel now has support for Kernel 2.6 with udev. It is no longer nececary to re-compile a kernel without udev support if you want to run Zaptel. This is contrary to the ewarn text messages in the zaptel 1.0.0 ebuild. According to this page: http://www.voip-info.org/tiki-index.php?page=Asterisk%20Zaptel%20Installation Zaptel can be built correctly for kernel 2.6 by using a different make-target. "make linux26" instead of "make"
> According to the #asterisk team, Zaptel now has support for Kernel 2.6 with > udev. It is no longer nececary to re-compile a kernel without udev support if > you want to run Zaptel. This is contrary to the ewarn text messages in the > zaptel 1.0.0 ebuild. * most people still use devfs * according to the asterisk devs it will never support devfs on 2.6 (even if it's still around till 2.7/2.8) * the message says: use udev and disable devfs _or_ use devfs and do something to re-create those missing device nodes _or_ stop now and enable USE="devfs26" to enable the experimental patch > According to this page: > http://www.voip-info.org/tiki-index.php?page=Asterisk%20Zaptel%20Installation > > Zaptel can be built correctly for kernel 2.6 by using a different > make-target. "make linux26" instead of "make" unnecessary, zaptel makefile does auto-detects the currently running kernelversion and selects the right make target (see Makefile, esp. BUILDVER= and the all target)
I think I've run into a bug / problem with Zaptel and kernel 2.6: Zaptel generated several warnings about running kernel 2.6: * You're using zaptel with linux-2.6: * Zaptel doesn't support devfs with 2.6, you'll need to use udev or * disable devfs * or use devfs and write a script which re-creates the device nodes for * you I looked through some topics on the forum and to use udev it seems I must make a sheer endless numer of modifications to the box incl. the kernel (not happy with that) but it could also be fixed using a script or a patch? I guess this error is caused by zaptel & kernel 2.6 asterisk # ztcfg Notice: Configuration file is /etc/zaptel.conf line 141: Unable to open master device '/dev/zap/ctl' While this device does in fact exist and also I am unable to mobprobe the module zaptel. I emerged udev and then tried to re-emerge zaptel which fails with about 6-7 pages of errors! Some small snippets: include/linux/types.h:18: error: syntax error before "__kernel_dev_t" include/linux/types.h:18: warning: type defaults to `int' in declaration of `__kernel_dev_t' include/linux/types.h:18: warning: data definition has no type or storage class include/linux/types.h:21: error: syntax error before "dev_t" include/linux/types.h:152: warning: type defaults to `int' in declaration of `f_tinode' include/linux/types.h:152: warning: data definition has no type or storage class include/linux/types.h:155: error: syntax error before '}' token In file included from /var/tmp/portage/zaptel-1.0.0/work/zaptel-1.0.0/zaptel.c:42: include/linux/kernel.h:15:27: asm/byteorder.h: No such file or directory include/linux/kernel.h:16:21: asm/bug.h: No such file or directory In file included from /var/tmp/portage/zaptel-1.0.0/work/zaptel-1.0.0/zaptel.c:42: include/linux/kernel.h:81: error: syntax error before "size_t" include/linux/kernel.h:82: warning: function declaration isn't a prototype include/linux/kernel.h:82: warning: conflicting types for built-in function `snprintf' include/linux/kernel.h:83: error: syntax error before "size_t" include/linux/kernel.h:83: warning: function declaration isn't a prototype include/linux/time.h:145:31: division by zero in #if include/linux/time.h:145:31: division by zero in #if include/linux/time.h:145:31: division by zero in #if include/linux/time.h:145:31: division by zero in #if include/linux/fs.h:356: error: storage size of `bd_sem' isn't known include/linux/fs.h:357: error: storage size of `bd_mount_sem' isn't known include/linux/fs.h:431: error: storage size of `i_atime' isn't known include/linux/fs.h:432: error: storage size of `i_mtime' isn't known
>I think I've run into a bug / problem with Zaptel and kernel 2.6: >Zaptel generated several warnings about running kernel 2.6: >* You're using zaptel with linux-2.6: >* Zaptel doesn't support devfs with 2.6, you'll need to use udev or >* disable devfs >* or use devfs and write a script which re-creates the device nodes for >* you >I looked through some topics on the forum and to use udev it seems I must make >a sheer endless numer of modifications to the box incl. the kernel (not happy >with that) but it could also be fixed using a script there are several ways to create the necessary device-nodes >or a patch? yeah... ...devfs26, it's mentioned in the info messages >I guess this error is caused by zaptel & kernel 2.6 >asterisk # ztcfg >Notice: Configuration file is /etc/zaptel.conf >line 141: Unable to open master device '/dev/zap/ctl' >While this device does in fact exist and also I am unable to mobprobe the >module zaptel. error messages of modprobe? error messages in dmesg? the device exists, but without driver loaded there's no way ztcfg will work >I emerged udev and then tried to re-emerge zaptel which fails with about 6-7 >pages of errors! Some small snippets: Open a new bug... ...paste output of: emerge info, ls -l /usr/src/linux and emerge -p linux-headers into the proper field ...do: emerge zaptel >zaptel-26.log 2>&1 create a new attachment in bug report and upload zaptel-26.log
wording is ok
