Jonathan, It sounds like your problem has to do with interaction of the SVN and the already install code on the RPi2 We have a number of Allstar systems installed on Raspberry Pis. They are all running Debian Jessie and the latest SVN nad URIs without issues. If you want to run with the SVN code, you can start with a clean base image and add Asterisk. I have built some scripts that will ease this process. You can DL the entire install script, patches for RPi and tweaked config files from: <https://github.com/N4IRS/AllStar> You can also pick and choose any of the scripts or patches you like from the above. 73, Steve N4IRS On 06/09/2015 05:37 AM, app_rpt-users-request@ohnosec.org wrote:

Message: 4 Date: Tue, 09 Jun 2015 05:37:07 -0400 From: Jonathan Merwin<pyrodox@icloud.com> To:"app_rpt-users@ohnosec.org" <app_rpt-users@ohnosec.org> Subject: [App_rpt-users] Bug with latest SVN on Raspberry Pi/URIx Message-ID:<74C6CF65-EDCE-4983-BBF2-3EBA00B51622@icloud.com> Content-Type: text/plain; charset=us-ascii

I'm not sure if this belongs here, or over at the Arm list. But I've noticed a bug with the current SVN version of app_rpt on the Raspberry Pi 2 V1.0 Allstar system.

Initial setup is fine, everything is working well. When I download the current SVN of app_rpt, complie and install it, I run into a bug. I'm using the Raspberry Pi 2 version B with a DMK URIx.

After installation of the current SVN version of app_rpt, upon reboot, Asterisk/app_rpt will start as normal, I hear my repeater's ID, nodes connected, courtesy and function tones, etc. It will repeat, all seems to be functioning normally... But after about a minute app_rpt throws an "HID thread died or something!!" error and starts flooding the Asterisk CLI screen with "can't detach usb device" errors from chan_usbradio. At this point my URIx starts slow flashing. Asterisk/app_rpt will no longer output any audio, it will not repeat, nothing.

Weird part is, if I call astres.sh, Asterisk/app_rpt will restart and work as normal, and it doesn't throw the HID error. It only does this on a cold boot, after losing power, etc.

Has anyone else encountered this?