[Asus Eee PC X101CH] Display brightness is always 0 and the screen is hardly readble after boot

Bug #1140614 reported by Nir Soffer
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

After boot, display brightness is always 0 and the screen is hardly readable.
cat /sys/class/backlight/acpi_video0/brightness -> 7
cat /sys/class/backlight/psb-bl/brightness -> 0

Workadound

To fix the system brightness, open the terminal application and run these commands:

sudo -s
[enter your password]
echo 80 > /sys/class/backlight/psb-bl/brightness
exit

For permentant fix edit /etc/rc.local as root, and add this line before the line "exit 0":

echo 80 > /sys/class/backlight/psb-bl/brightness

You may use any value from 0 to 100 instead of 80.
---
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nirs 2070 F.... pulseaudio
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=4cebec9a-7504-469c-8677-d25304edfd40
InstallationDate: Installed on 2012-06-08 (267 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: ASUSTeK COMPUTER INC. X101CH
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 psbfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-26-generic root=UUID=8a182610-1789-4b8d-b2e3-18f776104030 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-26.40-generic 3.5.7.6
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-26-generic N/A
 linux-backports-modules-3.5.0-26-generic N/A
 linux-firmware 1.95
Tags: quantal
Uname: Linux 3.5.0-26-generic i686
UpgradeStatus: Upgraded to quantal on 2013-02-22 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X101CH.0501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X101CH
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX101CH.0501:bd01/06/2012:svnASUSTeKCOMPUTERINC.:pnX101CH:pvrx.x:rvnASUSTeKCOMPUTERINC.:rnX101CH:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x:
dmi.product.name: X101CH
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Nir Soffer (nirsof) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected quantal
description: updated
Revision history for this message
Nir Soffer (nirsof) wrote : BootDmesg.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : CRDA.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : IwConfig.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : Lspci.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : Lsusb.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : ProcEnviron.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : ProcModules.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : PulseList.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : RfKill.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : UdevDb.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : UdevLog.txt

apport information

Revision history for this message
Nir Soffer (nirsof) wrote : WifiSyslog.txt

apport information

tags: added: workaround
Revision history for this message
Nir Soffer (nirsof) wrote : Re: Display brightness is always 0 and the screen is hardly readble after boot on Asus X101CH

Like https://bugs.launchpad.net/ubuntu/+source/linux/+bug/765438 - but I'not sure it is a duplicate.

Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Nir Soffer (nirsof) wrote : Re: Display brightness is always 0 and the screen is hardly readble after boot on Asus X101CH

Fixed if adding this to the boot parameters:

acpi_osi=Linux acpi_backlight=vendor

But in this mode the system freeze when you try to change the brightness using the hardware keys (Fn + F5, Fn + F6).

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Nir Soffer (nirsof) wrote :

Tested with kernel 3.9.0-rc1 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc1-raring/)

Partialy fixed - brightness is now 100 (maximum value) on reboot instead of 0.

Expected: brightness should be the same value set by the user.

Revision history for this message
penalvch (penalvch) wrote :

Nir Soffer, as per http://www.asus.com/Notebooks_Ultrabooks/Eee_PC_X101CH/#support_Download_8 an update is available for your BIOS (1203). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

tags: added: bios-outdated-1203 needs-upstream-testing regression-potential
removed: workaround
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: - Display brightness is always 0 and the screen is hardly readble after
- boot on Asus X101CH
+ [Asus Eee PC X101CH] Display brightness is always 0 and the screen is
+ hardly readble after boot
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.