Kubuntu 13.10 Wifi não funciona - tempo limite de DHCP

4

Eu tenho um adaptador WiFi 802.11b / g / n Realtek RTL8188CE no meu computador. Hoje eu atualizei para 13.10 e não consigo me conectar. Antes de atualizar o WiFi funcionou muito bem. Eu posso ver redes WiFi, mas apenas dá o erro "A configuração IP não estava disponível" ao tentar se conectar. Outros dispositivos funcionam bem. Eu tentei excluir a configuração e refazê-lo várias vezes, e isso não funciona.

Então, olhando para o syslog, parece que a requisição DHCP está expirando. Eu posso conectar-me à rede se eu definir manualmente o IP e outras configurações, mas ainda não tenho conexão com a Internet por meio do Wifi - acho que minha configuração manual ainda está um pouco desligada.

Aqui está o lspci:

chrisn@Zircon:~$ lspci | grep WiFi
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01)

E saída de rede lshw -C

  *-network               
   description: Wireless interface
   product: RTL8188CE 802.11b/g/n WiFi Adapter
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@0000:02:00.0
   logical name: wlan0
   version: 01
   serial: 54:04:a6:de:cb:ba
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
   configuration: broadcast=yes driver=rtl8192ce driverversion=3.11.0-12-generic firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11bgn
   resources: irq:16 ioport:d000(size=256) memory:fe500000-fe503fff

Este é / var / log / syslog do ponto em que cliquei no botão "Conectar" para quando ele desistiu.

