Fedora-Fr - Communauté francophone Fedora - Linux

Communauté francophone des utilisateurs de la distribution Linux Fedora.

  

Dernière news : [Appel à participation] Paris Open Source Summit 2018

#1 17/11/2017 11:07:33

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Wifi déraille quand Mr Bluetooth démarre

Salut à toutes et à tous,

Je me suis dernièrement payé une enceinte bluetooth. C'est donc la première fois que j'utilise le BT de mon PC. Le souci c'est que quand j'utilise le bluetooth de mon pc, le Wifi déconne quelques temps après et l'icone de wifi se transforme en point d'interrogation. C'était le cas sous F26 et c'est toujours le cqs avec F27.

Quelqu'un aurait une idée de la manière dont je pourrais savoir ce qui lui arrive ?

Voici ce que me renvoie lspci :

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM86 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1)
04:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10)
05:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723AE PCIe Wireless Network Adapter

Par avance, merci


"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#2 17/11/2017 11:13:05

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

En faisant tourner les logs en même temps tu vois des choses ?

# journalctl -f

F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

#3 17/11/2017 11:25:47

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Ok, voilà le pavé wink mais a priori le problème est redondant :  "rtlwifi: AP off, try to reconnect now" semble être le début des ennuis de wifi

Nov 17 10:14:22 linux.home gnome-shell[1876]: Received error from DBus search provider org.gnome.Calendar.desktop: Gio.IOErrorEnum: Timeout was reached
Nov 17 10:14:30 linux.home dbus-daemon[1805]: [session uid=1000 pid=1805] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.152' (uid=1000 pid=7771 comm="gnome-control-center bluetooth " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
Nov 17 10:14:30 linux.home dbus-daemon[1805]: [session uid=1000 pid=1805] Activation via systemd failed for unit 'dbus-org.bluez.obex.service': Unit dbus-org.bluez.obex.service not found.
Nov 17 10:14:30 linux.home gnome-shell[1876]: setup_framebuffers: assertion 'width > 0' failed
Nov 17 10:14:38 linux.home bluetoothd[826]: connect error: Host is down (112)
Nov 17 10:14:57 linux.home kernel: input: 04:52:C7:EF:43:8F as /devices/virtual/input/input18
Nov 17 10:14:57 linux.home systemd-logind[821]: Watching system buttons on /dev/input/event16 (04:52:C7:EF:43:8F)
Nov 17 10:14:57 linux.home dbus-daemon[829]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.0" (uid=0 pid=821 comm="/usr/lib/systemd/systemd-logind " label="system_u:system_r:systemd_logind_t:s0") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.50" (uid=1000 pid=1876 comm="/usr/bin/gnome-shell " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
Nov 17 10:15:00 linux.home bluetoothd[826]: /org/bluez/hci0/dev_04_52_C7_EF_43_8F/fd1: fd(24) ready
Nov 17 10:15:00 linux.home rtkit-daemon[857]: Supervising 6 threads of 2 processes of 2 users.
Nov 17 10:15:00 linux.home rtkit-daemon[857]: Successfully made thread 7826 of process 1953 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Nov 17 10:15:00 linux.home rtkit-daemon[857]: Supervising 7 threads of 2 processes of 2 users.
Nov 17 10:15:03 linux.home gnome-shell[1876]: [Gnome Email Notifications] Checking mail
Nov 17 10:15:03 linux.home dbus-daemon[1805]: [session uid=1000 pid=1805] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.152' (uid=1000 pid=7771 comm="gnome-control-center bluetooth " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
Nov 17 10:15:03 linux.home dbus-daemon[1805]: [session uid=1000 pid=1805] Activation via systemd failed for unit 'dbus-org.bluez.obex.service': Unit dbus-org.bluez.obex.service not found.
Nov 17 10:15:30 linux.home avahi-daemon[853]: Registering new address record for fe80::47fa:575e:81b:d372 on wlp5s0.*.
Nov 17 10:15:38 linux.home kernel: rtlwifi: AP off, try to reconnect now
Nov 17 10:15:38 linux.home kernel: wlp5s0: Connection to AP e4:3e:d7:aa:80:ab lost
Nov 17 10:15:38 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=e4:3e:d7:aa:80:ab reason=4 locally_generated=1
Nov 17 10:15:38 linux.home NetworkManager[940]: <warn>  [1510910138.6814] sup-iface[0x5635b83ad0a0,wlp5s0]: connection disconnected (reason -4)
Nov 17 10:15:38 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 17 10:15:38 linux.home NetworkManager[940]: <info>  [1510910138.6905] device (wlp5s0): supplicant interface state: completed -> disconnected
Nov 17 10:15:38 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Nov 17 10:15:38 linux.home NetworkManager[940]: <info>  [1510910138.7868] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:15:39 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:15:39 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:15:39 linux.home NetworkManager[940]: <info>  [1510910139.8267] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:15:39 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:15:39 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:15:39 linux.home kernel: wlp5s0: authenticated
Nov 17 10:15:39 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:15:39 linux.home NetworkManager[940]: <info>  [1510910139.8367] device (wlp5s0): supplicant interface state: authenticating -> associating
Nov 17 10:15:39 linux.home wpa_supplicant[1093]: wlp5s0: Associated with e4:3e:d7:aa:80:ab
Nov 17 10:15:39 linux.home kernel: wlp5s0: RX AssocResp from e4:3e:d7:aa:80:ab (capab=0x411 status=0 aid=2)
Nov 17 10:15:39 linux.home kernel: wlp5s0: associated
Nov 17 10:15:39 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 17 10:15:39 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Nov 17 10:15:39 linux.home NetworkManager[940]: <info>  [1510910139.8680] device (wlp5s0): supplicant interface state: associating -> 4-way handshake
Nov 17 10:15:39 linux.home wpa_supplicant[1093]: wlp5s0: WPA: Key negotiation completed with e4:3e:d7:aa:80:ab [PTK=CCMP GTK=TKIP]
Nov 17 10:15:39 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to e4:3e:d7:aa:80:ab completed [id=0 id_str=]
Nov 17 10:15:39 linux.home NetworkManager[940]: <info>  [1510910139.8956] device (wlp5s0): supplicant interface state: 4-way handshake -> completed
Nov 17 10:15:57 linux.home kernel: rtlwifi: AP off, try to reconnect now
Nov 17 10:15:57 linux.home kernel: wlp5s0: Connection to AP e4:3e:d7:aa:80:ab lost
Nov 17 10:15:57 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=e4:3e:d7:aa:80:ab reason=4 locally_generated=1
Nov 17 10:15:57 linux.home NetworkManager[940]: <warn>  [1510910157.1134] sup-iface[0x5635b83ad0a0,wlp5s0]: connection disconnected (reason -4)
Nov 17 10:15:57 linux.home NetworkManager[940]: <info>  [1510910157.1190] device (wlp5s0): supplicant interface state: completed -> disconnected
Nov 17 10:15:57 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 17 10:15:57 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Nov 17 10:15:57 linux.home NetworkManager[940]: <info>  [1510910157.2187] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:15:58 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:15:58 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:15:58 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:15:58 linux.home NetworkManager[940]: <info>  [1510910158.2589] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:15:58 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:15:58 linux.home kernel: wlp5s0: authenticated
Nov 17 10:15:58 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:15:58 linux.home NetworkManager[940]: <info>  [1510910158.2654] device (wlp5s0): supplicant interface state: authenticating -> associating
Nov 17 10:15:58 linux.home wpa_supplicant[1093]: wlp5s0: Associated with e4:3e:d7:aa:80:ab
Nov 17 10:15:58 linux.home kernel: wlp5s0: RX AssocResp from e4:3e:d7:aa:80:ab (capab=0x411 status=0 aid=2)
Nov 17 10:15:58 linux.home kernel: wlp5s0: associated
Nov 17 10:15:58 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 17 10:15:58 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Nov 17 10:15:58 linux.home NetworkManager[940]: <info>  [1510910158.2722] device (wlp5s0): supplicant interface state: associating -> associated
Nov 17 10:15:58 linux.home NetworkManager[940]: <info>  [1510910158.2990] device (wlp5s0): supplicant interface state: associated -> 4-way handshake
Nov 17 10:15:58 linux.home wpa_supplicant[1093]: wlp5s0: WPA: Key negotiation completed with e4:3e:d7:aa:80:ab [PTK=CCMP GTK=TKIP]
Nov 17 10:15:58 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to e4:3e:d7:aa:80:ab completed [id=0 id_str=]
Nov 17 10:15:58 linux.home NetworkManager[940]: <info>  [1510910158.3137] device (wlp5s0): supplicant interface state: 4-way handshake -> completed
Nov 17 10:16:03 linux.home gnome-shell[1876]: [Gnome Email Notifications] Checking mail
Nov 17 10:16:07 linux.home kernel: rtlwifi: AP off, try to reconnect now
Nov 17 10:16:07 linux.home kernel: wlp5s0: Connection to AP e4:3e:d7:aa:80:ab lost
Nov 17 10:16:07 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=e4:3e:d7:aa:80:ab reason=4 locally_generated=1
Nov 17 10:16:07 linux.home NetworkManager[940]: <warn>  [1510910167.3515] sup-iface[0x5635b83ad0a0,wlp5s0]: connection disconnected (reason -4)
Nov 17 10:16:07 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 17 10:16:07 linux.home NetworkManager[940]: <info>  [1510910167.3590] device (wlp5s0): supplicant interface state: completed -> disconnected
Nov 17 10:16:07 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Nov 17 10:16:07 linux.home NetworkManager[940]: <info>  [1510910167.4572] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:16:08 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:16:08 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:16:08 linux.home NetworkManager[940]: <info>  [1510910168.4968] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:16:08 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:16:08 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:16:08 linux.home kernel: wlp5s0: authenticated
Nov 17 10:16:08 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:16:08 linux.home NetworkManager[940]: <info>  [1510910168.5070] device (wlp5s0): supplicant interface state: authenticating -> associating
Nov 17 10:16:08 linux.home kernel: wlp5s0: RX AssocResp from e4:3e:d7:aa:80:ab (capab=0x411 status=0 aid=2)
Nov 17 10:16:08 linux.home wpa_supplicant[1093]: wlp5s0: Associated with e4:3e:d7:aa:80:ab
Nov 17 10:16:08 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 17 10:16:08 linux.home kernel: wlp5s0: associated
Nov 17 10:16:08 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Nov 17 10:16:08 linux.home NetworkManager[940]: <info>  [1510910168.5145] device (wlp5s0): supplicant interface state: associating -> associated
Nov 17 10:16:08 linux.home NetworkManager[940]: <info>  [1510910168.5420] device (wlp5s0): supplicant interface state: associated -> 4-way handshake
Nov 17 10:16:08 linux.home wpa_supplicant[1093]: wlp5s0: WPA: Key negotiation completed with e4:3e:d7:aa:80:ab [PTK=CCMP GTK=TKIP]
Nov 17 10:16:08 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to e4:3e:d7:aa:80:ab completed [id=0 id_str=]
Nov 17 10:16:08 linux.home NetworkManager[940]: <info>  [1510910168.5548] device (wlp5s0): supplicant interface state: 4-way handshake -> completed
Nov 17 10:16:10 linux.home chrome-hmjkmjkepdijhoojdojkdfohbdgmmhki-Default.desktop[4567]: [4567:4601:1117/101610.967601:ERROR:ssl_client_socket_impl.cc(1129)] handshake failed; returned -1, SSL error code 1, net_error -100
Nov 17 10:16:10 linux.home chrome-hmjkmjkepdijhoojdojkdfohbdgmmhki-Default.desktop[4567]: [4567:4601:1117/101610.967962:ERROR:connection_factory_impl.cc(386)] Failed to connect to MCS endpoint with error -100
Nov 17 10:16:35 linux.home kernel: rtlwifi: AP off, try to reconnect now
Nov 17 10:16:35 linux.home kernel: wlp5s0: Connection to AP e4:3e:d7:aa:80:ab lost
Nov 17 10:16:36 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=e4:3e:d7:aa:80:ab reason=4 locally_generated=1
Nov 17 10:16:36 linux.home NetworkManager[940]: <warn>  [1510910196.0305] sup-iface[0x5635b83ad0a0,wlp5s0]: connection disconnected (reason -4)
Nov 17 10:16:36 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 17 10:16:36 linux.home NetworkManager[940]: <info>  [1510910196.0397] device (wlp5s0): supplicant interface state: completed -> disconnected
Nov 17 10:16:36 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Nov 17 10:16:36 linux.home NetworkManager[940]: <info>  [1510910196.1359] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:16:37 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:16:37 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:16:37 linux.home kernel: perf: interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
Nov 17 10:16:37 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:16:37 linux.home NetworkManager[940]: <info>  [1510910197.1749] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:16:37 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:16:37 linux.home kernel: wlp5s0: authenticated
Nov 17 10:16:37 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:16:37 linux.home NetworkManager[940]: <info>  [1510910197.2165] device (wlp5s0): supplicant interface state: authenticating -> associating
Nov 17 10:16:37 linux.home kernel: wlp5s0: RX AssocResp from e4:3e:d7:aa:80:ab (capab=0x411 status=0 aid=2)
Nov 17 10:16:37 linux.home kernel: wlp5s0: associated
Nov 17 10:16:37 linux.home wpa_supplicant[1093]: wlp5s0: Associated with e4:3e:d7:aa:80:ab
Nov 17 10:16:37 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 17 10:16:37 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Nov 17 10:16:37 linux.home NetworkManager[940]: <info>  [1510910197.3151] device (wlp5s0): supplicant interface state: associating -> associated
Nov 17 10:16:37 linux.home NetworkManager[940]: <info>  [1510910197.3319] device (wlp5s0): supplicant interface state: associated -> 4-way handshake
Nov 17 10:16:37 linux.home wpa_supplicant[1093]: wlp5s0: WPA: Key negotiation completed with e4:3e:d7:aa:80:ab [PTK=CCMP GTK=TKIP]
Nov 17 10:16:37 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to e4:3e:d7:aa:80:ab completed [id=0 id_str=]
Nov 17 10:16:37 linux.home NetworkManager[940]: <info>  [1510910197.3882] device (wlp5s0): supplicant interface state: 4-way handshake -> completed
Nov 17 10:16:55 linux.home Franz.desktop[2354]: ####### appdata settings saved #######
Nov 17 10:17:02 linux.home kernel: rtlwifi: AP off, try to reconnect now
Nov 17 10:17:02 linux.home kernel: wlp5s0: Connection to AP e4:3e:d7:aa:80:ab lost
Nov 17 10:17:02 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=e4:3e:d7:aa:80:ab reason=4 locally_generated=1
Nov 17 10:17:02 linux.home NetworkManager[940]: <warn>  [1510910222.6510] sup-iface[0x5635b83ad0a0,wlp5s0]: connection disconnected (reason -4)
Nov 17 10:17:02 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 17 10:17:02 linux.home NetworkManager[940]: <info>  [1510910222.6574] device (wlp5s0): supplicant interface state: completed -> disconnected
Nov 17 10:17:02 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Nov 17 10:17:02 linux.home NetworkManager[940]: <info>  [1510910222.7561] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:17:03 linux.home gnome-shell[1876]: [Gnome Email Notifications] Checking mail
Nov 17 10:17:03 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:17:03 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:17:03 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:17:03 linux.home NetworkManager[940]: <info>  [1510910223.7970] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:17:03 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 2/3)
Nov 17 10:17:04 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 3/3)
Nov 17 10:17:04 linux.home kernel: wlp5s0: authentication with e4:3e:d7:aa:80:ab timed out
Nov 17 10:17:04 linux.home NetworkManager[940]: <info>  [1510910224.1353] device (wlp5s0): supplicant interface state: authenticating -> disconnected
Nov 17 10:17:04 linux.home NetworkManager[940]: <info>  [1510910224.6374] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:17:05 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:17:05 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:17:05 linux.home NetworkManager[940]: <info>  [1510910225.6757] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:17:05 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:17:05 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:17:05 linux.home kernel: wlp5s0: authenticated
Nov 17 10:17:05 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:17:05 linux.home kernel: wlp5s0: RX AssocResp from e4:3e:d7:aa:80:ab (capab=0x411 status=0 aid=2)
Nov 17 10:17:05 linux.home kernel: wlp5s0: associated
Nov 17 10:17:05 linux.home wpa_supplicant[1093]: wlp5s0: Associated with e4:3e:d7:aa:80:ab
Nov 17 10:17:05 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 17 10:17:05 linux.home NetworkManager[940]: <info>  [1510910225.6831] device (wlp5s0): supplicant interface state: authenticating -> associated
Nov 17 10:17:05 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Nov 17 10:17:05 linux.home NetworkManager[940]: <info>  [1510910225.7091] device (wlp5s0): supplicant interface state: associated -> 4-way handshake
Nov 17 10:17:05 linux.home wpa_supplicant[1093]: wlp5s0: WPA: Key negotiation completed with e4:3e:d7:aa:80:ab [PTK=CCMP GTK=TKIP]
Nov 17 10:17:05 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to e4:3e:d7:aa:80:ab completed [id=0 id_str=]
Nov 17 10:17:05 linux.home NetworkManager[940]: <info>  [1510910225.7317] device (wlp5s0): supplicant interface state: 4-way handshake -> completed
Nov 17 10:17:21 linux.home kernel: rtlwifi: AP off, try to reconnect now
Nov 17 10:17:21 linux.home kernel: wlp5s0: Connection to AP e4:3e:d7:aa:80:ab lost
Nov 17 10:17:21 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=e4:3e:d7:aa:80:ab reason=4 locally_generated=1
Nov 17 10:17:21 linux.home NetworkManager[940]: <warn>  [1510910241.0859] sup-iface[0x5635b83ad0a0,wlp5s0]: connection disconnected (reason -4)
Nov 17 10:17:21 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 17 10:17:21 linux.home NetworkManager[940]: <info>  [1510910241.0915] device (wlp5s0): supplicant interface state: completed -> disconnected
Nov 17 10:17:21 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Nov 17 10:17:21 linux.home NetworkManager[940]: <info>  [1510910241.1912] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:17:22 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:17:22 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:17:22 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:17:22 linux.home NetworkManager[940]: <info>  [1510910242.2308] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:17:22 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 2/3)
Nov 17 10:17:22 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 3/3)
Nov 17 10:17:22 linux.home kernel: wlp5s0: authentication with e4:3e:d7:aa:80:ab timed out
Nov 17 10:17:22 linux.home NetworkManager[940]: <info>  [1510910242.5673] device (wlp5s0): supplicant interface state: authenticating -> disconnected
Nov 17 10:17:23 linux.home NetworkManager[940]: <info>  [1510910243.0682] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:17:24 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:17:24 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:17:24 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:17:24 linux.home NetworkManager[940]: <info>  [1510910244.1069] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:17:24 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:17:24 linux.home kernel: wlp5s0: authenticated
Nov 17 10:17:24 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:17:24 linux.home NetworkManager[940]: <info>  [1510910244.1143] device (wlp5s0): supplicant interface state: authenticating -> associating
Nov 17 10:17:24 linux.home wpa_supplicant[1093]: wlp5s0: Associated with e4:3e:d7:aa:80:ab
Nov 17 10:17:24 linux.home kernel: wlp5s0: RX AssocResp from e4:3e:d7:aa:80:ab (capab=0x411 status=0 aid=2)
Nov 17 10:17:24 linux.home kernel: wlp5s0: associated
Nov 17 10:17:24 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 17 10:17:24 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Nov 17 10:17:24 linux.home NetworkManager[940]: <info>  [1510910244.1313] device (wlp5s0): supplicant interface state: associating -> 4-way handshake
Nov 17 10:17:24 linux.home wpa_supplicant[1093]: wlp5s0: WPA: Key negotiation completed with e4:3e:d7:aa:80:ab [PTK=CCMP GTK=TKIP]
Nov 17 10:17:24 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to e4:3e:d7:aa:80:ab completed [id=0 id_str=]
Nov 17 10:17:24 linux.home NetworkManager[940]: <info>  [1510910244.1500] device (wlp5s0): supplicant interface state: 4-way handshake -> completed
Nov 17 10:17:47 linux.home kernel: rtlwifi: AP off, try to reconnect now
Nov 17 10:17:47 linux.home kernel: wlp5s0: Connection to AP e4:3e:d7:aa:80:ab lost
Nov 17 10:17:47 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=e4:3e:d7:aa:80:ab reason=4 locally_generated=1
Nov 17 10:17:47 linux.home NetworkManager[940]: <warn>  [1510910267.7064] sup-iface[0x5635b83ad0a0,wlp5s0]: connection disconnected (reason -4)
Nov 17 10:17:47 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 17 10:17:47 linux.home NetworkManager[940]: <info>  [1510910267.7171] device (wlp5s0): supplicant interface state: completed -> disconnected
Nov 17 10:17:47 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Nov 17 10:17:47 linux.home NetworkManager[940]: <info>  [1510910267.8121] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:17:48 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:17:48 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:17:48 linux.home NetworkManager[940]: <info>  [1510910268.8527] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:17:48 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:17:48 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 2/3)
Nov 17 10:17:49 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 3/3)
Nov 17 10:17:49 linux.home kernel: wlp5s0: authentication with e4:3e:d7:aa:80:ab timed out
Nov 17 10:17:49 linux.home NetworkManager[940]: <info>  [1510910269.1913] device (wlp5s0): supplicant interface state: authenticating -> disconnected
Nov 17 10:17:49 linux.home NetworkManager[940]: <info>  [1510910269.6925] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:17:50 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:17:50 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:17:50 linux.home NetworkManager[940]: <info>  [1510910270.7316] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:17:50 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:17:50 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:17:50 linux.home kernel: wlp5s0: authenticated
Nov 17 10:17:50 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:17:50 linux.home NetworkManager[940]: <info>  [1510910270.7415] device (wlp5s0): supplicant interface state: authenticating -> associating
Nov 17 10:17:50 linux.home wpa_supplicant[1093]: wlp5s0: Associated with e4:3e:d7:aa:80:ab
Nov 17 10:17:50 linux.home kernel: wlp5s0: RX AssocResp from e4:3e:d7:aa:80:ab (capab=0x411 status=0 aid=2)
Nov 17 10:17:50 linux.home kernel: wlp5s0: associated
Nov 17 10:17:50 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 17 10:17:50 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Nov 17 10:17:50 linux.home NetworkManager[940]: <info>  [1510910270.7504] device (wlp5s0): supplicant interface state: associating -> associated
Nov 17 10:17:50 linux.home NetworkManager[940]: <info>  [1510910270.7674] device (wlp5s0): supplicant interface state: associated -> 4-way handshake
Nov 17 10:17:50 linux.home wpa_supplicant[1093]: wlp5s0: WPA: Key negotiation completed with e4:3e:d7:aa:80:ab [PTK=CCMP GTK=TKIP]
Nov 17 10:17:50 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to e4:3e:d7:aa:80:ab completed [id=0 id_str=]
Nov 17 10:17:50 linux.home NetworkManager[940]: <info>  [1510910270.8143] device (wlp5s0): supplicant interface state: 4-way handshake -> completed
Nov 17 10:18:03 linux.home gnome-shell[1876]: [Gnome Email Notifications] Checking mail
Nov 17 10:18:26 linux.home kernel: rtlwifi: AP off, try to reconnect now
Nov 17 10:18:26 linux.home kernel: wlp5s0: Connection to AP e4:3e:d7:aa:80:ab lost
Nov 17 10:18:26 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=e4:3e:d7:aa:80:ab reason=4 locally_generated=1
Nov 17 10:18:26 linux.home NetworkManager[940]: <warn>  [1510910306.6262] sup-iface[0x5635b83ad0a0,wlp5s0]: connection disconnected (reason -4)
Nov 17 10:18:26 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 17 10:18:26 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Nov 17 10:18:26 linux.home NetworkManager[940]: <info>  [1510910306.6358] device (wlp5s0): supplicant interface state: completed -> disconnected
Nov 17 10:18:26 linux.home NetworkManager[940]: <info>  [1510910306.7318] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:18:27 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:18:27 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:18:27 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:18:27 linux.home NetworkManager[940]: <info>  [1510910307.7713] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:18:27 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 2/3)
Nov 17 10:18:27 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:18:27 linux.home kernel: wlp5s0: authenticated
Nov 17 10:18:27 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:18:27 linux.home NetworkManager[940]: <info>  [1510910307.9202] device (wlp5s0): supplicant interface state: authenticating -> associating
Nov 17 10:18:28 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 2/3)
Nov 17 10:18:28 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 3/3)
Nov 17 10:18:28 linux.home kernel: wlp5s0: association with e4:3e:d7:aa:80:ab timed out
Nov 17 10:18:28 linux.home NetworkManager[940]: <info>  [1510910308.2553] device (wlp5s0): supplicant interface state: associating -> disconnected
Nov 17 10:18:28 linux.home NetworkManager[940]: <info>  [1510910308.7563] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:18:29 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:18:29 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:18:29 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:18:29 linux.home NetworkManager[940]: <info>  [1510910309.7959] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:18:29 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:18:29 linux.home kernel: wlp5s0: authenticated
Nov 17 10:18:29 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:18:29 linux.home NetworkManager[940]: <info>  [1510910309.8043] device (wlp5s0): supplicant interface state: authenticating -> associating
Nov 17 10:18:29 linux.home kernel: wlp5s0: RX AssocResp from e4:3e:d7:aa:80:ab (capab=0x411 status=0 aid=2)
Nov 17 10:18:29 linux.home wpa_supplicant[1093]: wlp5s0: Associated with e4:3e:d7:aa:80:ab
Nov 17 10:18:29 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 17 10:18:29 linux.home kernel: wlp5s0: associated
Nov 17 10:18:29 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Nov 17 10:18:29 linux.home NetworkManager[940]: <info>  [1510910309.8110] device (wlp5s0): supplicant interface state: associating -> associated
Nov 17 10:18:29 linux.home NetworkManager[940]: <info>  [1510910309.8346] device (wlp5s0): supplicant interface state: associated -> 4-way handshake
Nov 17 10:18:29 linux.home wpa_supplicant[1093]: wlp5s0: WPA: Key negotiation completed with e4:3e:d7:aa:80:ab [PTK=CCMP GTK=TKIP]
Nov 17 10:18:29 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to e4:3e:d7:aa:80:ab completed [id=0 id_str=]
Nov 17 10:18:29 linux.home NetworkManager[940]: <info>  [1510910309.8506] device (wlp5s0): supplicant interface state: 4-way handshake -> completed
Nov 17 10:19:03 linux.home gnome-shell[1876]: [Gnome Email Notifications] Checking mail
Nov 17 10:19:07 linux.home kernel: rtlwifi: AP off, try to reconnect now
Nov 17 10:19:07 linux.home kernel: wlp5s0: Connection to AP e4:3e:d7:aa:80:ab lost
Nov 17 10:19:07 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=e4:3e:d7:aa:80:ab reason=4 locally_generated=1
Nov 17 10:19:07 linux.home NetworkManager[940]: <warn>  [1510910347.5743] sup-iface[0x5635b83ad0a0,wlp5s0]: connection disconnected (reason -4)
Nov 17 10:19:07 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 17 10:19:07 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Nov 17 10:19:07 linux.home NetworkManager[940]: <info>  [1510910347.5839] device (wlp5s0): supplicant interface state: completed -> disconnected
Nov 17 10:19:07 linux.home NetworkManager[940]: <info>  [1510910347.6798] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:19:08 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:19:08 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:19:08 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:19:08 linux.home NetworkManager[940]: <info>  [1510910348.7190] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:19:08 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 2/3)
Nov 17 10:19:08 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 3/3)
Nov 17 10:19:09 linux.home kernel: wlp5s0: authenticated
Nov 17 10:19:09 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:19:09 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:19:09 linux.home NetworkManager[940]: <info>  [1510910349.0298] device (wlp5s0): supplicant interface state: authenticating -> associating
Nov 17 10:19:09 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 2/3)
Nov 17 10:19:09 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 3/3)
Nov 17 10:19:09 linux.home kernel: wlp5s0: association with e4:3e:d7:aa:80:ab timed out
Nov 17 10:19:09 linux.home NetworkManager[940]: <info>  [1510910349.3675] device (wlp5s0): supplicant interface state: associating -> disconnected
Nov 17 10:19:09 linux.home NetworkManager[940]: <info>  [1510910349.8686] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:19:10 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:19:10 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:19:10 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:19:10 linux.home NetworkManager[940]: <info>  [1510910350.9078] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:19:10 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:19:10 linux.home kernel: wlp5s0: authenticated
Nov 17 10:19:10 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:19:10 linux.home NetworkManager[940]: <info>  [1510910350.9147] device (wlp5s0): supplicant interface state: authenticating -> associating
Nov 17 10:19:10 linux.home kernel: wlp5s0: RX AssocResp from e4:3e:d7:aa:80:ab (capab=0x411 status=0 aid=2)
Nov 17 10:19:10 linux.home kernel: wlp5s0: associated
Nov 17 10:19:10 linux.home wpa_supplicant[1093]: wlp5s0: Associated with e4:3e:d7:aa:80:ab
Nov 17 10:19:10 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 17 10:19:10 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Nov 17 10:19:10 linux.home NetworkManager[940]: <info>  [1510910350.9266] device (wlp5s0): supplicant interface state: associating -> associated
Nov 17 10:19:10 linux.home NetworkManager[940]: <info>  [1510910350.9390] device (wlp5s0): supplicant interface state: associated -> 4-way handshake
Nov 17 10:19:10 linux.home wpa_supplicant[1093]: wlp5s0: WPA: Key negotiation completed with e4:3e:d7:aa:80:ab [PTK=CCMP GTK=TKIP]
Nov 17 10:19:10 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to e4:3e:d7:aa:80:ab completed [id=0 id_str=]
Nov 17 10:19:10 linux.home NetworkManager[940]: <info>  [1510910350.9690] device (wlp5s0): supplicant interface state: 4-way handshake -> completed
Nov 17 10:19:27 linux.home avahi-daemon[853]: Withdrawing address record for 2a02:120b:c3fe:9bd0:ff37:c20e:3678:4e26 on wlp5s0.
Nov 17 10:19:27 linux.home avahi-daemon[853]: Leaving mDNS multicast group on interface wlp5s0.IPv6 with address 2a02:120b:c3fe:9bd0:ff37:c20e:3678:4e26.
Nov 17 10:19:27 linux.home avahi-daemon[853]: Joining mDNS multicast group on interface wlp5s0.IPv6 with address fe80::47fa:575e:81b:d372.
Nov 17 10:19:31 linux.home kernel: psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
Nov 17 10:19:31 linux.home kernel: psmouse serio1: Touchpad at isa0060/serio1/input0 - driver resynced.
Nov 17 10:19:42 linux.home kernel: rtlwifi: AP off, try to reconnect now
Nov 17 10:19:42 linux.home kernel: wlp5s0: Connection to AP e4:3e:d7:aa:80:ab lost
Nov 17 10:19:42 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=e4:3e:d7:aa:80:ab reason=4 locally_generated=1
Nov 17 10:19:42 linux.home NetworkManager[940]: <warn>  [1510910382.3897] sup-iface[0x5635b83ad0a0,wlp5s0]: connection disconnected (reason -4)
Nov 17 10:19:42 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 17 10:19:42 linux.home NetworkManager[940]: <info>  [1510910382.3986] device (wlp5s0): supplicant interface state: completed -> disconnected
Nov 17 10:19:42 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Nov 17 10:19:42 linux.home NetworkManager[940]: <info>  [1510910382.4951] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:19:43 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:19:43 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:19:43 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:19:43 linux.home NetworkManager[940]: <info>  [1510910383.5362] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:19:43 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 2/3)
Nov 17 10:19:43 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 3/3)
Nov 17 10:19:43 linux.home kernel: wlp5s0: authentication with e4:3e:d7:aa:80:ab timed out
Nov 17 10:19:43 linux.home NetworkManager[940]: <info>  [1510910383.8793] device (wlp5s0): supplicant interface state: authenticating -> disconnected
Nov 17 10:19:44 linux.home NetworkManager[940]: <info>  [1510910384.3800] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 17 10:19:45 linux.home wpa_supplicant[1093]: wlp5s0: SME: Trying to authenticate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:19:45 linux.home kernel: wlp5s0: authenticate with e4:3e:d7:aa:80:ab
Nov 17 10:19:45 linux.home kernel: wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:19:45 linux.home NetworkManager[940]: <info>  [1510910385.4201] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 17 10:19:45 linux.home wpa_supplicant[1093]: wlp5s0: Trying to associate with e4:3e:d7:aa:80:ab (SSID='Choupies_box_2.4GHz' freq=2412 MHz)
Nov 17 10:19:45 linux.home kernel: wlp5s0: authenticated
Nov 17 10:19:45 linux.home kernel: wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
Nov 17 10:19:45 linux.home NetworkManager[940]: <info>  [1510910385.4268] device (wlp5s0): supplicant interface state: authenticating -> associating
Nov 17 10:19:45 linux.home kernel: wlp5s0: RX AssocResp from e4:3e:d7:aa:80:ab (capab=0x411 status=0 aid=2)
Nov 17 10:19:45 linux.home kernel: wlp5s0: associated
Nov 17 10:19:45 linux.home wpa_supplicant[1093]: wlp5s0: Associated with e4:3e:d7:aa:80:ab
Nov 17 10:19:45 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 17 10:19:45 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Nov 17 10:19:45 linux.home NetworkManager[940]: <info>  [1510910385.4439] device (wlp5s0): supplicant interface state: associating -> 4-way handshake
Nov 17 10:19:45 linux.home wpa_supplicant[1093]: wlp5s0: WPA: Key negotiation completed with e4:3e:d7:aa:80:ab [PTK=CCMP GTK=TKIP]
Nov 17 10:19:45 linux.home wpa_supplicant[1093]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to e4:3e:d7:aa:80:ab completed [id=0 id_str=]
Nov 17 10:19:45 linux.home NetworkManager[940]: <info>  [1510910385.4657] device (wlp5s0): supplicant interface state: 4-way handshake -> completed

