From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1ScYUH-0002oq-QJ for garchives@archives.gentoo.org; Thu, 07 Jun 2012 08:54:42 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A9639E05A5; Thu, 7 Jun 2012 08:54:23 +0000 (UTC) Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com [74.125.83.53]) by pigeon.gentoo.org (Postfix) with ESMTP id DD9E9E0656 for ; Thu, 7 Jun 2012 08:52:56 +0000 (UTC) Received: by eekc41 with SMTP id c41so132668eek.40 for ; Thu, 07 Jun 2012 01:52:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=IBZNGrbyPBYc6JsVX5WyWoYOY2zkvBHK5mBlpkt1cmg=; b=TRRkXSLkIAsM7tEkpiL6+Y04nFZN6Hg4hohwNcU5hBcQYTj/xtEyPsYWy6qRux23kU +1wjpLDqkNMTKOUtdvOuwCEkm9rRWwA6VkHpwztA9jU0iyYNaoV8Kz1YoF9F/lSYZQ68 8e/VH1e16dJrc32WKVK1M3JDNaCztKmRUB3rnwwafieLYrKt0QXPERNnMzk4rSDDcGur NCS1kB5W0z9UCcCy0goenDGePHkKFsk22wvTubF2udmKg4kCSp3xcAiPVGu1p0kGOP3N nmCNaPj+NFnj/trMndXuYFg1gsPgXk7gbfqPcn/SA39ifI7roC9mOQJTXRxlyXQjiE9B ovuQ== Received: by 10.14.188.130 with SMTP id a2mr714879een.86.1339059175948; Thu, 07 Jun 2012 01:52:55 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.14.3.3 with HTTP; Thu, 7 Jun 2012 01:52:35 -0700 (PDT) In-Reply-To: <20120605174114.26bf31db@unet.univie.ac.at> References: <00F2F686C9B74D02A9E34DAE5334A49C@mic2> <20120605174114.26bf31db@unet.univie.ac.at> From: Andrey Moshbear Date: Thu, 7 Jun 2012 04:52:35 -0400 Message-ID: Subject: Re: [gentoo-user] Issues with >=x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue? To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 6958ea19-7541-46db-a313-bea1d23bfb21 X-Archives-Hash: df32415d0172657feed72a17d6d933b7 On Tue, Jun 5, 2012 at 11:41 AM, Michael Scherer wrote: > On Fri, 1 Jun 2012 04:11:35 -0400 > Andrey Moshbear wrote: > >> On Wed, May 23, 2012 at 11:12 AM, Michael Scherer >> wrote: >> > ----- Original Message ----- From: "Andrey Moshbear" >> > To: "gentoo-user" >> > Sent: Tuesday, 22 May, 2012 08:02 >> > Subject: [gentoo-user] Issues with >> > >=x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue? >> > >> > >> > >> >> Lately, I've been having some issues with segfaults when running >> >> startx and it's been pretty persistent. >> >> >> >> Xorg.0.log and emerge --info are available at >> >> https://gist.github.com/2766926 . >> >> Kernel config is available at https://gist.github.com/276943 . >> >> >> >> I've tried downgrading, but <=x11-drivers/xf86-video-ati-6.14.2 >> >> fails to compile due to incomplete structs. >> >> >> >> Is this more a driver or a hardware issue? >> >> >> > >> > first thing thing is your usage of ACCEPT_KEYWORDS="amd64 ~amd64". >> > with ~amd64 you globally >> > allow all packages masked for amd64. unless you are a >> > developer/tester for gentoo you should remove >> > this keyword, because gentoo usually has good reasons to mask some >> > packages. if for some reason you >> > really need a masked package, you can do this easily only for that >> > package. global unmasking alone might be the reason for half of >> > your troubles. >> > >> > second, it is advisable to use kernel modesetting, which is >> > obviously not enabled. gentoo has a detailed >> > howto for this under http://www.gentoo.org/doc/en/xorg-config.xml. >> > this gives you all necessary details. >> > >> > just a quick shot for the moment. your kernel config doesn't under >> > the link you give, I'd like to see that >> > too, and maybe /etc/X11/xorg.conf or the contents >> > of /etc/X11/xorg.conf.d, if you have any of these, >> > >> > regards, nichael >> > >> > >> >> Well, I added radeon drm & modesetting and the kernel is crashing >> right after the microcode is loaded, but without any signs of panic, >> be it flashing keyboard lights or kernel backtrace with register >> values. >> >> Also, the segfault was caused by the DRI code interpreting a DRI >> opcode as a pointer, hence 0xa4 or similar in the back trace. >> >> -- >> m0shbear >> > > in any case, I'd need some more information: > the link to your .config is broken, I only get an empty page. > if the kernel is involved, output of dmesg and rc.log would > be needed to. > > by the way, did you anything with your ACCEPT_KEYWORDS? > if not, the best thing would be set it simply ="" (and > afterwards --update world, --depclean and revdep-rebuild), > but that's up to you. > > please send me the requested information, otherwise it's > difficult to find out what's wrong. > Also, I've noticed that that radeon.ko autodetection configures it as a RS780, whereas, according to motherboard documentation, it should be RS880 (780G vs 785G). This may be a reason for crashing, since the video card dies due to being supplied bad microcode.