1 |
Daiajo Tibdixious posted on Thu, 06 Oct 2016 15:57:10 +1100 as excerpted: |
2 |
|
3 |
> Doing this on phone as chromium update still going (in console mode). |
4 |
> |
5 |
> Ati-drivers-15.12-r1 requires xorg-server-1.17.4 or less, yet world |
6 |
> update insists on pulling in xorg-server-1.8 which then pulls in masked |
7 |
> versions of xf86-input-evdev & xf86-video-ati & and the emerge dies |
8 |
> because the 2 versions of xorg-server can't co-exist. |
9 |
> |
10 |
> I want ati-drivers as my led screen does not look good with basic radeon |
11 |
> driver. |
12 |
> |
13 |
> I am wondering why masked versions are being pulled in as nothing in |
14 |
> package.accept_keywords nor package.unmask |
15 |
> |
16 |
> In world I just have xorg-x11 meta package. I'm wondering if I should |
17 |
> replace that with specific packages. The ebuild does not suggest its |
18 |
> pulling in the 1.8 version, but I may be miss-reading it. |
19 |
> |
20 |
> I have manually installed the latest stable versions of the affected |
21 |
> packages & expect it to work. |
22 |
|
23 |
I know you're on the phone, but please disable HTML mail for the mailing |
24 |
lists, at least. Also, on phone or not, shouldn't affect your ability to |
25 |
quote and then reply in context, /under/ the part you're referring to, |
26 |
instead of above it, entirely out of context. |
27 |
|
28 |
Did you really mean the very old xorg-server-1.8, which you specified |
29 |
twice so I'd ordinarily think so, but it's _really_ old, older than the |
30 |
oldest 1.12.4-r5 in the main tree, so it's hardly a sane guess, or the |
31 |
newer 1.18.x? 1.8, whatever graveyard you might be pulling it from, is |
32 |
certainly < 1.17.4, tho, while 1.18.x is certainly not... |
33 |
|
34 |
Assuming you mean 1.18.x... |
35 |
|
36 |
You're running into two incompatible requirements, causing emerge to die |
37 |
in ordered to let you resolve things manually, as it can't figure out an |
38 |
automatic resolution. |
39 |
|
40 |
1) The xorg drivers (xf86-*) must be built to match the xorg-server |
41 |
version they will be running with. For minor upgrades, this is usually |
42 |
just an ABI incompatibility and the the same driver versions can be |
43 |
rebuilt to match the new server version, but the xorg-server jump to 1.18 |
44 |
is an API jump as well, and requires newer versions of the drivers that |
45 |
can handle that new API. |
46 |
|
47 |
So that's what's pulling in the newer drivers. You can't upgrade the |
48 |
server to 1.18.* without upgrading the drivers as well. |
49 |
|
50 |
2) One of the problems with proprietary drivers is that they often lag |
51 |
freedomware development in support of new APIs by some time, forcing |
52 |
distros (and on metadistros such as gentoo that offer multiple versions |
53 |
to choose from, users) to choose between holding back in ordered to |
54 |
accommodate those still using the lagging proprietary drivers, at the |
55 |
expense of allowing those using all freedomware use of the bugfixes and |
56 |
newer features available in current versions, or moving forward at full |
57 |
freedomware API change speed for those with all freedomware, while |
58 |
inconveniencing and occasionally entirely dropping support for those who |
59 |
choose to use proprietaryware that doesn't support the newer APIs. And |
60 |
unlike freedomware, the community can't do anything to bring the lagging |
61 |
proprietaryware support for the new APIs because it's proprietary and |
62 |
won't let them at it -- the proprietaryware developers must do it |
63 |
themselves, and hold hostage anyone using that software to their own |
64 |
whims and schedules as to when that might be, including never, because |
65 |
the code isn't available to the community for people to either make those |
66 |
changes themselves or to pay someone else to do it (perhaps with a |
67 |
kickstarter project or the like) if they can't. |
68 |
|
69 |
This is what's happening here. Your ATI driver doesn't yet support those |
70 |
new APIs in xorg-server-1.18.x, and thus won't load if you try to force |
71 |
the driver to run with the new server. |
72 |
|
73 |
|
74 |
Now normally, when faced with such a case portage will recognize that the |
75 |
two versions can't be installed together and that your ati drivers only |
76 |
work with the older version, and will resolve the problem by dropping the |
77 |
newer version of xorg-server. However, in this case it's not doing so, |
78 |
possibly because something else (shouldn't be the xorg metapackage, but |
79 |
might be a newer version of... something else) actually requires the |
80 |
newer version, or possibly due to some other bug. |
81 |
|
82 |
Regardless, your only choice to keep your ATI driver working, unless |
83 |
there's an upgrade to it you can unmask, is to continue with the older |
84 |
xorg-server-1.17.x. You may still be able to upgrade the other xorg |
85 |
drivers (the xf86-* stuff), or may not, but even if you can keep them, if |
86 |
they were built against xorg-server-1.18.x, you'll have to rebuild them |
87 |
against the older 1.17.x once it's remerged, in ordered to get them to |
88 |
work with it. |
89 |
|
90 |
Of course your other choice is to try the latest radeon or amdgpu driver |
91 |
and see if it fixes the LED issue with your monitor that you mentioned, |
92 |
allowing you to drop the proprietaryware ATI driver. If you haven't |
93 |
tried it in awhile, it may indeed be fixed. |
94 |
|
95 |
|
96 |
Meanwhile, the easiest way to ensure that portage doesn't consider xorg- |
97 |
server-1.18, if you decide you need to stay with the ATI driver and |
98 |
there's no upgrade yet to it to work with 1.18, would be to package.mask |
99 |
=xorg-server-1.18* (or similar). Just don't forget to unmask it once a |
100 |
newer ATI driver that supports it is available. =:^) |
101 |
|
102 |
Of course as mentioned, since you've already manually tried 1.18 and the |
103 |
other driver upgrades, you'll have to either rebuild them as well, or |
104 |
downgrade them too, once you downgrade back to xorg-server-1.17.x. |
105 |
|
106 |
-- |
107 |
Duncan - List replies preferred. No HTML msgs. |
108 |
"Every nonfree program has a lord, a master -- |
109 |
and if you use the program, he is your master." Richard Stallman |