"acer-wmi: Unable to detect available WMID devices" on boot

Bug #560464 reported by Bill Hansen
196
This bug affects 39 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: plymouth

1) Ubuntu lucid (development branch) 10.04
2) plymouth:
  Installed: 0.8.1-4ubuntu1
  Candidate: 0.8.1-4ubuntu1
  Version table:
 *** 0.8.1-4ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status
3) My Acer AOD250 to boot without error warnings.
4) During the boot the screen flickers to black and pops up "acer-wmi: Unable to detect available WMID devices" as confirmed in the dmesg log. Happens on both Lucid upgrade & on liveUSB boot, but not in Karmic.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
CheckboxSubmission: 2b6c3b3ed5a39e3bddf9ba495e06c5d9
CheckboxSystem: ed86e29ffba809c116a39e33fa9fc45c
Date: Sun Apr 11 00:11:10 2010
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash

Revision history for this message
Bill Hansen (416inversed) wrote :
Revision history for this message
Bill Hansen (416inversed) wrote :

Added output of lspci -vvnn

Revision history for this message
Cody Russell (bratsche) wrote :

We're not using xsplash in Lucid, so this must be related to another package.

Changed in xsplash (Ubuntu):
status: New → Invalid
Revision history for this message
Bill Hansen (416inversed) wrote :

Sorry. I was just following the Ubuntu documentation for diagnosing packages:

"If you encounter a bug with the boot splash screen (typically an Ubuntu logo displayed during boot), the package is xsplash since 9.10 Karmic Koala and usplash in versions before that."

So, would it be Plymouth then?

Revision history for this message
Bill Hansen (416inversed) wrote :

Plymouth replaced xsplash in Lucid

affects: xsplash (Ubuntu) → plymouth (Ubuntu)
Changed in plymouth (Ubuntu):
status: Invalid → New
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

The error comes from the kernel; this should be triaged first for the kernel issue.

affects: plymouth (Ubuntu) → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Bill,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Bill Hansen (416inversed) wrote :

After installing linux-image-2.6.34-999-generic_2.6.34-999.201004281008_i386 I no longer get the "acer-wmi: Unable to detect available WMID devices" warning on boot, but I also no longer get any Plymouth splash screens either.

After grub, I just get a black screen that flickers the back-light a couple of times straight into the log-in screen.

Let me know if you need any more information.

tags: removed: needs-upstream-testing
Revision history for this message
Craig St. Clair (stclaircj) wrote :

I've installed the RC on my Acer TravelMate 290 and get this error upon boot up. I can workaround by booting the recovery mode and choosing the "low graphics" option. All else seems to be functional.

I'm not a computer programer or developer but would be willing to test or check anything for someone who is.

Revision history for this message
Christian Kunz (post-derkunz) wrote :

hi,

i've the same problem with my acer travelmate 420 after upgrade to lucid....

Revision history for this message
Markhor (markhor) wrote :

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.

Revision history for this message
Markhor (markhor) wrote :
Revision history for this message
Markhor (markhor) wrote :

Well, here is a quick fix. Add

blacklist acer-wmi

to /etc/modprobe.d/blacklist.conf.
No error messages occur after that. Adding AOD250 to the driver source as I suggested earlier is a more correct way though.

By the way, lsmod|grep acer-wmi gives nothing after the boot is finished, and everything like wifi works fine. This confirms my hypothesis.

Revision history for this message
colferma (colferma) wrote :

I've been having the same problem (Lucid 10.4, Acer Revo 3610) and Markhor's blacklist fix did the job, but bootup still takes a little while. It pauses at the black screen, just as it used to before it said the 'acer-wmi' error message, except now it just stays blank.

Revision history for this message
MT (micdhack) wrote :

i am having the same issue here...no splash, then just the terminal cursor, then the error message, screen flickers, ubuntu splash for 1-3 sec and then my desktop.
So even if we fix the error still we wont have a splash screen at the beggining.

Revision history for this message
Markhor (markhor) wrote :

To all those having troubles with boot splash:
1)follow workaround of the issue 540801: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/540801/comments/2. That is,
sudo su
echo FRAMEBUFFER=y > /etc/initramfs-tools/conf.d/splash
update-initramfs -u
exit

