how to downgrade to xorg-server-1.4.2?

[koslowj]

The upgrade to xorg-server-1.5.3 broke my x-system, as I'm using the mtx-driver 1.4.6.2 from tuxx-home.at.
I've been trying to downgrade to xorg-server-1.4.2, but ran into the following problem: while fetching and digesting the appropriate ebuild works, when I try to unpack it, I get the following message:

ERROR: x11-base/xorg-server-1.4.2 failed.
Call stack:
ebuild.sh, line 48: Called pkg_setup
xorg-server-1.4.2.ebuild, line 328: Called die
The specific snipped of code:
use nptl || die "${diemsg}"
The die message:
You must build xorg-server and mesa with the same nptl USE setting.

Now my global USE settings include nptl and nptlonly. There are no specific USE settings for mesa and for xorg-server. But even after re-emerging mesa successfully, I'm getting the same error message when trying to ebuild xorg-server-1.4.2. Even prefixing the emerge of mesa and the ebuild of xorg-server-1.4.2 with USE="nptl nptlonly" has the same result.

I need to get this fixed urgently, as my machine is unusable at the moment. I'm typing this on my wife's notebook under xp

Thanks in advance for any help,

-- Juergen

[Clad in Sky]

Perhaps you should get rid of nptlonly in the global flags? Just an idea.
_________________
Kali Ma
Now it's autumn of the aeons
Dance with your sword
Now it's time for the harvest

[koslowj]

Thanks for the suggestion, but so far this doesn't change anything.

One further oddity: when calling "ebuild .../xorg-server-1.4.2.ebuild digest", I get the following output:

>>> Creating Manifest for /usr/portage/x11-base/xorg-server
digest assumed
xorg-server-1.5.3-r4::xorg-server-1.5.3-gentoo-patches-06.tar.bz2

It looks odd to me that a patch for xorg-server-1.5.3 is mentioned.

-- Juergen

[VoidMage]

As 1.5.3 went stable, soon 1.6.0 should hit the tree (it's been in the overlay
for awhile), unless that driver gets updated, you'll be in trouble shortly
(in at most 9 months).

[koslowj]

I finally decided to re-install, presumably having misconfigured my system in the vain attempt to get rid of the strange incompatibility between xorg-server and mesa. Usually, less drastic methods should work, namely getting a version of the portage-*.tar.bzip file dating from before the upgrade of xorg-server and overwriting your portage directory with this. Then one can emerge an older xorg-server, which in my case turned out to be xorg-server-1.3.0.0-r6, rather than xorg-server-1.4.2. I had presumed the latter by mistake (but in retrospect still wouldn't know how to decide which one to take). Then mask the higer versions of xorg-server in the etc/portage/package.mask file to avoid another desaster, before syncing the tree.

Issues remain with respect to libXrender: the old xorg-server wants version 0.9.2, while other packets prefer version 0.9.4, so I masked that one as well.

The main problem is the dreadful linux support by Matrox. The Parhelia 128 otherwise is a nice card, but the promised support never materialized. Just some dedicated individuals made the use of this card possible at all, especially Alex from tuxx-home.at. My next machine, delayed due to other factors, will definitely not have a Matrox card.

Presently, with xorg-server beyond 1.3.0.0-r6 and libXrender beyond 0.9.2 masked, emerge -puD system world still suggests updating mesa (from 6.5.2-r1 to 7.3-r1) and mesa-progs (from 7.0.1 to 7.0.3), besides updates to xf86-video-vesa (from 1.3.0 to 2.2.0), xf86-video-fbdev (from 0.3.1 to 0.4.0) and xf86-input-mouse (from 1.2.3 to 1.4.0). In view of the latest experience I'm a bit hesitant applying those upgrades...

-- Juergen