SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Personally, I'd just wait for 2.6.38. I'm running 2.6.38-rc8 and it's apparently one of the better kernels since, oh, 2.6.33 or so. The kernel developers need a slap upside their heads .. At least, Pat has a sense of humor about the mess.
Anyway, moving to 2.6.37 is a better choice than providing "LTS" for an incomplete and buggy 2.6.35 ... Who wants that kind of service?
Many thanks to Pat and all the team. Leet rc1 behaving quite nicely atm although I have to spend MUCH more time to really asses the release. Can't wait to get the dvd with the release # printed thereon...and the t-shirts will be priceless.
Audacious from 1337 (Audacious 2.4.3) gives this error when playing (stream, or local files):
** WARNING **
Audacious has detected that your ALSA device has a broken timer. A workaround
is being used to prevent CPU overload. Please report this problem to your
Linux distributor or to the ALSA developers.
Also, Audacious developers said:
Please submit bug reports to your distribution unless you built the very latest version of Audacious yourself. We do not provide end-user support.
Current release is 2.4.4 (February 22, 2011)
Current testing release is 2.5-beta1 (March 11, 2011)
I have to say that I don't see any other problem with 2.4.3, except that "ugly" notice about broken timer when playback starts, and I also don't know if 2.4.4 fixes that problem.
I noticed the broken timer message in audacious the other day. It seems to only show if you're using the 'default' dmix device. When I change the properties for the alsa plugin to use hw:0 the message goes away, so it looks like it's something to do with alsa's dmix. Only problem with doing this though is that unless your card can do hardware mixing, you're limited to one sound output at a time.
I tried updating to 2.4.4 but that's just the same.
Oh well.. don't know what to say then.. except that I just found this on the Audacious forum:
..The broken timer is an ALSA problem and cannot be fixed within Audacious; it must be fixed in ALSA. That's why the message says to report the problem to your distribution or to the ALSA developers. Not to us.