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.
x has been crashing at random with kwin+compositing since i updated to current (the major X updates, nov 14). everytime it does i get this message:
[drm] Num pipes: 1
[drm] Setting GART location based on new memory map
[drm] Loading R500 Microcode
[drm] Num pipes: 1
[drm] writeback test succeeded in 1 usecs
seems that the gpu resets itself. only solutions that work right now is either turning off compositing or using kms.
i've tried recompiling libdrm/mesa/xorg-video-ati, using a fresh .kde folder, mesa 7.8.1/7.8.2 and the problem still persists. am running out of ideas and wondering if anyone else is having the same issues..
The output you posted is completely normal. It happens when you switch between X and the console. Have you taken a look in your /var/log/Xorg.0.log file to see what it says about the crashes?
i thought that the messages were normal before this, but that's the only logs i can trace everytime kde crashes back to the login screen. kde starts up fine and Xorg.0.log looks normal but i'll have a look again at the next crash.
sed -i s/OpenGLIsUnsafe=false/OpenGLIsUnsafe=true/ ~/.kde/share/config/kwinrc
and please give us a feedback.
HTH,
i typed in the command but there wasn't any output. i'm not familiar with the sed command but i understand that changes the 'OpenGLIsUnsafe=false' to true right? KDE had changed the config to 'true' before and i had to manually change it to 'false' to enable desktop effects, otherwise it won't allow the effects to be enabled. i've never had any issues with this particular configuration before this.
i typed in the command but there wasn't any output. i'm not familiar with the sed command but i understand that changes the 'OpenGLIsUnsafe=false' to true right?
Right. sed doesn't output anything but in case of an error (and in you case the command did nothing as you already had 'OpenGLIsUnsafe=true')
Quote:
KDE had changed the config to 'true' before and i had to manually change it to 'false' to enable desktop effects, otherwise it won't allow the effects to be enabled. I've never had any issues with this particular configuration before this.
What puzzles me is that here (Slackware-current as well) if I remove ~/.kde and then launch KDE I find 'OpenGLIsUnsafe=false' in kwinrc
I have a nVidia GPU, not an Ati one , could that be the cause of this different KDE's behavior ???
In my case KDE crashes at startup with either 'nv' or 'vesa' X drivers, it only startx correctly with the 'nouveau' X driver, unless I set 'OpenGLIsUnsafe=true'. But again, I have a nVidia GPU.
Last edited by Didier Spaier; 12-17-2010 at 05:36 PM.
I don't see anything wrong here. Are you sure these data were output after the crash, not at X startup ? ...May be you have something interesting in /var/log/messages or /var/log/syslog ?
i can confirm that enabling KMS solves the problem. only reason i'm hesitant to use KMS is because of some flickering issues. i was wondering if the problem lies in xorg 1.9.2 and if it's safe to revert to the 1.7.7
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.