LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 12-04-2017, 05:40 PM   #1
mazerunner
Member
 
Registered: Nov 2017
Posts: 57

Rep: Reputation: Disabled
Question WiFi signal way to weak on my HP laptop


I just installed Linux Mint 18.3 "Sylvia" - Cinnamon (64-bit) on my HP laptop but I realize that the WiFi signal is way to weak (40% to 50%)

The rooter is here in the same room, 3 m. away, and there is even visual contact with the rooter's antenna. All other devices, like android tablets and cellphones, seem to get a full signal.

Any ideas as to what can be wrong? Here's my network hardware, checked with inxi -Fxz
Code:
Network:   Card-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
           driver: r8169 v: 2.3LK-NAPI port: 4000 bus-ID: 02:00.0
           IF: enp2s0 state: down mac: <filter>
           Card-2: Realtek RTL8723BE PCIe Wireless Network Adapter
           driver: rtl8723be port: 3000 bus-ID: 03:00.0
           IF: wlo1 state: up mac: <filter>
 
Old 12-04-2017, 10:06 PM   #2
jefro
Moderator
 
Registered: Mar 2008
Posts: 20,163

Rep: Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181
I am not sure the way you get some number on that is reliable.

Could be too close,
poor channel selection,
poor frequency choice,
poor width assignment,
interference with almost any electrical or electronic device.
some driver issue/kernel issue/acpi issue.

Does the thing work as expected or do you just worry that the signal meter is "low"?
 
Old 12-04-2017, 11:28 PM   #3
mazerunner
Member
 
Registered: Nov 2017
Posts: 57

Original Poster
Rep: Reputation: Disabled
No, it does not work as expected.

With Windows 10 on my laptop, I used to have internet when moving to other rooms. Now, I don't. When I move to another room I lose the connection. Only normal, when with absolute eye contact with the rooter antenna I get a 40%. What to expect when a wall comes to stand in between with such a weak signal?
 
Old 12-05-2017, 02:36 AM   #4
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 15,305
Blog Entries: 9

Rep: Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391
please supply the info requested here:
https://forums.bunsenlabs.org/viewtopic.php?id=24
 
Old 12-05-2017, 04:01 AM   #5
ferrari
Senior Member
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 4,768

Rep: Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898
A known issue with some laptops using this chipset in implemtations where two antenna ports are present but only one physical antenna connected....

https://github.com/lwfinger/rtlwifi_new/issues/88

Recent driver builds allow the antenna port to be explicitly selected.
 
Old 12-05-2017, 09:45 AM   #6
mazerunner
Member
 
Registered: Nov 2017
Posts: 57

Original Poster
Rep: Reputation: Disabled
@ferrari: I read the thread but I'm not sure how to proceed.

( edit: I had a problem with "dependencies" of adobeair, but I managed to remove the damn thing. )


Here is the rest of the output, concerning the networking:

uname -rv
Code:
4.10.0-38-generic #42~16.04.1-Ubuntu SMP Tue Oct 10 16:32:20 UTC 2017

lspci -knn | grep -EiA2 net
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 07)
	Subsystem: Hewlett-Packard Company RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [103c:81ee]
	Kernel driver in use: r8169
	Kernel modules: r8169
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723]
	DeviceName: Sanji2 
	Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:81c1]
	Kernel driver in use: rtl8723be
	Kernel modules: rtl8723be
