Although my system works fine I realized performing a dmesg command (through putty) gives lots of sentences like:
Last login: Thu Apr 30 22:15:13 2009 from 192.168.0.7
root@meteohub:~$ dmesg
rq 9 len 8 ret -110
<7>usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd hidlog rqt 33 rq 9 len 8 ret -110
<7>usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd hidlog rqt 33 rq 9 len 8 ret -110
and this hundreds of times.
Is that meaning I need to replace USB stick as soon as posible?
Chill
USB in peril?
Moderator: Mattk
Re:USB in peril?
It's me again!
New info related with USBDEVFS_CONTROL failed :huh:
I've two NSLU2 (one for replacement purposes).
I've two USB sticks ready to go.
I discovered the main USB stick gave this error I reported last message. Then I replaced USB (but I had to re-enter all configuration even when I was performing Restore Settings, browsing to the folder where it was and pushing Load File
)
The amazing thing is when I perform a new dmesg to both meteohub's systems:
The older one looks fine NO MORE USBDEVFS_CONTROL failed messages
The main one outputs hundreds of USBDEVFS_CONTROL failed
So far, what is the trouble? I guess it is NSLU2...
Does it make any sense?
What to do?
Chill
New info related with USBDEVFS_CONTROL failed :huh:
I've two NSLU2 (one for replacement purposes).
I've two USB sticks ready to go.
I discovered the main USB stick gave this error I reported last message. Then I replaced USB (but I had to re-enter all configuration even when I was performing Restore Settings, browsing to the folder where it was and pushing Load File
The amazing thing is when I perform a new dmesg to both meteohub's systems:
The older one looks fine NO MORE USBDEVFS_CONTROL failed messages
The main one outputs hundreds of USBDEVFS_CONTROL failed
So far, what is the trouble? I guess it is NSLU2...
Does it make any sense?
What to do?
Chill
Re:USB in peril?
At the moment I would not be too worried. This does not look like USB stick problems, but like connection issues on the weather station via USB. WMR-200 is known for being a bit problematic and providing connection issues. Nevertheless, Meteohub does it's best to try a connection again and again to overcome these problems. As far as I know, you can do just a few things to improve:
- use quality USB cable with ferrite cores at the ends.
- empty wmr200 internal data logger and set internal logging interval to the lowest possible value to slow down logger on running full with data.
- use quality USB cable with ferrite cores at the ends.
- empty wmr200 internal data logger and set internal logging interval to the lowest possible value to slow down logger on running full with data.

