1 |
On Tue, Jun 5, 2012 at 11:41 AM, Michael Scherer |
2 |
<a6702894@××××××××××××××.at> wrote: |
3 |
> On Fri, 1 Jun 2012 04:11:35 -0400 |
4 |
> Andrey Moshbear <andrey.vul@×××××.com> wrote: |
5 |
> |
6 |
>> On Wed, May 23, 2012 at 11:12 AM, Michael Scherer |
7 |
>> <a6702894@××××××××××××××.at> wrote: |
8 |
>> > ----- Original Message ----- From: "Andrey Moshbear" |
9 |
>> > <andrey.vul@×××××.com> To: "gentoo-user" |
10 |
>> > <gentoo-user@l.g.o> Sent: Tuesday, 22 May, 2012 08:02 |
11 |
>> > Subject: [gentoo-user] Issues with |
12 |
>> > >=x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue? |
13 |
>> > |
14 |
>> > |
15 |
>> > |
16 |
>> >> Lately, I've been having some issues with segfaults when running |
17 |
>> >> startx and it's been pretty persistent. |
18 |
>> >> |
19 |
>> >> Xorg.0.log and emerge --info are available at |
20 |
>> >> https://gist.github.com/2766926 . |
21 |
>> >> Kernel config is available at https://gist.github.com/276943 . |
22 |
>> >> |
23 |
>> >> I've tried downgrading, but <=x11-drivers/xf86-video-ati-6.14.2 |
24 |
>> >> fails to compile due to incomplete structs. |
25 |
>> >> |
26 |
>> >> Is this more a driver or a hardware issue? |
27 |
>> >> |
28 |
>> > |
29 |
>> > first thing thing is your usage of ACCEPT_KEYWORDS="amd64 ~amd64". |
30 |
>> > with ~amd64 you globally |
31 |
>> > allow all packages masked for amd64. unless you are a |
32 |
>> > developer/tester for gentoo you should remove |
33 |
>> > this keyword, because gentoo usually has good reasons to mask some |
34 |
>> > packages. if for some reason you |
35 |
>> > really need a masked package, you can do this easily only for that |
36 |
>> > package. global unmasking alone might be the reason for half of |
37 |
>> > your troubles. |
38 |
>> > |
39 |
>> > second, it is advisable to use kernel modesetting, which is |
40 |
>> > obviously not enabled. gentoo has a detailed |
41 |
>> > howto for this under http://www.gentoo.org/doc/en/xorg-config.xml. |
42 |
>> > this gives you all necessary details. |
43 |
>> > |
44 |
>> > just a quick shot for the moment. your kernel config doesn't under |
45 |
>> > the link you give, I'd like to see that |
46 |
>> > too, and maybe /etc/X11/xorg.conf or the contents |
47 |
>> > of /etc/X11/xorg.conf.d, if you have any of these, |
48 |
>> > |
49 |
>> > regards, nichael |
50 |
>> > |
51 |
>> > |
52 |
>> |
53 |
>> Well, I added radeon drm & modesetting and the kernel is crashing |
54 |
>> right after the microcode is loaded, but without any signs of panic, |
55 |
>> be it flashing keyboard lights or kernel backtrace with register |
56 |
>> values. |
57 |
>> |
58 |
>> Also, the segfault was caused by the DRI code interpreting a DRI |
59 |
>> opcode as a pointer, hence 0xa4 or similar in the back trace. |
60 |
>> |
61 |
>> -- |
62 |
>> m0shbear |
63 |
>> |
64 |
> |
65 |
> in any case, I'd need some more information: |
66 |
> the link to your .config is broken, I only get an empty page. |
67 |
> if the kernel is involved, output of dmesg and rc.log would |
68 |
> be needed to. |
69 |
> |
70 |
> by the way, did you anything with your ACCEPT_KEYWORDS? |
71 |
> if not, the best thing would be set it simply ="" (and |
72 |
> afterwards --update world, --depclean and revdep-rebuild), |
73 |
> but that's up to you. |
74 |
> |
75 |
> please send me the requested information, otherwise it's |
76 |
> difficult to find out what's wrong. |
77 |
> |
78 |
|
79 |
Also, I've noticed that that radeon.ko autodetection configures it as |
80 |
a RS780, whereas, according to motherboard documentation, it should be |
81 |
RS880 (780G vs 785G). |
82 |
This may be a reason for crashing, since the video card dies due to |
83 |
being supplied bad microcode. |