Specified device was not found


Advanced search

Message boards : Number crunching : Specified device was not found

Author Message
Profile Steve Hawker*
Send message
Joined: 4 Mar 13
Posts: 23
Credit: 132,088
RAC: 0

Message 1879 - Posted: 10 Jul 2013 | 22:59:46 UTC

From the output: Could not find any of the devices listed in sensors.xml: The specified device was not found

I'm using Linux Mint.
I ran usermod as suggested
WU was completed and validated but no credit, as I would expect as the sensor wasn't found.

This also explains my buzzer issue because if the sensor isn't found, then the command to turn off the buzzer won't get through (same with backlight too I suspect)

What edits to sensors.xml do I need?

Also, what does that button do on the end of the sensor?

Thanks

Steve

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,370,831
RAC: 71

Message 1882 - Posted: 11 Jul 2013 | 17:21:20 UTC - in response to Message 1879.

Do not edit the sensors.xml, it's supplied by the server and by default describes all our sensors.

You have to find out why the app does not see the sensor. Could you run 'lsusb' to see if it is seen by the O/S ?

Profile Steve Hawker*
Send message
Joined: 4 Mar 13
Posts: 23
Credit: 132,088
RAC: 0

Message 1883 - Posted: 12 Jul 2013 | 1:37:45 UTC - in response to Message 1882.

Do not edit the sensors.xml, it's supplied by the server and by default describes all our sensors.

You have to find out why the app does not see the sensor. Could you run 'lsusb' to see if it is seen by the O/S ?


i have 3 devices, all found by lsusb

Bus 005 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 005 Device 003: ID 04d8:f6fe Microchip Technology, Inc.
Bus 006 Device 002: ID 1b1c:0c04 Corsair

Profile TJM
Project administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,370,831
RAC: 71

Message 1894 - Posted: 13 Jul 2013 | 21:09:13 UTC - in response to Message 1883.

Could you try running the app standalone, as root ?
You'll have to rename the sensors_1.77.... to sensors.xml, the app saves the output to stderr.txt.

Profile Steve Hawker*
Send message
Joined: 4 Mar 13
Posts: 23
Credit: 132,088
RAC: 0

Message 2048 - Posted: 8 Oct 2013 | 8:47:08 UTC - in response to Message 1894.
Last modified: 8 Oct 2013 | 8:47:24 UTC

Could you try running the app standalone, as root ?
You'll have to rename the sensors_1.77.... to sensors.xml, the app saves the output to stderr.txt.


What am I doing wrong here?

Galactica radioactiveathome.org_boinc # whoami
root
Galactica radioactiveathome.org_boinc # pwd
/var/lib/boinc-client/projects/radioactiveathome.org_boinc
Galactica radioactiveathome.org_boinc # ls -l
total 904
-rwxr-xr-x 1 boinc boinc 918132 Jul 8 20:22 radac_1.77_i686-pc-linux-gnu__nci
-rw-r--r-- 1 boinc boinc 2819 Jul 8 20:22 sensors.xml
Galactica radioactiveathome.org_boinc # radac_1.77_i686-pc-linux-gnu__nci
radac_1.77_i686-pc-linux-gnu__nci: command not found
Galactica radioactiveathome.org_boinc #

I tried the group setup - i confirmed the users were added
I created the rules file using ATTRS
I rebooted
I lit a candle and played Dark Side of the Moon

I am now utterly spent.

btw, the sensor worked flawlessly first time on an ancient Win XP machine but now I must let my wife have that back.
____________

mickydl*
Send message
Joined: 12 Jul 12
Posts: 3
Credit: 636,765
RAC: 149

Message 2049 - Posted: 8 Oct 2013 | 13:22:56 UTC - in response to Message 2048.
Last modified: 8 Oct 2013 | 13:23:23 UTC

Hi Teammate :)

try

./radac_1.77_i686-pc-linux-gnu__nci

Notice the dot and the forward-slash in front of the program name to indicate the current directory. In most Linux distributions the current directory is not in the search path (for security reasons) when you are root.

I hope that helps.

mickydl*

Profile Steve Hawker*
Send message
Joined: 4 Mar 13
Posts: 23
Credit: 132,088
RAC: 0

Message 2051 - Posted: 9 Oct 2013 | 19:53:06 UTC - in response to Message 2049.

Hi Teammate :)

try

./radac_1.77_i686-pc-linux-gnu__nci

Notice the dot and the forward-slash in front of the program name to indicate the current directory. In most Linux distributions the current directory is not in the search path (for security reasons) when you are root.

I hope that helps.

mickydl*


Thanks! Now I see it, I remember doing this before, and of course it worked.

The outcome was that the detector was found. So my conclusion is that the rules is the problem. So i'm going to try your suggestion from our team site, which I reread this morning.

Profile Steve Hawker*
Send message
Joined: 4 Mar 13
Posts: 23
Credit: 132,088
RAC: 0

Message 2052 - Posted: 9 Oct 2013 | 21:08:14 UTC

I now have my sensor working and reporting on my Linux box all thanks to the amazing mickeydl*

Awesome.

Post to thread

Message boards : Number crunching : Specified device was not found


Main page · Your account · Message boards


Copyright © 2024 BOINC@Poland | Open Science for the future