No, of course that's not it.
When you get a new kernel, if you haven't compiled the module for nvidia
it simply isn't there, and simply will not work. Note that I didn't say
that my X won't start, or that I no longer have 3D acceleration, or that
my nvidia drivers are no longer present.
That's no
Sorry; I see "nvidia-graphics-drivers-180" is a nomenclature for
Launchpad, not an actual package.
This fixed my problem:
dpkg-reconfigure nvidia-185-kernel-source
Now, Jockey can see the nvidia driver.
--
xorg: failed to load module "nvidia"
https://bugs.launchpad.net/bugs/450493
You received
There is no such package called "nvidia-graphics-drivers-180"
Also, I'm experiencing this bug in nvidia-185-*
Trying to get somewhere with Jockey:
$ sudo jockey-text -l
(no output)
$ sudo jockey-text -u
(no output)
$ sudo jockey-text -c
(no output)
The jockey logs are filled with lines like thi
I have a clue (perhaps).
Looking in /lib/modules, there is NO file named nvidia.ko... which is
present on my older, Jaunty system.
Surely the nvidia 185 driver deb file should install a kernel module?
Indeed, recovering all of the nvidia-185* files from /var/cache/apt/ and
dpkg-deb -x 'ing them
I have a clue (perhaps).
Looking in /lib/modules, there is NO file named nvidia.ko... which is
present on my older, Jaunty system.
Surely the nvidia 185 driver deb file should install a kernel module?
Indeed, recovering all of the nvidia-185* files from /var/cache/apt/ and
dpkg-deb -x 'ing them
Update: it just happened 3-4m after a clean boot. This time it happened
"harder"... I could not even ssh into the box to try and inspect logs.
Later inspection of the logs (after a re-boot) shows nothing in
/var/log/messages or syslog or Xorg.0.log; they didn't get a chance to
write before it reall
** Attachment added: "dmesg output after lockup"
http://launchpadlibrarian.net/33389293/bug.txt
--
hard lock up after suspend
https://bugs.launchpad.net/bugs/447768
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
Public bug reported:
Binary package hint: xorg
I have a Jaunty x86_64 install with an NVidia GPU that used to perform
flawlessly: acceleration, reliable suspend/resume, etc.
At some point recently after a kernel upgrade, the system began to have
hard-lockups. I couldn't find rhyme or reason, til
*** This bug is a duplicate of bug 374699 ***
https://bugs.launchpad.net/bugs/374699
oops; found a dupe with a solution
--
gnome-keyboard-properties won't map caps lock as additional ESC
https://bugs.launchpad.net/bugs/380781
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 374699 ***
https://bugs.launchpad.net/bugs/374699
Confirmed here. I've combed through gconf-editor, looking for where this
might be flipping settings, but can't find it yet. It's a compiled-C
program, so I can't peek in the source easily to find out what it's
10 matches
Mail list logo
