Bug 13276 - setting primary bootdevice (bios) to external vga, kernel mode setting for internal lvds fails
Summary: setting primary bootdevice (bios) to external vga, kernel mode setting for in...
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-10 22:45 UTC by Florian Mickler
Modified: 2010-09-03 06:23 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.29, 2.6.30
Subsystem:
Regression: No
Bisected commit-id:


Attachments
my kernel config (15.23 KB, application/octet-stream)
2009-05-10 22:45 UTC, Florian Mickler
Details
dmesg (116.34 KB, text/plain)
2009-05-10 22:53 UTC, Florian Mickler
Details
X log (28.25 KB, text/plain)
2009-05-10 23:04 UTC, Florian Mickler
Details

Description Florian Mickler 2009-05-10 22:45:55 UTC
Created attachment 21296 [details]
my kernel config 

My Thinkpad R61 has an bios option to set the primary display to 'vga'.

old behaviour (non-kms): using this, the internal display (lvds) stays black, if vga(external) is connected and i see everything on the attached vga. (bios, grub, kernel)
sometimes later X starts and activates the lvds and i have one big desktop. all's well. 

but nowadays with kernel-mode-setting:

booting with kms enabled (config and dmesg attached) i get thing's displayed on my vga until the kernel sets the video modes. on my vga display all is well, but the lvds starts ''growing white''. 

starting X dosn't fix things, but the lvds is ''resetted'' and restarts to grow white. sometimes i see some residue of the (vga)framebuffer content at first until all is white.


i have one warning in my dmesg (see attached), but only after i start X. the display-distortion is independent of X.


note: setting the primary boot-device in the bios to 'internal display' everything works just fine, everything is displayed on the lvds, until the kernel starts setting the modes. from then on, i have nice cloned framebuffer console. X works also as it should. 


i have also attached the Xorg.0.log, maybe you can see something in there.
Comment 1 Florian Mickler 2009-05-10 22:53:18 UTC
Created attachment 21297 [details]
dmesg

dmesg from the bootup. allthewhile the lvds is ''growing white'' . 

perhaps the warning can give a clue? 

note that the last dmesg-entry is from me turning my Lvds back on with xrandr --auto, after setting it to --off. 

to no avail, it started from all black, growing white again.
Comment 2 Florian Mickler 2009-05-10 22:59:54 UTC
to describe the symptom ''growing white'' a little bit more: 
it seems as if there were some bits falling on the lvds-framebuffer, incrementing the color-values of the pixels  until  everything is white. the landing seems to be somehow gauss distributed i.e. the center gets white first. thus the impression of a white center, growing to the borders. 
 

it also seems to increment all color-components evenly, so there is no big color-festival, but a fade from black to white through the grayscale.
Comment 3 Florian Mickler 2009-05-10 23:02:17 UTC
 $ xrandr 
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
VGA1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 473mm x 296mm
   1680x1050      60.0*+
   1280x1024      75.0  
   1024x768       75.1     70.1     60.0  
   832x624        74.6  
   800x600        72.2     75.0     60.3     56.2  
   640x480        72.8     75.0     66.7     60.0  
   720x400        70.1  
LVDS1 connected (normal left inverted right x axis y axis)
   1400x1050      60.0 +   50.0  
   1024x768       60.0  
   800x600        60.3  
   640x480        60.0  
   0x0             0.0  
TV1 disconnected (normal left inverted right x axis y axis)
Comment 4 Florian Mickler 2009-05-10 23:04:49 UTC
Created attachment 21298 [details]
X log

don't know if this is interesting.
Comment 5 Florian Mickler 2009-06-12 21:10:01 UTC
i opened a bug for this at bugs.fd.org:

https://bugs.freedesktop.org/show_bug.cgi?id=22262
Comment 6 Gordon Jin 2009-09-17 03:31:12 UTC
Let's track at freedesktop (which has been fixed).

Note You need to log in before you can comment on or make changes to this bug.