Arch Linux

pseudonomous

Member

Registered: 2008-04-23

Posts: 349

Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

Hi everybody,

I know this is sort of like double posting, but my issues are with different cards on different computers, so I think this is appropraite.

Now i have an intel 82845G/GL "brookdale" intel onboard graphics controller.  Post Xorg upgrade, I could get say, 700-900 fps in glxgears, with no error messages, now post-upgrade I've noticed:

1) If I don't specify modes in my xorg, xorg will make bad choices for the defualt resolution which will cuase Xorg to completely lockup unless I use the vesa driver or the NoAccel option.  That's not too bad, I can fix this by specifying modes

2) I get a new error message when running glxgears:

Failed to initialize TTM buffer manager.  Falling back to classic

3) For some reason, when I open a Terminal after starting xfce a (random?) character will be repeated as input until I hit the backspace key, after which things seem fine.  This doesn't happen if I open another terminal.  (that's the xfce-terminal, to be precise).

Here's my Xorg.conf:

Section "ServerLayout"
    Option           "AllowEmptyInput" "off"
    Identifier     "X.org Configured"
    Screen      0  "Screen0" 0 0
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
    ModulePath   "/usr/lib/xorg/modules"
    FontPath     "/usr/share/fonts/misc"
    FontPath     "/usr/share/fonts/100dpi:unscaled"
    FontPath     "/usr/share/fonts/75dpi:unscaled"
    FontPath     "/usr/share/fonts/TTF"
    FontPath     "/usr/share/fonts/Type1"
EndSection

Section "Module"
    Load  "extmod"
    Load  "glx"
    Load  "dbe"
    Load  "xtrap"
    Load  "dri"
    Load  "freetype"
EndSection

Section "InputDevice"
    Identifier  "Keyboard0"
    Driver      "kbd"
    Option        "Device" "/dev/input/by-id/usb-Microsoft_Comfort_Curve_Keyboard_2000-event-kbd"
EndSection

Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "mouse"
    Option        "Protocol" "usb"
    Option        "Device" "/dev/input/by-id/usb-Logitech_USB_Optical_Mouse-event-mouse"
    Option        "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
    #DisplaySize      360   270    # mm
    Identifier   "Monitor0"
    VendorName   "GWY"
    ModelName    ""
    HorizSync    30.0 - 97.0
    VertRefresh  50.0 - 160.0
    Option        "DPMS"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
        #Option     "NoAccel"                # [<bool>]
        #Option     "SWcursor"               # [<bool>]
        #Option     "ColorKey"               # <i>
        #Option     "CacheLines"             # <i>
        #Option     "Dac6Bit"                # [<bool>]
        #Option     "DRI"                    # [<bool>]
        #Option     "NoDDC"                  # [<bool>]
        #Option     "ShowCache"              # [<bool>]
        #Option     "XvMCSurfaces"           # <i>
        #Option     "PageFlip"               # [<bool>]
    Option        "AccelMethod" "exa"
    Option        "EnabledPageFlip" "true"
    Identifier  "Card0"
    Driver      "intel"
    VendorName  "Intel Corporation"
    BoardName   "82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device"
    BusID       "PCI:0:2:0"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device     "Card0"
    Monitor    "Monitor0"
    DefaultDepth 24
    SubSection "Display"
        Viewport   0 0
        Depth     1
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     4
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     8
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     15
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     16
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     24
        Modes "1600x1200" "1280x1024"
    EndSubSection
EndSection

Note that before I specified:

    Option           "AllowEmptyInput" "off"

I couldn't get input devices to work anywhere near properly, probably becuase of the new hotplugging being enabled. 

I've tried with a color depth of 16, but this doesn't seem to help.

Here's the output from glxinfo:

name of display: :0.0
Failed to initialize TTM buffer manager.  Falling back to classic.
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_MESA_copy_sub_buffer, 
    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: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 845G 20061102 x86/MMX/SSE2
