[SOLVED] How do i enable direct rendering sandy bridge Fedora 17

idoitprone · #1 18th June 2012, 03:02 AM

I have a nvidia optimus system

How do i enable direct rendering for the intel sandy bridge chip hd3000

Code:

$ glxinfo | grep direct
libGL: OpenDriver: trying /usr/lib32/dri/i965_dri.so
libGL error: dlopen /usr/lib32/dri/i965_dri.so failed (/usr/lib32/dri/i965_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL: OpenDriver: trying /usr/lib32/dri/swrast_dri.so
libGL error: dlopen /usr/lib32/dri/swrast_dri.so failed (/usr/lib32/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: swrast_dri.so
libGL error: reverting to indirect rendering
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)

Wayne · #2 18th June 2012, 04:02 AM

I'm sure I read somewhere that there's no Linux support for the Optimus chip...

ausadl · #3 18th June 2012, 04:49 AM

Don't know how much of help but try look at http://bumblebee-project.org/

David Batson · #4 18th June 2012, 07:55 PM

http://rpmfusion.org/Howto/nVidia#VDPAU.2BAC8-VAAPI

Oops that's for NVidia. You need libva-vaapi from rpmfusion for Intel.

EDIT: Actually it should be the following:
libva
libva-intel-driver
libva-utils

idoitprone · #5 19th June 2012, 03:40 AM

Quote:

Originally Posted by David Batson

http://rpmfusion.org/Howto/nVidia#VDPAU.2BAC8-VAAPI

Oops that's for NVidia. You need libva-vaapi from rpmfusion for Intel.

EDIT: Actually it should be the following:
libva
libva-intel-driver
libva-utils

nope i installed those packages and video acceleration does not work for the intel chip

Code:

$ glxinfo | grep direct
libGL: OpenDriver: trying /usr/lib32/dri/i965_dri.so
libGL error: dlopen /usr/lib32/dri/i965_dri.so failed (/usr/lib32/dri/i965_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL: OpenDriver: trying /usr/lib32/dri/swrast_dri.so
libGL error: dlopen /usr/lib32/dri/swrast_dri.so failed (/usr/lib32/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: swrast_dri.so
libGL error: reverting to indirect rendering
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)

@ausadi and @ Wayne i already have bumblbee installed. I am just waiting for those drivers to be stable and work together with virtualgl and etc.

I just want the intel chip to work, but direct rendering is not enabled which is a problem because I cannot go on an adventure to find the greatest insult on monkey island

David Batson · #6 19th June 2012, 03:51 AM

It seems to be looking in the wrong directory.
i965_dri.so should be in /usr/lib/dri/ or usr/lib64/dri/ depending upon if you have a Fedora 32 bit or Fedora 64 bit.

I only have /usr/lib/ and usr/lib64/ on my Fedora 17 install (64-bit system here). i965_dri.so is in /usr/lib64/dri/ on my system (sandybridge intel hd3000)

Code:

[root@localhost ~]# vainfo
libva: VA-API version 0.32.0
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib64/dri/i965_drv_video.so
libva: va_openDriver() returns 0
vainfo: VA-API version: 0.32 (libva 1.0.15)
vainfo: Driver version: Intel i965 driver - 1.0.15
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileH264Baseline           :	VAEntrypointVLD
      VAProfileH264Baseline           :	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
[root@localhost ~]# glxinfo | grep direct
direct rendering: Yes
[root@localhost ~]#

idoitprone · #7 19th June 2012, 04:32 AM

Quote:

Originally Posted by David Batson

It seems to be looking in the wrong directory.
i965_dri.so should be in /usr/lib/dri/ or usr/lib64/dri/ depending upon if you have a Fedora 32 bit or Fedora 64 bit.

I only have /usr/lib/ and usr/lib64/ on my Fedora 17 install (64-bit system here). i965_dri.so is in /usr/lib64/dri/ on my system (sandybridge intel hd3000)

Code:

[root@localhost ~]# vainfo
libva: VA-API version 0.32.0
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib64/dri/i965_drv_video.so
libva: va_openDriver() returns 0
vainfo: VA-API version: 0.32 (libva 1.0.15)
vainfo: Driver version: Intel i965 driver - 1.0.15
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileH264Baseline           :	VAEntrypointVLD
      VAProfileH264Baseline           :	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
[root@localhost ~]# glxinfo | grep direct
direct rendering: Yes
[root@localhost ~]#

i have fedora 17 64 bit

Code:

$ vainfo 
libva: VA-API version 0.32.0
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib64/dri/i965_drv_video.so
libva: va_openDriver() returns 0
vainfo: VA-API version: 0.32 (libva 1.0.15)
vainfo: Driver version: Intel i965 driver - 1.0.15
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileH264Baseline           : VAEntrypointVLD
      VAProfileH264Baseline           : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD

i get the same output when i run vainfo

but when i run glxinfo i still get this.

I just want to get direct rendering working so i can run some wine apps. I find it strange that direct rendering does not work with an intel chip, maybe its because i have 32 lib as a dependency of wine

i tried simlinking /usr/lib to /usr/lib32 but ii get this error

Code:

$ glxinfo  | grep direct
ibGL: OpenDriver: trying /usr/lib32/dri/i965_dri.so
libGL error: dlopen /usr/lib32/dri/i965_dri.so failed (/usr/lib32/dri/i965_dri.so: wrong ELF class: ELFCLASS32)
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL: OpenDriver: trying /usr/lib32/dri/swrast_dri.so
libGL error: dlopen /usr/lib32/dri/swrast_dri.so failed (/usr/lib32/dri/swrast_dri.so: wrong ELF class: ELFCLASS32)
libGL error: unable to load driver: swrast_dri.so
libGL error: reverting to indirect rendering
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)

David Batson · #8 19th June 2012, 05:25 AM

Not in Fedora atm, but do you have the (appropriate) mesa packages installed?

---------- Post added at 10:25 PM ---------- Previous post was at 10:21 PM ----------

AFAIK, wrong ELF class means that you are tying to use a 32-bit driver for a 64-bit application or vice versa.

Maybe you installed the 32-bit mesa libraries instead of the 64-bit ones.

idoitprone · #9 19th June 2012, 05:37 AM

Quote:

Originally Posted by David Batson

Not in Fedora atm, but do you have the (appropriate) mesa packages installed?

---------- Post added at 10:25 PM ---------- Previous post was at 10:21 PM ----------

AFAIK, wrong ELF class means that you are tying to use a 32-bit driver for a 64-bit application or vice versa.

Maybe you installed the 32-bit mesa libraries instead of the 64-bit ones.

Code:

rpm -qa | grep mesa | sort
mesa-dri-drivers-8.0.3-1.fc17.i686
mesa-dri-drivers-8.0.3-1.fc17.x86_64
mesa-dri-filesystem-8.0.3-1.fc17.i686
mesa-dri-filesystem-8.0.3-1.fc17.x86_64
mesa-libEGL-8.0.3-1.fc17.i686
mesa-libEGL-8.0.3-1.fc17.x86_64
mesa-libEGL-devel-8.0.3-1.fc17.i686
mesa-libEGL-devel-8.0.3-1.fc17.x86_64
mesa-libgbm-8.0.3-1.fc17.i686
mesa-libgbm-8.0.3-1.fc17.x86_64
mesa-libgbm-devel-8.0.3-1.fc17.i686
mesa-libgbm-devel-8.0.3-1.fc17.x86_64
mesa-libGL-8.0.3-1.fc17.i686
mesa-libGL-8.0.3-1.fc17.x86_64
mesa-libglapi-8.0.3-1.fc17.i686
mesa-libglapi-8.0.3-1.fc17.x86_64
mesa-libGL-devel-8.0.3-1.fc17.i686
mesa-libGL-devel-8.0.3-1.fc17.x86_64
mesa-libGLES-8.0.3-1.fc17.i686
mesa-libGLES-8.0.3-1.fc17.x86_64
mesa-libGLES-devel-8.0.3-1.fc17.i686
mesa-libGLU-8.0.3-1.fc17.i686
mesa-libGLU-8.0.3-1.fc17.x86_64
mesa-libGLU-devel-8.0.3-1.fc17.i686
mesa-libGLU-devel-8.0.3-1.fc17.x86_64
mesa-libGLw-6.5.1-10.fc17.i686
mesa-libGLw-6.5.1-10.fc17.x86_64
mesa-libGLw-devel-6.5.1-10.fc17.i686
mesa-libOSMesa-8.0.3-1.fc17.i686
mesa-libOSMesa-8.0.3-1.fc17.x86_64
mesa-libOSMesa-devel-8.0.3-1.fc17.i686
mesa-libwayland-egl-8.0.3-1.fc17.i686
mesa-libwayland-egl-8.0.3-1.fc17.x86_64
mesa-libwayland-egl-devel-8.0.3-1.fc17.i686
mesa-libxatracker-8.0.3-1.fc17.i686
mesa-libxatracker-8.0.3-1.fc17.x86_64
mesa-libxatracker-devel-8.0.3-1.fc17.i686
mesa-libxatracker-devel-8.0.3-1.fc17.x86_64

not sure which packages that you have in mind?

David Batson · #10 19th June 2012, 05:59 AM

You might try to determine which drivers are 32-bit and which 64-bit in each of the following directories. You can probably tell the difference between them by the file size.

/usr/lib/dri/i965_dri.so
/usr/lib32/dri/i965_dri.so
/usr/lib64/dri/i965_dri.so

If you get a wrong ELF class error, try using a different i965_dri.so in /usr/lib32/dri/

At least that is what I would try.

---------- Post added at 10:59 PM ---------- Previous post was at 10:48 PM ----------

Just booted back into Fedora. This is what I have for mesa. I am strictly 64-bit. Looking in Add/Remove Software I only see the 64-bit mesa libraries available for my system.

Code:

[root@localhost ~]# rpm -qa | grep mesa | sort
mesa-dri-drivers-8.0.3-1.fc17.x86_64
mesa-dri-filesystem-8.0.3-1.fc17.x86_64
mesa-libGL-8.0.3-1.fc17.i686
mesa-libGL-8.0.3-1.fc17.x86_64
mesa-libglapi-8.0.3-1.fc17.i686
mesa-libglapi-8.0.3-1.fc17.x86_64
mesa-libGLU-8.0.3-1.fc17.i686
mesa-libGLU-8.0.3-1.fc17.x86_64
mesa-libxatracker-8.0.3-1.fc17.x86_64
[root@localhost ~]#

You have both 32-bit and 64-bit mesa installed. Not sure how you did that. Was yours an upgrade install or clean install? I used a clean install here.

EDIT: Looking again at my output in Terminal there do appear to be some 32-bit mesa rpms there. Not all that you have though.

idoitprone · #11 19th June 2012, 01:43 PM

Quote:

Originally Posted by David Batson

You might try to determine which drivers are 32-bit and which 64-bit in each of the following directories. You can probably tell the difference between them by the file size.

/usr/lib/dri/i965_dri.so
/usr/lib32/dri/i965_dri.so
/usr/lib64/dri/i965_dri.so

If you get a wrong ELF class error, try using a different i965_dri.so in /usr/lib32/dri/

At least that is what I would try.

---------- Post added at 10:59 PM ---------- Previous post was at 10:48 PM ----------

Just booted back into Fedora. This is what I have for mesa. I am strictly 64-bit. Looking in Add/Remove Software I only see the 64-bit mesa libraries available for my system.

Code:

[root@localhost ~]# rpm -qa | grep mesa | sort
mesa-dri-drivers-8.0.3-1.fc17.x86_64
mesa-dri-filesystem-8.0.3-1.fc17.x86_64
mesa-libGL-8.0.3-1.fc17.i686
mesa-libGL-8.0.3-1.fc17.x86_64
mesa-libglapi-8.0.3-1.fc17.i686
mesa-libglapi-8.0.3-1.fc17.x86_64
mesa-libGLU-8.0.3-1.fc17.i686
mesa-libGLU-8.0.3-1.fc17.x86_64
mesa-libxatracker-8.0.3-1.fc17.x86_64
[root@localhost ~]#

You have both 32-bit and 64-bit mesa installed. Not sure how you did that. Was yours an upgrade install or clean install? I used a clean install here.

EDIT: Looking again at my output in Terminal there do appear to be some 32-bit mesa rpms there. Not all that you have though.

hmmmmmmmmm

Code:

$ls -l /usr/
total 304
dr-xr-xr-x.   2 root root  69632 Jun 18 21:29 bin
drwxr-xr-x.   2 root root   4096 Feb  3 02:28 etc
drwxr-xr-x.   2 root root   4096 Feb  3 02:28 games
drwxr-xr-x. 106 root root  12288 Jun 18 21:36 include
dr-xr-xr-x.  57 root root  20480 Jun 18 21:31 lib
lrwxrwxrwx.   1 root root     11 Jun 18 23:30 lib32 -> /usr/lib64/
dr-xr-xr-x. 187 root root 135168 Jun 18 21:36 lib64
drwxr-xr-x.  34 root root  12288 Jun 18 20:25 libexec
drwxr-xr-x.  13 root root   4096 May 20 07:29 local
dr-xr-xr-x.   2 root root  20480 Jun 18 20:26 sbin
drwxr-xr-x. 331 root root  12288 Jun 16 12:51 share
drwxr-xr-x.   7 root root   4096 Jun 18 20:20 src
lrwxrwxrwx.   1 root root     10 Apr 10 21:21 tmp -> ../var/tmp
$ glxinfo | grep direct
direct rendering: Yes

wat the heck is going on. symlinking lib64 to lib 32 fixes the problem. What the heck.

now i have to figure out this other problem with wine later since it is not fixed

---------- Post added 19th June 2012 at 05:43 AM ---------- Previous post was 18th June 2012 at 11:33 PM ----------

now i realize my problem i was trying to symlink 32 libraries but i symlink the wrong thing

i added

Code:

export LIBGL_DRIVERS_PATH=/usr/lib32/dri

which i later removed show stupid of me oh well i guess i solved it

esbennn · #12 25th June 2012, 05:38 PM

Quote:

now i realize my problem i was trying to symlink 32 libraries but i symlink the wrong thing

i added

Code:

export LIBGL_DRIVERS_PATH=/usr/lib32/dri

which i later removed show stupid of me oh well i guess i solved it

Hi there!
I am having this problem as well on fresh f17 x64 box.

Not quite sure what you actually did in the end to fix this?
I'd much appreciate it if you'd explain it, since i would very much like to mash up some cars and pedestrians in Carmageddon 2

I tried the

Code:

 export LIBGL_DRIVERS_PATH=/usr/lib32/dri

before i found this post, but that obviously didn't work for me.

Thanks!