Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
[gentoo-user] Kernel 3.6: No external Monitor
7 views
Skip to first unread message
Norman Rieß
Nov 20, 2012, 4:10:02 AM11/20/12
to
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
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
Bruce Hill
Nov 20, 2012, 10:10:01 AM11/20/12
to
(1) the Fedora bug report
(2) your 3.5 kernel .config
(3) your 3.6 (and 3.7rc) kernel .config(s)
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
sup...@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
Norman Rieß
Nov 20, 2012, 10:10:02 AM11/20/12
to
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.
> 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)
>
(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
Norman Rieß
Nov 20, 2012, 1:40:02 PM11/20/12
to
Am 20.11.2012 19:02, schrieb Florian Philipp:
In what situation? 3.5 or 3.6 kernel?
> Am 20.11.2012 14:52, schrieb Norman Rie�:
>> Am 20.11.2012 13:51, schrieb Bruce Hill:
>> Am 20.11.2012 13:51, schrieb Bruce Hill:
Damien Levac
Nov 20, 2012, 2:20:02 PM11/20/12
to
On 11/20/12 13:33, Norman Rieß wrote:
> Am 20.11.2012 19:02, schrieb Florian Philipp:
> 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:
>>> Am 20.11.2012 13:51, schrieb Bruce Hill:
problem to solve in 3.5. :P
Damien
Norman Rieß
Nov 20, 2012, 3:40:02 PM11/20/12
to
xrandr does not show the display.
3.5 activates the display during kernel loading, on 3.6 it stays shut
off during the whole boot process.
3.6:
xrandr --current
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 32767 x 32767
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis)
287mm x 180mm
1440x900 60.0*+ 50.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
---------------------------------------------
3.5 both screens mirrored:
xrandr --current
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 32767 x 32767
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis)
287mm x 180mm
1440x900 60.0*+ 50.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1440x900+0+0 (normal left inverted right x axis y axis)
518mm x 324mm
1920x1200 60.0 +
1600x1200 60.0
1680x1050 59.9
1680x945 60.0
1400x1050 59.9
1600x900 60.0
1280x1024 60.0
1440x900 59.9*
1280x960 60.0
1366x768 60.0
1360x768 60.0
1280x800 59.9
1280x768 60.0
1024x768 60.0
1024x576 60.0
800x600 60.3 56.2
848x480 60.0
640x480 60.0
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
---------------------------------------------
3.5 in my dualscreen setup:
xrandr --current
Screen 0: minimum 320 x 200, current 3360 x 1200, maximum 32767 x 32767
LVDS1 connected 1440x900+1920+0 (normal left inverted right x axis y
axis) 287mm x 180mm
1440x900 60.0*+ 50.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1920x1200+0+0 (normal left inverted right x axis y axis)
518mm x 324mm
1920x1200 60.0*+
1600x1200 60.0
1680x1050 59.9
1680x945 60.0
1400x1050 59.9
1600x900 60.0
1280x1024 60.0
1440x900 59.9
1280x960 60.0
1366x768 60.0
1360x768 60.0
1280x800 59.9
1280x768 60.0
1024x768 60.0
1024x576 60.0
800x600 60.3 56.2
848x480 60.0
640x480 60.0
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
Damien Levac
Nov 20, 2012, 4:50:02 PM11/20/12
to
On 11/20/12 15:35, Norman Rie� wrote:
> Am 20.11.2012 20:08, schrieb Damien Levac:
> Am 20.11.2012 20:08, schrieb Damien Levac:
>> On 11/20/12 13:33, Norman Rie� wrote:
>>> Am 20.11.2012 19:02, schrieb Florian Philipp:
>>> 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:
>>>>> Am 20.11.2012 13:51, schrieb Bruce Hill:
wait for the fix to solve itself. The reason I'm saying this is that
Intel programmers are really working hard on their graphics drivers with
Steam comming to Linux and this is probably just a bug in their drivers
to which we have no power.
I could also be wrong though but I learned to just back off and wait
when a new kernel version breaks something.
Damien
Florian Philipp
Nov 20, 2012, 5:30:01 PM11/20/12
to
Am 20.11.2012 21:35, schrieb Norman Rieß:
> Am 20.11.2012 20:08, schrieb Damien Levac:
>> On 11/20/12 13:33, Norman Rieß wrote:
>>> 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.
[...]
> Am 20.11.2012 20:08, schrieb Damien Levac:
>> On 11/20/12 13:33, Norman Rieß wrote:
>>> 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.
>>>> What does `xrandr --current` say? (from x11-apps/xrandr)
>>>>
>>>>
>>> In what situation? 3.5 or 3.6 kernel?
>>>
>> In doubt, both. But I'm fairly sure he meant 3.6 since there are no
>> problem to solve in 3.5. :P
>>
>
>>>
>> In doubt, both. But I'm fairly sure he meant 3.6 since there are no
>> problem to solve in 3.5. :P
>>
>
> Yeah, i was kinda irritated by that question, as i allready said, that
> xrandr does not show the display.
[...]
> xrandr does not show the display.
Sorry, missed that part.
Can you try without KMS?
http://wiki.debian.org/KernelModesetting
Regards,
Florian Philipp
Norman Rieß
Nov 21, 2012, 12:20:02 PM11/21/12
to
Am 20.11.2012 23:24, schrieb Florian Philipp:
Regards,
Norman
> Am 20.11.2012 21:35, schrieb Norman Rie�:
>> Am 20.11.2012 20:08, schrieb Damien Levac:
>> Am 20.11.2012 20:08, schrieb Damien Levac:
>>> On 11/20/12 13:33, Norman Rie� wrote:
>>>> Am 20.11.2012 19:02, schrieb Florian Philipp:
>>>> 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:
>>>>>> 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.
> [...]
>>>>> What does `xrandr --current` say? (from x11-apps/xrandr)
>>>>>
>>>> In what situation? 3.5 or 3.6 kernel?
>>>>
>>> In doubt, both. But I'm fairly sure he meant 3.6 since there are no
>>> problem to solve in 3.5. :P
>>>
>>
>> Yeah, i was kinda irritated by that question, as i allready said, that
>> xrandr does not show the display.
> [...]
>
> Sorry, missed that part.
>
> Can you try without KMS?
> http://wiki.debian.org/KernelModesetting
>
> Regards,
> Florian Philipp
>
Setting nomodeset does not solve the problem.
>>>>>>>> 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.
> [...]
>>>>> What does `xrandr --current` say? (from x11-apps/xrandr)
>>>>>
>>>> In what situation? 3.5 or 3.6 kernel?
>>>>
>>> In doubt, both. But I'm fairly sure he meant 3.6 since there are no
>>> problem to solve in 3.5. :P
>>>
>>
>> Yeah, i was kinda irritated by that question, as i allready said, that
>> xrandr does not show the display.
> [...]
>
> Sorry, missed that part.
>
> Can you try without KMS?
> http://wiki.debian.org/KernelModesetting
>
> Regards,
> Florian Philipp
>
Regards,
Norman
Bruce Hill
Nov 21, 2012, 12:50:01 PM11/21/12
to
On Wed, Nov 21, 2012 at 06:09:47PM +0100, Norman Rie� wrote:
>
> Setting nomodeset does not solve the problem.
>
> Regards,
> Norman
Sorry I didn't have the time to reply ... RL is consuming me.
>
> Setting nomodeset does not solve the problem.
>
> Regards,
> Norman
You can search on the Linux Kernel Mailing List https://lkml.org/ to see if
this bug is there, also. If it is a kernel bug, it will get fixed; and it
would be best for you to stay with whatever 3.5 series kernel works for now.
Or better yet, since 3.5 is EOL, use a 3.4 series such as 3.4.19.
0 new messages