Created attachment 33341 [details] Kernel dmesg output (each console switch triggers an invalid framebuffer id message) Kernel mode setting does not work for me any more on my laptop. The last working version is 2.6.32-rc6. 2.6.32-rc8 certainly does not work anymore. I've also tested with various later versions including 2.6.33-rc7. When using builtin kms, the kernel just hangs when loading. When using a module, the loading does not hang the computer, but blacks the laptop screen (it is completely off, including the backlight). After a while xdm kicks in and I get display. Switching to a virtual console gets back to the no-display situation. Also with a second screen attached (on dvi) there is no display.
Created attachment 33342 [details] Kernel config (2.6.33-rc7)
Do you have fbcon loaded? You need it for a console on the drm framebuffer otherwise you will get a blank display until X starts.
Created attachment 33343 [details] Xorg.0.log (from working kernel)
I'm not sure about whether fbcon is loaded when built as a module, but it is enabled in the kernel config. It still doesn't fix the case when built into the kernel, or the fact that it doesn't activate my DVI output properly (even running X) even though it sees it (as gdm is nicely asking for username/password on the dvi screen (presumably))
Can you attach your xorg log and dmesg from 2.6.33-rc7? Also to clarify: 2.6.32-rc8 and 2.6.33-rc7 - console is blank - LVDS works when X starts if no DVI monitor is connected - LVDS and DVI are both blank when X starts if both are connected 2.6.32-rc6 - working console and X on all outputs Does `modprobe fbcon` enable your console? Does DVI work if you connect it after you've started X on the LVDS?
I've tried it this morning again with .33-rc7 (without the DVI screen connected at all, previously I had the DVI screen connected), and instead of displaying X, it hung. While it did bring up the network etc, it did not actually give me ssh access. Also no X. Also to clarify, the LVDS (and DVI screen when connected) are completely off, not just blank. As I could not log in, modprobe fbcon was not possible, also I did not get X.
I've just tried things again, now not relying on module autoloading by udev. I've explicitly loaded fbcon (which worked, but did not change the screen). Then I've ran "modprobe radeon" remotely, which resulted in turning of the screen and first for a long time locking the ssh connection. After a long time (a couple of minutes) the console prompt appears, and the ssh connection is usable again. It might be that with the built-in support the same thing would happen, I just never happened to leave the computer alone that long to notice.
Some further info. While running X on the X server with the .33-rc7 kernel, when I move the mouse (with KWin compositing mode enabled) I get "horizontal snow" kind of noise. (btw. Dmesg doesn't say anything)
This may be a dup of bug 25506.
Indeed the bug seems to be related. Tomorrow I'll try with 33-rc8, as well as taking a look at reverting some of the commits mentioned in that bug.
*** This bug has been marked as a duplicate of bug 25506 ***
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.