From: Oliver Seitz <info@vtnd.de>
To: intel-gfx@lists.freedesktop.org
Subject: LVDS output not working (anymore)
Date: Wed, 09 Feb 2011 08:52:20 +0100 [thread overview]
Message-ID: <4D5247B4.2020505@vtnd.de> (raw)
Hello list!
I'm using intel D945GSEJT boards, connected to industrial LVDS panels
without EDID or the like.
On debian 5.0 this did work when disabling kms (parameter "nomodeset").
When running X, LVDS could be enabled using xrandr.
Now, on debian 6.0, LVDS output does not show up in xrandr's output list
anymore. I understand that there have been some recent changes that are
not fully applied to debian 6.0. Is there a way to activate the LVDS output?
I wouldn't need X, a working framebuffer would be fine.
I've tried intelfb on 2.6.37 kernel, but it crashes (reboots) at once
when I execute "modprobe intelfb". No log messages are visible after the
reboot, I presume the messages aren't written to disk in time before the
reboot occurs.
Greets,
Kiste
next reply other threads:[~2011-02-09 7:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 7:52 Oliver Seitz [this message]
2011-02-09 9:16 ` LVDS output not working (anymore) Chris Wilson
2011-02-09 13:40 ` Oliver Seitz
2011-02-09 13:59 ` Chris Wilson
2011-02-09 15:01 ` [PATCH] drm, drm/i915/lvds: Honour video= parameter to override LVDS fixed mode Chris Wilson
2011-02-09 23:41 ` Dave Airlie
2011-03-28 21:33 ` Steven Newbury
2011-03-28 21:46 ` Steven Newbury
2011-03-29 6:18 ` Oliver Seitz
2011-03-29 6:49 ` Chris Wilson
2011-03-29 6:57 ` Keith Packard
2011-03-29 7:21 ` Mike Isely
2011-03-29 7:29 ` Chris Wilson
2011-03-29 7:49 ` Dave Airlie
2011-03-29 8:02 ` Dave Airlie
2011-03-29 10:55 ` Steven Newbury
2011-03-29 11:41 ` [Intel-gfx] " Steven Newbury
2011-03-29 11:50 ` Steven Newbury
2011-03-29 12:37 ` Steven Newbury
2011-03-29 14:52 ` Steven Newbury
2011-04-03 23:36 ` Steven Newbury
2011-03-29 10:50 ` Steven Newbury
2011-02-10 11:39 ` Oliver Seitz
2011-02-13 16:46 ` Oliver Seitz
2011-02-16 6:18 ` Oliver Seitz
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=4D5247B4.2020505@vtnd.de \
--to=info@vtnd.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox