#1 Le 16/08/2018, à 08:40
- Shadufi
[Résolu] Ubuntu 18.04 - Wifi détecter mais impossible de s'y connecter
Bonjour à tous, si je crée cette discussion c'est que j'ai écumé pendant 3 jours tout les forums possible et inimaginable pour résoudre mon problème.
Je vous explique :
J'ai décider de passer sur Ubuntu 18.04. Alors que j'ai, sur Windows, crée une clé usb bootable afin d'installer Ubuntu.
L'installation fini (sans l'utilisation du wifi) je décide de me connecter a la wifi pour faire les mises à jours ... Le drame commence
Après quelque minute d'attente un message d'erreur apparaît :
L'activation de la connexion a échoué
je regarde donc les log :
tail /var/log/syslog -f
et voici le résultat :
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.3922] device (wlo1): Activation: starting connection 'takamori' (7e687d26-2b32-4bcf-ad9f-1254a05aa748)
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.3930] audit: op="connection-activate" uuid="7e687d26-2b32-4bcf-ad9f-1254a05aa748" name="takamori" pid=1249 uid=1000 result="success"
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.3939] device (wlo1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.3947] manager: NetworkManager state is now CONNECTING
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.3974] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.3997] device (wlo1): Activation: (wifi) access point 'takamori' has security, but secrets are required.
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.3998] device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.4004] sup-iface[0x55736d094240,wlo1]: wps: type pbc start...
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.4123] device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.4130] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.4137] device (wlo1): Activation: (wifi) connection 'takamori' has security, and secrets exist. No new secrets needed.
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.4138] Config: added 'ssid' value 'takamori'
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.4138] Config: added 'scan_ssid' value '1'
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.4138] Config: added 'bgscan' value 'simple:30:-80:86400'
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.4139] Config: added 'key_mgmt' value 'WPA-PSK'
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.4139] Config: added 'auth_alg' value 'OPEN'
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.4139] Config: added 'psk' value '<hidden>'
Aug 16 10:36:33 kilian NetworkManager[5615]: <info> [1534401393.4422] device (wlo1): supplicant interface state: ready -> scanning
Aug 16 10:36:33 kilian gnome-shell[1249]: Object St.Widget (0x559837a58440), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: == Stack trace for context 0x559834314320 ==
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #0 0x5598346d91a0 i resource:///org/gnome/shell/ui/modalDialog.js:93 (0x7f06a45f14d8 @ 22)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #1 0x7ffd20b0bca0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f06a45b5de0 @ 71)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #2 0x5598346d90e8 i resource:///org/gnome/gjs/modules/_legacy.js:39 (0x7f06a45b5b38 @ 215)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #3 0x5598346d9058 i resource:///org/gnome/shell/ui/status/network.js:781 (0x7f0688012f78 @ 409)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #4 0x7ffd20b0d010 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f06a45b5de0 @ 71)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #5 0x5598346d8fd0 i resource:///org/gnome/shell/ui/modalDialog.js:168 (0x7f06a45f1a28 @ 92)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #6 0x7ffd20b0dbf0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f06a45b5de0 @ 71)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #7 0x7ffd20b0dc70 I self-hosted:913 (0x7f06a45f12b8 @ 346)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #8 0x7ffd20b0eb70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f06a45d3b38 @ 54)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #9 0x7ffd20b0ecc0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f06a45d3bc0 @ 1626)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #10 0x7ffd20b0ed70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f06a45d3c48 @ 100)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #11 0x7ffd20b0ee00 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f06a45d3cd0 @ 10)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #12 0x7ffd20b0ee80 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f06a45d3230 @ 386)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #13 0x7ffd20b0ef30 b resource:///org/gnome/shell/ui/tweener.js:245 (0x7f06a45cf808 @ 159)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #14 0x7ffd20b0ef90 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f06a45b5de0 @ 71)
Aug 16 10:36:33 kilian org.gnome.Shell.desktop[1249]: #15 0x7ffd20b0f030 b resource:///org/gnome/shell/ui/tweener.js:220 (0x7f06a45cf780 @ 15)
Aug 16 10:36:34 kilian wpa_supplicant[716]: wlo1: SME: Trying to authenticate with 40:5a:9b:ec:50:44 (SSID='takamori' freq=2462 MHz)
Aug 16 10:36:34 kilian kernel: [ 2129.612609] wlo1: authenticate with 40:5a:9b:ec:50:44
Aug 16 10:36:34 kilian NetworkManager[5615]: <info> [1534401394.3955] device (wlo1): supplicant interface state: scanning -> authenticating
Aug 16 10:36:34 kilian kernel: [ 2129.631248] wlo1: send auth to 40:5a:9b:ec:50:44 (try 1/3)
Aug 16 10:36:34 kilian wpa_supplicant[716]: wlo1: Trying to associate with 40:5a:9b:ec:50:44 (SSID='takamori' freq=2462 MHz)
Aug 16 10:36:34 kilian kernel: [ 2129.637159] wlo1: authenticated
Aug 16 10:36:34 kilian kernel: [ 2129.638889] wlo1: associate with 40:5a:9b:ec:50:44 (try 1/3)
Aug 16 10:36:34 kilian NetworkManager[5615]: <info> [1534401394.4072] device (wlo1): supplicant interface state: authenticating -> associating
Aug 16 10:36:34 kilian wpa_supplicant[716]: wlo1: Associated with 40:5a:9b:ec:50:44
Aug 16 10:36:34 kilian wpa_supplicant[716]: wlo1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Aug 16 10:36:34 kilian wpa_supplicant[716]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Aug 16 10:36:34 kilian kernel: [ 2129.644164] wlo1: RX AssocResp from 40:5a:9b:ec:50:44 (capab=0x431 status=0 aid=8)
Aug 16 10:36:34 kilian kernel: [ 2129.644332] wlo1: associated
Aug 16 10:36:34 kilian NetworkManager[5615]: <info> [1534401394.4149] device (wlo1): supplicant interface state: associating -> 4-way handshake
Aug 16 10:36:34 kilian wpa_supplicant[716]: wlo1: WPA: Key negotiation completed with 40:5a:9b:ec:50:44 [PTK=CCMP GTK=TKIP]
Aug 16 10:36:34 kilian wpa_supplicant[716]: wlo1: CTRL-EVENT-CONNECTED - Connection to 40:5a:9b:ec:50:44 completed [id=0 id_str=]
Aug 16 10:36:34 kilian wpa_supplicant[716]: bgscan simple: Failed to enable signal strength monitoring
Aug 16 10:36:34 kilian kernel: [ 2129.652656] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
Aug 16 10:36:34 kilian NetworkManager[5615]: <info> [1534401394.4214] device (wlo1): supplicant interface state: 4-way handshake -> completed
Aug 16 10:36:34 kilian NetworkManager[5615]: <info> [1534401394.4215] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'takamori'.
Aug 16 10:36:34 kilian NetworkManager[5615]: <info> [1534401394.4216] device (wlo1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 16 10:36:34 kilian NetworkManager[5615]: <info> [1534401394.4224] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
Aug 16 10:36:34 kilian NetworkManager[5615]: <info> [1534401394.4237] dhcp4 (wlo1): dhclient started with pid 5640
Aug 16 10:36:34 kilian dhclient[5640]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 3 (xid=0xc6ed7b6b)
Aug 16 10:36:35 kilian avahi-daemon[727]: Joining mDNS multicast group on interface wlo1.IPv6 with address fe80::56b4:c092:2d49:c8c5.
Aug 16 10:36:35 kilian avahi-daemon[727]: New relevant interface wlo1.IPv6 for mDNS.
Aug 16 10:36:35 kilian avahi-daemon[727]: Registering new address record for fe80::56b4:c092:2d49:c8c5 on wlo1.*.
Aug 16 10:36:37 kilian dhclient[5640]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 4 (xid=0xc6ed7b6b)
Aug 16 10:36:37 kilian chromium-browser.desktop[2205]: [2205:2218:0816/103637.453092:ERROR:connection_factory_impl.cc(403)] Failed to connect to MCS endpoint with error -105
Aug 16 10:36:37 kilian chromium-browser.desktop[2205]: [2205:4282:0816/103637.455561:ERROR:get_updates_processor.cc(243)] PostClientToServerMessage() failed during GetUpdates
Aug 16 10:36:41 kilian dhclient[5640]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 7 (xid=0xc6ed7b6b)
Aug 16 10:36:48 kilian dhclient[5640]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 11 (xid=0xc6ed7b6b)
Aug 16 10:36:52 kilian chromium-browser.desktop[2205]: [2205:4282:0816/103652.679728:ERROR:get_updates_processor.cc(243)] PostClientToServerMessage() failed during GetUpdates
Aug 16 10:36:59 kilian dhclient[5640]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 18 (xid=0xc6ed7b6b)
Aug 16 10:37:17 kilian dhclient[5640]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 21 (xid=0xc6ed7b6b)
Aug 16 10:37:19 kilian NetworkManager[5615]: <warn> [1534401439.9404] dhcp4 (wlo1): request timed out
Aug 16 10:37:19 kilian NetworkManager[5615]: <info> [1534401439.9405] dhcp4 (wlo1): state changed unknown -> timeout
Aug 16 10:37:19 kilian NetworkManager[5615]: <info> [1534401439.9575] dhcp4 (wlo1): canceled DHCP transaction, DHCP client pid 5640
Aug 16 10:37:19 kilian NetworkManager[5615]: <info> [1534401439.9576] dhcp4 (wlo1): state changed timeout -> done
Aug 16 10:37:19 kilian NetworkManager[5615]: <info> [1534401439.9581] device (wlo1): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Aug 16 10:37:19 kilian NetworkManager[5615]: <info> [1534401439.9585] manager: NetworkManager state is now DISCONNECTED
Aug 16 10:37:19 kilian NetworkManager[5615]: <warn> [1534401439.9593] device (wlo1): Activation: failed for connection 'takamori'
Aug 16 10:37:19 kilian NetworkManager[5615]: <info> [1534401439.9605] device (wlo1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 16 10:37:19 kilian avahi-daemon[727]: Withdrawing address record for fe80::56b4:c092:2d49:c8c5 on wlo1.
Aug 16 10:37:19 kilian avahi-daemon[727]: Leaving mDNS multicast group on interface wlo1.IPv6 with address fe80::56b4:c092:2d49:c8c5.
Aug 16 10:37:19 kilian avahi-daemon[727]: Interface wlo1.IPv6 no longer relevant for mDNS.
Aug 16 10:37:19 kilian kernel: [ 2175.205136] wlo1: deauthenticating from 40:5a:9b:ec:50:44 by local choice (Reason: 3=DEAUTH_LEAVING)
Aug 16 10:37:19 kilian gnome-shell[900]: An active wireless connection, in infrastructure mode, involves no access point?
Aug 16 10:37:19 kilian wpa_supplicant[716]: wlo1: CTRL-EVENT-DISCONNECTED bssid=40:5a:9b:ec:50:44 reason=3 locally_generated=1
Aug 16 10:37:19 kilian NetworkManager[5615]: <warn> [1534401439.9841] sup-iface[0x55736d094240,wlo1]: connection disconnected (reason -3)
Aug 16 10:37:19 kilian wpa_supplicant[716]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Aug 16 10:37:19 kilian NetworkManager[5615]: <info> [1534401439.9842] device (wlo1): supplicant interface state: completed -> disconnected
Aug 16 10:37:19 kilian gnome-shell[1249]: An active wireless connection, in infrastructure mode, involves no access point?
Aug 16 10:37:20 kilian chromium-browser.desktop[2205]: [2205:2218:0816/103720.478430:ERROR:connection_factory_impl.cc(403)] Failed to connect to MCS endpoint with error -106
Bizarrement, j'arrive a me connecter via port usb(avec mon téléphone) ou via Rj45 ...
Aidez moi s'il vous plait je ne sais plus quoi faire ...
[Résolution]
Vu la carte wifi :
Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723]
Regarde au § 2 et début du § 3 (documentation) > [Tuto] Pas de Wi-fi ? Eléments importants à vérifier pour désactiver le secure-boot.
Pour le réglage d'antenne > [Résolu]Pas de connexion wifi RTL8723BE Livebox et Ubuntu 16.04.
Il faut passer sur un chiffrement WPA2 seul, comme indiqué au § 1 > [Tuto] Pas de Wi-fi ? Eléments importants à vérifier.
Dernière modification par Shadufi (Le 16/08/2018, à 11:41)
Hors ligne
#2 Le 16/08/2018, à 08:43
- xubu1957
Re : [Résolu] Ubuntu 18.04 - Wifi détecter mais impossible de s'y connecter
Bonjour,
Il faut donner, connecté en filaire, un wificheck rassemblant les informations > Configuration wifi.
Nota : un fichier wificheck.log est créé dans votre répertoire personnel, collez l'intégralité de son contenu dans votre discussion.
Astuce pour copier / coller sans erreur :
triple clic gauche pour sélectionner et copier une ligne entière
clic molette pour coller dans le terminal
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#3 Le 16/08/2018, à 09:01
- Shadufi
Re : [Résolu] Ubuntu 18.04 - Wifi détecter mais impossible de s'y connecter
>> cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
>> lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 007: ID 0fce:71e0 Sony Ericsson Mobile Communications AB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> lspci -k -nn | grep -A 3 -i net
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723]
Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:804c]
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be, wl
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 0a)
Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet controller [103c:80a5]
Kernel driver in use: r8169
Kernel modules: r8169
>> sudo lshw -C network
*-network
description: Interface réseau sans fil
produit: RTL8723BE PCIe Wireless Network Adapter
fabriquant: Realtek Semiconductor Co., Ltd.
identifiant matériel: 0
information bus: pci@0000:03:00.0
nom logique: wlo1
version: 00
numéro de série: 68:14:01:23:02:4b
bits: 64 bits
horloge: 33MHz
fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=rtl8723be driverversion=4.15.0-32-generic firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11
ressources: irq:17 portE/S:4000(taille=256) mémoire:94100000-94103fff
*-network
description: Ethernet interface
produit: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
fabriquant: Realtek Semiconductor Co., Ltd.
identifiant matériel: 0
information bus: pci@0000:04:00.0
nom logique: eno1
version: 0a
numéro de série: 70:5a:0f:1c:bf:06
taille: 10Mbit/s
capacité: 100Mbit/s
bits: 64 bits
horloge: 33MHz
fonctionnalités: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8107e-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII speed=10Mbit/s
ressources: irq:16 portE/S:3000(taille=256) mémoire:94004000-94004fff mémoire:94000000-94003fff
*-network
description: Ethernet interface
identifiant matériel: 3
nom logique: enp0s20f0u1
numéro de série: da:08:aa:b4:80:d4
fonctionnalités: ethernet physical
configuration: broadcast=yes driver=rndis_host driverversion=22-Aug-2005 firmware=RNDIS device ip=192.168.42.19 link=yes multicast=yes
>> lsmod
Module Size Used by
rndis_host 16384 0
cdc_ether 16384 1 rndis_host
usbnet 45056 2 rndis_host,cdc_ether
ccm 20480 0
rfcomm 77824 4
cmac 16384 1
bnep 20480 2
nls_iso8859_1 16384 1
intel_rapl 20480 0
x86_pkg_temp_thermal 16384 0
intel_powerclamp 16384 0
coretemp 16384 0
wl 6447104 0
kvm 593920 0
irqbypass 16384 1 kvm
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
ghash_clmulni_intel 16384 0
arc4 16384 2
snd_hda_codec_hdmi 49152 1
pcbc 16384 0
rtl8723be 98304 0
snd_soc_skl 90112 0
aesni_intel 188416 2
snd_soc_skl_ipc 65536 1 snd_soc_skl
btcoexist 131072 1 rtl8723be
aes_x86_64 20480 1 aesni_intel
snd_hda_ext_core 24576 1 snd_soc_skl
rtl8723_common 24576 1 rtl8723be
crypto_simd 16384 1 aesni_intel
rtl_pci 32768 1 rtl8723be
snd_soc_sst_dsp 32768 1 snd_soc_skl_ipc
snd_hda_codec_realtek 94208 1
snd_hda_codec_generic 73728 1 snd_hda_codec_realtek
glue_helper 16384 1 aesni_intel
snd_soc_sst_ipc 16384 1 snd_soc_skl_ipc
rtlwifi 77824 4 rtl_pci,btcoexist,rtl8723_common,rtl8723be
snd_soc_acpi 16384 1 snd_soc_skl
mac80211 778240 3 rtl_pci,rtlwifi,rtl8723be
snd_soc_core 241664 1 snd_soc_skl
snd_compress 20480 1 snd_soc_core
ac97_bus 16384 1 snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
cryptd 24576 3 crypto_simd,ghash_clmulni_intel,aesni_intel
cfg80211 622592 3 wl,mac80211,rtlwifi
intel_cstate 20480 0
intel_rapl_perf 16384 0
joydev 24576 0
snd_hda_intel 40960 6
hp_wmi 16384 0
input_leds 16384 0
serio_raw 16384 0
sparse_keymap 16384 1 hp_wmi
snd_hda_codec 126976 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
rtsx_pci_ms 20480 0
uvcvideo 86016 0
videobuf2_vmalloc 16384 1 uvcvideo
videobuf2_memops 16384 1 videobuf2_vmalloc
btusb 45056 0
btrtl 16384 1 btusb
btbcm 16384 1 btusb
videobuf2_v4l2 24576 1 uvcvideo
memstick 16384 1 rtsx_pci_ms
snd_hda_core 81920 7 snd_hda_intel,snd_hda_codec,snd_hda_ext_core,snd_soc_skl,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
wmi_bmof 16384 0
snd_hwdep 20480 1 snd_hda_codec
videobuf2_core 40960 2 uvcvideo,videobuf2_v4l2
videodev 184320 3 uvcvideo,videobuf2_core,videobuf2_v4l2
media 40960 2 uvcvideo,videodev
btintel 16384 1 btusb
bluetooth 548864 33 btrtl,btintel,bnep,btbcm,rfcomm,btusb
ecdh_generic 24576 2 bluetooth
snd_pcm 98304 8 snd_hda_intel,snd_hda_codec,snd_pcm_dmaengine,snd_hda_ext_core,snd_hda_core,snd_soc_skl,snd_hda_codec_hdmi,snd_soc_core
mei_me 40960 0
snd_seq_midi 16384 0
snd_seq_midi_event 16384 1 snd_seq_midi
mei 90112 1 mei_me
snd_rawmidi 32768 1 snd_seq_midi
hp_accel 28672 0
lis3lv02d 20480 1 hp_accel
input_polldev 16384 1 lis3lv02d
shpchp 36864 0
snd_seq 65536 2 snd_seq_midi_event,snd_seq_midi
snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer 32768 2 snd_seq,snd_pcm
mac_hid 16384 0
snd 81920 25 snd_compress,snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_seq_device,snd_hda_codec_realtek,snd_soc_core,snd_pcm
hp_wireless 16384 0
acpi_pad 180224 0
processor_thermal_device 16384 0
int3400_thermal 16384 0
int340x_thermal_zone 16384 1 processor_thermal_device
intel_soc_dts_iosf 16384 1 processor_thermal_device
intel_pch_thermal 16384 0
acpi_thermal_rel 16384 1 int3400_thermal
soundcore 16384 1 snd
tpm_crb 16384 0
sch_fq_codel 20480 7
parport_pc 36864 0
ppdev 20480 0
lp 20480 0
parport 49152 3 lp,parport_pc,ppdev
ip_tables 28672 0
x_tables 40960 1 ip_tables
autofs4 40960 2
nouveau 1716224 1
rtsx_pci_sdmmc 24576 0
i915 1617920 32
mxm_wmi 16384 1 nouveau
i2c_algo_bit 16384 2 nouveau,i915
ttm 106496 1 nouveau
drm_kms_helper 172032 2 nouveau,i915
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops 16384 1 drm_kms_helper
drm 401408 20 nouveau,i915,ttm,drm_kms_helper
r8169 86016 0
ahci 36864 2
rtsx_pci 65536 2 rtsx_pci_sdmmc,rtsx_pci_ms
psmouse 147456 0
mii 16384 2 r8169,usbnet
libahci 32768 1 ahci
wmi 24576 4 wmi_bmof,mxm_wmi,nouveau,hp_wmi
video 45056 2 nouveau,i915
>> iwconfig
wlo1 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short limit:7 RTS thr=2347 B Fragment thr:off
Power Management:off
>> ifconfig -a
eno1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 70:5a:0f:1c:bf:06 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp0s20f0u1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.42.19 netmask 255.255.255.0 broadcast 192.168.42.255
inet6 fe80::4738:6090:2217:ea5b prefixlen 64 scopeid 0x20<link>
ether da:08:aa:b4:80:d4 txqueuelen 1000 (Ethernet)
RX packets 6834 bytes 7343837 (7.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5571 bytes 818698 (818.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Boucle locale)
RX packets 1722 bytes 143716 (143.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1722 bytes 143716 (143.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlo1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 68:14:01:23:02:4b txqueuelen 1000 (Ethernet)
RX packets 7 bytes 1103 (1.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 95 bytes 17018 (17.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>> sudo iwlist scan
wlo1 No scan results
>> uname -r -m
4.15.0-32-generic x86_64
>> cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
>> nm-tool
>> nmcli dev wifi
IN-USE SSID MODE CHAN RATE SIGNAL BARS SECURITY
takamori Infra 11 130 Mo/s 37 ▂▄__ WPA1 WPA2
>> nmcli connection list (< 15.04) ou nmcli connection show (>= 15.04)
NAME UUID TYPE DEVICE
Connexion filaire 2 a97754c1-661b-3234-a21a-e100f17cc06a ethernet enp0s20f0u1
CANALBOX-7E21C0 2ec9e45b-6903-4b6d-997e-542556c7a84d wifi --
Connexion filaire 1 f8c63540-a55d-39e0-8388-24a05c3a3e12 ethernet --
Salon.o 149a1de9-7416-421e-af62-76bea9e9519a wifi --
takamori 7e687d26-2b32-4bcf-ad9f-1254a05aa748 wifi --
>> nmcli connection status
>> sudo rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Hors ligne
#4 Le 16/08/2018, à 09:25
- xubu1957
Re : [Résolu] Ubuntu 18.04 - Wifi détecter mais impossible de s'y connecter
Vu la carte wifi :
Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723]
Regarde au § 2 et début du § 3 (documentation) > [Tuto] Pas de Wi-fi ? Eléments importants à vérifier pour désactiver le secure-boot.
Pour le réglage d'antenne > [Résolu]Pas de connexion wifi RTL8723BE Livebox et Ubuntu 16.04.
Il faut passer sur un chiffrement WPA2 seul, comme indiqué au § 1 > [Tuto] Pas de Wi-fi ? Eléments importants à vérifier.
Dernière modification par xubu1957 (Le 16/08/2018, à 09:31)
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne
#5 Le 16/08/2018, à 11:35
- Shadufi
Re : [Résolu] Ubuntu 18.04 - Wifi détecter mais impossible de s'y connecter
MERCIIII !!! Ça fonctionne ! c'était un soucis d'antenne !!
Hors ligne
#6 Le 16/08/2018, à 11:36
- xubu1957
Re : [Résolu] Ubuntu 18.04 - Wifi détecter mais impossible de s'y connecter
Pour éditer ta discussion et rajouter [Résolu] au début du titre, il faut utiliser le bouton Modifier au bas de ton premier message.
Merci
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
Hors ligne