Which NVIDIA driver on newly upgraded Lenovo Laptop

to see if it is in use

glxinfo | grep OpenGL

another reason it is not from a .run file (in addition to what 1fallen said) is that the driver installed from .run file would not survive the upgrade. If the driver is functioning it couldn’t be from .run file.

Then tell me why dpkg -S does not return the kernel package name ?

That is the million dollar question???

I don’t recall seeing this:

dpkg -S nvidia-driver*

dpkg -S operates on files not package names …

@stevecoh1 can you do:

dpkg -S /usr/lib/modules/6.5.0-1022-oem/kernel/nvidia-535/nvidia.ko

and tell us what it returns ? (should either be an error message or a package name)

~$ dpkg -S /usr/lib/modules/6.5.0-1022-oem/kernel/nvidia-535/nvidia.ko
dpkg-query: no path found matching pattern /usr/lib/modules/6.5.0-1022-oem/kernel/nvidia-535/nvidia.ko

So, error message.

Mine:


dpkg -S nvidia-driver*
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/installationandconfiguration.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/randr14.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/programmingmodes.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/appendices.html
papirus-icon-theme: /usr/share/icons/Papirus/16x16/apps/nvidia-drivers-settings.svg
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/gbm.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/dma_issues.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/configtwinview.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/installedcomponents.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/xrandrextension.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/newusertips.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/nvidia-persistenced.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/commonproblems.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/sli.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/framelock.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/minimumrequirements.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/knownissues.html
papirus-icon-theme: /usr/share/icons/Papirus/32x32/apps/nvidia-drivers-settings.svg
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/displaydevicenames.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/audiosupport.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/kernel_open.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/glxsupport.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/xcompositeextension.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/egpu.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/depth30.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/nvidia-ml.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/xineramaglx.html
papirus-icon-theme: /usr/share/icons/Papirus/22x22/apps/nvidia-drivers-settings.svg
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/editxconfig.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/nvidia-dbus.conf
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/configmultxscreens.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/nvidiasettings.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/faq.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/addtlresources.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/copyright
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/procinterface.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/NVIDIA_Changelog.gz
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/nvidia-persistenced-init.tar.bz2
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/configlaptop.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/LICENSE.gz
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/gpunames.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/i2c.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/installdriver.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/nvidia-debugdump.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/dpi.html
papirus-icon-theme: /usr/share/icons/Papirus/64x64/apps/nvidia-drivers-settings.svg
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/ngx.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/gsp.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/kms.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/index.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/xwayland.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/nvidia-peermem.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/flippingubb.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/xconfigoptions.html
papirus-icon-theme: /usr/share/icons/Papirus/48x48/apps/nvidia-drivers-settings.svg
app-install-data: /usr/share/app-install/desktop/nvidia-driver-173.desktop
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/changelog.Debian.gz
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/powermanagement.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/introduction.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/retpoline.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/wayland-issues.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/openglenvvariables.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/acknowledgements.html
app-install-data: /usr/share/app-install/desktop/nvidia-driver-185.desktop
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/dynamicpowermanagement.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/nvidia-smi.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/vdpausupport.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/profiles.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/selectdriver.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/dynamicboost.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/optimus.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/addressingcapabilities.html
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/primerenderoffload.html
app-install-data: /usr/share/app-install/desktop/nvidia-driver-96.desktop
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/README.txt.gz
nvidia-driver-565: /usr/share/doc/nvidia-driver-565/html/supportedchips.html
papirus-icon-theme: /usr/share/icons/Papirus/24x24/apps/nvidia-drivers-settings.svg

okay, just to counter-check do the following too:

dpkg -S /usr/lib/modules/6.5.0-1022-oem/kernel/block/bfq.ko*

OOPS, right, it queries in both directions, sorry …

No worries! :slight_smile: No harm no foul…

