<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 09/03/2014 12:45 PM, Loren Tedford
wrote:<br>
</div>
<blockquote
cite="mid:CAK=eTyjd_byCc_fL8ydxQohKu8+Df7TqWpXhi-NFhVDtibC0KQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hello having issues running both repeaters for some
reason it is telling me that Device usb27103 currently not
active what does this mean? its all plugged in was working then
all the suddenly stopped working randomly is it not detecting
the device number correctly with the URI? I am running 2 Cm200
on vhf for this repeater and node 29925 is running flawlessly
with out any issues with 2 Cm200 on UHF<br>
<br>
</div>
</blockquote>
<br>
Sometimes, things happen. Some software bug causes the usb daemon
to fall, or something...<br>
<br>
On that note, I did a quick google search for start/stop/status on
usb devices for CentOS and came up with<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.zedt.eu/tech/linux/restarting-usb-subsystem-centos/">http://www.zedt.eu/tech/linux/restarting-usb-subsystem-centos/</a><br>
<br>
Their suggestion of looking in <code>/sys/bus/pci/drivers/ehci_hcd
or xhci_hcd doesn't exist in my directory path. So, I did a
'lsusb' and came up with:<br>
[root@W5OMR /sys/bus/usb/drivers/usbfs]# lsusb<br>
Bus 005 Device 001: ID 0000:0000 <br>
Bus 005 Device 003: ID 0d8c:013a C-Media Electronics, Inc. <br>
Bus 005 Device 002: ID 0d8c:013a C-Media Electronics, Inc. <br>
Bus 002 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 for
Business<br>
Bus 002 Device 001: ID 0000:0000 <br>
Bus 001 Device 001: ID 0000:0000 <br>
Bus 003 Device 001: ID 0000:0000 <br>
Bus 004 Device 001: ID 0000:0000 <br>
</code><br>
<br>
From the link, they suggest;<code><br>
<br>
echo -n "0000:00:xx.y" > unbind</code>
<p>Remember to enable them back:</p>
<p><code>echo -n "0000:00:xx.y" > bind</code></p>
<p>where instead of <tt>xx.y</tt> you fill in the correct set of
numbers to use the IDs discovered above.</p>
<p>This procedure is the same for all RHEL-like distributions (Red
Hat Enterprise, CentOS, Fedora).<br>
</p>
<br>
The bottom line is, there's hardly ever a reason to reboot an entire
working Linux operating system loaded machine.<br>
Services can stopped and restarted from the command line without the
need to reboot the entire system.<br>
<br>
I have had, on occasion, the need to restart the networking
sub-system. By performing a <br>
<br>
root@w5omr> /etc/init.d/networking restart<br>
<br>
takes care of that problem.<br>
<br>
Just my 0.02c <br>
<br>
73 = Best Regards,<br>
-Geoff/W5OMR<br>
<br>
</body>
</html>