https://bugs.freedesktop.org/show_bug.cgi?id=29400 Marek Olšák <maraeo@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Drivers/DRI/r300 AssignedTo|mesa-dev@xxxxxxxxxxxxxxxxxx |dri-devel@xxxxxxxxxxxxxxxxx |org |.org --- Comment #4 from Marek Olšák <maraeo@xxxxxxxxx> 2010-08-04 14:52:19 PDT --- I do not use KDE, so it is not clear to me what is wrong on the screenshot. Please also attach the screenshot how it should look like, so that we can compare. Here's some advice on how to bisect efficiently. Your driver is usually located in something like: /usr/lib/dri/r300_dri.so Delete that file and make a new symlink r300_dri.so in place of the original file and point it to .../mesa/lib/gallium/radeong_dri.so, where mesa is your git-cloned mesa repository. Here I have: $ ls -l /usr/lib/dri/r300_dri.so lrwxrwxrwx 1 root root 47 2010-05-23 21:22 /usr/lib/dri/r300_dri.so -> /home/eosie/dev/mesa/lib/gallium/radeong_dri.so Now when you just compile the driver ("make"), it will be automatically used by all applications you run, and those running ones should be just restarted. Concerning KDE, you probably want to restart kdm after typing "make" in the mesa directory. It's really that simple. Now there is nothing stopping you from bisecting. ;) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