chrisn@Zircon:~$ sudo tail -f -n0 /var/log/syslog
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) starting connection 'Diamond'
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0/wireless): access point 'Diamond' has security, but secrets are required.
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0/wireless): connection 'Diamond' has security, and secrets exist.  No new secrets needed.
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Config: added 'ssid' value 'Diamond'
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Config: added 'scan_ssid' value '1'
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Config: added 'key_mgmt' value 'NONE'
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Config: added 'auth_alg' value 'OPEN'
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Config: added 'wep_key0' value '<omitted>'
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Config: added 'wep_tx_keyidx' value '0'
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 19 14:03:05 Zircon NetworkManager[909]: <info> Config: set interface ap_scan to 1
Oct 19 14:03:06 Zircon NetworkManager[909]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Oct 19 14:03:07 Zircon wpa_supplicant[1415]: wlan0: SME: Trying to authenticate with 00:1f:33:e9:99:8a (SSID='Diamond' freq=2437 MHz)
Oct 19 14:03:07 Zircon kernel: [ 1911.641635] wlan0: authenticate with 00:1f:33:e9:99:8a
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Oct 19 14:03:07 Zircon kernel: [ 1911.651176] wlan0: send auth to 00:1f:33:e9:99:8a (try 1/3)
Oct 19 14:03:07 Zircon wpa_supplicant[1415]: wlan0: Trying to associate with 00:1f:33:e9:99:8a (SSID='Diamond' freq=2437 MHz)
Oct 19 14:03:07 Zircon kernel: [ 1911.654471] wlan0: authenticated
Oct 19 14:03:07 Zircon kernel: [ 1911.654701] rtl8192ce 0000:02:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
Oct 19 14:03:07 Zircon kernel: [ 1911.656855] wlan0: associate with 00:1f:33:e9:99:8a (try 1/3)
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> (wlan0): supplicant interface state: authenticating -> associating
Oct 19 14:03:07 Zircon wpa_supplicant[1415]: wlan0: Associated with 00:1f:33:e9:99:8a
Oct 19 14:03:07 Zircon wpa_supplicant[1415]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:1f:33:e9:99:8a completed (reauth) [id=0 id_str=]
Oct 19 14:03:07 Zircon kernel: [ 1911.660841] wlan0: RX AssocResp from 00:1f:33:e9:99:8a (capab=0x431 status=0 aid=4)
Oct 19 14:03:07 Zircon kernel: [ 1911.660951] wlan0: associated
Oct 19 14:03:07 Zircon kernel: [ 1911.661236] cfg80211: Calling CRDA for country: US
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> (wlan0): supplicant interface state: associating -> completed
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Diamond'.
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct 19 14:03:07 Zircon kernel: [ 1911.667519] cfg80211: Regulatory domain changed to country: US
Oct 19 14:03:07 Zircon kernel: [ 1911.667525] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 19 14:03:07 Zircon kernel: [ 1911.667530] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Oct 19 14:03:07 Zircon kernel: [ 1911.667534] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Oct 19 14:03:07 Zircon kernel: [ 1911.667538] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 19 14:03:07 Zircon kernel: [ 1911.667541] cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 19 14:03:07 Zircon kernel: [ 1911.667545] cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 19 14:03:07 Zircon kernel: [ 1911.667548] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Oct 19 14:03:07 Zircon kernel: [ 1911.667551] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> dhclient started with pid 8714
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> Activation (wlan0) Beginning IP6 addrconf.
Oct 19 14:03:07 Zircon avahi-daemon[944]: Withdrawing address record for fe80::5604:a6ff:fede:cbba on wlan0.
Oct 19 14:03:07 Zircon avahi-daemon[944]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::5604:a6ff:fede:cbba.
Oct 19 14:03:07 Zircon avahi-daemon[944]: Interface wlan0.IPv6 no longer relevant for mDNS.
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Oct 19 14:03:07 Zircon dhclient: Internet Systems Consortium DHCP Client 4.2.4
Oct 19 14:03:07 Zircon dhclient: Copyright 2004-2012 Internet Systems Consortium.
Oct 19 14:03:07 Zircon dhclient: All rights reserved.
Oct 19 14:03:07 Zircon dhclient: For info, please visit https://www.isc.org/software/dhcp/
Oct 19 14:03:07 Zircon dhclient: 
Oct 19 14:03:07 Zircon NetworkManager[909]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Oct 19 14:03:07 Zircon dhclient: Listening on LPF/wlan0/54:04:a6:de:cb:ba
Oct 19 14:03:07 Zircon dhclient: Sending on   LPF/wlan0/54:04:a6:de:cb:ba
Oct 19 14:03:07 Zircon dhclient: Sending on   Socket/fallback
Oct 19 14:03:07 Zircon dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x6713caf2)
Oct 19 14:03:07 Zircon kernel: [ 1911.918587] wlan0: Limiting TX power to 27 (27 - 0) dBm as advertised by 00:1f:33:e9:99:8a
Oct 19 14:03:08 Zircon avahi-daemon[944]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::5604:a6ff:fede:cbba.
Oct 19 14:03:08 Zircon avahi-daemon[944]: New relevant interface wlan0.IPv6 for mDNS.
Oct 19 14:03:08 Zircon avahi-daemon[944]: Registering new address record for fe80::5604:a6ff:fede:cbba on wlan0.*.
Oct 19 14:03:10 Zircon dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 (xid=0x6713caf2)
Oct 19 14:03:17 Zircon dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15 (xid=0x6713caf2)
Oct 19 14:03:27 Zircon NetworkManager[909]: <info> (wlan0): IP6 addrconf timed out or failed.
Oct 19 14:03:27 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Oct 19 14:03:27 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Oct 19 14:03:27 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Oct 19 14:03:32 Zircon dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 (xid=0x6713caf2)
Oct 19 14:03:42 Zircon dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 (xid=0x6713caf2)
Oct 19 14:03:52 Zircon NetworkManager[909]: <warn> (wlan0): DHCPv4 request timed out.
Oct 19 14:03:52 Zircon NetworkManager[909]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 8714
Oct 19 14:03:52 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Oct 19 14:03:52 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Oct 19 14:03:52 Zircon NetworkManager[909]: <info> (wlan0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Oct 19 14:03:52 Zircon NetworkManager[909]: <info> Marking connection 'Diamond' invalid.
Oct 19 14:03:52 Zircon NetworkManager[909]: <warn> Activation (wlan0) failed for connection 'Diamond'
Oct 19 14:03:52 Zircon NetworkManager[909]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Oct 19 14:03:52 Zircon NetworkManager[909]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Oct 19 14:03:52 Zircon NetworkManager[909]: <info> (wlan0): deactivating device (reason 'none') [0]
Oct 19 14:03:52 Zircon kernel: [ 1957.444402] wlan0: deauthenticating from 00:1f:33:e9:99:8a by local choice (reason=3)
Oct 19 14:03:52 Zircon wpa_supplicant[1415]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
Oct 19 14:03:52 Zircon NetworkManager[909]: <info> (wlan0): supplicant interface state: completed -> disconnected
Oct 19 14:03:52 Zircon kernel: [ 1957.468579] cfg80211: Calling CRDA to update world regulatory domain
Oct 19 14:03:52 Zircon kernel: [ 1957.475397] cfg80211: World regulatory domain updated:
Oct 19 14:03:52 Zircon kernel: [ 1957.475404] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 19 14:03:52 Zircon kernel: [ 1957.475410] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 19 14:03:52 Zircon kernel: [ 1957.475414] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 19 14:03:52 Zircon kernel: [ 1957.475419] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Oct 19 14:03:52 Zircon kernel: [ 1957.475423] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 19 14:03:52 Zircon kernel: [ 1957.475427] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

Alguém tem alguma ideia?

    
por ChrisN 19.10.2013 / 03:25

5 respostas

0

Isso não é realmente uma resposta, é uma solução. Parece que, como já foi notado, o driver incluído no kernel em 13.10 está com defeito. Eu instalei a versão do kernel 3.8.13-03081312-generic do link e inicializei a partir dele. Meu wireless está funcionando bem agora.

Edit: O driver no kernel 3.9.11-030911-generic também funciona, e é isso que estou usando agora.

E ainda outra atualização: o Kernel 3.12.0-031200-generic corrigiu o problema.

    
por ChrisN 05.11.2013 / 00:00
1

Eu tive exatamente o mesmo problema e encontrei uma correção bastante artificial: remasterizar o live CD. Em uma instalação do Ubuntu eu instalei o Ubuntu Customization Kit (UCK) e usei para personalizar o ISO original do Kubuntu 13.10. Basicamente, o UCK chroots no ISO e permite que você o personalize. Eu comecei o UCK e pedi para me dar acesso a um console, então eu modifiquei o /etc/apt/sources.list e adicionei esta linha:

deb http://archive.ubuntu.com/ubuntu/ saucy-proposed main restricted universe multiverse

para permitir o download dos pacotes mais recentes (instáveis). Então eu corri apt-get update e apt-get dist-upgrade , que instalou, entre os outros, plasma-nm e outros pacotes relacionados à rede. Então terminei a sessão do UCK e construí um novo ISO. Se eu iniciar meu sistema usando este ISO personalizado, então o DHCP não expira e, aparentemente, tudo funciona bem.

Eu posso colocar meu ISO online se alguém estiver interessado (apenas deixe um comentário, eu não quero enviar 1GB se ninguém vai usá-lo), no entanto peço que você crie seu próprio ISO porque é simples e você não precisa confiar em mim e assumir que eu não adulterei o ISO.

Lembre-se de que testei apenas o sistema em tempo real e não executei uma instalação completa. YMMV.

    
por Giuseppe Cardone 20.10.2013 / 14:31
0

Eu tive o mesmo problema ao instalar o 13.10 a partir de um ISO de construção diária. A atualização completa do sistema corrigiu o problema para mim.

Os passos que eu segui foram:

  • Use uma conexão ethernet (porque configurar manualmente sem fio é uma dor)
  • Execute dhclient eth0 para configurá-lo e verifique se a interface está ativa
  • Execute a rotina apt-get update / apt-get dist-upgrade
  • Exclua quaisquer conexões sem fio armazenadas anteriormente
  • Reinicializar

Isso resolveu o problema para mim. No entanto, de vez em quando, o Network Manager tentava assumir o controle e desconfigurar a conexão, fazendo com que o download parasse. Eu tive que cancelar o download, executar dhclient eth0 novamente e, em seguida, retomar o dist-upgrade.

Espero que funcione para você!

    
por Rohan Dhruva 19.10.2013 / 20:18
0

Existem alguns problemas com o driver incluído no 13.10. Parece estar ficando cada vez pior.

Se você se sentir aventureiro, peguei o código-fonte do driver e arrumei tudo para mim. Eu postei no Github: link

Até agora esta é a única versão do driver que eu conheço (além do pré-empacotado) que compila e trabalha no Ubuntu 13.10. Existem instruções de instalação no arquivo README.md .

    
por Freedom_Ben 29.10.2013 / 00:00
-1

Você pode tentar usar esse script que eu criei na rede:

bin / sh

Caso! [%] em       .bin / sh       nmcli nm sleep = false 'rede'   Caso final

e pode funcionar bem assim.

    
por Michael 29.08.2014 / 16:21