$ dpkg -S /usr/lib/modules/6.5.0-1022-oem/kernel/block/bfq.ko*
dpkg-query: no path found matching pattern /usr/lib/modules/6.5.0-1022-oem/kernel/block/bfq.ko

hmm, can you check with ls if that file exists actually (i just picked a random one that i have on my machine)

EDIT:
alternatively this should definitely exist:

dpkg -S /lib/modules/6.5.0-1022-oem/kernel/drivers/net/dummy.ko*

and should return linux-modules-6.5.0-1022-oem

$ ls -l /usr/lib/modules/6.5.0-1022-oem/kernel/block/bfq.ko
-rw-r--r-- 1 root root 246777 Apr 25  2024 /usr/lib/modules/6.5.0-1022-oem/kernel/block/bfq.ko
$ dpkg -S /lib/modules/6.5.0-1022-oem/kernel/drivers/net/dummy.ko*
linux-modules-6.5.0-1022-oem: /lib/modules/6.5.0-1022-oem/kernel/drivers/net/dummy.ko

Sorry for delays, I’m simultaneously trying to arrange a complicated air travel trip.

Now this is curious … if ls shows the file exists, dpkg should also know where it comes from …

Here is the same command on my system:

ogra@styx:~$ dpkg -S /lib/modules/6.12.0-28-qcom-x1e/kernel/block/bfq.ko*
linux-modules-extra-6.12.0-28-qcom-x1e: /lib/modules/6.12.0-28-qcom-x1e/kernel/block/bfq.ko.zst
ogra@styx:~$ 

You should see a similar output on every Ubuntu system, this is really curious … I wonder if there is something fishy with your package database, but that could only happen if someone manually tinkers with it or if there is any corruption of the db files

One more try for me today, please try this:

sudo /usr/bin/nvidia-uninstall


This is the weirdest puzzle I’ve seen in years.

Oh, Happy, happy, joy, joy!

To reiterate my goals here.

  1. I want the Ubuntu version of the latest proprietary NVIDIA driver that will work on my system.

  2. I want to continue on Ubuntu 24.04.1 without needing for the third time in a week to start from scratch

  3. I want the system to be fully upgradeable, with none of these mysteries.

It seems that every piece of information I provide gets me deeper into quicksand. I may be willing to reinstall to factory but not unless I absolutely have to.

Sorry for the rant. I don’t suppose you can tell me the meaning of this discrepancy.

What do you expect this to do? What state will my system be in if I do it? I’ll do it if it only means that I’ll be running the system off the CPU graphics.

1 Like

It probably wont do a thing, but yes just uninstall the current driver.

You have case here that has all of us scraching our heads over, I would love to have a magic pill that would fix this…but there is not one.

It doesn’t exist.

$ sudo /usr/bin/nvidia-uninstall
[sudo] password for scohen: 
sudo: /usr/bin/nvidia-uninstall: command not found

Yep, this is confirmation to me that it is Not a .run file by you or the installer

OK, any idea what to try next? @1fallen, @ogra, @sgt-mike, @monkeybrain ? There were a number of suggestions I did not pursue because the discussion veered in different directions, seemed flawed, etc. Is any of them worth another look?

If not, this is what I am left with. I will not start it unless no one can give me any alternative course of action to pursue:

  1. Back up everything on my system currently. It isn’t much.
  2. Reinstall factory config from my USB stick live boot. 22.04.
  3. Do whatever diagnostics you can suggest on this factory fresh system.
  4. Remove anything you think I should move from that factory fresh system. I would like to know in advance what these might be, if any.
  5. If all checks out, repeat the steps I did with Lenovo Tech Support on Monday to get 24.04.1 running
  6. Do whatever diagnostics you can suggest on this newly upgraded 24.04.1 system.
  7. If it still doesn’t work, revert once again to 22.04 and stay there, one very unhappy camper.

Getting back to the original puzzle, anyone care to hazard a guess why the factory configuration from Lenovo had release upgrades set to “never”?