On Tuesday 15 Apr 2014 18:39:09 [email protected] wrote: > Tom Wijsman <[email protected]> [14-04-15 19:36]: > > On Tue, 15 Apr 2014 17:59:19 +0200 > > > > [email protected] wrote: > > > Alan McKinnon <[email protected]> [14-04-15 17:33]: > > > To exegrate the whole discussion: > > > > > > "Help! I have a problem with Linux!" > > > > > > "...I have some heard of Linux...bad things...use windows instead!" > > > > > > So: Due to the already mentioned reasons I cannot use other hardware/ > > > other software. I need to get THIS running. > > > > > > Next question: How can I downgrade to the previous version of > > > nvidia-drivers/nvidia-settings/nvidia-cude-toolkit, which works > > > nice for me? > > > > Put the version you don't want in /etc/portage/package.mask; see `man > > portage` for details, but for example if you don't want 337.12 or newer, > > you would do something like this: > > > > /etc/portage/package.mask: > > >=x11-drivers/nvidia-drivers-337.12 > > > > Then doing `emerge -u x11-drivers/nvidia-drivers` will downgrade it. > > ...problem here is, that the emerge process already killed all ebuilds > except the newest one of nvidie-cuda-toolkit and nvidia-settings... > > And the emerge detects a mismatch between the nvidia-drivers to > downgrade and the (still newest) nvidie-cuda-toolkit and nvidia-settings > and refuses to do anything... > > lost?
You can find your way back, even if portage has removed previous versions. Check portage ebuilds here: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-drivers/ or use subversion to pull in the one you need. Then set it up in your local overlay, run 'ebuild <ebuild_file> manifest' and emerge it. As long as it does not have any dependencies which are no longer available you should be OK. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
