latest detector series not recognized by app on linux


Advanced search

Message boards : Number crunching : latest detector series not recognized by app on linux

Author Message
ChristianB
Send message
Joined: 24 Jul 12
Posts: 2
Credit: 24,707
RAC: 0

Message 1569 - Posted: 9 Jan 2013 | 20:02:17 UTC

I'm running one sensor from the latest batch of detectors on my debian 64bit host at home. I created a udevd rule

ATTR{idVendor}=="04d8", MODE="666", GROUP="plugdev"
and the sensor is also recognized by the kernel.
I recognized that the vendor ID is not (yet) in the sensors.xml file that comes with the radac application. Is this preventing the sensor from beeing detected? And when is it fixed?

This is the host in question: 3063

"dmesg" wrote:
[ 1.719158] usb 3-1: New USB device found, idVendor=04d8, idProduct=f6fe
[ 1.719161] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.719164] usb 3-1: Product: radioactiveathome.org GRS
[ 1.719165] usb 3-1: Manufacturer: microchip


"lsusb -v" wrote:
Bus 003 Device 002: ID 04d8:f6fe Microchip Technology, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x04d8 Microchip Technology, Inc.
idProduct 0xf6fe
bcdDevice 3.01
iManufacturer 1 microchip
iProduct 2 radioactiveathome.org GRS
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.01
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 22
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 100
Device Status: 0x0001
Self Powered
[/quote]

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

Message 1570 - Posted: 10 Jan 2013 | 23:13:08 UTC - in response to Message 1569.

I'll update all the Linux apps today.

ChristianB
Send message
Joined: 24 Jul 12
Posts: 2
Credit: 24,707
RAC: 0

Message 1571 - Posted: 11 Jan 2013 | 12:54:28 UTC

Thanks, now the backlight is off at least. We'll see more in 2 hours when the first job is finished.

Profile Saenger
Send message
Joined: 16 Jun 11
Posts: 165
Credit: 606,948
RAC: 145

Message 1572 - Posted: 11 Jan 2013 | 15:52:38 UTC - in response to Message 1571.

Thanks, now the backlight is off at least. We'll see more in 2 hours when the first job is finished.

Looks OK to me, congratz to your first credits ;)
____________
Gruesse vom Saenger

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

Message 1575 - Posted: 11 Jan 2013 | 23:08:20 UTC - in response to Message 1572.

1.72 fixes the problem and I hope it will work for everyone, it wasn't supposed to be released yet (very little tests were done), however there was a bug in the USB code, without update the app would not see the 3.01 sensor even with sensors.xml patched.

During the weekend I'll patch & update the Raspberry Pi app (until then 3.01 on Pi is not supported).

Dagorath
Avatar
Send message
Joined: 4 Jul 11
Posts: 151
Credit: 42,738
RAC: 0

Message 1578 - Posted: 12 Jan 2013 | 5:05:44 UTC - in response to Message 1575.

During the weekend I'll patch & update the Raspberry Pi app (until then 3.01 on Pi is not supported).


Just in case you didn't hear about it, the latest BOINC client beta/alpha has changes to ARM architecture recognition. It won't be long before that becomes the released code. You might want to think about that and prepare. I heard about it in this post and this post at Asteroids@home project. I'm not sure if it has implications for R@H, it's just an FYI.

____________

Profile The Dreamer
Avatar
Send message
Joined: 16 Jun 11
Posts: 11
Credit: 416,790
RAC: 0

Message 1579 - Posted: 12 Jan 2013 | 22:05:52 UTC

I got an email that my sensor was disconnected....no, its still there.

But, noticed that the app kept restarting. Finally tracked it down...and in stderr.txt it was saying every 11 seconds: "No heartbeat from client for 30 sec - exiting", and then restarting....

Radac $Rev: 560 $ starting...
claimed interface, could not get bound driver: No data available,0
sensors.xml: 6 nodes found
Found sensor v2.51
3321607,910,2013-1-12 17:31:42,593,n,381683167
[11 seconds later - pid]: No heartbeat from client for 30 sec - exiting
. . .

