asterisk users - Oct 2011 - Issues with Xorcom astribanks when running Ubuntu 11.10 (oneiric) as a quemu/libvirt guest

Hi,

Xorcom astribanks get initialized straight on when using Ubuntu 11.10
packages but I am having a hard time to get the same result running in a
qemu/libvirt image.

The first difficulty is that astribanks devices get different usb device
ids during their initialisation process, requiring hot plug support.

I have figured out how to solve this issue using the technique described
in this post :
http://www.blogs.uni-osnabrueck.de/rotapken/2011/04/11/how-to-auto-hotplug-usb-devices-to-libvirt-vms/

That doesn't seem to be enough and the initialisation fails with a
status 1:

Oct 28 18:58:19 asterisk-rg 'xpp_fxloader'[1006]: Trying to find what to
do for product e4e4/1160/101, device /dev/bus/usb/001/004
Oct 28 18:58:19 asterisk-rg 'xpp_fxloader'[1010]: Loading firmware
'/usr/share/dahdi/USB_FW.hex' into '/dev/bus/usb/001/004'
Oct 28 18:58:23 asterisk-rg 'xpp_fxloader'[1024]: Trying to find what to
do for product e4e4/1161/101, device /dev/bus/usb/001/005
Oct 28 18:58:34 asterisk-rg
'xpp_fxloader'[1035]: /usr/sbin/astribank_tool failed with status 1

Seeing that Xorcom requires USB 2.0 and that the current versions of
libvirt and qemu in Ubuntu 11.10 emulate USB 1.10 in guests, I have
installed Boris Derzhavets' packages:
https://launchpad.net/~bderzhavets/+archive/seabios163 and updated my
host definition to emulate USB 2.0 but I still have the same issue.

Have I missed something?

Thanks,

Eric

On Sat, Oct 29, 2011 at 3:14 PM, Eric van der Vlist <vdv at dyomedea.com>
wrote:
> Hi,
>
> Xorcom astribanks get initialized straight on when using Ubuntu 11.10
> packages but I am having a hard time to get the same result running in a
> qemu/libvirt image.
>
> The first difficulty is that astribanks devices get different usb device
> ids during their initialisation process, requiring hot plug support.
>
> I have figured out how to solve this issue using the technique described
> in this post :
>
http://www.blogs.uni-osnabrueck.de/rotapken/2011/04/11/how-to-auto-hotplug-usb-devices-to-libvirt-vms/
>
> That doesn't seem to be enough and the initialisation fails with a
> status 1:
>
> Oct 28 18:58:19 asterisk-rg 'xpp_fxloader'[1006]: Trying to find
what to
> do for product e4e4/1160/101, device /dev/bus/usb/001/004
> Oct 28 18:58:19 asterisk-rg 'xpp_fxloader'[1010]: Loading firmware
> '/usr/share/dahdi/USB_FW.hex' into '/dev/bus/usb/001/004'
> Oct 28 18:58:23 asterisk-rg 'xpp_fxloader'[1024]: Trying to find
what to
> do for product e4e4/1161/101, device /dev/bus/usb/001/005
> Oct 28 18:58:34 asterisk-rg
> 'xpp_fxloader'[1035]: /usr/sbin/astribank_tool failed with status 1
>
> Seeing that Xorcom requires USB 2.0 and that the current versions of
> libvirt and qemu in Ubuntu 11.10 emulate USB 1.10 in guests, I have
> installed Boris Derzhavets' packages:
> https://launchpad.net/~bderzhavets/+archive/seabios163 and updated my
> host definition to emulate USB 2.0 but I still have the same issue.
>
> Have I missed something?
>
> Thanks,
>
> Eric
>
Try Xorcom's great support....  Tzafrir posted the solution to this a
few months ago, search the list for it.

-- 
~ Andrew "lathama" Latham lathama at gmail.com http://lathama.net ~

On Sat, Oct 29, 2011 at 08:14:55PM +0200, Eric van der Vlist
wrote:
> Hi,
> 
> Xorcom astribanks get initialized straight on when using Ubuntu 11.10
> packages but I am having a hard time to get the same result running in a
> qemu/libvirt image.
qemu? qemu+kqemu (the kernel module)? kvm? I would expect plain qemu to
have pretty bad performance, though I hardly tried to use it lately.

Anyway, it should be more than enough for the simple firmware loading
step.
> 
> The first difficulty is that astribanks devices get different usb device
> ids during their initialisation process, requiring hot plug support.
> 
> I have figured out how to solve this issue using the technique described
> in this post :
>
http://www.blogs.uni-osnabrueck.de/rotapken/2011/04/11/how-to-auto-hotplug-usb-devices-to-libvirt-vms/
> 
> That doesn't seem to be enough and the initialisation fails with a
> status 1:
> 
> Oct 28 18:58:19 asterisk-rg 'xpp_fxloader'[1006]: Trying to find
what to
> do for product e4e4/1160/101, device /dev/bus/usb/001/004
> Oct 28 18:58:19 asterisk-rg 'xpp_fxloader'[1010]: Loading firmware
> '/usr/share/dahdi/USB_FW.hex' into '/dev/bus/usb/001/004'
That's good.
> Oct 28 18:58:23 asterisk-rg 'xpp_fxloader'[1024]: Trying to find
what to
> do for product e4e4/1161/101, device /dev/bus/usb/001/005
> Oct 28 18:58:34 asterisk-rg
> 'xpp_fxloader'[1035]: /usr/sbin/astribank_tool failed with status 1
> 
> Seeing that Xorcom requires USB 2.0 
Technically the Astribank driver requires USB 2.0 as it was not worth it
to adapt it to the maximal URB (messagee) size of 64 byte of USB 1.1.
astribank_hexload actually was never adapted to that limitation either.
While this may be considered a bug, we hardly needed to load the
firmware on USB 1.1 and this gets an earlier and safer fail on most
cases.

Anyway, astribank_tool does not use large USB messages. I would not
expect it to fail on USB 1.1 . The problem is elsewhere. What happens if
you manually run:

  /usr/share/dahdi/xpp_fxloader load #?

Or:

  astribank_tool -D 001/005 -Q

If you have dahdi-tools < 2.5, you'll need:

  astribank_tool -D /dev/bun/usb/001/005 -Q
> and that the current versions of
> libvirt and qemu in Ubuntu 11.10 emulate USB 1.10 in guests, I have
> installed Boris Derzhavets' packages:
> https://launchpad.net/~bderzhavets/+archive/seabios163 and updated my
> host definition to emulate USB 2.0 but I still have the same issue.
> 
> Have I missed something?
What version of dahdi-tools is it?

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir