Re: nvidia driver problem

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

steef wrote:
Joe Hart wrote:
steef wrote:

i did that <dpkg-reconf etc. etc. > several times. when i still had the
alien driver 'formally' *installed* in the kernel. i too replaced in
that configuration manually the native nv-driver "nv" with "nvidia"
without results.



after having *uninstalled* the alien driver as root: < nvidia-installer
--uninstall> i do not get the driver installed again.



should i remove the 'new' xorg-files in xorg.conf (in X11) or what to
get the d.... thing installed again???



or, perhaps, i should remove the glx driver (like in earlier times) to
get the alien driver installed again and get it permanently going by not
letting nvidia adapt X11/xorg.conf automatically but do it manually??


The nvidia-glx driver (from non-free) conflicts with the one from
nvidia. The installer for the nvidia one should warn you about that, so
yes, in order to use the alien driver (as you put it) you need to
remove the open source one.

With this computer I need the "nvidia" driver, but others work fine with
the open source "nv" driver. For some reason the "nv" driver takes 40%
of the cpu and leaves my system at a crawl. It depends on the computer
because I've installed the "nv" driver on other computers and had no
problems at all. For normal day-to-day things, I'd say use the "nv"
driver if it works on your computer because at least it is supported.
However, if you want to use Beryl, or play cutting edge 3d games, then
yes, you need the "nvidia" drivers.


Joe




thanks joe. keep using nv. (installed a new 2.6.18 kernel with nvidiafb:
seems all the 2.6.18 kernels have that trait)
LAST QUESTION: what package do i need to measure cpu-usage? (valgrind
maybe??)

thanks,

steef

I actually use GlassMonitor which is a theme for superkarmba. I'm all
KDE here. You can also see the cpu usage with ksysguard, but again,
it's a kde app.

a quick check:

joe@MyBox:~$ apt-cache search monitor | grep cpu
ascpu - AfterStep look & feel CPU statistics monitor tool
cpufreqd - fully configurable daemon for dynamic frequency and voltage
scaling
glcpu - 3D-plotter for system activity
statd - data collection daemon for GLcpu

Take your pick, I've never seen any of them.

Isn't Debian neat?

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF3IGriXBCVWpc5J4RApfhAKC2ifTmQUiMWlrhqQ4AgUHh12k1JACgpDMo
amz+eypdBfAmrvOaQN2++sE=
=LxEF
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: [SLE] NVIDA 6200 was FX5200
    ... even for 2D (video acceleration). ... Today, I thought I'd upgrade the video driver, which is exceptionally ... into YOU and ask for the nvidia driver. ... The nvidia installer does not work as long as a Xserver is still ...
    (SuSE)
  • Re: Xorg - nv - 8600GT blank screen problem.
    ... (I also had blank screens with the nv driver, ... the nVidia installer script worked ... confident that nvidia blob will drop in without much hassle. ...
    (Debian-User)
  • Re: [SLE] Black screen after NVidia update - 2nd posting
    ... > Yes, I have used the nvidia installer, and just did it again for the 3rd ... > to enable the NVidia driver." ... You should be able to put back in the NVIDIA specific XF86Config file and at ...
    (SuSE)
  • Re: Livna nVidia problems...
    ... >>> open source nv driver to get around something you can't get to work ... reported to NVIDIA. ... What I should have said was the livna rpms installs ... If you use the official installer you cannot do this, ...
    (Fedora)
  • Re: Hibernation without EWF
    ... Installing the class installer for the display was the trick. ... Not surprising hibernation doesn't work for you. ... Your display driver never got installed on the target. ... You not only need the class installer but also the proper display driver for the video card you are using on the target machine. ...
    (microsoft.public.windowsxp.embedded)