 Wi-spy And X/qt, Will it work? |
  |
 Jun 21 2006, 06:07 PM
Post
#16
|
|
 Group: Members Posts: 693 Joined: 4-June 04 From: Ohio Member No.: 3,570  |
QUOTE(cvmiller @ Jun 21 2006, 04:39 PM) QUOTE(BarryW @ Jun 18 2006, 09:59 PM) Beats me. I'm not a programmer. I mostly just break stuff.  Color me dumb. I have been looking around trying to find libusb, only to see (tonight) that Meanie included it in his zip file. Barry, you did install libusb as well as the wispy-tools, right? Can you give us the last 10 lines (or so) of your dmesg command output right after inserting the wispy. thanks, Craig... I had already installed the same libusb that Meanie included. I tried Meanie's just incase it was different. here you go! usbh: monitor_int_hndlr: usbh: monitor_bh: usbh: udc_connected: ACTIVE_LOW: 1<7>usbh: monitor_connected: 1 usbh: monitor_load: 4 usbh: monitor_hotplug: agent: usbh interface: monitor action: load usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-ohci.c: USB OHCI at membase 0xfe000000, IRQ 3 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected hub.c: new USB device -2, assigned address 2 usb.c: USB device 2 (vend/prod 0x1781/0x83e) is not claimed by any active driver. |
 |
 
|
|
Jun 21 2006, 06:17 PM
Post
#17
|
|
 Group: Members Posts: 2,808 Joined: 21-March 05 From: Sydney, Australia Member No.: 6,686 |
