From: Ivan Bulatovic <combuster@gmx.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: External display
Date: Fri, 14 Jan 2011 14:57:57 +0100 [thread overview]
Message-ID: <1295013477.7644.6.camel@localhost.localdomain> (raw)
In-Reply-To: <849307$b585ru@azsmga001.ch.intel.com>
On Fri, 2011-01-14 at 12:51 +0000, Chris Wilson wrote:
> On Fri, 14 Jan 2011 13:38:08 +0100, Christoph Lukas <christoph.lukas@gmx.net> wrote:
> > Hi,
> >
> > I am using a Dell E6410 notebook running Ubuntu. Most of the time I am
> > running this notebook in a docking station with closed lid and with an
> > external (DVI) monitor attached to the dock.
> >
> > Running different kernels I see different behaviour regarding the
> > display configuration after boot.
> >
> > Booting a 2.6.32 based kernel the internal display is turned off, the
> > external display is turned on and running at it's native resolution of
> > 1920x1200.
> > This is what I would expect.
>
> Once upon a time we trusted the lid status and reported the internal
> screen as disconnected when the lid was closed. We were beset by bugs
> reporting broken lid status and the LVDS not working. So we gave up.
> Usually between the BIOS and userspace responding to lid notification
> events, the LVDS is turned off when the lid is closed.
>
You can always boot with video=LVDS-1:d kernel parameter, that will
disable your LVDS connection and run your external monitor in native
resolution.
Only thing is, you have to remove that parameter every time you boot
your notebook without it being connected to docking station.
next prev parent reply other threads:[~2011-01-14 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 12:38 External display Christoph Lukas
2011-01-14 12:51 ` Chris Wilson
2011-01-14 13:57 ` Ivan Bulatovic [this message]
2011-01-14 17:58 ` Damnshock
2011-01-16 16:31 ` Damnshock
2011-01-16 17:14 ` Ivan Bulatovic
2011-01-16 17:27 ` Damnshock
2011-01-16 18:01 ` Ivan Bulatovic
2011-01-14 18:57 ` Christoph Lukas
2011-01-16 8:13 ` Christoph Lukas
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=1295013477.7644.6.camel@localhost.localdomain \
--to=combuster@gmx.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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.