SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Found the new updates on my HD this morning (thanks to AlienBOB & mirror-slackware-current.sh). Installed on my desktop (Intel graphics) with no issues, all worked well. Then moved to my laptop (Toshiba Satellite P205D-S7805).
I use both KDE-4.6 & fluxbox on this laptop, depending on the situation. I use "wally-2.4" to set the wallpaper. On both desktops, the wallpaper displays properly & will switch fine. All of the KDE apps work OK, but LibreOffice, xfe, xscreensaver (among others) would cause the display to "tear" badly. I tried to get a screenshot, but all I could do was Ctrl-Alt-Bkspc to kill X. I did a lot of googling, but found nothing recent. I upgraded to the mesa that is in testing, but while it worked (& is still working), it didn't solve my problem. I figured the problem was the video driver, so downgraded to the xf86-video-ati-6.13.2-x86_64-1 package & that provided stable video.
So, I have "worked around" my problem. Just wanted to report it & hope that someone might have a solution instead of a work around.
Have you tried enabling vsync? I know with the nvidia driver you can enable it globally, but I believe you can enable for certain individual things like GL screensavers, kwin effects, etc. I always get terrible tearing if I don't enable vsync.
However it is odd than downgrading fixed your problem, so vsync is probably not the culprit, but its worth a look.
Hi,Daedra. Thanks for the response. I can't seem to find a method to "enable vsync". It's not a program, module or option in the kernel config. This is ati (radeon), not nvidia; would that be the difference?
Are you using the proprietary ATI linux driver? Because I know it can be done with there driver. With opensource ATI drivers I found this page which may have some useful information. I can't really help much because I have never had to deal with ATI under linux.
This new driver requires KMS, which is set by default in the new kernel.
Otherwise, create /etc/modprobe.d/radeon.conf with this content:
options radeon modeset=1
Also, the kernel should be booted with vga=normal.
Problems have been observed when trying to use KMS after starting a VESA
framebuffer console. Sorry about the penguins."
Edit: And this:
Provide an alternate ATI driver in case of problems with the latest one.
Last edited by NoStressHQ; 02-11-2011 at 10:50 PM.
@ Daedra: I'm using the open source radeon driver. I think my graphics chip is no longer supported by the proprietary driver, but I will check that out.
@ NoStressHQ: I was using KMS with the earlier kernels. I did rename /etc/modprobe.d/radeon.conf so that the kernel could start kms prior to my trying the new kernel. I didn't think it would matter, since I had no "vga=XXX" statement in my grub2 stanza, but in desperation, I added "vga=normal". Made no difference. In my first post I stated that using xf86-video-ati-6.13.2-i486-1.txz was the work around I used. Thanks for the suggestions, though.
@ dugan: Nope, no compositing manager. I don't require much eye-candy, except for changing the wallpaper every few minutes, & wally takes care of that.
I did rename /etc/modprobe.d/radeon.conf so that the kernel could start kms prior to my trying the new kernel.
I don't think it matters what a file is named in modprobe.d so renaming radeon.conf to something else doesn't really do anything. Try removing the file from modprobe.d and see if that helps. I just upgraded a 64-current radeon box and had to remove the modprobe.d/radeon.conf file.