"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#4 17/11/2017 12:34:47

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Et du coup il n'y a que le Wi-Fi qui en pâti ? Pas de souci avec le BT pendant son activation ?
Et dès la désactivation du BT, tout rentre dans l'ordre ?


F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

#5 17/11/2017 13:26:55

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Non, le BT semble fonctionner normalement. Et quand je coupe le BT il faut quand même que je désactive/réactive le wifi pour que ça fonctionne de nouveau normalement.


"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#6 17/11/2017 15:39:36

Mister_G
Membre
Lieu : Rouen (76)
Inscription : 07/05/2007
Messages : 654

Re : Wifi déraille quand Mr Bluetooth démarre

j'ai trouvé cela
ca ne résout pas ton soucis mais ca l'éclaire un peu

et la  une explication des autres codes possibles

Dernière modification par Mister_G (17/11/2017 15:40:37)


i7 870 - 16 Go - gtx 970 - ssd 500 Go - Win 10 +  ssd 250 Go - F27 64 Fluxbox - 28" hanns g
lenovo i5- 4 Go - ssd 128 Go - debian sid 32 Fluxbox  - 15.6"

Hors ligne

#7 17/11/2017 17:30:54

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

A la fin du fichier /etc/NetworkManager/NetworkManager.conf peux-tu ajouter la section suivante

[device]
wifi.scan-rand-mac-address=no

Puis redémarrer le service

# systemctl restart NetworkManager.service

F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

#8 24/11/2017 15:49:35

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Merci de votre aide.
Nicoss, ça ne change rien a priori :

Nov 24 14:46:12 wifi-secure-147-124.unifr.ch kernel: wlp5s0: Limiting TX power to 14 dBm as advertised by 20:37:06:f6:ae:52
Nov 24 14:47:09 wifi-secure-147-124.unifr.ch gnome-shell[1784]: [Gnome Email Notifications] Checking mail
Nov 24 14:47:28 wifi-secure-147-124.unifr.ch kernel: rtlwifi: AP off, try to reconnect now
Nov 24 14:47:28 wifi-secure-147-124.unifr.ch kernel: wlp5s0: Connection to AP 20:37:06:f6:ae:52 lost
Nov 24 14:47:28 wifi-secure-147-124.unifr.ch wpa_supplicant[1103]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=20:37:06:f6:ae:52 reason=4 locally_generated=1
Nov 24 14:47:28 wifi-secure-147-124.unifr.ch NetworkManager[8465]: <warn>  [1511531248.8949] sup-iface[0x7f91dc007a00,wlp5s0]: connection disconnected (reason -4)
Nov 24 14:47:28 wifi-secure-147-124.unifr.ch wpa_supplicant[1103]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 24 14:47:28 wifi-secure-147-124.unifr.ch wpa_supplicant[1103]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=FR
Nov 24 14:47:28 wifi-secure-147-124.unifr.ch NetworkManager[8465]: <info>  [1511531248.9048] device (wlp5s0): supplicant interface state: completed -> disconnected
Nov 24 14:47:29 wifi-secure-147-124.unifr.ch NetworkManager[8465]: <info>  [1511531249.0007] device (wlp5s0): supplicant interface state: disconnected -> scanning
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch wpa_supplicant[1103]: wlp5s0: SME: Trying to authenticate with 20:37:06:f6:ae:52 (SSID='secure-unifr' freq=2437 MHz)
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch kernel: wlp5s0: authenticate with 20:37:06:f6:ae:52
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch kernel: wlp5s0: send auth to 20:37:06:f6:ae:52 (try 1/3)
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch NetworkManager[8465]: <info>  [1511531255.5214] device (wlp5s0): supplicant interface state: scanning -> authenticating
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch wpa_supplicant[1103]: wlp5s0: Trying to associate with 20:37:06:f6:ae:52 (SSID='secure-unifr' freq=2437 MHz)
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch kernel: wlp5s0: authenticated
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch kernel: wlp5s0: associate with 20:37:06:f6:ae:52 (try 1/3)
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch kernel: wlp5s0: RX AssocResp from 20:37:06:f6:ae:52 (capab=0x431 status=0 aid=64)
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch wpa_supplicant[1103]: wlp5s0: Associated with 20:37:06:f6:ae:52
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch wpa_supplicant[1103]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch kernel: wlp5s0: associated
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch NetworkManager[8465]: <info>  [1511531255.5333] device (wlp5s0): supplicant interface state: authenticating -> associated
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch wpa_supplicant[1103]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CH
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch wpa_supplicant[1103]: wlp5s0: WPA: Key negotiation completed with 20:37:06:f6:ae:52 [PTK=CCMP GTK=CCMP]
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch wpa_supplicant[1103]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to 20:37:06:f6:ae:52 completed [id=0 id_str=]
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch wpa_supplicant[1103]: bgscan simple: Failed to enable signal strength monitoring
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch NetworkManager[8465]: <info>  [1511531255.5423] device (wlp5s0): supplicant interface state: associated -> 4-way handshake
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch NetworkManager[8465]: <info>  [1511531255.5439] device (wlp5s0): supplicant interface state: 4-way handshake -> completed
Nov 24 14:47:35 wifi-secure-147-124.unifr.ch kernel: wlp5s0: Limiting TX power to 14 dBm as advertised by 20:37:06:f6:ae:52
Nov 24 14:47:45 wifi-secure-147-124.unifr.ch gjs[3528]: JS WARNING: [/home/laurent/.local/share/gnome-shell/extensions/drop-down-terminal@gs-extensions.zzrough.org/terminal.js 287]: reference to undefined property "GdkWaylandWindow"
Nov 24 14:47:45 wifi-secure-147-124.unifr.ch gjs[3528]: JS LOG: could not get x11 server time (cause: TypeError: Object is of type GdkWaylandWindow - cannot convert to GdkX11Window)

