Bug 7477 - ACPI not working fine with A6km.
Summary: ACPI not working fine with A6km.
Status: CLOSED UNREPRODUCIBLE
Alias: None
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: acpi_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-08 23:23 UTC by Dominique Derrier
Modified: 2007-11-07 09:32 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.17-10-generic (ubuntu)
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
DSDT from /proc/acpi (BIOS 210) (29.07 KB, application/octet-stream)
2006-11-08 23:26 UTC, Dominique Derrier 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Dominique Derrier 2006-11-08 23:23:08 UTC 
Most recent kernel where this bug did not occur: 2.6.17-10-generic 
(unbuntu package)
Distribution: Ubuntu
Hardware Environment: Asus notebook A6Q00KM - a6km
Software Environment: AMD64
Problem Description:
- Event thru Acpi not working (Fn + whatever)
- multiple read on /proc/acpi/battery/BAT0/state hand system
- hald can't read event

For normal user: it's look like the system is very slow to start
(because hald don't start).

Steps to reproduce:
- each boot

Perhaps you need some other technicals informations.
Don't hesitate if you any questions.

Dominique
Comment 1 Dominique Derrier 2006-11-08 23:26:23 UTC 
Created attachment 9437 [details]
DSDT from /proc/acpi (BIOS 210)

DSDT from /proc/acpi (BIOS 210)
Comment 2 Zero3Cool 2007-09-29 02:48:15 UTC 
Hey. I have a similar setup, but are NOT having the same problems as you. My Fn keys are working fine, and boot seems normal. My setup:

Most recent kernel where this bug did not occur: 2.6.22-12-386
Distribution: Ubuntu Gutsy Beta (7.10)
Hardware Environment: Asus A6KM-Q025H Notebook
Software Environment: i386 (?)

If anyone needs me to test/do anything, just say so :).
Comment 3 Zero3Cool 2007-09-29 02:48:56 UTC 
(Oh, by the way - Newest BIOS from Asus named "300")
Comment 4 Fu Michael 2007-11-06 05:06:41 UTC 
Dominique, would you please retest on the latest kernel. You may need to do a BIOS upgrade too. According to comment# 2, it seems it just works fine..thanks.
Comment 5 Fu Michael 2007-11-06 22:34:38 UTC 
resolution in bug# 8919 may also helps you...
Comment 6 Dominique Derrier 2007-11-07 09:32:37 UTC 
The bug is not present with 2.6.20-15-generic and feisty on my amd x86_64.
Note You need to log in before you can comment on or make changes to this bug.