Re: [gentoo-user] Issues with >=x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue?

[Andrey Moshbear <andrey.vul@gmail.com>]

On Wed, May 23, 2012 at 11:12 AM, Michael Scherer
<a6702894@unet.univie.ac.at> wrote:
> ----- Original Message ----- From: "Andrey Moshbear" <andrey.vul@gmail.com>
> To: "gentoo-user" <gentoo-user@lists.gentoo.org>
> 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