Your message dated Fri, 02 Oct 2009 11:49:57 +0200 with message-id <4AC5CCC5.3090802@ens-lyon.org> and subject line Re: Bug#549300: 5 out of 6 video cards do not work (radeon, mach64, nv, sis, mga) has caused the Debian Bug report #549300, regarding 5 out of 6 video cards do not work (radeon, mach64, nv, sis, mga) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 549300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549300 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: 5 out of 6 video cards do not work (radeon, mach64, nv, sis, mga)
- From: Joe Rayhawk <jrayhawk@omgwallhack.org>
- Date: Fri, 2 Oct 2009 02:05:10 -0700
- Message-id: <[🔎] 20091002090510.GT19761@orchitis.omgwallhack.org>
Package: xserver-xorg Version: 1:7.4+4 Five out of six cards in my system aren't working properly. A similar setup (minus Matrox G400x4 and plus another TNT2) worked fine in 6.8 and 7.1. The configuration, system, and log information (because there's a lot of it) is here: http://www.omgwallhack.org/home/jrayhawk/xorgbugreport2/ Most of these problems have been present for over a year, though the problem with the AGP Radeon is less than a month old. Also new is the mercifully complete lack of kernel crashes when testing video problems. The Matrox G400x4 has always had framebuffer corruption problems, with or without the Matrox binary blob. Its behavior has not changed and should probably be disregarded for the purposes of this bug. If anyone wants more information or if I should refile this bug elsewhere, let me know. I am also willing to arrange root access and/or some sort of physical access (bringing them to the machine, or the machine to them) to trustworthy parties or folks in the Portland area.Attachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: Joe Rayhawk <jrayhawk@omgwallhack.org>, 549300-done@bugs.debian.org
- Subject: Re: Bug#549300: 5 out of 6 video cards do not work (radeon, mach64, nv, sis, mga)
- From: Brice Goglin <Brice.Goglin@ens-lyon.org>
- Date: Fri, 02 Oct 2009 11:49:57 +0200
- Message-id: <4AC5CCC5.3090802@ens-lyon.org>
- In-reply-to: <[🔎] 20091002090510.GT19761@orchitis.omgwallhack.org>
- References: <[🔎] 20091002090510.GT19761@orchitis.omgwallhack.org>
Joe Rayhawk wrote: > Package: xserver-xorg > Version: 1:7.4+4 > > Five out of six cards in my system aren't working properly. > A similar setup (minus Matrox G400x4 and plus another TNT2) worked fine > in 6.8 and 7.1. The configuration, system, and log information (because > there's a lot of it) is here: > > http://www.omgwallhack.org/home/jrayhawk/xorgbugreport2/ > > Most of these problems have been present for over a year, though the > problem with the AGP Radeon is less than a month old. Also new is the > mercifully complete lack of kernel crashes when testing video problems. > > The Matrox G400x4 has always had framebuffer corruption problems, with > or without the Matrox binary blob. Its behavior has not changed and > should probably be disregarded for the purposes of this bug. > > If anyone wants more information or if I should refile this bug > elsewhere, let me know. I am also willing to arrange root access and/or > some sort of physical access (bringing them to the machine, or the > machine to them) to trustworthy parties or folks in the Portland area. > Most of the crashes in your log are caused by a Xserver bug that's fixed in 1.6.4-2 Otherwise your bug is useless if you mix multiple problems and don't attach the files here (you website might not always work). I am closing this bug. Please report different ones with the right files attached. Just make sure you file the bug with reportbug and let it attach the right logs to the report. Brice
--- End Message ---