search

lwfinger / rtl8723du

88 stars 44 forks source link

locks up on fedora32: systemd-udevd hogs cpu #8

Open karlp opened 3 years ago

karlp commented 3 years ago

I realize this might not be the clearest or most helpful, but I'm not even sure where to proceed.

I have some rtl8723bu and du modules. The bu modules actually appear to "just work" with the rtl8xxxu driver, and I've reported that to Jens. However, the du modules... don't. Out of the box (no driver from here, standard fedora32 system, whatever that might mean), the btusb driver sees the bluetooth portion, but within a second or two the usb device disconnects, as if the device firmware has crashed.

I've built and installed this driver, and have blacklisted btrtl and rtl8xxxu and have then plugged in my rtl8723du module. Kernel log below, for Linux strem 5.11.22-100.fc32.x86_64 #1 SMP Wed May 19 18:58:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

The "tracker" stuff is I think a red herring, but what I see is that "systemd-udevd" instantly goes to 100% cpu on one core. It stays like this until a few seconds after I disconnect the rtl8723du device. "iw list" or similar commands hang, and can't be killed. Even sudo kill -9 from another terminal will hang. Firefox won't launch, but things that were already running seem to continue working.

Rebooting is the only recovery, and normally requires a hard power off, as network manager hangs trying to "cleanup"

Further, the line Unknown symbol __rtw_dbg (err -2) is presumably why there's no debug info from the driver itself.

