3 ms·
That was an USB 1.x issue, had nothing to do with the sound chip behind the USB interface. Yeah, that's right, the kernel crew broke something pretty fundament
by hga 10y ago
That was an USB 1.x issue, had nothing to do with the sound chip behind the USB interface. Yeah, that's right, the kernel crew broke something pretty fundamental in that primarily desktop device driver (servers are going do be doing heavy duty things with USB 2 and above), and nobody noticed and/or cared enough to not ship it with squeeze.
That's also the version that broke the Wacom support as I recall, it came back with wheezy or maybe Ubuntu Vivid's kernel.
Pulse Audio is pretty awful, but I've always been able to get it to do my bidding, modulo not being able to get the Ubuntu version I'm using to multiplex outputs (I can probably make that happen, it's not a Pulse Audio issue per se I'm pretty sure, but it's just easier to switch output from stereo system to headphones the few times I use Skype).
- digi_owl 10y agoAh yes, USB. Could be the powersave/suspend issue. Iirc, the kernel implemented it as if there was a upper limit on how long the device could take to get ready after a resume. But apparently the time mentioned in the spec was just a suggestion, not a hard limit. And many devices would take a minute or longer to come back once resumed. Lets just say that USB is a "fun" protocol, and the latest addition has not helped much.
- hga 10y agoIt was as I recall a timing/time out issue, and very possibly the one you describe, it would just have to not effect the normal keyboard and mouse USB 1.x devices, and I'm pretty sure these USB 1.x sound devices had much better than "a minute or longer" times in resuming. And, yeah, I can imagine how much of a zoo USB in the real world is....