Gentoo Archives: gentoo-user

From: Michael Scherer <a6702894@××××××××××××××.at>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Issues with >=x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue?
Date: Tue, 12 Jun 2012 14:35:10
Message-Id: 20120612163313.168b5d0f@unet.univie.ac.at
In Reply to: Re: [gentoo-user] Issues with >=x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware issue? by Michael Scherer
1 On Thu, 7 Jun 2012 16:18:02 +0200
2 Michael Scherer <a6702894@××××××××××××××.at> wrote:
3
4 > On Thu, 7 Jun 2012 04:52:35 -0400
5 > Andrey Moshbear <andrey.vul@×××××.com> wrote:
6 >
7 > > On Tue, Jun 5, 2012 at 11:41 AM, Michael Scherer
8 > > <a6702894@××××××××××××××.at> wrote:
9 > > > On Fri, 1 Jun 2012 04:11:35 -0400
10 > > > Andrey Moshbear <andrey.vul@×××××.com> wrote:
11 > > >
12 > > >> On Wed, May 23, 2012 at 11:12 AM, Michael Scherer
13 > > >> <a6702894@××××××××××××××.at> wrote:
14 > > >> > ----- Original Message ----- From: "Andrey Moshbear"
15 > > >> > <andrey.vul@×××××.com> To: "gentoo-user"
16 > > >> > <gentoo-user@l.g.o> Sent: Tuesday, 22 May, 2012
17 > > >> > 08:02 Subject: [gentoo-user] Issues with
18 > > >> > >=x11-drivers/xf86-video-ati-6.14.4: driver issue or hardware
19 > > >> > >issue?
20 > > >> >
21 > > >> >
22 > > >> >
23 > > >> >> Lately, I've been having some issues with segfaults when
24 > > >> >> running startx and it's been pretty persistent.
25 > > >> >>
26 > > >> >> Xorg.0.log and emerge --info are available at
27 > > >> >> https://gist.github.com/2766926 .
28 > > >> >> Kernel config is available at https://gist.github.com/276943 .
29 > > >> >>
30 > > >> >> I've tried downgrading, but
31 > > >> >> <=x11-drivers/xf86-video-ati-6.14.2 fails to compile due to
32 > > >> >> incomplete structs.
33 > > >> >>
34 > > >> >> Is this more a driver or a hardware issue?
35 > > >> >>
36 > > >> >
37 > > >> > first thing thing is your usage of ACCEPT_KEYWORDS="amd64
38 > > >> > ~amd64". with ~amd64 you globally
39 > > >> > allow all packages masked for amd64. unless you are a
40 > > >> > developer/tester for gentoo you should remove
41 > > >> > this keyword, because gentoo usually has good reasons to mask
42 > > >> > some packages. if for some reason you
43 > > >> > really need a masked package, you can do this easily only for
44 > > >> > that package. global unmasking alone might be the reason for
45 > > >> > half of your troubles.
46 > > >> >
47 > > >> > second, it is advisable to use kernel modesetting, which is
48 > > >> > obviously not enabled. gentoo has a detailed
49 > > >> > howto for this under
50 > > >> > http://www.gentoo.org/doc/en/xorg-config.xml. this gives you
51 > > >> > all necessary details.
52 > > >> >
53 > > >> > just a quick shot for the moment. your kernel config doesn't
54 > > >> > under the link you give, I'd like to see that
55 > > >> > too, and maybe /etc/X11/xorg.conf or the contents
56 > > >> > of /etc/X11/xorg.conf.d, if you have any of these,
57 > > >> >
58 > > >> > regards, nichael
59 > > >> >
60 > > >> >
61 > > >>
62 > > >> Well, I added radeon drm & modesetting and the kernel is crashing
63 > > >> right after the microcode is loaded, but without any signs of
64 > > >> panic, be it flashing keyboard lights or kernel backtrace with
65 > > >> register values.
66 > > >>
67 > > >> Also, the segfault was caused by the DRI code interpreting a DRI
68 > > >> opcode as a pointer, hence 0xa4 or similar in the back trace.
69 > > >>
70 > > >> --
71 > > >> m0shbear
72 > > >>
73 > > >
74 > > > in any case, I'd need some more information:
75 > > > the link to your .config is broken, I only get an empty page.
76 > > > if the kernel is involved, output of dmesg and rc.log would
77 > > > be needed to.
78 > > >
79 > > > by the way, did you anything with your ACCEPT_KEYWORDS?
80 > > > if not, the best thing would be set it simply ="" (and
81 > > > afterwards --update world, --depclean and revdep-rebuild),
82 > > > but that's up to you.
83 > > >
84 > > > please send me the requested information, otherwise it's
85 > > > difficult to find out what's wrong.
86 > > >
87 > >
88 > > Also, I've noticed that that radeon.ko autodetection configures it
89 > > as a RS780, whereas, according to motherboard documentation, it
90 > > should be RS880 (780G vs 785G).
91 > > This may be a reason for crashing, since the video card dies due to
92 > > being supplied bad microcode.
93 > >
94 >
95 > according to the gentoo manual, under "device drivers-graphics-
96 > support for framebufferdevices" you should uncheck
97 > -everything- except "enable video mode handling helpers".
98 > instead of uvesafb in the kernel parameters you may use
99 > "radeondrmfb", if anything at all.
100 >
101 > from the Xorg radeon page:
102 > "First of all check that you don't load radeonfb, uvesafb or vesafb
103 > module. This includes no vga parameters for kernel when using KMS.
104 > Console is provided by fbcon and radeondrmfb frame buffer console. So
105 > it is best to make sure that fbcon module is loaded"
106 >
107 > disabling vesa also should rid you of uvesa messages in Xorg.0.log.
108 >
109 > the rs880 and configuring as rs780 is indeed probably at the root
110 > of your troubles. seems that you got the wrong firmware. I have
111 > found other postings with the exact same problem, but as yet
112 > no clear solution. I'll see what I can find and let you know.
113 >
114 > regards, michael
115 >
116 >
117
118 if you haven't solved your problem already, there are two
119 possibilities you coud try:
120 one is using the Radeon R600-family RLC microcode: radeon/R600_rlc.bin
121 (without something else). this should include the rs880.
122 another option might be to download firmware-linux-nonfree from
123 http://packages.debian.org/de/squeeze/firmware-linux-nonfree
124 some people seem to have used it successfully, but I don't
125 know if it works on gentoo.
126
127 sorry that I can only guess on this, not having an rs880 myself.
128 isn't someone on gentoo users with a similar configuration who
129 could give you better advice?
130
131 regards, michael

Replies