QUOTE(BarryW @ Jun 22 2006, 12:07 PM) QUOTE(cvmiller @ Jun 21 2006, 04:39 PM) QUOTE(BarryW @ Jun 18 2006, 09:59 PM) Beats me. I'm not a programmer. I mostly just break stuff. Color me dumb. I have been looking around trying to find libusb, only to see (tonight) that Meanie included it in his zip file. Barry, you did install libusb as well as the wispy-tools, right? Can you give us the last 10 lines (or so) of your dmesg command output right after inserting the wispy. thanks, Craig... I had already installed the same libusb that Meanie included. I tried Meanie's just incase it was different. here you go! usbh: monitor_int_hndlr: usbh: monitor_bh: usbh: udc_connected: ACTIVE_LOW: 1<7>usbh: monitor_connected: 1 usbh: monitor_load: 4 usbh: monitor_hotplug: agent: usbh interface: monitor action: load usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-ohci.c: USB OHCI at membase 0xfe000000, IRQ 3 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected hub.c: new USB device -2, assigned address 2 usb.c: USB device 2 (vend/prod 0x1781/0x83e) is not claimed by any active driver. usb.c: USB device 2 (vend/prod 0x1781/0x83e) is not claimed by any active driver. yep, no kernel module/driver |
|
|
|
|
Jun 21 2006, 06:38 PM
Post
#18
|
|
|
Group: Members Posts: 242 Joined: 31-March 04 Member No.: 2,592 |
QUOTE(BarryW @ Jun 21 2006, 06:02 PM) This gives me a: wispy_gtk: error while loading shared libraries: libusb-0.1.4: cannot load shared object file: No such file or directory Same for curses. Both with root and the normal zaurus user. Hmm, that is kind odd, because you did install libusb, right? I ran ldd against the wispy-tools and it looks like it is going to find libusb just fine on my Z: bash-2.05# ldd wispy_curses libusb-0.1.4 => /usr/lib/libusb-0.1.4 (0x4002a000) libncurses.so.4 => /lib/libncurses.so.4 (0x4003b000) libc.so.6 => /lib/libc.so.6 (0x4009d000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) (ldd is on devimg if you have played with that) Can you check to see that you have libusb in /usr/lib/? Craig... |
|
|
|
|
Jun 21 2006, 08:36 PM
Post
#19
|
|
|
Group: Members Posts: 693 Joined: 4-June 04 From: Ohio Member No.: 3,570 |
QUOTE(cvmiller @ Jun 21 2006, 05:38 PM) QUOTE(BarryW @ Jun 21 2006, 06:02 PM) This gives me a: wispy_gtk: error while loading shared libraries: libusb-0.1.4: cannot load shared object file: No such file or directory Same for curses. Both with root and the normal zaurus user. Hmm, that is kind odd, because you did install libusb, right? I ran ldd against the wispy-tools and it looks like it is going to find libusb just fine on my Z: bash-2.05# ldd wispy_curses libusb-0.1.4 => /usr/lib/libusb-0.1.4 (0x4002a000) libncurses.so.4 => /lib/libncurses.so.4 (0x4003b000) libc.so.6 => /lib/libc.so.6 (0x4009d000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) (ldd is on devimg if you have played with that) Can you check to see that you have libusb in /usr/lib/? Craig... Yep, it's in there. lrwxrwxrwx 1 501 501 19 Jun 22 01:58 libusb-0.1.so.4 -> libusb-0.1.so.4.4.2 -rwxr-xr-x 1 root qpe 27592 Apr 11 20:46 libusb-0.1.so.4.4.2 lrwxrwxrwx 1 501 501 19 Jun 22 01:58 libusb.so -> libusb-0.1.so.4.4.2 lrwxrwxrwx 1 501 501 21 Jun 22 01:58 libusbpp-0.1.so.4 -> libusbpp-0.1.so.4.4.2 -rwxr-xr-x 1 root qpe 18556 Apr 11 20:46 libusbpp-0.1.so.4.4.2 lrwxrwxrwx 1 501 501 21 Jun 22 01:58 libusbpp.so -> libusbpp-0.1.so.4.4.2 Should I chown it to root? |
|
|
|
|
Jun 22 2006, 03:34 AM
Post
#20
|
|
|
Group: Members Posts: 242 Joined: 31-March 04 Member No.: 2,592 |
QUOTE(BarryW @ Jun 21 2006, 08:36 PM) Yep, it's in there. lrwxrwxrwx 1 501 501 19 Jun 22 01:58 libusb-0.1.so.4 -> libusb-0.1.so.4.4.2 -rwxr-xr-x 1 root qpe 27592 Apr 11 20:46 libusb-0.1.so.4.4.2 lrwxrwxrwx 1 501 501 19 Jun 22 01:58 libusb.so -> libusb-0.1.so.4.4.2 lrwxrwxrwx 1 501 501 21 Jun 22 01:58 libusbpp-0.1.so.4 -> libusbpp-0.1.so.4.4.2 -rwxr-xr-x 1 root qpe 18556 Apr 11 20:46 libusbpp-0.1.so.4.4.2 lrwxrwxrwx 1 501 501 21 Jun 22 01:58 libusbpp.so -> libusbpp-0.1.so.4.4.2 Should I chown it to root? Hmm, the sym links don't really matter (I believe) it is the actual ownership of the libusb library itself, and I can see that is owned by root, so it should be ok. Interestly enough your libusb library is a different size than mine. bash-2.05$ cd /usr/lib bash-2.05$ ls -l libusb* lrwxrwxrwx 1 root root 16 Jun 22 01:45 libusb -> libusb-0.1.4.4.0 lrwxrwxrwx 1 root root 16 Jun 22 01:45 libusb-0.1.4 -> libusb-0.1.4.4.0 lrwxrwxrwx 1 root root 19 Jun 22 01:45 libusb-0.1.4.4.0 -> libusb-0.1.4.4.0.so -rwxr-xr-x 1 root qpe 36968 Aug 12 2005 libusb-0.1.4.4.0.so lrwxrwxrwx 1 root root 19 Jun 22 01:45 libusb.so -> libusb-0.1.4.4.0.so Not sure why mine is 36k and yours is 27k. I installed the libusb that was included in Meanie's zip file. Is that the one you installed? Craig... |
|
|
|
|
Jun 22 2006, 08:30 AM
Post
#21
|
|
|
Group: Members Posts: 242 Joined: 31-March 04 Member No.: 2,592 |
QUOTE(Meanie @ Jun 21 2006, 06:17 PM) usb.c: USB device 2 (vend/prod 0x1781/0x83e) is not claimed by any active driver. yep, no kernel module/driver So isn't this just an issue of configuring hotplug to associate a driver with this device? Barry, do you know which driver is being used in your working slackware machine? Perhaps you can give us a list of your kernel modules (on the slackware machine) which include usb: /sbin/lsmod | grep usb Thanks, Craig... |
|
|
|
|
Jun 22 2006, 11:04 AM
Post
#22
|
|
|
Group: Members Posts: 693 Joined: 4-June 04 From: Ohio Member No.: 3,570 |
QUOTE(cvmiller @ Jun 22 2006, 07:30 AM) QUOTE(Meanie @ Jun 21 2006, 06:17 PM) usb.c: USB device 2 (vend/prod 0x1781/0x83e) is not claimed by any active driver. yep, no kernel module/driver So isn't this just an issue of configuring hotplug to associate a driver with this device? Barry, do you know which driver is being used in your working slackware machine? Perhaps you can give us a list of your kernel modules (on the slackware machine) which include usb: /sbin/lsmod | grep usb Thanks, Craig... It sees it as a keyboard. I've also compiled it in a knoppix live environment, and it sees it as a keyboard there as well. # /sbin/lsmod | grep usb usbserial 21372 0 [pl2303] usbkbd 3096 0 (unused) input 3296 0 [keybdev mousedev hid usbkbd] usbcore 62188 1 [pl2303 usbserial hid usbkbd uhci] |
|
|
|
|
Jun 23 2006, 05:16 PM
Post
#23
|
|
|
Group: Members Posts: 242 Joined: 31-March 04 Member No.: 2,592 |
QUOTE(BarryW @ Jun 22 2006, 11:04 AM) It sees it as a keyboard. I've also compiled it in a knoppix live environment, and it sees it as a keyboard there as well. Hmm, that is interesting. Well the good news is that there is a keyboard driver for the Zaurus. I have hooked up a USB keyboard to the Z and it works (sort of), with the exception that the key mapping is all wrong. So perhaps there is hope. Perhaps all that is needed is a hotplug config to link the device with the keyboard driver. I am heading to California in the morning, so perhaps I'll find a wi-spy there, if not I'll be ordering one when I get back. Craig... |
|
|
|
|
Jul 4 2006, 01:22 PM
Post
#24
|
|
|
Group: Members Posts: 242 Joined: 31-March 04 Member No.: 2,592 |
Well, I looked all over the SF Bay Area for this device. No luck. I'll have to mail-order one. I hope to have some more info soon (after I receive it).
Craig.... |
|
|
|
|
Jul 4 2006, 01:39 PM
Post
#25
|
|
|
Group: Members Posts: 693 Joined: 4-June 04 From: Ohio Member No.: 3,570 |
QUOTE(cvmiller @ Jul 4 2006, 12:22 PM) Well, I looked all over the SF Bay Area for this device. No luck. I'll have to mail-order one. I hope to have some more info soon (after I receive it). Craig.... Good to see you're still looking into it. My forhead hurts. I have thought about flashing pdax just to see if it works that way. |
|
|
|
|
Jul 7 2006, 06:59 PM
Post
#26
|
|
|
Group: Members Posts: 242 Joined: 31-March 04 Member No.: 2,592 |
QUOTE(BarryW @ Jul 4 2006, 01:39 PM) Good to see you're still looking into it. My forhead hurts. I have thought about flashing pdax just to see if it works that way. OK, got the unit via mail-order. Got through the "device not claimed" (modprobe hid). Created /dev/hiddev0, but still getting "unable to find device" problem. But I have only been working on this for a couple of hours. Unfortunately, I don't have strace to see exactly what the program (wispy_curses) is missing. I did plug it into my LinuxPPC laptop, and after making wispy_curses and wispy_gtk, it works fine. I do see differences between the LinuxPPC (kernel 2.6) and the Zaurus (2.4), which I am not sure about. On LinuxPPC, I see that it is the usbfs driver that is being used. I don't find a usbfs driver in the 2.4 kernel for the Zaurus (this could be a 2.6 only thing). Barry, is your Slackware Linux 2.4 or 2.6? Can you do a cat /proc/bus/usb/devices and see what driver the wispy is using? Mine reports: P: Vendor=1781 ProdID=083e Rev= 1.00 S: Manufacturer=MetaGeek S: Product=Wi-Spy C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 98mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbfs Craig... |
|
|
|
|
Jul 7 2006, 07:18 PM
Post
#27
|
|
|
Group: Members Posts: 693 Joined: 4-June 04 From: Ohio Member No.: 3,570 |
QUOTE(cvmiller @ Jul 7 2006, 05:59 PM) QUOTE(BarryW @ Jul 4 2006, 01:39 PM) Good to see you're still looking into it. My forhead hurts. I have thought about flashing pdax just to see if it works that way. OK, got the unit via mail-order. Got through the "device not claimed" (modprobe hid). Created /dev/hiddev0, but still getting "unable to find device" problem. But I have only been working on this for a couple of hours. Unfortunately, I don't have strace to see exactly what the program (wispy_curses) is missing. I did plug it into my LinuxPPC laptop, and after making wispy_curses and wispy_gtk, it works fine. I do see differences between the LinuxPPC (kernel 2.6) and the Zaurus (2.4), which I am not sure about. On LinuxPPC, I see that it is the usbfs driver that is being used. I don't find a usbfs driver in the 2.4 kernel for the Zaurus (this could be a 2.6 only thing). Barry, is your Slackware Linux 2.4 or 2.6? Can you do a cat /proc/bus/usb/devices and see what driver the wispy is using? Mine reports: P: Vendor=1781 ProdID=083e Rev= 1.00 S: Manufacturer=MetaGeek S: Product=Wi-Spy C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 98mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbfs Craig... It was 2.4. Unfortunetly my laptop died on me over the weekend. So no linux (other than my Z) till I can replace it. That could be a while. |
|
|
|
|
Jul 8 2006, 06:49 AM
Post
#28
|
|
|
Group: Members Posts: 242 Joined: 31-March 04 Member No.: 2,592 |
QUOTE(BarryW @ Jul 7 2006, 07:18 PM) It was 2.4. Unfortunetly my laptop died on me over the weekend. So no linux (other than my Z) till I can replace it. That could be a while. Bummers! I am sorry to hear that. OK, I have a little more info on how this thing works. libusb requires usbfs to be available. Unfortunatley in the 2.4 kernel, this must be built into the kernel (not a module). The stock sharp kernel does not have usbfs built in. I have the sharp kernel source, I can build a new kernel, but after that I am stuck. I don't know enough about how this thing boots to know where to put it, perhaps Meanie has some more info there. Perhaps the Guyhelm ROM includes usbfs, I'll have to do more research. But that appears to be the stopping point for the moment. Craig... |
|
|
|
|
Nov 27 2006, 12:19 AM
Post
#29
|
|
 Group: Moderators Posts: 1,619 Joined: 29-October 03 From: Los Angeles Member No.: 809 |
QUOTE(BarryW @ Jun 18 2006, 09:59 PM) Beats me. I'm not a programmer. I mostly just break stuff. Yes and I can testify your honor! He basterdized the sl-6000 with twinkly lights!  Anyway, Curious to see what this does cuz my c-3200 has no adhoc and cannot make it work with previous wifi sniffers. |
|
|
|
|
Nov 27 2006, 09:11 AM
Post
#30
|
|
|
Group: Members Posts: 693 Joined: 4-June 04 From: Ohio Member No.: 3,570 |
QUOTE(Cresho @ Nov 26 2006, 11:19 PM) QUOTE(BarryW @ Jun 18 2006, 09:59 PM) Beats me. I'm not a programmer. I mostly just break stuff. Yes and I can testify your honor! He basterdized the sl-6000 with twinkly lights! Anyway, Curious to see what this does cuz my c-3200 has no adhoc and cannot make it work with previous wifi sniffers. You need to get yourself an ambicom wifi card. Kismet works on my 3200. |
|
|
|
|
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:
|
Lo-Fi Version | Time is now: 22nd May 2013 - 08:20 PM |