Gentoo Archives: gentoo-user

From: Damien Levac <damien.levac@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Kernel 3.6: No external Monitor
Date: Tue, 20 Nov 2012 21:46:40
Message-Id: 50ABFA2C.8080401@gmail.com
In Reply to: Re: [gentoo-user] Kernel 3.6: No external Monitor by "Norman Rieß"
1 On 11/20/12 15:35, Norman Rieß wrote:
2 > Am 20.11.2012 20:08, schrieb Damien Levac:
3 >> On 11/20/12 13:33, Norman Rieß wrote:
4 >>> Am 20.11.2012 19:02, schrieb Florian Philipp:
5 >>>> Am 20.11.2012 14:52, schrieb Norman Rieß:
6 >>>>> Am 20.11.2012 13:51, schrieb Bruce Hill:
7 >>>>>> On Tue, Nov 20, 2012 at 08:44:08AM +0100, Norman Rieß wrote:
8 >>>>>>> Hello,
9 >>>>>>>
10 >>>>>>> i am using a Thinkpad X301 with a DVI Monitor connected to the mini
11 >>>>>>> displayport.
12 >>>>>>> That worked perfectly for years, but with Kernel 3.6 (and 3.7rc) the DVI
13 >>>>>>> Monitor stays black on boot and it is not visible in xrandr. As if it
14 >>>>>>> wasn't connected at all.
15 >>>>>>> Rebooting with 3.5 brings back the Display with full functionality.
16 >>>>>>>
17 >>>>>>> All i found about this was a Fedora bugreport stating the issue, but is
18 >>>>>>> unanswered for a month now.
19 >>>>>>>
20 >>>>>>> Does someone got an idea here or faced the same issue and solved it?
21 >>>>>>>
22 >>>>>>> Regards,
23 >>>>>>> Norman
24 >>>>>> Can you give us a link to:
25 >>>>>>
26 >>>>>> (1) the Fedora bug report
27 >>>>>> (2) your 3.5 kernel .config
28 >>>>>> (3) your 3.6 (and 3.7rc) kernel .config(s)
29 >>>>>>
30 >>>>> Yes.
31 >>>>> (1) https://bugzilla.redhat.com/show_bug.cgi?id=869824
32 >>>>>
33 >>>>> (2) http://smash-net.org/temp/config-3.5.4
34 >>>>> (3) http://smash-net.org/temp/config-3.6.6
35 >>>>> http://smash-net.org/temp/config-3.7.0-rc6
36 >>>>>
37 >>>>>
38 >>>>>
39 >>>> What does `xrandr --current` say? (from x11-apps/xrandr)
40 >>>>
41 >>>> Regards,
42 >>>> Florian Philipp
43 >>>>
44 >>> In what situation? 3.5 or 3.6 kernel?
45 >>>
46 >> In doubt, both. But I'm fairly sure he meant 3.6 since there are no
47 >> problem to solve in 3.5. :P
48 >>
49 >> Damien
50 >>
51 > Yeah, i was kinda irritated by that question, as i allready said, that
52 > xrandr does not show the display.
53 > 3.5 activates the display during kernel loading, on 3.6 it stays shut
54 > off during the whole boot process.
55 >
56 >
57 > 3.6:
58 > xrandr --current
59 > Screen 0: minimum 320 x 200, current 1440 x 900, maximum 32767 x 32767
60 > LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis)
61 > 287mm x 180mm
62 > 1440x900 60.0*+ 50.0
63 > 1024x768 60.0
64 > 800x600 60.3 56.2
65 > 640x480 59.9
66 > VGA1 disconnected (normal left inverted right x axis y axis)
67 > HDMI1 disconnected (normal left inverted right x axis y axis)
68 > DP1 disconnected (normal left inverted right x axis y axis)
69 > DP2 disconnected (normal left inverted right x axis y axis)
70 >
71 > ---------------------------------------------
72 > 3.5 both screens mirrored:
73 > xrandr --current
74 > Screen 0: minimum 320 x 200, current 1440 x 900, maximum 32767 x 32767
75 > LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis)
76 > 287mm x 180mm
77 > 1440x900 60.0*+ 50.0
78 > 1024x768 60.0
79 > 800x600 60.3 56.2
80 > 640x480 59.9
81 > VGA1 disconnected (normal left inverted right x axis y axis)
82 > HDMI1 connected 1440x900+0+0 (normal left inverted right x axis y axis)
83 > 518mm x 324mm
84 > 1920x1200 60.0 +
85 > 1600x1200 60.0
86 > 1680x1050 59.9
87 > 1680x945 60.0
88 > 1400x1050 59.9
89 > 1600x900 60.0
90 > 1280x1024 60.0
91 > 1440x900 59.9*
92 > 1280x960 60.0
93 > 1366x768 60.0
94 > 1360x768 60.0
95 > 1280x800 59.9
96 > 1280x768 60.0
97 > 1024x768 60.0
98 > 1024x576 60.0
99 > 800x600 60.3 56.2
100 > 848x480 60.0
101 > 640x480 60.0
102 > DP1 disconnected (normal left inverted right x axis y axis)
103 > DP2 disconnected (normal left inverted right x axis y axis)
104 >
105 > ---------------------------------------------
106 > 3.5 in my dualscreen setup:
107 > xrandr --current
108 > Screen 0: minimum 320 x 200, current 3360 x 1200, maximum 32767 x 32767
109 > LVDS1 connected 1440x900+1920+0 (normal left inverted right x axis y
110 > axis) 287mm x 180mm
111 > 1440x900 60.0*+ 50.0
112 > 1024x768 60.0
113 > 800x600 60.3 56.2
114 > 640x480 59.9
115 > VGA1 disconnected (normal left inverted right x axis y axis)
116 > HDMI1 connected 1920x1200+0+0 (normal left inverted right x axis y axis)
117 > 518mm x 324mm
118 > 1920x1200 60.0*+
119 > 1600x1200 60.0
120 > 1680x1050 59.9
121 > 1680x945 60.0
122 > 1400x1050 59.9
123 > 1600x900 60.0
124 > 1280x1024 60.0
125 > 1440x900 59.9
126 > 1280x960 60.0
127 > 1366x768 60.0
128 > 1360x768 60.0
129 > 1280x800 59.9
130 > 1280x768 60.0
131 > 1024x768 60.0
132 > 1024x576 60.0
133 > 800x600 60.3 56.2
134 > 848x480 60.0
135 > 640x480 60.0
136 > DP1 disconnected (normal left inverted right x axis y axis)
137 > DP2 disconnected (normal left inverted right x axis y axis)
138 >
139 I know this is not really what you want to hear about, but you should
140 wait for the fix to solve itself. The reason I'm saying this is that
141 Intel programmers are really working hard on their graphics drivers with
142 Steam comming to Linux and this is probably just a bug in their drivers
143 to which we have no power.
144
145 I could also be wrong though but I learned to just back off and wait
146 when a new kernel version breaks something.
147
148 Damien