SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Put 3.1 on this morning. Don't really have much to offer about the new power-management features, however, alsa now recognises my sound hardware more accurately, so I'm a happy bunny
Last edited by GazL; 10-25-2011 at 09:21 PM.
Reason: turned out it wasn't the quirks code that made the difference
Isn't 3.1.x series the development kernel and not the mainstream stable like 3.0.x?
It was until Linus tagged it as 3.1.0 and released it. 3.1.y is now a stable branch.
There may be some merit to staying back on 3.0.y for a little while longer to let the new one settle down - I normally wait for the .1 or .2 - but because of the improvement in support for my sound hardware, I'll risk being an early adopter this time around.
My point in power management is because i have a core i7 and cpufreq don't seem to output info about turbo boost or incorporate that in the scaling of freqs.
This new utility is supposed to be better in this aspect.
My point in power management is because i have a core i7 and cpufreq don't seem to output info about turbo boost or incorporate that in the scaling of freqs.
This new utility is supposed to be better in this aspect.
If this comment is still valid, you'll need to rebuild pciutils package with shared libpci enabled for cpupowerutils to work.
I've been running the 3.1.0 kernel since this last Saturday. Everything is looking good, but does anyone see the migragtion/x using up to 90% CPU? The funny thing is, although 'ps' states migration is at 90% CPU, it really isn't - CPU looks fine about ~4% total usage.
Put 3.1 on this morning. Don't really have much to offer about the new power-management features, however, alsa now recognises my sound hardware more accurately, so I'm a happy bunny
My experience may be related. For a year or two now I lived with a regression that prevented speakers from being muted when headphones were plugged in. It only manifested on this one computer. Linux 3.1 fixed it.
Last edited by qweasd; 10-26-2011 at 04:06 PM.
Reason: Version
I've been running the 3.1.0 kernel since this last Saturday. Everything is looking good, but does anyone see the migragtion/x using up to 90% CPU? The funny thing is, although 'ps' states migration is at 90% CPU, it really isn't - CPU looks fine about ~4% total usage.
Seems ok here.
Code:
root@slack:~# ps aux |head -1 ; ps aux |grep [m]igration
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 6 0.0 0.0 0 0 ? S 09:35 0:00 [migration/0]
root 7 0.0 0.0 0 0 ? S 09:35 0:00 [migration/1]
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
