<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Im not quite sure how to put this politically correctly, so I wont even attempt it.<br><br>USB SUCKS!<br><br>Okay.. I said it :-) (I feel better now)<br><br>Under most conditions experienced by users of chan_usbradio and chan_simpleusb, the USB interface in the<br>Linux kernel works well and reliably. And when it works, it works consistently.<br><br>HOWEVER, there are cases where its just plain and simply broken. Newer kernels have made attempts to<br>fix some problems, and have, in fact, made things even more broken.<br><br>Whatever you do, dont try using chan_usbradio with a Muilti-TT hub. Its not a pretty picture.<br><br>Many people in many instances use this stuff on a regular basis with no problems. Unfortunately,<br>that experience is not able to be shared by everyone. <br><br>As is typical, the world continues to be broken. :-)<br><br>JIM WB6NIL<br><br><br>> From: ajp26@buffalo.edu<br>> To: app_rpt-users@ohnosec.org<br>> Date: Thu, 10 Mar 2011 14:02:56 -0500<br>> Subject: [App_rpt-users] DMK URI and Segfault<br>> <br>> Afternoon,<br>> <br>> I've been working on setting up a simplex node using a DMK URI and a HTX-212, and I have many things I need to iron out. I've found I have some sort of trouble going on, when the PTT is keyed, in a varying but, often short period of time, the unit shuts off. The cable is still open and unshielded, so I imagine this to probably be the source of that problem. Outside of this, I can't see any good way to reset the device without hanging the system. If I pull the unit, it recognizes that it is gone, but, re-attaching it causes the machine to lock hard with some display on the screen that seems to be in reference to this device or USB something-or-other. This is on my desktop, ACID Linux, i7 870, Intel Extreme motherboard. <br>> <br>> Has anyone had this one happen? Obviously, I'd prefer not to unplug it anyways, but, with the troubleshooting, it seems I must do so.<br>> <br>> Adam<br>> KC2YQF<br>> <br>> Also, it seems the kickstart script looks for /dev/hda to start with, mine are all sXX drives, which seemed to work out anyways, it picked "sdd" using some process I'm not sure of. It also did me the favor of eliminating the partition table on all of my other drives, which, while recoverable, wasn't particularly thrilling.<br>> <br>> <br>> <br>> <br>> _______________________________________________<br>> App_rpt-users mailing list<br>> App_rpt-users@ohnosec.org<br>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br> </body>
</html>