Whatever the reason was, jockey does not automatically pull in linux-
restricted-modules any more, so it isn't an issue any more in intrepid.
** Changed in: jockey (Ubuntu)
Status: Incomplete => Fix Released
--
jockey blocks loading of the nvidia propriatary driver
https://bugs.launchpad.
the updates came down via update-manager , although I do sometimes use
synaptic etc so that may be it , but restricted manager etc were not
reinstalled , the only things I removed to correct the problem were
jockey-common and jockey-gtk. I start out a new release using the
restricted packages but s
Ah, so the issue might be that the installation of jockey automatically
installs the Recommends: as well (if you use Applications -> Add/Remove
or Synaptic) and thus pulls in linux-restricted-modules. The latter and
your upstream installation seem to bite each other. Can you confirm
this?
What's t
I will reinstall jockey and post what you asked for this evening , I do
not even have restricted manager, nvidia kernel , nvidia-glx , etc
installed . I removed them about 1/2 way through A1 and went to manualy
installing the nvidia driver. Currently using 169.09.pkg2 ( i'm 64bit )
.
--
jockey
That's it, jockey does not touch the proprietary driver unless you
explicitly tell it so (which doesn't seem to be the case for you). Can
you please install jockey again and do
sudo modprobe -b -v nvidia
and copy&paste the output here?
Also, do you use linux-restricted-modules, or did you inst
I have no flie /etc/modprobe.d/blacklist-local . why would jockey
disable the PROPRIATARY driver ? if it did so it did so automaticly , I
have been using the propriatary driver since about 1/2 way through alpha
1 with no issues until an update a day or so before I filed the bug it
may not be jock
Merely installing jockey does not do anything to the driver. You can of
course use jockey to disable the driver, did you do that? Can you please
attach your /etc/modprobe.d/blacklist-local ?
** Changed in: jockey (Ubuntu)
Status: New => Incomplete
--
jockey blocks loading of the nvidia pr
I noticed something similar from the live CD. After the live system loaded, I
went to "drivers", but then I got an error in jockey.
I'm using the 32-bit version of hardy. I think that the problem I have is
related to the one I already reported (jockey error when the system starts):
https://bug
