From: "Norman Rieß" <norman@smash-net.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel 3.6: No external Monitor
Date: Tue, 20 Nov 2012 19:33:32 +0100 [thread overview]
Message-ID: <50ABCCFC.6060900@smash-net.org> (raw)
In-Reply-To: <50ABC5BB.7030708@binarywings.net>
Am 20.11.2012 19:02, schrieb Florian Philipp:
> Am 20.11.2012 14:52, schrieb Norman Rieß:
>> Am 20.11.2012 13:51, schrieb Bruce Hill:
>>> On Tue, Nov 20, 2012 at 08:44:08AM +0100, Norman Rieß wrote:
>>>> Hello,
>>>>
>>>> i am using a Thinkpad X301 with a DVI Monitor connected to the mini
>>>> displayport.
>>>> That worked perfectly for years, but with Kernel 3.6 (and 3.7rc) the DVI
>>>> Monitor stays black on boot and it is not visible in xrandr. As if it
>>>> wasn't connected at all.
>>>> Rebooting with 3.5 brings back the Display with full functionality.
>>>>
>>>> All i found about this was a Fedora bugreport stating the issue, but is
>>>> unanswered for a month now.
>>>>
>>>> Does someone got an idea here or faced the same issue and solved it?
>>>>
>>>> Regards,
>>>> Norman
>>>
>>> Can you give us a link to:
>>>
>>> (1) the Fedora bug report
>>> (2) your 3.5 kernel .config
>>> (3) your 3.6 (and 3.7rc) kernel .config(s)
>>>
>>
>> Yes.
>> (1) https://bugzilla.redhat.com/show_bug.cgi?id=869824
>>
>> (2) http://smash-net.org/temp/config-3.5.4
>> (3) http://smash-net.org/temp/config-3.6.6
>> http://smash-net.org/temp/config-3.7.0-rc6
>>
>>
>>
>
> What does `xrandr --current` say? (from x11-apps/xrandr)
>
> Regards,
> Florian Philipp
>
In what situation? 3.5 or 3.6 kernel?
next prev parent reply other threads:[~2012-11-20 18:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 7:44 [gentoo-user] Kernel 3.6: No external Monitor Norman Rieß
2012-11-20 12:51 ` Bruce Hill
2012-11-20 13:52 ` Norman Rieß
2012-11-20 18:02 ` Florian Philipp
2012-11-20 18:33 ` Norman Rieß [this message]
2012-11-20 19:08 ` Damien Levac
2012-11-20 20:35 ` Norman Rieß
2012-11-20 21:46 ` Damien Levac
2012-11-20 22:24 ` Florian Philipp
2012-11-21 17:09 ` Norman Rieß
2012-11-21 17:45 ` Bruce Hill
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=50ABCCFC.6060900@smash-net.org \
--to=norman@smash-net.org \
--cc=gentoo-user@lists.gentoo.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