Rainer Maier
2005-Sep-12 09:26 UTC
AW: [Asterisk-Users] Debian Sarge, Kernel 2.6.13 and AVM Fritz!PCI v2.0 card
Hi Jon, perfect instructions, thank you very much. I used them and after some tests they worked. Here is what I did. Maybe someone could use it completely: ------------------------------------------------------------ Install helpers: apt-get install kernel-package ncurses-dev fakeroot wget bzip2 Go to usr directory: cd /usr/src wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.13.1.tar.bz2 Unpack the kernel sources and change into directory: tar xjf linux-2.6.13.1.tar.bz2 ln -s /usr/src/linux-2.6.13.1 /usr/src/linux cd linux/ copy /boot/config-2.v.v.v to /usr/src/linux/. It is normally a good idea to take the configuration of your existing (working!) kernel 2.6 as a starting point for the configuration of your new kernel. Usually the current kernel configuration is saved in a file under /boot, e.g. /boot/config-2.6.3. We will load this configuration and then do the changes we desire. make oldconfig make menuconfig check for ->fs->EXT2 ->driver->ATA is included in kernel make OR: Load alternative config (i.e. config-2.v.v.v) and then store the new one. make Then run the following commands (please note that make dep is not needed any more for kernel 2.6): make-kpkg kernel_image If no error occurs you will find the new kernel as a Debian package called kernel-image-2.6.x.x_custom.1.0_i386.deb under /usr/src. cd ../ Install new kernel: dpkg -i kernel-image-2.6.13.1_i386.deb Create a ramdisk of your new kernel (otherwise your system will most likely not boot): cd /boot/ mkinitrd -o /boot/initrd.img-2.6.13.1 2.6.13.1 reboot Then I run your procedures. I think I would not have needed the CVS system maybe except for the updates of packets in the future. I could have downloaded it directly from isdn4linux. But anyhow, all drivers are loaded now. I still have the problem that asterisk complains he could not load chan_capi.c there would not be any CAPI installed. Any idears why and how I could get it running. I must admit I don't have a clue how asterisks knows of exactly this file. ------------------------------------------------------------ -----Urspr?ngliche Nachricht----- Von: Jon Dean [mailto:jon.dean@wormhole.co.nz] Gesendet: Samstag, 10. September 2005 13:40 An: Rainer Maier Betreff: Re: [Asterisk-Users] Debian Sarge, Kernel 2.6.13 and AVM Fritz!PCI v2.0 card On Fri, 09 Sep 2005 21:47, Rainer Maier wrote:> Hi all, > > I am new on this list an I hope the posting is correct. > > I am using Debian Sarge, kernel 2.6.13 from www.kernel.org and want to > install the drivers for an AVM Fritz!PCI v2.0 ISDN card. > > I used the directions from AVM but Asterisk allways stops with CAPI > not installed! > > I am new to Asterisk but this problem must already have been solved. > I did not find a search function in the asterisk list. > > How can I find a thread to this and other problems ? > Does anyone know of a helpful page ? > > Best regards > Rainer MaierHi Rainer, Good news for you - I have got a single fritz going under 2.6.13 today. My problem is I need two fritz to go under 2.6.13 and am having problems acheiving that. Anyway, stuff for you to do. Ignore the AVM instructions. Download the misdn drivers using this script and cvs - the password is readonly. #!/bin/bash export CVSROOT=:pserver:anonymous@cvs.isdn4linux.de:/i4ldev cvs login cvs -z9 co mISDN # <-comment out after you made a checkout #cvs -q -z9 update -dPA # <- and uncomment this for updating the find the script in the msidn called std2kern and run it this will place the misdn source code into the 2.6.13 source directory. This fire up make menuconfig for 2.6.13 and find the isdn/misdn/hardware screen and select the avmfritz stuff, plus all the capi stuff as well. Then build the modules and install the modules. Then once all is done, run this script to load the modules (basically order is everything supposedly). #!/bin/sh if [ $# -ge 1 ]; then DEBUG=$1 else DEBUG=0 fi if [ $# -ge 2 ]; then DEBUG_F=$2 else DEBUG_F=0xffffffff fi if [ $# -ge 3 ]; then ttt=$3 else ttt=180 fi #INSMOD_PARA=-m MEXT=.ko cd /usr/src/linux/drivers/isdn/hardware/mISDN #modprobe capidrv modprobe capi insmod ${INSMOD_PARA} mISDN_core${MEXT} debug=${DEBUG} >/tmp/m_core.mod # insmod ${INSMOD_PARA} faxl3${MEXT} debug=${DEBUG_F} ttt=$ttt> /tmp/m_faxl3.modinsmod ${INSMOD_PARA} mISDN_l1${MEXT} debug=${DEBUG} >/tmp/m_l1.mod insmod ${INSMOD_PARA} mISDN_l2${MEXT} debug=${DEBUG} >/tmp/m_l2.mod insmod ${INSMOD_PARA} l3udss1${MEXT} debug=${DEBUG} >/tmp/m_l3u.mod insmod ${INSMOD_PARA} mISDN_capi${MEXT} debug=${DEBUG} >/tmp/m_capi.mod # insmod ${INSMOD_PARA} mISDN_isac${MEXT} >/tmp/m_isac.mod insmod ${INSMOD_PARA} mISDN_x25dte${MEXT} debug=${DEBUG} >/tmp/m_x25dte.mod insmod ${INSMOD_PARA} mISDN_dtmf${MEXT} debug=${DEBUG} >/tmp/m_dtmf.mod #insmod ${INSMOD_PARA} w6692pci${MEXT} debug=${DEBUG} pots=1 led=${LED} protocol=2 > /tmp/w6692pci.mod #insmod ${INSMOD_PARA} sedlfax${MEXT} debug=${DEBUG_F} protocol=2,2> /tmp/sf.mod#insmod ${INSMOD_PARA} /lib/modules/2.6.13/kernel/drivers/isdn/hardware/mISDN/avmfritz.ko debug=${DEBUG_F} protocol=2 > /tmp/sf.mod modprobe avmfritz protocol=2 and you should get some usefull information from capiinfo Kind Regards, jon dean -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
Tzafrir Cohen
2005-Sep-12 12:23 UTC
[Asterisk-Users] Debian Sarge, Kernel 2.6.13 and AVM Fritz!PCI v2.0 card
On Mon, Sep 12, 2005 at 06:26:31PM +0200, Rainer Maier wrote:> > Hi Jon, > perfect instructions, thank you very much. > I used them and after some tests they worked. > > Here is what I did. Maybe someone could use it completely: > ------------------------------------------------------------ > Install helpers: > apt-get install kernel-package ncurses-dev fakeroot wget bzip2 > > Go to usr directory: > cd /usr/src > wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.13.1.tar.bz2 > > Unpack the kernel sources and change into directory: > tar xjf linux-2.6.13.1.tar.bz2 > ln -s /usr/src/linux-2.6.13.1 /usr/src/linux cd linux/That should not be necessary. Generally, one cannot assume that there is just "one kernel" and it is dangerous to assume /usr/src/linux matches the running kernel. See comment below. Basically, extract the kernel under a directory. Optionally patch it. make menuconfig Now you have a tree with your desired .config file. You run 'make-kpkg buildpackage --rootcmd fakeroot' One of the resulting packages is a kernel-image package . Another one is a kernel-headers package. Install the kernel-image on the target machine (obviously) and kernel-headers on the build machine. The kernel-headers package could be used instead of the complete kernel source . Thus the convension can be to look for the "kernel source" in /usr/src/kernel-headers-`uname -r` .> > copy /boot/config-2.v.v.v to /usr/src/linux/. > It is normally a good idea to take the configuration of your existing > (working!) kernel 2.6 as a starting point for the configuration of your new > kernel. Usually the current kernel configuration is saved in a file under > /boot, e.g. /boot/config-2.6.3. We will load this configuration and then do > the changes we desire. > > make oldconfig > make menuconfig > check for ->fs->EXT2 ->driver->ATA is included in kernel make > OR: > Load alternative config (i.e. config-2.v.v.v) and then store the new one. > make > > Then run the following commands (please note that make dep is not needed any > more for kernel 2.6): > make-kpkg kernel_image > > If no error occurs you will find the new kernel as a Debian package called > kernel-image-2.6.x.x_custom.1.0_i386.deb under /usr/src.Again, it doesn't have to be /usr/src . The point is not to build as root (fakeroot is used to overcome some small packaging problems)> cd ../ > > Install new kernel: > dpkg -i kernel-image-2.6.13.1_i386.deb > > Create a ramdisk of your new kernel (otherwise your system will most likely > not boot): > cd /boot/ > mkinitrd -o /boot/initrd.img-2.6.13.1 2.6.13.1 rebootThat should not be required. Normally that is done automatically by the postinst script of the kernel (if neeeded).> > Then I run your procedures. > I think I would not have needed the CVS system maybe except for the updates > of packets in the future. > I could have downloaded it directly from isdn4linux. > But anyhow, all drivers are loaded now. > > I still have the problem that asterisk complains he could not load > chan_capi.c there would not be any CAPI installed. > Any idears why and how I could get it running. > I must admit I don't have a clue how asterisks knows of exactly this file.Could you please give the exact error message? And all the messages related to chan_capi? -- Tzafrir Cohen | tzafrir@jbr.cohens.org.il | VIM is http://tzafrir.org.il | | a Mutt's tzafrir@cohens.org.il | | best ICQ# 16849755 | | friend