dmesg|grep -Ei 'wlan|firmw|dhc'
Code:
[    0.176197] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    1.422072] [drm] GuC firmware load skipped
[   18.099953] rtl8723be: Using firmware rtlwifi/rtl8723befw.bin
[   18.161298] bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.bin failed with error -2
[   19.066231] rtl8723be 0000:03:00.0 wlo1: renamed from wlan0
[   20.908567] audit: type=1400 audit(1512487163.108:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=813 comm="apparmor_parser"
[   20.908569] audit: type=1400 audit(1512487163.108:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=813 comm="apparmor_parser"
[   20.908570] audit: type=1400 audit(1512487163.108:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=813 comm="apparmor_parser"
[   20.908571] audit: type=1400 audit(1512487163.108:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=813 comm="apparmor_parser"

Last edited by mazerunner; 12-05-2017 at 10:08 AM.
 
Old 12-05-2017, 09:46 AM   #7
mazerunner
Member
 
Registered: Nov 2017
Posts: 57

Original Poster
Rep: Reputation: Disabled
sudo cat /var/log/syslog | grep -Ei 'net|wpa|dhc'
Code:
Dec  5 00:25:13 myLaptop wpa_supplicant[1161]: wlo1: WPA: Group rekeying completed with 58:98:35:11:4a:b8 [GTK=TKIP]
Dec  5 00:30:27 myLaptop wpa_supplicant[1161]: wlo1: CTRL-EVENT-DISCONNECTED bssid=58:98:35:11:4a:b8 reason=4 locally_generated=1
Dec  5 00:30:27 myLaptop NetworkManager[886]: <warn>  [1512426627.5259] sup-iface[0x2185a00,wlo1]: connection disconnected (reason -4)
Dec  5 00:30:27 myLaptop NetworkManager[886]: <info>  [1512426627.5332] device (wlo1): supplicant interface state: completed -> disconnected
Dec  5 00:30:27 myLaptop wpa_supplicant[1161]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec  5 00:30:27 myLaptop NetworkManager[886]: <info>  [1512426627.6304] device (wlo1): supplicant interface state: disconnected -> scanning
Dec  5 00:30:42 myLaptop NetworkManager[886]: <warn>  [1512426642.3955] device (wlo1): link timed out.
Dec  5 00:30:42 myLaptop NetworkManager[886]: <info>  [1512426642.3956] device (wlo1): state change: activated -> failed (reason 'ssid-not-found') [100 120 53]
Dec  5 00:30:42 myLaptop NetworkManager[886]: <info>  [1512426642.3966] manager: NetworkManager state is now CONNECTED_LOCAL
Dec  5 00:30:42 myLaptop NetworkManager[886]: <info>  [1512426642.3971] manager: NetworkManager state is now DISCONNECTED
Dec  5 00:30:42 myLaptop NetworkManager[886]: <warn>  [1512426642.4712] device (wlo1): Activation: failed for connection 'Auto Starbase'
Dec  5 00:30:42 myLaptop NetworkManager[886]: <info>  [1512426642.4781] device (wlo1): state change: failed -> disconnected (reason 'none') [120 30 0]
Dec  5 00:30:42 myLaptop kernel: [ 1153.083329] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
Dec  5 00:30:42 myLaptop systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec  5 00:30:42 myLaptop systemd[1]: Started Network Manager Script Dispatcher Service.
Dec  5 00:30:42 myLaptop NetworkManager[886]: <info>  [1512426642.5444] dhcp4 (wlo1): canceled DHCP transaction, DHCP client pid 1225
Dec  5 00:30:42 myLaptop NetworkManager[886]: <info>  [1512426642.5445] dhcp4 (wlo1): state changed bound -> done
Dec  5 00:30:42 myLaptop NetworkManager[886]: <info>  [1512426642.5463] dns-mgr: Writing DNS information to /sbin/resolvconf
Dec  5 00:30:44 myLaptop NetworkManager[886]: <info>  [1512426644.1259] device (wlo1): supplicant interface state: scanning -> inactive
Dec  5 01:20:35 myLaptop ureadahead[350]: ureadahead:/var/lib/NetworkManager/dhclient-wlo1.conf: Δεν υπάρχει τέτοιο αρχείο ή κατάλογος
Dec  5 01:20:35 myLaptop systemd[1]: Reached target Network (Pre).
Dec  5 01:20:35 myLaptop systemd[1]: Starting Raise network interfaces...
Dec  5 01:20:35 myLaptop systemd[1]: Started Raise network interfaces.
Dec  5 01:20:35 myLaptop kernel: [    0.118721] NET: Registered protocol family 16
Dec  5 01:20:35 myLaptop kernel: [    0.372747] NetLabel: Initializing
Dec  5 01:20:35 myLaptop kernel: [    0.372747] NetLabel:  domain hash size = 128
Dec  5 01:20:35 myLaptop kernel: [    0.372748] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
Dec  5 01:20:35 myLaptop kernel: [    0.372760] NetLabel:  unlabeled traffic allowed by default
Dec  5 01:20:35 myLaptop kernel: [    0.396202] NET: Registered protocol family 2
Dec  5 01:20:35 myLaptop kernel: [    0.396599] NET: Registered protocol family 1
Dec  5 01:20:35 myLaptop kernel: [    1.034088] audit: initializing netlink subsys (disabled)
Dec  5 01:20:35 myLaptop kernel: [    1.325019] NET: Registered protocol family 10
Dec  5 01:20:35 myLaptop kernel: [    1.327575] NET: Registered protocol family 17
Dec  5 01:20:35 myLaptop kernel: [    1.382891] FUJITSU Extended Socket Network Device Driver - version 1.2 - Copyright (c) 2015 FUJITSU LIMITED
Dec  5 01:20:35 myLaptop kernel: [    1.410806] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Dec  5 01:20:35 myLaptop kernel: [   17.654503] NET: Registered protocol family 31
Dec  5 01:20:35 myLaptop kernel: [   20.461114] audit: type=1400 audit(1512429634.615:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=820 comm="apparmor_parser"
Dec  5 01:20:35 myLaptop kernel: [   20.461116] audit: type=1400 audit(1512429634.615:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=820 comm="apparmor_parser"
Dec  5 01:20:35 myLaptop kernel: [   20.461117] audit: type=1400 audit(1512429634.615:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=820 comm="apparmor_parser"
Dec  5 01:20:35 myLaptop kernel: [   20.461117] audit: type=1400 audit(1512429634.615:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=820 comm="apparmor_parser"
Dec  5 01:20:35 myLaptop systemd[1]: Starting Network Manager...
Dec  5 01:20:35 myLaptop kernel: [   21.457343] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Dec  5 01:20:35 myLaptop avahi-daemon[931]: Network interface enumeration completed.
Dec  5 01:20:35 myLaptop acpid: starting up with netlink and the input layer
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.0999] NetworkManager (version 1.2.6) is starting...
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.1000] Read config: /etc/NetworkManager/NetworkManager.conf (etc: default-wifi-powersave-on.conf)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.1302] manager[0x176a200]: monitoring kernel firmware directory '/lib/firmware'.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.1302] monitoring ifupdown state file '/run/network/ifstate'.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.2183] dns-mgr[0x1763950]: init: dns=dnsmasq, rc-manager=resolvconf, plugin=dnsmasq
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.2552] rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0/ieee80211/phy0/rfkill0) (driver rtl8723be)
Dec  5 01:20:37 myLaptop systemd[1]: Started Network Manager.
Dec  5 01:20:37 myLaptop systemd[1]: Reached target Network.
Dec  5 01:20:37 myLaptop systemd[1]: Started vnStat network traffic monitor.
Dec  5 01:20:37 myLaptop systemd[1]: Starting Network Manager Wait Online...
Dec  5 01:20:37 myLaptop systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec  5 01:20:37 myLaptop systemd[1]: Started Network Manager Script Dispatcher Service.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3349] init!
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3350] management mode: unmanaged
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3354] devices added (path: /sys/devices/pci0000:00/0000:00:1c.4/0000:02:00.0/net/enp2s0, iface: enp2s0)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3354] device added (path: /sys/devices/pci0000:00/0000:00:1c.4/0000:02:00.0/net/enp2s0, iface: enp2s0): no ifupdown configuration found.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3354] devices added (path: /sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0/net/wlo1, iface: wlo1)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3354] device added (path: /sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0/net/wlo1, iface: wlo1): no ifupdown configuration found.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3354] devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3354] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3354] end _init.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3355] settings: loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list. (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ifupdown.so)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3355] settings: loaded plugin keyfile: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3357] SettingsPlugin-Ofono: init!
Dec  5 01:20:37 myLaptop NetworkManager[941]: <warn>  [1512429637.3357] SettingsPlugin-Ofono: file doesn't exist: /var/lib/ofono
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3357] SettingsPlugin-Ofono: end _init.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3357] settings: loaded plugin ofono: (C) 2013-2016 Canonical Ltd.  To report bugs please use the NetworkManager mailing list. (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ofono.so)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3358] (24673184) ... get_connections.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.3358] (24673184) ... get_connections (managed=false): return empty list.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4214] keyfile: new connection /etc/NetworkManager/system-connections/Auto Starbase (29dce508-028e-4f3b-a7a3-1e3ca90cde6f,"Auto Starbase")
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4216] SettingsPlugin-Ofono: (24673408) ... get_connections.
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4216] SettingsPlugin-Ofono: (24673408) connections count: 0
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4217] get unmanaged devices count: 0
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4224] settings: hostname: using hostnamed
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4224] settings: hostname changed from (none) to "myLaptop"
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4225] Using DHCP client 'dhclient'
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4226] manager: WiFi enabled by radio killswitch; enabled by state file
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4226] manager: WWAN enabled by radio killswitch; enabled by state file
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4227] manager: Networking is enabled by state file
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4228] Loaded device plugin: NMVxlanFactory (internal)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4228] Loaded device plugin: NMVlanFactory (internal)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4228] Loaded device plugin: NMVethFactory (internal)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4228] Loaded device plugin: NMTunFactory (internal)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4228] Loaded device plugin: NMMacvlanFactory (internal)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4229] Loaded device plugin: NMIPTunnelFactory (internal)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4229] Loaded device plugin: NMInfinibandFactory (internal)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4229] Loaded device plugin: NMEthernetFactory (internal)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4229] Loaded device plugin: NMBridgeFactory (internal)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4229] Loaded device plugin: NMBondFactory (internal)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4544] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4547] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4550] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.4552] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
Dec  5 01:20:37 myLaptop NetworkManager[941]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.5052] device (lo): link connected
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.5057] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/0)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.5060] (wlo1): using nl80211 for WiFi device control
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.5062] device (wlo1): driver supports Access Point (AP) mode
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.5067] manager: (wlo1): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/1)
Dec  5 01:20:37 myLaptop NetworkManager[941]: <info>  [1512429637.5075] device (wlo1): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec  5 01:20:37 myLaptop kernel: [   23.347702] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
Dec  5 01:20:38 myLaptop NetworkManager[941]: <info>  [1512429638.0905] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Dec  5 01:20:38 myLaptop kernel: [   23.929359] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
Dec  5 01:20:38 myLaptop NetworkManager[941]: <info>  [1512429638.0913] keyfile: add connection in-memory (2375b13e-9bba-3cad-be2c-5fb18d8b819f,"Ενσύρματη σύνδεση 1")
Dec  5 01:20:38 myLaptop NetworkManager[941]: <info>  [1512429638.0918] settings: (enp2s0): created default wired connection 'Ενσύρματη σύνδεση 1'
Dec  5 01:20:38 myLaptop NetworkManager[941]: <info>  [1512429638.0924] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec  5 01:20:38 myLaptop kernel: [   23.932560] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
Dec  5 01:20:38 myLaptop kernel: [   24.148296] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
Dec  5 01:20:38 myLaptop NetworkManager[941]: <info>  [1512429638.3303] urfkill disappeared from the bus
Dec  5 01:20:38 myLaptop dbus[933]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Dec  5 01:20:38 myLaptop systemd[1]: Starting WPA supplicant...
Dec  5 01:20:38 myLaptop NetworkManager[941]: <info>  [1512429638.3344] ofono is now available
Dec  5 01:20:38 myLaptop NetworkManager[941]: <info>  [1512429638.3345] bluez: use BlueZ version 5
Dec  5 01:20:38 myLaptop NetworkManager[941]: <warn>  [1512429638.3349] failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
It's too big a text and I have to break it in 6 parts in order to comply with the forum post length limit. I feel like I'm spamming. Would that be alright? Do you really need this?

