[gentoo-user] Re: Video card memory disabled?

2006-11-22 Thread James
Mick michaelkintzios at gmail.com writes:


 I've booted into a new kernel (2.6.18-gentoo-r2) and suddenly discovered more 
 info than I had previously noticed in lspci regarding my video card:
 ==
 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY 
 (prog-if 00 [VGA])
 Subsystem: Compaq Computer Corporation Evo N600c
 Flags: bus master, stepping, 66MHz, medium devsel, latency 66, IRQ 11
 Memory at 4800 (32-bit, prefetchable) [size=128M]
 I/O ports at 3000 [size=256]
 Memory at 4020 (32-bit, non-prefetchable) [size=64K]
 [virtual] Expansion ROM at 4022 [disabled] [size=128K]
 Capabilities: [58] AGP version 2.0
 Capabilities: [50] Power Management version 2
 ==


Hello Mick,

I have an ATI video card that says the same thing about the ROM:

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 [Mobility
FireGL 9000] (rev 01) (prog-if 00 [VGA])
Subsystem: CLEVO/KAPOK Computer Unknown device 0402
Flags: bus master, stepping, fast Back2Back, 66MHz, medium devsel,
latency 66, IRQ 11
Memory at f000 (32-bit, prefetchable) [size=128M]
I/O ports at 9000 [size=256]
Memory at ec10 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at ec12 [disabled] [size=128K]
Capabilities: [58] AGP version 2.0
Capabilities: [50] Power Management version 2


This is under a 2.6.17-gentoo-r8 kernel

I'm going to look at what you are saying under two different
kernels (2.6.17-gentoo-r8 and  2.6.18-gentoo-r8) to see
what I get.  I'd be curious as to how your problem is
resolved too, as it may help me get more 3D performance too.


James

-- 
gentoo-user@gentoo.org mailing list



[gentoo-user] Re: Video card memory disabled?

2006-11-22 Thread James
==
  $ glxgears
 libGL warning: 3D driver claims to not support visual 0x4b
 2446 frames in 5.0 seconds = 489.111 FPS
 2441 frames in 5.0 seconds = 488.094 FPS
 2448 frames in 5.0 seconds = 489.509 FPS
 2438 frames in 5.0 seconds = 487.576 FPS
 2445 frames in 5.0 seconds = 488.976 FPS
 2442 frames in 5.0 seconds = 488.238 FPS
 2439 frames in 5.0 seconds = 487.720 FPS
 ==


under 2.6.17-gentoo-r8 I get (glxgears):
6751 frames in 5.0 seconds = 1350.118 FPS
7174 frames in 5.0 seconds = 1434.668 FPS
6596 frames in 5.0 seconds = 1319.182 FPS
6946 frames in 5.0 seconds = 1389.107 FPS
6582 frames in 5.0 seconds = 1316.222 FPS
5700 frames in 5.0 seconds = 1139.907 FPS
7038 frames in 5.0 seconds = 1407.494 FPS
6879 frames in 5.0 seconds = 1375.700 FPS
6737 frames in 5.0 seconds = 1347.254 FPS
7072 frames in 5.0 seconds = 1414.338 FPS
7027 frames in 5.0 seconds = 1405.366 FPS

 ==
 $ glxinfo
 name of display: :0.0
 libGL warning: 3D driver claims to not support visual 0x4b
 display: :0  screen: 0
 direct rendering: Yes
 ==

under glxinfo (2.6.17-gentoo-r8):

name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
snip very long listing of info

 
 While you're looking at this I would appreciate if you could tell me why I am 
 getting this libGL warning (and how to fix it)?

 Finally, I am also getting this mtrr overlap at boot:
 ==
 mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
 mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
 mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
 mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
 mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
 agpgart: Found an AGP 2.0 compliant device at :00:00.0.
 agpgart: Putting AGP V2 device at :00:00.0 into 4x mode
 agpgart: Putting AGP V2 device at :01:00.0 into 4x mode
 [drm] Setting GART location based on new memory map
 [drm] writeback test succeeded in 1 usecs
 

