I don't know anything about your OS, but look at the 3rd line down in your posted listing: open("/usr/lib/freetz/librtlsdr.so.0", O_RDONLY) = -1 ENOENT (No such file or directory) It isn't finding the library.  That same message repeats many times throughout your listing.  It's not finding many libraries from looking at it again.  If you're using cmake you can probably fix the paths to libraries in your CMakeCache.txt in the build directory.  If not you might need to set an LDFLAGS in your environment or something. If the process doesn't have execute permissions on all the directories in the paths it won't find anything either because it can't search there.  Does it work if you run as root?   Alan ----- Radio Astronomy - the ultimate DX --- On Thu, 6/6/13, Robert Kiendl <Robert.Kiendl(a)automatis.com> wrote: From: Robert Kiendl <Robert.Kiendl(a)automatis.com> Subject: AW: rtl-tcp-server running on avm-fritzbox To: osmocom-sdr(a)lists.osmocom.org Date: Thursday, June 6, 2013, 3:52 AM Hi, I guess there is a permission problem accessing the device. Under normal conditions udev is doing the permission stuff when plugging in the device. I have had once the similar issue for own compiled binary mipsbe for mikrotik and tplink devices. Because of the lack of udev is simply altered the permission after plugging the dongle (something like /dev/dvb/adapter[something]  perms 755) This made it work afterwards. Hope this info helps, Ciao Robert, 73 de oe6rke -----Ursprüngliche Nachricht----- Von: osmocom-sdr-bounces(a)lists.osmocom.org [mailto:osmocom-sdr-bounces@lists.osmocom.org] Im Auftrag von df8oe(a)gmx.de Gesendet: Donnerstag, 06. Juni 2013 08:41 An: osmocom-sdr(a)lists.osmocom.org Betreff: rtl-tcp-server running on avm-fritzbox I want to use a rtl-dvb-stick connected to a fritz-box-dsl-router via tcp. Software running on the fritzbox is freetz (www.freetz.org) and cpu-architecture is mips. So I created a makefile and compiled the software without errors. But when I start the software (usb-dongle connected) it throws a usb_claim_interface error -5. rtl_test recognizes the type of stick correctly but throws identical error message. So I started rtl_test with strace - here you can find the output: http://www.df8oe.de/output.txt Any tipps for solving the problem are welcome ;) Best regards df8oe

df8oe(a)gmx.de wrote: .. Interface has a very specific meaning in USB. Please look into chapters 5 8 and 9 of the USB 2.0 spec available at usb.org to learn more. The interface can not be claimed because the kernel doesn't think that it exists. The error is actually really clear. USB is a packet bus with highly structured communication. Device nodes in /dev are not a good reference. df8oe(a)gmx.de wrote: Unfortunately the fritzbox has a useless mini lsusb program as opposed to the actual lsusb utility from the usbutils package. It would be great if you could build the real one. Somewhat less effort and still interesting would be to mount debugfs and then cat /sys/kernel/debug/usb/devices Other than that, it would be helpful if you could build a libusb binary with debug logging enabled. See http://libusb.org/wiki/debug for copypaste instructions that would apply to a host build. You must modify them as appropriate for your cross build of course. //Peter

df8oe(a)gmx.de wrote: What is your kernel version and what is your libusb-1.0 version? One thing that sticks out is: wTotalLength 8704 Another is: wMaxPacketSize 0x0002 1x 2 bytes These clearly show an endianness problem which would more likely be in your version of libusb-1.0 than in the kernel. //Peter

df8oe(a)gmx.de wrote: This kernel version is over two years old. I don't want to think about how many THOUSAND commits there have been in the kernel since then. This should be OK, but I'm not sure that it was tested very much on BE machines. Please build a version of the library with debugging. Of course you have to cross-compile libusb-1.0.9 (better yet libusb.git code) for the target. //Peter

Am Donnerstag, 6. Juni 2013, 21:18:25 schrieb Peter Stuge: If the interface does not exist: Where does the kernel get the following information (have a look at the log): "ezcap USB 2.0 DVB-T/DAB/FM dongl"..., 33ezcap USB 2.0 DVB-T/DAB/FM dongle) I think the interface cannot be opened or the binary thinks it cannot be opened (but it can be opened). When I plug in the stick correspondent devices are created under /dev/usb/ Andreas