locks up on fedora32: systemd-udevd hogs cpu #8
Comments
|
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? |
|
I just pushed a new branch, v5.13.4. Please try it to see if it helps. |
|
I had a similar issue and the branch v5.13.4 solved it. |
|
Hi i am relatively new to linux. can you please help me understanding how can i install these drivers? Thank you !! |
|
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: 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 Once you have the necessary components, build the driver with As Fedora has the driver already installed, you may need to blacklist it. In the locked-up condition, run the command 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. |
|
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 Android<https://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 GitHub<#8 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH7PFWRJUEUEKOZIXF2SZI3UXGKGXANCNFSM46DELTXA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://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: ***@***.***>
|
|
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. |
|
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 Android<https://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 GitHub<#8 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH7PFWS6J4NR3KVWXXMCRQDUXGO4ZANCNFSM46DELTXA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://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: ***@***.***>
|
|
You need line 19. Removal of line 35 is OK. |
|
Thanks a lot! but i dont see anything by typing ifconfig. |
|
Your device was not in the tables, but now added. Do a 'git pull', 'make', and 'sudo make install'. |
|
I took the new commit and build it again.. root@# lsmod |
|
There is something funky about the ARM build. On my laptop after modprobe of the module, I get You can ignore the other drivers that need cfg80211, but 8723du definitely does. What CONFIG_PLATFORM variable are you setting in the Makefile? |
|
I havent changed anything in the Makefile |
|
What branch are you using? |
|
branch v5.13.4
Get Outlook for Android<https://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 GitHub<#8 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH7PFWRYKWHRAQBPFIYO6D3UYGNT3ANCNFSM46DELTXA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://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: ***@***.***>
|
|
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"? |
|
both are empty. |
|
Please run 'dmesg > dmesg.txt' and attach file dmesg.txt. |
|
here is the .txt file |
|
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. |
|
Thanks a lot! the build worked with CONFIG_CFG80211_WEXT=y and now i can see wlan0 with internet connectivity. .363244] RTW: rtl8723d_set_FwPwrMode_cmd(): FW LPS mode = 0, SmartPS=2 full logs are : dmesg2.txt |
|
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. |
|
Yes. Thanks a lot for your help! :) |
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
btrtlandrtl8xxxuand have then plugged in my rtl8723du module. Kernel log below, forLinux 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/LinuxThe "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.The text was updated successfully, but these errors were encountered: