#1 Le 17/12/2019, à 10:00
- viot
Kernel Linux version 5.3.0-24.26 et Realtek RTL822BE 802.11a/b/g/n/ac
A nouveau plus de connexion wifi avec les noyaux 5.3.0. Le problème avec la version 5.0.0.21 avait été résolu (voir) et le problème recommence.
Voici les informations recueillies avec cette version du noyau
lspci -nnk | grep 0280 -A3
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter [1a3b:2950]
Kernel driver in use: rtw_pci
Kernel modules: rtwpci
lsmod | grep cfg8021
cfg80211 712704 2 mac80211,rtw88
iwconfig
wlp3s0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
lo no wireless extensions.
nmcli dev wifi
IN-USE SSID MODE CHAN RATE SIGNAL BARS SECUR
Tuxland Infra 6 195 Mbit/s 100 ▂▄▆█ WPA1
Tuxland5 Infra 36 405 Mbit/s 79 ▂▄▆_ WPA1
-- Infra 36 130 Mbit/s 65 ▂▄▆_ WPA2
DIRECT-f9-HP M277 LaserJet Infra 6 65 Mbit/s 60 ▂▄▆_ WPA2
Livebox-7B67_EXT Infra 1 130 Mbit/s 37 ▂▄__ WPA1
TC-ALANS Infra 11 130 Mbit/s 20 ▂___ WPA1
HP-Print-66-Officejet 4630 Infra 1 54 Mbit/s 17 ▂___ --
Livebox-7B67 Infra 1 130 Mbit/s 12 ▂___ WPA1
sudo bootctl
System:
Firmware: n/a (n/a)
Secure Boot: disabled
Setup Mode: user
Current Boot Loader:
Product: n/a
Features: ✗ Boot counting
✗ Menu timeout control
✗ One-shot menu timeout control
✗ Default entry control
✗ One-shot entry control
ESP: n/a
File: └─n/a
Available Boot Loaders on ESP:
ESP: /boot/efi (/dev/disk/by-partuuid/9e8da71b-9bc4-4ae7-9b97-b049da45463a)
File: └─/EFI/BOOT/bootx64.efi
Boot Loaders Listed in EFI Variables:
Title: ubuntu
ID: 0x0001
Status: active, boot-order
Partition: /dev/disk/by-partuuid/9e8da71b-9bc4-4ae7-9b97-b049da45463a
File: └─/EFI/UBUNTU/SHIMX64.EFI
Title: Windows Boot Manager
ID: 0x0000
Status: active, boot-order
Partition: /dev/disk/by-partuuid/9e8da71b-9bc4-4ae7-9b97-b049da45463a
File: └─/EFI/MICROSOFT/BOOT/BOOTMGFW.EFI
Boot Loader Entries:
$BOOT: /boot/efi (/dev/disk/by-partuuid/9e8da71b-9bc4-4ae7-9b97-b049da45463a)
En résumé les réseaux sont vus par la carte wifi, mais impossible de se connecter
La signature du problème se voit dans
dmesg
dont voici un extrait concernant le problème du driver rtwpci
D'avance merci pour votre aide!
[ 6.970480] rtw_pci 0000:03:00.0: failed to send h2c command
[ 7.311801] rfkill: input handler disabled
[ 9.682645] rtw_pci 0000:03:00.0: failed to send h2c command
[ 9.682755] rtw_pci 0000:03:00.0: failed to send h2c command
[ 9.730007] wlp3s0: authenticate with 54:64:d9:4e:01:df
[ 10.230189] wlp3s0: send auth to 54:64:d9:4e:01:df (try 1/3)
[ 10.231403] wlp3s0: authenticated
[ 10.234313] wlp3s0: associate with 54:64:d9:4e:01:df (try 1/3)
[ 10.235994] wlp3s0: RX AssocResp from 54:64:d9:4e:01:df (capab=0x1011 status=0 aid=6)
[ 10.236063] rtw_pci 0000:03:00.0: failed to send h2c command
[ 10.236107] rtw_pci 0000:03:00.0: failed to send h2c command
[ 10.236112] rtw_pci 0000:03:00.0: sta 54:64:d9:4e:01:df joined with macid 0
[ 10.738280] ------------[ cut here ]------------
[ 10.738300] purge skb(s) not reported by firmware
[ 10.738392] WARNING: CPU: 2 PID: 0 at drivers/net/wireless/realtek/rtw88/tx.c:156 rtw_tx_report_purge_timer+0x25/0x60 [rtw88]
[ 10.738395] Modules linked in: sep5(OE) socperf3(OE) pax(OE) cmac bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress ac97_bus x86_pkg_temp_thermal snd_hda_codec_generic intel_powerclamp ledtrig_audio snd_pcm_dmaengine coretemp kvm_intel snd_hda_intel snd_hda_codec kvm snd_hda_core irqbypass snd_hwdep snd_pcm mei_hdcp snd_seq_midi snd_seq_midi_event intel_rapl_msr snd_rawmidi crct10dif_pclmul crc32_pclmul joydev ghash_clmulni_intel i915 snd_seq aesni_intel rtwpci rtw88 aes_x86_64 uvcvideo btusb crypto_simd snd_seq_device snd_timer videobuf2_vmalloc drm_kms_helper btrtl cryptd glue_helper videobuf2_memops mac80211 videobuf2_v4l2 btbcm intel_cstate drm snd videobuf2_common btintel bluetooth intel_rapl_perf videodev cfg80211 asus_nb_wmi i2c_algo_bit processor_thermal_device spi_pxa2xx_platform fb_sys_fops asus_wmi
[ 10.738473] input_leds mei_me syscopyarea intel_rapl_common idma64 mc ecdh_generic sysfillrect dw_dmac intel_xhci_usb_role_switch sparse_keymap serio_raw wmi_bmof soundcore mxm_wmi ecc libarc4 8250_dw dw_dmac_core hid_multitouch mei roles sysimgblt virt_dma intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_thermal_rel acpi_pad asus_wireless sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid_generic i2c_hid hid r8169 i2c_i801 ahci intel_lpss_pci realtek libahci intel_lpss video wmi pinctrl_sunrisepoint pinctrl_intel
[ 10.738546] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G OE 5.3.0-24-generic #26-Ubuntu
[ 10.738549] Hardware name: ASUSTeK COMPUTER INC. X705UDR/X705UDR, BIOS X705UDR.302 09/27/2017
[ 10.738568] RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88]
[ 10.738574] Code: 00 00 00 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 f0 bd c8 c0 e8 f6 0a 87 f2 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 ed 4e 27 f3 48 8d 7b e0 49 89 c4 e8
[ 10.738577] RSP: 0018:ffffb6c480170e48 EFLAGS: 00010286
[ 10.738582] RAX: 0000000000000000 RBX: ffff96afd3c8d848 RCX: 000000000000083f
[ 10.738585] RDX: 0000000000000000 RSI: 00000000000000f6 RDI: 000000000000083f
[ 10.738587] RBP: ffffb6c480170e60 R08: ffff96afdea97448 R09: 0000000000000004
[ 10.738591] R10: 0000000000000000 R11: 0000000000000001 R12: ffff96afdea9b600
[ 10.738594] R13: ffff96afd3c8d848 R14: ffffffffc0c2a7d0 R15: ffff96afd3c8d848
[ 10.738598] FS: 0000000000000000(0000) GS:ffff96afdea80000(0000) knlGS:0000000000000000
[ 10.738602] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 10.738605] CR2: 00007fbec8105000 CR3: 00000002a620a003 CR4: 00000000003606e0
[ 10.738609] Call Trace:
[ 10.738612] <IRQ>
[ 10.738626] call_timer_fn+0x32/0x130
[ 10.738635] __run_timers.part.0+0x177/0x270
[ 10.738643] ? tick_sched_handle+0x33/0x60
[ 10.738649] ? tick_sched_timer+0x3d/0x80
[ 10.738657] ? recalibrate_cpu_khz+0x10/0x10
[ 10.738662] ? ktime_get+0x42/0xa0
[ 10.738669] run_timer_softirq+0x2a/0x50
[ 10.738677] __do_softirq+0xe1/0x2d6
[ 10.738685] ? hrtimer_interrupt+0x13b/0x220
[ 10.738692] irq_exit+0xae/0xb0
[ 10.738698] smp_apic_timer_interrupt+0x7b/0x140
[ 10.738703] apic_timer_interrupt+0xf/0x20
[ 10.738707] </IRQ>
[ 10.738715] RIP: 0010:cpuidle_enter_state+0xc5/0x420
[ 10.738727] Code: ff e8 2f 70 83 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3d 03 00 00 31 ff e8 02 ca 89 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 89 d1 01 00 00 41 c7 44 24 10 00 00 00 00 48 83 c4 18
[ 10.738731] RSP: 0018:ffffb6c4800dbe38 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
[ 10.738735] RAX: ffff96afdeaaa740 RBX: ffffffffb4b5a780 RCX: 000000000000001f
[ 10.738738] RDX: 0000000000000000 RSI: 000000004041ceb5 RDI: 0000000000000000
[ 10.738741] RBP: ffffb6c4800dbe78 R08: 00000002800cedbf R09: 000000000000afc7
[ 10.738744] R10: ffff96afdeaa94e4 R11: ffff96afdeaa94c4 R12: ffff96afdeab5500
[ 10.738747] R13: 0000000000000008 R14: 0000000000000008 R15: ffff96afdeab5500
[ 10.738760] ? cpuidle_enter_state+0xa1/0x420
[ 10.738767] cpuidle_enter+0x2e/0x40
[ 10.738774] call_cpuidle+0x23/0x40
[ 10.738778] do_idle+0x1dd/0x270
[ 10.738784] cpu_startup_entry+0x20/0x30
[ 10.738790] start_secondary+0x168/0x1c0
[ 10.738798] secondary_startup_64+0xa4/0xb0
[ 10.738806] ---[ end trace 2579f178723892a4 ]---
Hors ligne
#3 Le 17/12/2019, à 11:28
- xubu1957
Re : Kernel Linux version 5.3.0-24.26 et Realtek RTL822BE 802.11a/b/g/n/ac
Bonjour,
IN-USE SSID MODE CHAN RATE SIGNAL BARS SECUR
Tuxland Infra 6 195 Mbit/s 100 ▂▄▆█ WPA1
Tuxland5 Infra 36 405 Mbit/s 79 ▂▄▆_ WPA1
Il faudrait mettre un seul chiffrement WPA2, comme indiqué au § 1 > [Tuto] Pas de Wi-fi ? Eléments importants à vérifier.
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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
#4 Le 23/12/2019, à 11:58
- viot
Re : Kernel Linux version 5.3.0-24.26 et Realtek RTL822BE 802.11a/b/g/n/ac
Le changement a été fait sur la box, mais il n'y a aucun changement avec le noyau 5.3.0.
Plus de connexion avec le wifi.
Je pense que le nouveau module est buggé, mais comment faire?
IN-USE SSID MODE CHAN RATE SIGNAL BARS SECURITY
Tuxland Infra 1 195 Mbit/s 100 ▂▄▆█ WPA2
* Tuxland5 Infra 36 405 Mbit/s 75 ▂▄▆_ WPA2
Hors ligne
#5 Le 23/12/2019, à 15:45
- NicoApi73
Re : Kernel Linux version 5.3.0-24.26 et Realtek RTL822BE 802.11a/b/g/n/ac
Bonjour,
Tu parlais de messages dans le kern.log. Quels sont ils?
Donne :
dmesg -lerr | tail -50
Hors ligne
#6 Le 23/12/2019, à 18:34
- viot
Re : Kernel Linux version 5.3.0-24.26 et Realtek RTL822BE 802.11a/b/g/n/ac
dmesg -lerr | tail -50
donne
[ 5.917496] rtw_pci 0000:03:00.0: failed to send h2c command
[ 6.558933] sep5_10: Driver loading...
[ 10.219360] rtw_pci 0000:03:00.0: failed to send h2c command
[ 10.219401] rtw_pci 0000:03:00.0: failed to send h2c command
[ 18.674133] rtw_pci 0000:03:00.0: failed to send h2c command
[ 18.674221] rtw_pci 0000:03:00.0: failed to send h2c command
[ 18.674305] rtw_pci 0000:03:00.0: failed to send h2c command
[ 18.674719] rtw_pci 0000:03:00.0: failed to send h2c command
[ 19.197448] rtw_pci 0000:03:00.0: failed to send h2c command
[ 20.246203] rtw_pci 0000:03:00.0: failed to send h2c command
[ 23.507151] rtw_pci 0000:03:00.0: failed to send h2c command
[ 23.507189] rtw_pci 0000:03:00.0: failed to send h2c command
[ 31.958087] rtw_pci 0000:03:00.0: failed to send h2c command
[ 31.958176] rtw_pci 0000:03:00.0: failed to send h2c command
[ 31.958247] rtw_pci 0000:03:00.0: failed to send h2c command
[ 31.958374] rtw_pci 0000:03:00.0: failed to send h2c command
[ 32.561597] rtw_pci 0000:03:00.0: failed to send h2c command
La situation est différente de la fois précédente avec le noyau 5.0.021 car le module chargé a changé et il voit les réseaux, mais il n'arrive pas a établir de connexion.
Hors ligne