Last edited by mazerunner; 12-05-2017 at 09:52 AM.
 
Old 12-05-2017, 10:24 AM   #8
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 15,305
Blog Entries: 9

Rep: Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391
actually, scratch all that.

this one fits the problem description perfectly:
Quote:
Originally Posted by ferrari View Post
A known issue with some laptops using this chipset in implemtations where two antenna ports are present but only one physical antenna connected....

https://github.com/lwfinger/rtlwifi_new/issues/88

Recent driver builds allow the antenna port to be explicitly selected.
Quote:
Originally Posted by mazerunner View Post
@ferrari: I read the thread but I'm not sure how to proceed.
first of all, you really need to read through all of it.
from what i can see, you needed to use a particular branch of the driver mentioned, but it isn't quite clear to me if that was merged into the master branch meanwhile.
that you need to find out through reading.

in any case, it looks like you need the option 'ant_sel=Y', where Y can be either 1 or 2.
you need to test this.
adding options to kernel modules.

Last edited by ondoho; 12-05-2017 at 10:36 AM.
 
Old 12-05-2017, 04:32 PM   #9
mazerunner
Member
 
Registered: Nov 2017
Posts: 57

Original Poster
Rep: Reputation: Disabled
damn this is so goddamn difficult...

I read the thread but I don't get half of what's there. What is a "branch"? Is it a driver?