"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#9 24/11/2017 21:12:41

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Effectivement ça n'a pas l'air d'avoir changé grand chose...

Que retourne

$ rpm -qa bluez\*
$ dmesg

F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

#10 04/12/2017 17:23:38

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Salut, voici ce que ça renvoie :

 5.805502] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    5.856332] Netfilter messages via NETLINK v0.30.
[    5.867997] ip_set: protocol 6
[    5.909840] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[    6.472207] tun: Universal TUN/TAP device driver, 1.6
[    6.473496] virbr0: port 1(virbr0-nic) entered blocking state
[    6.473497] virbr0: port 1(virbr0-nic) entered disabled state
[    6.473526] device virbr0-nic entered promiscuous mode
[    6.566323] virbr0: port 1(virbr0-nic) entered blocking state
[    6.566325] virbr0: port 1(virbr0-nic) entered listening state
[    6.605667] virbr0: port 1(virbr0-nic) entered disabled state
[    7.357953] wlp5s0: authenticate with e4:3e:d7:aa:80:ab
[    7.374573] wlp5s0: send auth to e4:3e:d7:aa:80:ab (try 1/3)
[    7.376383] wlp5s0: authenticated
[    7.377144] wlp5s0: associate with e4:3e:d7:aa:80:ab (try 1/3)
[    7.382724] wlp5s0: RX AssocResp from e4:3e:d7:aa:80:ab (capab=0x411 status=0 aid=4)
[    7.382912] wlp5s0: associated
[    7.382919] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready
[   11.743428] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170531/nsarguments-95)
[   11.743797] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
[   11.743802] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170531/nsarguments-95)
[   11.744094] nouveau 0000:01:00.0: DRM: evicting buffers...
[   11.744096] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
[   11.744175] nouveau 0000:01:00.0: DRM: suspending fence...
[   11.744413] nouveau 0000:01:00.0: DRM: suspending object tree...
[   18.535014] fuse init (API version 7.26)
[   19.071455] Bluetooth: RFCOMM TTY layer initialized
[   19.071459] Bluetooth: RFCOMM socket layer initialized
[   19.071525] Bluetooth: RFCOMM ver 1.11
[   20.404544] rfkill: input handler disabled
[ 2852.953634] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based  firewall rule not found. Use the iptables CT target to attach helpers instead.

