Hi all! from Spain,
First, let me talk about some data on my scenario,
- OS Leap 43.2
- Gigabyte Brix htpc 64bits
- Affected module: rtl8723be
Cause to latest update, NetworkManager wasn’t able to establish connection to my router 4G (Huawei B310S). About wireless net data:
> sudo iwlist wlan0 scan
Cell 01 - Address: 74:A5:28:FB:FE:48
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=70/70 Signal level=-8 dBm
Encryption key:on
ESSID:“Flybox-FE48”
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=00000000bb442611
Extra: Last beacon: 68ms ago
IE: Unknown: 000B466C79626F782D46453438
IE: Unknown: 010882840B162430486C
IE: Unknown: 030101
IE: Unknown: 2A0100
IE: Unknown: 2F0100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 32040C121860
IE: Unknown: 2D1AAC1917FFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1601081500000000000000000000000000000000000000
IE: Unknown: 4A0E14000A002C01C800140005001900
IE: Unknown: 7F080500000000000040
IE: Unknown: DD090010180201000C0000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
IE: Unknown: 46057208010000
Looking for some information about connectivity troubles related to rtl8723be module, I found mention on ant_sel parameter. Thanks to some testing, I found ant_sel=1 as the right paramenter in my case, when system applied 0 as default value.
So I decided to create 50-rtl8723be.conf into /etc/modprobe.d with following content
options rtl8723be ant_sel=1
and by invoking mkinitrd, I “communicated” to system the existence of this script.
But, surprisingly, after reboot I always needed apply rmmod and modprobe rtl8723be in order to make my wireless usable.
I tested the state of sys info by applying
# for f in /sys/module/rtl8723be/parameters/*; do echo -n "$f: " ; cat “$f” ; done
/sys/module/rtl8723be/parameters/ant_sel: 1
/sys/module/rtl8723be/parameters/debug: 0
/sys/module/rtl8723be/parameters/disable_watchdog: N
/sys/module/rtl8723be/parameters/fwlps: Y
/sys/module/rtl8723be/parameters/ips: Y
/sys/module/rtl8723be/parameters/msi: N
/sys/module/rtl8723be/parameters/swenc: N
/sys/module/rtl8723be/parameters/swlps: N
Why the system is not able to deliver the ant_sel parameter from conf file, and is always needed apply rmmod and modprobe from console?
Best Regards,
Welcome to openSUSE Forums. The config file should be all that’s required, so it’s not clear to me why it needs to be reloaded manually. Running the mkinitrd command is necessary.
BTW, the ‘systool’ command is useful when wanting to confirm loaded module parameters…
systool -vm rtl8723be
What is happening when you try to connect to your router? How is your NM connection configured? To share info that here, examine the applicable config file in the /etc/NetworkManager/system-connections/ directory
Hi Deano,
First… I’m sorry, my OS isn’t 43.2 but 42.3 … typo…
ok, here we go! 
>sudo systool -vm rtl8723be
Attributes:
coresize = “114688”
initsize = “0”
initstate = “live”
refcnt = “0”
srcversion = “7746BBEBC9F20CB9616A593”
taint = “O”
uevent = <store method only>
version = “20170718.a24cb56”
Parameters:
ant_sel = “1”
debug = “0”
disable_watchdog = “N”
fwlps = “Y”
ips = “Y”
msi = “N”
swenc = “N”
swlps = “N”
Sections:
.bss = “0xffffffffa0c54540”
.data = “0xffffffffa0c52000”
.data.unlikely = “0xffffffffa0c541a8”
.eh_frame = “0xffffffffa0c50060”
.exit.text = “0xffffffffa0c4cfad”
.gnu.linkonce.this_module= “0xffffffffa0c541c0”
.init.text = “0xffffffffa0c59000”
.note.gnu.build-id = “0xffffffffa0c4d000”
.parainstructions = “0xffffffffa0c4fb40”
.rodata = “0xffffffffa0c4d040”
.rodata.str1.1 = “0xffffffffa0c4f29c”
.rodata.str1.8 = “0xffffffffa0c4dd98”
.strtab = “0xffffffffa0c5bd28”
.symtab = “0xffffffffa0c5a000”
.text = “0xffffffffa0c3c000”
__mcount_loc = “0xffffffffa0c4fbd0”
__param = “0xffffffffa0c4ff20”
/etc/NetworkManager/system-connections/Flybox-FE48
[connection]
id=Flybox-FE48
uuid=794808c4-caca-4fc2-8d9d-de2c011acfdc
type=wifi
permissions=user:xxxxx:;
secondaries=
[wifi]
mac-address=40:E2:30:E9:88:19
mac-address-blacklist=
mode=infrastructure
seen-bssids=
ssid=Flybox-FE48
[wifi-security]
auth-alg=open
group=
key-mgmt=wpa-psk
pairwise=
proto=
psk-flags=1
[ipv4]
dns-search=
method=auto
[ipv6]
dns-search=
method=auto
- For the time being I added to /etc/init.d/after.local the following sentences, in order to automatically get some kind of solution for this problem.
rmmod rtl8723be
modprobe rtl8723be
[to be continued]
… additionally… ]
13 Nov 18:10:25 ntpd[1626]: Listen and drop on 0 v6wildcard ::]:123
13 Nov 18:10:25 ntpd[1626]: Listen and drop on 1 v4wildcard 0.0.0.0:123
13 Nov 18:10:25 ntpd[1626]: Listen normally on 2 lo 127.0.0.1:123
13 Nov 18:10:25 ntpd[1626]: Listen normally on 3 wlan0 192.168.1.101:123
13 Nov 18:10:25 ntpd[1626]: Listen normally on 4 lo ::1]:123
13 Nov 18:10:25 ntpd[1626]: Listen normally on 5 wlan0 [fe80::42e2:30ff:fee9:8819%3]:123
13 Nov 18:10:25 ntpd[1626]: Listening on routing socket on fd #22 for interface updates
13 Nov 18:10:45 ntpd[1626]: receive: Unexpected origin timestamp 0xddb45092.b9124d20 does not match aorg 0000000000.00000000 from server@193.1
45.15.15 xmt 0xddb45095.7f6e889f
13 Nov 18:10:45 ntpd[1626]: receive: Unexpected origin timestamp 0xddb45092.b92e61da does not match aorg 0000000000.00000000 from server@147.1
56.7.26 xmt 0xddb45095.81133fdf
13 Nov 18:15:51 ntpd[1626]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
13 Nov 18:58:07 ntpd[1626]: Deleting interface #3 wlan0, 192.168.1.101#123, interface stats: received=166, sent=166, dropped=1, active_time=28
59 secs
13 Nov 18:58:07 ntpd[1626]: 193.145.15.15 local addr 192.168.1.101 -> <null>
13 Nov 18:58:07 ntpd[1626]: 147.156.7.26 local addr 192.168.1.101 -> <null>
13 Nov 18:58:07 ntpd[1626]: 147.156.7.50 local addr 192.168.1.101 -> <null>
13 Nov 18:58:07 ntpd[1626]: 213.251.52.234 local addr 192.168.1.101 -> <null>
13 Nov 18:58:07 ntpd[1626]: Deleting interface #5 wlan0, fe80::42e2:30ff:fee9:8819%3#123, interface stats: received=0, sent=0, dropped=0, acti
ve_time=2859 secs
13 Nov 19:19:44 ntpd[1626]: ntpd exiting on signal 15 (Terminated)
13 Nov 19:22:04 ntpd[1567]: Listen and drop on 0 v6wildcard ::]:123
13 Nov 19:22:04 ntpd[1567]: Listen and drop on 1 v4wildcard 0.0.0.0:123
13 Nov 19:22:04 ntpd[1567]: Listen normally on 2 lo 127.0.0.1:123
13 Nov 19:22:04 ntpd[1567]: Listen normally on 3 wlan0 192.168.1.101:123
13 Nov 19:22:04 ntpd[1567]: Listen normally on 4 lo ::1]:123
13 Nov 19:22:04 ntpd[1567]: Listen normally on 5 wlan0 [fe80::42e2:30ff:fee9:8819%3]:123
13 Nov 19:22:04 ntpd[1567]: Listening on routing socket on fd #22 for interface updates
13 Nov 19:22:20 ntpd[1567]: receive: Unexpected origin timestamp 0xddb4615b.e6c60b3a does not match aorg 0000000000.00000000 from server@147.1
56.7.18 xmt 0xddb4615c.78e0966b
13 Nov 19:35:54 ntpd[1567]: Deleting interface #3 wlan0, 192.168.1.101#123, interface stats: received=68, sent=68, dropped=1, active_time=829
secs
I don’t know it’s related or not, but I found it strange…
dmesg | grep rtl
4.531481] rtl8723be: Using firmware rtlwifi/rtl8723befw_36.bin
4.581108] ieee80211 phy0: Selected rate control algorithm ‘rtl_rc’
4.581574] rtlwifi: rtlwifi: wireless switch is on
6.993789] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
6.993796] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin
13.987976] rtl8723be: Using firmware rtlwifi/rtl8723befw_36.bin
13.997267] ieee80211 phy1: Selected rate control algorithm ‘rtl_rc’
13.998117] rtlwifi: rtlwifi: wireless switch is on
1204.182846] rtl8723be 0000:02:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
1204.182852] rtl8723be 0000:02:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
# journalctl -u NetworkManager
Journal file /var/log/journal/c41959031fad4b583de40e605a09cda9/system@00055de1c6e597d6-1030024eb5de0c4a.journal~ is truncated, ignoring file.
– Logs begin at lun 2017-11-13 18:10:55 CET, end at jue 2017-12-21 14:00:02 CET. –
nov 13 19:52:50 KOHAI-HOST01 systemd[1]: Starting Network Manager…
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> NetworkManager (version 1.0.12) is starting…
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
nov 13 19:52:50 KOHAI-HOST01 systemd[1]: Started Network Manager.
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded settings plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded settings plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs pleas
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> keyfile: new connection /etc/NetworkManager/system-connections/Flybox-FE48 (0be3a03
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> monitoring kernel firmware directory ‘/lib/firmware’.
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> WiFi hardware radio set disabled
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> WWAN hardware radio set enabled
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMVxlanFactory (internal)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMVlanFactory (internal)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMVethFactory (internal)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMTunFactory (internal)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMMacvlanFactory (internal)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMInfinibandFactory (internal)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMGreFactory (internal)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMEthernetFactory (internal)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMBridgeFactory (internal)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMBondFactory (internal)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/libnm-device-plugin-a
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/libnm-device-plugin-
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-device-plugin-
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> WiFi disabled by radio killswitch; disabled by state file
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> WWAN enabled by radio killswitch; enabled by state file
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> WiMAX enabled by radio killswitch; enabled by state file
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> Networking is enabled by state file
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> (lo): link connected
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> (lo): new Generic device (carrier: ON, driver: ‘unknown’, ifindex: 1)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> (wlan0): using nl80211 for WiFi device control
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> (wlan0): driver supports Access Point (AP) mode
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> (wlan0): new 802.11 WiFi device (carrier: UNKNOWN, driver: ‘rtl8723be’, ifindex: 3)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> (wlan0): device state change: unmanaged → unavailable (reason ‘managed’) [10 20 2]
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> (eth0): new Ethernet device (carrier: OFF, driver: ‘r8169’, ifindex: 2)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> (eth0): device state change: unmanaged → unavailable (reason ‘managed’) [10 20 2]
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> keyfile: add connection in-memory (42cd86ed-685e-499e-97ea-84edb12981da,"Wired conn
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> (eth0): created default wired connection ‘Wired connection 1’ (->I used for some days a wired connection in order to test what’s happening with wifi conn)
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> use BlueZ version 5
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> ModemManager available in the bus
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> wpa_supplicant running
nov 13 19:52:56 KOHAI-HOST01 NetworkManager[1037]: <info> startup complete
nov 13 19:53:12 KOHAI-HOST01 NetworkManager[1037]: <info> connectivity: check for uri ‘http://conncheck.opensuse.org’ failed with 'Error reso
nov 13 19:58:27 KOHAI-HOST01 systemd[1]: Stopping Network Manager…
nov 13 19:58:27 KOHAI-HOST01 NetworkManager[1037]: <info> caught SIGTERM, shutting down normally.
nov 13 19:58:27 KOHAI-HOST01 NetworkManager[1037]: <info> (wlan0): device state change: unavailable → unmanaged (reason ‘unmanaged’) [20 10
nov 13 19:58:27 KOHAI-HOST01 NetworkManager[1037]: <info> (eth0): device state change: unavailable → unmanaged (reason ‘unmanaged’) [20 10 3
nov 13 19:58:27 KOHAI-HOST01 NetworkManager[1037]: <info> exiting (success)
nov 13 19:58:27 KOHAI-HOST01 systemd[1]: Stopped Network Manager.
– Reboot –
… and more…
I hope this helps.
Looking forward to hearing from you,
Please enclose all commands and output within code tags (refer to the ‘#’ button in the forum editor). Your opening post isn’t clear about whether you’ve been able to connect via wifi at all. The NetworkManager logging suggests that the wifi device is disabled…
nov 13 19:52:50 KOHAI-HOST01 NetworkManager[1037]: <info> WiFi disabled by radio killswitch; disabled by state file
/usr/sbin/rfkill list
If the wifi is soft-blocked it can be unblocked with
sudo /usr/sbin/rfkill unblock wifi
You can also check the NetworkManager interface states with the following as root.
sudo cat /var/lib/NetworkManager/NetworkManager.state
*If necessary, that file can be deleted (as root) and restart NetworkManager
sudo systemctl restart NetworkManager
Check that wifi is enabled…
nmcli g
and the NM interface states…
nmcli d
Capture the NetworkManager log again when you try to connect to your AP.