<div dir="ltr"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
You have a very perplexing situation and curiosity is getting the best<br>
of me on this one. I have another command for you to try so that we can<br>
know what kernels are actually installed vs. which one is running. If<br>
you could give us the output of `dpkg --list | grep linux-image` it<br>
might shed a little more insight.<br>
<br>
Thanks.<br>
Dan<br>
<br>
<br>
There goes the entire idea of the kernel being held back due to some<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
other package. So why not try to install the right kernel explicitly?<br>
<br>
sudo apt intstall linux-image-generic=5.8.0.33.38<br>
-- <br>
</div>@gents:<br></blockquote><div><br></div><div>Posting the output of the first request, I'll run the explicit kernel install in a bit.</div><div><br></div><div>[CODE] $ dpkg --list | grep linux-image<br>rc linux-image-5.0.0-13-generic 5.0.0-13.14 amd64 Signed kernel image generic<br>rc linux-image-5.0.0-16-generic 5.0.0-16.17 amd64 Signed kernel image generic<br>rc linux-image-5.0.0-17-generic 5.0.0-17.18 amd64 Signed kernel image generic<br>rc linux-image-5.0.0-20-generic 5.0.0-20.21 amd64 Signed kernel image generic<br>rc linux-image-5.2.0-10-generic 5.2.0-10.11 amd64 Signed kernel image generic<br>rc linux-image-5.2.0-15-generic 5.2.0-15.16+signed1 amd64 Signed kernel image generic<br>rc linux-image-5.2.0-8-generic 5.2.0-8.9 amd64 Signed kernel image generic<br>rc linux-image-5.3.0-10-generic 5.3.0-10.11 amd64 Signed kernel image generic<br>rc linux-image-5.3.0-13-generic 5.3.0-13.14 amd64 Signed kernel image generic<br>rc linux-image-5.3.0-17-generic 5.3.0-17.18 amd64 Signed kernel image generic<br>rc linux-image-5.3.0-18-generic 5.3.0-18.19+1 amd64 Signed kernel image generic<br>rc linux-image-5.3.0-19-generic 5.3.0-19.20 amd64 Signed kernel image generic<br>rc linux-image-5.3.0-22-generic 5.3.0-22.24 amd64 Signed kernel image generic<br>rc linux-image-5.3.0-24-generic 5.3.0-24.26 amd64 Signed kernel image generic<br>rc linux-image-5.4.0-12-generic 5.4.0-12.15 amd64 Signed kernel image generic<br>rc linux-image-5.4.0-14-generic 5.4.0-14.17 amd64 Signed kernel image generic<br>rc linux-image-5.4.0-18-generic 5.4.0-18.22 amd64 Signed kernel image generic<br>rc linux-image-5.4.0-21-generic 5.4.0-21.25 amd64 Signed kernel image generic<br>rc linux-image-5.4.0-26-generic 5.4.0-26.30 amd64 Signed kernel image generic<br>rc linux-image-5.4.0-29-generic 5.4.0-29.33 amd64 Signed kernel image generic<br>rc linux-image-5.4.0-33-generic 5.4.0-33.37 amd64 Signed kernel image generic<br>rc linux-image-5.4.0-37-generic 5.4.0-37.41 amd64 Signed kernel image generic<br>rc linux-image-5.4.0-40-generic 5.4.0-40.44 amd64 Signed kernel image generic<br>ii linux-image-5.4.0-42-generic 5.4.0-42.46 amd64 Signed kernel image generic<br>rc linux-image-5.4.0-9-generic 5.4.0-9.12 amd64 Signed kernel image generic</div><div>[/CODE]</div><div><br></div><div>Seems like a lot of kernels, is that just the history, because I do run "autoremove" with some frequency . . . ??</div><div><br></div><div>F<br></div><div> </div></div></div>