"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#11 04/12/2017 18:21:49

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Il manque au moins une commande.
Le dmesg est entier ?


F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

#12 04/12/2017 19:39:52

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Je voudrais être sûr : est-ce que je lance les 2 commandes lorsque le wifi déraille ou à n'importe quel moment ?


"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#13 04/12/2017 19:51:44

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

La première n'a pas d'importance, elle va lister les paquets.
La seconde après, car il faut voir ce que ça raconte après le problème, d'ailleurs si tu peux aussi remettre propre avant de faire la commande.

Et pour la peine une troisième qu'il faudra faire 2 fois.
Avant d'activer le bluetooth et après l'avoir activé.

# rfkill list

F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

#14 04/01/2018 20:02:08

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Salut !!!

Voici le retour de rpm -qa bluez\*

bluez-obexd-5.47-2.fc27.x86_64
bluez-5.47-2.fc27.x86_64
bluez-libs-5.47-2.fc27.x86_64
bluez-cups-5.47-2.fc27.x86_64

Voici le retour de rfkill avant d'activer le wifi

0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

Voici le retour de rfkill après que le wifi déraille

0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

Voici le retour de dmseg ici (trop long pour être copié ici)


"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#15 05/01/2018 21:59:16

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Si tu penses vraiment que des retours de commandes sont trop long pour être entre balises code <> alors utilise plutôt https://paste.fedoraproject.org.

