On Tue, 01 Feb 2011 23:11:15 +0100, Ove wrote in message <4d488503.8000...@arcticnet.no>:
> Do you have any kind of evidence that any of this is actually > FlightGear's fault? ..none other than seing this (appear to) appear on upgrading FG to 2.0.0-2 (from 1.9.1.1 which was ok on the same bleeding edge radeon driver,) and seeing some (accidental?) improvement in FG-git and FG-2.0.0-3. ..I see none of this nonsensical camouflage pattern animation in any other program, that lead me to believe this is a FG bug. > If you are running bleeding-edge versions of the > open source DRI drivers (which it looks like you are), I think you > might want to contact the DRI developers first. Perhaps you have > installed mismatched versions of some modules, ..always possible, how do I check? I see radeonhd has DRI issues, I'm on radeon, not radeonhd, I never got around to check with that driver, requires a reboot to unset KMS AFAIUI, which won't happen until I have replaced the 3/4 dead bios battery. A bit scary having those boot aborts happen to your only link out. > for example - plus, if > there's a bug in the drivers, they'd probably like to know about it. ..reasonable suggestion, #611803, is why I also asked the Nvidia crowd to try reproduce it with the nouveau driver, my potential DRI bug would show up there too, if it's an e.g. DRI bug from e.g. re-used code from radeon or libdrm-radeon1. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
