Every time when I do emerge ati-drivers, I get following warning message: * Checking for DRM support disabled ... [ !! ] * You have DRM support enabled, the direct rendering * will not work. The message sounds quite confusing in case like mine, ie. when I use ATi DRM compiled as a module: CONFIG_DRM=m CONFIG_DRM_RADEON=m because as long as the module 'radeon' is not loaded, I can safely do modprobe fglrx and use ATi binary driver sucessfully Reproducible: Always Steps to Reproduce: 1. Configure and build kernel to use CONFIG_DRM=m and CONFIG_DRM_RADEON=m 2. emerge ati-drivers Actual Results: Ebuild complains about not working DRM. Expected Results: Ebuild should complain (or even hard fail) only if CONFIG_DRM=y and CONFIG_DRM_RADEON=y. I guess my emerge --info information is irrevelant in this case.
Wrong, the fglrx module won't work if there DRM support is enable, even if is enable as module.
It *does* work, as long as 'radeon' module is _not inserted_ before 'fglrx' module: 026 ~ # lsmod Module Size Used by fglrx 252064 7 via686a 17304 0 i2c_sensor 2944 1 via686a i2c_isa 2048 0 i2c_core 17040 3 via686a,i2c_sensor,i2c_isa snd_seq_midi 6944 0 snd_emu10k1_synth 6912 0 snd_emux_synth 34560 1 snd_emu10k1_synth snd_seq_virmidi 5888 1 snd_emux_synth snd_seq_midi_emul 6912 1 snd_emux_synth snd_emu10k1 114724 3 snd_emu10k1_synth snd_rawmidi 20640 3 snd_seq_midi,snd_seq_virmidi,snd_emu10k1 snd_ac97_codec 80636 1 snd_emu10k1 snd_util_mem 3456 2 snd_emux_synth,snd_emu10k1 snd_hwdep 7072 2 snd_emux_synth,snd_emu10k1 via_agp 7680 1 agpgart 28616 2 fglrx,via_agp pl2303 18820 0 usbserial 27240 1 pl2303 fuse 32652 0 026 ~ # fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON 9600 Generic OpenGL version string: 1.3.5395 (X4.3.0-8.18.6) 026 ~ # cat /var/log/Xorg.0.log | grep DRI (II) Loading extension XFree86-DRI (**) fglrx(0): Option "NoDRI" "no" (**) fglrx(0): NoDRI = NO (II) Loading extension ATIFGLRXDRI (II) fglrx(0): doing DRIScreenInit (II) fglrx(0): DRIScreenInit done (II) fglrx(0): DRI initialization successfull! (II) fglrx(0): [DRI] installation complete
quite a good news, since the first of the 8.xx serie it was quite a problem, I'll update the ebuild soon. Sorry for closing before
No problem, but please test it. I will provide additional info if requested.
should be fixed now
Which version of the ati-drivers is it no longer an issue with? I've run into this on my LiveCD builds and would love to be able to have both drivers on the CD.
Latest version in portage, beware that has some weird issues with monitors I'd like to have sorted.
I never got a response... which version of the ATI binary drivers was this fixed in so I can look out for it for release stuff?
(In reply to comment #8) > I never got a response... which version of the ATI binary drivers was this > fixed in so I can look out for it for release stuff? I believe all the current stable versions are compatible. I've always had ati-drivers emerged along with DRM as a module and never had a problem. I've been doing this for almost 2 years now.
Any chance I could get a version number since "current stable" isn't the same on x86/amd64 and I need this information for both for LiveCD building? I don't use ATI anything, so I wouldn't even know where to look for this information, but would love to provide accelerated OpenGL for all ATI users.
I can confirm that it works under x86 for all versions currently in portage; there is only one verison marked as x86, with the rest ~x86 or hard masked. 8.14.13-r2 is the only stable for x86. Can't comment regarding amd64 as I do not own one.
every driver since ati-drivers-8.14.13-r3.ebuild should check for DRM being builtin, so you are safe since then. I hope it helps
