No backlight at login, and broken Plymouth on Acer Aspire One D260 (acpi)

Bug #626456 reported by Kazade
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Debian
New
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

When booting an Acer Aspire One D260 with UNE 10.04 LTS (2.6.32) there are two problems during boot. Firstly, Plymouth displays the VESA text-style boot splash and then secondly, as soon as the GDM appears the backlight switches off for around 20 seconds (it eventually comes on allowing login).

Both of these symptoms disappear when acpi=off is added a kernel option at GRUB.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-24-generic 2.6.32-24.41
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alison 1313 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x58200000 irq 16'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,10250349,00100001'
   Controls : 14
   Simple ctrls : 8
Date: Sun Aug 29 21:10:33 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=03d5a1ee-7630-4efc-9e2a-6a4b35651196
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
MachineType: Acer AOD260
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=56d12af9-8a07-4df7-8ae7-0d5888ab18d9 ro quiet splash
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 04/28/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.01
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: AOD260
dmi.board.vendor: Acer
dmi.board.version: V1.01
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.01
dmi.modalias: dmi:bvnAcer:bvrV1.01:bd04/28/2010:svnAcer:pnAOD260:pvrV1.01:rvnAcer:rnAOD260:rvrV1.01:cvnAcer:ct10:cvrV1.01:
dmi.product.name: AOD260
dmi.product.version: V1.01
dmi.sys.vendor: Acer

Revision history for this message
Kazade (kazade) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Kazade,

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: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Kazade (kazade) wrote :

I've tested the latest mainline kernel (2.6.36) Plymouth is now displaying correctly, but I'm still left with no backlight at GDM for about 10-30 seconds.

tags: removed: needs-upstream-testing
Revision history for this message
Waluyo Adi Siswanto (was-wlk) wrote :

I have similar problem (Acer aspire one Happy) in installing Ubuntu Netbook 10.10:

https://answers.launchpad.net/ubuntu/+source/plymouth/+question/134338

Revision history for this message
Corey Kearney (snkiz-deactivatedaccount) wrote :

Also seeing this issue on a new install of Mavrick 10.10. what else needs to be done to confirm it?

Revision history for this message
Kazade (kazade) wrote :

Still happening with Maverick running the 2.6.38 mainline kernel

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.