under glxinfo (2.6.17-gentoo-r8)  greping dmesg for9 gl drm agp) I get:
[drm] Initialized drm 1.0.1 20051102
[drm] Initialized radeon 1.24.0 20060225 on minor 0
[drm] Setting GART location based on new memory map
[drm] Loading R200 Microcode
[drm] writeback test succeeded in 1 usecs

agpgart: Detected SiS 646 chipset
agpgart: AGP aperture is 64M @ 0xe800
agpgart: Found an AGP 2.0 compliant device at :00:00.0.
agpgart: Putting AGP V2 device at :00:00.0 into 1x mode
agpgart: Putting AGP V2 device at :01:00.0 into 1x mode

Does look suspicious

Now I'm off to test my new 2.6.18-gentoo-r2 kernel


James

-- 
gentoo-user@gentoo.org mailing list



[gentoo-user] Re: Video card memory disabled?

2006-11-22 Thread James
James wireless at tampabay.rr.com writes:

 
 ==
   $ glxgears
  libGL warning: 3D driver claims to not support visual 0x4b
  2446 frames in 5.0 seconds = 489.111 FPS
  2441 frames in 5.0 seconds = 488.094 FPS
  2448 frames in 5.0 seconds = 489.509 FPS
  2438 frames in 5.0 seconds = 487.576 FPS
  2445 frames in 5.0 seconds = 488.976 FPS
  2442 frames in 5.0 seconds = 488.238 FPS
  2439 frames in 5.0 seconds = 487.720 FPS
  ==
 
 under 2.6.17-gentoo-r8 I get (glxgears):
 6751 frames in 5.0 seconds = 1350.118 FPS
 7174 frames in 5.0 seconds = 1434.668 FPS
 6596 frames in 5.0 seconds = 1319.182 FPS
 6946 frames in 5.0 seconds = 1389.107 FPS
 6582 frames in 5.0 seconds = 1316.222 FPS
 5700 frames in 5.0 seconds = 1139.907 FPS
 7038 frames in 5.0 seconds = 1407.494 FPS
 6879 frames in 5.0 seconds = 1375.700 FPS
 6737 frames in 5.0 seconds = 1347.254 FPS
 7072 frames in 5.0 seconds = 1414.338 FPS
 7027 frames in 5.0 seconds = 1405.366 FPS
 
  ==

under 2.6.18-gentoo-r2:

7790 frames in 5.0 seconds = 1557.990 FPS
57673 frames in 5.0 seconds = 11534.464 FPS
57865 frames in 5.0 seconds = 11572.907 FPS
56563 frames in 5.0 seconds = 11312.441 FPS
54164 frames in 5.0 seconds = 10832.644 FPS
53139 frames in 5.0 seconds = 10627.705 FPS
56300 frames in 5.0 seconds = 11259.851 FPS
54578 frames in 5.0 seconds = 10915.574 FPS
55864 frames in 5.0 seconds = 11172.672 FPS


looks improved?


  $ glxinfo
  name of display: :0.0
  libGL warning: 3D driver claims to not support visual 0x4b
  display: :0  screen: 0
  direct rendering: Yes
  ==
 
 under glxinfo (2.6.17-gentoo-r8):
 
 name of display: :0.0
 display: :0  screen: 0
 direct rendering: Yes
 server glx vendor string: SGI
 server glx version string: 1.2
 snip very long listing of info