Jun 04 16:14:49 strem kernel: usb 1-3: new high-speed USB device number 21 using xhci_hcd
Jun 04 16:14:49 strem kernel: usb 1-3: New USB device found, idVendor=0bda, idProduct=d723, bcdDevice= 2.00
Jun 04 16:14:49 strem kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 04 16:14:49 strem kernel: usb 1-3: Product: 802.11n WLAN Adapter
Jun 04 16:14:49 strem kernel: usb 1-3: Manufacturer: Realtek
Jun 04 16:14:49 strem kernel: usb 1-3: SerialNumber: 00e04c000001
Jun 04 16:14:49 strem kernel: Bluetooth: hci1: RTL: examining hci_ver=08 hci_rev=000d lmp_ver=08 lmp_subver=8723
Jun 04 16:14:49 strem systemd[1]: Starting Load/Save RF Kill Switch Status...
Jun 04 16:14:49 strem kernel: Bluetooth: hci1: RTL: rom_version status=0 version=2
Jun 04 16:14:49 strem kernel: Bluetooth: hci1: RTL: loading rtl_bt/rtl8723d_fw.bin
Jun 04 16:14:49 strem kernel: Bluetooth: hci1: RTL: loading rtl_bt/rtl8723d_config.bin
Jun 04 16:14:49 strem kernel: Bluetooth: hci1: RTL: cfg_sz 10, total sz 33266
Jun 04 16:14:49 strem mtp-probe[4400]: checking bus 1, device 21: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
Jun 04 16:14:49 strem mtp-probe[4400]: bus: 1, device: 21 was not an MTP device
Jun 04 16:14:49 strem systemd[1]: Started Load/Save RF Kill Switch Status.
Jun 04 16:14:49 strem 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/>
Jun 04 16:14:49 strem upowerd[1397]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-3
Jun 04 16:14:49 strem kernel: rtw88_8723d: loading out-of-tree module taints kernel.
Jun 04 16:14:49 strem kernel: rtw88_8723d: module verification failed: signature and/or required key missing - tainting kernel
Jun 04 16:14:49 strem kernel: rtw88_8723d: Unknown symbol __rtw_dbg (err -2)
Jun 04 16:14:49 strem kernel: usbcore: registered new interface driver rtl8723du
Jun 04 16:14:49 strem NetworkManager[898]: <info>  [1622823289.9355] device (wlan0): driver supports Access Point (AP) mode
Jun 04 16:14:49 strem NetworkManager[898]: <info>  [1622823289.9361] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/11)
Jun 04 16:14:49 strem mtp-probe[4410]: checking bus 1, device 21: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
Jun 04 16:14:49 strem mtp-probe[4410]: bus: 1, device: 21 was not an MTP device
Jun 04 16:14:49 strem upowerd[1397]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.2
Jun 04 16:14:49 strem systemd-udevd[4405]: Using default interface naming scheme 'v245'.
Jun 04 16:14:49 strem systemd-udevd[4405]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 04 16:14:49 strem wireless[4417]: setting regulatory domain to IS based on timezone (Atlantic/Reykjavik)
Jun 04 16:14:49 strem kernel: rtl8723du 1-3:1.2 wlp0s20f0u3i2: renamed from wlan0
Jun 04 16:14:49 strem NetworkManager[898]: <info>  [1622823289.9639] rfkill5: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.2/ieee80211/phy1/rfki>
Jun 04 16:14:49 strem NetworkManager[898]: <info>  [1622823289.9654] device (wlan0): interface index 10 renamed iface from 'wlan0' to 'wlp0s20f0u3i2'
Jun 04 16:14:49 strem NetworkManager[898]: <info>  [1622823289.9721] device (wlp0s20f0u3i2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jun 04 16:14:49 strem systemd-udevd[4425]: Using default interface naming scheme 'v245'.
Jun 04 16:14:50 strem kernel: Bluetooth: hci1: RTL: fw version 0x828a96f1
Jun 04 16:14:50 strem bluetoothd[873]: Endpoint registered: sender=:1.106 path=/MediaEndpoint/A2DPSink/sbc
Jun 04 16:14:50 strem bluetoothd[873]: Endpoint registered: sender=:1.106 path=/MediaEndpoint/A2DPSource/sbc
Jun 04 16:14:52 strem ModemManager[871]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3': not supported by any plugin
Jun 04 16:14:54 strem systemd[1]: systemd-rfkill.service: Succeeded.
Jun 04 16:14:54 strem audit[1]: SERVICE_STOP 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/s>
Jun 04 16:14:57 strem systemd[1786]: tracker-extract.service: Succeeded.
Jun 04 16:15:08 strem systemd[1786]: dbus-:1.2-org.gnome.ControlCenter.SearchProvider@1.service: Succeeded.
Jun 04 16:15:16 strem tracker-store[4139]: OK
Jun 04 16:15:16 strem systemd[1786]: tracker-store.service: Succeeded.
Jun 04 16:15:17 strem gnome-shell[2058]: Received error from D-Bus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is no>
Jun 04 16:15:17 strem systemd[1786]: Started dbus-:1.2-org.gnome.Boxes.SearchProvider@2.service.
Jun 04 16:15:17 strem systemd[1786]: Started dbus-:1.2-org.gnome.Calculator.SearchProvider@2.service.
Jun 04 16:15:17 strem systemd[1786]: Started dbus-:1.2-org.gnome.Characters.BackgroundService@2.service.
Jun 04 16:15:17 strem systemd[1786]: Started dbus-:1.2-org.gnome.Contacts.SearchProvider@2.service.
Jun 04 16:15:17 strem systemd[1786]: Started dbus-:1.2-org.gnome.ControlCenter.SearchProvider@2.service.
Jun 04 16:15:17 strem systemd[1786]: Started dbus-:1.2-org.gnome.Documents@2.service.
Jun 04 16:15:17 strem systemd[1786]: Started dbus-:1.2-org.gnome.Nautilus@2.service.
Jun 04 16:15:17 strem systemd[1786]: Started dbus-:1.2-org.gnome.Photos@3.service.
Jun 04 16:15:17 strem systemd[1786]: Started dbus-:1.2-org.gnome.clocks@2.service.
Jun 04 16:15:17 strem systemd[1786]: Started dbus-:1.2-org.gnome.seahorse.Application@6.service.
Jun 04 16:15:17 strem systemd[1786]: Starting Tracker metadata database store and lookup manager...
Jun 04 16:15:17 strem systemd[1786]: Started Tracker metadata database store and lookup manager.
Jun 04 16:15:17 strem systemd[1786]: dbus-:1.2-org.gnome.seahorse.Application@6.service: Succeeded.
Jun 04 16:15:17 strem gnome-shell[2058]: Received error from D-Bus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is no>
Jun 04 16:15:17 strem systemd[1786]: Started dbus-:1.2-org.gnome.seahorse.Application@7.service.
Jun 04 16:15:17 strem gnome-shell[2058]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesk>
Jun 04 16:15:17 strem gnome-shell[2058]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 2 but got 0
Jun 04 16:15:17 strem systemd[1786]: dbus-:1.2-org.gnome.seahorse.Application@7.service: Succeeded.
Jun 04 16:15:17 strem PackageKit[1412]: resolve transaction /7900_dbabcaed from uid 1000 finished with success after 4ms
Jun 04 16:15:17 strem systemd[1786]: Started Application launched by gnome-shell.
Jun 04 16:15:18 strem audit[4694]: NETFILTER_CFG table=filter family=7 entries=0 op=xt_register pid=4694 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 comm=495043204C61756>
Jun 04 16:15:27 strem systemd[1786]: dbus-:1.2-org.gnome.clocks@2.service: Succeeded.
Jun 04 16:15:27 strem systemd[1786]: dbus-:1.2-org.gnome.Boxes.SearchProvider@2.service: Succeeded.
Jun 04 16:15:29 strem systemd[1786]: dbus-:1.2-org.gnome.Nautilus@2.service: Succeeded.
Jun 04 16:15:37 strem systemd[1786]: dbus-:1.2-org.gnome.Calculator.SearchProvider@2.service: Succeeded.
Jun 04 16:15:47 strem systemd[1786]: dbus-:1.2-org.gnome.Characters.BackgroundService@2.service: Succeeded.
Jun 04 16:15:47 strem gnome-contacts-[4438]: Failed to reach quiescence normally (0 backends and 5 persona stores still haven't reached quiescence). Forcing IndividualAggregator quiesc>
Jun 04 16:15:47 strem tracker-store[4492]: OK
Jun 04 16:15:47 strem systemd[1786]: tracker-store.service: Succeeded.
Jun 04 16:15:50 strem systemd-udevd[634]: wlp0s20f0u3i2: Worker [4425] processing SEQNUM=4521 is taking a long time
Jun 04 16:15:50 strem systemd[1786]: dbus-:1.2-org.gnome.Documents@2.service: Succeeded.
Jun 04 16:15:50 strem systemd[1786]: dbus-:1.2-org.gnome.Documents@2.service: Consumed 25.562s CPU time.
Jun 04 16:15:57 strem systemd[1786]: dbus-:1.2-org.gnome.Contacts.SearchProvider@2.service: Succeeded.
Jun 04 16:16:14 strem kernel: usb 1-3: USB disconnect, device number 21
Jun 04 16:16:14 strem bluetoothd[873]: Endpoint unregistered: sender=:1.106 path=/MediaEndpoint/A2DPSink/sbc
Jun 04 16:16:14 strem bluetoothd[873]: Endpoint unregistered: sender=:1.106 path=/MediaEndpoint/A2DPSource/sbc
Jun 04 16:16:14 strem systemd[1]: Starting Load/Save RF Kill Switch Status...
Jun 04 16:16:14 strem systemd[1]: Started Load/Save RF Kill Switch Status.
Jun 04 16:16:14 strem 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/>
Jun 04 16:16:17 strem systemd[1786]: dbus-:1.2-org.gnome.ControlCenter.SearchProvider@2.service: Succeeded.
Jun 04 16:16:20 strem systemd[1]: systemd-rfkill.service: Succeeded.
Jun 04 16:16:19 strem audit[1]: SERVICE_STOP 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/s>
Jun 04 16:17:23 strem gnome-shell[2058]: Received error from D-Bus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is no>
Jun 04 16:17:23 strem systemd[1786]: Started dbus-:1.2-org.gnome.Boxes.SearchProvider@3.service.
lwfinger commented 3 years ago

I do not see this problem with openSUSE TW; however, NetworkManager does not see the device. I tried creating a virtual machine with Fedora34, but that crashed in Setup when I was entering my password. I then downloaded F32 server as I could not find an iso for F32 Workstation. On that VM, I was able to build and install the driver, but I did not get any wifi. The device is shown in dmesg, but no wifi interface is presented. How do you connect?

lwfinger commented 3 years ago

I just pushed a new branch, v5.13.4. Please try it to see if it helps.

Hume2 commented 3 years ago

I had a similar issue and the branch v5.13.4 solved it.

hsnhrn commented 2 years ago

Hi i am relatively new to linux. can you please help me understanding how can i install these drivers? Thank you !!

lwfinger commented 2 years ago

I am not sure the path that Fedora has taken to get this driver into your system, but that lockuo was caused by a change in the kernel. I have seen it before, and I think this repo is fixed. The reason for uncertainty is that I have no device to test.

You can install this repo with these commands: git clone git://github.com/lwfinger/rtl8723du.git -b v5.13.4 cd rtl8723du

It is best practice to do all builds as a normal user. That way, a typo can only mess up your files, but it will not destroy the system!

The first time you build an external module, you must install the distro components needed to build external modules. File README.md shows the commands for a number of distros. For Fedora, the commands are sudo dnf install kernel-headers kernel-devel sudo dnf group install "C Development Tools and Libraries"

Once you have the necessary components, build the driver with make sudo make install

As Fedora has the driver already installed, you may need to blacklist it. In the locked-up condition, run the command lsmod | grep 8723

If the resulting driver is named anything other than "8723du", you will need to blacklist it in /etc/modprobe.d/50-blacklist.conf.

You should look at README.md, particularly about the steps to be taken when your kernel changes.

hsnhrn commented 2 years ago

Hi, thanks a lot. Actually i am using it for Yocto linux. I wrote a recipe to cross compile it and create a .ko file. I loaded the .ko file. What else i need to do?

Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: lwfinger @.> Sent: Friday, January 21, 2022 6:33:31 PM To: lwfinger/rtl8723du @.> Cc: hsnhrn @.>; Comment @.> Subject: Re: [lwfinger/rtl8723du] locks up on fedora32: systemd-udevd hogs cpu (#8)

I am not sure the path that Fedora has taken to get this driver into your system, but that lockuo was caused by a change in the kernel. I have seen it before, and I think this repo is fixed. The reason for uncertainty is that I have no device to test.

You can install this repo with these commands: git clone git://github.com/lwfinger/rtl8723du.git -b v5.13.4 cd rtl8723du

It is best practice to do all builds as a normal user. That way, a typo can only mess up your files, but it will not destroy the system!

The first time you build an external module, you must install the distro components needed to build external modules. File README.md shows the commands for a number of distros. For Fedora, the commands are sudo dnf install kernel-headers kernel-devel sudo dnf group install "C Development Tools and Libraries"

Once you have the necessary components, build the driver with make sudo make install

As Fedora has the driver already installed, you may need to blacklist it. In the locked-up condition, run the command lsmod | grep 8723

If the resulting driver is named anything other than "8723du", you will need to blacklist it in /etc/modprobe.d/50-blacklist.conf.

You should look at README.md, particularly about the steps to be taken when your kernel changes.

— Reply to this email directly, view it on GitHubhttps://github.com/lwfinger/rtl8723du/issues/8#issuecomment-1018719484, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7PFWRJUEUEKOZIXF2SZI3UXGKGXANCNFSM46DELTXA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.Message ID: @.***>

lwfinger commented 2 years ago

I have no idea why you needed to cross compile it. When you say you loaded the file, whet exactly did you do?

If you installed the module correctly, all you need to do is plug it in.

hsnhrn commented 2 years ago

I created a recipe like this.. https://github.com/EmbeddedAndroid/meta-rtlwifi/blob/master/recipes-bsp/drivers/rtl8723bu.bb It is for 8723bu and i did almost the same for 8723du and removed lime 19 and 35. Then i plugged in and it doesnt showed me the interface.

Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: lwfinger @.> Sent: Friday, January 21, 2022 7:13:32 PM To: lwfinger/rtl8723du @.> Cc: hsnhrn @.>; Comment @.> Subject: Re: [lwfinger/rtl8723du] locks up on fedora32: systemd-udevd hogs cpu (#8)

I have no idea why you needed to cross compile it. When you say you loaded the file, whet exactly did you do?

If you installed the module correctly, all you need to do is plug it in.

— Reply to this email directly, view it on GitHubhttps://github.com/lwfinger/rtl8723du/issues/8#issuecomment-1018747065, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7PFWS6J4NR3KVWXXMCRQDUXGO4ZANCNFSM46DELTXA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.Message ID: @.***>

lwfinger commented 2 years ago

You need line 19. Removal of line 35 is OK.

lwfinger commented 2 years ago

@karlp - your issue should now be fixed. Do a 'git pull' and remake.

@hsnhrn - Your recipe is getting the master branch. Proper implementation of cfg80211 requires branch v5.13.4. You need to find out how to do that in line 8. Line 9 is not needed - the source has been fixed for that problem.

hsnhrn commented 2 years ago

Thanks a lot! i am able to build the branch v5.13.4. and its installed in the image. but still the same problem. the logs which i get are these.. [ 49.143664] usb 1-1: new high-speed USB device number 4 using ehci-platform [ 49.354966] usb 1-1: New USB device found, idVendor=7392, idProduct=d611, bcdDevice= 2.00 [ 49.361746] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 49.383673] usb 1-1: Product: 802.11n WLAN Adapter [ 49.387044] usb 1-1: Manufacturer: Realtek [ 49.391126] usb 1-1: SerialNumber: 00e04c000001

but i dont see anything by typing ifconfig. can you please help me if i am missing something? thanks a lot!

lwfinger commented 2 years ago

Your device was not in the tables, but now added. Do a 'git pull', 'make', and 'sudo make install'.

hsnhrn commented 2 years ago

I took the new commit and build it again.. Its showing me the same logs as before. I tried loading the module manually and it shows me these logs below root:~# insmod /lib/modules/5.10.10/8723du.ko [ 335.679956] 8723du: loading out-of-tree module taints kernel. [ 335.854377] RTW: module init start [ 335.856342] RTW: rtl8723du v5.13.4-17-ga6e5ee6.20210514_COEX20200103-3535 [ 335.863132] RTW: rtl8723du BT-Coex version = COEX20200103-3535 [ 335.871274] RTW: rtw_inetaddr_notifier_register [ 335.875567] usbcore: registered new interface driver rtl8723du [ 335.880585] RTW: module init ret=0

root@# lsmod Module Size Used by 8723du 1949696 0 cfg80211 622592 1 8723du sch_fq_codel 20480 2

lwfinger commented 2 years ago

There is something funky about the ARM build. On my laptop after modprobe of the module, I get finger@localhost:~/rtl8723du>lsmod | grep 8723 8723du 2498560 0 cfg80211 1089536 5 iwlmvm,rtw89_core,iwlwifi,8723du,mac80211 usbcore 352256 7 xhci_hcd,ehci_pci,uvcvideo,ehci_hcd,8723du,btusb,xhci_pci finger@localhost:~/rtl8723du>

You can ignore the other drivers that need cfg80211, but 8723du definitely does.

What CONFIG_PLATFORM variable are you setting in the Makefile?

hsnhrn commented 2 years ago

I havent changed anything in the Makefile

lwfinger commented 2 years ago

What branch are you using?

hsnhrn commented 2 years ago

branch v5.13.4

Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: lwfinger @.> Sent: Thursday, January 27, 2022 8:40:45 PM To: lwfinger/rtl8723du @.> Cc: hsnhrn @.>; Mention @.> Subject: Re: [lwfinger/rtl8723du] locks up on fedora32: systemd-udevd hogs cpu (#8)

What branch are you using?

— Reply to this email directly, view it on GitHubhttps://github.com/lwfinger/rtl8723du/issues/8#issuecomment-1023575657, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7PFWRYKWHRAQBPFIYO6D3UYGNT3ANCNFSM46DELTXA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

lwfinger commented 2 years ago

With a better read, I see that 8723du is referencing cfg80211, thus you have built the driver correctly. I did some web searching on how to control wireless networks using Yocto. Unfortunately, I did not find any clear description on how to accomplish this. With a normal Linux distribution, one would use NetworkManager, some other similar package. I use the former, which controls the device and sets up the encryption parameters and communicates with wpa_supplicant to connect to the network.

What is the output of "iw list'?

How about "sudo iw dev wlan0 scan"?

hsnhrn commented 2 years ago

both are empty.

lwfinger commented 2 years ago

Please run 'dmesg > dmesg.txt' and attach file dmesg.txt.

hsnhrn commented 2 years ago

here is the .txt file dmesg.txt I tried to enable "CONFIG_CFG80211_WEXT" in kernel. but after i enable, it broke my my build

lwfinger commented 2 years ago

That build should have worked.

From your dmesg.txt, I could see the kernel finding your device, but it never loaded the driver. The problem is that I put the new device in the wrong place. Please pull and build again.

hsnhrn commented 2 years ago

Thanks a lot! the build worked with CONFIG_CFG80211_WEXT=y and now i can see wlan0 with internet connectivity. But there are now some logs coming continuously like these below..

.363244] RTW: rtl8723d_set_FwPwrMode_cmd(): FW LPS mode = 0, SmartPS=2 [ 425.615284] RTW: rtw_set_ps_mode(wlan0) Enter 802.11 power save - WIFI-TRAFFIC_IDLE [ 425.622219] RTW: rtl8723d_set_FwPwrMode_cmd(): FW LPS mode = 2, SmartPS=2 [ 433.391210] RTW: rtw_set_ps_mode(wlan0) Leave 802.11 power save - WIFI-LPS_CTRL_RX_TRAFFIC_LEAVE [ 433.398687] RTW: rtl8723d_set_FwPwrMode_cmd(): FW LPS mode = 0, SmartPS=2 [ 436.017672] RTW: rtw_set_ps_mode(wlan0) Enter 802.11 power save - WIFI-TRAFFIC_IDLE [ 436.026495] RTW: rtl8723d_set_FwPwrMode_cmd(): FW LPS mode = 2, SmartPS=2 [ 443.570366] RTW: rtw_set_ps_mode(wlan0) Leave 802.11 power save - WIFI-LPS_CTRL_RX_TRAFFIC_LEAVE [ 443.577747] RTW: rtl8723d_set_FwPwrMode_cmd(): FW LPS mode = 0, SmartPS=2 [ 448.499470] RTW: rtw_set_ps_mode(wlan0) Enter 802.11 power save - WIFI-TRAFFIC_IDLE [ 448.506597] RTW: rtl8723d_set_FwPwrMode_cmd(): FW LPS mode = 2, SmartPS=2

full logs are : dmesg2.txt can you please help in this regard as well? what are these? and how to turn it off? :)

lwfinger commented 2 years ago

I turned those off. When I get a chance, I will remove a lot of the other messages that you are getting.

At least we have made progress.

hsnhrn commented 2 years ago

Yes. Thanks a lot for your help! :)