[SOLVED] Screen remains off after resuming from suspend to ram after upgrading kernel.
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.
Screen remains off after resuming from suspend to ram after upgrading kernel.
After I had upgraded my kernel from 4.0.4 to 4.1.13 my screen stays off when resuming from suspend to disk. I filed a bug report on Bugzilla already concerning this. https://bugzilla.kernel.org/show_bug.cgi?id=107721 Does anyone know of a work around for this in the mean time?
What makes it crucial for you to need 4.1.13 instead of 4.0.4? If there is no specific feature/bug-fix that requires you to use 4.1.13, the obvious work around would be to move back to the working 4.0.4 kernel.
What makes it crucial for you to need 4.1.13 instead of 4.0.4? If there is no specific feature/bug-fix that requires you to use 4.1.13, the obvious work around would be to move back to the working 4.0.4 kernel.
There are some bugs in 4.0.4 as well as 4.0.5. One of them is in concern of ext4 corruption under certain circumstances. As far as I can tell, I wasn't affected by that bug. However there are some rather annoying bugs in both 4.0.4 and 4.0.5 involving the hard disk constantly being accessed after the system has been running for a certain period of time. This problem also happens shortly after a resume from either suspend or hibernate. It makes the system so sluggish that it is almost unusable. The only way to fix it is to reboot. 4.0.5 has an additional problem that prevents PHC from working which I use. Also the 4.0.x kernels are EOL'ed so any problems with them will not be fixed so there is no point in reporting them. As a result I was very interested in getting away from those kernels. Since the 4.1.x kernels are still being maintained it made sense to move to that line of kernels.
My hardware is a Dell Latitude D620 with an nVidia Quadro NVS 110M rev.a1
Perhaps silly questions, but to be sure.
Do you use the nVidia proprietary driver, and if so, did you rebuild the kernel module after the kernel upgrade?
Perhaps silly questions, but to be sure.
Do you use the nVidia proprietary driver, and if so, did you rebuild the kernel module after the kernel upgrade?
No I use the Nouvuea one. version 1.0.9. I never got around to trying to compile the nVidia one.
It would be good to know whether you can replicate the issue when using the nVidia proprietary driver.
While I have great sympathy for the Nouveau project, I believe that the company that produces the hardware is in the best position to write the software that supports it.
It would be good to know whether you can replicate the issue when using the nVidia proprietary driver.
While I have great sympathy for the Nouveau project, I believe that the company that produces the hardware is in the best position to write the software that supports it.
I switched to the nVidia driver and that fixed the problem. Thanks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.