From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42490] NUTMEG DP to VGA bridge not working
Date: Fri, 14 Sep 2012 07:59:36 +0000 [thread overview]
Message-ID: <bug-42490-502-Y2sD42idAf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-42490-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=42490
--- Comment #44 from lukenshiro@ngi.it 2012-09-14 07:59:36 UTC ---
Sorry, I've managed to resolve my first problem (screen blanking after boot for
about 30-40 seconds): it is not related to drm, but it depends on fbcon loaded
as a module (instead of it being compiled statically).
As explained in /usr/src/linux/Documentation/fb/fbcon.txt if fbcon is compiled
as a module (CONFIG_FRAMEBUFFER_CONSOLE=m) it can produce blanking and/or
garbage on display if it is not loaded immediately.
If "Framebuffer Console support" is compiled statically
(CONFIG_FRAMEBUFFER_CONSOLE=y) there is no blanking here.
"Works for me"
HTH.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-09-14 7:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42490-502@http.bugs.freedesktop.org/>
2011-11-02 21:51 ` [Bug 42490] NUTMEG DP to VGA bridge not working bugzilla-daemon
2011-11-03 2:15 ` bugzilla-daemon
2011-11-03 14:17 ` bugzilla-daemon
2011-11-04 2:15 ` bugzilla-daemon
2011-11-06 2:58 ` bugzilla-daemon
2012-03-12 13:43 ` bugzilla-daemon
2012-04-15 3:00 ` bugzilla-daemon
2012-04-16 4:38 ` bugzilla-daemon
2012-04-27 21:18 ` bugzilla-daemon
2012-04-28 7:39 ` bugzilla-daemon
2012-04-28 10:40 ` bugzilla-daemon
2012-04-28 10:41 ` bugzilla-daemon
2012-04-28 23:01 ` bugzilla-daemon
2012-04-29 8:38 ` bugzilla-daemon
2012-04-29 8:41 ` bugzilla-daemon
2012-04-29 9:14 ` bugzilla-daemon
2012-04-29 12:27 ` bugzilla-daemon
2012-04-29 12:30 ` bugzilla-daemon
2012-04-29 14:45 ` bugzilla-daemon
2012-04-29 15:14 ` bugzilla-daemon
2012-04-29 15:34 ` bugzilla-daemon
2012-04-30 9:54 ` bugzilla-daemon
2012-05-07 19:57 ` bugzilla-daemon
2012-05-08 6:54 ` bugzilla-daemon
2012-09-05 18:31 ` bugzilla-daemon
2012-09-05 18:34 ` bugzilla-daemon
2012-09-07 19:19 ` bugzilla-daemon
2012-09-07 19:35 ` bugzilla-daemon
2012-09-07 21:07 ` bugzilla-daemon
2012-09-07 21:08 ` bugzilla-daemon
2012-09-07 21:11 ` bugzilla-daemon
2012-09-07 21:28 ` bugzilla-daemon
2012-09-07 21:52 ` bugzilla-daemon
2012-09-08 8:59 ` bugzilla-daemon
2012-09-08 15:46 ` bugzilla-daemon
2012-09-08 18:15 ` bugzilla-daemon
2012-09-09 7:33 ` bugzilla-daemon
2012-09-13 12:21 ` bugzilla-daemon
2012-09-14 7:59 ` bugzilla-daemon [this message]
2012-09-30 15:46 ` bugzilla-daemon
2013-09-07 20:51 ` bugzilla-daemon
2019-11-19 8:23 ` bugzilla-daemon
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=bug-42490-502-Y2sD42idAf@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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