D&C GLug - Home Page

[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]

Re: [LUG] Ubuntu 20.04 lost network

 

On 24/07/2020 17:56, Mark Smith wrote:

>> Update: I'm back online by just booting into an old kernel, 5.4.0-41
>> (5.4.0-40 works also), so something is borked in 5.4.0-42...




I think your "| grep ii" might have been unhelpful here as seeing the other related packages matched from the search but with a different status would have been useful. It's hard to tell from such a brief snippet of info but looking carefully, I see linux-modules-extra is installed for kernels 5.4.0-40 and 5.4.0-41 but not 5.4.0-42. So if your particular network hardware happens to depend on the support in linux-modules-extra that would explain why 5.4.0-42 is unhappy.

Also note how your installed packages naming convention for the kernels changes at exactly 5.4.0-42 too:

linux-image-5.4.0-40-generic               5.4.0-40.44
linux-image-5.4.0-41-generic               5.4.0-41.45
linux-image-unsigned-5.4.0-42-generic      5.4.0-42.46

That looks pretty significant as well.

I would first apt purge everything 5.4.0-42 related and then reinstall making sure to also include linux-image-5.4.0-42-generic and linux-modules-extra-5.4.0-41-generic this time. Sometimes Ubuntu systems just weirdly get random kernel updates wrong - left a "Requires" or a "Depends" out of the Debian rules when packaging perhaps. I can't tell you how many times I've seen Ubuntu systems pull in their updated kernel and immediately trigger DKMS to rebuild the associated modules... only to fail immediately because the matching linux-headers need to be installed first but apt has decided to pull them in later, or not at all. I filed a bug about this and it's still not reliably fixed years later :[

--
The Mailing List for the Devon & Cornwall LUG
https://mailman.dcglug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq