Bug 2831

Summary:	custom DSDT in initrd found but ignored completely
Product:	Mageia	Reporter:	Christian Lohmaier <lohmaier+mageia>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	major
Priority:	Normal	CC:	dbello, liberforce, marja11
Version:	2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kernel	CVE:
Status comment:
Attachments:	dmesg log with modified dsdt in initrd

Description Christian Lohmaier 2011-09-24 22:35:32 CEST

Description of problem:
It's impossible to override DSDT using initrd method, despite the dsdt being found, the one used by the kernel still is the one provided by the bios

Version-Release number of selected component (if applicable):
Mageia 1 - on Fujitsu Siemens Esprimo Mobile U9200

How reproducible:
100%

Steps to Reproduce:
1. dump dsdt table
# cat /sys/firmware/acpi/tables/DSDT > dsdt_bios.dat
2. decode table using iasl package
# iasl -d dsdt_bios.dat
3. edit decoded dsdt to fix some bugs. (in my case needed for Battery-state detection, it is to correct the nesting of an else statement, see https://wiki.ubuntu.com/LaptopTestingTeam/Old/FujitsuEsprimoU9200 for the concrete fix, but as the fix is irrelevant for the detection, just do a similar change)
# vim dsdt_bios.dsl
4. compile the modified version and add it to the initrd & reboot
# iasl -ta dsdt_bios.dsl
# cp dsdt.aml /boot/dsdt.aml
# echo "dsdt_files=/boot/dsdt.aml" >> /etc/sysconfig/mkinitrd
# bootloader-config --action rebuild-initrds
# shutdown -r now
5. verify that the dsdt from the initrd is "used" (more like: the dsdt did make it into the initrd - after all this bug is about that the modified version is not in action)
# dmesg|grep -A1 custom
ACPI: Checking initramfs for custom DSDT
ACPI: Found DSDT in DSDT.aml.
6. dump dsdt table again - expected is that it would not be the same as the one from the bios
# cat /sys/firmware/acpi/tables/DSDT > dsdt_modified.dat
7. compare the bios version and the one obtained after booting with the modified initrd:
# md5sum dsdt_bios.dat dsdt_modified.dat
92ba2300e0f3d7bd519507120ae33b90 dsdt_bios.dat
92ba2300e0f3d7bd519507120ae33b90 dsdt_modified.dat

â major bug, as overriding the buggy dsdt is the only way to get proper hardware support esp. one some older hardware.

Manuel Hiebel 2011-09-24 23:39:02 CEST

Assignee: bugsquad => tmb

Comment 1 Thomas Backlund 2011-09-25 21:08:07 CEST

Can you provide full dmesg output

Comment 2 Christian Lohmaier 2011-09-26 18:06:59 CEST

Created attachment 843 [details]
dmesg log with modified dsdt in initrd

not sure how the full dmesg log would help here as the additional line "ACPI: Found DSDT in DSDT.aml." is the only visible difference. Anyway, dmesg log is attached.

Comment 3 Christian Lohmaier 2011-10-14 15:55:21 CEST

do you need more info? Can't you reproduce?

Luis Menina 2011-10-19 15:25:24 CEST

CC: (none) => liberforce

Comment 4 Diego Bello 2011-11-22 22:23:20 CET

Any news on this?

I posted bug 1563 (https://bugs.mageia.org/show_bug.cgi?id=1563) and I was told the bug lays on this one.

Is there a way I can help to solve this?

CC: (none) => dbello

Comment 5 Christian Lohmaier 2011-12-17 01:14:20 CET

Good news (for me at least) is that alpha2/GNOME3 correctly handles the battery/ac state despite the apparently buggy DSDT - so either appropriate fixes went into the kernel, or GNOME3 uses a different method (once again) to check battery status.
While it doesn't solve the original problem, it solves the reason for needing this workaround (at least for me - but worth to try with alpha2 and check whether the problem is fixed for you (Diego) as well)

Comment 6 Marja Van Waes 2012-04-26 22:13:30 CEST

Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.

Please set status to ASSIGNED if you think this bug was assigned correctly.

CC: (none) => marja11

Comment 7 Marja Van Waes 2012-07-06 15:05:40 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 8 Manuel Hiebel 2012-11-05 16:53:32 CET

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Comment 9 Manuel Hiebel 2012-12-02 14:32:46 CET

Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

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

Comment 10 Diego Bello 2013-03-09 18:18:10 CET

I just tried this on Mageia 2 and still doesn't work.

So far, the only way I can make my laptop see the battery is to recompile the kernel.

Status: RESOLVED => REOPENED
Version: 1 => 2
Resolution: WONTFIX => (none)

Manuel Hiebel 2013-03-09 18:23:06 CET

Source RPM: kernel-2.6.38.8-5.mga1.src.rpm => kernel

Comment 11 Luis Menina 2013-03-10 00:46:02 CET

AFAIK, the kernel policy is to have BIOS problems fixed in the kernel, to avoid clumsy workarounds like changing the DSDT which may harm your hardware. So I think you should concentrate efforts on bug #1563.

Status: REOPENED => RESOLVED
Resolution: (none) => WONTFIX