Now you will do get a boot splash, but it is buggy.

2)replace vga16fb with uvesafb. Tested here (Russian): http://habrahabr.ru/blogs/ubuntu/92637. That is,
Open /etc/default/grub, find GRUB_CMDLINE_LINUX_DEFAULT and change it (replace everywhere 1024x600 with your actual resolution):

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset video=uvesafb:mode_option=1024x600-24,mtrr=3,scroll=ywrap"

Find GRUB_GFXMODE, replace it:

GRUB_GFXMODE=1024x600

Open /etc/initramfs-tools/modules and add:

uvesafb mode_option=1024x600-24 mtrr=3 scroll=ywrap

Now install v86d and update grub:

sudo apt-get install v86d
sudo update-grub

Open /etc/modprobe.d/blacklist-framebuffer.conf and add:

blacklist vga16fb

Revision history for this message
dsaints (stcrabwise) wrote :

i do have same problem with acer 4736G.. is there an easy way around to fix this bug.. cuz im a new one with this OS.. please help.. i cud not even relate on the fix /solution stated above by others so please help..

Revision history for this message
dsaints (stcrabwise) wrote :

and one thing more.. as i open the file with gedit.. (Open /etc/default/grub, find GRUB_CMDLINE_LINUX_DEFAULT and change it ) i cud not even edit with this application.. so what application should i use to edit this line of code.. thanks..

Revision history for this message
Markhor (markhor) wrote :

Open with "gksu gedit". This means that you launch gedit with root rights. So, type

gksu gedit /etc/default/grub

Revision history for this message
Pablo Hinojosa (pablohn6) wrote :

The same problem in Acer Aspire One with Lucid Lynx.

Revision history for this message
Dokuro (hikage-no-dokuro) wrote :

Same thing on Aspire 5515. However the boot is very fast, and this screen just blinks. The boot process takes up to 20 secs. The Ubuntu "loading" screen shows and then the login.

Revision history for this message
kukide (kukide) wrote :

Hi, my problem looks like this bug. I have Acer Aspire One D250-0Bk. I want to install UNE 10.04 from liveUSB. Ubuntu can not boot from USB. I found somewhere advice to press Esc after screen goes to black. And its working. I install UNE without any error. After restart booting stops in black screen.
Boot is doing this: power > bios > screen with terminal cursor, HDD blinking > screen going to black and HDD stop blinking. Thats all.
For me what is working is pressing Esc at right time in startup.

When I boot with comand line its stop booting on line: "acer-wmi: Unable to detect available WMID devices".
I try Markhor solution, but when I want to close terminal after update grub, terminal writes Its still running some process... I closed with this message because i wait long time and nothing is happening.
After restart computer does this: power > bios > screen with terminal cursor > black screen > splash screen with ubuntu logo > HDD stop blinking and dot under logo doesnt change color. After switch-off with power buton and start again its startup without any problem.
But now still after first start going too black. Pressing Esc button after splash screen is working. If i dont press Esc then goes to black and after power button restart it starts again normally. Boot only works right after hard restart, and only every other time.

Revision history for this message
Markhor (markhor) wrote :

This isn't a usual failure, maybe a hardware problem... You should better start a thread somewhere at forums.ubuntu.com.

Reinstalling the OS from scratch is always a good idea.

As for the live USB, during BIOS screen, enter the boot devices menu (press F2) and make sure that boot from USB is higher than from HDD. I don't remember exactly about F2, maybe you have to enter the BIOS menu itself and change the boot device order there. BIOS screen displays what key you should press. After changing that I was able to install Lucid on my AOD250.

Revision history for this message
Onestar (thejournalofonestar) wrote :

I've received this same error on my Acer Aspire One as well. A clean install (just tried 15 minutes ago) doesn't remedy the problem.

I've also been having problems getting Ubuntu to recognize the SD card reader in my netbook. I'm not a programmer, but I wonder...could there be a correlation between this issue and my reader not working in Ubuntu? It works in every other OS I've tried.

Revision history for this message
Markhor (markhor) wrote :

There is no connection between this issue and SD card reader. Start a thread at forums.ubuntu.com, write there outputs from lsusb and lspci for a start and notify me. I will try to help you.

