O Ubuntu 14.04.3 trava após conectar-se com o wifi [duplicado]

Question

Acabei de instalar o Ubuntu 14.04.3 LTS Kernel Version 3.19.0-39-generic.

Eu posso conectar-me à internet com o cabo Ethernet. Quando mudo para uma rede sem fio fixa, o computador congela!

Eu tenho o cartão sem fio BCM43227 da Broadcom. Eu pensei que poderia ser um problema de driver, então eu fiz o seguinte (já que aparentemente os drivers Broadcom são um pouco bugs):

sudo apt-get purge bcmwl-kernel-source broadcom-sta-common broadcom-sta-source
sudo apt-get install b43-fwcutter firmware-b43-installer

Mas não funcionou.

Eu pesquisei muito e descobri que havia erros similares ( link , Congelar após atualizar o kernel para 3.13.0-66 (14.04) ou 3.19.0-31 (15.04) ) recentemente que pode ser corrigido ( link ).

Alguns desses erros vêm dos repositórios propostos, que eu NÃO tenho ativado. Esse problema ainda é um bug? ou um motorista errado?

Qualquer ajuda será apreciada: -)

Editar 1: saída de lspci -knn | grep Net -A2

02:00.0 Network controller [0280]: Broadcom Corporation BCM43227 802.11b/g/n [14e4:4358]
    Subsystem: Foxconn International, Inc. Device [105b:e040]
    Kernel driver in use: bcma-pci-bridge

Editar 2: tentei a solução a partir de possíveis duplicatas Instalando os drivers wireless Broadcom

que significa executar o comando

sudo apt-get install bcmwl-kernel-source

Infelizmente, não funcionou. O sistema congelou novamente depois de se conectar à rede sem fio.

Observação: este foi o mesmo driver que foi instalado após a nova instalação que eu fiz há algumas horas, ou pelo menos é o que eu acho, já que as configurações do sistema - > atualizações de software - > drivers adicionais disseram que eu estava usando os drivers proprietários.

Editar 3:

Após a inicialização, o cabo e a conexão sem fio estão conectados. Nenhum congelamento do sistema.

Cabo Ethernet desconectado, conexão sem fio ainda ativa. Nenhum congelamento do sistema.

No momento em que tentei abrir o navegador - > > sistema congelou! : - (

Eu não sei o que isso significa ... algum pensamento?

Editar 4: o log cat /var/log/syslog | grep -i network | tail -n25

Isso é tudo o que posso obter antes que o sistema congele (o Eth-Cable desconectado e o navegador aberto):

Dec  8 09:03:37 aguilar NetworkManager[996]: <info> Config: set interface ap_scan to 1
Dec  8 09:03:37 aguilar NetworkManager[996]: <info> (eth0): device state change: activated -> unavailable (reason 'carrier-changed')
Dec  8 09:03:37 aguilar NetworkManager[996]: <info> (eth0): deactivating device (reason 'carrier changed')
Dec  8 09:03:37 aguilar NetworkManager[996]: <warn> DNS: plugin dnsmasq update failed
Dec  8 09:03:37 aguilar NetworkManager[996]: <info> Removing DNS information from /sbin/resolvconf
Dec  8 09:03:37 aguilar NetworkManager[996]: <info> NetworkManager state is now CONNECTING
Dec  8 09:03:37 aguilar NetworkManager[996]: <info> (wlan0): supplicant interface state: inactive -> scanning
Dec  8 09:03:44 aguilar NetworkManager[996]: <info> (wlan0): supplicant interface state: scanning -> associating
Dec  8 09:03:44 aguilar NetworkManager[996]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Dec  8 09:03:44 aguilar NetworkManager[996]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Dec  8 09:03:44 aguilar NetworkManager[996]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'GOE-WLAN'.
Dec  8 09:03:44 aguilar NetworkManager[996]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec  8 09:03:44 aguilar NetworkManager[996]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Dec  8 09:03:44 aguilar NetworkManager[996]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Dec  8 09:03:44 aguilar NetworkManager[996]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Dec  8 09:03:44 aguilar NetworkManager[996]: <info> Activation (wlan0) Beginning IP6 addrconf.
Dec  8 09:03:44 aguilar NetworkManager[996]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Dec  8 09:03:44 aguilar NetworkManager[996]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Dec  8 09:03:45 aguilar NetworkManager[996]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Dec  8 09:03:45 aguilar NetworkManager[996]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Dec  8 09:03:45 aguilar NetworkManager[996]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Dec  8 09:03:45 aguilar NetworkManager[996]: <info> NetworkManager statte is now CONNECTED_GLOBAL
Dec  8 09:03:45 aguilar NetworkManager[996]: <info> Policy set 'GOE-WLAN' (wlan0) as default for IPv4 routing and DNS
Dec  8 09:03:45 aguilar NetworkManager[996]: <info> Writing DNS  information to /sbin/resolvconf
Dec  8 09:03:46 aguilar NetworkManager[996]: <info> Activation (wlan0) successful, device activated

Logar após a inicialização e antes de abrir meu navegador:

Dec  8 09:07:11 aguilar NetworkManager[838]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Dec  8 09:07:11 aguilar NetworkManager[838]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'GOE-WLAN'.
Dec  8 09:07:11 aguilar NetworkManager[838]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec  8 09:07:11 aguilar NetworkManager[838]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Dec  8 09:07:11 aguilar NetworkManager[838]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Dec  8 09:07:11 aguilar NetworkManager[838]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Dec  8 09:07:11 aguilar NetworkManager[838]: <info> Activation (wlan0) Beginning IP6 addrconf.
Dec  8 09:07:11 aguilar NetworkManager[838]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Dec  8 09:07:11 aguilar NetworkManager[838]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Dec  8 09:07:12 aguilar NetworkManager[838]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Dec  8 09:07:12 aguilar NetworkManager[838]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Dec  8 09:07:12 aguilar NetworkManager[838]: <warn> error monitoring device for netlink events: error processing netlink message: Object busy
Dec  8 09:07:12 aguilar NetworkManager[838]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Dec  8 09:07:13 aguilar NetworkManager[838]: <info> Writing DNS information to /sbin/resolvconf
Dec  8 09:07:13 aguilar NetworkManager[838]: <info> Activation (wlan0) successful, device activated.
Dec  8 09:07:12 aguilar NetworkManager[838]: <info> WiFi hardware radio set enabled
Dec  8 09:07:23 aguilar NetworkManager[838]: <warn> error monitoring device for netlink events: error processing netlink message: Object busy
Dec  8 09:07:24 aguilar NetworkManager[838]: <info> (eth0): IP6 addrconf timed out or failed.
Dec  8 09:07:24 aguilar NetworkManager[838]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Dec  8 09:07:24 aguilar NetworkManager[838]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Dec  8 09:07:24 aguilar NetworkManager[838]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Dec  8 09:07:30 aguilar NetworkManager[838]: <info> (wlan0): IP6 addrconf timed out or failed.
Dec  8 09:07:30 aguilar NetworkManager[838]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Dec  8 09:07:30 aguilar NetworkManager[838]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Dec  8 09:07:30 aguilar NetworkManager[838]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.

    

Answer 1

Você precisa instalar um driver proprietário. Executar:

sudo apt-get install bcmwl-kernel-source

Nada é buggy. Você simplesmente não instalou o driver correto.