OpenGL version string: 1.3 Mesa 7.2
OpenGL extensions:
    GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_point_parameters, 
    GL_ARB_texture_border_clamp, GL_ARB_texture_compression, 
    GL_ARB_texture_cube_map, GL_ARB_texture_env_add, 
    GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, 
    GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, 
    GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, 
    GL_ARB_transpose_matrix, GL_ARB_vertex_buffer_object, 
    GL_ARB_vertex_program, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, 
    GL_EXT_blend_color, GL_EXT_blend_equation_separate, 
    GL_EXT_blend_func_separate, GL_EXT_blend_logic_op, GL_EXT_blend_minmax, 
    GL_EXT_blend_subtract, GL_EXT_clip_volume_hint, GL_EXT_cull_vertex, 
    GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, 
    GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays, 
    GL_EXT_packed_depth_stencil, GL_EXT_packed_pixels, 
    GL_EXT_point_parameters, 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_env_combine, GL_EXT_texture_env_dot3, 
    GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, 
    GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, 
    GL_3DFX_texture_compression_FXT1, GL_APPLE_client_storage, 
    GL_APPLE_packed_pixels, GL_ATI_blend_equation_separate, 
    GL_ATI_separate_stencil, GL_IBM_rasterpos_clip, 
    GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, 
    GL_MESA_pack_invert, GL_MESA_ycbcr_texture, GL_MESA_window_pos, 
    GL_NV_blend_square, GL_NV_light_max_exponent, GL_NV_point_sprite, 
    GL_NV_texture_rectangle, GL_NV_texgen_reflection, GL_NV_vertex_program, 
    GL_NV_vertex_program1_1, GL_OES_read_format, GL_SGIS_generate_mipmap, 
    GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, 
    GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays

3 GLX Visuals
   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
----------------------------------------------------------------------
0x21 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x22 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x72 32 tc  0 16  0 r  .  .  5  6  5  0  0  0  0  0  0  0  0  0 0 None

36 GLXFBConfigs:
   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
----------------------------------------------------------------------
0x73  0 tc  0 16  0 r  .  .  5  6  5  0  0  0  0  0  0  0  0  0 0 None
0x74  0 tc  0 16  0 r  .  .  5  6  5  0  0  0  0 16 16 16  0  0 0 Slow
0x75  0 tc  0 16  0 r  y  .  5  6  5  0  0  0  0  0  0  0  0  0 0 None
0x76  0 tc  0 16  0 r  y  .  5  6  5  0  0  0  0 16 16 16  0  0 0 Slow
0x77  0 tc  0 16  0 r  y  .  5  6  5  0  0  0  0  0  0  0  0  0 0 None
0x78  0 tc  0 16  0 r  y  .  5  6  5  0  0  0  0 16 16 16  0  0 0 Slow
0x79  0 tc  0 16  0 r  .  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x7a  0 tc  0 16  0 r  .  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x7b  0 tc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x7c  0 tc  0 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x7d  0 tc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x7e  0 tc  0 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x7f  0 tc  0 16  0 r  .  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x80  0 tc  0 16  0 r  .  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x81  0 tc  0 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x82  0 tc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x83  0 tc  0 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x84  0 tc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x85  0 dc  0 16  0 r  .  .  5  6  5  0  0  0  0  0  0  0  0  0 0 None
0x86  0 dc  0 16  0 r  .  .  5  6  5  0  0  0  0 16 16 16  0  0 0 Slow
0x87  0 dc  0 16  0 r  y  .  5  6  5  0  0  0  0  0  0  0  0  0 0 None
0x88  0 dc  0 16  0 r  y  .  5  6  5  0  0  0  0 16 16 16  0  0 0 Slow
0x89  0 dc  0 16  0 r  y  .  5  6  5  0  0  0  0  0  0  0  0  0 0 None
0x8a  0 dc  0 16  0 r  y  .  5  6  5  0  0  0  0 16 16 16  0  0 0 Slow
0x8b  0 dc  0 16  0 r  .  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x8c  0 dc  0 16  0 r  .  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x8d  0 dc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x8e  0 dc  0 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x8f  0 dc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x90  0 dc  0 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x91  0 dc  0 16  0 r  .  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x92  0 dc  0 16  0 r  .  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x93  0 dc  0 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x94  0 dc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x95  0 dc  0 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x96  0 dc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow

And here some excerpt from Xorg.0.log, these are out of order from which they appear, warnings are listed first, then errors:

