FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have enabled 3d acceleration in VirtualBox and I'm using the 3d driver included with the guest additions.
I'm not sure knowing my graphics card would make much difference, that's all (sort of) abstracted away by VirtualBox, but for reference I'm using an nVidia GeForce 9400GT and the proprietary nvidia drivers. 3d works perfectly well for the host (Ubuntu 10.04 LTS), and it works for one of my other guests (Ubuntu 10.10). All are 64bit
also fedora IS NOT anywhere like Ubuntu and dose things VERY differently ( apples and oranges ) \
also if you do NOT use the nvidia rpm in the fedora repos and use the .run ( from the nvidia web site) you will also need to REINSTALL ALL of mesa and mesa-devel
the .run overwrites some fedora system files AND SOURCE HEADER FILES , these need to be fixed otherwise you WILL get opengl segfaults
Why would I use any nvidia driver in a VirtualBox guest? Fedora doesn't know about my nvidia card. All it sees is the one emulated by VirtualBox, and I'm using the vboxvideo X driver. Fedora describes the emulated graphics chip as
My first post may seem lacking in information to the casual observer, but VirtualBox only emulates one graphics device, and the X drivers are part of the guest additions, so in fact all the information is there. I mentioned dkms, because there is a bug the old fallback method in that sym links to VBoxOGL.so aren't correctly setup.
JohnVV, while I appreciate your efforts to help, you seem to have glossed over the fact that I'm running Fedora in a virtual machine. This nugget of information is quite significant, and changes the problem space somewhat.
I was in 2 minds whether to post here, or in the Virtualisation forum, I decided here because it seems to be a problem with Fedora, rather than the virtualisation solution I'm using.
[ 191.046] (**) AIGLX enabled
...
[ 191.512] (II) [drm] DRM interface version 1.3
[ 191.512] (II) [drm] DRM open master succeeded.
...
[ 191.557] (EE) AIGLX error: vboxvideo does not export required DRI extension
[ 191.561] (EE) AIGLX: reverting to software rendering
[ 191.567] (II) AIGLX: Loaded and initialized /usr/lib64/dri/swrast_dri.so
[ 191.567] (II) GLX: Initialized DRISWRAST GL provider for screen 0
The 2 errors are somewhat misleading, both my Ubuntu and ArchLinux guest log the same errors, but 3d acceleration works fine for them.
I've done an update, which included:
Quote:
Dec 12 12:28:19 Updated: ibus-libs-1.3.9-1.fc14.x86_64
Dec 12 12:28:20 Updated: ibus-gtk2-1.3.9-1.fc14.x86_64
Dec 12 12:28:29 Updated: ibus-1.3.9-1.fc14.x86_64
Dec 12 12:28:32 Updated: xulrunner-1.9.2.13-1.fc14.x86_64
Dec 12 12:28:34 Updated: mesa-dri-drivers-7.9-4.fc14.x86_64
Dec 12 12:28:35 Updated: mesa-libGL-7.9-4.fc14.x86_64
Dec 12 12:28:35 Updated: gnome-python2-extras-2.25.3-26.fc14.1.x86_64
Dec 12 12:28:35 Updated: mesa-libGLU-7.9-4.fc14.x86_64
Dec 12 12:28:35 Updated: glx-utils-7.9-4.fc14.x86_64
Dec 12 12:28:36 Updated: gnome-python2-gtkhtml2-2.25.3-26.fc14.1.x86_64
Dec 12 12:28:36 Updated: gnome-python2-libegg-2.25.3-26.fc14.1.x86_64
Dec 12 12:28:36 Updated: ibus-gtk3-1.3.9-1.fc14.x86_64
Dec 12 12:28:37 Updated: openssl-1.0.0c-1.fc14.x86_64
Dec 12 12:28:38 Updated: 1:xorg-x11-font-utils-7.4-3.fc14.x86_64
Dec 12 12:28:42 Updated: firefox-3.6.13-1.fc14.x86_64
Dec 12 12:28:44 Updated: paktype-naqsh-fonts-3.0-4.fc14.noarch
Dec 12 12:28:45 Updated: paktype-tehreer-fonts-2.0-10.fc14.noarch
And I reinstalled the guest additions. Now running glxgears results in SIGILL (Illegal Instruction)
I'm getting permission denied on some ioctl calls to /dev/dri/card0. I am a member of the video group, and selinux is set to permissive. I'm not sure about those resource unavailable errors either. At that point in time fd 3 is a handle to /tmp/.X11-unix/X0
Quote:
[philip@boron ~]$ ls -l /dev/dri/card0
crw-rw----+ 1 root video 226, 0 Dec 12 13:40 /dev/dri/card0
[philip@boron ~]$ ls -l /tmp/.X11-unix/X0
srwxrwxrwx. 1 root root 0 Dec 12 13:40 /tmp/.X11-unix/X0
the SIGILL is generated from within a call in libGL:
Code:
Starting program: /usr/bin/glxgears
[Thread debugging using libthread_db enabled]
Program received signal SIGILL, Illegal instruction.
0x00007ffff7b443a7 in ?? () from /usr/lib64/libGL.so.1
(gdb) bt
#0 0x00007ffff7b443a7 in ?? () from /usr/lib64/libGL.so.1
#1 0x00007ffff7b45771 in ?? () from /usr/lib64/libGL.so.1
#2 0x00007ffff7b425a9 in ?? () from /usr/lib64/libGL.so.1
#3 0x00007ffff7b43556 in glXChooseVisual () from /usr/lib64/libGL.so.1
#4 0x0000000000402a37 in ?? ()
#5 0x0000003c57c1ee7d in __libc_start_main () from /lib64/libc.so.6
#6 0x00000000004017a9 in ?? ()
#7 0x00007fffffffe328 in ?? ()
#8 0x000000000000001c in ?? ()
#9 0x0000000000000001 in ?? ()
#10 0x00007fffffffe5f3 in ?? ()
#11 0x0000000000000000 in ?? ()
will post the stack trace again once I have the debuginfo rpms in.
(gdb) run
Starting program: /usr/bin/glxgears
[Thread debugging using libthread_db enabled]
Missing separate debuginfo for /usr/lib64/dri/vboxvideo_dri.so
Missing separate debuginfo for /usr/lib64/VBoxOGLcrutil.so
Missing separate debuginfo for /usr/lib64/VBoxOGLpackspu.so
Missing separate debuginfo for /usr/lib64/VBoxOGLerrorspu.so
Missing separate debuginfo for /usr/lib64/VBoxOGLfeedbackspu.so
Missing separate debuginfo for /usr/lib64/VBoxOGLpassthroughspu.so
Program received signal SIGILL, Illegal instruction.
__glXClientInfo (dpy=0x604010, opcode=154) at glxcmds.c:1286
1286 {
(gdb) bt
#0 __glXClientInfo (dpy=0x604010, opcode=154) at glxcmds.c:1286
#1 0x00007ffff7b45771 in __glXInitialize (dpy=0x604010) at glxext.c:865
#2 0x00007ffff7b425a9 in GetGLXPrivScreenConfig (dpy=0x604010, scrn=0, ppriv=0x7fffffffdf30,
ppsc=0x7fffffffdf28) at glxcmds.c:130
#3 0x00007ffff7b43556 in glXChooseVisual (dpy=0x604010, screen=0, attribList=0x7fffffffe100)
at glxcmds.c:1152
#4 0x0000000000402a37 in make_window (argc=<value optimized out>, argv=<value optimized out>)
at glxgears.c:515
#5 main (argc=<value optimized out>, argv=<value optimized out>) at glxgears.c:756
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.