Windows. There are only two physical keys: - power-on button - "keyboard"-labeled button, which seems to do nothing hardware-related; it triggers an event caught up by acer_wmi. I think all it does is telling the OS: "hey, pull up the software virtual keyboard on the second display".
> > - there are a some unhandled WMI events logged from the acer-wmi > > module [3] when closing the lid, opening it, and most importantly, > > when the (main) screen is turned on or off by DPMS. > > > > I will look at your dsdt and log from acer-wmi then try to improve > acer-wmi. Thanks a lot! > > What do you think? I haven't really succeeded in nailing the source of > > the issue down, but here are a few possibilities I'm thinking of: > > > > - the driver is not aware it can drive two LVDS displays (not very > > likely, and it has worked once, see above) > > > > - there is some kind of switch that is able to turn the second screen > > on or off (I'm thinking of something like rfkill). If so, it looks > > like something non-standard and undocumented. This would explain > > the WMI events (see the last note above) > > > > What's the behavior of Windows? I meant an internal switch that would be controlled by GPIO or such. It doesn't seem very likely though... > > - buggy ACPI implementation. I tried to extract then recompile the > > DSDT [4], and iasl spews out 17 errors and 12 warnings. Also worth > > noticing is that line in dmesg: > > "pci0000:00: ACPI _OSC request failed (AE_ERROR), returned control mask: > > 0x1d" > > > > > > The Archlinux userland is: > > - libdrm 2.4.27 > > - xorg-server 1.11.2 > > - intel-dri 7.11.1 > > - xf86-video-intel 2.17.0 > > > > > > Please let me know if there are any other details I should provide. > > Regards, > > Baptiste > > > > Attachments: > > [1] dmesg-DSM-functions.log - drm errors when booting normally > > [2] dmesg-video-lvds2.log - drm errors when forcing LVDS2 on the cmdline > > [3] acer_wmi.log - WMI events that land in dmesg > > [4] dsdt - /sys/firmware/acpi/tables/DSDT > > Please also attached on dmidecode log. See [3] for dmidecode, I've also provided the dsdt [4] again. Here is also everything related to ACPI in dmesg [5]. > Thank's a lot! > Joey Lee Let me know if there's anything else I can provide, Baptiste [1] http://lists.freedesktop.org/archives/intel-gfx/2010-October/008339.html [2] https://bugs.freedesktop.org/show_bug.cgi?id=29821 [3] http://zorun.tonbnc.fr/lkml/dmidecode [4] http://zorun.tonbnc.fr/lkml/dsdt [5] http://zorn.tonbnc.fr/lkml/dmesg-acpi.log
