Bug 6428

Summary:	Suspend and hibernate not working with kernel 3.3.6!
Product:	Mageia	Reporter:	Tolhildan Karker <tolhildan_123>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	major
Priority:	Normal	CC:	mageia
Version:	2
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Tolhildan Karker 2012-06-12 12:12:55 CEST

I have problem with suspend/hibernate with my laptop. The kernel I use is the latest 3.3.6-desktop586-2.mga2 kernel in Mageia 2 KDE, 32-bit. I know this is not graphical driver issue. I recently tried another distribution that did come with kernel 3.3.X. Same problem there. Over there my temporary solution was to use kernel 3.1.X. I know also kernel 3.2.X works with suspend/hibernate. So this is upstream bug that I hope Mageia finds a way to fix. Maybe newer kernel or something. Other then that Mageia have been a blessing in performance and stability. I will now give hardware information maybe the team would like to have. 

uname -r 
3.3.6-desktop586-2.mga2

lshw
http://paste.kde.org/497864/

hwinfo
http://paste.kde.org/497882/

dmidecode
http://paste.kde.org/497876/

I hope this enough information about hardware etc. Please tell me if something more is needed. 

Thanks!

Comment 1 Tolhildan Karker 2012-06-12 12:16:04 CEST

It is more wake up from suspend and hibernate that does not seems to work.

Thanks!

Comment 2 Tolhildan Karker 2012-06-12 12:59:43 CEST

Okey I got it fixed. It is not kernel or graphical driver issue/bug. The problem was that Mageia after installation of nvidia-blobs had different set in nvidia-settings -> X Server Display Configuration -> Configuration had picked disabled. I changed it to "Seperate X Screen" instead. So now it works. I also unchecked "Lock screen in action". After that every thing works just fine. 

Sorry that I did not check does thing first. I did not thought Mageia would pick "disabled" instead of "Seperate X Screen". So this post can be marked as "fixed". I hope this maybe can help others in my situation. 

Thanks!

Comment 3 Sander Lepik 2012-06-12 19:55:25 CEST

Ok, closing.

Status: NEW => RESOLVED
CC: (none) => sander.lepik
Resolution: (none) => INVALID