Re: kde Desktop on wheezy - nvidiacard - production ready?
On Fri, Feb 15, 2013 at 12:58:45AM +0100, Michael wrote:
> > Is anyone running wheezy today?
>
> Yes. I don't see crashes or critical bugs with major applications, but i avoid KDE on 'production' desktops :) but then, 'production ready' is a slightly broad term :)
>
> From my i386 laptop, it seems to be ok though (with plasma desktop) if you don't insist on 3D GL eye candy.
>
> Give it a try. You should be able to downgrade anytime, just change sources.list again.
Downgrading is not easy. It will not automatically downgrade packages
that are more recent than specified in sources.list.
Downgrading is easy only if you have a *complete* copy of your old
system elsewhere so you wipe out the neew one and restore the old.
And watch out for things like /var/spool/mail, which contains your mail
and which you prbably don't want to downgrade.
-- hendrik
>
> > have to do with nvidia.
>
> If generic ones (like the nvidia driver from xorg package) don't suffice for you, you may install nvidia-kernel-source and module-assistant, and do
> (root:) m-a clean nvidia; m-a a-i nvidia
> You still need to install nvidia-glx, nvidia-support, and dependent stuff; and to ditch the generic driver, you probably need to put 'nvidia' into a rudimentary xorg.conf file as provided by packages nvidia-xconfig.
>
> For failsafe, you should know how to run a root terminal, and better use text-console (the thing you end up with when you deinstall any loginmanager or use Ctrl+Alt+'Entf' (on a German keyboard) from X.) For example if nvidia does not work as expected, use aptitude from textconsole then you should be able to fix anything, without X session.
>
I recommend put 'testing' into sources.list, instead of 'wheezy'; this will keep you up-to-date even if 'wheezy' gets stale some day.
You probably mean 'wheezy becomes stable, not stale.
>
> If your machine is rather modern, you can have both testing and unstable in sources, because they are rather 'close' compared to the large gap between testing and stable. Then you can downgrade specific packages to 'testing' when they seem to be buggy, and keep others (if possible) 'unstable'. For what it's worth.
> You can try that with testing / stable too, of course, though it should be harder to balance.
With such a combination, you will usually just get the packages from
the newer release and you might as well not mention the older one,
except perhaps for packages that have been dropped from the new release
and don't have newer versions.
-- hendrik
Reply to: