Hi, I was able to reproduce the issue Joost mentioned.
I was misleaded in believing that x-setup could have been the cause,
since I reproduced the issue by deleting /etc/gpu-detector.conf and
rebooted forcing x-setup to rewrite xorg.conf.
Instead it turns out that the latest linux-sabayon version
I can confirm that with latest kernel bump
(sys-kernel/linux-sabayon-3.4-r6 from Limbo) the issue is now
resolved.
The problem was exactly as pointed out by Lorenzo.
On Thu, Jul 19, 2012 at 1:30 PM, Lorenzo Cogotti miciam...@hotmail.it wrote:
Hi, I was able to reproduce the issue Joost
radeon.ko should be loaded automatically.
Quick test, is 3D working? What's inside Xorg.0.log?
--
Fabio Erculiani
On the FGLRX side everything is back to what was normal.
xbox-360 joost # lsmod | grep radeon
xbox-360 joost # lsmod | grep fglrx
fglrx2579795 123
On Thu, Jul 19, 2012 at 6:19 PM, Fabio Erculiani lx...@sabayon.org wrote:
radeon.ko should be loaded automatically.
Quick test,
Hi all,
Latest Limbo bump set a file in /etc/modprobe.d/ called radeon.conf
The purpose of that file is to enable KMS for FOSS ati driver, however
when you do this when you use FGLRX and your card is =5xxx and never
had problems with latest FGLRX driver and new Xorg, this workaround
actually
