> 3. User runs glxgears. It uses DRI. > 4. Switch VTs, chown otheruser /dev/dri/card0, chmod 600 > /dev/dri/card0.
maybe this killed some file handles of the x-server. > 5. Change mind, chown root /dev/dri/card0 (no second chmod) > 6. Switch Vts, user runs glxgears again. Reports "operation not > permitted, using slow indirect rendering" and runs at 230 fps. the system reports on what it thinks that has happend. but i am unsure on my explanation. > 7. Switch VTs, check /dev/dri/card0. IT'S NOT THERE! radeon kernel > module is still loaded and has the same access count. > Remember this > is in devfs. > 8. Used the Magic SysRq Key to sync, remount and reboot. so what have we learnt? better do not manipulate rights of files that are in currently in use by some other application. someone with something better to pop up? _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
