Please consider reintroducing x11-libs/libXi-1.2.1 media-libs/mesa-7.5.2 to the portage tree, masked if necessary. These are required to build xorg-server-1.6.5-r1 (which thankfully is still in the tree, and stable). Since xorg-server 1.7, UMS is no more supported, but I am still stuck with it as the KMS driver does not work for me. (See https://bugs.gentoo.org/show_bug.cgi?id=312013 and https://bugzilla.kernel.org/show_bug.cgi?id=13805 upstream). For reference, the other packages I rely on remaining in portage are x11-libs/libXext-1.0.5 x11-libs/libXinerama-1.0.3 x11-libs/libXtst-1.0.3 x11-libs/libXxf86vm-1.0.2 x11-proto/fixesproto-4.0 x11-proto/inputproto-1.5.1 x11-proto/recordproto-1.13.2 x11-proto/xextproto-7.0.5 x11-proto/xf86vidmodeproto-2.2.2 x11-proto/xineramaproto-1.1.2 Thank you!
(In reply to comment #0) > Please consider reintroducing > x11-libs/libXi-1.2.1 > media-libs/mesa-7.5.2 > to the portage tree, masked if necessary. > > These are required to build xorg-server-1.6.5-r1 > (which thankfully is still in the tree, and stable). > > Since xorg-server 1.7, UMS is no more supported, > but I am still stuck with it as the KMS driver > does not work for me. > > (See https://bugs.gentoo.org/show_bug.cgi?id=312013 > and https://bugzilla.kernel.org/show_bug.cgi?id=13805 upstream). > > For reference, the other packages I rely on remaining in portage are > x11-libs/libXext-1.0.5 > x11-libs/libXinerama-1.0.3 > x11-libs/libXtst-1.0.3 > x11-libs/libXxf86vm-1.0.2 > x11-proto/fixesproto-4.0 > x11-proto/inputproto-1.5.1 > x11-proto/recordproto-1.13.2 > x11-proto/xextproto-7.0.5 > x11-proto/xf86vidmodeproto-2.2.2 > x11-proto/xineramaproto-1.1.2 > > Thank you! > Hello, UMS is supported in 1.7. It has to do with the driver mostly, not the server. Which chipset are you using? Current stable intel drivers, for example, still support UMS.
Aww, shure it is the driver, sorry... xf86-video-intel-2.9.1 does not work for me with xorg-1.7, as described in https://bugs.gentoo.org/show_bug.cgi?id=312013 The driver in turn will not be fixed, according to Rémi Cardona (in Comment #13 of the bug mentioned above). I do have an intel 855GM chipset in a ThinkPad R50e, which basically seems to work w/KMS nowadays, but I am one of the happy few where it does not.
Stupid me hit the resolved button...
I'm sorry for the bad news but I won't bring them back. I also own an 855GM laptop and the ride with GEM/DRI2/KMS has been bumpy (to say the least). I won't bring them back because other people will assume we support them when we barely have enough man-power and knowledge to support *2* main versions of the server (stable and ~arch) and a couple driver versions. The *only* solution is to try the latest and greatest code (live git ebuilds are available in the x11 overlay, through layman) and report bugs upstream. Again, sorry for this answer, it probably isn't what you wanted to hear, but older versions of Xorg components will not come back to portage. Thanks for your understanding
I do understand your reluctance, thank you for your consideration anyway. It does not surprise me too much, as this waiting game would be ever more awkward. I am only rather afraid that basically that is it w/ suspend ops on my laptop, as the upstream bug is being neglected for three releases now and the intel guys clearly are concentrating on current chipsets rather than spending their time in the antiques section. So the latest and greatest most probably just won't do. I keep on trying it, habitually, though :-) BTW: This is actually not a problem with X or the intel driver, it really is the kernel w/KMS itself that fails.
