[Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off [3.2-rc4+]

[Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off [3.2-rc4+]

[Baptiste Jonglez]

[-- Attachment #1: Type: text/plain, Size: 3739 bytes --]

Hi,

I've got a lot of troubles with a dual-LVDS Acer laptop (it doesn't
have a keyboard, but two displays with touchscreens)

The Intel GPU is integrated into the Core i5-480M CPU: it's a bit
older than Sandybridge, as it seems to be based on the Arrandale
micro-architecture.

In the BIOS, both displays work fine; but as soon as the kernel boots
up, the second display (i.e. the one where you usually find a
keyboard) is turned off. The main display works as expected.

xrandr reports two LVDS displays: LVDS1, which is connected, and
LVDS2, which is marked as "disconnected". No matter what I tried, I
can't bring that second display up.

During the boot, just after the drm is set up, the following message
shows up:

  [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions

(attached is the relevant part of dmesg [1])



I then tried booting with "video=LVDS-2:e". The same message shows up
while booting, with these two following:

  [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:4]
  fbcon_init: detected unhandled fb_set_par error, error code -22

(attached is the relevant part of dmesg [2])

With that kernel command line forcing LVDS2, the
"drm_crtc_helper_set_config" error shows up each time I switch tty;
additionally, X does not want to start anymore (spewing out the
aforementioned error multiple times before giving up)


I'm currently using the latest 3.2 kernel from linus' tree
(af968e29acd91ebeb4224e899202c46c93171ecd), but the behavior was
similar with a vanilla 3.1.2.


Other notes about this issue:

 - with an Ubuntu 2.6.35 kernel, the second display is on but
   flickering (with the picture distorted like an old analog TV...).
   The main display is working fine, as always.

 - with an Archlinux 2.6.37.5 kernel, the behavior is the same as with
   3.2, the main display is ok and the second one is off.

 - I did succeed, only once and out of pure luck, to get the second
   screen to work with the 3.1.2 kernel. I haven't been able to
   reproduce that... I had booted with "video=LVDS-2:e" and let the
   laptop running ; pressing a key a few hours later turned back
   *both* displays on (the main display had been turned off by DPMS,
   and the second, well, was off from the start, as always)
   While not very helpful, it shows that it's definitely possible.

 - 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.



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)

 - 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

[-- Attachment #2: dmesg-DSM-functions.log --]
[-- Type: text/plain, Size: 1723 bytes --]

[    2.294970] agpgart-intel 0000:00:00.0: Intel HD Graphics Chipset
[    2.295226] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
[    2.296300] agpgart-intel 0000:00:00.0: detected 131072K stolen memory
[    2.296518] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xa0000000
[    2.302498] [drm] Initialized drm 1.1.0 20060810
[    2.318612] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    2.318709] i915 0000:00:02.0: setting latency timer to 64
[    2.424180] mtrr: no more MTRRs available
[    2.424261] [drm] MTRR allocation failed.  Graphics performance may suffer.
[    2.425220] i915 0000:00:02.0: irq 40 for MSI/MSI-X
[    2.425225] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    2.425315] [drm] Driver supports precise vblank timestamp query.
[    2.425466] [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
[    2.425603] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    2.487520] fixme: max PWM is zero.
[    3.003403] Refined TSC clocksource calibration: 2660.000 MHz.
[    3.003492] Switching to clocksource tsc
[    3.296175] fbcon: inteldrmfb (fb0) is primary device
[    3.490453] Console: switching to colour frame buffer device 170x48
[    3.495380] fb0: inteldrmfb frame buffer device
[    3.495420] drm: registered panic notifier
[    3.515547] acpi device:03: registered as cooling_device0
[    3.515962] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5
[    3.516030] ACPI: Video Device [GFX0] (multi-head: yes  rom: yes  post: no)
[    3.516214] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

[-- Attachment #3: dmesg-video-lvds2.log --]
[-- Type: text/plain, Size: 2112 bytes --]

[    2.306530] agpgart-intel 0000:00:00.0: Intel HD Graphics Chipset
[    2.306734] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
[    2.307707] agpgart-intel 0000:00:00.0: detected 131072K stolen memory
[    2.307934] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xa0000000
[    2.311694] [drm] Initialized drm 1.1.0 20060810
[    2.318817] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    2.318908] i915 0000:00:02.0: setting latency timer to 64
[    2.362432] mtrr: no more MTRRs available
[    2.362510] [drm] MTRR allocation failed.  Graphics performance may suffer.
[    2.363227] i915 0000:00:02.0: irq 40 for MSI/MSI-X
[    2.363235] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    2.363319] [drm] Driver supports precise vblank timestamp query.
[    2.363451] [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
[    2.363573] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    2.425580] fixme: max PWM is zero.
[    3.010644] Refined TSC clocksource calibration: 2660.000 MHz.
[    3.010728] Switching to clocksource tsc
[    3.074370] [drm] forcing LVDS-2 connector ON
[    3.142131] fbcon: inteldrmfb (fb0) is primary device
[    3.380663] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:4]
[    3.380666] fbcon_init: detected unhandled fb_set_par error, error code -22
[    3.389011] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:4]
[    3.391194] Console: switching to colour frame buffer device 170x48
[    3.399524] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:4]
[    3.401833] fb0: inteldrmfb frame buffer device
[    3.401852] drm: registered panic notifier
[    3.420810] acpi device:03: registered as cooling_device0
[    3.421225] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5
[    3.421356] ACPI: Video Device [GFX0] (multi-head: yes  rom: yes  post: no)
[    3.421530] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

