On 2011/07/30 07:51 (GMT+0800) George Olson composed:
Yes, if unichrome is the driver name, replace radeon with it (keeping quotes), and removing the comment #.
Since the behavior has changed, I would double-check to see which driver is actually being loaded and with what parameters. Do an lsmod as root, you should see the kernel driver name in the list. And look at /var/log/Xorg.0.log for what X is actually doing with the driver.
Ok, how do I open the 50-device.conf file in kwrite as root so that I can edit and save it? I can't remember how to open up kwrite with root privileges.
Back up. Look in Xorg.0.log. If there are not already numerous lines that include UNICHROME, only then might specifying unichrome as the driver in 50-monitor.conf serve any purpose. A lot of UNICHROME lines in Xorg.0.log means it's already being used. If you need to modify that file, kwrite is not the only way. I never use kwrite to modify config files. I open MC after logging in as root in Konsole or on a tty. Going to a tty first also facilitates X restarting to initiate the configuration change. IOW, first log out of KDE, then log in as root, then open MC, with which you navigate to /etc/X11/xorg.conf.d/ and use MC's internal editor to make the change, then restart X. I suspect your 3D problem is that the FOSS unichrome driver simply doesn't support 3D well on your gfxchip. If true, it means you need VIA's proprietary driver for 3D to work OK. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org