0

I rebooted and found that not only did I not have a wifi connection, but the System Settings Network panel had lost its Hotspot and WiFi tabs (only VPN & Proxy)! When I checked the AppCenter Installed tab, I found at the very top of the list was a backport-iwlwifi-dkms package that I don't recall ever installing. Upon removing it and rebooting, things were back to normal, although the AppCenter Installed tab continues to show a Drivers section with the backport-iwlwifi-dkms package ready to be installed (which I obviously don't want to do!).

Does anybody know what is going on? And how can I get this horrible driver out of my Installed list?

  • I see it too and almost installed it (it asked for secureboot password, so I cancelled it - if it ain't broke..), I think it's just an update, that's why you will see it there. Good to know that uninstalling is so simple though.. – jena Jan 28 at 12:45
0

I would just ignore it. I also get old(er) nvidia drivers being offered, but I just don't even pay attention to them:

enter image description here

| improve this answer | |
  • IMHO, the people at Elementary really should not put things up on their AppCenter that break their clients' systems! – Tim02130 Jan 26 at 21:07
  • 1
    I don't think this is really their fault. First of all, it's backport by Intel pushed to Ubuntu repository (as some people may even need it). Second, it's separate from normal updates - I had to specifically click it's button to install it, it was always excluded from normal updates. I'm actually surprised how well this is handled. – jena Jan 28 at 12:47
  • I thought the whole point of a separate Elementary AppCenter was to give the Elementary developers control of their users' systems, saving them having to get into the complexities of handling a vanilla Ubuntu system. That's certainly why I decided to go with Elementary anyway. Furthermore this driver is showing up in my "Installed" tab, even though it's NOT currently installed, and inviting me to install it. Finally I don't know how it ever got installed in the first place; it was sheer luck that i thought to try uninstalling it when I suddenly found my WiFi had been wrecked. – Tim02130 Feb 2 at 23:39
  • After "sudo apt install -y linux-firmware", I got the message "linux-firmware is already the newest version (1.173.18)." Does this mean I didn't need to do this? – Tim02130 Jun 28 at 17:52
0

Remove iwlwifi driver from App Center. Then open terminal and type:

sudo update-initramfs -u

Provide the result of this command. I will be able to guide you which firmware for Wi-Fi adapter is needed.

| improve this answer | |
  • I can see no option to in the App Center to remove the driver (or I would've done it already and never have submitted this post!). As it stands my WiFi works most of the time without the driver anyway. It does go down every few days and I have to switch the WiFi off and on to get it back up. If a new driver will fix that minor nuisance I'll try it, otherwise I can live with things the way they are. – Tim02130 Jun 25 at 11:39
  • Here's the output you asked for: sudo update-initramfs -u [sudo] password for tfhavel: update-initramfs: Generating /boot/initrd.img-5.3.0-59-generic I: The initramfs will attempt to resume from /dev/nvme0n1p6 I: (UUID=1b076493-99fa-4aa7-bfb2-81d480f67e0e) I: Set the RESUME variable to override this. – Tim02130 Jun 25 at 11:40
  • I thought it will show the information about missing firmware. sudo lscpi will list all devices. I am curious what kind of Wi-Fi adapter it is. – Sysadmin Jun 25 at 19:27
  • lspci (not lscpi, which doesn't exist) does not show any wifi device; ifconfig shows however the device name is wlp0s20f3, if that means anything to you. The laptop itself is an LG Gram-17Z990-R-AAS9U1. – Tim02130 Jun 26 at 11:28
  • wlp0s20f3 is the interface name what does says nothing about the Wi-Fi adapter model. I will try to find out using the name of the laptop model. – Sysadmin Jun 26 at 18:12
0

Type commands in terminal one by one:

cd
cd /Downloads
wget https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-9000-pu-b0-jf-b0-34.618819.0.tgz
tar -xzvf iwlwifi-9000-pu-b0-jf-b0-34.618819.0.tgz 
cd iwlwifi-9000-pu-b0-jf-b0-34.618819.0
sudo cp iwlwifi-9000-pu-b0-jf-b0-34.ucode /lib/firmware
sudo apt update
sudo apt upgrade
sudo apt install --reinstall linux-image-generic
sudo apt install -y linux-firmware 
sudo apt install -y linux-image-extra-*
sudo apt install -y linux-modules-extra-$(uname -r)
sudo update-initramfs -u
sudo apt autoremove 
sudo apt autoclean
sudo reboot

Explanation from the README.iwlwifi-9000.ucode

  1. OVERVIEW

The files iwlwifi-9000-pu-b0-jf-b0-34.ucode provided in this package must be present on your system in order for the Intel Wireless WiFi Link AGN driver for Linux (iwlwifi) to operate on your system.

The "-34" in the filename reflects an interface/architecture version number. It will change only when changes in new uCode releases make the new uCode incompatible with earlier drivers.

On adapter initialization, and at varying times during the uptime of the adapter, the microcode is loaded into the memory on the network adapter. The microcode provides the low level MAC features including radio control and high precision timing events (backoff, transmit, etc.) while also providing varying levels of packet filtering which can be used to keep the host from having to handle packets that are not of interest given the current operating mode of the device.

  1. INSTALLATION

The iwlwifi driver will look for the file iwlwifi-9000-pu-b0-jf-b0-34.ucode using the kernel's firmware_class infrastructure. More information can be found under Documentation/firmware_class in kernel source. In order to function correctly, you need to have this support enabled in your kernel. When you configure the kernel, you can find this option in the following location:

    Device Drivers ->
            Generic Driver Options ->
                    Userspace firmware loading support

You can determine if your kernel currently has firmware loader support by looking for the CONFIG_FW_LOADER definition on your kernel's .config.

In addition to having the firmware_class support in your kernel, you must also have a working udev and uevent infrastructure configured. The steps for installing and configuring udev are very distribution specific.

Once you have the firmware loader in place (or if you aren't sure and you just want to try things to see if it works), you need to install the microcode file into the appropriate location.

Where that appropriate location is depends (again) on your system distribution. You can typically find this location by looking in the udev scripts of your distro, the default is /lib/firmware.

Installation of the firmware is simply:

    % cp iwlwifi-9000-pu-b0-jf-b0-34.ucode /lib/firmware

You can now load the driver (see the INSTALL and README.iwlwifi provided with the iwlwifi package for information on building and using that driver.)

Additional Intel Wi-Fi Linux Drivers for other people: Intel Wi-Fi drivers for Linux:

| improve this answer | |
0

How to install i915 firmware.

Type in terminal:

cd /home/username/Downloads/
sudo mkdir i915
cd i915 
git clone https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git 
sudo cp -R linux-firmware/i915/* /lib/firmware/i915/
sudo update-initramfs -u
sudo reboot
| improve this answer | |
  • OK (except for the "/" at the beginning of "/linux-firmware" on the cp line). – Tim02130 Jun 29 at 18:57
  • Corrected. You were right. Let me know how Wi-Fi works. The same way as before or it is stable now? – Sysadmin Jun 30 at 5:46
  • Having now used it for a month, yes it does appear more stable now! Thanks, Tim – Tim02130 Aug 4 at 20:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.