Take a look at x11-base/xorg-drivers. The driver specs have moved from
xorg-server to there (thankfully). VIDEO_CARDS is still used.
--Jeff
Maybe I should add these masks to our funtoo cautionary mask? Anyone
really want 1.7.1? Looks like it is causing a lot of problems.
-Daniel
> BTW - what's the matter with x11-libs/libXxf86vm? xorg-server-1.7.1
> won't build without it, complaining of missing package at the
> configure level. It looks like a dependency issue to me, not?
Much easier will be help you if you will attach error + build.log.
Anyway, x11-libs/libXxf86vm-1.1.0 builded for me a few secunds ago
without any issue.
> You must rebuild all drivers if upgrading from xorg-server 1.6
> or earlier, because the ABI changed. If you cannot start X because
> of module version mismatch errors, this is your problem.
> You can generate a list of all installed packages in the x11-drivers
> category using this command:
> emerge portage-utils; qlist -I -C x11-drivers/
So the problem is that most of users never doing it, never reading it...
Sorry, my bad. It came to me a bit as an afterthought, so I wasn't prepared.
Anyway, I tried to upgrade xorg-server without libXxf86vm (for some reason,
probably a conflict...). Then as you try to merge xorg-server-1.7.1 it fails
at the configure stage complaining something about xxf86vm package. Merging
libXxf86vm solves the problem and xorg-server builds properly.
> Anyway, x11-libs/libXxf86vm-1.1.0 builded for me a few secunds ago
> without any issue.
Couldn't you maybe unmerge libXxf86vm and try to merge xorg-server-1.7.1 to
FWIW, the discussion on this list seems to be adhering to the above
statement :-)
--Jeff
Maybe it should be unmasked in ~x86?
Here some background http://bugs.gentoo.org/show_bug.cgi?id=239008
I haven't found any bugs yet that would hinder the unmasking
/usr/portage/profiles/package.mask/gentoo
# Markus Meier <mae...@gentoo.org> (13 Jun 2009)
# mask pre releases of media-gfx/inkscape-0.47
>=media-gfx/inkscape-0.47_pre0
I am also running 1.7.1 without issues.
My question is, why aren't these drivers rebuilt after every xorg-server
upgrade using a similar method as mentioned by Piotr Karbowski above:
emerge -p $(qlist -IC x11-drivers/)
As far as I've seen, video drivers are rebuilt by default, so what other
driver has a "legitimate" reason to crash the system? Mouse or keyboard?
> I'm not sure that masking it now
> will help, since they'll probably run into the same problems anyways
> when the mask is removed. Often they're not issues that are simply
> corrected by waiting for another micro release, since they are either
> user error (like not rebuilding drivers) or some other new
> incompatibility (like a new change that must be made in kernel config).
Which here means turning off default setting. One would hope that at some
point in the future, drivers will get fixed to the point when turning off KMS is
no longer required. Especially if you assume that KMS used to work with the
older package.
> FWIW, the discussion on this list seems to be adhering to the above
> statement :-)
I wouldn't say so. I wrote it crashes my box and I made doubly sure to
rebuild all drivers. Others just wrote that they heard about issues, plus one
person reported KMS conflict. So we know this server crashes fairly popular
hardware, plus it requires turning off KMS on some other hardware, hence it is
broken there. Both cases strongly hint at driver issues, which could get fixed
in the future.
I'm not suggesting masking or unmasking anything, I don't have enough
knowledge to do so. I'm just trying to make sure you guys base your decision
on reported facts.
Andrzej Rosa.
> > Much easier will be help you if you will attach error + build.log.
>
> Sorry, my bad. It came to me a bit as an afterthought, so I wasn't
> prepared.
>
> Anyway, I tried to upgrade xorg-server without libXxf86vm (for some reason,
> probably a conflict...). Then as you try to merge xorg-server-1.7.1 it
> fails at the configure stage complaining something about xxf86vm package.
> Merging libXxf86vm solves the problem and xorg-server builds properly.
The relevant part of emerge output is probably this:
checking for GL... configure: error: Package requirements (glproto >= 1.4.9 gl
>= 7.1.0) were not met:
Package xxf86vm was not found in the pkg-config search path.
Perhaps you should add the directory containing `xxf86vm.pc'
to the PKG_CONFIG_PATH environment variable
Package 'xxf86vm', required by 'gl', not found
To reproduce unmerge x11-libs/libXxf86vm and try to build xorg-server-1.7.1.
Andrzej Rosa.
But yes -- input drivers. Anything you can find via "eix xf86-input"
>> I'm not sure that masking it now
>> will help, since they'll probably run into the same problems anyways
>> when the mask is removed. Often they're not issues that are simply
>> corrected by waiting for another micro release, since they are either
>> user error (like not rebuilding drivers) or some other new
>> incompatibility (like a new change that must be made in kernel config).
>>
>
> Which here means turning off default setting. One would hope that at some
> point in the future, drivers will get fixed to the point when turning off KMS is
> no longer required. Especially if you assume that KMS used to work with the
> older package.
>
KMS isn't on by default.
>
>
>> FWIW, the discussion on this list seems to be adhering to the above
>> statement :-)
>>
>
> I wouldn't say so. I wrote it crashes my box and I made doubly sure to
> rebuild all drivers. Others just wrote that they heard about issues
Most of the issues were resolved in 1.7.1, which is why 1.7.0 wasn't
unmasked.
> person reported KMS conflict. So we know this server crashes fairly popular
> hardware
But works very well for other people on the same hardware.
> plus it requires turning off KMS on some other hardware, hence it is
> broken there.
Again, KMS isn't on by default.
I'd like to point out that this is part of the pain that comes with
running ~. You assume some risk by pegging yourself to testing, which is
what the ~ keyword is for. This isn't a bad thing -- without people
testing and reporting bugs, things could never get fixed and work
properly in stable -- but I don't really see evidence here of a systemic
failure in xorg-server 1.7.1 that requires a full-on mask. Rather it
seems like people are running into bugs in testing software, which is
why it's marked testing, and that finding and reporting them will
benefit everyone. You guys are the front line (and we thank you for it).
--Jeff