Bug 104229

Summary:	"Media keys" cause lockup on eMachines M68xx laptop.
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Steve Leach <stevenaleach>
Component:	Basesystem	Assignee:	Dr. Werner Fink <werner>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	trenn
Version:	Beta 1
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Steve Leach 2005-08-11 19:02:45 UTC

Both openSUSE 10.0 beta1 32 and 64 bit are effected.

Booting install, install no acpi, or install safe will all freeze if any
"special" key is pressed, this includes the screen brightness up or down keys
volume keys, etc.

After the kernel has been loaded, the screen brightness is set at its lowest
level.  If, at any point, the brightness up key is pressed the system will freeze.

The system in question is an eMachines m6805 with bios updated with m6809 bios
(m6805/m6807 bios is buggy and will not work with Linux).

Comment 1 Timo Hoenig 2005-08-11 19:26:33 UTC

This seems to be a known problem of the e6805:

<quote>
After installing Debian, the laptop booted okay, but anytime you touched any of the 'special keys' 
(including the ones to adjust the screen brightness), or close the lid, the thing would freeze. So, to 
make it work right, you have to fix the ACPI DSDT table. (For more info on ACPI, go here: http://acpi.
sourceforge.net). I fixed the DSDT table until it compiled cleanly. 
<quote>

See: http://greg.primate.net/m6805/ for more infomation and a fix.

trenn: Do we have a feature to detect systems with broken DSDT and load sane ones for the 
affected systems?

Comment 2 Thomas Renninger 2005-08-11 20:18:04 UTC

No.

If I understand this right, you use a BIOS of another machine?
The hardware address of the key probably is another, no wonder it freezes -> bug
is invalid, sorry.

You could either: take the DSDT of the m6809 and try to find out the I/O address
you need to adjust from m6805.

Or even better, fix the m6805 DSDT.
If you promise to nag your vendor to implement the changes and publish it on:
http://acpi.sourceforge.net/dsdt/tables/
I can have a look at...

Oh there already are already two.
Hmm, those DSDTs are hardware dependant (how much memory, etc.). You should
downgrade to the latest BIOS designed for your machine, extract and disassemble
the DSDT. Then try to recompile. Try to fix the errors based on the one you find
at the link above.

How you disassemble and recompile your DSDT, you find some hints here:
http://powersave.sourceforge.net/powersave/DSDT.html#DSDT

If you have problems you can mail me privately.