[-- Attachment #4: acer_wmi.log --]
[-- Type: text/plain, Size: 1144 bytes --]

[    6.863084] wmi: Mapper loaded
...
[    8.313598] acer_wmi: Acer Laptop ACPI-WMI Extras
[    8.315141] acer_wmi: Function bitmap for Communication Button: 0x801
[    8.315391] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[    8.318054] Linux media interface: v0.10
[    8.320963] acer_wmi: Brightness must be controlled by generic video driver
[    8.320974] iTCO_wdt: Found a HM55 TCO device (Version=2, TCOBASE=0x0460)
[    8.321080] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[    8.327597] input: Acer WMI hotkeys as /devices/virtual/input/input14
...
[  966.559929] acer_wmi: Unknown function number - 4 - 90   /* entering DPMS (main display off) */
...
[ 6149.355987] acer_wmi: Unknown function number - 4 - 90   /* exiting DPMS (main display backon) */
[ 6151.259037] acer_wmi: Unknown function number - 5 - 0    /* closing lid */
[ 6153.597345] acer_wmi: Unknown function number - 5 - 15   /* opening lid */
[ 6158.112272] acer_wmi: Unknown key number - 0x84          /* pressing the "keyboard" physical button */
[ 6158.387780] acer_wmi: Unknown function number - 2 - 132  /* releasing the "keyboard" physical button*/

[-- Attachment #5: dsdt --]
[-- Type: application/octet-stream, Size: 60508 bytes --]

Re: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off [3.2-rc4+]

[joeyli]

Add Cc. to platform-driver-x86 and linux-acpi

Hi Baptiste

於 日，2011-12-04 於 17:07 +0100，Baptiste Jonglez 提到：
> Hi,
> 
> I've got a lot of troubles with a dual-LVDS Acer laptop (it doesn't
> have a keyboard, but two displays with touchscreens)
> 
> The Intel GPU is integrated into the Core i5-480M CPU: it's a bit
> older than Sandybridge, as it seems to be based on the Arrandale
> micro-architecture.
> 
> In the BIOS, both displays work fine; but as soon as the kernel boots
> up, the second display (i.e. the one where you usually find a
> keyboard) is turned off. The main display works as expected.
> 
> xrandr reports two LVDS displays: LVDS1, which is connected, and
> LVDS2, which is marked as "disconnected". No matter what I tried, I
> can't bring that second display up.
> 
> During the boot, just after the drm is set up, the following message
> shows up:
> 
>   [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
> 
> (attached is the relevant part of dmesg [1])
> 
> 

Have no idea for this _DSM error, need help from drm and acpi experts.

> 
> I then tried booting with "video=LVDS-2:e". The same message shows up
> while booting, with these two following:
> 
>   [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:4]
>   fbcon_init: detected unhandled fb_set_par error, error code -22
> 
> (attached is the relevant part of dmesg [2])
> 
> With that kernel command line forcing LVDS2, the
> "drm_crtc_helper_set_config" error shows up each time I switch tty;
> additionally, X does not want to start anymore (spewing out the
> aforementioned error multiple times before giving up)
> 
> 
> I'm currently using the latest 3.2 kernel from linus' tree
> (af968e29acd91ebeb4224e899202c46c93171ecd), but the behavior was
> similar with a vanilla 3.1.2.
> 
> 
> Other notes about this issue:
> 
>  - with an Ubuntu 2.6.35 kernel, the second display is on but
>    flickering (with the picture distorted like an old analog TV...).
>    The main display is working fine, as always.
> 
>  - with an Archlinux 2.6.37.5 kernel, the behavior is the same as with
>    3.2, the main display is ok and the second one is off.
> 
>  - I did succeed, only once and out of pure luck, to get the second
>    screen to work with the 3.1.2 kernel. I haven't been able to
>    reproduce that... I had booted with "video=LVDS-2:e" and let the
>    laptop running ; pressing a key a few hours later turned back
>    *both* displays on (the main display had been turned off by DPMS,
>    and the second, well, was off from the start, as always)
>    While not very helpful, it shows that it's definitely possible.
> 

What does Windows platform's behavior? Does there have any physical key
that can turn on/off the second LVDS on Windows?

>  - 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.

> 
> 
> 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?

>  - 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.


Thank's a lot!
Joey Lee

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off [3.2-rc4+]

[joeyli]

Add Cc. to platform-driver-x86 and linux-acpi

Hi Baptiste

於 日，2011-12-04 於 17:07 +0100，Baptiste Jonglez 提到：
> Hi,
> 
> I've got a lot of troubles with a dual-LVDS Acer laptop (it doesn't
> have a keyboard, but two displays with touchscreens)
> 
> The Intel GPU is integrated into the Core i5-480M CPU: it's a bit
> older than Sandybridge, as it seems to be based on the Arrandale
> micro-architecture.
> 
> In the BIOS, both displays work fine; but as soon as the kernel boots
> up, the second display (i.e. the one where you usually find a
> keyboard) is turned off. The main display works as expected.
> 
> xrandr reports two LVDS displays: LVDS1, which is connected, and
> LVDS2, which is marked as "disconnected". No matter what I tried, I
> can't bring that second display up.
> 
> During the boot, just after the drm is set up, the following message
> shows up:
> 
>   [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
> 
> (attached is the relevant part of dmesg [1])
> 
> 

Have no idea for this _DSM error, need help from drm and acpi experts.

> 
> I then tried booting with "video=LVDS-2:e". The same message shows up
> while booting, with these two following:
> 
>   [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:4]
>   fbcon_init: detected unhandled fb_set_par error, error code -22
> 
> (attached is the relevant part of dmesg [2])
> 
> With that kernel command line forcing LVDS2, the
> "drm_crtc_helper_set_config" error shows up each time I switch tty;
> additionally, X does not want to start anymore (spewing out the
> aforementioned error multiple times before giving up)
> 
> 
> I'm currently using the latest 3.2 kernel from linus' tree
> (af968e29acd91ebeb4224e899202c46c93171ecd), but the behavior was
> similar with a vanilla 3.1.2.
> 
> 
> Other notes about this issue:
> 
>  - with an Ubuntu 2.6.35 kernel, the second display is on but
>    flickering (with the picture distorted like an old analog TV...).
>    The main display is working fine, as always.
> 
>  - with an Archlinux 2.6.37.5 kernel, the behavior is the same as with
>    3.2, the main display is ok and the second one is off.
> 
>  - I did succeed, only once and out of pure luck, to get the second
>    screen to work with the 3.1.2 kernel. I haven't been able to
>    reproduce that... I had booted with "video=LVDS-2:e" and let the
>    laptop running ; pressing a key a few hours later turned back
>    *both* displays on (the main display had been turned off by DPMS,
>    and the second, well, was off from the start, as always)
>    While not very helpful, it shows that it's definitely possible.
> 

What does Windows platform's behavior? Does there have any physical key
that can turn on/off the second LVDS on Windows?

>  - 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.

> 
> 
> 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?

>  - 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.


Thank's a lot!
Joey Lee

[BUG] i915/intel-acpi.c: failed to get supported _DSM functions (was: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off)

[Baptiste Jonglez]

CC-ing intel-gfx@lists.freedesktop.org (see below)

On Mon, Dec 05, 2011 at 11:00:41AM +0800, joeyli wrote:
> Add Cc. to platform-driver-x86 and linux-acpi
> 
> Hi Baptiste
> 
> 於 日，2011-12-04 於 17:07 +0100，Baptiste Jonglez 提到：
> > Hi,
> > 
> > I've got a lot of troubles with a dual-LVDS Acer laptop (it doesn't
> > have a keyboard, but two displays with touchscreens)
> > 
> > The Intel GPU is integrated into the Core i5-480M CPU: it's a bit
> > older than Sandybridge, as it seems to be based on the Arrandale
> > micro-architecture.
> > 
> > In the BIOS, both displays work fine; but as soon as the kernel boots
> > up, the second display (i.e. the one where you usually find a
> > keyboard) is turned off. The main display works as expected.
> > 
> > xrandr reports two LVDS displays: LVDS1, which is connected, and
> > LVDS2, which is marked as "disconnected". No matter what I tried, I
> > can't bring that second display up.
> > 
> > During the boot, just after the drm is set up, the following message
> > shows up:
> > 
> >   [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
> > 
> > (attached is the relevant part of dmesg [1])
> > 
> > 
> 
> Have no idea for this _DSM error, need help from drm and acpi experts.

It definitely looks like an ACPI issue.
That function is defined in `drivers/gpu/drm/i915/intel_acpi.c'.
The whole file was added more than a year ago by commit 723bfd707a97
(see the relevant thread on intel-gfx@ [1]) to "add _DSM support".
One of the first comment is about "Calpella", which is exactly the
platform of my laptop (as shown by lshw)

However, I honestly don't know what is wrong with that code...
Is there anything I can provide to sort things out?

> > I then tried booting with "video=LVDS-2:e". The same message shows up
> > while booting, with these two following:
> > 
> >   [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:4]
> >   fbcon_init: detected unhandled fb_set_par error, error code -22
> > 
> > (attached is the relevant part of dmesg [2])
> > 
> > With that kernel command line forcing LVDS2, the
> > "drm_crtc_helper_set_config" error shows up each time I switch tty;
> > additionally, X does not want to start anymore (spewing out the
> > aforementioned error multiple times before giving up)
> > 
> > 
> > I'm currently using the latest 3.2 kernel from linus' tree
> > (af968e29acd91ebeb4224e899202c46c93171ecd), but the behavior was
> > similar with a vanilla 3.1.2.
> > 
> > 
> > Other notes about this issue:
> > 
> >  - with an Ubuntu 2.6.35 kernel, the second display is on but
> >    flickering (with the picture distorted like an old analog TV...).
> >    The main display is working fine, as always.

I just bumped on bug report #29821 on freedesktop.org [2] which dates
the "flicker" bug around 2.6.35. I guess the ubuntu kernel doesn't
have the fix (and actually, the fix might be responsible for the lack
of output on the second display with later kernels.)

I'll try with an older kernel to see what it does.

> >  - with an Archlinux 2.6.37.5 kernel, the behavior is the same as with
> >    3.2, the main display is ok and the second one is off.
> > 
> >  - I did succeed, only once and out of pure luck, to get the second
> >    screen to work with the 3.1.2 kernel. I haven't been able to
> >    reproduce that... I had booted with "video=LVDS-2:e" and let the
> >    laptop running ; pressing a key a few hours later turned back
> >    *both* displays on (the main display had been turned off by DPMS,
> >    and the second, well, was off from the start, as always)
> >    While not very helpful, it shows that it's definitely possible.
> > 
> 
> What does Windows platform's behavior? Does there have any physical key
> that can turn on/off the second LVDS on Windows?

Actually, the first thing I did was wiping Windows out :)
From what I've seen, both screens seem to work out-of-the-box on
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

[BUG] i915/intel-acpi.c: failed to get supported _DSM functions (was: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off)

[Baptiste Jonglez]

CC-ing intel-gfx@lists.freedesktop.org (see below)

On Mon, Dec 05, 2011 at 11:00:41AM +0800, joeyli wrote:
> Add Cc. to platform-driver-x86 and linux-acpi
> 
> Hi Baptiste
> 
> 於 日，2011-12-04 於 17:07 +0100，Baptiste Jonglez 提到：
> > Hi,
> > 
> > I've got a lot of troubles with a dual-LVDS Acer laptop (it doesn't
> > have a keyboard, but two displays with touchscreens)
> > 
> > The Intel GPU is integrated into the Core i5-480M CPU: it's a bit
> > older than Sandybridge, as it seems to be based on the Arrandale
> > micro-architecture.
> > 
> > In the BIOS, both displays work fine; but as soon as the kernel boots
> > up, the second display (i.e. the one where you usually find a
> > keyboard) is turned off. The main display works as expected.
> > 
> > xrandr reports two LVDS displays: LVDS1, which is connected, and
> > LVDS2, which is marked as "disconnected". No matter what I tried, I
> > can't bring that second display up.
> > 
> > During the boot, just after the drm is set up, the following message
> > shows up:
> > 
> >   [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
> > 
> > (attached is the relevant part of dmesg [1])
> > 
> > 
> 
> Have no idea for this _DSM error, need help from drm and acpi experts.

It definitely looks like an ACPI issue.
That function is defined in `drivers/gpu/drm/i915/intel_acpi.c'.
The whole file was added more than a year ago by commit 723bfd707a97
(see the relevant thread on intel-gfx@ [1]) to "add _DSM support".
One of the first comment is about "Calpella", which is exactly the
platform of my laptop (as shown by lshw)

However, I honestly don't know what is wrong with that code...
Is there anything I can provide to sort things out?

> > I then tried booting with "video=LVDS-2:e". The same message shows up
> > while booting, with these two following:
> > 
> >   [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:4]
> >   fbcon_init: detected unhandled fb_set_par error, error code -22
> > 
> > (attached is the relevant part of dmesg [2])
> > 
> > With that kernel command line forcing LVDS2, the
> > "drm_crtc_helper_set_config" error shows up each time I switch tty;
> > additionally, X does not want to start anymore (spewing out the
> > aforementioned error multiple times before giving up)
> > 
> > 
> > I'm currently using the latest 3.2 kernel from linus' tree
> > (af968e29acd91ebeb4224e899202c46c93171ecd), but the behavior was
> > similar with a vanilla 3.1.2.
> > 
> > 
> > Other notes about this issue:
> > 
> >  - with an Ubuntu 2.6.35 kernel, the second display is on but
> >    flickering (with the picture distorted like an old analog TV...).
> >    The main display is working fine, as always.

I just bumped on bug report #29821 on freedesktop.org [2] which dates
the "flicker" bug around 2.6.35. I guess the ubuntu kernel doesn't
have the fix (and actually, the fix might be responsible for the lack
of output on the second display with later kernels.)

I'll try with an older kernel to see what it does.

> >  - with an Archlinux 2.6.37.5 kernel, the behavior is the same as with
> >    3.2, the main display is ok and the second one is off.
> > 
> >  - I did succeed, only once and out of pure luck, to get the second
> >    screen to work with the 3.1.2 kernel. I haven't been able to
> >    reproduce that... I had booted with "video=LVDS-2:e" and let the
> >    laptop running ; pressing a key a few hours later turned back
> >    *both* displays on (the main display had been turned off by DPMS,
> >    and the second, well, was off from the start, as always)
> >    While not very helpful, it shows that it's definitely possible.
> > 
> 
> What does Windows platform's behavior? Does there have any physical key
> that can turn on/off the second LVDS on Windows?

Actually, the first thing I did was wiping Windows out :)
>From what I've seen, both screens seem to work out-of-the-box on
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

Re: [BUG] i915/intel-acpi.c: failed to get supported _DSM functions (was: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off)

[Matthew Garrett]

On Mon, Dec 05, 2011 at 09:56:47PM +0100, Baptiste Jonglez wrote:
> CC-ing intel-gfx@lists.freedesktop.org (see below)
> On Mon, Dec 05, 2011 at 11:00:41AM +0800, joeyli wrote:
> > >   [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
> > > 
> > > (attached is the relevant part of dmesg [1])
> > > 
> > > 
> > 
> > Have no idea for this _DSM error, need help from drm and acpi experts.
> 
> It definitely looks like an ACPI issue.
> That function is defined in `drivers/gpu/drm/i915/intel_acpi.c'.
> The whole file was added more than a year ago by commit 723bfd707a97
> (see the relevant thread on intel-gfx@ [1]) to "add _DSM support".
> One of the first comment is about "Calpella", which is exactly the
> platform of my laptop (as shown by lshw)

Ignore that - it's entirely harmless.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

Re: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off [3.2-rc4+]

[Baptiste Jonglez]

[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]

On Mon, Dec 05, 2011 at 11:00:41AM +0800, joeyli wrote:
> Add Cc. to platform-driver-x86 and linux-acpi
> 
> Hi Baptiste
> 
> 於 日，2011-12-04 於 17:07 +0100，Baptiste Jonglez 提到：
> > Hi,
> > 
> > I've got a lot of troubles with a dual-LVDS Acer laptop (it doesn't
> > have a keyboard, but two displays with touchscreens)
> > 
> > The Intel GPU is integrated into the Core i5-480M CPU: it's a bit
> > older than Sandybridge, as it seems to be based on the Arrandale
> > micro-architecture.
> > 
> > In the BIOS, both displays work fine; but as soon as the kernel boots
> > up, the second display (i.e. the one where you usually find a
> > keyboard) is turned off. The main display works as expected.
> > 
> > xrandr reports two LVDS displays: LVDS1, which is connected, and
> > LVDS2, which is marked as "disconnected". No matter what I tried, I
> > can't bring that second display up.
> > 
> > During the boot, just after the drm is set up, the following message
> > shows up:
> > 
> >   [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
> > 
> > (attached is the relevant part of dmesg [1])

The second screen works fine with the attached patch. It actually is
6 months old but seems to have been lost in the wild...

Thanks Benjamin!

There is still the issue of unhandled acer-wmi events, but it's far
less incapacitating. I wonder what's the best way to report events to
userspace, though (e.g. for the "keyboard" button, userspace might
want to know when it is pressed in order to display a virtual keyboard
or any other fancy stuff)

Joey, if you need more logs for acer-wmi, I'll be happy to provide.


Baptiste

[-- Attachment #2: iconia-patch-lvds-lkml --]
[-- Type: text/plain, Size: 2812 bytes --]

Original patch by Chris Wilson [1], here slightly adapted for the latest tree.

[1] https://bugs.freedesktop.org/attachment.cgi?id=49069


We were checking whether the supplied edid matched the connector it was
read from. We do this in case a DDC read returns an EDID for another
device on a multifunction or otherwise interesting card. However, we
failed to include LVDS as a digital device and so rejecting an otherwise
valid EDID.

Fixes the detection of the secondary SDVO LVDS panel on the Libretto
W105.

diff --git a/drivers/gpu/drm/i915/intel_sdvo.c b/drivers/gpu/drm/i915/intel_sdvo.c
index 3003fb2..ac322fb 100644
--- a/drivers/gpu/drm/i915/intel_sdvo.c
+++ b/drivers/gpu/drm/i915/intel_sdvo.c
@@ -50,6 +50,7 @@
 #define IS_TMDS(c)	(c->output_flag & SDVO_TMDS_MASK)
 #define IS_LVDS(c)	(c->output_flag & SDVO_LVDS_MASK)
 #define IS_TV_OR_LVDS(c) (c->output_flag & (SDVO_TV_MASK | SDVO_LVDS_MASK))
+#define IS_DIGITAL(c) (c->output_flag & (SDVO_TMDS_MASK | SDVO_LVDS_MASK))
 
 
 static const char *tv_format_names[] = {
@@ -1314,6 +1315,18 @@ intel_sdvo_tmds_sink_detect(struct drm_connector *connector)
 	return status;
 }
 
+static bool
+intel_sdvo_connector_matches_edid(struct intel_sdvo_connector *sdvo,
+				struct edid *edid)
+{
+	bool monitor_is_digital = !!(edid->input & DRM_EDID_INPUT_DIGITAL);
+	bool connector_is_digital = !!IS_DIGITAL(sdvo);
+
+	DRM_DEBUG_KMS("connector_is_digital? %d, monitor_is_digital? %d\n",
+			connector_is_digital, monitor_is_digital);
+	return connector_is_digital == monitor_is_digital;
+}
+
 static enum drm_connector_status
 intel_sdvo_detect(struct drm_connector *connector, bool force)
 {
@@ -1358,10 +1371,11 @@ intel_sdvo_detect(struct drm_connector *connector, bool force)
 		if (edid == NULL)
 			edid = intel_sdvo_get_analog_edid(connector);
 		if (edid != NULL) {
-			if (edid->input & DRM_EDID_INPUT_DIGITAL)
-				ret = connector_status_disconnected;
-			else
+			if (intel_sdvo_connector_matches_edid(intel_sdvo_connector,
+								edid))
 				ret = connector_status_connected;
+			else
+				ret = connector_status_disconnected;
 			connector->display_info.raw_edid = NULL;
 			kfree(edid);
 		} else
@@ -1402,11 +1416,8 @@ static void intel_sdvo_get_ddc_modes(struct drm_connector *connector)
 		edid = intel_sdvo_get_analog_edid(connector);
 
 	if (edid != NULL) {
-		struct intel_sdvo_connector *intel_sdvo_connector = to_intel_sdvo_connector(connector);
-		bool monitor_is_digital = !!(edid->input & DRM_EDID_INPUT_DIGITAL);
-		bool connector_is_digital = !!IS_TMDS(intel_sdvo_connector);
-
-		if (connector_is_digital == monitor_is_digital) {
+		if (intel_sdvo_connector_matches_edid(to_intel_sdvo_connector(connector),
+							edid)) {
 			drm_mode_connector_update_edid_property(connector, edid);
 			drm_add_edid_modes(connector, edid);
 		}

Re: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off [3.2-rc4+]

[Benjamin Tissoires]

Hi Baptiste,

On Tue, Dec 6, 2011 at 22:51, Baptiste Jonglez <baptiste@jonglez.org> wrote:
> On Mon, Dec 05, 2011 at 11:00:41AM +0800, joeyli wrote:
>> Add Cc. to platform-driver-x86 and linux-acpi
>>
>> Hi Baptiste
>>
>> 於 日，2011-12-04 於 17:07 +0100，Baptiste Jonglez 提到：
>> > Hi,
>> >
>> > I've got a lot of troubles with a dual-LVDS Acer laptop (it doesn't
>> > have a keyboard, but two displays with touchscreens)
>> >
>> > The Intel GPU is integrated into the Core i5-480M CPU: it's a bit
>> > older than Sandybridge, as it seems to be based on the Arrandale
>> > micro-architecture.
>> >
>> > In the BIOS, both displays work fine; but as soon as the kernel boots
>> > up, the second display (i.e. the one where you usually find a
>> > keyboard) is turned off. The main display works as expected.
>> >
>> > xrandr reports two LVDS displays: LVDS1, which is connected, and
>> > LVDS2, which is marked as "disconnected". No matter what I tried, I
>> > can't bring that second display up.
>> >
>> > During the boot, just after the drm is set up, the following message
>> > shows up:
>> >
>> >   [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
>> >
>> > (attached is the relevant part of dmesg [1])
>
> The second screen works fine with the attached patch. It actually is
> 6 months old but seems to have been lost in the wild...

You don't have the problem of the second backlight still off?
On our Iconia, we need to trigger a special DMI command to set it up
(SDSS, IIRC).

>
> Thanks Benjamin!

All the credits are from Ajax and somebody else on IRC I don't recall,
really sorry. Thanks to them.

Cheers,
Benjamin.

>
> There is still the issue of unhandled acer-wmi events, but it's far
> less incapacitating. I wonder what's the best way to report events to
> userspace, though (e.g. for the "keyboard" button, userspace might
> want to know when it is pressed in order to display a virtual keyboard
> or any other fancy stuff)
>
> Joey, if you need more logs for acer-wmi, I'll be happy to provide.
>
>
> Baptiste

Re: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off [3.2-rc4+]

[Baptiste Jonglez]

On Tue, Dec 06, 2011 at 11:12:26PM +0100, Benjamin Tissoires wrote:
> Hi Baptiste,

Hi,

> On Tue, Dec 6, 2011 at 22:51, Baptiste Jonglez <baptiste@jonglez.org> wrote:
> > The second screen works fine with the attached patch. It actually is
> > 6 months old but seems to have been lost in the wild...
> 
> You don't have the problem of the second backlight still off?
> On our Iconia, we need to trigger a special DMI command to set it up
> (SDSS, IIRC).

No, with the patch, it worked out-of-the-box.

I can even control the brightness in
`/sys/class/backlight/acpi_video0/brightness' (it affects both
displays at the same time though). But even at 0, it's still perfectly
readable.

Maybe this a bug that got fixed recently? I've actually tried the 3.1
kernel (and then the 3.2-rc4) because I noticed a lot of commits and
improvements in the i915 driver recently.

> > Thanks Benjamin!
> 
> All the credits are from Ajax and somebody else on IRC I don't recall,
> really sorry. Thanks to them.
> 
> Cheers,
> Benjamin.

Regards,
Baptiste

Re: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off [3.2-rc4+]

[Benjamin Tissoires]

Hi,

On Tue, Dec 6, 2011 at 23:31, Baptiste Jonglez <baptiste@jonglez.org> wrote:
> On Tue, Dec 06, 2011 at 11:12:26PM +0100, Benjamin Tissoires wrote:
>> Hi Baptiste,
>
> Hi,
>
>> On Tue, Dec 6, 2011 at 22:51, Baptiste Jonglez <baptiste@jonglez.org> wrote:
>> > The second screen works fine with the attached patch. It actually is
>> > 6 months old but seems to have been lost in the wild...
>>
>> You don't have the problem of the second backlight still off?
>> On our Iconia, we need to trigger a special DMI command to set it up
>> (SDSS, IIRC).
>
> No, with the patch, it worked out-of-the-box.

mmm, this is weird. We must not have the same bios or device version.
We need to explicitly set the LCD2 up.

>
> I can even control the brightness in
> `/sys/class/backlight/acpi_video0/brightness' (it affects both
> displays at the same time though). But even at 0, it's still perfectly
> readable.

Yes, the acpi can control both brightness. But WMI can control each
brightness. However, we are not sure this is what people want. So we
do not plan to introduce a second brightness control.

>
> Maybe this a bug that got fixed recently? I've actually tried the 3.1
> kernel (and then the 3.2-rc4) because I noticed a lot of commits and
> improvements in the i915 driver recently.

We doubled-checked on 3.2-rc4, and we still need our patch. This is
definitively a bios/hardware configuration problem.

Cheers,
Benjamin

>
>> > Thanks Benjamin!
>>
>> All the credits are from Ajax and somebody else on IRC I don't recall,
>> really sorry. Thanks to them.
>>
>> Cheers,
>> Benjamin.
>
> Regards,
> Baptiste

Re: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off [3.2-rc4+]

[Baptiste Jonglez]

On Thu, Dec 08, 2011 at 11:11:22AM +0100, Benjamin Tissoires wrote:
> Hi,
> 
> On Tue, Dec 6, 2011 at 23:31, Baptiste Jonglez <baptiste@jonglez.org> wrote:
> > On Tue, Dec 06, 2011 at 11:12:26PM +0100, Benjamin Tissoires wrote:
> >> Hi Baptiste,
> >
> > Hi,
> >
> >> On Tue, Dec 6, 2011 at 22:51, Baptiste Jonglez <baptiste@jonglez.org> wrote:
> >> > The second screen works fine with the attached patch. It actually is
> >> > 6 months old but seems to have been lost in the wild...
> >>
> >> You don't have the problem of the second backlight still off?
> >> On our Iconia, we need to trigger a special DMI command to set it up
> >> (SDSS, IIRC).
> >
> > No, with the patch, it worked out-of-the-box.
> 
> mmm, this is weird. We must not have the same bios or device version.
> We need to explicitly set the LCD2 up.

The version of our BIOS is 1.01, dated from 12/23/2010.


Do you think there's any chance these patches will make it to the 3.2
kernel? I guess you want to make sure your second patch works fine
before...

Baptiste