LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 04-09-2007, 02:35 AM   #1
Kocil
Member
 
Registered: Feb 2003
Distribution: Redhat since 5.2, Slackware since 9.0, Vector since 4.0
Posts: 209

Rep: Reputation: 31
Question DRI, glxgears runs fast but glxinfo said it is disabled ???


Dear all.

I have a notebook with Intel 915 graphics card.
I was trying to enable the DRI on that notebook,
following the excellent guide at
http://www.linuxquestions.org/questions/showthread.php?t=402003.

I compiled new kernel 2.6.20,
and replaced the old X11R6 with the X11R7 package from slackware-x11-project on sourceforge.
Set the xorg.conf accordingly, and a couple fixes here and there,
then run startx from console.

Everything looked fine.
No significant error printed at the console,
as well as logged at /var/log/X.org.log.
glxgears showed 600~700 FPS (24 bit mode) and 900~1000 FPS (16 bit mode).
ppracer (a 3D game) run well.

HOWEVER ... glxinfo said that
direct rendering : no



So ... did I really get the DRI enabled or not ?
Is there any other way than glxinfo to tell that the DRI is working ?

Thank you.
--------------

Snippet from Xorg.0.log, showing the drm sucessfully loaded i915 dri module
Code:
(II) I810(0): [drm] loaded kernel module for "i915" driver
(II) I810(0): [drm] DRM interface version 1.3
(II) I810(0): [drm] created "i915" driver at busid "pci:0000:00:02.0"

Output of glxinfo,
notice that direct rendering is still no,
although the OpenGL renderer string is already
Mesa DRI Intel(R) 915GM 20061017 x86/MMX/SSE2

Code:
name of display: :0.0
display: :0  screen: 0
direct rendering: No
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_make_current_read, 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_copy_sub_buffer, 
    GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_swap_control, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group, 
    GLX_EXT_texture_from_pixmap
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 915GM 20061017 x86/MMX/SSE2
OpenGL version string: 1.3 Mesa 6.5.2
OpenGL extensions:
    GL_ARB_depth_texture, GL_ARB_fragment_program, GL_ARB_imaging, 
    GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_point_parameters, 
    GL_ARB_shadow, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, 
    GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
 
Old 04-09-2007, 07:20 AM   #2
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 542Reputation: 542Reputation: 542Reputation: 542Reputation: 542Reputation: 542
That is your onboard graphics device, right? It **might** not be capable of doing better than it already is (which is pretty decent for an Intel onboard unit).. Can you verify that the machine *can* do better, from past experience?
In the config file (despite the information above in your post), have you loaded the module 'GLX' and are using the DRI extension?
Hmmmmmmm....
 
Old 04-09-2007, 10:45 AM   #3
duryodhan
Senior Member
 
Registered: Oct 2006
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
Posts: 1,054

Rep: Reputation: 46
No you didn't get DRI enabled.

Try and not use the i915 driver, it is screwed up . Use the i810 driver.

There must be a gazzillion posts already on how to get DRI working (along with the beautiful sticky) by cwwilson. Search in LQ-Slackware .. you will most probably get what you want.

I dont have time right now / See if someone else can help you out.
 
Old 04-10-2007, 05:44 AM   #4
Kocil
Member
 
Registered: Feb 2003
Distribution: Redhat since 5.2, Slackware since 9.0, Vector since 4.0
Posts: 209

Original Poster
Rep: Reputation: 31
Quote:
Originally Posted by duryodhan
No you didn't get DRI enabled.
Try and not use the i915 driver, it is screwed up . Use the i810 driver.
I was using i810 driver,
it load the i915 DRI module by itself
(That is the expected behaviour)

Quote:
That is your onboard graphics device, right? It **might** not be capable of doing better than it already is (which is pretty decent for an Intel onboard unit).. Can you verify that the machine *can* do better, from past experience?
Yes it is on board. I was using a laptop indeed
All that I can verify, it was worse.
Before the i810 driver,
I was using the default vesa driver, and glxgears got around 300 FPS.
PPracer was unplayable.

Judging by the glxgears and ppracer performance,
I though the DRI was working.
 
Old 04-10-2007, 11:08 AM   #5
GamerX
Member
 
Registered: Nov 2006
Location: Vancouver, BC
Distribution: Slackware
Posts: 102

Rep: Reputation: Disabled
Direct rendering and GL acceleration are different. glxgears is an OpenGL application and is able to use the video card because OpenGL acts as a driver itself. i.e. video cards expose an interface according to OpenGL 2.0 specs (and similarly DirectX) and the applications (like glxgears) based on OpenGL libraries for rendering are hence able to use the hardware's features for acceleration.

Window managers do not necessarily use OpenGL, they use a "rendering manager" which may or may not be able to use hardware for acceleration (direct rendering).

Also check that you have Direct Rendering Manager option enabled when compiling the kernel (under device drivers -> graphics)
 
Old 04-11-2007, 03:39 AM   #6
Kocil
Member
 
Registered: Feb 2003
Distribution: Redhat since 5.2, Slackware since 9.0, Vector since 4.0
Posts: 209

Original Poster
Rep: Reputation: 31
Quote:
Originally Posted by GamerX
Also check that you have Direct Rendering Manager option enabled when compiling the kernel (under device drivers -> graphics)
Thanks for the OpenGL / DRM explanation.
Meanwhile, I checked the kernel, DRM is already enabled as a module [M],
and the i915 driver is also enabled as a module.
(FYI, they have moved DRM to Device Driver -> Character Devices).
The module is properly installed too.
Code:
kocil:$ find /lib/modules/2.6.20/ -iname "*i915*"
/lib/modules/2.6.20/kernel/drivers/char/drm/i915.ko
it is also has been loaded
Code:
root:# lsmod            
Module                  Size  Used by
i915                   21504  2 
drm                    69404  3 i915
Just curious, when I call startx, X.org informs the following warning
Code:
(II) Primary Device is: PCI 00:02:0
(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
(--) Chipset 915GM found
Meanwhile, lspci lists two video cards as follow
Code:
root:# lspci
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
Maybe xorg uses the first PCI device (00:02:0) that is VGA compatible,
thus DRI cannot be enabled.

Still wondering
 
Old 04-12-2007, 04:04 AM   #7
Kocil
Member
 
Registered: Feb 2003
Distribution: Redhat since 5.2, Slackware since 9.0, Vector since 4.0
Posts: 209

Original Poster
Rep: Reputation: 31
Hi folks.

It has solved.
I removed the X11-7.2 packages, then installed X11-7.1.1 packages from Zenwalk.
No change in the xorg.conf, except the ModulePaths.
The glxinfo said DRI is enabled, and the glxgears got 1100 FPS.

Thanks for all of you.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
glxinfo/glxgears can't open display jrtayloriv Linux - Newbie 2 08-06-2009 12:43 PM
DRI disabled when i try to remote solaris via suse a.toraby Linux - Software 0 10-17-2006 05:17 AM
Direct rendering enabled in Xorg log, disabled in glxinfo alexbaretta Linux - Software 1 06-23-2006 11:04 AM
XFree86 DRI : glxinfo -> Direct rendering : No Muzzy Linux - Hardware 20 05-24-2004 07:03 AM
glxinfo reports DRI disabled as a normal user guerilla fighta Linux - Software 4 10-07-2003 11:37 AM


All times are GMT -5. The time now is 11:54 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration