Wifi parou de funcionar no Arch no Macbook Air após a atualização do sistema

1

Após uma atualização do sistema Arch hoje, meu wifi parou de funcionar. Isso está em um Macbook Air 2012.

% nmcli                                                                                                                                                                 ~
lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(5) manual pages for complete usage details.
% nmcli con up id guybrush                                                                                                                                                ~
Error: Connection activation failed: No suitable device found for this connection.
%                                                                                                                                                                     4 ~

O que eu faço? Eu uso o driver broadcom-wl-dkms.

PS:

% sudo pacman -S  broadcom-wl-dkms                                                                                                                                      ~
resolving dependencies...
looking for conflicting packages...

Packages (1) broadcom-wl-dkms-6.30.223.271-17

Total Installed Size:   7.60 MiB
Net Upgrade Size:      -0.02 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                                                                         [############################################################] 100%
(1/1) checking package integrity                                                                       [############################################################] 100%
(1/1) loading package files                                                                            [############################################################] 100%
(1/1) checking for file conflicts                                                                      [############################################################] 100%
(1/1) checking available disk space                                                                    [############################################################] 100%
:: Running pre-transaction hooks...
(1/1) Remove DKMS modules
==> dkms remove broadcom-wl/6.30.223.271 -k 4.15.1-2-ARCH
Error! There is no instance of broadcom-wl 6.30.223.271
for kernel 4.15.1-2-ARCH (x86_64) located in the DKMS tree.
==> dkms remove broadcom-wl/6.30.223.271 -k 4.7.5-1-ARCH
Error! There is no instance of broadcom-wl 6.30.223.271
for kernel 4.7.5-1-ARCH (x86_64) located in the DKMS tree.
:: Processing package changes...
(1/1) upgrading broadcom-wl-dkms                                                                       [############################################################] 100%

To load the new module, run the following commands as root:

  rmmod b43 b43legacy bcm43xx bcma brcm80211 brcmfmac brcmsmac ssb wl
  modprobe wl

Or just reboot the system.

:: Running post-transaction hooks...
(1/2) Install DKMS modules
==> dkms install broadcom-wl/6.30.223.271 -k 4.15.1-2-ARCH
==> dkms install broadcom-wl/6.30.223.271 -k 4.7.5-1-ARCH
Error! Bad return status for module build on kernel: 4.7.5-1-ARCH (x86_64)
Consult /var/lib/dkms/broadcom-wl/6.30.223.271/build/make.log for more information.
(2/2) Arming ConditionNeedsUpdate...
%
    
por Toothrot 06.02.2018 / 15:56

2 respostas

1

Eu também tenho um Macbook com arco instalado. Eu não tenho isso aqui, então não posso dar uma resposta precisa, mas o que eu normalmente tento nesses casos é reverter para uma versão anterior do pacote:

cd /var/cache/pacman/pkg
sudo pacman -U broadcom-wl-dkms-VERSION

Se você instalou o driver através do AUR, pode estar desatualizado e, nesse caso, a reinstalação poderá corrigir o problema.

    
por 06.02.2018 / 16:08
1

A instalação de b43-firmware do AUR resolveu o problema. Não há necessidade de rebaixar o driver.

    
por 06.02.2018 / 21:06