Thank you for the investigation! Ill try a reboot. On Jan 4, 2010 5:45 PM, "Iain Bucław" <iainbuc...@gmx.co.uk> wrote:
The current kernel you were running on is Linux 2.6.32-7-generic x86_64 when the drivers were being built, but it seems that the headers weren't available when dkms went to build them, so skipped and continued onto the 2.6.32-9-generic x86_64 kernel. This is as per the following output: Building for 2.6.32-7-generic and 2.6.32-9-generic Building for architecture x86_64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. Building initial module for 2.6.32-9-generic Done. So as far as apt/dpkg is concerned, the installation was successful, and rebooting into the 2.6.32-9-generic kernel should load the nvidia drivers as normal. Now, despite this successful completion, jockey continued onto run `modinfo` on the newly compiled driver, and then proceeded to try and write a new xorg.conf - but since it wasn't done for the current running kernel - returned an error. Hence you are getting the message you received. 2010-01-04 15:02:12,646 WARNING: modinfo for module nvidia failed: ERROR: modinfo: could not find module nvidia 2010-01-04 15:02:12,646 ERROR: XorgDriverHandler.enable(): package or module not installed, aborting Although things like this will happen in a development version (what with the constant kernel changes), I suppose something could be done about Jockey and actually *ending successfully* if the driver installed isn't for the current kernel and `modinfo` returns an error - that or just return a warning saying that the driver has not been installed on this kernel with the advise that this usually is because that the incorrect headers are installed OR the advise of which kernel(s) it has been built for. Regards Iain -- Jockey failed to install 185 nvidia on lucid https://bugs.launchpad.net/bugs/503094 You receive... -- Jockey failed to install 185 nvidia on lucid https://bugs.launchpad.net/bugs/503094 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
