Description of problem: Wireless card RTL8723BE has a weak signal even if I stand next to the wireless AP. Version-Release number of selected component (if applicable): 08:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter How reproducible: The driver has been loaded but the signal is weak and network disconnects are frequently. Steps to Reproduce: 1. lsmod | grep rtl8732be rtl8723be 86016 0 btcoexist 53248 1 rtl8723be rtl8723_common 24576 1 rtl8723be rtl_pci 28672 1 rtl8723be rtlwifi 73728 2 rtl_pci,rtl8723be mac80211 696320 3 rtl_pci,rtlwifi,rtl8723be cfg80211 536576 2 mac80211,rtlwifi btrtl 16384 1 btusb bluetooth 487424 39 bnep,btbcm,btrtl,btusb,rfcomm,btintel 2. dmesg | grep rtl [ 3.392999] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723 [ 3.393003] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin [ 3.692495] rtl8723be: Using firmware rtlwifi/rtl8723befw.bin [ 3.696967] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' [ 3.697504] rtlwifi: rtlwifi: wireless switch is on [ 3.701026] rtl8723be 0000:08:00.0 wlo1: renamed from wlan0 [ 66.770706] Modules linked in: ccm rfcomm fuse cmac xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_broute bridge stp llc ebtable_filter ebtable_nat ebtables ip6table_mangle ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_security ip6table_filter ip6_tables iptable_mangle iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_security bnep arc4 rtl8723be btcoexist rtl8723_common rtl_pci rtlwifi intel_rapl mac80211 x86_pkg_temp_thermal coretemp kvm iTCO_wdt iTCO_vendor_support hp_wmi crct10dif_pclmul ppdev sparse_keymap crc32_pclmul crc32c_intel snd_hda_codec_realtek cfg80211 snd_hda_codec_hdmi snd_hda_codec_generic [ 66.770741] snd_hda_intel vfat fat btusb btrtl snd_hda_codec btbcm uvcvideo btintel bluetooth snd_hda_core videobuf2_vmalloc snd_hwdep videobuf2_core joydev snd_seq videobuf2_memops v4l2_common videodev snd_seq_device i2c_i801 snd_pcm media snd_timer processor_thermal_device lpc_ich int340x_thermal_zone snd shpchp rfkill intel_soc_dts_iosf soundcore hp_accel mei_me mei parport_pc lis3lv02d iosf_mbi parport hp_wireless input_polldev int3400_thermal acpi_thermal_rel acpi_pad tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper drm r8169 serio_raw mii wmi video fjes 3. Actual results: The signal is weka Expected results: Additional info:
Just to report back. The issue has been resolved by performing the following steps: 1) I pulled the github tree of rtl8723be drivers from here: https://github.com/lwfinger/rtlwifi_new 2) Did a ./configure && make && make install 3) Then created /etc/modprobe.d/50-rtl8723be.conf file with the following content: options rtl8723be ips=0 ant_sel=2 4) Rebooted the machine and I had full signal now. 5) The topic describing this issue is here: https://github.com/lwfinger/rtlwifi_new/issues/34
Comments from lwfinger suggest antenna selection will be enhanced in kernel 4.7, though the code changes are suitable for back porting to earlier 4.x kernels. https://github.com/lwfinger/rtlwifi_new/issues/28#issuecomment-198845381 This issue is affecting my HP 250 G4 laptop. Having wireless networking work with Fedora, without building kernel modules would be great. Thanks, Paul
kernel-4.4.8-300.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-8a1f49149e
kernel-4.4.8-200.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-373c063e79
kernel-4.4.8-200.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-373c063e79
kernel-4.4.8-300.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8a1f49149e
kernel-4.4.8-300.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
kernel-4.4.8-200.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Why is this considered to be fixed? In F24, on two different laptops I have had to add ant_sel=1 to modprobe for them to have working wifi. Current kernel is 4.6.7-300.fc24.x86_64.
My understanding is that some manufactures have incorrectly set the fuses that indicate which port the antenna is connected to. Normally the driver reads the hardware value and tells the card to use the signal from that port. Before this "fix", the driver would use the wrong port as indicated by flawed hardware, resulting in a very weak signal. Now that the upstream fix is present in Fedora, users have the option of manually telling the driver where the antenna is, overriding the incorrect hardware. It would be even better if this correction could be done in software without manual intervention. However if at all possible, that would be a task for the upstream driver maintainer. Fedora has backported the "ant_sel" option, giving users the option of a manual workaround. The fix is not ideal, but at least a manual workaround now exists.
Created attachment 1320293 [details] dnf history info 269
After some recent updates on Fedora 26, Realtek rtl8723be wireless card has wifi signal problems. The signal is very weak again and I had to reopen this bug. In the log you'll find the latest updates that broke the wireless card. Current running kernel: 4.12.8-300.fc26.x86_64 If further information is required, please let me know.
This bug is currently reported against a Fedora version which is already unsuported. I am changing the version to '27', the latest supported release. Please check whether this bug is still an issue on the '27' release. If you find this bug not being applicable on this release, please close it.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.17.7-100.fc27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28. If you experience different issues, please open a new bug report for those.
I am new to Fedora and is using Fedora 28 right now. Yes, I'm still experiencing this issue on Fedora 28. I have tried almost everything but it did no good. As I said I am new to Fedora 28, thus, I don't know how to change the version. For this reason, I'm reporting this as a comment.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.18.10-100.fc27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 28 or Fedora 29, and are still experiencing this issue, please change the version to Fedora 28 or 29. If you experience different issues, please open a new bug report for those.
The issue on Fedora27 is still present with the latest kernel. I haven't updated to F28 to see if this changes the situation. I will soon update to F28 and will let you know if the issue has been resolved.
Unfortunately, I haven't been able to test RTL8723BE wireless card on Fedora 28. If someone else did so, please update the issue.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.