Hi all, I have been struggling with the feasibility of adding a zaptel 2 port fxo PCI card to a vm for a few weeks. Initially, I installed xen 3.0.2-2sources and compiled the kernel to include the 1000 HZ timing, which I know is a requirement for ztdummy and I hope to not use. What I''m running into is the basic understanding of how to get zaptel to compile on a DomU. 1. I was able to hide the card from Dom0 and have the DomU detect it, but the zaptel source will not compile without the kernel source. 2. I downloaded the xen source and placed it on DomU, compiled it and received compile errors [warning: "CONFIG_ZAPATA_DEBUG" is not defined"]. Upon research of that, I found that the kernel had changed and they were writing a patch. 3. As a result of the above, I went to xen 2.0.7 for its hardware support and the kernel. Has anyone successfully compiled zaptel module on a DomU? If so, what should I be doing to make this work? Thank you so much, I''m hoping that this will create a tread for others to benefit from, as well. Regards, Damon Brown _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,> > Has anyone successfully compiled zaptel module on a DomU? If so, > what should I be doing to make this work?yes... I did. I just copy all the xen-3.0.2 tree to my domU. Them, I made a /usr/src/linux link pointing to /usr/src/xen-3.0.2/linux-2.6.16-xen. After that, I can compile my zaptel drive just like it should on a stantard system.> Thank you so much, I''m hoping that this will create a tread for > others to benefit from, as well. > > Regards, > Damon Brown-- Christian Lyra POP-PR - RNP http://lyra.soueu.com.br Thus spake the master programmer: ``It is time for you to leave.'''' The Tao Of Programing _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 5/16/06, Damon Brown <brown078@gmail.com> wrote:> Hi all, > > I have been struggling with the feasibility of adding a zaptel 2 port fxo > PCI card to a vm for a few weeks. Initially, I installed xen 3.0.2-2 > sources and compiled the kernel to include the 1000 HZ timing, which I know > is a requirement for ztdummy and I hope to not use. What I''m running into > is the basic understanding of how to get zaptel to compile on a DomU.I have been using Asterisk on Xen for quite some time now, but without any zaptel hardware - just the zaptel and ztdummy drivers. Last night I tried to add one of the cheap WCFXO cards, and so far I can''t get the wcfxo driver to detect the card. It is presented to the domU correctly. I am still using Xen 2.0.7, I haven''t had time to try 3.0 yet (and don''t have the time to risk destabilizing my setup). Here''s the messages I get: May 16 09:24:37 uranus kernel: PCI: Obtained IRQ 18 for device 0000:02:04.0 May 16 09:24:37 uranus kernel: FXO PCI Master abort May 16 09:24:37 uranus last message repeated 36 times May 16 09:24:37 uranus kernel: Failed to initailize DAA, giving up... May 16 09:24:37 uranus kernel: FXO PCI Master abort May 16 09:24:37 uranus kernel: FXO PCI Master abort May 16 09:24:37 uranus kernel: wcfxo: probe of 0000:02:04.0 failed with error -5 May 16 09:24:37 uranus kernel: Registered tone zone 0 (United States / North America) root@uranus:~# lspci -v 0000:02:04.0 Communication controller: Motorola: Unknown device 5608 Subsystem: Motorola: Unknown device 0000 Flags: bus master, medium devsel, latency 32, IRQ 18 I/O ports at c800 [size=256] Memory at ff6bf000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 If anyone has any ideas, I''d be grateful. Dave -- David Muench - davemuench@gmail.com Jabber/Google Talk: davemuench@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I have been able to get the cheapy fxo cards detected compiled and running, but I have some nasty issues using it. It seems that those cards are really IRQ happy and when Im using the card, the rest of the box becomes almost unresponsive. To compile the code, just build it in your domain0 and set KVERS=2.6.16-xenU (or whatever your kernel version is). Then just copy the modules into your domU. -- Jason The place where you made your stand never mattered, only that you were there... and still on your feet On Tue, 16 May 2006, David Muench wrote:> On 5/16/06, Damon Brown <brown078@gmail.com> wrote: >> Hi all, >> >> I have been struggling with the feasibility of adding a zaptel 2 port fxo >> PCI card to a vm for a few weeks. Initially, I installed xen 3.0.2-2 >> sources and compiled the kernel to include the 1000 HZ timing, which I know >> is a requirement for ztdummy and I hope to not use. What I''m running into >> is the basic understanding of how to get zaptel to compile on a DomU. > > I have been using Asterisk on Xen for quite some time now, but without > any zaptel hardware - just the zaptel and ztdummy drivers. Last night > I tried to add one of the cheap WCFXO cards, and so far I can''t get > the wcfxo driver to detect the card. It is presented to the domU > correctly. I am still using Xen 2.0.7, I haven''t had time to try 3.0 > yet (and don''t have the time to risk destabilizing my setup). Here''s > the messages I get: > > May 16 09:24:37 uranus kernel: PCI: Obtained IRQ 18 for device 0000:02:04.0 > May 16 09:24:37 uranus kernel: FXO PCI Master abort > May 16 09:24:37 uranus last message repeated 36 times > May 16 09:24:37 uranus kernel: Failed to initailize DAA, giving up... > May 16 09:24:37 uranus kernel: FXO PCI Master abort > May 16 09:24:37 uranus kernel: FXO PCI Master abort > May 16 09:24:37 uranus kernel: wcfxo: probe of 0000:02:04.0 failed with error > -5 > May 16 09:24:37 uranus kernel: Registered tone zone 0 (United States / > North America) > > root@uranus:~# lspci -v > 0000:02:04.0 Communication controller: Motorola: Unknown device 5608 > Subsystem: Motorola: Unknown device 0000 > Flags: bus master, medium devsel, latency 32, IRQ 18 > I/O ports at c800 [size=256] > Memory at ff6bf000 (32-bit, non-prefetchable) [size=4K] > Capabilities: [40] Power Management version 2 > > If anyone has any ideas, I''d be grateful. > > Dave > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks Jason Were you able to get it to compile ? I just get this C error on the asterisk CVS head and stable: make[1]: Entering directory `/usr/src/xen-3.0.2-2/linux-2.6.16-xen'' CC [M] /usr/src/asterisk/zaptel/zaptel.o /usr/src/asterisk/zaptel/zaptel.c: In function `zt_register'': /usr/src/asterisk/zaptel/zaptel.c:4448: warning: passing arg 2 of `class_device_create'' makes pointer from integer without a cast /usr/src/asterisk/zaptel/zaptel.c:4448: warning: passing arg 3 of `class_device_create'' makes integer from pointer without a cast /usr/src/asterisk/zaptel/zaptel.c:4448: warning: passing arg 4 of `class_device_create'' from incompatible pointer type /usr/src/asterisk/zaptel/zaptel.c:4448: error: too few arguments to function `class_device_create'' /usr/src/asterisk/zaptel/zaptel.c: In function `zt_init'': /usr/src/asterisk/zaptel/zaptel.c:6507: warning: passing arg 2 of `class_device_create'' makes pointer from integer without a cast /usr/src/asterisk/zaptel/zaptel.c:6507: warning: passing arg 3 of `class_device_create'' makes integer from pointer without a cast /usr/src/asterisk/zaptel/zaptel.c:6507: warning: passing arg 4 of `class_device_create'' from incompatible pointer type /usr/src/asterisk/zaptel/zaptel.c:6507: error: too few arguments to function `class_device_create'' /usr/src/asterisk/zaptel/zaptel.c:6508: warning: passing arg 2 of `class_device_create'' makes pointer from integer without a cast /usr/src/asterisk/zaptel/zaptel.c:6508: warning: passing arg 3 of `class_device_create'' makes integer from pointer without a cast /usr/src/asterisk/zaptel/zaptel.c:6508: warning: passing arg 4 of `class_device_create'' from incompatible pointer type /usr/src/asterisk/zaptel/zaptel.c:6508: error: too few arguments to function `class_device_create'' /usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing arg 2 of `class_device_create'' makes pointer from integer without a cast /usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing arg 3 of `class_device_create'' makes integer from pointer without a cast /usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing arg 4 of `class_device_create'' from incompatible pointer type /usr/src/asterisk/zaptel/zaptel.c:6509: error: too few arguments to function `class_device_create'' /usr/src/asterisk/zaptel/zaptel.c:6510: warning: passing arg 2 of `class_device_create'' makes pointer from integer without a cast /usr/src/asterisk/zaptel/zaptel.c:6510: warning: passing arg 3 of `class_device_create'' makes integer from pointer without a cast /usr/src/asterisk/zaptel/zaptel.c:6510: warning: passing arg 4 of `class_device_create'' from incompatible pointer type /usr/src/asterisk/zaptel/zaptel.c:6510: error: too few arguments to function `class_device_create'' /usr/src/asterisk/zaptel/zaptel.c: At top level: /usr/src/asterisk/zaptel/zaptel.c:176: warning: `fcstab'' defined but not used make[2]: *** [/usr/src/asterisk/zaptel/zaptel.o] Error 1 make[1]: *** [_module_/usr/src/asterisk/zaptel] Error 2 make[1]: Leaving directory `/usr/src/xen-3.0.2-2/linux-2.6.16-xen'' make: *** [linux26] Error 2 Thanks On 5/16/06, Jason <xen@jasonandjessi.com> wrote:> > I have been able to get the cheapy fxo cards detected compiled and > running, but I have some nasty > issues using it. It seems that those cards are really IRQ happy and when > Im using the card, the > rest of the box becomes almost unresponsive. > > To compile the code, just build it in your domain0 and set KVERS> 2.6.16-xenU (or whatever your > kernel version is). Then just copy the modules into your domU. > > -- > Jason > The place where you made your stand never mattered, > only that you were there... and still on your feet > > On Tue, 16 May 2006, David Muench wrote: > > > On 5/16/06, Damon Brown <brown078@gmail.com> wrote: > >> Hi all, > >> > >> I have been struggling with the feasibility of adding a zaptel 2 port > fxo > >> PCI card to a vm for a few weeks. Initially, I installed xen 3.0.2-2 > >> sources and compiled the kernel to include the 1000 HZ timing, which I > know > >> is a requirement for ztdummy and I hope to not use. What I''m running > into > >> is the basic understanding of how to get zaptel to compile on a DomU. > > > > I have been using Asterisk on Xen for quite some time now, but without > > any zaptel hardware - just the zaptel and ztdummy drivers. Last night > > I tried to add one of the cheap WCFXO cards, and so far I can''t get > > the wcfxo driver to detect the card. It is presented to the domU > > correctly. I am still using Xen 2.0.7, I haven''t had time to try 3.0 > > yet (and don''t have the time to risk destabilizing my setup). Here''s > > the messages I get: > > > > May 16 09:24:37 uranus kernel: PCI: Obtained IRQ 18 for device 0000:02: > 04.0 > > May 16 09:24:37 uranus kernel: FXO PCI Master abort > > May 16 09:24:37 uranus last message repeated 36 times > > May 16 09:24:37 uranus kernel: Failed to initailize DAA, giving up... > > May 16 09:24:37 uranus kernel: FXO PCI Master abort > > May 16 09:24:37 uranus kernel: FXO PCI Master abort > > May 16 09:24:37 uranus kernel: wcfxo: probe of 0000:02:04.0 failed with > error > > -5 > > May 16 09:24:37 uranus kernel: Registered tone zone 0 (United States / > > North America) > > > > root@uranus:~# lspci -v > > 0000:02:04.0 Communication controller: Motorola: Unknown device 5608 > > Subsystem: Motorola: Unknown device 0000 > > Flags: bus master, medium devsel, latency 32, IRQ 18 > > I/O ports at c800 [size=256] > > Memory at ff6bf000 (32-bit, non-prefetchable) [size=4K] > > Capabilities: [40] Power Management version 2 > > > > If anyone has any ideas, I''d be grateful. > > > > Dave > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Damon Brown Web Application Developer and Consultant Phone: (916)601-8190 e-mail: damon@technicate.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hmm, odd. Yeah I was able to get it to compile first shot. I think the only additional thing I had to do was create a link in /lib/modules/2.6.16-xenU/build to /usr/src/xen-3.0.2/linux-2.6.16-xenU -- Jason The place where you made your stand never mattered, only that you were there... and still on your feet On Tue, 16 May 2006, Damon Brown wrote:> Thanks Jason > Were you able to get it to compile ? I just get this C error on the > asterisk CVS head and stable: > > make[1]: Entering directory `/usr/src/xen-3.0.2-2/linux-2.6.16-xen'' > CC [M] /usr/src/asterisk/zaptel/zaptel.o > /usr/src/asterisk/zaptel/zaptel.c: In function `zt_register'': > /usr/src/asterisk/zaptel/zaptel.c:4448: warning: passing arg 2 of > `class_device_create'' makes pointer from integer without a cast > /usr/src/asterisk/zaptel/zaptel.c:4448: warning: passing arg 3 of > `class_device_create'' makes integer from pointer without a cast > /usr/src/asterisk/zaptel/zaptel.c:4448: warning: passing arg 4 of > `class_device_create'' from incompatible pointer type > /usr/src/asterisk/zaptel/zaptel.c:4448: error: too few arguments to function > `class_device_create'' > /usr/src/asterisk/zaptel/zaptel.c: In function `zt_init'': > /usr/src/asterisk/zaptel/zaptel.c:6507: warning: passing arg 2 of > `class_device_create'' makes pointer from integer without a cast > /usr/src/asterisk/zaptel/zaptel.c:6507: warning: passing arg 3 of > `class_device_create'' makes integer from pointer without a cast > /usr/src/asterisk/zaptel/zaptel.c:6507: warning: passing arg 4 of > `class_device_create'' from incompatible pointer type > /usr/src/asterisk/zaptel/zaptel.c:6507: error: too few arguments to function > `class_device_create'' > /usr/src/asterisk/zaptel/zaptel.c:6508: warning: passing arg 2 of > `class_device_create'' makes pointer from integer without a cast > /usr/src/asterisk/zaptel/zaptel.c:6508: warning: passing arg 3 of > `class_device_create'' makes integer from pointer without a cast > /usr/src/asterisk/zaptel/zaptel.c:6508: warning: passing arg 4 of > `class_device_create'' from incompatible pointer type > /usr/src/asterisk/zaptel/zaptel.c:6508: error: too few arguments to function > `class_device_create'' > /usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing arg 2 of > `class_device_create'' makes pointer from integer without a cast > /usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing arg 3 of > `class_device_create'' makes integer from pointer without a cast > /usr/src/asterisk/zaptel/zaptel.c:6509: warning: passing arg 4 of > `class_device_create'' from incompatible pointer type > /usr/src/asterisk/zaptel/zaptel.c:6509: error: too few arguments to function > `class_device_create'' > /usr/src/asterisk/zaptel/zaptel.c:6510: warning: passing arg 2 of > `class_device_create'' makes pointer from integer without a cast > /usr/src/asterisk/zaptel/zaptel.c:6510: warning: passing arg 3 of > `class_device_create'' makes integer from pointer without a cast > /usr/src/asterisk/zaptel/zaptel.c:6510: warning: passing arg 4 of > `class_device_create'' from incompatible pointer type > /usr/src/asterisk/zaptel/zaptel.c:6510: error: too few arguments to function > `class_device_create'' > /usr/src/asterisk/zaptel/zaptel.c: At top level: > /usr/src/asterisk/zaptel/zaptel.c:176: warning: `fcstab'' defined but not > used > make[2]: *** [/usr/src/asterisk/zaptel/zaptel.o] Error 1 > make[1]: *** [_module_/usr/src/asterisk/zaptel] Error 2 > make[1]: Leaving directory `/usr/src/xen-3.0.2-2/linux-2.6.16-xen'' > make: *** [linux26] Error 2 > > > Thanks > > On 5/16/06, Jason <xen@jasonandjessi.com> wrote: >> >> I have been able to get the cheapy fxo cards detected compiled and >> running, but I have some nasty >> issues using it. It seems that those cards are really IRQ happy and when >> Im using the card, the >> rest of the box becomes almost unresponsive. >> >> To compile the code, just build it in your domain0 and set KVERS>> 2.6.16-xenU (or whatever your >> kernel version is). Then just copy the modules into your domU. >> >> -- >> Jason >> The place where you made your stand never mattered, >> only that you were there... and still on your feet >> >> On Tue, 16 May 2006, David Muench wrote: >> >> > On 5/16/06, Damon Brown <brown078@gmail.com> wrote: >> >> Hi all, >> >> >> >> I have been struggling with the feasibility of adding a zaptel 2 port >> fxo >> >> PCI card to a vm for a few weeks. Initially, I installed xen 3.0.2-2 >> >> sources and compiled the kernel to include the 1000 HZ timing, which I >> know >> >> is a requirement for ztdummy and I hope to not use. What I''m running >> into >> >> is the basic understanding of how to get zaptel to compile on a DomU. >> > >> > I have been using Asterisk on Xen for quite some time now, but without >> > any zaptel hardware - just the zaptel and ztdummy drivers. Last night >> > I tried to add one of the cheap WCFXO cards, and so far I can''t get >> > the wcfxo driver to detect the card. It is presented to the domU >> > correctly. I am still using Xen 2.0.7, I haven''t had time to try 3.0 >> > yet (and don''t have the time to risk destabilizing my setup). Here''s >> > the messages I get: >> > >> > May 16 09:24:37 uranus kernel: PCI: Obtained IRQ 18 for device 0000:02: >> 04.0 >> > May 16 09:24:37 uranus kernel: FXO PCI Master abort >> > May 16 09:24:37 uranus last message repeated 36 times >> > May 16 09:24:37 uranus kernel: Failed to initailize DAA, giving up... >> > May 16 09:24:37 uranus kernel: FXO PCI Master abort >> > May 16 09:24:37 uranus kernel: FXO PCI Master abort >> > May 16 09:24:37 uranus kernel: wcfxo: probe of 0000:02:04.0 failed with >> error >> > -5 >> > May 16 09:24:37 uranus kernel: Registered tone zone 0 (United States / >> > North America) >> > >> > root@uranus:~# lspci -v >> > 0000:02:04.0 Communication controller: Motorola: Unknown device 5608 >> > Subsystem: Motorola: Unknown device 0000 >> > Flags: bus master, medium devsel, latency 32, IRQ 18 >> > I/O ports at c800 [size=256] >> > Memory at ff6bf000 (32-bit, non-prefetchable) [size=4K] >> > Capabilities: [40] Power Management version 2 >> > >> > If anyone has any ideas, I''d be grateful. >> > >> > Dave >> > >> > >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users