(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) intel(0): Bad V_BIOS checksum
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x00020207 to 0x00020203
(WW) intel(0): PIPEASTAT before: status: VBLANK_INT_ENABLE VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): PIPEASTAT after: status: VBLANK_INT_ENABLE VSYNC_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): ESR is 0x00000010, page table error
(WW) intel(0): PGTBL_ER is 0x00000011
(WW) intel(0): Existing errors found in hardware state.
(WW) intel(0): Option "EnabledPageFlip" is not used
Current Operating System: Linux gypsy 2.6.27-ARCH #1 SMP PREEMPT Fri Nov 28 10:56:24 UTC 2008 i686
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) Mouse0: Unknown protocol "usb"
(EE) PreInit failed for input device "Mouse0"
(EE) Microsoft Comfort Curve Keyboard 2000: Read error: No such device
(EE) Microsoft Comfort Curve Keyboard 2000: Read error: No such device
(EE) Logitech USB Optical Mouse: Read error: No such device
(EE) No brand 4 Port KVMSwicther: Read error: No such device
(EE) intel(0): underrun on pipe A!

I've tried "xaa" mode rendering, but this doesn't seem to improve things.

It looks like I still have some problems with my input devices, but since they are more or less working, I'm not extremely concerned about the errors regarding keyboard, mouse, and kvm switch, I think the warings and the last error might give some clue as to why I'm having trouble with acceration.  Any advice will be appreciated.

On the plus side, I can finally get Xorg to default to starting 1600x1200 mode.

Last edited by pseudonomous (2008-12-01 19:27:25)

---

... imagine I'm making this argument without referencing cartoons.

moljac024

Member

From: Serbia

Registered: 2008-01-29

Posts: 2,676

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

Hmm, I get the same error when running glxgears

---

The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...

patroclo7

Member

From: Bassano del Grappa, ITALY

Registered: 2006-01-11

Posts: 915

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

TTM has been removed in the intel xorg driver, GEM is replacing it, but needs support in the kernel (it should be in 2.6.28). So you fall back to classic.
See the following gentoo bug: http://bugs.gentoo.org/show_bug.cgi?id=237468
I can alleviate the performance loss slightly with the following ~/.drirc:

<driconf>                                                                                                                                                                 
  <device screen="0" driver="i915">                                                                                                                                       
      <application name="Default">                                                                                                                                        
            <option name="vblank_mode" value="0" />                                                                                                                       
      </application>                                                                                                                                            
  </device>                                                                                                                                               
</driconf>

Last edited by patroclo7 (2008-12-01 11:41:26)

---

Mortuus in anima, curam gero cutis

b9anders

Member

Registered: 2007-11-07

Posts: 691

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

TTM has been removed in the intel xorg driver, GEM is replacing it, but needs support in the kernel (it should be in 2.6.28). So you fall back to classic.
See the following gentoo bug: http://bugs.gentoo.org/show_bug.cgi?id=237468
I can alleviate the performance loss slightly with the following ~/.drirc:

<driconf>                                                                                                                                                                 
  <device screen="0" driver="i915">                                                                                                                                       
      <application name="Default">                                                                                                                                        
            <option name="vblank_mode" value="0" />                                                                                                                       
      </application>                                                                                                                                            
  </device>                                                                                                                                               
</driconf>

So basically, the latest upgrade removes functionality for intel cards until 28 is out?

patroclo7

Member

From: Bassano del Grappa, ITALY

Registered: 2006-01-11

Posts: 915

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

I wouldn't say that functionality is removed, more exactly performance is degraded. This comes from a lack of coordination  in the development of the kernel and of the xorg driver. Obviously this concerns upstream, archlinux as a distro is totally innocent

---

Mortuus in anima, curam gero cutis

pseudonomous

Member

Registered: 2008-04-23

Posts: 349

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

Thanks for the info, patrocio7, you wouldn't happen to know if this would effect cards using the "r128" driver as well, would you?

---

... imagine I'm making this argument without referencing cartoons.

patroclo7

Member

From: Bassano del Grappa, ITALY

Registered: 2006-01-11

Posts: 915

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

No idea, sorry.

---

Mortuus in anima, curam gero cutis

b9anders

Member

Registered: 2007-11-07

Posts: 691

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

I wouldn't say that functionality is removed, more exactly performance is degraded. This comes from a lack of coordination  in the development of the kernel and of the xorg driver. Obviously this concerns upstream, archlinux as a distro is totally innocent

Does anyone know when the 28 kernel is expected to hit testing? Considering whether to downgrade until then.

patroclo7

Member

From: Bassano del Grappa, ITALY

Registered: 2006-01-11

Posts: 915

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

Less than a month I guess.