Anyway, from the thread I understand that I should use rock.new_btcoex but I wasn't sure where to get it. So I google and I find it in this page.

I have downloaded the zip and extracted the files. They are in some folder in my home directory.

So, I'm trying to follow these instructions found here, now:
- get Realtek RTL8723BE PCIe Wireless driver here
- save to your usb pendrive.
- copied and extract rock.new_btcoex.zip to your ubuntu/linux mint local folder
- right click on rock.new_btcoex folder and choose "open in terminal".
- Install RTL8723BE PCIe Wifi driver

make
sudo make install


and when I make (that's install here, right?) I get:
error: #error "This branch is abandoned. Please do not use"

I've always hated Microsoft (during the XP era mostly) for having to look for drivers. But this one beats everything. I truly want to cry right now but I'll go to bed and tomorrow, with new spirits, I'll keep trying to understand what exactly is the problem (I'm still not sure. Something with having the wrong number of "antennas" or something, I think. Which, then, I gather must be antennas in the laptop, not visible to the eye.) and even if I don't understand, find some procedure to "make" the "branch" that I might get a descent wifi signal.

Thanks for the help, though. Linux without the community would be impossible. (Now it's just bloody difficult.)

Last edited by mazerunner; 12-05-2017 at 04:33 PM.
 
Old 12-05-2017, 05:04 PM   #10
ferrari
Senior Member
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 4,768

Rep: Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898
As you're using Linux Mint 18.3, from a quick Google I think you'll be using a 4.10.0-38 kernel (or similar). This may mean that the driver already has the ant_sel option. Check with
Code:
sudo modinfo rtl8723be
You should see this option available...
Code:
parm:           ant_sel:Set to 1 or 2 to force antenna number (default 0)
 (int)
It is possible to load the driver with the 'ant_sel' option specifying which antenna port to use. This is a trial and error exercise.

Start by observing weak signals in your scan results (eg -70dBm)
Code:
sudo /usr/sbin/iw dev wl scan wlo1
When the driver is unloaded and reloaded with the ant_sel option (ant_sel=0, 1, or 2)
Code:
sudo modprobe -r rtl8723be
Code:
sudo modprobe -v rtl8723be ant_sel=2
then check the observed signal level in the scan results again. If you've selected the correct antenna port, you'll get a much stronger RSL reported. This can then be made permanent, so that the driver is loaded with this option at boot. This involves creating a custom file in the /etc/modprobe.d/ directory eg /etc/modprobe.d/rtl8723be.conf with something like
Code:
options rtl8723be ips=0 ant_sel=2
FWIW, here's a recent openSUSE thread I helped with which dealt with the same issue.

Last edited by ferrari; 12-05-2017 at 05:11 PM.
 
1 members found this post helpful.
Old 12-05-2017, 05:10 PM   #11
ferrari
Senior Member
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 4,768

Rep: Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898
Quote:
Something with having the wrong number of "antennas" or something, I think. Which, then, I gather must be antennas in the laptop, not visible to the eye.) and even if I don't understand, find some procedure to "make" the "branch" that I might get a descent wifi signal.
Yes, the wifi antennas are built in to your laptop. HP chose to produce some hardware with only one antenna fitted. The Linux driver doesn't know which antenna port the physical antenna is connected to though, so this needs to be manually discovered and specified. Larry Finger (Realtek driver developer) has been liaising with Realtek about this issue, and for now this manual tweak may be needed for some laptops employing this particular wifi hardware. From what I understand though, there are plans to automate this in the driver as the Windows driver probably does already. (I guess by checking signal strength from each port and deducing which port the antenna is connected to.)

