I use Xubuntu 10.04 RTM on Aspire One AOD250 and get the same message. Here is what I think of this bug. According to the latest Ubuntu kernel source, "Unable to detect available WMID devices" error message is printk-ed at drivers/platform/x86/acer-wmi.c line 1293. Here is the complete code:
printk(ACER_INFO "Acer Laptop ACPI-WMI Extras\n"); if (dmi_check_system(acer_blacklist)) { printk(ACER_INFO "Blacklisted hardware detected - " "not loading\n"); return -ENODEV; } find_quirks(); /* * Detect which ACPI-WMI interface we're using. */ if (wmi_has_guid(AMW0_GUID1) && wmi_has_guid(WMID_GUID1)) interface = &AMW0_V2_interface; if (!wmi_has_guid(AMW0_GUID1) && wmi_has_guid(WMID_GUID1)) interface = &wmid_interface; if (wmi_has_guid(WMID_GUID2) && interface) { if (ACPI_FAILURE(WMID_set_capabilities())) { printk(ACER_ERR "Unable to detect available WMID " "devices\n"); return -ENODEV; } } else if (!wmi_has_guid(WMID_GUID2) && interface) { printk(ACER_ERR "No WMID device detection method found\n"); return -ENODEV; } What is interesting here is acer_blacklist. In detail, on line 229: /* The Aspire One has a dummy ACPI-WMI interface - disable it */ static struct dmi_system_id __devinitdata acer_blacklist[] = { { .ident = "Acer Aspire One (SSD)", .matches = { DMI_MATCH(DMI_SYS_VENDOR, "Acer"), DMI_MATCH(DMI_PRODUCT_NAME, "AOA110"), }, }, { .ident = "Acer Aspire One (HDD)", .matches = { DMI_MATCH(DMI_SYS_VENDOR, "Acer"), DMI_MATCH(DMI_PRODUCT_NAME, "AOA150"), }, }, {} }; So I guess we should just add AOD250 model to this list. I will try to do this myself, but it is the first time I compile a kernel module, don't rely on me. -- "acer-wmi: Unable to detect available WMID devices" on boot https://bugs.launchpad.net/bugs/560464 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs