Ok, thanks. This sounds like the outline of a plan. I’d like to flesh it out a bit before I do it. If it all fails I have no choice but to reinstall from factory settings via live USB
Is this right?
rm -f each file identified by for command except the one or two above.
reboot. What mode will it come up in? Will it be no graphics, or will it just not use the graphics card? There are limited graphics capabilities on board the Intel CPU.
In each case, what would be the commands I should issue from a command line to install what needs to be installed?
dpkg tells you it doesn’t come from a deb it knows, not that it doesn’t come from any deb, there is a difference from my understanding, If you download a random deb not from known source or install one with checkinstall dpkg would say the same thing, but it can still remove it nonetheless
That is my understanding, I could be wrong though. But it doesn’t hurt to try, takes a few seconds while we have been here for days already.
Right, that plan sounds correct … (not sure you need -f but you will need sudo …)
the system will come up with a black screen with login prompt and you should be able to log in with your credentials …
once you are logged in run ubuntu-drivers list and see if it suggests anything now, if so, pick the suggested one … else I think there were already suggestions above in this thread how to use ubuntu-drivers install to install the right version …
How do you know it doesn’t come from a .run file ?
We know for sure it does not come from a .deb file … ANY deb you install ever is known by the dpkg database unless you extracted it manually (using the ar command) and copied the contents in place … as soon as you do dpkg -i or apt install info about this is in the database and it does not matter if you upgraded to a new release or whatnot, that info will not go away until you remove the deb with dpkg or apt (which in turn removes its files) …
When you use synaptic it queries exactly that database for info …
Now you might claim next that someone did dpkg -i and then edited the database by hand to remove all traces and that would in fact be possible … but rather unlikely on a freshly booted factory installed laptop that only got upgraded to the next release since it was unboxed …
OP said adamantly he never downloaded or installed from a .run file. I believe him since it takes a bit of work and effort to install from the .run file and it is not possible that he did it by accident without remembering.
I bet it is a .deb from Lenovo’s 22.04 repo and left orphaned when he upgraded to 24.04 where the repo doesn’t support.
$ dpkg --list | grep linux-image*
ii linux-image-6.5.0-1022-oem 6.5.0-1022.23 amd64 Signed kernel image oem
ii linux-image-6.8.0-52-generic 6.8.0-52.53 amd64 Signed kernel image generic
ii linux-image-generic 6.8.0-52.53 amd64 Generic Linux kernel image
ii linux-image-generic-hwe-22.04 6.8.0-52.53~22.04.1 amd64 Generic Linux kernel image
Well, explain how that would technically work while I’m out doing my groceries, I’ll happily read your explanation
A deb that is still installed will have a database entry no matter if the archive it came from still exists, was a different release or has been orphaned or became unsupported … dpkg only cares for local files, not for archives or where the packages originally came from
I did, adamantly, say that I never downloaded or installed any graphics drivers from a run file. However, a possibility was raised that Lenovo might have done so.
There is only one way to find out. Just let OP try it.
I am sure you know more about the intricacies of dpkg than I do. I only ask one question. If it is not a .deb and not from .run file then what is it? How does it get there? If there is a third possibility I would love to know.
