[SOLVED] Upgrading Slackware 14 to Kernel 3.2.45 resulted in black screen on boot.
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.
The only issue I observed is with mplayer using sdl. When changing resolutions
while in full screen mplayer crashes and the screen changes to a weird
resolution. This happens with both kernels 3.2.29 and 3.2.45.
I've tried downlowding the latest mplayer source from mplayer site and
compiling it. The result is the same.
If you have it in 3.2.29 as well that it is not the same issue as we are specifically talking about regressions since the upgrade.
Patrick asked about issues with intel graphics. I have an intel graphic card and that's the only issue I've had. The mplayer issue is not important for me that's why I didn't open a new thread for that.
The sdl package was updated too. That's other reason that made me think it could be related.
Mon Jun 3 22:10:16 UTC 2013
patches/packages/linux-3.2.45/*: Rebuilt.
One more reverted commit. This one was leading to hangs on systems with
Intel graphics. The previous revert was also reverted in 3.2.46, but it
seems safer to just get this one manually than to take the newer kernel and
still have to do another patch to it anyway. Hopefully the third time is
the charm. :)
+--------------------------+
Just another confirmation that the second patched kernel package for 3.2.45 also locks up X for me (same driver, dell optiplex machine). Deleting the lines as indicated by Philippe and rebuilding works for me (no problems in the past few hours.)
Just another confirmation that the second patched kernel package for 3.2.45 also locks up X for me (same driver, dell optiplex machine). Deleting the lines as indicated by Philippe and rebuilding works for me (no problems in the past few hours.)
There's an official third build by Patrick Volkerding available now (see the above post by hitest, quoting the Slackware changelog): this rebuild fixes the i915 issue by reverting the same commit that you already removed manually. However, it is possible that your mirror isn't up-to-date yet (if the build date is 22 May 2013 then it's still the second one).
Philip
Last edited by Philip Lacroix; 06-04-2013 at 10:18 AM.
Originally Posted by dr.s View Post
I use a virtualbox guest vm that I clone and copy to a desktop and a laptop as needed (for experimentation, testing stuff etc.)
The guest runs Slackware 14.0 with the 3.2.29 stock kernel, upgrading to 3.2.45 was straightforward as usual but launching X within the guest brought up a frozen black screen with a blinking cursor at the top left corner. I rebooted the guest and tried again after uninstalling/reinstalling the guest additions but that didn't help.
Aside from reverting to 3.2.29, found only these 2 workarounds:
-remove the guest additions, X starts working again (issue re-occurs if I reinstall the additions)
-upgrade to 3.8.13, this apparently resolves everything with no issues so far, guest + X + additions working smoothly.
Quote:
Originally Posted by gonzas
I have the same issue. Have you found what causes the problem? I would like to keep both the additions and 3.2.45 :-)
Thank you.
I upgraded to the 3rd kernel build and the problem remains.
Third build works great for me also, but then again I have an Nvidia card so the problems didn't really apply to me anyway. But at least I can say that the new build didn't screw anything new up.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.