Ubuntu
linux package

8086:0166 [Taichi 21] external screen is not working properly

Bug #1205694 reported by Joao Felipe Nicolaci Pimentel on 2013-07-27

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Medium	Unassigned

Bug Description

First of all, I'd like to say that both screen are recognized by xrandr: The internal as eDP1 and the external as DP1.
The external screen works under some circumstances, but without backlight.

If the computer is off, and I turn on with the lid closed, the external screen "works"
If the computer is turned on, on linux, and I restart, the external screen keeps "working".

If the computer is off and I turn on with the lid opened or the computer is on windows, using the external screen, and I restart to linux, I can't use the external screen: The image keeps "off". Although, the screen is recognized by xrandr, but no setting turns the screen on (not even xrandr --output DP1 --auto)

In the situations that the external screen works, the backlight has no effect on it:
When I adjust the backlight (either by the hotkeys, or by echo 50 > /sys/class/backlight/acpi_video0/brightness, or echo 3000 > /sys/class/backlight/intel_backlight/brightness), it just adjusts the internal screen
When I use the hotkey to turn off the screen, it just turn off the internal screen

Also, if I use xrandr to turn off the external screen, or suspend the computer, the external screen is turned off. When I try again to turn on, or resume it doesn't work.

I tried to boot with acpi_backlight=vendor, and again just the internal screen worked properly. The hotkey to change the backlight didn't work, but echo 3000 > /sys/class/backlight/intel_backlight/brightness worked
I tried to boot with video.use_bios_initial_backlight=0 and the backlight worked just for the internal screen again
I tried to boot with acpi_osi="!Windows 2012", the same thing

By running dmesg | grep 'ACPI: Video', I get:
[ 4.981826] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)

And lspci | grep VGA shows:
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)

I don't know if I should get 2 results in them, since I have two screens, but in DSDT, I just see one device with methods _DOS, _DOD, so I guess it is right. There is an if in the BCL, checking if it is Windows 8, but I believe acpi_osi="!Windows 2012", should "fix" it if that was the problem

I believe that solving the backlight problem when I'm able to turn on the screen might solve the screen not turning on with the lid open.

I tried to use the current Mainline kernel (3.11.0-999, or something like that), but after the boot the external screen was off and the internal was on, not showing anything but a black screen.

I followed the Kernel/Debugging/Backlight page and I'll submit all the files that it generated.

Thank you for your help!

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-26-generic 3.8.0-26.38
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: joao 2437 F.... pulseaudio
Date: Sat Jul 27 12:44:02 2013
HibernationDevice: RESUME=UUID=8c6201ab-045c-4bb7-b20d-c4650cca8821
InstallationDate: Installed on 2013-07-23 (4 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: ASUSTeK COMPUTER INC. TAICHI21
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic root=UUID=1b4e19b1-47cc-4068-a6d6-b73868b3c9d8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.8.0-26-generic N/A
linux-backports-modules-3.8.0-26-generic N/A
linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: TAICHI21.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: TAICHI21
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTAICHI21.208:bd01/08/2013:svnASUSTeKCOMPUTERINC.:pnTAICHI21:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTAICHI21:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: TAICHI21
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
---
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4118 F.... pulseaudio
ubuntu 14584 F.... pulseaudio
CasperVersion: 1.336
DistroRelease: Ubuntu 13.10
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130904)
MachineType: ASUSTeK COMPUTER INC. TAICHI21
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper persistent initrd=/casper/initrd.lz splash -- maybe-ubiquity
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
RelatedPackageVersions:
linux-restricted-modules-3.11.0-4-generic N/A
linux-backports-modules-3.11.0-4-generic N/A
linux-firmware 1.113
Tags: saucy
Uname: Linux 3.11.0-4-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/08/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: TAICHI21.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: TAICHI21
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTAICHI21.208:bd01/08/2013:svnASUSTeKCOMPUTERINC.:pnTAICHI21:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTAICHI21:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: TAICHI21
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

See original description

Tags:

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-07-27:

ls /sys/class/backlight > backlight Edit (28 bytes, text/plain)
AlsaInfo.txt Edit (26.4 KiB, text/plain; charset="utf-8")
BootDmesg.txt Edit (69.2 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (472 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (8.8 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (690 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.7 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.7 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (16.7 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (240 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (164.0 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (364.0 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (945.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-07-27:

bug_report.tar.gz Edit (241.3 KiB, application/x-tar)

I couldn't attach all the files. So they are in the attached file
The file contains:
backlight: ls /sys/class/backlight > backlight
acpi: grep -r . /proc/acpi > acpi
acpidump.txt: sudo acptidump -o acpidump.txt
DSDT.dat, SSDT1.dat ... SSDT12.dat: acpixtract acpidump.txt
DSDT.dsl: iasl -d DSDT.dat
fwts: sudo fwts > fwts
fwts_method > sudo fwts method > fwts_method
video: dmesg | grep 'ACPI: Video' > Video
dmidecode.log: sudo dmidecode
version: cat /proc/version > version
vendorbacklight: ls /sys/class/backlight > vendorbacklight
lslabacklight: ls -la /sys/class/backlight/intel_backlight/ > lslabacklight
lslaasusbacklight: ls -la /sys/class/backlight/asus-nb-wmi > lslaasusbacklight

Revision history for this message

Brad Figg (brad-figg) wrote on 2013-07-27: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

penalvch (penalvch) on 2013-07-28

tags:	added: bios-outdated-taichi21a needs-upstream-testing regression-potential
Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-07-28:

This BIOS isn't for my model.

This is for the TAICHI21A, mine is just TAICHI21. I'm in the most up to date: BIOS 208

The output is:
TAICHI21.208
01/08/2013

Thank you.

Revision history for this message

Johan Bernhardsson (smallone) wrote on 2013-09-02:

I can confirm this. I have a taichi with the latest bios update. The display can be configured but it does not light up.

Revision history for this message

penalvch (penalvch) wrote on 2013-09-02:

Johan Bernhardsson, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documention in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Revision history for this message

penalvch (penalvch) wrote on 2013-09-04:

Joao Felipe Nicolaci Pimentel, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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>

tags:

added: latest-bios-208
removed: bios-outdated-taichi21a

Artem Grunichev (gluk-7) on 2013-09-07

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2013-09-07:

Artem Grunichev, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: AlsaInfo.txt

#10

AlsaInfo.txt Edit (27.0 KiB, text/plain)

apport information

tags:	added: apport-collected saucy
description:	updated

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: BootDmesg.txt

#11

BootDmesg.txt Edit (63.0 KiB, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: CRDA.txt

#12

CRDA.txt Edit (257 bytes, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: CurrentDmesg.txt

#13

CurrentDmesg.txt Edit (1.3 KiB, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: IwConfig.txt

#14

IwConfig.txt Edit (475 bytes, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: Lspci.txt

#15

Lspci.txt Edit (8.8 KiB, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: Lsusb.txt

#16

Lsusb.txt Edit (611 bytes, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: ProcCpuinfo.txt

#17

ProcCpuinfo.txt Edit (3.7 KiB, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: ProcEnviron.txt

#18

ProcEnviron.txt Edit (103 bytes, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: ProcInterrupts.txt

#19

ProcInterrupts.txt Edit (2.2 KiB, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: ProcModules.txt

#20

ProcModules.txt Edit (4.4 KiB, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: PulseList.txt

#21

PulseList.txt Edit (18.6 KiB, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: RfKill.txt

#22

RfKill.txt Edit (240 bytes, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: UdevDb.txt

#23

UdevDb.txt Edit (157.5 KiB, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: UdevLog.txt

#24

UdevLog.txt Edit (333.1 KiB, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: WifiSyslog.txt

#25

WifiSyslog.txt Edit (109.9 KiB, text/plain)

apport information

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-09-08: Re: Taichi 21 external screen is not working properly (probably due backlight)

#26

The issue still exists in the development build of 4 days ago

Revision history for this message

penalvch (penalvch) wrote on 2013-09-08:

#27

Joao Felipe Nicolaci Pimentel, did this problem not occur in a release prior to Raring?

summary:

- Taichi 21 external screen is not working properly (probably due
- backlight)
+ 8086:0166 [Taichi 21] external screen is not working properly

Revision history for this message

Johan Bernhardsson (smallone) wrote on 2013-10-15:

#28

This is a bug concerning all linux distributions not only ubuntu.

Probably a driver problem. But as asus hasn't released any details on how the chip set works switching its hard to say whats going on.

I can confirm that this bug exists on all version of ubuntu from 12.04 and up (i have tested them all)

Setting the different backlight options only controls the light in the keyboard or the internal display but not the external display.

Perhaps it is some kind of display switch needed in the lines of optimus. I will investigate this later this week. Please keep this bug open.

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2013-10-20:

#29

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Incomplete

Revision history for this message

Joao Felipe Nicolaci Pimentel (joaofelipenp) wrote on 2013-10-20:

#30

The bug occurs in 12.04 (at least using the live usb) and still occurs in 13.10 (installed from scratch)

Revision history for this message

penalvch (penalvch) wrote on 2013-10-22:

#31

Joao Felipe Nicolaci Pimentel, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. 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.12-rc6

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.

tags:

added: precise

Revision history for this message

SOIMiMozO (soimimozo) wrote on 2013-12-11:

#32

Have the same ultrabook. Tested Ubuntu 13.04 with latest kernel 3.13.0-0311300rc3. The problem still persists.

Revision history for this message

penalvch (penalvch) wrote on 2013-12-11:

#33

SOIMiMozO, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Revision history for this message

Daiver (daiver) wrote on 2013-12-29:

#34

Taichi 31 have same problem.
Does anybody know what (ACPI, intel driver, asus driver) used to enable/disable backlight ?

Revision history for this message

penalvch (penalvch) wrote on 2013-12-29:

#36

Daiver, thank you for your comment. So your hardware may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux