You are not logged in.
Lately I got problems with my notebook and the monitor setup. It might be related to the forum topics Resolution broken - EDID issue? or EDID Checksum error on boot, but anything posted there did not resolved my issue.
Hardware: Dell Latitude E6400, E-Port Replicator PR01X/02X, Samsung SyncMaster 2243EW (1680x1050), dual-head setup (DP-1 and VGA-1 connected), nVidia Quadro NVS 160M, xf86-video-nouveau (0.0.16_git20120210-1), Arch running Gnome 3.4.1 with all updates (2012-05-05)
Symptom: The monitor connected to VGA-1 gets wrong resolution (1024x768) or stays blank, dmesg shows EDID checksum errors (see full logs in this post). Infrequently the boot into X/Gnome shows garbage after login and the system crashes. This (blank, garbage, crashes) also happens when trying to fix the resolution via
$ xrandr --output DP-1 --auto --primary --output VGA-1 --auto --right-of DP-1
When probing with xrandr, all resolutions are correctly found
$ xrandr --props
-> result
but sometimes the mouse pointer is gone after this command; also the VGA monitor goes or stays blank.
When using the Gnome System-Settings->Displays applet to adjust the monitors, it sometimes results into garbage screens or crashes.
Comments: First I suspected a hardware error (that's why I cannot give an exact date when these errors first occured), but I cross checked several setups. Switched screens (right/left), exchanged Port Replicator: no improvement. Moving KMS from early to late start: no improvement.
Fedora 16 Live USB (dual-head, several boots): no errors. Also I happened to have a similar setup at my office with Samsung SyncMaster 203B (1400x1050): no errors.
A downgrade to the previous nouveau version did not work, the system failed to boot into X/Gnome at all.
The problems might be related to the nouveau troubleshooting topic, but I am not sure.
Logs and configuration: Following a dmesg after boot and the relevant xorg.conf.d files.
Anyone else with similar issues, or any idea what might be the cause?
Cheers,
christoph
P.S.: Sorry for the long post, but it might serve as a reference when filing a bug.
Last edited by roepi (2012-06-20 09:29:05)
Offline
I have the same issues with Fedora 17 Beta (2012-05-05) LiveCD, same EDID checksum errors, same wrong resolution; see dmesg log. So I assume there is something with the new nouveau DRM.
I found an old bug in the nouveau-freedesktop bugtracker, but last activity is Nov 2011 and I am not sure if it is related.
What is the best to handle this issue, file a bug with Arch Linux, file a bug with nouveau-freedesktop? (Although it says on their website
If you are using packages from your distribution, send the bug reports to your distribution and not directly to us.
)
Help is appreciated, best regards,
christoph
Offline
I filed a bug at bugs.freedesktop.org->xorg->Driver/nouveau. Marcin Slusarz annotated that the bug is a regression probably fixed in the given commit.
So how would I know when the next nouveau driver update is scheduled for Arch Linux?
Best regards,
christoph
Offline
So how would I know when the next nouveau driver update is scheduled for Arch Linux?
Kernel 3.4 should be released and get into testing next week. You will just have to hope that this patch made it into 3.4, maybe it will even be merged into the next 3.3.x release.
Offline
Resolved with Kernel 3.4.2, that made it from testing to core this weekend. Thanks.
christoph
P.S.: I am not allowed to edit the subject of my first post to [SOLVED]. Not enough rights, or does someone else need to do this?
Offline
Interesting. I could prepend the [SOLVED] tag to another thread started by me, but I still cannot change it with this thread when editing the first post. Anyone has an idea about that?
Offline
Perhaps there is limited maximum number of characters in the subject
Offline
Argh, stupid me. That was the reason.
Thanks.
Offline