Revision history for this message
Markhor (markhor) wrote :

Hey! Will somebody mark this as "Confirmed"? There are a lot of people suffering from this.

Revision history for this message
tux-sven (sven.b) wrote :
Download full text (48.8 KiB)

Hi. I Am running Mint 9 Gnome.(=Ubuntu 10.04) Here is a debug log from this morning:

The startup failed twice. On third try it succeeded. When it stopped I hit some keys to see if it was alive. Finally I had to restart using the on/off switch. The computer is a "netbook" Acer Aspire One D250. OS is updated.

Jun 9 09:58:26 acer-mint kernel: [ 0.000000] MTRR default type: uncachable
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] MTRR fixed ranges enabled:
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 00000-9FFFF write-back
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] A0000-BFFFF uncachable
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] C0000-C7FFF write-protect
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] C8000-EFFFF uncachable
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] F0000-FFFFF write-protect
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] MTRR variable ranges enabled:
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 0 base 0FFF00000 mask 0FFF00000 write-protect
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 1 base 0FFFC0000 mask 0FFFE0000 uncachable
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 2 base 000000000 mask 0E0000000 write-back
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 3 base 020000000 mask 0E0000000 write-back
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 4 base 03F800000 mask 0FF800000 uncachable
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 5 base 03F700000 mask 0FFF00000 uncachable
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 6 disabled
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 7 base 000000000 mask 0FFFE0000 uncachable
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] e820 update range: 0000000000002000 - 0000000000006000 (usable) ==> (reserved)
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] initial memory mapped : 0 - 00c00000
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 0000000000 - 0000400000 page 4k
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 0000400000 - 0037400000 page 2M
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] 0037400000 - 00377fe000 page 4k
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] kernel direct mapping tables up to 377fe000 @ 7000-c000
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] On node 0 totalpages: 259568
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] free_area_init_node: node 0, pgdat c0798720, node_mem_map c1001000
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] DMA zone: 32 pages used for memmap
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] DMA zone: 0 pages reserved
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] DMA zone: 3963 pages, LIFO batch:0
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] Normal zone: 1744 pages used for memmap
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] Normal zone: 221486 pages, LIFO batch:31
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] HighMem zone: 255 pages used for memmap
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] HighMem zone: 32088 pages, LIFO batch:7
Jun 9 09:58:26 acer-mint kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000
Jun 9 09:...

Revision history for this message
tux-sven (sven.b) wrote :

Here is what the screen of my Acer Aspire One looked like during the missed start:

