All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francisco Jerez <currojerez@riseup.net>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Radeon 3650HD laptop LVDS lid open/closed detection problem
Date: Mon, 21 Jun 2010 16:53:55 +0200	[thread overview]
Message-ID: <87y6e8zbb0.fsf@riseup.net> (raw)
In-Reply-To: <20100621125159.GE2350@barney.localdomain> (Jerome Glisse's message of "Mon, 21 Jun 2010 14:51:59 +0200")


[-- Attachment #1.1.1: Type: text/plain, Size: 2871 bytes --]

Jerome Glisse <glisse@freedesktop.org> writes:

> On Mon, Jun 21, 2010 at 03:31:19PM +0300, Pasi Kärkkäinen wrote:
>> Hello,
>> 
>> After fixing the dvi/hdmi detection problem I now have another problem
>> with the HP EliteBook 8530p, which has Radeon 3650HD adapter.
>> 
>> Here's a summary of the environment:
>> 
>> 	- laptop connected to a docking station.
>> 	- external display in use, connected with DVI to the dock.
>> 	- laptop lid closed, so internal LVDS display is not used.
>> 
>> Now, when I start the laptop, I can see the BIOS and grub on the external DVI display.
>> All fine so far. I select the Fedora 13 kernel, and Linux starts. I see the Fedora
>> graphical boot on the external DVI display, just like it should be. GDM login prompt
>> appears on the external DVI display, still everything fine.
>> 
>> And then it goes wrong. After I login to X, the external display only shows the background
>> picture.. it turns out the desktop stuff has been started to the internal LVDS display,
>> which shouldn't be used at all since the laptop lid is closed!! 
>> 
>> When the laptop lid is closed, and external display is connected, I want to use only the external display..
>> 
>> Any ideas how to troubleshoot this one? 
>> 
>> -- Pasi
>> 
>
> It's better to open bug when you face issue rather than mail, as it's
> harder to track information in mail thread than in a bug. Your issue
> is not easily fixed because there is many laptop with broken acpi which
> report wrong lid status (some of them always report lid closed what ever
> is the lid status, other always report lid open, ... i am not expert on
> how broken this is but from what i have been told i should rather consider
> drinking than trying to look into it and then go to the drinking step).
>
> Bottom line is that lid detection is unreliable thus so far we ignore
> it silently. I think the plan is to monitor lid status change and if
> we detect change from either open to close or close to open then we
> can start assuming that acpi lid status is reliable and act accordingly.
>
In Nouveau we report connector_status_unknown for closed lids (On the
kernel side unknown outputs are left disabled unless there's nothing
else definitely connected: if lid detection doesn't work at all the
system will still be usable). This would solve your problem if we made
the X server set the first output known to be connected as RandR
primary.

In short, I see two different "bugs" here:
 * radeon reports connector_status_connected when the lid is closed.
 * the X server doesn't select a primary output among the definitely
   connected ones.

> Cheers,
> Jerome
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

[-- Attachment #1.2: Type: application/pgp-signature, Size: 229 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2010-06-21 14:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 12:31 Radeon 3650HD laptop LVDS lid open/closed detection problem Pasi Kärkkäinen
2010-06-21 12:51 ` Jerome Glisse
2010-06-21 14:53   ` Francisco Jerez [this message]
2010-06-21 15:12     ` Alex Deucher
2010-06-21 15:52       ` Francisco Jerez
2010-07-12 11:53       ` Pasi Kärkkäinen
2010-07-12 14:48         ` Alex Deucher
2010-07-12 16:59           ` Pasi Kärkkäinen
2010-07-12 17:37             ` Alex Deucher
2010-07-26 19:42               ` Pasi Kärkkäinen
2010-07-26 21:13                 ` Alex Deucher
2010-07-27  8:41                   ` Pasi Kärkkäinen
2010-09-19 11:18                     ` Pasi Kärkkäinen
2010-09-19 11:34                       ` Pasi Kärkkäinen
2010-09-19 12:25                         ` Pasi Kärkkäinen
2010-09-19 14:56                           ` Pasi Kärkkäinen
2010-09-20  3:56                             ` Alex Deucher
2010-09-20  5:53                               ` Pasi Kärkkäinen
2010-09-21  5:09                                 ` Alex Deucher
2010-09-21  8:35                                   ` Pasi Kärkkäinen
2010-06-21 18:05   ` Pasi Kärkkäinen

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=87y6e8zbb0.fsf@riseup.net \
    --to=currojerez@riseup.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=pasik@iki.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.