Re: [blfs-support] AIGLX: Screen 0 is not DRI2 capable
On 06/29/2012 10:23 AM, Omar wrote: > Thanks Armin. > I've fixed the errors which you pointed. The following is the status now. > > >>> libGL: screen 0 does not appear to be DRI2 capable >>> libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so >>> libGL: Can't open configuration file /etc/drirc: No such file or >> directory. >>> libGL: Can't open configuration file /root/.drirc: No such file or >> directory. >>> .. >>> [ 962.866] (II) AIGLX: Screen 0 is not DRI2 capable >>> [ 962.867] (II) AIGLX: Screen 0 is not DRI capable >>> [ 962.908] (II) AIGLX: Loaded and initialized swrast > > The messages above is still there. I extract some new messages I consider > important below. > > [24.861] (WW) vmware(0): Disabling 3D support. > [24.861] (WW) vmware(0): Disabling Render Acceleration. > [24.861] (WW) vmware(0): Disabling RandR12+ support. > [24.862] (--) vmware(0): VMware SVGA regs at (0x10d0, 0x10d1) > ... > [25.096] (II) vmware(0): Not using default mode "320x175" (bad mode > clock/interlace/doublescan) > ... > [25.133] (II) UnloadModule: "vesa" > [25.133] (II) Unloading vesa > [25.133] (II) UnloadModule: "fbdev" > [25.133] (II) Unloading fbdev > [25.133] (II) UnloadSubModule: "fbdevhw" > [25.133] (II) Unloading fbdevhw > > I will find them in kernel again. > Omar > If you are using any kernel before 3.3, you should take a look at "Staging Drivers" in Drivers subtree of kernel. There is "Driver for VMware Virtual GPU" or whatever (CONFIG_DRM_VMWGFX config option). I would suggest that you build it as module, because I haven't tried it the other way. Other thing is that you need 3D capable video card and drivers on your host, 3D switch needs to be enabled in virtual machine configuration section. And at last, for better 3D support use Player 4.0 or Workstation 8.0. There is also 3D support in Player 3.1/Workstation 7.1, but first one is lot better. And if everything else fails, I'd try newer kernel, presumably 3.4 one, but I think that 3.2 should work good enough. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] AIGLX: Screen 0 is not DRI2 capable
On 06/29/2012 12:44 PM, Ken Moffat wrote: > On Fri, Jun 29, 2012 at 10:29:41AM +0800, Omar wrote: >> Just attachment of this mail. >> > If you need to compress a large file to attach it, use a linux > compressor - 99% of people here cannot open rar files. In this > case, I don't think we need it. >> Luckily I had unrar installed when I updated it in the book, but I am strongly against using it in Linux based stuff. Zip could be ok since most of us may already have it if building mozilla products or such, but not rar. >>> Thank you all. >>> 1. My environment is based on LFS7.1 on VMware. > > Google thinks you need the correct options when building Mesa. > According to debian bug 652501 you need the svga gallium driver. > That driver is enabled in the book's instructions for Mesa. > > ĸen > To be more specific, you need gallium svga driver AND libxatracker (--enable-xa in Mesa instructions). That is already enabled in default Mesa instructions in BLFS, and Xorg VMware driver will pick it up. But, you need vmwgfx kernel driver, which is now in the place as the other DRM drivers in kernel, but is in staging area in pre 3.3 kernels. It is not enabled by default tough in any case. And the last point is ... Your host system needs to have working 3D stuff. On windows host, any DirectX9 capable card should work very well, including some newer i915, possibly r200 ones and geforce4 or better. ones. I had hard time getting 3D acceleration to work on Linux hosts and Intel card. It wouldn't be of any problem with propretary ATI or NVidia, but since intel is open source, and VMware player needs s3tc GL extension which is patented by SIS so Mesa devs can't integrate it in Mesa source tree. There is however external library at freedesktop.org for that, and I just got that last night after few months of giving up on 3d in vmware! I guess same thing would be needed for open source radeon and nouveau drivers. Also, for good 3D support, you need at least Player 4.0 or Workstation 8.0. There is some 3D support in Player 3.1/Workstation 7.1, but not that good. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] AIGLX: Screen 0 is not DRI2 capable
Armin K. wrote: > On 06/28/2012 09:17 PM, Bruce Dubbs wrote: >> I also get all of these with nouveau except the i945 line. >> > > Sure, you get nouveau or nouveau_vieux there, that line says which DRI > driver is loaded. I don't see that. I do see: (II) NOUVEAU(0): [DRI2] DRI driver: nouveau (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau ... (II) AIGLX: Loaded and initialized nouveau (II) GLX: Initialized DRI2 GL provider for screen 0 >> I'm not seeing swrast at all, but I am quite disappointed in the nouveau >> performance. For glxgears, it get about 250 frames/sec. On the same >> HW using a very old nvidia proprietary driver I get about 8700 fps. >> glxgears may not be a great benchmark, but a 35-1 speed ratio means >> something. > If you are using nouveau from BLFS with newer NVidia chipset, you might > want to try latest libdrm, mesa 8.1 git checkout and nouveau 1.0.1 with > Kernel 3.4. I will try that as soon as I get the monitor issue straightened out. Right now I only get two cloned 1920x1200 screens instead of a single integrated 3840x1200 screen. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] AIGLX: Screen 0 is not DRI2 capable
On 06/28/2012 09:17 PM, Bruce Dubbs wrote: > > I also get all of these with nouveau except the i945 line. > Sure, you get nouveau or nouveau_vieux there, that line says which DRI driver is loaded. > I'm not seeing swrast at all, but I am quite disappointed in the nouveau > performance. For glxgears, it get about 250 frames/sec. On the same > HW using a very old nvidia proprietary driver I get about 8700 fps. > glxgears may not be a great benchmark, but a 35-1 speed ratio means > something. > > -- Bruce > If you are using nouveau from BLFS with newer NVidia chipset, you might want to try latest libdrm, mesa 8.1 git checkout and nouveau 1.0.1 with Kernel 3.4. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] AIGLX: Screen 0 is not DRI2 capable
Armin K. wrote: > On 06/28/2012 06:13 PM, Bruce Dubbs wrote: >> IIRC R128 can do DRI. Sometimes the monitor isn't capable though. >> >> Looking at my recent work with the nouveau driver, the text 'rendering' >> is not mentioned in Xorg.0.log, although glxinfo does have "direct >> rendering: Yes". > If I am not wrong, lot of DRI drivers were dropped from Mesa 8.0 that > were available in Mesa 7.11, including the r128 one. On recent Xorg > server, message is like the following: > > [ 12475.942] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer > [ 12475.942] (II) AIGLX: enabled GLX_INTEL_swap_event > [ 12475.942] (II) AIGLX: enabled GLX_SGI_swap_control and > GLX_MESA_swap_control > [ 12475.942] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer > objects > [ 12475.942] (II) AIGLX: Loaded and initialized i965 > [ 12475.942] (II) GLX: Initialized DRI2 GL provider for screen 0 I also get all of these with nouveau except the i945 line. > So no direct rendering message. Also, I think that if you use swrast you > will still have direct rendering set as yes in glxinfo, but you will be > using software emulation. I'm not seeing swrast at all, but I am quite disappointed in the nouveau performance. For glxgears, it get about 250 frames/sec. On the same HW using a very old nvidia proprietary driver I get about 8700 fps. glxgears may not be a great benchmark, but a 35-1 speed ratio means something. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] AIGLX: Screen 0 is not DRI2 capable
On Thu, Jun 28, 2012 at 12:51:22PM +0200, Armin K. wrote: > On 06/28/2012 11:26 AM, Omar wrote: > > Hi all, > > When checking DRI from /var/log/Xorg.0.log in section "Xorg-7.7-1 Testing > > and Configuration" I can't find messages like "(II) R128(0): Direct > > rendering enabled" and "(II) intel(0): direct rendering: DRI2 Enabled". The > > log just tells me that > > > > " > > Load Module DRI2... > > Load Module DRI... > > . > > > > [26.680] (II) AIGLX: Screen 0 is not DRI2 capable > > [26.680] (II) AIGLX: Screen 0 is not DRI capable > > [...] > > Alright, I think Ken or Andy asked same question about direct rendering. > Turned out they weren't members of "video" group. Check if your user is > member of that group by running "groups" as that user. If not, add > yourself to the video group and log in again. Another possibility might > be older card. I see you mention r128, and that driver is old and I > think there isn't any DRI driver for it in Mesa 8.0. There is DRI driver > tough, in Kernel - Drivers - Graphics - Direct Rendering or something > like that. If all fails, you can post whole Xorg.0.log so we could check > it out. Yes, it was me and that solved the problem on my old radeon r200. If I'm reading Omar correctly, he hasn't said *what* video card he is using (nor which video driver). They are key to this. The 'R128' is what the book gives as an example. Perhaps we should suggest a different test, to be run from an xterm or similar. Neither of these will help diagnose Omar's problem, but we could use $glxinfo | grep renderer (software rendering means DRI, not DRI2), or just report on AIGLX $grep AIGLX /var/log/Xorg.0.log Wikipedia suggests that AIGLX depends on the xorg video driver - ati (radeon), intel (i810 and later) and nouveau should work, others might not. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] AIGLX: Screen 0 is not DRI2 capable
On 06/28/2012 06:13 PM, Bruce Dubbs wrote: > > IIRC R128 can do DRI. Sometimes the monitor isn't capable though. > > Looking at my recent work with the nouveau driver, the text 'rendering' > is not mentioned in Xorg.0.log, although glxinfo does have "direct > rendering: Yes". > > -- Bruce > If I am not wrong, lot of DRI drivers were dropped from Mesa 8.0 that were available in Mesa 7.11, including the r128 one. On recent Xorg server, message is like the following: [ 12475.942] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 12475.942] (II) AIGLX: enabled GLX_INTEL_swap_event [ 12475.942] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 12475.942] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 12475.942] (II) AIGLX: Loaded and initialized i965 [ 12475.942] (II) GLX: Initialized DRI2 GL provider for screen 0 So no direct rendering message. Also, I think that if you use swrast you will still have direct rendering set as yes in glxinfo, but you will be using software emulation. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] AIGLX: Screen 0 is not DRI2 capable
Armin K. wrote: > On 06/28/2012 11:26 AM, Omar wrote: >> Hi all, When checking DRI from /var/log/Xorg.0.log in section >> "Xorg-7.7-1 Testing and Configuration" I can't find messages like >> "(II) R128(0): Direct rendering enabled" and "(II) intel(0): direct >> rendering: DRI2 Enabled". The log just tells me that >> >> " Load Module DRI2... Load Module DRI... . >> >> [26.680] (II) AIGLX: Screen 0 is not DRI2 capable [26.680] >> (II) AIGLX: Screen 0 is not DRI capable >> >> " I considered whether it was the problem of kernel but I can't >> find any kernel options about AIGLX. >> >> (I can start up xinit, xterm and xclock now.) Thanks in advance for >> any suggestions. >> >> >> BTW, in the part "Setting up X Input Devices" whether it is a >> mistake in writing about "/etc/X11/xorg.conf.d/xkb-defaults.conf" >> and so on. I remember "/etc/X11" is the symbolic link to >> "/usr/share/X11/xorg.conf.d", then it could be >> "/etc/X11/xkb-defaults.conf", right? Omar >> > > Alright, I think Ken or Andy asked same question about direct > rendering. Turned out they weren't members of "video" group. Check if > your user is member of that group by running "groups" as that user. > If not, add yourself to the video group and log in again. Another > possibility might be older card. I see you mention r128, and that > driver is old and I think there isn't any DRI driver for it in Mesa > 8.0. There is DRI driver tough, in Kernel - Drivers - Graphics - > Direct Rendering or something like that. If all fails, you can post > whole Xorg.0.log so we could check it out. IIRC R128 can do DRI. Sometimes the monitor isn't capable though. Looking at my recent work with the nouveau driver, the text 'rendering' is not mentioned in Xorg.0.log, although glxinfo does have "direct rendering: Yes". -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] AIGLX: Screen 0 is not DRI2 capable
On 06/28/2012 11:26 AM, Omar wrote: > Hi all, > When checking DRI from /var/log/Xorg.0.log in section "Xorg-7.7-1 Testing and > Configuration" I can't find messages like "(II) R128(0): Direct rendering > enabled" and "(II) intel(0): direct rendering: DRI2 Enabled". The log just > tells me that > > " > Load Module DRI2... > Load Module DRI... > . > > [26.680] (II) AIGLX: Screen 0 is not DRI2 capable > [26.680] (II) AIGLX: Screen 0 is not DRI capable > > " > I considered whether it was the problem of kernel but I can't find any kernel > options about AIGLX. > > (I can start up xinit, xterm and xclock now.) Thanks in advance for any > suggestions. > > > BTW, in the part "Setting up X Input Devices" whether it is a mistake in > writing about "/etc/X11/xorg.conf.d/xkb-defaults.conf" and so on. I remember > "/etc/X11" is the symbolic link to "/usr/share/X11/xorg.conf.d", then it > could be "/etc/X11/xkb-defaults.conf", right? > Omar > Alright, I think Ken or Andy asked same question about direct rendering. Turned out they weren't members of "video" group. Check if your user is member of that group by running "groups" as that user. If not, add yourself to the video group and log in again. Another possibility might be older card. I see you mention r128, and that driver is old and I think there isn't any DRI driver for it in Mesa 8.0. There is DRI driver tough, in Kernel - Drivers - Graphics - Direct Rendering or something like that. If all fails, you can post whole Xorg.0.log so we could check it out. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] AIGLX: Screen 0 is not DRI2 capable
Hi all, When checking DRI from /var/log/Xorg.0.log in section "Xorg-7.7-1 Testing and Configuration" I can't find messages like "(II) R128(0): Direct rendering enabled" and "(II) intel(0): direct rendering: DRI2 Enabled". The log just tells me that " Load Module DRI2... Load Module DRI... . [ 26.680] (II) AIGLX: Screen 0 is not DRI2 capable [ 26.680] (II) AIGLX: Screen 0 is not DRI capable " I considered whether it was the problem of kernel but I can't find any kernel options about AIGLX. (I can start up xinit, xterm and xclock now.) Thanks in advance for any suggestions. BTW, in the part "Setting up X Input Devices" whether it is a mistake in writing about "/etc/X11/xorg.conf.d/xkb-defaults.conf" and so on. I remember "/etc/X11" is the symbolic link to "/usr/share/X11/xorg.conf.d", then it could be "/etc/X11/xkb-defaults.conf", right? Omar -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
