Installation problem

141 views
Skip to first unread message

zl1klp

unread,
Feb 29, 2012, 10:26:58 PM2/29/12
to wfrog-users
Hi all,
trying to install wfrog for the first time on my ALIX3D2 running
debian + WMR200. Everything seems ok after dpkg -i,but when running, I
get this:

wfrog
Exception in thread Thread-3:
Traceback (most recent call last):
File "/usr/lib/python2.6/threading.py", line 532, in
__bootstrap_inner
self.run()
File "/usr/lib/python2.6/threading.py", line 484, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/lib/wfrog/wfdriver/wfdriver.py", line 117, in run
self.station.run(gen, self.enqueue_event)
File "/usr/lib/wfrog/wfdriver/station/wmr200.py", line 349, in run
self.logData()
File "/usr/lib/wfrog/wfdriver/station/wmr200.py", line 439, in
logData
self.sendCommand(0xD0)
File "/usr/lib/wfrog/wfdriver/station/wmr200.py", line 210, in
sendCommand
self.sendPacket([0x01, command, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00])
File "/usr/lib/wfrog/wfdriver/station/wmr200.py", line 196, in
sendPacket
self.devh.controlMsg(usb.TYPE_CLASS + usb.RECIP_INTERFACE,
AttributeError: 'NoneType' object has no attribute 'controlMsg'

Any idea?
Kind regards,
Riku

zl1klp

unread,
Feb 29, 2012, 10:35:24 PM2/29/12
to wfrog-users
further: wfrog.log

2012-03-01 03:34:12,014 INFO [config] Starting wfrog 0.8.2
2012-03-01 03:34:12,016 INFO [config] Loaded settings file /etc/wfrog/
settings.yaml
2012-03-01 03:34:14,938 INFO [config] Starting wfrog 0.8.2
2012-03-01 03:34:14,939 INFO [config] Loaded settings file /etc/wfrog/
settings.yaml
2012-03-01 03:34:14,952 INFO [station.wmr200] Thread started
2012-03-01 03:34:14,958 INFO [station.wmr200] USB initialization
2012-03-01 03:34:15,016 INFO [station.wmr200] Oregon Scientific
weather station found
2012-03-01 03:34:15,018 INFO [station.wmr200] Manufacturer: 0
2012-03-01 03:34:15,019 INFO [station.wmr200] Product: 1
2012-03-01 03:34:15,020 INFO [station.wmr200] Device version: 03.02
2012-03-01 03:34:15,025 INFO [station.wmr200] USB version: 01.10
2012-03-01 03:34:15,035 INFO [station.wmr200] Unloaded other driver
from interface 0
2012-03-01 03:34:15,382 INFO [config] Starting wfrog 0.8.2
2012-03-01 03:34:15,384 INFO [config] Loaded settings file /etc/wfrog/
settings.yaml
2012-03-01 03:34:15,465 INFO [renderer.http] Started server on port
7680
2012-03-01 03:34:16,225 ERROR [station.wmr200] WMR200 connect failed:
error sending control message: Device or resource busy
Traceback (most recent call last):
File "/usr/lib/wfrog/wfdriver/station/wmr200.py", line 259, in
connectDevice
0xA, [], 0, 0, int(usbTimeout * 1000))
USBError: error sending control message: Device or resource busy
2012-03-01 03:34:16,230 ERROR [station.wmr200] Can't write request
record: error sending control message: Device or resource busy
Traceback (most recent call last):
File "/usr/lib/wfrog/wfdriver/station/wmr200.py", line 198, in
sendPacket
timeout = int(usbTimeout * 1000))
USBError: error sending control message: Device or resource busy
2012-03-01 03:34:16,231 ERROR [station.wmr200] WMR200 disconnect
failed: could not release intf 0: Invalid argument
Traceback (most recent call last):
File "/usr/lib/wfrog/wfdriver/station/wmr200.py", line 319, in
disconnectDevice
self.devh.releaseInterface()
USBError: could not release intf 0: Invalid argument

Chris Schlaeger

unread,
Mar 1, 2012, 3:32:18 AM3/1/12
to wfrog...@googlegroups.com

Either you have problems with your USB stack in the Linux kernel or
there is another program accessing the device already.

Chris

zl1klp

unread,
Mar 1, 2012, 4:18:23 AM3/1/12
to wfrog-users
So in your view the trouble starts from here?

Chris Schlaeger

unread,
Mar 1, 2012, 2:11:43 PM3/1/12
to wfrog...@googlegroups.com

No, that's done be default to ensure that we get a cleanly initialized
driver. Maybe /var/log/messages has some helpful details.

Chris

Riku Luostari

unread,
Mar 1, 2012, 3:01:03 PM3/1/12
to wfrog...@googlegroups.com
Ok, here the /var/log/messages. At 19:52:35 I plugged in the WMR200 and at
19:55:24 started wfrog. To me it seems to be going ok up until wfrog does
something funny for whatever the reason - I'm puzzled.

Cheers,
Riku

Mar 1 19:52:35 HamServer kernel: [63184.660591] usb 2-2: new low speed USB
device using ohci_hcd and address 4
Mar 1 19:52:35 HamServer kernel: [63184.867575] usb 2-2: New USB device
found, idVendor=0fde, idProduct=ca01
Mar 1 19:52:35 HamServer kernel: [63184.867621] usb 2-2: New USB device
strings: Mfr=0, Product=1, SerialNumber=0
Mar 1 19:52:35 HamServer kernel: [63184.867663] usb 2-2: Product: Universal
Bridge
Mar 1 19:52:35 HamServer kernel: [63184.869971] usb 2-2: configuration #1
chosen from 1 choice
Mar 1 19:52:35 HamServer kernel: [63184.879003] generic-usb
0003:0FDE:CA01.000C: hiddev0,hidraw0: USB HID v1.10 Device [Universal
Bridge] on usb-0000:00:0f.4-2/input0
Mar 1 19:55:24 HamServer kernel: [63354.398098] usb 2-2: reset low speed
USB device using ohci_hcd and address 4
Mar 1 19:55:25 HamServer kernel: [63354.756474] generic-usb
0003:0FDE:CA01.000D: hiddev0,hidraw0: USB HID v1.10 Device [Universal
Bridge] on usb-0000:00:0f.4-2/input0
Mar 1 19:55:25 HamServer kernel: [63355.258336] usb 2-2: usbfs: process
1370 (wfrog) did not claim interface 0 before use
Mar 1 19:55:25 HamServer kernel: [63355.263377] usb 2-2: usbfs: process
1370 (wfrog) did not claim interface 0 before use

Riku Luostari

unread,
Mar 1, 2012, 6:42:05 PM3/1/12
to Riku Luostari, wfrog...@googlegroups.com
Hi again,
Made a bit of progress, but I don't think it is as it should. Removed hid &
usbhid modules using modprobe -r, as a result it started working. However if
I reboot the computer I will end up in the same situation needing to
manually remove hid and usbhid again. As if some other process already
claims usbhid. From message log it doesn't seem that way though.
Cheers,
Riku

Chris Schlaeger

unread,
Mar 2, 2012, 2:05:01 PM3/2/12
to wfrog...@googlegroups.com, Riku Luostari

That looks suspiciously like you have some program probing the USB
devices and this is jamming the usbhid or hid driver.

Chris

Reply all
Reply to author
Forward
0 new messages