[SOLVED] some graphic corruption with radeon driver after Apr 27 updates
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
some graphic corruption with radeon driver after Apr 27 updates
Hi.
Yesterday I've installed last -current updates. My system is always kept to -current.
From today I have some graphic corruption in kde. Until yesterday all was ok. I'm not using compositing engine. My laptop has an X700 mobile
I'm using an xorg.conf config file because I've a multimonitor setup and I have saved xrandr settings directly in xorg.conf
In the xorg.conf file I'm using the radeon driver (not fglrx)
I'm getting some strange behaviour by example when I scroll text, where some line disappear from the screen, and sometimes some grafic element (icons, by example) is replaced by weird elements.
Ok I'have activated the modesetting. Now I cannot restart the system, tomorrow I'll check if the problem is solved.
In addition to the activation of modesetting in /etc/modprobe.d/radeon-drm.conf, I had to load the kernel module at startup to make Xorg work correctly. I added the line:
Code:
/sbin/modprobe radeon
in /etc/rc.d/rc.local
Do not forget to change permission of this file to executable (if it's not already set)
If you want a proper 3D acceleration you should load the radeon drm module before to start the X.org server.
From my own investigation (I may be wrong), I need to load the kernel radeon module before X starts because the Slackware generic kernel is not shipped with parameter CONFIG_DRM_RADEON_KMS set:
Code:
less /boot/config-generic-smp-2.6.33.2-smp | grep RADEON
CONFIG_DRM_RADEON=m
# CONFIG_DRM_RADEON_KMS is not set
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
I compiled a custom kernel in which CONFIG_DRM_RADEON_KMS=y and the kernel radeon module loaded automatically.
More precisely here are changes for RADEON in my custom kernel:
Code:
less /boot/config-2.6.33-custom | grep RADEON
CONFIG_DRM_RADEON=m
CONFIG_DRM_RADEON_KMS=y
# CONFIG_FB_RADEON is not set
Last edited by gegechris99; 04-30-2010 at 02:21 PM.
Reason: info about my custom kernel
The option CONFIG_DRM_RADEON_KMS should be enabled to have the radeon module loaded correctly on X startup.
But I should get the same result loading manually the module before starting X, is correct?
Instead of putting 'modprobe radeon' in rc.local can I put the line in rc.modules? I think it's the right place. The effect should be identical .. it's only a question of order and coherence.
As the configure help states, CONFIG_DRM_RADEON_KMS configure kernel mode setting by default when loading the radeon module.
This is highly recommended if your card is supported to take advantage of KMS features.
If not set may be you can get the same result adding the "modeset=yes" or whatever in the modprobe command. You can check that with "modinfo radeon" and have a look at /usr/src/linux/Documentation/kernel-paramleters.txt too (if hopefully it's up to date).
If you want to make sure this module be loaded, yes rc.modules (that is to say the file rc.modules links to) is a good place for the modprobe command.
Last edited by Didier Spaier; 05-03-2010 at 04:30 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.