Bug 31366 - [drm][KMS][Regression] Screen shutdown during boot
Summary: [drm][KMS][Regression] Screen shutdown during boot
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: All Linux (All)
: medium major
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-03 15:22 UTC by Unbekandt Léo
Modified: 2010-11-04 12:03 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Dmesg of 2.6.36.x boot (383.96 KB, text/plain)
2010-11-03 15:22 UTC, Unbekandt Léo
no flags Details
Dmesg with debug of the 2.6.32.x kernel (163.19 KB, text/plain)
2010-11-03 15:32 UTC, Unbekandt Léo
no flags Details

Description Unbekandt Léo 2010-11-03 15:22:17 UTC
Created attachment 40026 [details]
Dmesg of 2.6.36.x boot

Graphic Card : Nvidia 9500M (Hybrid SLI : chipset of the Dell Studio XPS 13 composed by a nvidia 9400GM and a 9200GS) Under Linux, only the 9400 is detected and it always work fine.

I'm using nouveau on an Archlinux x86_64 GNU/linux system. I have had a great KMS for months, but since the 2.6.35.x kernel, I lost it.

Instead of my KMS, my screen shutdown, and switch on again when X is launching, and everything went nice, 2D,3D, dual screen etc.

I think it is a drm driver problem. Here is my dmesg with drm.debug=14 to have a maximum of information, but there isn't really an error.

I tried with Ubuntu 10.10 32/64bits live CDs, but the results are the same, however when I boot my "old" kernel 2.6.32.x, I still have my KMS of course.

When I type Ctrl+Alt+F1, my computer switch on the tty, I can login and use it blindly, but my screen show the last screen of my graphical environment.
Comment 1 Unbekandt Léo 2010-11-03 15:32:46 UTC
Created attachment 40028 [details]
Dmesg with debug of the 2.6.32.x kernel

Here is my other kernel dmesg with drm debug output.
Comment 2 Marcin Slusarz 2010-11-04 09:28:11 UTC
It's funny. On 2.6.32 kernel we detected both cards (NV98 and NVAC), but couldn't initialize NV98 because we couldn't find its VBIOS. On 2.6.36 we again detected both cards but this time we found _both_ VBIOSes. As NV98 was detected first it drives primary framebuffer (fb0). 

So it's not a bug :).
Comment 3 Marcin Slusarz 2010-11-04 09:36:05 UTC
You can point fb0 at correct card by using fbcon=map: boot option.
See http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/fb/fbcon.txt
Comment 4 Unbekandt Léo 2010-11-04 12:02:58 UTC
Thanks for all, it works nice with fbcon=map:1

I'm happy to see that it's not a bug, it's a feature !

Sincerely,

Leo


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.