Rien de bien parlant encore, juste le fait que le Wi-Fi ne puisse plus se connecter. D'ailleurs l'IPV4 est activé aussi ?

Que retourne

$ lspci -nnk | grep -iA3 "Network"

F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

#16 07/01/2018 16:07:26

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Nicosss a écrit :

D'ailleurs l'IPV4 est activé aussi ?

Argh, j'imagine. Comment je peux vérifier ?

sinon, le retour de lspci -nnk | grep -iA3 "Network" :

[laurent@linux ~]$ lspci -nnk | grep -iA3 "Network"
05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723AE PCIe Wireless Network Adapter [10ec:8723]
	Subsystem: AzureWave Device [1a3b:2114]
	Kernel driver in use: rtl8723ae
	Kernel modules: rtl8723ae

"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#17 07/01/2018 18:12:56

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Dans les paramètres réseau tu dois le voir.
Sinon

$ nmcli connection show

F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

#18 10/02/2018 08:43:11

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Voilà ce que renvoie nmcli connection show

[laurent@linux ~]$ nmcli connection show
NOM                             UUID                                  TYPE             PÉRIPHÉRIQUE 
Choupies_box_2.4GHz             b7a447ed-b0d4-4dca-8f1f-7ea1e8e332e4  802-11-wireless  wlp5s0       
CUBOT ECHO                      bd03ef0f-448b-46c8-9383-36a5f25f8f4a  802-11-wireless  --           
HUAWEI P9                       c0dd33d4-bb9c-4e08-9d11-fbb68ea4a0d3  802-11-wireless  --           
SFR_0710                        d0ddd13f-af77-4164-b99c-a13fe63e768f  802-11-wireless  --           
VPN 1                           c135bfbb-9fba-480e-a31b-1ad9a83173d4  vpn              --           
eduroam                         07d3f374-afd4-4995-9d92-f4050365177c  802-11-wireless  --           
enp4s0                          8b5d8bcf-ba01-35ff-8c47-7bf80a66b9b7  802-3-ethernet   --           
freeb                           bc48e1ea-4206-4baa-9c66-1e0ca155d2d4  802-11-wireless  --           
freebox_Michele                 5e524211-18fd-44df-a969-a335d856ef3f  802-11-wireless  --           
se-fr-01.protonvpn.com.udp1194  d68b1135-c013-4203-860d-33f879edd795  vpn              --           

