Dotaz: 3D akcelerace s Ati RAGE 128, zátuh systému

[Václav HFechs Švirga]

Sehnal jsem trochu postarší počítač (Athlon 1,2 Ghz, 196 MB ram na VIA chipsetu) s grafickou kartou (32 MB) která se v lspci hlásí jako:

VGA compatible controller: ATI Technologies Inc Rage 128 RL/VR AGP

Napadlo mě že by nebylo špatné zkusit na ní rozjet 3D akceleraci, protože přece jen občas si nějakou starší hru zahrát po lance na dvou pc není špatné (bzflag..., kdo zná ví ). Sáhl jsem hned po OSS driverech a nastavil podle nějakého howta xorg.conf a akcelerace "klapla" na první pokus. Glxgears ukazuje něco kolem 500 (hádam že na tu kartu dobrý výkon) a tuxracer taky běží. Jenže mé nadšení opadlo při pokusu o spuštění hry cube. Je mi jasné že od tak stařičké karty nemůžu čekat zázraky, ale nějak jsem doufal, že aspoň verze z roku 2004 může nějak (na nejmenší rozlišení) fungovat. Bohužel po spuštění (a sdl initu) kompletně zatuhne linux (arch linux) a pomůže jen restart.

Pro jistotu uvedu podstatné sekce Xorgu.

Section "Module"
  Load "i2c"
  Load "bitmap"
  Load "ddc"
  Load "extmod"
  Load "freetype"
  Load "int10"
  Load "type1"
  Load "vbe"
  load "glx"
  load "dri"
  load "drm"
EndSection

Section "Device"
        Identifier  "Card0"
        Driver      "r128"
        VendorName  "All"
        BoardName   "All"
        Option          "AccelMethod"   "EXA"
        VideoRam 32768
        Option "AGPMode" "4"
        Option "AGPFastWrite" "True"
        BusID       "PCI:1:0:0"
EndSection

Section "DRI"
        Mode 0666
EndSection

V xorg.log jsem nic zvláštího během spuštění cube nezaznamenal, ale při spuštění X nějaké chyby jsou:

(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32

A pak jsem ještě nalezl chyby v /var/log/messages.log

Apr 18 23:08:53 pracka [drm] Initialized drm 1.1.0 20060810
Apr 18 23:08:53 pracka [drm] Initialized r128 2.5.0 20030725 on minor 0
Apr 18 23:08:53 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 18 23:08:53 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 18 23:08:53 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 18 23:08:56 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 18 23:08:56 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 18 23:08:56 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 18 23:08:58 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 18 23:08:58 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 18 23:08:58 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 18 23:08:59 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 18 23:08:59 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 18 23:08:59 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 18 23:09:02 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 18 23:09:02 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 18 23:09:02 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 18 23:09:03 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 18 23:09:03 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 18 23:09:03 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 18 23:09:05 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 18 23:09:05 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 18 23:09:05 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 18 23:09:07 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 18 23:09:07 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 18 23:09:07 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 18 23:09:08 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 18 23:09:08 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 18 23:09:08 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode

A nakonec výpis glxinfo:

name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method, 
    GLX_SGI_swap_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, 
    GLX_SGIX_visual_select_group
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, 
    GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, 
    GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, 
    GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_swap_control, 
    GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_swap_control, 
    GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, 
    GLX_SGIX_visual_select_group
OpenGL vendor string: VA Linux Systems, Inc.
OpenGL renderer string: Mesa DRI Rage 128 20051027 AGP 4x x86/MMX+/3DNow!+/SSE
OpenGL version string: 1.2 Mesa 6.5.2
OpenGL extensions:
    GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, 
    GL_ARB_texture_compression, GL_ARB_texture_env_add, 
    GL_ARB_texture_mirrored_repeat, GL_ARB_transpose_matrix, 
    GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, 
    GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint, 
    GL_EXT_compiled_vertex_array, GL_EXT_convolution, GL_EXT_copy_texture, 
    GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_histogram, 
    GL_EXT_packed_pixels, GL_EXT_polygon_offset, GL_EXT_rescale_normal, 
    GL_EXT_secondary_color, GL_EXT_separate_specular_color, 
    GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, 
    GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_object, 
    GL_EXT_vertex_array, GL_APPLE_packed_pixels, GL_IBM_rasterpos_clip, 
    GL_IBM_texture_mirrored_repeat, GL_MESA_ycbcr_texture, GL_MESA_window_pos, 
    GL_NV_blend_square, GL_NV_light_max_exponent, GL_NV_texgen_reflection, 
    GL_OES_read_format, GL_SGI_color_matrix, GL_SGI_color_table, 
    GL_SGIS_generate_mipmap, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x23 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x24 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x25 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x26 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x27 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x28 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x29 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x2a 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x2b 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x2c 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x2d 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x2e 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x2f 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x30 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x31 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x32 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow

Možná to vážně bude zastaralostí grafické karty, ale raději se ptám.

Odpovědi

[Václav HFechs Švirga]

Neverball se choval podobně (rovněž zátuh, ale šlo ještě hýbat myší), ale tady pomohlo zvýšit barevnou hloubku z 16 na 24 bitů (u cube bohužel ne). Bzflag taky funguje.

[Václav HFechs Švirga]

Hm, teď jsem si všiml že jsem z messages.log vložil tu méně podstatnou část, chyby před pádem systému jsou trochu jiné, vložím to sem zítra.

[black - aka pol]

OSS drivery vždycky braly víc výkonu, zkusil jsi normální?

[black - aka pol]

Schválně jsem je zkusil a chová se to úplně stejně. Ach jo.

01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro Ultra TF

glxgears 400~1200

Rage má strašně slabý výkon na OpenGL, nicméně padat by to nemuselo. Udělat si balíček ze zdroje se mi bohužel nepodařilo, Makefile nenajde snad vůbec nic...

[~||~]

Takovyto problem jsem mival s postarsi grafickou kartou, zjistil jsem, ze pri vysoke zatezi (v 3D hrach) se po chvili prehreje bud karta, nebo CPU a proto dojde k zatuhnuti. Chyby oznamujici prepinani karty do rezimu AGP 0 byvaji zpusobeny chybnou konfiguraci BIOS, AGP mode by v nem mel byt nastaven manualne a to bud na 4x, nebo na 2x. Take muze pomoci zvysit AGP latency, nebo AGP texture size v BIOS. Kdyz system zatuhne, funguje numlock ? Pokud funguje, pak muze byt problem v tom, ze se prepne obrazovy rezim graficke karty na jeden z tech, ktere nejsou podporovany, pote hra spadne a rezim zustane nastaven chybne, cili neni nic videt (jen cerna obrazovka), ale v takovem pripade vzdy numlock funguje.

[Václav HFechs Švirga]

Ano, asi to bude ten problém.

[Václav HFechs Švirga]

Jenom s tím rozdílem že podle strace cube nespadlo.

[Václav HFechs Švirga]

K danému PC jsem se dostal až dnes, ale slibované chyby jsou zde (ano, je to podobné, přecházení do 0x módu).

Apr 20 20:30:02 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:30:02 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:30:02 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:30:06 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:30:06 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:30:06 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:30:07 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:30:07 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:30:07 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:30:09 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:30:09 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:30:09 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:30:12 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:30:12 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:30:12 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:30:13 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:30:13 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:30:13 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:30:15 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:30:15 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:30:15 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:30:17 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:30:17 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:30:17 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:30:18 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:30:18 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:30:18 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:31:30 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:31:30 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:31:30 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:31:32 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:31:32 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:31:32 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:31:34 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:31:34 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:31:34 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:31:36 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:31:36 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:31:36 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:31:37 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:31:37 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:31:37 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:31:39 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:31:39 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:31:39 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:31:41 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:31:41 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:31:41 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:31:42 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:31:42 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:31:42 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:31:44 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:31:44 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:31:44 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:38:30 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:38:30 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:38:30 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:38:32 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:38:32 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:38:32 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:38:34 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:38:34 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:38:34 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:38:35 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:38:35 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:38:35 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:38:37 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:38:37 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:38:37 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:38:39 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:38:39 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:38:39 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:38:40 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:38:40 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:38:40 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:38:42 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:38:42 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:38:42 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:38:44 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:38:44 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
Apr 20 20:38:44 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
Apr 20 20:51:35 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:51:35 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
Apr 20 20:51:35 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 2x mode
Apr 20 20:51:38 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:51:38 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
Apr 20 20:51:38 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 2x mode
Apr 20 20:51:40 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:51:40 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
Apr 20 20:51:40 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 2x mode
Apr 20 20:51:41 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:51:41 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
Apr 20 20:51:41 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 2x mode
Apr 20 20:51:43 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:51:43 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
Apr 20 20:51:43 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 2x mode
Apr 20 20:51:45 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:51:45 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
Apr 20 20:51:45 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 2x mode
Apr 20 20:51:46 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:51:46 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
Apr 20 20:51:46 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 2x mode
Apr 20 20:51:48 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:51:48 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
Apr 20 20:51:48 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 2x mode
Apr 20 20:51:49 pracka agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Apr 20 20:51:49 pracka agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
Apr 20 20:51:49 pracka agpgart: Putting AGP V2 device at 0000:01:00.0 into 2x mode

Numlock nesvítí a s počítačem se nedá cokoliv dělat. Ještě vyzkouším jestli pingá.

[Václav HFechs Švirga]

Tak beru zpět, numlock svítí, jen na jeho mačkání nějak nebere nikdo ohled (ale svítí, moje chyba). A mašina pingá.

[Václav HFechs Švirga]

Uhaaa, dal jsem tam repráčky a obavy se potvrdily - hudba hraje, hra běží, ale obraz není. A já bych si tak rád zahrál :(.

[Ctirad Feřtr]

Obávám se, že je to opět další střípek do mozaiky rozbitých DRI driverů po implemetaci AIGLX :( Ty příznaky jsou velmi podobné tomu, co mi to dělá na Matrox G400.

Zkusil bych ještě shodit AGP režim na 2x a vypnout fast write, tyhle věci na starých kartách často zlobily, ale obávám se, že to nepomůže.

[User682]

zdravim,

no na podobne chyby jsem narazil take. Rage Mobility, Rage128, MGA G550 a dalsi by se nasly. Neco nefunguje a na necem mplayer (mplayer -vo *gl*) se da slusne zakousnout masina. Fulscreen take najede na MGA.

Sice se vyviji o 106 drivery na radeony a nvidii, ale jaksi treba do notebooku novou grafiku nenarvete a menit matrox se mi nezda jako dobre reseni.

Nicmene, jak z toho ven? Hodim to jako otazku do fora.

Osobne asi s psanim/opravami x/dri driveru nepomuzu. Skutecne tolik casu nemam. Nicmene veci do kernelu se daji velmi dobre testovat a reportovat. Konfera okolo x/dri take nejak zije a lide vcelku reaguji i opravami.

Nevidel jsem a vcelku v tomto tapam, jak nejlepe zaridit, aby si clovek mohl do balickovaciho systemu nainstalovat snapshot nebo versi ze svn/git/. Tak, aby to nezborilo system nebo nezbyly potom ruzne rozkopirovane soubory bez ladu a skladu v systemu. A aby se daly take pouzivat stavajici funkcni X-ka.

Pak se da samozrejme zaspolupracovat s vyvojari. Na to nejaky cas je. Sice to neni pomoc nejlepsi, ale i testovani hodne pomuze.

Navody, nazory ? Je mozna samostatna instalace z svn/git a do toho bezici funkcni X-ka ?

diky

Pavel Kysilka

[nooneanymore]

Jednou se mi grafická karta Radeon 9600 Pro chovala podobně. Nebylo to softwarem, nýbrž mnou a hardwarem: karta nebyla pořádně zasunutá. Asi to tím nebude, ale čertví.

[Aleš Černý]

Dělalo mi to to samý a teď jsem odhalil příčinu - AGPMode 4x. Pokud nastavím jen 1x nebo 2x, jede to v pohodě, dám 4x a zátuh. Takže doporučuju zkusit v xorg.conf

Option "AGPMode" "2"

(Jo a ty volby "AGPFastWrite" a "AccelMethod" nevím, co zlepšují, ale já je tam pro jistotu nemám a funguje to a v pohodě.)