Bug 1829

Summary:	energy management differs between 32bit-Live-CD and 64bit-Installation
Product:	Mageia	Reporter:	Bicycle RepairMan <eagle150>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	lohmaier+mageia, marja11, stormi-mageia
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	Kernel	CVE:
Status comment:

Description Bicycle RepairMan 2011-06-16 21:30:40 CEST

Description of problem:
Using the Mageia1-Live-CD (a 32bit system, I suppose)dimming the display of my Samsung R730-JT07 laptop works with the hotkeys and via the battery management-app (in the lower right corner). After installing the 64bit version of Mageia1 on the same laptop, the hotkeys for dimming the display only show a small GUI, just like the one of KMix that shows the level of brightness of the screen. The only problem is that the screen brightness doesn't change at all. Using the slider in the battery management-app doesn't do anything either.

Version-Release number of selected component (if applicable):
Kernel 2.6.38.7 in the 32bit or 64bit variety

How reproducible:
Using the energy management from the Live-CD works, but not from the 64bit installation

I suspect that the differences in the kernel between the 32bit and the 64bit version are responsible for this bug.

Comment 1 Samuel Verschelde 2011-10-01 13:28:28 CEST

tmb: could differences between those kernels explain this bug?

CC: (none) => stormi
Assignee: bugsquad => tmb

Comment 2 Christian Lohmaier 2011-10-23 03:31:44 CEST

you might also try to add "acpi_backlight=vendor" to the kernel boot parameters

CC: (none) => lohmaier+mageia

Comment 3 Marja Van Waes 2012-01-25 07:55:11 CET

Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED.

Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. Don't change anything if you want to be pinged by me here again :)

CC: (none) => marja11

Comment 4 Marja Van Waes 2012-05-06 22:20:16 CEST

@ BicycleRepairMan

Is this issue still valid with the 64 bit Mga2b3 or 2rc LiveCD?

Keywords: (none) => NEEDINFO
Version: 1 => Cauldron

Comment 5 Bicycle RepairMan 2012-05-08 20:41:26 CEST

Well, I downloaded and burned Mageia-2-beta3-LiveCD-KDE4-Europe1-Americas-x86_64-CD.iso just for this, but I can't start it because of the stupid "system has to be rebooted due to a display driver change"-error. Yes, I have an NVIDIA-card, no, rebooting doesn't change anything. No, after that error-message I can't do anything. There is a green OK stuck in the lower right corner of the screen and the system is frozen. The only way to restart is to unplug the computer.
So, sorry, I would really like to help you to further this bug report, but I simply can't.

Comment 6 Thomas Backlund 2012-05-08 20:58:55 CEST

A few alternatives to get it to boot:

boot with xdriver=nouveau
(should boot with open source nouveau driver)

boot with rdblacklist=nouveau
(should boot with nvidia driver)

Comment 7 Marja Van Waes 2012-05-26 13:03:48 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Comment 8 Marja Van Waes 2012-07-06 15:04:59 CEST

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Comment 9 Marja Van Waes 2012-08-03 20:25:11 CEST

2x no reply, closing as old

Feel free to reopen if needed and tell in which fully updated Mageia version(s) you still have this issue

Status: NEW => RESOLVED
Resolution: (none) => OLD