"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#19 10/02/2018 10:52:43

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Désolé je me suis trompé dans la commande, c'était

$ nmcli device show

F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

#20 11/02/2018 17:39:36

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Pas de souci smile
Voici la sortie :

GENERAL.PÉRIPHÉRIQUE:                   wlp5s0
GENERAL.TYPE:                           wifi
GENERAL.ADR.-MAT.:                      40:E2:30:2F:EB:1A
GENERAL.MTU:                            1500
GENERAL.ÉTAT:                           100 (connecté)
GENERAL.CONNEXION:                      Choupies_box_2.4GHz
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
IP4.ADRESSE[1]:                         192.168.1.101/24
IP4.PASSERELLE:                         192.168.1.1
IP4.DNS[1]:                             192.168.1.1
IP4.DOMAINE[1]:                         home
IP6.ADRESSE[1]:                         2a02:120b:2c02:ce70:7983:bf55:cbce:48d7/64
IP6.ADRESSE[2]:                         fe80::d9b4:6324:d83f:a7ce/64
IP6.PASSERELLE:                         fe80::e63e:d7ff:feaa:80ab
IP6.ROUTE[1]:                           dst = 2a02:120b:2c02:ce70::/64, nh = ::, mt = 600
IP6.DNS[1]:                             2a02:120b:2c02:ce70:e63e:d7ff:feaa:80ab

GENERAL.PÉRIPHÉRIQUE:                   enp4s0
GENERAL.TYPE:                           ethernet
GENERAL.ADR.-MAT.:                      44:8A:5B:EF:78:B0
GENERAL.MTU:                            1500
GENERAL.ÉTAT:                           20 (indisponible)
GENERAL.CONNEXION:                      --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.PORTEUSE:              arrêt

GENERAL.PÉRIPHÉRIQUE:                   lo
GENERAL.TYPE:                           loopback
GENERAL.ADR.-MAT.:                      00:00:00:00:00:00
GENERAL.MTU:                            65536
GENERAL.ÉTAT:                           10 (non-géré)
GENERAL.CONNEXION:                      --
GENERAL.CON-PATH:                       --
IP4.ADRESSE[1]:                         127.0.0.1/8
IP4.PASSERELLE:                         --
IP6.ADRESSE[1]:                         ::1/128
IP6.PASSERELLE:                         --

"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#21 11/02/2018 20:15:39

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

L'IPv4 est bien activé.

Essaye de désactiver l'IPv6 sur wlp5s0 et poster le retour de dmesg complet (pas sur Dropbox wink ) après l'activation du BT.


F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

#22 11/02/2018 21:24:31

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Et voila la sortie sur paste.fedoraproject cool big_smile Pas assez de place sur paste.feodraproject donc j'ai tranché là où ca semblait important.

Dernière modification par loloboua (11/02/2018 21:35:01)


"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#23 11/02/2018 23:42:39

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Du coup ça donne quoi, car c'est difficile de voir dans le dmesg. Du moins pas d'erreur notable.

Dans les journaux système il se passe quoi aussi au moment de l'activation du BT

# journalctl -f

F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

#24 24/02/2018 11:02:37

loloboua
Ecologue ardennais
Lieu : Fribourg (Suisse)
Inscription : 01/05/2011
Messages : 179
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Voilà quelques ligne qui semble intéressantes dans le retour de journalctl -f