---

Mortuus in anima, curam gero cutis

agapito

Member

From: Who cares.

Registered: 2008-11-13

Posts: 679

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

What are benefits of GEM?

Because I have Mandriva Cooker with 2.6.28 rc5 kernel, Intel Driver 2.5.1, latest mesa, xorg and libdrm packages and performance is horrible.

---

Excuse my poor English.

patroclo7

Member

From: Bassano del Grappa, ITALY

Registered: 2006-01-11

Posts: 915

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

As you can see in the gentoo bug report the sequence of steps needed to enable GEM is quite complex, so I am unable to say if in Mandriva you are actually using GEM. Moreover I have never used GEM, I have only read that it should restore the performance which was given by the old i810, with less bugs and a more solid architecture.

Last edited by patroclo7 (2008-12-02 08:20:46)

---

Mortuus in anima, curam gero cutis

metal

Member

From: Russia,Moscow

Registered: 2006-01-23

Posts: 45

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

I  have same problem.
Why does we have intel driver 2.4.3? Acceleration won't work even after upgrading to the kernel 2.6.28. This driver useless for Xorg 1.5.

patroclo7

Member

From: Bassano del Grappa, ITALY

Registered: 2006-01-11

Posts: 915

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

Acceleration works(but the performance is slower), dri is enabled, and this driver is expected to be much less buggish than the previous releases of the driver. Moreover it is released and arch adopts always the most recent working releases. You should complain with upstream, not with the distribution.

---

Mortuus in anima, curam gero cutis

suggy

Member

Registered: 2008-08-12

Posts: 15

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

TTM has been removed in the intel xorg driver, GEM is replacing it, but needs support in the kernel (it should be in 2.6.28). So you fall back to classic.
See the following gentoo bug: http://bugs.gentoo.org/show_bug.cgi?id=237468
I can alleviate the performance loss slightly with the following ~/.drirc:

<driconf>                                                                                                                                                                 
  <device screen="0" driver="i915">                                                                                                                                       
      <application name="Default">                                                                                                                                        
            <option name="vblank_mode" value="0" />                                                                                                                       
      </application>                                                                                                                                            
  </device>                                                                                                                                               
</driconf>

Where does the file .drirc need to go? I see somewhere refered to as ~/ all the time but still haven't figured out where it actually means? /root?

dcrabs

Member

From: Sweden

Registered: 2008-10-03

Posts: 149

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

TTM has been removed in the intel xorg driver, GEM is replacing it, but needs support in the kernel (it should be in 2.6.28). So you fall back to classic.
See the following gentoo bug: http://bugs.gentoo.org/show_bug.cgi?id=237468
I can alleviate the performance loss slightly with the following ~/.drirc:

<driconf>                                                                                                                                                                 
  <device screen="0" driver="i915">                                                                                                                                       
      <application name="Default">                                                                                                                                        
            <option name="vblank_mode" value="0" />                                                                                                                       
      </application>                                                                                                                                            
  </device>                                                                                                                                               
</driconf>

Where does the file .drirc need to go? I see somewhere refered to as ~/ all the time but still haven't figured out where it actually means? /root?

It goes in ~/.drirc as stated above. "~" will always be the home directory of the current user. So if you are logged in as root it is "/root", if you are logged in with your normal user it will be "/home/username".

hoschi

Member

From: Ulm (Germany)

Registered: 2008-11-03

Posts: 468

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

So. I upgraded on kernel 2.6.28-rc7 - no positiv effect

As far as I know we need also libdrm-2.4 and intel-driver 2.5, both not in tree.
Okay, Arch is using the current official release, that is okay. But way we use a official release, if we know that their is a major failure in it?
80% of laptops and 50% desktops computers are now not usable for 3D applications...

If I know firefox-3.2 has a big security problem it will not add it to my distro, even when it is officially released?

Inkaine

Member

From: Germany

Registered: 2008-07-14

Posts: 88

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

Stop calling features bugs please!!! Go "blame" the the intel devs for being so stupid as to make their driver modern and make use of enhanced stability. Maybe first investigate about something before making claims. If you want performance and less complex systems - use Windows!

It seems most people still don't get that open source means constant DEVELOPMENT! And that it actually is a good thing.

And if you had investigated a bit more you'd have known that only kernel 2.6.28 won't be enough but GEM needs to be enabled in mesa, libdrm, intel-dri as well. If you want to use that, have fun using -git releases (available in AUR). And goddam stop whining about features!

