Nuliel a écritEst ce que les logs du crash changent lorsque aspm est désactivé? (je sais pas si ton grep a inclus le crash du pilote s'il a eu lieu)
Au passage le secure boot est désactivé?
Oui les retours changent. Par contre, à tort, je n'ai jamais demandé de retour dmesg complet.
On voit en mode normal :
[ 120.760510] rtw_8822be 0000:03:00.0: failed to read ASPM, ret=-5
[ 134.212112] rtw_8822be 0000:03:00.0: stop vif 80:c5:f2:3c:b0:95 on port 0
[ 136.213104] rtw_8822be 0000:03:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[ 147.786646] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 147.787053] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 147.816597] rtw_8822be 0000:03:00.0: Firmware version 13.1.0, H2C version 6
[ 147.829240] rtw_8822be 0000:03:00.0: Refused to change power state, currently in D3
[ 147.831241] rtw_8822be 0000:03:00.0: mac power on failed
[ 147.831246] rtw_8822be 0000:03:00.0: failed to power on mac
[ 147.831248] rtw_8822be 0000:03:00.0: failed to setup chip efuse info
[ 147.831249] rtw_8822be 0000:03:00.0: failed to setup chip information
[ 147.831718] rtw_8822be: probe of 0000:03:00.0 failed with error -114
et avec pcie_aspm=off
mathieu@MatLinux:~$ dmesg | grep rtw
[ 5.239304] rtw_8822be 0000:03:00.0: enabling device (0000 -> 0003)
[ 5.240367] rtw_8822be 0000:03:00.0: Firmware version 27.2.0, H2C version 13
[ 5.339197] rtw_8822be 0000:03:00.0: failed to download firmware
[ 7.339274] rtw_8822be 0000:03:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[ 7.339278] rtw_8822be 0000:03:00.0: failed to setup chip efuse info
[ 7.339281] rtw_8822be 0000:03:00.0: failed to setup chip information
[ 7.342318] rtw_8822be: probe of 0000:03:00.0 failed with error -16
