© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Guess you're right, for some (to me unknown) reason linux-preempt is not built for i386...
As for the underrun question: if you get "alsa-sink.c: Underrun!", that's the alsa driver telling PA it didn't get any buffers from PA in time.
If you get something like "protocol-native.c: Underrun on 'Rythmbox', 0 bytes in queue.", that's PA didn't get any buffers from Rythmbox in time.
Roughly, everything starting with "alsa-sink.c" or "alsa-source.c" in the log is related to PA - Alsa driver communication, and everything else is related to Client - PA communication.
The PA - alsa connection should work even if the client misbehaves, but that's a simplification - in some cases the client can affect the PA - alsa communication by e g specifying what latency it needs.