Looking back through my tasks...things were working with v1.69 up to Jan 11. When it got a v1.70...which ran 3 times longer than v1.69 and got 0 credits. And, then v1.72 which have all been failing with "Error While Computing".

Though compiling the 7.0.28 boinc_client for my Linux box seems to have it working again. They don't make it easy to find or build non-HEAD client_releases....(missing m4 and .h and .in files at the client_release_7.0.28 level) (the version from boinc.berkeley.edu needs newer libraries than 10.04.4LTS has...and there was some other reason that I needed to upgrade the 6.12.33 to keep running projects on this 32-bit server, but it continues to work fine on my 64-bit server) Also wasn't obvious that I couldn't checkout client_release_7.0.28 until after I had checked out client_release_7.0....

Anyways...seems downgrading to the recommended 7.0.28 seems better than the development 7.0.44 version....

The Dreamer.

Wonder when my other sensor is going to arrive....
____________
You may be a dreamer, but I'm The Dreamer, the definite article you might say!

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

Message 1593 - Posted: 16 Jan 2013 | 16:34:34 UTC - in response to Message 1579.

Nothing essential was changed in the app code between 1.69 and later Linux releases, so if there is a problem, it's coming from the latest BOINC API.
I'm already looking at this, however my Linux host seems to be unaffected so far. I'll check with latest development version of BOINC client.

Claggy
Send message
Joined: 29 Jul 12
Posts: 9
Credit: 149,374
RAC: 0

Message 1595 - Posted: 16 Jan 2013 | 21:08:37 UTC - in response to Message 1593.
Last modified: 16 Jan 2013 | 21:17:07 UTC

Nothing essential was changed in the app code between 1.69 and later Linux releases, so if there is a problem, it's coming from the latest BOINC API.
I'm already looking at this, however my Linux host seems to be unaffected so far. I'll check with latest development version of BOINC client.

Same problem at Einstein with their latest Linux apps, they had to rebuild them with an earlier api:

Trouble with Gamma-ray pulsar search #2 v0.01

Claggy

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

Message 1598 - Posted: 18 Jan 2013 | 10:43:15 UTC - in response to Message 1595.

I upgraded the app with the latest API, does it work now ?

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 45
Credit: 410,583
RAC: 171

Message 1602 - Posted: 19 Jan 2013 | 14:26:13 UTC
Last modified: 19 Jan 2013 | 14:26:56 UTC

Hi

The new version has fixed the problem for me as well on Centos 64 Bit that was reported on this thread. http://radioactiveathome.org/boinc/forum_thread.php?id=172

I have noticed that the signatures are all screwed up though with the new version ??

Radac $Rev: 560 $ starting...
Detached driver: usbhid
claimed interface, No error,0
sensors.xml: 6 nodes found
Found sensor v2.01
262750,120,2013-1-19 14:22:35,513,f,381683167
303290,138,2013-1-19 14:23:16,513,n,381683167
343840,154,2013-1-19 14:23:56,513,n,381683167
384380,168,2013-1-19 14:24:37,513,n,381683167
424930,190,2013-1-19 14:25:18,513,n,381683167
____________

Proud Founder of
Have a look at my WebCam

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

Message 1603 - Posted: 19 Jan 2013 | 14:45:35 UTC - in response to Message 1602.

App version does not affect sigs, your is not working now probably due to a glitch which happens sometimes on suspend/resume and then causes wrong scale on the graph (negative readings).

____________

Profile Dingo
Avatar
Send message
Joined: 16 Jun 11
Posts: 45
Credit: 410,583
RAC: 171

Message 1604 - Posted: 20 Jan 2013 | 3:09:56 UTC - in response to Message 1603.

Thanks for the response it happened at the same time and I assumed, never should do that, it was the app. I should have known to just sit and wait a while.
Cheers
____________

Proud Founder of
Have a look at my WebCam

Post to thread

Message boards : Number crunching : latest detector series not recognized by app on linux


Main page · Your account · Message boards


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