[SOLVED] kernel 3.2.x causes system freeze on Intel Ivy Bridge platform(e.g. ThinkPad T430)?
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.
FWIW, you used the wrong command for verification. Greg K-H signed the ".tar" file before compressed it using various compression algorithms. The right command in your case should be:
Hey guys, unfortunately i've nothing helpful to contribute to this conversation, but i just thought i'd say that i've also been experiencing freezes, except, on sandy bridge. I experience these freeze issues in Slackware 14 and Opensuse 12.2 on my thinkpad x220, i was beginning to think it was a hardware issue, (i'm still not convince it isn't for my situation). Opensuse runs the 3.4.6-2.10 kernel already. I'm going to try out the tips here on my Slack partition and hopefully they will work as i'm slowly converting my main laptop partition back to Slackware again, and it'd be great to remove this issue.
Oops, I missed the "unxz" command before that. Anyway, with the above method you keep things clean using just original downloaded files.
Yes, but if you forgot to import the key it will take longer because you'll have to run xz again. You only have to run unxz once. I delete the tarball afterwards anyway, what use is there to keep it ?
I had this problem too on an Asus R500VD ivy bridge, and also in an Acer A5920 intel 2 duo processor.
With aid of http://slackware.mirrors.tds.net/pub...sting-3.6-rc4/ i`m able to build the 3.6.3 kernel and it seems to be working fine until now.
Unfortunately i`m not own the acer notebook anymore to build a newer kernel to it, but the problem ocurred there too.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.