Re: [gentoo-user] Question regarding VIDEO_CARDS and unrelated question regarding USE flags
Alex Schuster wrote: direct rendering: Yes Great! I thought OpenGL support were better? And there is power saving. Although I have an onboard card, so I would not have a loud spinning fan. Well, the drivers I use (ati-drivers-8.552-r2) are working perfectly (in combination with my current kernel, gentoo-sources-2.6.25-r9) for all the applications that I have installed/use on my machine. Stability is an issue for me and until the open source driver has matured I will stay with this. I have no need for opengl 3+ currently as no applications that I have installed support it. Thanks! But you motivated me to give the new drivers a try. Ah, well, that's something at least... :-) Okay, I just did it. Emerged ati-drivers 9.7. Got a locked display, but after a reboot, all is fine. Wow! Maybe the problem last time was that I tried 9.6, or I did not reboot. Whatever. Well, X drivers has some bits that needs to be synchronised: a kernel space glue (DRM module) and the user space X driver. So if you have upgraded you need to kill X, unload the old kernel module and load the new one, start X again. If you didn't know this already... Thanks again, I needed a little kick. Bitte schön! MfG Peter K
Re: [gentoo-user] Question regarding VIDEO_CARDS and unrelated question regarding USE flags
pk writes: Alex Schuster wrote: So what modules does get loaded? All from your modules section (except for type1), an in total these: glx, extmod, dri, dbe, record, fglrx, kbd, mouse, vgahw, int10, vbe, fglrxdrm, ddc, fb, ramdac, xaa, fglrxdrm, glesx, amdxmm I know this command from when I had a NVidia card, and I am missing the 'YES' in my output of fglrxinfo. But I do not have a 'NO' there either. fglrxinfo is different from glxinfo. glxinfo is available in the mesa-progs package (emerging this will pull in mesa as well but there's no harm in that, unless you are tight on hard drive space - just make sure you shift back to ati opengl after emerging). Ah, I see. Didn't know about mesa-progs. Mesa is already installed, and space is really no concern here. The output of glxinfo looks good: name of display: :0.0 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_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe, GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer 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_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_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: ATI Radeon HD 3200 Graphics OpenGL version string: 2.1.8201 Release OpenGL shading language version string: 1.20 OpenGL extensions: GL_AMD_performance_monitor, GL_ARB_color_buffer_float, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_instanced, GL_ARB_fragment_program, GL_ARB_fragment_shader, GL_ARB_half_float_pixel,
Re: [gentoo-user] Question regarding VIDEO_CARDS and unrelated question regarding USE flags
pk writes: Alex Schuster wrote: I have a Radeon HD 3200 and I am using ati-drivers-8.552-r2. Higher versions did not compile. My kernel is 2.6.28-tuxonice-r3, and with newer kernels I was not able to build any ati-drivers at all. That was a while ago. I tried ati-drivers-9.6 a month ago when that came out, and I don't remember what exactly happened, it compiled but it didn't work either. I'm also using ati-drivers-8.552-r2, but with gentoo-sources-2.6.25-r9 (I usually skip one kernel release but .27 was initally riddled with problems so I skipped it and, well, I will probably not upgrade until I hear good news with regards to the open source drivers and the related kernel changes - maybe .32?)... I really don't know anything about tuxonice kernels, other than it's patches maintained out-of-tree with support for suspend-to-disk. I know that there has been problems with the suspend in the mainline but again I don't know if tuxonice is affected. As an experiment, you could try a vanilla or gentoo-sources kernel with the ati-drivers to see if that alleviates the problems you are having. I had tried vanilla-sources, with the same results. As expected, there should not be much of a difference. I am not using tuxonice suspend features, but I intend to do so in the future. fgl_glxgears sort of runs, with 135-170 FPS, but the graphics is distorted - see http://wonkology.org/~wonko/tmp/fgl_glxgears.png . Other OpenGL software Have you tried different settings in xorg.conf? No, I did not yet take the time to investigate this further. So many other problems :) I have this in mine (only the - maybe - relevant stuff shown): ... Section Module Load glx Load extmod Load dri Load dbe Load type1 EndSection Section dri Group 27# video Mode 0660 EndSection Section Device Identifier Card0 Driver fglrx VendorName ATI Technologies Inc BoardName Unknown Board Option mtrr off # === OpenGL specific profiles/settings === Option Capabilities 0x # === Video Overlay for the Xv extension === Option VideoOverlay on Option OpenGLOverlay off Option CenterMode off Option PseudoColorVisuals off Option Stereo off Option StereoSyncEnable 1 Option UseFastTLS 0 Option BlockSignalsOnLock on Option UseInternalAGPGART no Option ForceGenericCPUno Screen 0 EndSection ... Of course, my settings may be different from your needs. I added your stuff, that did not make much of a difference. I had an empty modules sections, but all of these modules are loaded by default. Except for type1, which does not exist. No idea where this comes from, maybe it's not even related to OpenGL, but ip_firegl_write looks like it might be. Well, I'm no expert but fglrx may be incompatible with tuxonice... I read there were at least some problems, but only related to hibernating, not using OpenGL. And Xorg.0.log shows these lines: (EE) AIGLX error: fglrx exports no extensions (/usr/lib/dri/fglrx_dri.so: undefined symbol: __driDriverExtensions) (EE) AIGLX: reverting to software rendering As far as I can tell it seems like it's reverting to software rendering, maybe for the AIGLX extension or maybe for all rendering... Does that mean I do not have hardware opengl rendering? fglrxinfo shows: Try: glxinfo | grep -i direct You should get: direct rendering: Yes ...if you have hardware opengl. I know this command from when I had a NVidia card, and I am missing the 'YES' in my output of fglrxinfo. But I do not have a 'NO' there either. CPU usage gets rather high, but not to 100 percent, as I would expect when it does all the rendering itself. But, where does glxinfo come from? I do not have it. I thought it's in the drivers package, like nvidia-drivers, and in case of ati-drivers it's called a little different. I also found this: http://bugs.gentoo.org/176441 It's for older ati-drivers but identical error message... Although the symbol being missed is a different one. I hope with the newer drivers (and perhaps a newer kernel) things will become better. I did not yet take the time to investigate this further. I've heard that newer kernels (=2.6.29?) are not working with ati-drivers. Not sure if this has been alleviated... I thought I read here that they do, but may give lots of warnings in syslog. I hope to have some free time this weekend, so I can try to the newer drivers. I really like to test the KDE4 desktop effects :) Wonko
Re: [gentoo-user] Question regarding VIDEO_CARDS and unrelated question regarding USE flags
Alex Schuster wrote: I had tried vanilla-sources, with the same results. As expected, there should not be much of a difference. I am not using tuxonice suspend features, but I intend to do so in the future. Hm, ok. I added your stuff, that did not make much of a difference. I had an empty modules sections, but all of these modules are loaded by default. Except for type1, which does not exist. Yea, type 1 is a left over from old days... :-) So what modules does get loaded? I know this command from when I had a NVidia card, and I am missing the 'YES' in my output of fglrxinfo. But I do not have a 'NO' there either. fglrxinfo is different from glxinfo. glxinfo is available in the mesa-progs package (emerging this will pull in mesa as well but there's no harm in that, unless you are tight on hard drive space - just make sure you shift back to ati opengl after emerging). Although the symbol being missed is a different one. Sorry, I didn't read properly... I thought I read here that they do, but may give lots of warnings in syslog. Well, I'm holding out for the open source drivers... There's nothing in newer fglrx drivers that I need currently. I wish I could be of more help though...
Re: [gentoo-user] Question regarding VIDEO_CARDS and unrelated question regarding USE flags
pk writes: Alex Schuster wrote: Oh, I just see that on my desktop machine xorg-server already got re- compiled without fglrx. I see no adverse effects yet, but then OpenGL never worked really well here. As I understand it the VIDEO_CARDS parameters (fglrx, radeon, etc.) only controls what drivers should be pulled in when building xorg. So it should not matter much; I'm just curious as to why it's removed from the flags when for instance nvidia is still there... Out of curiousity, what doesn't work for you with regards to OpenGL? For me almost all fglrx drivers have worked flawlessly for years. I'm hoping to migrate to the open source radeon driver as soon as it's stable with my current chip (rv670 - radeon 3870). I have a Radeon HD 3200 and I am using ati-drivers-8.552-r2. Higher versions did not compile. My kernel is 2.6.28-tuxonice-r3, and with newer kernels I was not able to build any ati-drivers at all. That was a while ago. I tried ati-drivers-9.6 a month ago when that came out, and I don't remember what exactly happened, it compiled but it didn't work either. fgl_glxgears sort of runs, with 135-170 FPS, but the graphics is distorted - see http://wonkology.org/~wonko/tmp/fgl_glxgears.png . Other OpenGL software seems to work without artifacts, though, at least Quake3 and some screen savers. But when playing around with things like Quake3, I get X crashes sometimes, and am able to switch to another virtual terminal only after pressing Alt-SysRq-R. And only for one time, if I try that application again and get another crash, even the SysRq trick does not help and I have to reboot. Then there is stuff like this in dmesg: BUG: using smp_processor_id() in preemptible [] code: X/13807 caller is KAS_GetExecutionLevel+0xb/0xb7 [fglrx] Pid: 13807, comm: X Tainted: P 2.6.28-tuxonice-r3_3 #19 Call Trace: [c01dec0c] debug_smp_processor_id+0xa0/0xb4 [f9dd75fd] KAS_GetExecutionLevel+0xb/0xb7 [fglrx] [f9df2e87] MCIL_GetExecutionLevel+0x47/0x90 [fglrx] [f9ea3e5f] RegisterIRQClient+0x5f/0x1a0 [fglrx] [f9eac4b0] ReInitializeHotPlugCallback+0x0/0x30 [fglrx] [f9ea0e9c] IRQMGR_IRQSourceSupported+0x6c/0x80 [fglrx] [f9ea42e1] ValidateIRQMgrAccess+0x31/0x200 [fglrx] [f9ea0660] IRQMGR_Access+0xd0/0x160 [fglrx] [f9e0bb20] fireglAsyncioUnregisterIntMsgHandlers+0x460/0x4f0 [fglrx] [f9ea0e9c] IRQMGR_IRQSourceSupported+0x6c/0x80 [fglrx] [f9e0b855] fireglAsyncioUnregisterIntMsgHandlers+0x195/0x4f0 [fglrx] [f9e0bb20] fireglAsyncioUnregisterIntMsgHandlers+0x460/0x4f0 [fglrx] [f9e46d69] asyncIONotifyMsg+0x339/0x3c0 [fglrx] [c03096a9] _spin_unlock_irqrestore+0xe/0x21 [f9e0a251] asyncioSvcRecvFn+0xd1/0x1c0 [fglrx] [f9e46c74] asyncIONotifyMsg+0x244/0x3c0 [fglrx] [f9e0ae1d] firegl_asyncio_write+0x1ad/0x290 [fglrx] [c018adc1] vfs_ioctl+0x50/0x5f [f9dda1ed] ip_firegl_write+0x2b/0x4f [fglrx] [f9dda1c2] ip_firegl_write+0x0/0x4f [fglrx] [c0181693] vfs_write+0x84/0x121 [c01817c8] sys_write+0x3c/0x63 [c0102dd9] sysenter_do_call+0x12/0x21 No idea where this comes from, maybe it's not even related to OpenGL, but ip_firegl_write looks like it might be. And Xorg.0.log shows these lines: (EE) AIGLX error: fglrx exports no extensions
Re: [gentoo-user] Question regarding VIDEO_CARDS and unrelated question regarding USE flags
Alex Schuster wrote: I have a Radeon HD 3200 and I am using ati-drivers-8.552-r2. Higher versions did not compile. My kernel is 2.6.28-tuxonice-r3, and with newer kernels I was not able to build any ati-drivers at all. That was a while ago. I tried ati-drivers-9.6 a month ago when that came out, and I don't remember what exactly happened, it compiled but it didn't work either. I'm also using ati-drivers-8.552-r2, but with gentoo-sources-2.6.25-r9 (I usually skip one kernel release but .27 was initally riddled with problems so I skipped it and, well, I will probably not upgrade until I hear good news with regards to the open source drivers and the related kernel changes - maybe .32?)... I really don't know anything about tuxonice kernels, other than it's patches maintained out-of-tree with support for suspend-to-disk. I know that there has been problems with the suspend in the mainline but again I don't know if tuxonice is affected. As an experiment, you could try a vanilla or gentoo-sources kernel with the ati-drivers to see if that alleviates the problems you are having. fgl_glxgears sort of runs, with 135-170 FPS, but the graphics is distorted - see http://wonkology.org/~wonko/tmp/fgl_glxgears.png . Other OpenGL software Have you tried different settings in xorg.conf? I have this in mine (only the - maybe - relevant stuff shown): ... Section Module Load glx Load extmod Load dri Load dbe Load type1 EndSection Section dri Group 27# video Mode 0660 EndSection Section Device Identifier Card0 Driver fglrx VendorName ATI Technologies Inc BoardName Unknown Board Option mtrr off # === OpenGL specific profiles/settings === Option Capabilities 0x # === Video Overlay for the Xv extension === Option VideoOverlay on Option OpenGLOverlay off Option CenterMode off Option PseudoColorVisuals off Option Stereo off Option StereoSyncEnable 1 Option UseFastTLS 0 Option BlockSignalsOnLock on Option UseInternalAGPGART no Option ForceGenericCPUno Screen 0 EndSection ... Of course, my settings may be different from your needs. No idea where this comes from, maybe it's not even related to OpenGL, but ip_firegl_write looks like it might be. Well, I'm no expert but fglrx may be incompatible with tuxonice... And Xorg.0.log shows these lines: (EE) AIGLX error: fglrx exports no extensions (/usr/lib/dri/fglrx_dri.so: undefined symbol: __driDriverExtensions) (EE) AIGLX: reverting to software rendering As far as I can tell it seems like it's reverting to software rendering, maybe for the AIGLX extension or maybe for all rendering... Does that mean I do not have hardware opengl rendering? fglrxinfo shows: Try: glxinfo | grep -i direct You should get: direct rendering: Yes ...if you have hardware opengl. I also found this: http://bugs.gentoo.org/176441 It's for older ati-drivers but identical error message... I hope with the newer drivers (and perhaps a newer kernel) things will become better. I did not yet take the time to investigate this further. I've heard that newer kernels (=2.6.29?) are not working with ati-drivers. Not sure if this has been alleviated... Could be other problems as well, of course... Best regards Peter K
[gentoo-user] Question regarding VIDEO_CARDS and unrelated question regarding USE flags
Hi, When I sync'ed a couple of days ago I got this: x ~ # emerge --with-bdeps y -DupN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] x11-base/xorg-server-1.5.3-r6 VIDEO_CARDS=(-fglrx%*) [ebuild R ] media-libs/alsa-lib-1.0.19 USE=(-midi%*) [ebuild U ] media-libs/libmikmod-3.1.11-r5 [3.1.11-r4] [ebuild R ] media-sound/alsa-tools-1.0.19 USE=-midi* [ebuild R ] media-sound/alsa-utils-1.0.19-r2 USE=(-midi%*) [ebuild R ] media-sound/audacity-1.3.7 USE=-midi* Q1. Does anyone know why the ebuild for xorg-server no longer have the fglrx flag (nvidia is present) available? Q2. Does anyone know why midi USE flag is no longer used? I've tried to google it, both general search and via gentoo mail list archives. Though my google skills may not be the best... Best regards Peter K
Re: [gentoo-user] Question regarding VIDEO_CARDS and unrelated question regarding USE flags
pk writes: x ~ # emerge --with-bdeps y -DupN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] x11-base/xorg-server-1.5.3-r6 VIDEO_CARDS=(-fglrx%*) [ebuild R ] media-libs/alsa-lib-1.0.19 USE=(-midi%*) [ebuild U ] media-libs/libmikmod-3.1.11-r5 [3.1.11-r4] [ebuild R ] media-sound/alsa-tools-1.0.19 USE=-midi* [ebuild R ] media-sound/alsa-utils-1.0.19-r2 USE=(-midi%*) [ebuild R ] media-sound/audacity-1.3.7 USE=-midi* Q1. Does anyone know why the ebuild for xorg-server no longer have the fglrx flag (nvidia is present) available? No. I noticed this yesterday, and skipped re-compiling of xorg-server, just in case. Oh, I just see that on my desktop machine xorg-server already got re- compiled without fglrx. I see no adverse effects yet, but then OpenGL never worked really well here. Q2. Does anyone know why midi USE flag is no longer used? There is http://bugs.gentoo.org/show_bug.cgi?id=272659 , although it does not really explain why midi is being dropped from ALSA. Wonko
Re: [gentoo-user] Question regarding VIDEO_CARDS and unrelated question regarding USE flags
Alex Schuster wrote: Oh, I just see that on my desktop machine xorg-server already got re- compiled without fglrx. I see no adverse effects yet, but then OpenGL never worked really well here. As I understand it the VIDEO_CARDS parameters (fglrx, radeon, etc.) only controls what drivers should be pulled in when building xorg. So it should not matter much; I'm just curious as to why it's removed from the flags when for instance nvidia is still there... Out of curiousity, what doesn't work for you with regards to OpenGL? For me almost all fglrx drivers have worked flawlessly for years. I'm hoping to migrate to the open source radeon driver as soon as it's stable with my current chip (rv670 - radeon 3870). There is http://bugs.gentoo.org/show_bug.cgi?id=272659 , although it does not really explain why midi is being dropped from ALSA. Found this: http://wonkabar.org/2009/08/02/alsa-cleanup-non-optional-midi-support-cleaner-confd/ ...not very much clearer but I left a comment/question on his blog. I'm just wondering what functionality gets lost... Thanks for the reply! Best regards Peter K
