linux-kernel - ACPI device for ASUS EEEPC 1101HA not added

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 1 Feb 2010 04:25:54 +0100
From:	Daniel Mack <daniel@...aq.de>
To:	linux-acpi@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, acpi4asus-user@...ts.sourceforge.net
Subject: ACPI device for ASUS EEEPC 1101HA not added

On my new 1101HA Eeepc, the special function keys do not work. This is
because the asus-laptop driver fails to match the ACPI device named
"ASUS010". However, acpidump tells me a device with that name does
actually exist - the (simplified) disassembly of the DSDT is below.

It looks like the gigantic parser state machine fails to add that
device for whatever reason. Any ideas how to fix that?


Thanks,
Daniel


/*
 * Intel ACPI Component Architecture
 * AML Disassembler version 20090521
 */
DefinitionBlock ("out/DSDT-0x3f660430-0.aml", "DSDT", 2, "A1359", "A1359000", 0x00000000)
{

    [...]

    Scope (_SB)
    {

        [...]

        Device (PCI0)
        {
            Name (_HID, EisaId ("PNP0A08"))
            Name (_ADR, Zero)

            [...]

            Device (SBRG)
            {

                [...]

                Scope (\_SB)
                {
                    Name (ATKP, Zero)
                    Device (ATKD)
                    {
                        Name (_HID, "ASUS010")
                        Name (_UID, 0x01010100)

                        [...]


The full version of the dump is here:

  http://caiaq.de/download/tmp/DSDT-0x3f660430-0.dsl

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/