oldherl

Member

Registered: 2008-08-31

Posts: 23

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

as I found here ( http://marc.info/?l=dri-devel&m=121127531521174&w=2 ), GEM is no better than TTM
then why to replace it>

wazow

Member

From: Europe

Registered: 2008-11-11

Posts: 39

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

Stop calling features bugs please!!! Go "blame" the the intel devs for being so stupid as to make their driver modern and make use of enhanced stability.

What you are suggesting is pure insanity, that I have been running away from when I switched from gentoo to Arch.  From a software engineering perspective it a clear mistake of intel devs to release their driver in this state, while none of the dependencies have been released.  It is plainly rude towards users.  Software is not for devs but for users.  Any dev forgetting that is shooting his own feet.

I admire and appreciate that intel devs work on this driver and make it available for us - this does not mean they do not make mistakes.  And this is clearly a mistake for me, as far as I can see.  This mistake has likely cost more time of users (in total) than these guys have spent developing the driver release.

patroclo7

Member

From: Bassano del Grappa, ITALY

Registered: 2006-01-11

Posts: 915

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

Perhaps we should be careful with words. It is not true that the dependencies of the driver have not been released. The intel driver works with classsic buffer management. The GEM stuff is required to enhance performance, but this is not what is usually considered a dependency. Nonetheless I understand that it is awkward to abandon an old system when the new one is not ready, falling back to something even older. Anyone somebody with some technical specific skills on the subject should complain with upstream (the distribution is TOTALLY innocent, because there are no bugs, no security risks etc. and so it is right to follow upstream)

---

Mortuus in anima, curam gero cutis

Svlad Cjelli

Member

From: dusk till dawn

Registered: 2008-10-21

Posts: 99

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

(the distribution is TOTALLY innocent, because there are no bugs, no security risks etc. and so it is right to follow upstream)

dito...

other distros have exactly the same problem. In Ubuntu my 3D performance is even worse...
Fedora (or Fedora Rawhide) uses a GEM-patched Kernel as far as i know. The peformance there is fairly decent (as far as i read)

dav7

Member

From: Australia

Registered: 2008-02-08

Posts: 674

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

This is interesting... hm.

That .drirc patch upped my FPS from about 80 to ~180, thanks

Although I have no idea what to do with it, lol.

-dav7

---

Windows was made for looking at success from a distance through a wall of oversimplicity. Linux removes the wall, so you can just walk up to success and make it your own.
--
Reinventing the wheel is fun. You get to redefine pi.

JGC

Developer

Registered: 2003-12-03

Posts: 1,664

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

Ok, some explanation:
- libdrm 2.4.1 and xf86-video-2.5.1 are buggy. And by buggy, I mean buggy. You don't want those on your system.
- The TTM message is useless. I'll patch it out of the next intel-dri release
- TTM is dead, it was replaced by GEM before it made it into the kernel and the server. That's why DRI2 got delayed.
- The Vblank setting limits your framerate by turning on VSync. This should not affect performance, because you can't see the higher framerate on the screen anyways.

I had reports about broken DPMS when AIGLX is enabled with VSync enabled, so I'm thinking about reverting that default.

most users who run glxgears will do a simple calculation: 1+1=2:
- they get 60fps performance
- there's a weird warning nobody understands
result:
There must be a bug that causes this warning and limits my framerate to 60fps, which is the wrong assumption.

wazow

Member

From: Europe

Registered: 2008-11-11

Posts: 39

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

Well, I have stumbled on this page not because of glxgears - I do not care about it.  I stumbled on it because I was tryin to understand why Maryo has become jerky recently.  Of course there could be other reasons, but this looked plausible.

linko

Member

From: Mississippi

Registered: 2008-12-06

Posts: 16

Re: Xorg dri problems, intel "failed to initialize TTM" [EXPLAINED]

I just installed Arch (coming from Debian) on my X61 Thinkpad, which uses the Intel 965G integrated graphics.  In Debian I get about 1000fps in glxgears.  In Arch I get 49fps, with the "Failed to initialize TTM buffer manager.  Falling back to classic." error.

Urban Terror plays smoother in Arch than I have EVER seen it play in Debian.  This error doesn't correlate to any graphics problems on my machine at all.

Thanks ^ JGC