mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Andrei Gaponenko <andrei.gaponenko@cern.ch>
Cc: linux-kernel@vger.kernel.org, corentincj@iksaif.net,
	sziwan@users.sourceforge.net
Subject: Re: video breaks asus-laptop display switching
Date: Sat, 22 Dec 2007 15:53:17 +0800	[thread overview]
Message-ID: <1198309997.9550.2.camel@acpi-sony> (raw)
In-Reply-To: <Pine.LNX.4.64.0712211433030.3239@0-11-d8-ea-8d-5b.dhcp.lbl.gov>


On Sat, 2007-12-22 at 06:36 +0800, Andrei Gaponenko wrote:
> 
> Hi,
> 
> With 2.6.23 or newer (including 2.6.24-rc6) kernels, writing to the
> /sys/devices/platform/asus-laptop/display file does not do anything:
> 
> Cold boot to single user, then connect an external monitor
> 
> # cat  /sys/devices/platform/asus-laptop/display
> 1
> 
> OK, only the built in LCD is enabled. Try to enable
> the external monitor as well:
> 
> # echo 3 > /sys/devices/platform/asus-laptop/display
> 
> still no image on the external.
> 
> # cat  /sys/devices/platform/asus-laptop/display
> 1
> 
> Still "1", not the "3" we wrote. On the other hand if I boot with an
> external monitor attached, the "display" file always contains 3, even
> after writing 1 there, and there is image on both monitors.
> 
> In 2.6.22 I had to load asus-laptop by hand, but then display
> switching worked nicely. 
> 
> I've noticed that if I do
> 
> # rmmod video
> 
> display switching starts working again with the newer kernels.
> The "video" module was auto-loaded on my system in 2.6.22, but
> did not cause the conflict.
hmm, please "echo 1 > /proc/acpi/video/xxx/DOS" in 2.6.23 and see
if there is any difference.

Thansk,
Rui



  reply	other threads:[~2007-12-22  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 22:36 Andrei Gaponenko
2007-12-22  7:53 ` Zhang Rui [this message]
2007-12-22  8:21   ` Andrei Gaponenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1198309997.9550.2.camel@acpi-sony \
    --to=rui.zhang@intel.com \
    --cc=andrei.gaponenko@cern.ch \
    --cc=corentincj@iksaif.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sziwan@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®