Upgrade to compiz-fusion-0.8.6

Today, when I ran the regular update of my gentoo systems there was an update for compiz-fusion in portage. The compiz update did not work out of the box on my x8_64 systems, missing keywords, blocking packages, etc.

Here is the way I got it to work. The procedure is similar to the one I described in upgrade-to-compiz-fusion-0.82.

emerge -uND world

!!! All ebuilds that could satisfy “>=x11-plugins/compiz-plugins-main-0.8.6” have been masked.
!!! One of the following masked packages is required to complete your request:
– x11-plugins/compiz-plugins-main-0.8.6 (masked by: ~amd64 keyword)

Add to /etc/portage/package.keywords:

=x11-plugins/compiz-plugins-main-0.8.6 **
=x11-plugins/compiz-plugins-unsupported-0.8.6 **
=x11-plugins/compiz-plugins-extra-0.8.6 **
=x11-plugins/compiz-plugins-unsupported-0.8.4-r1 **

the last line is there just because I don´t know if there will be a newer version of compiz-plugins-unsuported or not.

emerge compiz-fusion

[blocks B ] x11-plugins/compiz-fusion-plugins-extra (“x11-plugins/compiz-fusion-plugins-extra” is blocking x11-plugins/compiz-plugins-extra-0.8.4-r1)
[blocks B ] x11-plugins/compiz-fusion-plugins-main (“x11-plugins/compiz-fusion-plugins-main” is blocking x11-plugins/compiz-plugins-main-0.8.4-r1)

emerge -C compiz-fusion-plugins-extra compiz-fusion-plugins-main compiz-fusion-plugins-unsupported

emerge compiz-fusion

Afterwards I had a working compiz-fusion-0.8.6.

regards

Jürgen

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...

nvidia-drivers-180.60 is working !!!

After I have tested the nvidia-drivers-185.18.08 beta I searched the web for a new one and I found it yesterday on nvnews.net. This version seems to run well on my Dell M4300. For all using Gentoo I  made an ebuild:ebuild:nvidia-drivers (777)

# mkdir /usr/local/portage/
# cd /usr/local/portage/
# tar -xpvf nv-portage.tar

Be sure that PORTDIR_OVERLAY=”/usr/local/portage” is in your /etc/make.conf, then you can emerge it:
# ACCEPT_KEYWORDS=”~amd64″ emerge =nvidia-drivers-180.60 -1

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...

nvidia-drivers-185.18.08 beta is not working

Because of the problem with a good, fast and working nvidia driver, I’ve tested the actual beta driver from Nvidia. After installing it on my system (Dell M4300, with zen-sources 2.6.29-r3 running fine on it) everything seems to be fine. But there was the first fault. The character set in the Terminal swaps. The next serious error was restarting the X-Server or crashing the whole system while surfing with Epiphany. So I downgraded my system to nvidia-drivers-180.29 again as mentioned here. It seems Nvidia has to do some work on it, still we have another working release. Stay tuned, we will test it and tell you our experience with any new driver we found from Nvidia.

LG Thorsten

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...

Upgrade to compiz-fusion-0.8.2

Today, when I ran the regular update of my gentoo systems there was an update for compiz-fusion in portage. The compiz update did not work out of the box on my x8_64 systems, missing keywords, blocking packages, wrong manifests, etc.

Here is the way I got it to work:

emerge -uND world

!!! All ebuilds that could satisfy “~x11-plugins/compiz-plugins-main-0.8.2” have been masked.
!!! One of the following masked packages is required to complete your request:
– x11-plugins/compiz-plugins-main-0.8.2 (masked by: ~amd64 keyword)

Add to /etc/portage/package.keywords:

=x11-plugins/compiz-plugins-main-0.8.2 **
=x11-plugins/compiz-plugins-unsupported-0.8.2 **
=x11-plugins/compiz-plugins-extra-0.8.2 **

emerge compiz-fusion

[blocks B ] x11-plugins/compiz-fusion-plugins-extra (“x11-plugins/compiz-fusion-plugins-extra” is blocking x11-plugins/compiz-plugins-extra-0.8.2)
[blocks B ] x11-plugins/compiz-fusion-plugins-main (“x11-plugins/compiz-fusion-plugins-main” is blocking x11-plugins/compiz-plugins-main-0.8.2)
[blocks B ] x11-plugins/compiz-fusion-plugins-unsupported (“x11-plugins/compiz-fusion-plugins-unsupported” is blocking x11-plugins/compiz-plugins-unsupported-0.8.2)

emerge -C compiz-fusion-plugins-extra compiz-fusion-plugins-main compiz-fusion-plugins-unsupported

emerge compiz-fusion

!!! A file listed in the Manifest could not be found: /usr/portage/x11-plugins/compiz-plugins-extra/files/compiz-plugins-extra-no-gconf.patch

ebuild /usr/portage/x11-plugins/compiz-plugins-extra/compiz-plugins-extra-0.8.2.ebuild digest

Note: The generation of the digest is only a temporary solution. There should be the correct manifest in the portage tree.

emerge compiz-fusion

* Messages for package x11-wm/emerald-0.8.2:

* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /usr/portage/x11-wm/emerald/files/emerald-ru.po.patch
* ( emerald-ru.po.patch )
*
* ERROR: x11-wm/emerald-0.8.2 failed.

cd /usr/portage/x11-wm/emerald/files/

ln -s emerald-0.7.8-ru.po.patch emerald-ru.po.patch

Note: The symlink is only a temporary solution. The file should be added to the portage tree.

ebuild /usr/portage/x11-wm/emerald/emerald-0.8.2.ebuild digest

emerge compiz-fusion

Afterwards I had a working compiz-fusion-0.8.2 .

regards

Jürgen

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...

nvidia-drivers-180.37 causing strange segfaults

Today, while performing a large world upgrade on my gento x86_64 system, I noticed almost every build segfaulting (internal compiler error…). In the meanwhile I was encoding several videos (xvid) with avidemux. thus I had a somewhat high memory usage. Some of the avidemux processes also segfaulted. I noticed these segfaults also yesterday, but thought something was wrong with my video files. After many segfaults the system then ran completely out of memory and I had to reboot.

Because of my last experience with nvidias drivers (see: CTRL-C and CTRL-Z not working after nvidia-driver upgrade and high CPU usage) the nvidia-driver was my first supective. So I masked off nvidia-drivers-180.37 and downgraded to 180.29 again. Afterwads the segfaults didn’t occur anymore.

NVIDIA should really do better testing with their drivers before releasing.  Errors like this are normally extremely hard to track down, since nobody would suspect the graphics driver to be the reason for this. Well, in this case intuition saved me a lot of time…

regards

Jürgen

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...