[App_rpt] issue with hid interface in chan_usbradio
Greetings everyone: Was curious if anyone has run into an issue with the usbradio channel driver when running Asterisk under it's own user and group? I have run up against what I think is a permissions issue of sorts. I did have everything running briefly when Asterisk was set up to run under root access, but really want to avoid that if possible. The chan_usbradio driver errors when claiming the (usb) hid interface from the kernel. Apparently, it's getting an error at what would be line 791 in the chan_usbradio.c source code. Which then results in a call to 'usb_detach_kernel_driver_np', on line 793, in an attempt to detach the kernel interface, where it ultimately fails. I've tried a couple simple approaches to resolve this, like setting the dsp and usb device to have asterisk as their owner/group and also set permissions (with '666') for the devices. I would look at modifiying udev.rules and PAM configurations, but at this point, I'm clueless as to what is conflicting with the hid interface for the usb soundfob. Whew! Anyone have any suggestions? Thanks! Mike, K3XH
well, to my knowledge you have to run asterisk as root. I never tested it any other way, and I dont know of any other way of doing it.
From: K3XH <k3xh@embarqmail.com> Reply-To: Asterisk Repeater Controler <app_rpt@lists.illiana.net> To: app_rpt@lists.illiana.net Subject: [App_rpt] issue with hid interface in chan_usbradio Date: Fri, 19 Oct 2007 12:50:30 -0400 MIME-Version: 1.0 Received: from marauder.illiana.net ([75.146.102.69]) by bay0-mc9-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Fri, 19 Oct 2007 09:50:46 -0700 Received: (qmail 25590 invoked by uid 1484); 19 Oct 2007 16:50:37 -0000 Received: from 127.0.0.1 by marauder (envelope-from <app_rpt-bounces@lists.illiana.net>, uid 71) with qmail-scanner-2.01 (clamdscan: 0.84/2481. Clear:RC:1(127.0.0.1):. Processed in 0.088859 secs); 19 Oct 2007 16:50:37 -0000 Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 19 Oct 2007 16:50:37 -0000 Received: (qmail 25484 invoked by uid 1484); 19 Oct 2007 16:50:32 -0000 Received: from 208.47.184.3 by marauder (envelope-from <k3xh@embarqmail.com>,uid 71) with qmail-scanner-2.01 (clamdscan: 0.84/2481. Clear:RC:0(208.47.184.3):. Processed in 0.02196 secs); 19 Oct 2007 16:50:32 -0000 Received: from mailrelay.embarq.synacor.com (208.47.184.3)by 0 with SMTP; 19 Oct 2007 16:50:32 -0000 Received: neutral (smtp07.embarq.synacor.com: 67.77.126.178 is neitherpermitted nor denied by domain of embarqmail.com) Received: from [67.77.126.178] ([67.77.126.178:23695] helo=emperor.localdomain)by mailrelay.embarq.synacor.com (envelope-from <k3xh@embarqmail.com>)(ecelerity 2.2.0.18 r(18773)) with ESMTPAid 05/B1-08049-750E8174; Fri, 19 Oct 2007 12:50:31 -0400 X-Message-Delivery: Vj0zLjQuMDt1cz0wO2k9MDtsPTA7YT0w X-Message-Info: 6sSXyD95QpVfqbreACdgbRzhs9qETUz+OELLLU6zsiat1nnucDgZrBpVsvwl4j3C3D4Lln2ggTM7IxezyEM4vA== Return-Path: <k3xh@embarqmail.com> Delivered-To: mailman-app_rpt@lists.illiana.net Return-Path: <k3xh@embarqmail.com> X_CMAE_Category: 0,0 Undefined,Undefined X-CNFS-Analysis: v=1.0 c=1 a=DGUrQvzGQEq9E0QPYzgA:9a=gX08BCMhzZHnSlaTbBVZ24jrByQA:4 a=LVFWH4gLBqYA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Authentication-Results: smtp07.embarq.synacor.comsmtp.mail=k3xh@embarqmail.com; spf=neutral Authentication-Results: smtp07.embarq.synacor.comsmtp.user=mike-h@embarqmail.com; auth=pass (LOGIN) User-Agent: Thunderbird 2.0.0.4 (X11/20070604) X-BeenThere: app_rpt@lists.illiana.net X-Mailman-Version: 2.1.6 Precedence: list List-Id: Asterisk Repeater Controler <app_rpt.lists.illiana.net> List-Unsubscribe: <http://lists.illiana.net/mailman/listinfo/app_rpt>,<mailto:app_rpt-request@lists.illiana.net?subject=unsubscribe> List-Archive: <http://lists.illiana.net/pipermail/app_rpt> List-Post: <mailto:app_rpt@lists.illiana.net> List-Help: <mailto:app_rpt-request@lists.illiana.net?subject=help> List-Subscribe: <http://lists.illiana.net/mailman/listinfo/app_rpt>,<mailto:app_rpt-request@lists.illiana.net?subject=subscribe> Errors-To: app_rpt-bounces@lists.illiana.net X-OriginalArrivalTime: 19 Oct 2007 16:50:46.0792 (UTC) FILETIME=[32335080:01C81270]
Greetings everyone:
Was curious if anyone has run into an issue with the usbradio channel driver when running Asterisk under it's own user and group?
I have run up against what I think is a permissions issue of sorts. I did have everything running briefly when Asterisk was set up to run under root access, but really want to avoid that if possible.
The chan_usbradio driver errors when claiming the (usb) hid interface from the kernel. Apparently, it's getting an error at what would be line 791 in the chan_usbradio.c source code. Which then results in a call to 'usb_detach_kernel_driver_np', on line 793, in an attempt to detach the kernel interface, where it ultimately fails.
I've tried a couple simple approaches to resolve this, like setting the dsp and usb device to have asterisk as their owner/group and also set permissions (with '666') for the devices. I would look at modifiying udev.rules and PAM configurations, but at this point, I'm clueless as to what is conflicting with the hid interface for the usb soundfob. Whew!
Anyone have any suggestions?
Thanks! Mike, K3XH _______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
Steve / Jim Duuuude! ... Thanks for the reply... Yeah, I've been running Asterisk under it's own userid/group on my other box, so I tried setting up the rpt box the same. But what I've finally found is... that the Linux kernel claims hid interfaces when devices are 'inserted' and then does not seem to readily relinquish them to 'user-space' applications (???). There 'supposedly' is a means to indicate to the kernel to 'ignore' a particular class of device by rebuilding the kernel with a modified hid_blacklist struct (in source file '/usr/src/kernels/linux-2.6.23.1/drivers/hid/usbhid/hid-quirks.c' for kernel 2.6.23.1) with the hex code of the vendor and deviceid to ignore. I tried building the kernel in this fashion, but the issue remains... Go figure... So I decided to make my life easier and just run Asterisk as root. At least I now have the latest kernel running on my box... Thanks... mike. ...app_rpt rocks.... Jim Duuuude wrote:
well, to my knowledge you have to run asterisk as root. I never tested it any other way, and I dont know of any other way of doing it.
Mike, When might you have a radio interfaced? Do you need a node number assigned for Allstar Link? Steve, WA6ZFT K3XH wrote:
Steve / Jim Duuuude! ...
Thanks for the reply... Yeah, I've been running Asterisk under it's own userid/group on my other box, so I tried setting up the rpt box the same.
But what I've finally found is... that the Linux kernel claims hid interfaces when devices are 'inserted' and then does not seem to readily relinquish them to 'user-space' applications (???).
There 'supposedly' is a means to indicate to the kernel to 'ignore' a particular class of device by rebuilding the kernel with a modified hid_blacklist struct (in source file '/usr/src/kernels/linux-2.6.23.1/drivers/hid/usbhid/hid-quirks.c' for kernel 2.6.23.1) with the hex code of the vendor and deviceid to ignore. I tried building the kernel in this fashion, but the issue remains... Go figure... So I decided to make my life easier and just run Asterisk as root. At least I now have the latest kernel running on my box...
Thanks... mike. ...app_rpt rocks....
Jim Duuuude wrote:
well, to my knowledge you have to run asterisk as root. I never tested it any other way, and I dont know of any other way of doing it.
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
Steve, Right now I'm waiting for some components to arrive to get a soundfob constructed. Unless I'm mistaken, the usb channel driver looks like it can handle multiple soundfobs? Initially I'd like to try setting up a two-meter and 70-cm in a remote base configuration to test with. Although I won't need a node for Allstar right now, it's something that I'm very receptive to, once I've had a basic configuration operational for a while. 73, Mike. Stephen Rodgers wrote:
Mike,
When might you have a radio interfaced? Do you need a node number assigned for Allstar Link?
Steve, WA6ZFT
See below... K3XH wrote:
Steve,
Right now I'm waiting for some components to arrive to get a soundfob constructed. Unless I'm mistaken, the usb channel driver looks like it can handle multiple soundfobs?
Yes, but get one channel working at a time. Initially I'd like to try setting up a
two-meter and 70-cm in a remote base configuration to test with.
Although I won't need a node for Allstar right now, it's something that I'm very receptive to, once I've had a basic configuration operational for a while.
Probably a good idea as we prefer full duplex repeaters on allstarlink.
73, Mike.
Stephen Rodgers wrote:
Mike,
When might you have a radio interfaced? Do you need a node number assigned for Allstar Link?
Steve, WA6ZFT
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
participants (3)
-
Jim Duuuude -
K3XH -
Stephen Rodgers