I'm seeing a nouveau regression in 3.9.0-0.rc4.git0.1.fc19.x86_64 that was not in rc3.git0.3. With rc3.git0.3 the plymouth screen was slightly corrupted, but once gnome loaded, everything worked OK. With rc4.git0.1 I have a totally black screen.
So, new bug, but file it against kernel or xorg-x11-drv-nouveau?
Chris Murphy
On Mar 25, 2013, at 4:37 PM, Chris Murphy lists@colorremedies.com wrote:
I'm seeing a nouveau regression in 3.9.0-0.rc4.git0.1.fc19.x86_64 that was not in rc3.git0.3. With rc3.git0.3 the plymouth screen was slightly corrupted, but once gnome loaded, everything worked OK. With rc4.git0.1 I have a totally black screen.
So, new bug, but file it against kernel or xorg-x11-drv-nouveau?
I went ahead and put it under xorg-x11-drv-nouveau.
https://bugzilla.redhat.com/show_bug.cgi?id=927451
Chris Murphy
On Mon, 2013-03-25 at 16:37 -0600, Chris Murphy wrote:
I'm seeing a nouveau regression in 3.9.0-0.rc4.git0.1.fc19.x86_64 that was not in rc3.git0.3. With rc3.git0.3 the plymouth screen was slightly corrupted, but once gnome loaded, everything worked OK. With rc4.git0.1 I have a totally black screen.
So, new bug, but file it against kernel or xorg-x11-drv-nouveau?
xorg-x11-drv-nouveau. Always file graphics issues under the X driver component even when it's not technically correct, as it makes sure the right people see it.
So, new bug, but file it against kernel or xorg-x11-drv-nouveau?
If "kill -TERM <pid_of_/usr/bin/Xorg>" does restart the X server and results in a graphical display, then perhaps -nouveau might be better?
This report:
[NVA8][Nouveau] GPU lockup - switching to software fbcon https://bugzilla.redhat.com/show_bug.cgi?id=918732
sat in kernel for two weeks before being transferred to xorg-x11-drv-nouveau.
On Mar 25, 2013, at 5:26 PM, John Reiser jreiser@bitwagon.com wrote:
So, new bug, but file it against kernel or xorg-x11-drv-nouveau?
If "kill -TERM <pid_of_/usr/bin/Xorg>" does restart the X server and results in a graphical display, then perhaps -nouveau might be better?
X doesn't even start. dmesg reports inability to get necessary information from VBIOS.
Since it's an EFI UGA system, there is apparently no fallback. On EFI there isn't VGA, but there's either UGA or GOP. On my EFI GOP computer, I get fallback graphics when there are intel or radeon driver problems. But on the EFI UGA computer, X won't start, I'm relegated to text only. Not sure why.
Chris Murphy