Quote:
Thanks for the help, though. Linux without the community would be impossible. (Now it's just bloody difficult.)
Think of these challenges as part of the learning. It's not really a Linux problem though - Realtek and HP needs to share some blame here.
 
Old 12-06-2017, 07:13 AM   #12
mazerunner
Member
 
Registered: Nov 2017
Posts: 57

Original Poster
Rep: Reputation: Disabled
Dear ferrari,
following your instructions I managed to solve the problem!

Indeed, by giving:
Code:
sudo modinfo rtl8723be
I was able to see the option you mentioned.


Then:
Code:
sudo /usr/sbin/iw dev wl scan wlo1
didn't work. Apparently /usr/sbin/iw was not found.

For the rest, I executed both:

Code:
sudo modprobe -r rtl8723be
sudo modprobe -v rtl8723be ant_sel=2
and
Code:
sudo modprobe -r rtl8723be
sudo modprobe -v rtl8723be ant_sel=1
Well, the second one did it.

I appreciate your help a lot. Thanks!

Quote:
Originally Posted by ferrari View Post
Think of these challenges as part of the learning. It's not really a Linux problem though - Realtek and HP needs to share some blame here.
To me computers are backwards. I believe that we live in the caveman age of computers. And it's everybody's "fault". Android seems to be going the right direction: you just touch here and there and things happen with no need to type cryptic string commands to do basic stuff. Btw I don't appreciate Android for other reasons. But this is a rather philosophical discussion altogether.

For the time being, I'm grateful for all the help I get here.
 
1 members found this post helpful.
Old 12-06-2017, 11:57 AM   #13
ferrari
Senior Member
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 4,768

Rep: Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898Reputation: 898
Glad to have been of guidance! You'll need to make it persistent though as I already explained, otherwise get to have the same fun all over again after the next boot.
 
Old 12-06-2017, 12:01 PM   #14
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 15,305
Blog Entries: 9

Rep: Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391Reputation: 4391
Quote:
Originally Posted by mazerunner View Post
Well, the second one did it.
congratulations!
now, to make it permanent.
if you have a file /etc/modprobe.d/modprobe.conf on your system, you can add that line to it.

according to
Code:
man modprobe.d
it should be
Code:
options rtl8723be ant_sel=1
maybe better to create its own .conf file.
 
Old 12-06-2017, 12:16 PM   #15
jlinkels
LQ Guru
 
Registered: Oct 2003
Location: Bonaire, Leeuwarden
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,191

Rep: Reputation: 1039Reputation: 1039Reputation: 1039Reputation: 1039Reputation: 1039Reputation: 1039Reputation: 1039Reputation: 1039
Quote:
Originally Posted by mazerunner;5789615,
To me computers are backwards. I believe that we live in the caveman age of computers. And it's everybody's "fault". Android seems to be going the right direction: you just touch here and there and things happen with no need to type cryptic string commands to do basic stuff.
I happen to disagree. Touch here and there is exactly why OS-es like that are worthless and frustrating. On my Android I have the problem that after 36 hours or so it tells me that "there is no internet connection". While everything looks fine. IP is there, DNS is there, everything which I can see is there. Nothing resolves this (reconnecting, forgetting and re-discover), except for a cold reboot. It happens only on my home network, but all other devices (my son's gawdforbid iShit, other Androids, laptops, Pi's) everything just works. Except for my Android. Too bad it does not revert back to 4G, so I am not WhatsAppable which is very incovenient.

No I have swiped, touched and dragged icons until I am blue in the face, but there is no way to discover what the problem is. I just need to remember to do a cold reboot every morning before breakfast.

So I would be quite happy if I had a command line to enter some cryptic commands. Bottom line: hiding everything and dumbing down to icon shifting is nice, provided everyhting works and you have a fallback. Which there is not with Androids and iShit.

jlinkels
 
1 members found this post helpful.
  


Reply

Tags
wifi problem


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Installed Linux Mint 16 Now very weak wireless signal - keeps disconnecting Smaxwell Linux - Newbie 3 03-25-2014 07:08 AM
weak wifi signals zetrotrack000 Linux - Networking 4 03-28-2013 08:51 AM
Weak signal and slow speed with Realtek RTL8185 mawkernewek Linux - Wireless Networking 30 02-03-2010 05:06 AM
weak signal..5 feet away from router stratotak Linux - Laptop and Netbook 1 01-01-2009 02:57 AM
Weak wifi signal in Ubuntu Hardy LeftyAce Linux - Wireless Networking 4 11-08-2008 11:54 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 02:40 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration