On Tue, 3 May 2005 22:31:05 -0400, Ampere wrote in message 
<[EMAIL PROTECTED]>:

> Thanks for all the help guys.  It seems the depth-rate setting was
> preventing  FlightGear to run.  After I have changed the depth from
> 24-bits to 16-bits,  FlightGear runs fine.  Unfortunately,
> enemy-territory slows down even more  under 16-bits (not that it is
> playable anyway).
> 
> As far as hardware acceleration goes, even though it is available, I
> really  don't think those 3D applications are using it.  glxgears is
> running at ~500  fps.  I once managed to get the same amount of fps
> with no direct rendering,  so... =/
> Also, the framerates of glxgears seem to be extremely dependent on CPU
> cycles.   I have seen it falls to 9 while the system is accessing
> something from the  harddrive.  I don't know whether that is normal
> though.

[EMAIL PROTECTED]:~/FG $ glxgears
2890 frames in 5.0 seconds = 578.000 FPS
3517 frames in 5.0 seconds = 703.400 FPS
3517 frames in 5.0 seconds = 703.400 FPS
3444 frames in 5.0 seconds = 688.800 FPS
3492 frames in 5.0 seconds = 698.400 FPS
3521 frames in 5.0 seconds = 704.200 FPS
3485 frames in 5.0 seconds = 697.000 FPS

[EMAIL PROTECTED]:~/FG $ cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 5
model           : 8
model name      : AMD-K6(tm) 3D processor
stepping        : 12
cpu MHz         : 451.898
cache size      : 64 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8 pge mmx pni syscall
3dnow k6_mtrr bogomips        : 888.83

[EMAIL PROTECTED]:~/FG $ free
             total       used       free     shared    buffers    
cached Mem:        383992     365496      18496          0       2608   
  38780 -/+ buffers/cache:     324108      59884
Swap:       787176     398396     388780
[EMAIL PROTECTED]:~/FG $ lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3]
(rev 04) 
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo
MVP3/Pro133x AGP] 
0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile
South] (rev 12) 
0000:00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 
0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 08) 
0000:00:07.3 Host bridge: VIA Technologies, Inc. VT82C596 Power
Management (rev 20) 
0000:00:08.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97]
(rev 06)
0000:00:09.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX
[Boomerang] 
0000:01:00.0 VGA compatible controller: ATI Technologies Inc
RV280 [Radeon 9200 PRO] (rev 01) 
0000:01:00.1 Display controller: ATI Technologies Inc: Unknown device
5940 (rev 01)  
[EMAIL PROTECTED]:~/FG $   

> One thing for sure is that glxgears is taking up CPU cycles.  Check: 
> http://www.students.yorku.ca/~ampere/cpuload.jpg
> Ignoring the first and last peak, the description for the CPU Load
> graph is:  Idle -> glxgears running -> idle
> 
> Anyway, The 'Failed to load module "GLcore" ' is still here, and so
> the search  to why continues. =/
> Would you mind sending me your xorg.conf, Arnt?

..I'm still on that old junk XFree86-4.3.0.dfsg.1-12.0.1, so you'll have
to make do with my trusty old /etc/X11/XF86Config-4, gzip'ed.

..be adviced it _is_ possible to cook your crt with my custom 
1600x1200 modeline, it's made for my badly cooked 20", now 
it looks like I have lost the red gun on it today.  ;o)

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...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.

Attachment: XF86Config-4.gz
Description: Binary data

_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to