févr. 24 09:56:11 Nonmaididonc kernel: Bluetooth: hci0: last event is not cmd complete (0x0f)
févr. 24 09:56:12 Nonmaididonc dbus-daemon[878]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.54" (uid=1000 pid=1724 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.4" (uid=0 pid=925 comm="/usr/libexec/bluetooth/bluetoothd " label="system_u:system_r:bluetooth_t:s0")
févr. 24 09:56:12 Nonmaididonc gsd-media-keys[1965]: Unable to get default sink
févr. 24 09:56:12 Nonmaididonc systemd[1]: Starting Load/Save RF Kill Switch Status...
févr. 24 09:56:12 Nonmaididonc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
févr. 24 09:56:12 Nonmaididonc systemd[1]: Started Load/Save RF Kill Switch Status.
févr. 24 09:56:12 Nonmaididonc gnome-shell[1643]: Could not release device 13,82: GDBus.Error:org.freedesktop.login1.DeviceNotTaken: Device not taken
févr. 24 09:56:17 Nonmaididonc kernel: wlp5s0: deauthenticating from e4:3e:d7:aa:80:ab by local choice (Reason: 3=DEAUTH_LEAVING)
févr. 24 09:56:17 Nonmaididonc wpa_supplicant[1190]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=e4:3e:d7:aa:80:ab reason=3 locally_generated=1
févr. 24 09:56:17 Nonmaididonc avahi-daemon[922]: Interface wlp5s0.IPv6 no longer relevant for mDNS.
févr. 24 09:56:17 Nonmaididonc avahi-daemon[922]: Leaving mDNS multicast group on interface wlp5s0.IPv6 with address 2a02:120b:2c02:ce70:42e2:30ff:fe2f:eb1a.
févr. 24 09:56:17 Nonmaididonc dhclient[1541]: receive_packet failed on wlp5s0: Network is down
févr. 24 09:56:17 Nonmaididonc avahi-daemon[922]: Interface wlp5s0.IPv4 no longer relevant for mDNS.
févr. 24 09:56:17 Nonmaididonc avahi-daemon[922]: Leaving mDNS multicast group on interface wlp5s0.IPv4 with address 192.168.1.101.
févr. 24 09:56:17 Nonmaididonc avahi-daemon[922]: Withdrawing address record for 2a02:120b:2c02:ce70:42e2:30ff:fe2f:eb1a on wlp5s0.
févr. 24 09:56:17 Nonmaididonc avahi-daemon[922]: Withdrawing address record for 192.168.1.101 on wlp5s0.
févr. 24 09:56:17 Nonmaididonc NetworkManager[1051]: <info>  [1519462577.2196] manager: rfkill: WiFi hardware radio set disabled
févr. 24 09:56:17 Nonmaididonc NetworkManager[1051]: <info>  [1519462577.2201] device (wlp5s0): state change: activated -> unavailable (reason 'none', internal state 'managed')
févr. 24 09:56:17 Nonmaididonc wpa_supplicant[1190]: rfkill: WLAN soft blocked
févr. 24 09:56:17 Nonmaididonc NetworkManager[1051]: <info>  [1519462577.2246] dhcp4 (wlp5s0): canceled DHCP transaction, DHCP client pid 1541
févr. 24 09:56:17 Nonmaididonc NetworkManager[1051]: <info>  [1519462577.2249] dhcp4 (wlp5s0): state changed bound -> done
févr. 24 09:56:17 Nonmaididonc NetworkManager[1051]: <info>  [1519462577.2319] device (wlp5s0): set-hw-addr: set MAC address to FE:97:E1:82:AA:AF (scanning)
févr. 24 09:56:17 Nonmaididonc NetworkManager[1051]: <info>  [1519462577.2323] manager: NetworkManager state is now CONNECTED_SITE
févr. 24 09:56:17 Nonmaididonc dbus-daemon[878]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=1051 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
févr. 24 09:56:17 Nonmaididonc audit: NETFILTER_CFG table=filter family=2 entries=86
févr. 24 09:56:17 Nonmaididonc audit: NETFILTER_CFG table=nat family=2 entries=52
févr. 24 09:56:17 Nonmaididonc audit: NETFILTER_CFG table=mangle family=2 entries=40
févr. 24 09:56:17 Nonmaididonc systemd[1]: Starting Network Manager Script Dispatcher Service...
févr. 24 09:56:17 Nonmaididonc audit: NETFILTER_CFG table=raw family=2 entries=29
févr. 24 09:56:17 Nonmaididonc audit: NETFILTER_CFG table=filter family=10 entries=87
févr. 24 09:56:17 Nonmaididonc audit: NETFILTER_CFG table=nat family=10 entries=52
févr. 24 09:56:17 Nonmaididonc audit: NETFILTER_CFG table=mangle family=10 entries=40
févr. 24 09:56:17 Nonmaididonc audit: NETFILTER_CFG table=raw family=10 entries=30
févr. 24 09:56:17 Nonmaididonc NetworkManager[1051]: <info>  [1519462577.2513] manager: NetworkManager state is now CONNECTED_LOCAL
févr. 24 09:56:17 Nonmaididonc NetworkManager[1051]: <info>  [1519462577.2514] manager: NetworkManager state is now DISCONNECTED
févr. 24 09:56:17 Nonmaididonc wpa_supplicant[1190]: nl80211: deinit ifname=wlp5s0 disabled_11b_rates=0
févr. 24 09:56:17 Nonmaididonc NetworkManager[1051]: <info>  [1519462577.2724] audit: op="radio-control" arg="wireless-enabled:0" pid=1643 uid=1000 result="success"

"Le gras c'est la vie!!!"
Celui qui n'a jamais mangé un jarret de porc grillé sedanais n'a jamais rien mangé.
MSI CX61 2PC

Hors ligne

#25 24/02/2018 16:43:34

Nicosss
Membre
Lieu : Isère
Inscription : 05/03/2007
Messages : 4 025
Site Web

Re : Wifi déraille quand Mr Bluetooth démarre

Je ne comprends pas que le retour de commande de rfkill dise le contraire de ce qui apparait dans les logs

wpa_supplicant[1190]: rfkill: WLAN soft blocked
NetworkManager[1051]: <info>  [1519462577.2196] manager: rfkill: WiFi hardware radio set disabled

Est-ce que tu peux bien vérifier avec les précédentes commandes lors de l'activation du BT ? Et ajoute aussi la commande

$ nmcli general

Sinon on essayera avec des options en cas... Que retourne

# modinfo rtl8723ae

F29_64 Gnome-Shell - GA-990FXA-UD3 - Phenom II X6 1100T - NH-D14 - Ati HD 5570 Fanless - 8Go RAM /&/ F28_64 Gnome-Shell - GA-M55S-S3 - Athlon 64 X2 4200+ - GeminII - Ati HD5750 Fanless - 3Go RAM
F28_32 - 939A785GMH/128M - Athlon 64 4000+ - 2Go RAM /&/ F28_32 Gnome-Shell - EeePC 701 - 2Go RAM

Hors ligne

Pied de page des forums