I believe this occurred because of a system upgrade..but I can't exactly pinpoint it from the pacman logs. It could have occurred when linux-firmware was upgraded, I am really unsure.
Basically, I am running kernel26 18.104.22.168 on ArchLinux, linux-firmware 20100807, and have tried xf86-video-nouvea-git (the AUR package) as of (now).
So..my computer boots up, vesa fb takes over initially, as usual. Then right when nouveau normally loads, my display(s) go into a power-off state. (amber light).
I can login (fyi, I boot straight to terminal and manually run startx) and call startx. KDE4 then starts up properly and I can use kwin effects perfectly as usual (like present windows) via xrender.
Also, what is weird, is my displays are clones of each other instead of being one whole virtual screen, like I have set in my xorg.conf (and have not changed).
For anything else, just ask..obviously I'm anxious to get this fixed, especially since college starts very soon ;-)
Attached is xorg.conf. more incoming.
Created attachment 38051 [details]
Created attachment 38052 [details]
Created attachment 38053 [details]
Okay, that is my xorg log, and dmesg log, and just for the hell of it, I also attached the xrandr verbose output.
Not sure if that is useful for you guys or not.
Created attachment 38054 [details]
oops, almost forgot my xorg.conf.
Okay, xrandr --output DVI-I-3 --right-of DVI-I-4
fixes my problem for now. But the real question that I am wondering, is why does the xorg.conf virtual screen stuff not work? Is it related? Or is it just something that changed in xorg, nouveau, and is now deprecated/non-functional?
Uhh..seems the "screen clone" issue was fixed after I re-labeled the DVI outputs in my xorg.conf. I didn't realize they were non-const...because they obviously changed.
So now it's kind of just the framebuffer issue...although that still seems errata ;-)
Also, when I am in the X virtual terminal, and switch to a non-...the display is frozen with the same image (stand-still) until I switch back.
try to boot with kernel option "fbcon=map:1"
if it will help enable CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY
(In reply to comment #7)
> try to boot with kernel option "fbcon=map:1"
> if it will help enable CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY
The first had no affect.
The second requires compiling my own kernel, no? Can't really do that at the moment
It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report.
In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one.
The Nouveau Team