Re: [Flightgear-devel] Latest ATI related problem...
On Monday 29 December 2003 16:26, Simon Hollier wrote: On Sat, 2003-12-27 at 16:50, Lee Elliott wrote: Ta for the info. I got the 'feeling thet something changed' - I should have a look at the cvs logs but I'm not sure what to look for, or in which package. Live an' learn eh? ;) LeeE Lee, I was having lockups of all sorts with my 9200 on RH9 with Flightgear cvs. I'm now running XFree86 cvs(which is actually easy to build) and the updated DRM / DRI has fixed all such lockups. Actually, I've managed to hard lock my machine if I accidentally start two copies(fgrun double-click frenzy) of flightgear or any other 3d app for that matter. I never was able to tie the lockups to anything specific such as night/day, but I've never used the ATI drivers. There are still some rendering artifacts, like the flashing sky at night and the runway lights *flashing/blinking* (not sure how to describe it), but they have become tolerable. After dealing with hard locks, rendering artifacts are a blessing ;) Good luck! -Simon. -- Simon Hollier Computer Services Northeast Health District Is that on XFree86 V4.3? I'm still using 4.2 here as there aren't any official 4.3 packages for Debian yet. I might try the development stuff, if I can find it:) LeeE ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Latest ATI related problem...
On Tue, 2003-12-30 at 13:53, Lee Elliott wrote: Is that on XFree86 V4.3? I'm still using 4.2 here as there aren't any official 4.3 packages for Debian yet. I might try the development stuff, if I can find it:) LeeE Lee, I'm running XFree86 out of cvs : XFree86 Version 4.3.99.15 on top of the 2.6 kernel. The 4.3 release probably won't help you much, as that was what was locking up my machine. XFree86 just released the second release candidate for 4.4 and have provided binaries : ftp://ftp.xfree86.org/pub/XFree86/snapshots/4.3.99.902/binaries Looks like I need to update ;) The only thing that I noticed that changed(besides no more lockups) when I installed the cvs XFree was xpdf + ghostview. They have files in the X tree that I blew away. I just apt-get removed then apt-get installed them and it all works great. - Simon. -- Simon Hollier Computer Services Northeast Health District ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Latest ATI related problem...
Lee Elliott [EMAIL PROTECTED] wrote: I've been having a few problems, and not just with FG, since fitting a new ATI 9200 vid card but just recently I've found that I can't run FG at night-time at all. This wasn't originally the case when I first fitted the card - it's happened since, either as a result of system upgrades (Debian Unstable) or due to changes in FG or it's supporting packages i.e. plib or SimGear. If you feel comfortable with it then you might want to try binary snapshots of the DRI drivers for ATI Radeon: http://dri.sourceforge.net/snapshots/README.Debian Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Latest ATI related problem...
On Sat, 2003-12-27 at 16:50, Lee Elliott wrote: Ta for the info. I got the 'feeling thet something changed' - I should have a look at the cvs logs but I'm not sure what to look for, or in which package. Live an' learn eh? ;) LeeE Lee, I was having lockups of all sorts with my 9200 on RH9 with Flightgear cvs. I'm now running XFree86 cvs(which is actually easy to build) and the updated DRM / DRI has fixed all such lockups. Actually, I've managed to hard lock my machine if I accidentally start two copies(fgrun double-click frenzy) of flightgear or any other 3d app for that matter. I never was able to tie the lockups to anything specific such as night/day, but I've never used the ATI drivers. There are still some rendering artifacts, like the flashing sky at night and the runway lights *flashing/blinking* (not sure how to describe it), but they have become tolerable. After dealing with hard locks, rendering artifacts are a blessing ;) Good luck! -Simon. -- Simon Hollier Computer Services Northeast Health District ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Latest ATI related problem...
I had a similar problem about 1 month ago when I checked out a clean copy of FG and SimGear and compiled it. My system would keep locking up within 30 seconds whereas the 0.9.3 release runs just fine. My problem was that the nVidia drivers for the TNT2 are not so hot under Linux and I sorted the problem out by popping in a Ti4200 (same video driver and same system). A certain sequence of OpenGL calls would cause the drivers to go south with the TNT2. It was a video diver issue but it was definitely triggered by a change in SimGear/FlightGear/plib. Paul On Saturday, 27 December 2003 17:38, Lee Elliott wrote: I've been having a few problems, and not just with FG, since fitting a new ATI 9200 vid card but just recently I've found that I can't run FG at night-time at all. This wasn't originally the case when I first fitted the card - it's happened since, either as a result of system upgrades (Debian Unstable) or due to changes in FG or it's supporting packages i.e. plib or SimGear. I've tried both versions of the ATI drivers that I have - 3.2.5 3.2.8 - but the problem occurrs with both of them, but as I said, when I originally fitted the card this problem didn't happen - Heh! I have the screen grabs to prove it. Is anyone aware of any recent changes to FG, over the last month or so, that might be causing this? What happens now is that if I start FG with the sim time in darkness, FG runs for about 2-3 seconds before the display hangs. The mouse still works and I can ssh into the box from another system, where I can see X thrashing, but I'm not able to either restart X or even shutdown cleanly. Any attempt to do so results in a complete system lock-up. The mis-behaviour after the problem has occurred i.e. the inability to close X or cleanly shutdown, is definitely down to ATI's drivers but I'm wondering what's causing them to flip-out in the first place. The drivers were originally ok with FG and the problems with other packages don't appear to have changed, which rather points at changes in FG. LeeE ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Latest ATI related problem...
Ta for the info. I got the 'feeling thet something changed' - I should have a look at the cvs logs but I'm not sure what to look for, or in which package. Live an' learn eh? ;) LeeE On Saturday 27 December 2003 17:03, Paul Surgeon wrote: I had a similar problem about 1 month ago when I checked out a clean copy of FG and SimGear and compiled it. My system would keep locking up within 30 seconds whereas the 0.9.3 release runs just fine. My problem was that the nVidia drivers for the TNT2 are not so hot under Linux and I sorted the problem out by popping in a Ti4200 (same video driver and same system). A certain sequence of OpenGL calls would cause the drivers to go south with the TNT2. It was a video diver issue but it was definitely triggered by a change in SimGear/FlightGear/plib. Paul On Saturday, 27 December 2003 17:38, Lee Elliott wrote: I've been having a few problems, and not just with FG, since fitting a new ATI 9200 vid card but just recently I've found that I can't run FG at night-time at all. This wasn't originally the case when I first fitted the card - it's happened since, either as a result of system upgrades (Debian Unstable) or due to changes in FG or it's supporting packages i.e. plib or SimGear. I've tried both versions of the ATI drivers that I have - 3.2.5 3.2.8 - but the problem occurrs with both of them, but as I said, when I originally fitted the card this problem didn't happen - Heh! I have the screen grabs to prove it. Is anyone aware of any recent changes to FG, over the last month or so, that might be causing this? What happens now is that if I start FG with the sim time in darkness, FG runs for about 2-3 seconds before the display hangs. The mouse still works and I can ssh into the box from another system, where I can see X thrashing, but I'm not able to either restart X or even shutdown cleanly. Any attempt to do so results in a complete system lock-up. The mis-behaviour after the problem has occurred i.e. the inability to close X or cleanly shutdown, is definitely down to ATI's drivers but I'm wondering what's causing them to flip-out in the first place. The drivers were originally ok with FG and the problems with other packages don't appear to have changed, which rather points at changes in FG. LeeE ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
