Hello,
I don´t know whether to reopen this bug or file a new one. The problem
persists and even with the workarounds posted here I wasn´t able to get
my 8200 chipset running.
I´m using 2.6.24-21-generic, before with an Geforce4 chip that needed
the legacy driver. On upgrade, Ubuntu told me it
Confirming solution by package updates, and how-to undo workarounds ...
With updates from today this problem does not exist any more.
If a machine has traces of workaround described above, one needs to:
+ --uninstall any manual NVIDIA*run installation
+ remove nv* from DISABLED_MODULES (in
Wether or not this bug was real (or only the siblings were), I set it
to Fix Released so other people can find the knowledge collected here.
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Status: Invalid = Fix Released
--
wrong nvidia kernel module (7185 instead of 100.11.14)
Finally, the new 2.6.22-11 kernel packages and other update from the
last 3 day breaks down restricted stuff completely.
There are no loadable nvidia kernel modules!!??
The restricted manages tells us we would'nt need restricted drivers!!!???
The damn self-repair-function of gdm (or is it X)
I have a T61, and I also experienced this problem, and solving it
required multiple steps. This problem is really hard to debug because
it is almost impossible to even FIND the incorrect module that is being
loaded, since it seems to exist only in the initramfs! It ends up being
mounted on
I've just looked and dependencies sounds like an unimplemented launchpad
feature - see Bug #95419 .
--
wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
(manual install)
https://bugs.launchpad.net/bugs/136838
You received this bug notification because you are a member of
I think the module problem was due to the manual install needing extra
steps to avoid conflicting with the Ubuntu provided drivers (see
https://help.ubuntu.com/community/NvidiaManual ). I won't close this bug
but if I were you I would probably resolve this bug invalid and
subscribe myself to
For now this problem only exists with (obviously unsupported) foreign
software (NVidia driver installed manually).
From a pure Ubuntu point of view it cannot be reproduced because of other
problems of the current nvidia-glx-new package (see Bug #98641).
Therefore I set this bug to invalid and
I did'nt go with both ways at the same time.
But I could not go the .deb only way, because the nvidia-glx-new 100.11.14
package is still incomplete (#98641) and I can see this one kind of depends on
#98641 and perhaps other nvidia-glx-* bugs.
And there is of course the possibility that the final