(process:187): GLib-WARNING **: getpwuid_r(): failed due to unknown user id (0)
*Setting sensor limits
*Starting ClamAV virus database updater freshclam
*Speech-dispatcher configured for user sessions
*Starting Common Unix Printing System: cupsd
*PulseAudio configured for per-user sessions
*Enabling additional executable binary formats binfmt-support
*Checking battery state...
^\

   ^[[B^[[B^[[C^[[A ###(Here I manually hit some Arrow keys)###
[ 480.536123] INFO: task plymouth:187 blocked for more than 120 seconds.
[ 480.536375] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 600.536121] INFO: task plymouth:187 blocked for more than 120 seconds.
[ 600.536372] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 720.536122] INFO: task plymouth:187 blocked for more than 120 seconds.
[ 720.536374] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 840.536094] INFO: task plymouth:187 blocked for more than 120 seconds.
[ 840.536226] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 960.536123] INFO: task plymouth:187 blocked for more than 120 seconds.
[ 960.536398] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Revision history for this message
Markhor (markhor) wrote :

This is a separate bug. I would recommend to ask such things on the forum first, as a lot of people have Mint and do not experience this issue. Stop making garbage from this thread! This is NOT an AOD250 linux support center.

Revision history for this message
kukide (kukide) wrote :

After last update is booting fast and normal.

Revision history for this message
tux-sven (sven.b) wrote :

Very sorry, posted in wrong Bug by mistake. (I had a couple of interesting bugs open on my desktop at the same time)
Please can someone with administrative rights move the two wrong-posted big comments away?
/tux-sven

Konrad (konradmb)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Magnus Stefanus (stefan-frey) wrote :

I have an Acer 5532 and get the same error message while booting (acer-wmi: Unable to detect available WMID devices). However booting is very fast, so it's just an aesthetic problem for me. Seeing the bootscreen during whole boot procedure would be nice.

Revision history for this message
sirwilliamblake (sirwilliamblake) wrote :

I'm experiencing the same bug on an ACER Aspire 5515.

Revision history for this message
Leo (leorolla) wrote :

Confirmed on Acer Aspire One D150. I will try post #16 indications when I have the time.

Revision history for this message
Coiby Xu (coiby) wrote :

same bug with aspire 4930, ubuntu 10.04

Revision history for this message
caspual (pearlfr) wrote :

Hello

A simple way to not have this bug, edit /etc/default/grub :

GRUB_CMDLINE_LINUX_DEFAULT="quiet"

then update-grub. No splash, but no bug.

Bye

Revision history for this message
Coiby Xu (coiby) wrote :

Hi, caspual!
Your suggestion does not work for me. I don't knowy why. "acer-wmi: Unable to detect available WMID devices" didn't apear. But it still splashes for more than 10s.

T70BYM (toby-marshall71)
Changed in linux (Ubuntu):
status: Confirmed → In Progress
status: In Progress → Confirmed
Revision history for this message
Richard Leckinger (caraka) wrote :

Confirmed on Acer Aspire 5741G running Lucid 10.4 64 bit. Same symptoms, but no significant delays with boot or other problems.

Revision history for this message
evristow (evristow) wrote :

Confirmed on Acer Aspire 5940g. As the above message no delays on boot.

This isn't a Plymouth, but actually a Kernel problem. I've read on some old mail-list posts that this problem already happened in 2008 with some Acer models, it was faulty code on 'wmi.c', as already noted Markhor (post #11).

Weirdly I only noticed this issue on 10.04, even though this same computer was using 9.10 without I noticing any problems.

Just for information I am running kernel 2.6.32-24-generic with no modifications what so ever.

Regards,
Eduardo

Revision history for this message
Bluefinger (bluefinger) wrote :

Confirmed this on an eMachines eM350, which is a rebranded Acer Aspire One 532 (as Acer owns eMachines now). Whilst boot is fast, it blinks out after loader and I go pretty much straight to the login screen. Used the newest kernel, 2.6.32-24-generic, and same issue still occurs. Using Ubuntu 10.04 Netbook edition as well.

Revision history for this message
naxcitl (tmeumann) wrote :

Confirmed this bug on Acer Aspire 4741G-434G50Mnkk.

In response to Markhor's post (#11): I wonder whether the laptops in question really have dummy interfaces (thus needing to be added to the blacklist), or if the interfaces are valid and the method WMID_set_capabilities() is the source of the trouble.

I know that on my Aspire the multi-gesture trackpad (detected as an ALPS trackpad by Windows) is detected as a generic mouse by Ubuntu. I can't help but suspect the failure to complete the acer-wmi device detection at startup is responsible for this and am not sure that adding the laptop to the blacklist is the final solution. I'd like to get more functionality out of this trackpad, if the problems are related.

Anyway I'm just thinking out loud here. I don't really have enough experience in Linux/kernel hacking/etc. (or time for that matter) to test this.

Cheers.

Revision history for this message
feixue2588 (guoshixiong-87) wrote :

Confirmed on Acer Aspire 4741G, can't boot for the above message.Running on Lucid 10.04.1 64 bit.
I've been used for several days normally,but this problem appears when i boot my lap-top this morning.

Revision history for this message
Kona-chan (kona-chan) wrote :

Confirmed on Acer Aspire 2930 with Lucid 10.04.1 64 bit. The system has been installed from scratch. Blacklisting acer-wmi in /etc/modprobe.d/blacklist.conf did not help, and the system still boots very slow, up to one minute at all. I remember when I used to have Karmic, it's boot speed was impressively fast, and I really am disappointed now.

Revision history for this message
Ari Asril (jasbutut) wrote :

Confirmed on Acer Aspire 4741Z with Maverick running 2.6.35-020635rc5 mainline kernel. Got this message a boot but still able boot to X.

Revision history for this message
Jamie Borg (borg-jamie) wrote :

Confirmed on Acer Aspire 4741G. Initial install was fine on default graphics drivers. But the Ubuntu recommended the installation of the NVIDIA drivers and that is when I get the WMID error and it locks out on the Boot Screen after 2 dots are lit. The system is totally unresponsive. Forced Power Down.

Ubuntu update has since applied latest kernel and I have downloaded and installed the latest NVIDIA drivers from NVIDIA. Same issue with lockout at the Boot Screen.

Can run the system on the default graphics in the meantime. Will try a couple of these workarounds.

Revision history for this message
Tommedema (tommedema) wrote :

Confirmed on Acer Aspire 7741ZG.

Fresh Ubuntu 10.10 install, all updates acquired. Message and flash screen appears on every boot, and when I go into console with Ctrl + Alt + F1 the screen's resolution is very low, might be a correlation here.

Very annoying bug, results in longer boot time as well.

Revision history for this message
funicorn (funicorn) wrote :

It's too sad, 14 months past, and I'm using Ubuntu 11.04 with linux kernel 2.6.39-0-generic, and I still meet this bug.

shame on those who say it's the kernel problem from upstream

shame on those who say blacklist acer-wmi can fix this bug

shame on those who say it's a hardware problem

shame on those who hesitates to marked the bug as confirmed and then left it here with no progress.

Revision history for this message
orngjce223 (orngjce223) wrote :

Bug also confirmed on Acer Aspire D255.

As suggested by #13 I have blacklisted said item in blacklist.conf.

funicorn, open source works on whoever wants to do the fixes. Since this isn't a major security problem (AFAIK) and doesn't do much of anything to functionality (also AFAIK), nobody's gotten around to it. (To be fair, most of the devs have left it alone because they're dancing around Unity and friends, but that's not really an objection, is it?)

The offending code is provided in #11 so, if it bothers you, you may fix it. The syntax seems simple enough. Just copy the if-then block several times and replace the model numbers with all the numbers that have been mentioned in this discussion, if I parse it correctly? I don't program very much.

Revision history for this message
wjamoore (aaron-moore-alsatis) wrote :

is anyone going to fix this. And I mean fix.. Not work around. And blacklisting is not fixing.

Also i am hacked off at the number of solved tags when someone makes a workaround. So you loose 3rd gear in your car.. SOLVED move from 2nd to 4th. NOOOO!!!!! Not solved just a work around.

I've had 10.04 on a laptop for 1 week and it's not so good. At first 15 sec boot (great) and since today now this stupid ACER message and boot has gone out to 30 seconds.. Add to that the 100% screen brightness and the wired network not working. I'm not enjoying myself. I use this for my business. Some action please!!!

Revision history for this message
Pierce March (stepnjump) wrote :

I get the same error message on a D255-1268 netbook FYI.

Revision history for this message
Pierce March (stepnjump) wrote :

Ubuntu 11.04 32bits

Revision history for this message
alekkova (alekkova) wrote :

I found this and it's work for me.

rfkill list all
sudo rmmod -f acer_wmi
sudo rfkill unblock all
sudo su
echo "blacklist acer_wmi" >> /etc/modprobe.d/blacklist.conf
exit

Revision history for this message
胡绍坤 (hushaokun-epeb) wrote :

I think this is a problem about driver for power maneger ,the acpi cannot work right , so the power reduce very fast ,the backlight is controled by acpi's function key ,actruely the function key is worked ,and send the right key event ,but no hardware respond,it is the evidence for the acpi driver is not right,my english is not good,many method cannot to be explanted out .log time not use the world language,hehe.why the acer's driver engineer care about this problem?when i starup into ubuntu ,the power maneget tell me i can use 2 hours ,but in windows7 i can work 6.5 hours. This problem is important about user's experience on ubuntu os.and this problem coming up since two years ago ,the ubuntuer and acer did not care about it ?

Revision history for this message
William Nagy (wnags) wrote :

acer 5552 ubuntu 10.04.4

Revision history for this message
martin suchanek (martin-suc) wrote :

Sony vaio on raring 13.04 3.8.0-20 generic kernel , 3.9.0 generic kernel.

Revision history for this message
penalvch (penalvch) wrote :

Bill Hansen, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.