I currently do not have any 2D grahics accelaration with radeonhd since Xorg fails to open /dev/dri/card*. The /dev/dri/ - device nodes do not exist at me though the drm and drm_kms_helper modules are loaded.
Created attachment 43274 [details] Xorg.0.log Can anyone explain me this message: 'KMS is disabled. This is good for us, because RADEONHD ... ' ¡¡I have booted without 'nomodeset'!!
radeonhd does not support kms. You need to boot with radeon.modeset=0 to use radeonhd.
What is the difference between nomodeset and radeon.modeset=0? Does it also have an effect on the radeon driver? Why is it not called radeonhd.modeset=0?
I think it's called radeon.modeset because it affects the kernel driver, where the ati/amd code is called "radeon". It doesn't know or care which user mode driver is being used. Not sure about "nomodeset" but I only saw it used in the early days of KMS so guessing it may be obsolete. ----- Original Message ----- From: xorg-team-bounces+eich=suse.de@lists.x.org <xorg-team-bounces+eich=suse.de@lists.x.org> To: xorg-team@lists.x.org <xorg-team@lists.x.org> Sent: Sat Feb 12 08:27:25 2011 Subject: [radeonhd] [Bug 34194] DRM can not be opened/used though the module is loaded https://bugs.freedesktop.org/show_bug.cgi?id=34194 --- Comment #3 from Elmar Stellnberger <estellnb@gmail.com> 2011-02-12 05:27:25 PST --- What is the difference between nomodeset and radeon.modeset=0? Does it also have an effect on the radeon driver? Why is it not called radeonhd.modeset=0?
Guys, this discussion goes into the wrong direction. The reason radeon KMS doesn't work is this one. (II) Could not open DRM - module might not be loaded, KMS detection faulty. (II) [DRM] Kernel mode setting disabled Question is what Elmar wants to achieve. Using radeonhd driver? Then this doesn't matter, since radeonhd doesn't support radeon KMS anyway. But if he wants to use radeon driver then he should file a bug on bugzilla.kernel.org.
Well; I just want to boot into X - and have some effects like transparency. Basically there are the following issues: * radeonhd does not support any 2D graphics accelaration (glx-/driinfo) at me, possibly because it does not know that my card is an ATI Mobility Radeon HD-2700 which should be accessible the same way as an ATI Mobility Radeon HD-2600 is (confirmed with nomodeset and different kernels - see for the 'unknown card' message in the attached log). * kernel modesetting does not work at me at the time: https://bugzilla.kernel.org/show_bug.cgi?id=25052 (Yes, we are already working on a bug like this.) * The radeon driver with enabled DRI is currently unusable because it overflows the event loop. P.S.: As far as I can see the given 0.0.7 kernel version behaves in some way like if kms was disabled even if you don`t state a boot parameter for it (and in some way as if it was not - because of the missing /dev/dri/card*).
Created attachment 43300 [details] Xorg.0.log of radeonhd with radeon.modeset=0 (no direct rendering)
(In reply to comment #6) > Well; I just want to boot into X - and have some effects like transparency. > Basically there are the following issues: > > * radeonhd does not support any 2D graphics accelaration (glx-/driinfo) at me, You are talking about "3D" acceleration, not 2D acceleration. This is disabled in radeonhd on R6xx and higher - at least on openSUSE. > * kernel modesetting does not work at me at the time: > https://bugzilla.kernel.org/show_bug.cgi?id=25052 > (Yes, we are already working on a bug like this.) > > * The radeon driver with enabled DRI is currently unusable because it overflows > the event loop. I guess you mean the one not using KMS, right? > P.S.: As far as I can see the given 0.0.7 kernel version behaves in some way > like if kms was disabled even if you don`t state a boot parameter for it (and > in some way as if it was not - because of the missing /dev/dri/card*). Because it's broken as seen in the error message of Xorg.0.log? (II) Could not open DRM - module might not be loaded, KMS detection faulty. (II) [DRM] Kernel mode setting disabled
Actually, yes (radeonhd, no kms). If radeonhd supports 2D accelaration comprehensively I would guess that there was some support for transparency. How can I query for the degree of 2D-accelaration support? Is it a problem that radeonhd does not know about my card model (Radeon Mobility HD 2700)?
(In reply to comment #9) > Actually, yes (radeonhd, no kms). > If radeonhd supports 2D accelaration comprehensively I would guess that there > was some support for transparency. I seriously doubt that. > How can I query for the degree of 2D-accelaration support? I don't think you can. The best information you can currently get about radeonhd driver you can find here: http://wiki.x.org/wiki/radeonhd > Is it a problem that radeonhd does not know about my card model (Radeon > Mobility HD 2700)? According to the logfile it does.
>> was some support for transparency. > I seriously doubt that. RadeonHD does support transparency via the xrender - extension: For KDE4 just select: Compositing Type: Xrender Fensterknopf liob -> Fensterverhalten festlegen -> Arbeitsflächen Effekte -> Erweitert -> Composit Typ: XRender statt OpenGL ~ Window Button -> Window Behaviour -> Desktop Effects -> Extended -> Compositing Type: Xrender instead of OpenGL: OpenGL has by default no transparency support which is the reason why you will need this option with the proprietary ATI/NVIDIA drivers as well.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.