name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2

 
  While you're looking at this I would appreciate if you could 
  tell me why I am 
  getting this libGL warning (and how to fix it)?
 
  Finally, I am also getting this mtrr overlap at boot:
  ==
  mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
  mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
  mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
  mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
  mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
  agpgart: Found an AGP 2.0 compliant device at :00:00.0.
  agpgart: Putting AGP V2 device at :00:00.0 into 4x mode
  agpgart: Putting AGP V2 device at :01:00.0 into 4x mode
  [drm] Setting GART location based on new memory map
  [drm] writeback test succeeded in 1 usecs
  
 
 under glxinfo (2.6.17-gentoo-r8)  greping dmesg for9 gl drm agp) I get:
 [drm] Initialized drm 1.0.1 20051102
 [drm] Initialized radeon 1.24.0 20060225 on minor 0
 [drm] Setting GART location based on new memory map
 [drm] Loading R200 Microcode
 [drm] writeback test succeeded in 1 usecs
 
 agpgart: Detected SiS 646 chipset
 agpgart: AGP aperture is 64M  at  0xe800
 agpgart: Found an AGP 2.0 compliant device at :00:00.0.
 agpgart: Putting AGP V2 device at :00:00.0 into 1x mode
 agpgart: Putting AGP V2 device at :01:00.0 into 1x mode
 
 Does look suspicious


dmesg | grep drm
[drm] Initialized drm 1.0.1 20051102
[drm] Initialized radeon 1.25.0 20060524 on minor 0
[drm] Setting GART location based on new memory map
[drm] Loading R200 Microcode
[drm] writeback test succeeded in 1 usecs


dmesg | grep agp
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected SiS 646 chipset
agpgart: AGP aperture is 64M @ 0xe800
agpgart: Found an AGP 2.0 compliant device at :00:00.0.
agpgart: Putting AGP V2 device at :00:00.0 into 1x mode
agpgart: Putting AGP V2 device at :01:00.0 into 1x mode


I'm not sure what all of this means, but, bzflag 
crashed once before using this 2.6.18-gentoo-r2
kernel..

hth,


James





-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Re: Video card memory disabled?

2006-11-22 Thread Mick
On Wednesday 22 November 2006 19:58, James wrote:
 James wireless at tampabay.rr.com writes:
  ==
 
$ glxgears
   libGL warning: 3D driver claims to not support visual 0x4b
   2446 frames in 5.0 seconds = 489.111 FPS
   2441 frames in 5.0 seconds = 488.094 FPS
   2448 frames in 5.0 seconds = 489.509 FPS
   2438 frames in 5.0 seconds = 487.576 FPS
   2445 frames in 5.0 seconds = 488.976 FPS
   2442 frames in 5.0 seconds = 488.238 FPS
   2439 frames in 5.0 seconds = 487.720 FPS
   ==
 
  under 2.6.17-gentoo-r8 I get (glxgears):
  6751 frames in 5.0 seconds = 1350.118 FPS
  7174 frames in 5.0 seconds = 1434.668 FPS
  6596 frames in 5.0 seconds = 1319.182 FPS
  6946 frames in 5.0 seconds = 1389.107 FPS
  6582 frames in 5.0 seconds = 1316.222 FPS
  5700 frames in 5.0 seconds = 1139.907 FPS
  7038 frames in 5.0 seconds = 1407.494 FPS
  6879 frames in 5.0 seconds = 1375.700 FPS
  6737 frames in 5.0 seconds = 1347.254 FPS
  7072 frames in 5.0 seconds = 1414.338 FPS
  7027 frames in 5.0 seconds = 1405.366 FPS
 
   ==

 under 2.6.18-gentoo-r2:

 7790 frames in 5.0 seconds = 1557.990 FPS
 57673 frames in 5.0 seconds = 11534.464 FPS
 57865 frames in 5.0 seconds = 11572.907 FPS
 56563 frames in 5.0 seconds = 11312.441 FPS
 54164 frames in 5.0 seconds = 10832.644 FPS
 53139 frames in 5.0 seconds = 10627.705 FPS
 56300 frames in 5.0 seconds = 11259.851 FPS
 54578 frames in 5.0 seconds = 10915.574 FPS
 55864 frames in 5.0 seconds = 11172.672 FPS


 looks improved?

Errm, hold on!  Did you minimise the graphics?

   $ glxinfo
   name of display: :0.0
   libGL warning: 3D driver claims to not support visual 0x4b
   display: :0  screen: 0
   direct rendering: Yes
   ==
 
  under glxinfo (2.6.17-gentoo-r8):
 
  name of display: :0.0
  display: :0  screen: 0
  direct rendering: Yes
  server glx vendor string: SGI
  server glx version string: 1.2
  snip very long listing of info

 name of display: :0.0
 display: :0  screen: 0
 direct rendering: Yes
 server glx vendor string: SGI
 server glx version string: 1.2

   While you're looking at this I would appreciate if you could
   tell me why I am
   getting this libGL warning (and how to fix it)?
  
   Finally, I am also getting this mtrr overlap at boot:
   ==
   mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
   mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
   mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
   mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
   mtrr: 0x4800,0x800 overlaps existing 0x4800,0x100
   agpgart: Found an AGP 2.0 compliant device at :00:00.0.
   agpgart: Putting AGP V2 device at :00:00.0 into 4x mode
   agpgart: Putting AGP V2 device at :01:00.0 into 4x mode
   [drm] Setting GART location based on new memory map
   [drm] writeback test succeeded in 1 usecs
   
 
  under glxinfo (2.6.17-gentoo-r8)  greping dmesg for9 gl drm agp) I get:
  [drm] Initialized drm 1.0.1 20051102
  [drm] Initialized radeon 1.24.0 20060225 on minor 0
  [drm] Setting GART location based on new memory map
  [drm] Loading R200 Microcode
  [drm] writeback test succeeded in 1 usecs
 
  agpgart: Detected SiS 646 chipset
  agpgart: AGP aperture is 64M  at  0xe800
  agpgart: Found an AGP 2.0 compliant device at :00:00.0.
  agpgart: Putting AGP V2 device at :00:00.0 into 1x mode
  agpgart: Putting AGP V2 device at :01:00.0 into 1x mode
 
  Does look suspicious

 dmesg | grep drm
 [drm] Initialized drm 1.0.1 20051102
 [drm] Initialized radeon 1.25.0 20060524 on minor 0
 [drm] Setting GART location based on new memory map
 [drm] Loading R200 Microcode
 [drm] writeback test succeeded in 1 usecs


 dmesg | grep agp
 Linux agpgart interface v0.101 (c) Dave Jones
 agpgart: Detected SiS 646 chipset
 agpgart: AGP aperture is 64M @ 0xe800
 agpgart: Found an AGP 2.0 compliant device at :00:00.0.
 agpgart: Putting AGP V2 device at :00:00.0 into 1x mode
 agpgart: Putting AGP V2 device at :01:00.0 into 1x mode


 I'm not sure what all of this means, but, bzflag
 crashed once before using this 2.6.18-gentoo-r2
 kernel..

Well, your card's performance seems to be significantly better than mine.  Not 
sure now how to fix mine.  :-(

-- 
Regards,
Mick


pgpb5o7F2F0CJ.pgp
Description: PGP signature


[gentoo-user] Re: Video card memory disabled?

2006-11-22 Thread James
Mick michaelkintzios at gmail.com writes:


  55864 frames in 5.0 seconds = 11172.672 FPS

  looks improved?

 Errm, hold on!  Did you minimise the graphics?

OK, I have not used 'glxgears' before so I just ran
''glx gears'

which is a small square, about 2x2

dunno? 
options to use with glxgears?


  looks improved?

 Errm, hold on!  Did you minimise the graphics?

dunno,
same as before
see above comments...


 Well, your card's performance seems to be significantly better than mine.  
 Not 
 sure now how to fix mine.  

d's performance seems to be significantly better than mine.  Not 
 sure now how to fix mine.  
 

I responed to 'try and help' all of this 3D stuff is pretty new
to me, as far as configs go.
i.e. 'monkey see monkey do on my end


hth,

James




-- 
gentoo-user@gentoo.org mailing list