LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-11-2015, 03:56 PM   #1
Arcosanti
Member
 
Registered: Apr 2004
Location: Mesa, AZ USA
Distribution: Slackware 14.1 kernel 4.1.13 gcc 4.8.2
Posts: 246

Rep: Reputation: 22
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?
 
Old 11-11-2015, 04:24 PM   #2
moesasji
Member
 
Registered: May 2008
Distribution: Slackware Current / OpenBSD
Posts: 322

Rep: Reputation: 104Reputation: 104
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.
 
Old 11-11-2015, 05:26 PM   #3
Arcosanti
Member
 
Registered: Apr 2004
Location: Mesa, AZ USA
Distribution: Slackware 14.1 kernel 4.1.13 gcc 4.8.2
Posts: 246

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by moesasji View Post
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.
 
Old 11-12-2015, 01:18 AM   #4
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,377

Rep: Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757
From the bug report
Quote:
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?
 
Old 11-12-2015, 02:02 AM   #5
Arcosanti
Member
 
Registered: Apr 2004
Location: Mesa, AZ USA
Distribution: Slackware 14.1 kernel 4.1.13 gcc 4.8.2
Posts: 246

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by allend View Post
From the bug report

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.
 
Old 11-12-2015, 06:10 AM   #6
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,377

Rep: Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757
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.
 
Old 11-12-2015, 01:50 PM   #7
Arcosanti
Member
 
Registered: Apr 2004
Location: Mesa, AZ USA
Distribution: Slackware 14.1 kernel 4.1.13 gcc 4.8.2
Posts: 246

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by allend View Post
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.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Problems after resuming from suspend to ram chessonly Linux - General 1 08-10-2012 07:55 AM
udev/hal issue upon resuming from suspend to ram radu.pop Linux - Software 1 11-14-2009 09:21 PM
[SOLVED] suspend to ram resuming ok with vbe post - what does it mean? kushalkoolwal Linux - Software 2 07-30-2009 11:48 AM
Keyboard Doesn't Work After Resuming from Suspend to Ram beartooth91 Slackware 11 03-05-2009 01:18 PM
how to execute a command automatically after resuming from suspend to RAM? bjharker Linux - General 5 11-24-2008 08:00 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:12 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration