Hello! Yes, I do have the Sophos Antivirus software installed. However,
your commands failed to work on my machine. Previously, I had done the
same with a different command.


sudo systemctl stop sav-protect.service

This usually does the trick (stops the antivirus), then I proceeded to
your code of...

sudo apt-get install -f

...which did nothing.

I did try to update the linux image/kernel again... And these new
packages were installed...

frederick@frederickpina:~$ sudo apt-get upgrade linux-image-generic
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  amd64-microcode intel-microcode iucode-tool linux-image-generic
  linux-modules-extra-5.4.0-33-generic thermald
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/41.2 MB of archives.
After this operation, 193 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Selecting previously unselected package iucode-tool.
(Reading database ... 236417 files and directories currently installed.)
Preparing to unpack .../0-iucode-tool_2.3.1-1_amd64.deb ...
Unpacking iucode-tool (2.3.1-1) ...
Selecting previously unselected package linux-modules-extra-5.4.0-33-generic.
Preparing to unpack 
.../1-linux-modules-extra-5.4.0-33-generic_5.4.0-33.37_amd64.deb ...
Unpacking linux-modules-extra-5.4.0-33-generic (5.4.0-33.37) ...
Selecting previously unselected package intel-microcode.
Preparing to unpack .../2-intel-microcode_3.20191115.1ubuntu3_amd64.deb ...
Unpacking intel-microcode (3.20191115.1ubuntu3) ...
Selecting previously unselected package amd64-microcode.
Preparing to unpack .../3-amd64-microcode_3.20191218.1ubuntu1_amd64.deb ...
Unpacking amd64-microcode (3.20191218.1ubuntu1) ...
Selecting previously unselected package linux-image-generic.
Preparing to unpack .../4-linux-image-generic_5.4.0.33.38_amd64.deb ...
Unpacking linux-image-generic (5.4.0.33.38) ...
Selecting previously unselected package thermald.
Preparing to unpack .../5-thermald_1.9.1-1ubuntu0.1_amd64.deb ...
Unpacking thermald (1.9.1-1ubuntu0.1) ...
Setting up iucode-tool (2.3.1-1) ...
Setting up intel-microcode (3.20191115.1ubuntu3) ...
update-initramfs: deferring update (trigger activated)
intel-microcode: microcode will be updated at next boot
Setting up amd64-microcode (3.20191218.1ubuntu1) ...
update-initramfs: deferring update (trigger activated)
amd64-microcode: microcode will be updated at next boot
Setting up linux-modules-extra-5.4.0-33-generic (5.4.0-33.37) ...
Setting up thermald (1.9.1-1ubuntu0.1) ...
Setting up linux-image-generic (5.4.0.33.38) ...
Processing triggers for dbus (1.12.16-2ubuntu2) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for initramfs-tools (0.136ubuntu6) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-33-generic
Processing triggers for linux-image-5.4.0-33-generic (5.4.0-33.37) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.0-33-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-33-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-33-generic
Found initrd image: /boot/initrd.img-5.4.0-33-generic
Found linux image: /boot/vmlinuz-5.4.0-29-generic
Found initrd image: /boot/initrd.img-5.4.0-29-generic
Adding boot menu entry for UEFI Firmware Settings
done
frederick@frederickpina:~$ ^C

After this, I restarted the machine and thought the Wifi drivers would
work again; but in actuality did not.

I then tried to reinstall the wifi drivers directly, via this method...
But again, ran into another stumbling block:

frederick@frederickpina:~$ sudo apt update && apt install firmware-iwlwifi
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://ppa.launchpad.net/canonical-hwe-team/backport-iwlwifi/ubuntu focal 
InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease           
Hit:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease         
Hit:5 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal InRelease
Ign:6 https://packages.erlang-solutions.com/ubuntu focal InRelease
Hit:7 https://packages.erlang-solutions.com/ubuntu focal Release               
Hit:8 http://archive.ubuntu.com/ubuntu focal-security InRelease                
Hit:9 http://ppa.launchpad.net/libreoffice/ppa/ubuntu focal InRelease    
Hit:10 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease
Hit:11 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu focal InRelease
Hit:12 http://ppa.launchpad.net/transmissionbt/ppa/ubuntu focal InRelease
Hit:14 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu focal InRelease
Hit:15 http://ppa.launchpad.net/utappia/stable/ubuntu focal InRelease
Reading package lists... Done                      
Building dependency tree       
Reading state information... Done
All packages are up to date.
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission 
denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are 
you root?
frederick@frederickpina:~$ 


So, in conclusion... It feels like I'm making some marginal progress,
but I also feel like I'm back to square one; and still am as mystified
as ever regarding this technical issue.

Does any of this help clarify the issue for you? Thanks again for your
patience and support. I very much appreciate you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882194

Title:
  Intel Wireless 7265 [8086:095a] Subsystem [8086:5010] not probed after
  kernel packages upgrade failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to