With all good will in the world after installing those drivers I've been unable to boot my 3.10 or even 3.9 kernel using all possible boot flags. (gentoo=nox disable splash etc etc I tried all) A nogo thus far. )o;
Trying to undo it all... On Tue, Aug 27, 2013 at 10:14 PM, Joost Ruis <joost.r...@sabayon.org> wrote: > http://data.gpo.zugaina.org/gentoo/x11-drivers/ati-drivers/ChangeLog > > In Portage now, I'll go try test them against our 3.10 kernel. > > > On Tue, Aug 6, 2013 at 8:05 PM, Joost Ruis <joost.r...@sabayon.org> wrote: > >> I guess bumping ati-drivers resolves all issues. >> >> >> http://support.amd.com/us/kbarticles/Pages/AMDCatalyst13-8LINBetaDriver.aspx >> >> *Highlights of the AMD Catalyst™ 13.8 Beta Driver for Linux:* >> >> This release of AMD Catalyst™ Linux introduces support for the following >> new features: >> >> - OpenGL 4.3 support >> - Dynamic primary surface resizing >> - *Kernel 3.10 support* >> - SLED 11 SP3 support >> >> >> >> On Fri, Aug 2, 2013 at 7:28 PM, Joost Ruis <joost.r...@sabayon.org>wrote: >> >>> A quick followup on this, testing on my 2nd ATI/AMD system: >>> >>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI >>> RV770 [Radeon HD 4850] >>> >>> In this case KMS also kicks in, but now the FOSS driver is being used it >>> seems, all is well. >>> >>> >>> On Fri, Aug 2, 2013 at 5:22 PM, Joost Ruis <joost.r...@sabayon.org>wrote: >>> >>>> Hi all, >>>> >>>> I tested the latest amd64 MATE daily iso. >>>> On all Intel graphics systems there was no issue, but on my AMD/ATI PC >>>> there was. >>>> >>>> I had to explicitly set nomodeset on boot in order to get it running. >>>> Without that KMS kicks in and the system freezes up. >>>> >>>> The system has this card: >>>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI >>>> Cypress PRO [Radeon HD 5850] >>>> >>>> - If we are going to release the next release like this, and I guess we >>>> are, perhaps add a note about it to the release notes. It is fairly simple >>>> (Press F5 and check nomodeset). >>>> >>>> - If we are not going to release with a problem like this, what can I >>>> do to help tackle this problem? Is there some bug in the detection tools >>>> perhaps? >>>> >>>> - Also consider to not release with FGLRX preinstalled at all? >>>> >>>> Cheers. >>>> >>>> >>>> >>>> >>> >> >
