search for: seveeral

Displaying 4 results from an estimated 4 matches for "seveeral".

Did you mean: several
2009 Mar 31
2
What is the one thing that polycom can do...
...eekly conference/podcast. While not the one 'big picture' item that polycom should be focusing on, one could reasonably argue it would rank right up there in terms of 'bang for the buck' because it would be such an easy tweak. If this irks you as well, go make yourself heard. If seveeral people say the same thing, perhaps they'll do something about it. Maybe they actually ARE listening :-) -Karl -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090331/aec85e75/attachment.htm
2014 Sep 30
0
Tripp-Lite USB constantlly disconnecting.
...> If you run lsusb several times, does it still work? The exact output of lsusb isn't as important as whether anything gets logged by the kernel. Running lsusb shouldn't cause any extra kernel messages such as the disconnection/reconnection messages shown here: Running lsusb seveeral times works just fine and no disconnects are observed. > This doesn't seem to match the source code, which tries to claim the interface up to three times, and if it doesn't work, it exits with a fatal error. Your logs show the same PID for usbhid-ups, so it apparently didn't exi...
2014 Sep 30
2
Tripp-Lite USB constantlly disconnecting.
On Sep 29, 2014, at 12:50 PM, Shade Alabsa <shade34321 at gmail.com> wrote: > The lsusb command did not trigger a disconnect. The output of that > command is below. If you run lsusb several times, does it still work? The exact output of lsusb isn't as important as whether anything gets logged by the kernel. Running lsusb shouldn't cause any extra kernel messages such as
2014 Nov 18
2
Tripp-Lite USB constantlly disconnecting.
...veral times, does it still work? The exact > output of lsusb isn't as important as whether anything gets logged by > the kernel. Running lsusb shouldn't cause any extra kernel messages > such as the disconnection/reconnection messages shown here: > > Running lsusb seveeral times works just fine and no disconnects > are observed. > > > This doesn't seem to match the source code, which tries to claim > the interface up to three times, and if it doesn't work, it exits with > a fatal error. Your logs show the same PID for usbhid-ups, so it &...