floripaolo
Posts: 30
Joined: Thu Jun 14, 2018 10:16 am

WIFI dongle problem/spotty ssh connection

Fri Jan 24, 2020 9:43 am

I've been trying for several days now to configure my new external USB dongle for my RBPiZeroW since the onboard WIFI has a poor range. I also deactivated the onboard WIFI (blacklist).
At the moment I'm hooked up with an Ethernet adapter. But when I try connecting with the dongle (ethernet adapter removed) it appears to connect only occasionally. Btw: I'm not certain that connection drops altogether, but ssh-terminal stops working.

Here (hopefully) all relevant information:

Code: Select all

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.19.66+ #1253 Thu Aug 15 11:37:30 BST 2019 armv6l GNU/Linux
pi@raspberrypi:~ $ lsusb
Bus 001 Device 004: ID 0b95:772a ASIX Electronics Corp. AX88772A Fast Ethernet
Bus 001 Device 003: ID 0bda:f179 Realtek Semiconductor Corp. 
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@raspberrypi:~ $ lsmod
Module                  Size  Used by
fuse                   99599  3
rfcomm                 39694  4
cmac                    3433  1
bnep                   12862  2
hci_uart               30598  1
btbcm                   7822  1 hci_uart
serdev                 11024  1 hci_uart
bluetooth             397525  29 hci_uart,bnep,btbcm,rfcomm
ecdh_generic           19994  2 bluetooth
rtl8188fu             978209  0
sha256_generic         10778  0
asix                   27102  0
libphy                 64660  1 asix
cfg80211              596688  1 rtl8188fu
rfkill                 22462  5 bluetooth,cfg80211
raspberrypi_hwmon       2959  0
snd_bcm2835            17068  1
hwmon                  11200  1 raspberrypi_hwmon
snd_pcm                92916  1 snd_bcm2835
snd_timer              23433  1 snd_pcm
snd                    63223  5 snd_timer,snd_bcm2835,snd_pcm
i2c_bcm2835             7818  0
bcm2835_codec          28684  0
bcm2835_v4l2           35910  0
v4l2_mem2mem           18877  1 bcm2835_codec
bcm2835_mmal_vchiq     20644  2 bcm2835_codec,bcm2835_v4l2
v4l2_common             7385  1 bcm2835_v4l2
videobuf2_dma_contig    10303  1 bcm2835_codec
videobuf2_vmalloc       6084  1 bcm2835_v4l2
videobuf2_memops        1973  2 videobuf2_dma_contig,videobuf2_vmalloc
videobuf2_v4l2         16373  3 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem
videobuf2_common       37369  4 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
videodev              182789  6 bcm2835_codec,v4l2_common,videobuf2_common,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
media                  27597  2 videodev,v4l2_mem2mem
vc_sm_cma              25091  1 bcm2835_mmal_vchiq
fixed                   3336  0
uio_pdrv_genirq         3953  0
uio                    11360  1 uio_pdrv_genirq
i2c_dev                 7171  0
ip_tables              13419  0
x_tables               24457  1 ip_tables
ipv6                  429245  22
pi@raspberrypi:~ $ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
auto wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
pi@raspberrypi:~ $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=CH

network={
	ssid="xxxxxx"
	psk="xxxxxx"
}

pi@raspberrypi:~ $ 
Last edited by floripaolo on Fri Jan 24, 2020 2:14 pm, edited 1 time in total.

User avatar
B.Goode
Posts: 9243
Joined: Mon Sep 01, 2014 4:03 pm
Location: UK

Re: WIFI dongle problem/spotty ssh connection

Fri Jan 24, 2020 11:14 am

Maybe your RPi, or your site router, or both, are getting confused by having two possible network paths to the same device?

My Troubleshooting suggestion would be to remove the external Ethernet adapter from the RPi, then power cycle both the RPi and the router, then retry using only the external WiFi dongle for access to your LAN.

Lewis-H
Posts: 24
Joined: Thu Oct 31, 2019 12:45 pm

Re: WIFI dongle problem/spotty ssh connection

Fri Jan 24, 2020 12:18 pm

Edit /etc/network/interfaces and insert these configuration values:

auto lo
iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
auto wlan0

iface wlan0 inet dhcp
wpa-ssid YOURESSID
wpa-psk YOURWPAPASSWORD

floripaolo
Posts: 30
Joined: Thu Jun 14, 2018 10:16 am

Re: WIFI dongle problem/spotty ssh connection

Tue Jan 28, 2020 5:56 am

B.Goode wrote:
Fri Jan 24, 2020 11:14 am
Maybe your RPi, or your site router, or both, are getting confused by having two possible network paths to the same device?

My Troubleshooting suggestion would be to remove the external Ethernet adapter from the RPi, then power cycle both the RPi and the router, then retry using only the external WiFi dongle for access to your LAN.
I forgot to mention that the problem persists without ethernet adapter.

floripaolo
Posts: 30
Joined: Thu Jun 14, 2018 10:16 am

Re: WIFI dongle problem/spotty ssh connection

Tue Jan 28, 2020 6:05 am

floripaolo wrote:
Tue Jan 28, 2020 5:56 am
B.Goode wrote:
Fri Jan 24, 2020 11:14 am
Maybe your RPi, or your site router, or both, are getting confused by having two possible network paths to the same device?

My Troubleshooting suggestion would be to remove the external Ethernet adapter from the RPi, then power cycle both the RPi and the router, then retry using only the external WiFi dongle for access to your LAN.
I forgot to mention that the problem persists without ethernet adapter.
Now the headless RPi won't connect at all. Neither over WIFI nor over ethernet.

MrEngman
Posts: 3946
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: WIFI dongle problem/spotty ssh connection

Tue Jan 28, 2020 10:43 am

With the newer versions of Raspbian on the Pi do not edit file /etc/network/interfaces as this can really mess up the network configuration. Leave it as the default like

Code: Select all

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
Set up file /etc/wpa_supplicant/wpa_supplicant.conf like

Code: Select all

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=CH

network={
        ssid="network-name"
        psk="network-password"
}

MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

floripaolo
Posts: 30
Joined: Thu Jun 14, 2018 10:16 am

Re: WIFI dongle problem/spotty ssh connection

Tue Jan 28, 2020 12:38 pm

@MrEngman Those where the settings I had originally. By turning off the onboard Wifi on /etc/modprobe.d with blacklist brcmfmac I end up not having wifi at all. Here again the info data:

Code: Select all

pi@raspberrypi:~ $ lsusb
Bus 001 Device 002: ID 0bda:f179 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Code: Select all

pi@raspberrypi:~ $ lsmod
Module                  Size  Used by
fuse                   99599  3
rfcomm                 39694  4
cmac                    3433  1
bnep                   12862  2
hci_uart               30598  1
btbcm                   7822  1 hci_uart
serdev                 11024  1 hci_uart
bluetooth             397525  29 hci_uart,bnep,btbcm,rfcomm
ecdh_generic           19994  2 bluetooth
rtl8188fu             978209  0
brcmfmac              280034  0
brcmutil                9617  1 brcmfmac
sha256_generic         10778  0
cfg80211              596688  2 rtl8188fu,brcmfmac
raspberrypi_hwmon       2959  0
hwmon                  11200  1 raspberrypi_hwmon
snd_bcm2835            17068  1
snd_pcm                92916  1 snd_bcm2835
snd_timer              23433  1 snd_pcm
rfkill                 22462  7 bluetooth,cfg80211
snd                    63223  5 snd_timer,snd_bcm2835,snd_pcm
i2c_bcm2835             7818  1
bcm2835_codec          28684  0
bcm2835_v4l2           35910  0
v4l2_mem2mem           18877  1 bcm2835_codec
bcm2835_mmal_vchiq     20644  2 bcm2835_codec,bcm2835_v4l2
v4l2_common             7385  1 bcm2835_v4l2
videobuf2_dma_contig    10303  1 bcm2835_codec
videobuf2_vmalloc       6084  1 bcm2835_v4l2
videobuf2_memops        1973  2 videobuf2_dma_contig,videobuf2_vmalloc
videobuf2_v4l2         16373  3 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem
videobuf2_common       37369  4 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
videodev              182789  6 bcm2835_codec,v4l2_common,videobuf2_common,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
media                  27597  2 videodev,v4l2_mem2mem
vc_sm_cma              25091  1 bcm2835_mmal_vchiq
uio_pdrv_genirq         3953  0
fixed                   3336  0
uio                    11360  1 uio_pdrv_genirq
i2c_dev                 7171  2
ip_tables              13419  0
x_tables               24457  1 ip_tables
ipv6                  429245  24

Code: Select all

pi@raspberrypi:~ $  cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

Code: Select all

pi@raspberrypi:~ $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=CH

network={
	ssid="Txxxxxxx"
	psk="xxxxx"
}

MrEngman
Posts: 3946
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: WIFI dongle problem/spotty ssh connection

Tue Jan 28, 2020 4:03 pm

Hi floripaolo,

I've just tried setting up my Pi 0 W like you have and I have it working with the brcmfmac driver blacklisted and connected to my wifi network using the rtl8188fu driver using a wifi module with the same USB id you have.

Not sure how you got kernel 4.19.66+ #1253 as it's not available as an image file. So I started by creating a new SD card using image 2019-07-10-raspbian-buster-lite.zip which installed kernel 4.19.57+ #1244. Then booted the Pi 0 W and changed the password and the hostname, Rebooted and then installed nmap which I use to scan my network to see which devices are connected to it and installed my install-wifi script to install the 8188fu wifi driver I compile. I then ran command sudo rpi-update 11ef44989ad8564347301ec01bca9aaba89cb5e9 to update the kernel to 4.19.66+ #1253 and installed the 8188fu wifi driver.

I then rebooted and the Pi-0-W booted with the build in wifi and the 8188fu wifi both connected.

Code: Select all

pi@Pi-0-W:~ $ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.16.19  netmask 255.255.255.0  broadcast 192.168.16.255
        inet6 fe80::c66:7df0:b38f:7ad6  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:cc:7e:89  txqueuelen 1000  (Ethernet)
        RX packets 111  bytes 10682 (10.4 KiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 64  bytes 11189 (10.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.16.25  netmask 255.255.255.0  broadcast 192.168.16.255
        inet6 fe80::6af6:31fa:1c4f:fec8  prefixlen 64  scopeid 0x20<link>
        ether 00:e0:25:2d:91:35  txqueuelen 1000  (Ethernet)
        RX packets 139  bytes 18016 (17.5 KiB)
        RX errors 0  dropped 3  overruns 0  frame 0
        TX packets 47  bytes 7851 (7.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I then created a file /etc/modprobe.d/brcmfmac.conf, using command sudo nano /etc/modprobe.d/brcmfmac.conf, with a single line in it blacklist brcmfmac to blacklist the brcmfmac driver and stop the built in wifi running.

Then rebooted again and the Pi-0-W booted with just the 8188fu wifi connected.

Code: Select all

pi@Pi-0-W:~ $ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.16.25  netmask 255.255.255.0  broadcast 192.168.16.255
        inet6 fe80::6af6:31fa:1c4f:fec8  prefixlen 64  scopeid 0x20<link>
        ether 00:e0:25:2d:91:35  txqueuelen 1000  (Ethernet)
        RX packets 292  bytes 36706 (35.8 KiB)
        RX errors 0  dropped 5  overruns 0  frame 0
        TX packets 102  bytes 16576 (16.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pi@Pi-0-W:~ $ lsusb
Bus 001 Device 002: ID 0bda:f179 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@Pi-0-W:~ $ lsmod
Module                  Size  Used by
bnep                   12862  2
hci_uart               30598  1
btbcm                   7822  1 hci_uart
serdev                 11024  1 hci_uart
bluetooth             397525  24 hci_uart,bnep,btbcm
ecdh_generic           19994  1 bluetooth
8021q                  23744  0
garp                    7383  1 8021q
stp                     2297  1 garp
llc                     5642  2 garp,stp
rtl8188fu             978209  0
sha256_generic         10778  0
cfg80211              596688  1 rtl8188fu
rfkill                 22462  5 bluetooth,cfg80211
raspberrypi_hwmon       2959  0
hwmon                  11200  1 raspberrypi_hwmon
snd_bcm2835            17068  1
snd_pcm                92916  1 snd_bcm2835
snd_timer              23433  1 snd_pcm
snd                    63223  5 snd_timer,snd_bcm2835,snd_pcm
bcm2835_codec          28684  0
v4l2_mem2mem           18877  1 bcm2835_codec
bcm2835_v4l2           35910  0
bcm2835_mmal_vchiq     20644  2 bcm2835_codec,bcm2835_v4l2
v4l2_common             7385  1 bcm2835_v4l2
videobuf2_dma_contig    10303  1 bcm2835_codec
videobuf2_vmalloc       6084  1 bcm2835_v4l2
videobuf2_memops        1973  2 videobuf2_dma_contig,videobuf2_vmalloc
videobuf2_v4l2         16373  3 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem
videobuf2_common       37369  4 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
videodev              182789  6 bcm2835_codec,v4l2_common,videobuf2_common,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
media                  27597  2 videodev,v4l2_mem2mem
vc_sm_cma              25091  1 bcm2835_mmal_vchiq
uio_pdrv_genirq         3953  0
fixed                   3336  0
uio                    11360  1 uio_pdrv_genirq
ip_tables              13419  0
x_tables               24457  1 ip_tables
ipv6                  429245  18
pi@Pi-0-W:~ $ uname -a
Linux Pi-0-W 4.19.66+ #1253 Thu Aug 15 11:37:30 BST 2019 armv6l GNU/Linux
So it seems it is possible to set up the Pi-0-W in the way you want it. Not sure if anything here will help you but at least it shows it is possible to get the Pi-0-W running with the built in wifi disabled and using a separate wifi module.



MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

floripaolo
Posts: 30
Joined: Thu Jun 14, 2018 10:16 am

Re: WIFI dongle problem/spotty ssh connection

Tue Jan 28, 2020 8:21 pm

I flashed a new image but before updating to the new kernel i installed the driver:

Code: Select all

pi@raspberrypi:~ $ sudo install-wifi

 *** Raspberry Pi wifi driver installer by MrEngman.
 *** Performing self-update
 *** Relaunching after update

 *** Raspberry Pi wifi driver installer by MrEngman.

Your current kernel revision = 4.19.57+
Your current kernel build    = #1244

Checking for a wifi module to determine the driver to install.

Your wifi module is Bus 001 Device 002: ID 0bda:f179 Realtek Semiconductor Corp. 

And it uses the 8188fu driver.


Your Pi revision number is 
9000c1
You have a Pi 0 W v1.1
Checking for a 8188fu wifi driver module for your current kernel.
There is a driver module available for this kernel revision.
Downloading the 8188fu driver, 8188fu-4.19.57-1244.tar.gz.
Installing the 8188fu driver.

Installing driver config file rtl8188fu.conf.
mv rtl8188fu.conf /etc/modprobe.d/.
Installing driver module rtl8188fu.ko.
install -p -m 644 rtl8188fu.ko /lib/modules/4.19.57+/kernel/drivers/net/wireless
install: cannot create regular file '/lib/modules/4.19.57+/kernel/drivers/net/wireless': No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.19.57+: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
Loading and running the 8188fu driver, rtl8188fu.ko.
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.19.57+/modules.dep.bin'
modprobe: FATAL: Module rtl8188fu not found in directory /lib/modules/4.19.57+

then I updated Kernel (because i figured something went wrong):

Code: Select all

##############################################################
Would you like to proceed? (y/N)
 *** Downloading specific firmware revision (this will take a few minutes)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   168    0   168    0     0    492      0 --:--:-- --:--:-- --:--:--   492
100 89.9M    0 89.9M    0     0  1238k      0 --:--:--  0:01:14 --:--:-- 1361k
 *** Updating firmware
 *** Updating kernel modules
 *** depmod 4.19.66+
 *** depmod 4.19.66-v7+
 *** depmod 4.19.66-v7l+
 *** Updating VideoCore libraries
 *** Using HardFP libraries
 *** Updating SDK
 *** Running ldconfig
 *** Storing current firmware revision
 *** Deleting downloaded files
 *** Syncing changes to disk
 *** If no errors appeared, your firmware was successfully updated to 11ef44989ad8564347301ec01bca9aaba89cb5e9
 *** A reboot is needed to activate the new firmware
Then I rebooted and installed the driver

Code: Select all

pi@raspberrypi:~ $ sudo install-wifi

 *** Raspberry Pi wifi driver installer by MrEngman.
 *** Performing self-update
 *** Relaunching after update

 *** Raspberry Pi wifi driver installer by MrEngman.

Your current kernel revision = 4.19.66+
Your current kernel build    = #1253

Checking for a wifi module to determine the driver to install.

Your wifi module is Bus 001 Device 002: ID 0bda:f179 Realtek Semiconductor Corp. 

And it uses the 8188fu driver.


Your Pi revision number is 
9000c1
You have a Pi 0 W v1.1
Checking for a 8188fu wifi driver module for your current kernel.
There is a driver module available for this kernel revision.
Downloading the 8188fu driver, 8188fu-4.19.66-1253.tar.gz.
Installing the 8188fu driver.

Installing driver config file rtl8188fu.conf.
mv rtl8188fu.conf /etc/modprobe.d/.
Installing driver module rtl8188fu.ko.
install -p -m 644 rtl8188fu.ko /lib/modules/4.19.66+/kernel/drivers/net/wireless
Loading and running the 8188fu driver, rtl8188fu.ko.
This time no error messages. Then I blacklisted the onboard wifi. Rebooted but no luck.... The RPi doesn't show up....

MrEngman
Posts: 3946
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: WIFI dongle problem/spotty ssh connection

Tue Jan 28, 2020 10:08 pm

floripaolo wrote:
Tue Jan 28, 2020 8:21 pm
I flashed a new image but before updating to the new kernel i installed the driver:

Code: Select all

pi@raspberrypi:~ $ sudo install-wifi

 *** Raspberry Pi wifi driver installer by MrEngman.
 *** Performing self-update
 *** Relaunching after update

 *** Raspberry Pi wifi driver installer by MrEngman.

Your current kernel revision = 4.19.57+
Your current kernel build    = #1244

Checking for a wifi module to determine the driver to install.

Your wifi module is Bus 001 Device 002: ID 0bda:f179 Realtek Semiconductor Corp. 

And it uses the 8188fu driver.


Your Pi revision number is 
9000c1
You have a Pi 0 W v1.1
Checking for a 8188fu wifi driver module for your current kernel.
There is a driver module available for this kernel revision.
Downloading the 8188fu driver, 8188fu-4.19.57-1244.tar.gz.
Installing the 8188fu driver.

Installing driver config file rtl8188fu.conf.
mv rtl8188fu.conf /etc/modprobe.d/.
Installing driver module rtl8188fu.ko.
install -p -m 644 rtl8188fu.ko /lib/modules/4.19.57+/kernel/drivers/net/wireless
install: cannot create regular file '/lib/modules/4.19.57+/kernel/drivers/net/wireless': No such file or directory
depmod: ERROR: could not open directory /lib/modules/4.19.57+: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
Loading and running the 8188fu driver, rtl8188fu.ko.
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.19.57+/modules.dep.bin'
modprobe: FATAL: Module rtl8188fu not found in directory /lib/modules/4.19.57+
One way this error can happen is if you ran commands

Code: Select all

sudo apt-get update
sudo apt-get upgrade
and the upgrade installed a new kernel as if it does it will remove the old modules directories and you did not reboot before trying to install the wifi driver. This can happen as it is not always obvious that you will need to reboot.

If the kernel was updated and you did not reboot and the original directories were deleted then you would get the error you saw. If you didn't run sudo apt-get upgrade then I don't know why you would get that error.


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

floripaolo
Posts: 30
Joined: Thu Jun 14, 2018 10:16 am

Re: WIFI dongle problem/spotty ssh connection

Wed Jan 29, 2020 3:58 am

I started from scratch and did all the steps you described:
- flashed system
- booted, changed pwd
- rebooted installed nmp and install-wifi script and compiled
- rpi-updated and rebooted
- installed 8188fu driver with install-wifi
- rebooted

What I then get is:

Code: Select all

pi@raspberrypi:~ $ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.200  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 2001:1716:460b:c940:b7a0:9816:36ba:616e  prefixlen 64  scopeid 0x0<global>
        inet6 fdaa:bbcc:ddee:0:4fb:ae8:59b8:502c  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::74c9:c657:854a:6da  prefixlen 64  scopeid 0x20<link>
        inet6 2001:1716:460b:c940:d58d:c78d:50bd:c21f  prefixlen 128  scopeid 0x0<global>
        ether b8:27:eb:ba:2b:bf  txqueuelen 1000  (Ethernet)
        RX packets 255  bytes 46536 (45.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 110  bytes 20549 (20.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:e0:4c:3c:05:a4  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Shouldn't wlan1 also connect and get an Ip address?

floripaolo
Posts: 30
Joined: Thu Jun 14, 2018 10:16 am

Re: WIFI dongle problem/spotty ssh connection

Wed Jan 29, 2020 4:54 am

I also noticed with dmesg that there is an error message while loading the adapter:

Code: Select all

pi@raspberrypi:~ $ dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.19.66+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1253 Thu Aug 15 11:37:30 BST 2019
[    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi Zero W Rev 1.1
[    0.000000] Memory policy: Data cache writeback
[    0.000000] cma: Reserved 8 MiB at 0x1b400000
[    0.000000] On node 0 totalpages: 114688
[    0.000000]   Normal zone: 1008 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 114688 pages, LIFO batch:31
[    0.000000] random: get_random_bytes called from start_kernel+0x8c/0x49c with crng_init=0
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 113680
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:EF:7E:EA vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=301b09cd-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 434420K/458752K available (6971K kernel code, 635K rwdata, 2080K rodata, 468K init, 797K bss, 16140K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xdc800000 - 0xff800000   ( 560 MB)
                   lowmem  : 0xc0000000 - 0xdc000000   ( 448 MB)
                   modules : 0xbf000000 - 0xc0000000   (  16 MB)
                     .text : 0x(ptrval) - 0x(ptrval)   (6972 kB)
                     .init : 0x(ptrval) - 0x(ptrval)   ( 468 kB)
                     .data : 0x(ptrval) - 0x(ptrval)   ( 636 kB)
                      .bss : 0x(ptrval) - 0x(ptrval)   ( 798 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] ftrace: allocating 25191 entries in 74 pages
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000033] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
[    0.000095] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
[    0.000224] bcm2835: system timer (irq = 27)
[    0.000647] Console: colour dummy device 80x30
[    0.001288] console [tty1] enabled
[    0.001369] Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792)
[    0.060398] pid_max: default: 32768 minimum: 301
[    0.060982] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.061039] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.062482] CPU: Testing write buffer coherency: ok
[    0.063882] Setting up static identity map for 0x8200 - 0x8238
[    0.065367] devtmpfs: initialized
[    0.076186] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
[    0.076658] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.076738] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.078112] pinctrl core: initialized pinctrl subsystem
[    0.079727] NET: Registered protocol family 16
[    0.083010] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.090599] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[    0.090676] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.090849] Serial: AMBA PL011 UART driver
[    0.094111] bcm2835-mbox 2000b880.mailbox: mailbox enabled
[    0.138923] bcm2835-dma 20007000.dma: DMA legacy API manager at (ptrval), dmachans=0x1
[    0.141626] SCSI subsystem initialized
[    0.141952] usbcore: registered new interface driver usbfs
[    0.142097] usbcore: registered new interface driver hub
[    0.142358] usbcore: registered new device driver usb
[    0.160998] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-08-22 11:58, variant start
[    0.171032] raspberrypi-firmware soc:firmware: Firmware hash is 0e6daa5106dd4164474616408e0dc24f997ffcf3
[    0.183422] clocksource: Switched to clocksource timer
[    0.284404] VFS: Disk quotas dquot_6.6.0
[    0.284589] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.284954] FS-Cache: Loaded
[    0.285344] CacheFiles: Loaded
[    0.304619] NET: Registered protocol family 2
[    0.305992] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes)
[    0.306114] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.306228] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.306350] TCP: Hash tables configured (established 4096 bind 4096)
[    0.306548] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.306615] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.307056] NET: Registered protocol family 1
[    0.308209] RPC: Registered named UNIX socket transport module.
[    0.308270] RPC: Registered udp transport module.
[    0.308301] RPC: Registered tcp transport module.
[    0.308328] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.310499] hw perfevents: no irqs for PMU, sampling events not supported
[    0.310623] hw perfevents: enabled with armv6_1176 PMU driver, 3 counters available
[    0.314884] Initialise system trusted keyrings
[    0.315357] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[    0.330627] FS-Cache: Netfs 'nfs' registered for caching
[    0.332020] NFS: Registering the id_resolver key type
[    0.332117] Key type id_resolver registered
[    0.332153] Key type id_legacy registered
[    0.332205] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.338123] Key type asymmetric registered
[    0.338193] Asymmetric key parser 'x509' registered
[    0.338328] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.338854] io scheduler noop registered
[    0.338912] io scheduler deadline registered (default)
[    0.339536] io scheduler cfq registered
[    0.339588] io scheduler mq-deadline registered (default)
[    0.339624] io scheduler kyber registered
[    0.342356] bcm2708_fb soc:fb: FB found 1 display(s)
[    0.351585] Console: switching to colour frame buffer device 82x26
[    0.359111] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 656x416
[    0.368369] bcm2835-rng 20104000.rng: hwrng registered
[    0.371662] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
[    0.378319] vc-sm: Videocore shared memory driver
[    0.381889] gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x20200000
[    0.408542] brd: module loaded
[    0.425289] loop: module loaded
[    0.428992] Loading iSCSI transport class v2.0-870.
[    0.432891] usbcore: registered new interface driver smsc95xx
[    0.435926] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.466881] dwc_otg 20980000.usb: base=(ptrval)
[    0.670165] Core Release: 2.80a
[    0.672960] Setting default values for core params
[    0.675832] Finished setting default values for core params
[    0.879103] Using Buffer DMA mode
[    0.882001] Periodic Transfer Interrupt Enhancement - disabled
[    0.884957] Multiprocessor Interrupt Enhancement - disabled
[    0.887858] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.890731] Dedicated Tx FIFOs mode
[    0.894302] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = db514000 dma = 0x5b514000 len=9024
[    0.899914] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.912710] dwc_otg: Microframe scheduler enabled
[    0.912957] WARN::hcd_init_fiq:457: FIQ on core 0
[    0.915610] WARN::hcd_init_fiq:458: FIQ ASM at c04fd6a0 length 36
[    0.918227] WARN::hcd_init_fiq:497: MPHI regs_base at dc810000
[    0.920892] dwc_otg 20980000.usb: DWC OTG Controller
[    0.923586] dwc_otg 20980000.usb: new USB bus registered, assigned bus number 1
[    0.926280] dwc_otg 20980000.usb: irq 56, io mem 0x00000000
[    0.928872] Init: Port Power? op_state=1
[    0.931427] Init: Power Port (0)
[    0.934392] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.939537] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.942262] usb usb1: Product: DWC OTG Controller
[    0.944971] usb usb1: Manufacturer: Linux 4.19.66+ dwc_otg_hcd
[    0.947718] usb usb1: SerialNumber: 20980000.usb
[    0.951553] hub 1-0:1.0: USB hub found
[    0.954383] hub 1-0:1.0: 1 port detected
[    0.958084] dwc_otg: FIQ enabled
[    0.958097] dwc_otg: NAK holdoff enabled
[    0.958104] dwc_otg: FIQ split-transaction FSM enabled
[    0.958125] Module dwc_common_port init
[    0.958687] usbcore: registered new interface driver usb-storage
[    0.961842] mousedev: PS/2 mouse device common for all mice
[    0.966059] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    0.969589] bcm2835-cpufreq: min=700000 max=1000000
[    0.973128] sdhci: Secure Digital Host Controller Interface driver
[    0.976019] sdhci: Copyright(c) Pierre Ossman
[    0.979462] mmc-bcm2835 20300000.mmcnr: could not get clk, deferring probe
[    0.983168] sdhost-bcm2835 20202000.mmc: could not get clk, deferring probe
[    0.986501] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.990108] ledtrig-cpu: registered to indicate activity on CPUs
[    0.993192] hidraw: raw HID events driver (C) Jiri Kosina
[    0.996444] usbcore: registered new interface driver usbhid
[    0.999441] usbhid: USB HID core driver
[    1.003593] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0
[    1.008788] [vc_sm_connected_init]: start
[    1.019224] [vc_sm_connected_init]: end - returning 0
[    1.024074] Initializing XFRM netlink socket
[    1.026949] NET: Registered protocol family 17
[    1.029815] Key type dns_resolver registered
[    1.034576] registered taskstats version 1
[    1.037484] Loading compiled-in X.509 certificates
[    1.050489] uart-pl011 20201000.serial: cts_event_workaround enabled
[    1.053650] 20201000.serial: ttyAMA0 at MMIO 0x20201000 (irq = 81, base_baud = 0) is a PL011 rev2
[    1.062078] mmc-bcm2835 20300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    1.065179] mmc-bcm2835 20300000.mmcnr: DMA channel allocated
[    1.095803] sdhost: log_buf @ (ptrval) (5b513000)
[    1.137614] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.142222] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.146621] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.149284] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    1.153387] of_cfs_init
[    1.156163] of_cfs_init: OK
[    1.159597] Waiting for root device PARTUUID=301b09cd-02...
[    1.184706] Indeed it is in host mode hprt0 = 00021501
[    1.247470] random: fast init done
[    1.250069] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.317661] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.326260] mmc0: new high speed SDHC card at address aaaa
[    1.331896] mmcblk0: mmc0:aaaa SC16G 14.8 GiB
[    1.341685]  mmcblk0: p1 p2
[    1.383946] mmc1: new high speed SDIO card at address 0001
[    1.388866] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.394145] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.397067] Indeed it is in host mode hprt0 = 00001101
[    1.460024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.475393] devtmpfs: mounted
[    1.482974] Freeing unused kernel memory: 468K
[    1.486074] This architecture does not have kernel memory protection.
[    1.489094] Run /sbin/init as init process
[    1.634887] usb 1-1: New USB device found, idVendor=0bda, idProduct=f179, bcdDevice= 0.00
[    1.641452] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.644829] usb 1-1: Product: 802.11n
[    1.648070] usb 1-1: Manufacturer: Realtek
[    1.651268] usb 1-1: SerialNumber: 00E00930395B
[    2.296432] systemd[1]: System time before build time, advancing clock.
[    2.468496] NET: Registered protocol family 10
[    2.474454] Segment Routing with IPv6
[    2.542361] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    2.553630] systemd[1]: Detected architecture arm.
[    2.582044] systemd[1]: Set hostname to <raspberrypi>.
[    2.599950] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument
[    3.898702] random: crng init done
[    4.611989] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[    4.621669] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[    5.508591] systemd[1]: Created slice system-getty.slice.
[    5.517997] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    5.528005] systemd[1]: Listening on udev Control Socket.
[    5.537234] systemd[1]: Listening on udev Kernel Socket.
[    7.805146] systemd[1]: Mounted Kernel Configuration File System.
[    8.096857] systemd[1]: Started File System Check Daemon to report status.
[    8.325566] systemd[1]: Started Apply Kernel Variables.
[    8.855942] systemd[1]: Started File System Check on Root Device.
[    8.935725] systemd[1]: Starting Remount Root and Kernel File Systems...
[    9.154830] systemd[1]: Started Journal Service.
[    9.971691] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   10.694880] systemd-journald[89]: Received request to flush runtime journal from PID 1
[   12.980905] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[   13.004077] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[   13.004104] [vc_sm_connected_init]: start
[   13.030733] [vc_sm_connected_init]: installed successfully
[   13.052930] media: Linux media interface: v0.10
[   13.211929] videodev: Linux video capture interface: v2.00
[   13.353933] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[   13.375426] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[   13.404885] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[   13.450048] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[   13.508009] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[   13.508032] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[   13.525342] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[   13.525372] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[   13.574680] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[   13.574704] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[   14.242313] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[   14.414507] bcm2835_audio soc:audio: card created with 8 channels
[   14.957460] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   15.400771] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   16.036876] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[   16.067764] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   16.068328] usbcore: registered new interface driver brcmfmac
[   16.448810] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   16.449066] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   16.450304] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[   16.545018] rtl8188fu: loading out-of-tree module taints kernel.

[   18.393786] =======================================================
[   18.393792] ==== Launching Wi-Fi driver! (Powered by Rockchip) ====
[   18.393796] =======================================================
[   18.393801] Realtek 8188FU USB WiFi driver (Powered by Rockchip) init.
[   18.393806] RTL871X: module init start
[   18.393816] RTL871X: rtl8188fu v4.3.23.6_20964.20170110
[   23.848829] RTL871X: hal_com_config_channel_plan chplan:0x20
[   24.171014] usb 1-1: request firmware rtlwifi/rtl8188fufw.bin
[   24.214904] usb 1-1: request firmware rtlwifi/rtl8188fufw.bin loaded
[   26.692024] uart-pl011 20201000.serial: no DMA platform data
[   26.843714] RTL871X: rtw_ndev_init(wlan1) if1 mac_addr=00:e0:09:30:39:5b
[   26.891274] usbcore: registered new interface driver rtl8188fu
[   26.891295] RTL871X: module init ret=0
[   27.028864] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[   27.899123] 8021q: 802.1Q VLAN Support v1.8
[   28.686782] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   28.686802] brcmfmac: power management disabled
[   29.994942] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[   30.721679] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   31.592856] Bluetooth: Core ver 2.22
[   31.596774] NET: Registered protocol family 31
[   31.596790] Bluetooth: HCI device and connection manager initialized
[   31.597359] Bluetooth: HCI socket layer initialized
[   31.597672] Bluetooth: L2CAP socket layer initialized
[   31.598846] Bluetooth: SCO socket layer initialized
[   31.623339] Bluetooth: HCI UART driver ver 2.3
[   31.623355] Bluetooth: HCI UART protocol H4 registered
[   31.628187] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   31.630806] Bluetooth: HCI UART protocol Broadcom registered
[   32.033525] RTL871X: nolinked power save enter
[   32.389432] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   32.389446] Bluetooth: BNEP filters: protocol multicast
[   32.389472] Bluetooth: BNEP socket layer initialized
[   37.668308] RTL871X: nolinked power save leave
[   39.575005] RTL871X: nolinked power save enter
[   44.636539] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00
[   44.636572] RTL871X: nolinked power save leave
[   49.693524] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00
[   49.693546] RTL871X: nolinked power save leave
[   54.757255] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00
[   54.757276] RTL871X: nolinked power save leave
[   59.815810] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00
[   59.815833] RTL871X: nolinked power save leave
[   64.885327] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00
[   64.885347] RTL871X: nolinked power save leave
[   69.945203] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00
[   69.945236] RTL871X: nolinked power save leave
[   75.006797] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00
[   75.006819] RTL871X: nolinked power save leave
[   80.066702] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00
[   80.066722] RTL871X: nolinked power save leave
[   85.128290] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00
[   85.128309] RTL871X: nolinked power save leave
[   90.180748] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00
[   90.180783] RTL871X: nolinked power save leave
[   95.235567] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00
[   95.235589] RTL871X: nolinked power save leave
pi@raspberrypi:~ $ 

MrEngman
Posts: 3946
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: WIFI dongle problem/spotty ssh connection

Wed Jan 29, 2020 9:03 pm

I've no idea what could cause that error.

I've got two different wifi dongles using this driver and I've tried then on every different Raspbian kernel from 4.14.98 to the current latest 4.19.93 without any errors on a variety of different Pi 0, 0w, B, B+, 2B, 3B, 3A+ 3B+ and 4B 4GB.

Your previous post showing the ifconfig output looks a bit odd to me as it shows multiple IPV6 IP addresses when I would expect to only see one. Maybe this is causing an issue with the 8188fu driver. If you can use your wifi using only IPV4 may be try and blacklist IPV6 to stop it using IPV6. My network doesn't use IPV6 so ifconfig on my Pi only shows a single IPV6 with a local IP value.

I have occasionally blacklisted IPV6 by creating a file /etc/modprobe.d.ipv6.conf with a single line blacklist ipv6 but my Pi currently running the 8188fu wifi have IPV6 enabled.

Can't think of any way to get it fixed but one common issue is a bad PSU or power supply wiring which can cause problems with wifi not starting at boot.

The only other suggesting is starting again and create a new SD card and see if you can get round the issue with that, or perhaps to start with re-installing the driver again using my script in case the current one could have been corrupted somehow.



MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

floripaolo
Posts: 30
Joined: Thu Jun 14, 2018 10:16 am

Re: WIFI dongle problem/spotty ssh connection

Thu Jan 30, 2020 5:32 am

It really starts getting tedious....
This is what I get blacklisting ipv6:

Code: Select all

pi@raspberrypi:~ $ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.200  netmask 255.255.255.0  broadcast 192.168.1.255
        ether b8:27:eb:ba:2b:bf  txqueuelen 1000  (Ethernet)
        RX packets 172  bytes 22117 (21.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 85  bytes 13768 (13.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:e0:4c:aa:6e:2d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Maybe I have a faulty WIFI adapter?

floripaolo
Posts: 30
Joined: Thu Jun 14, 2018 10:16 am

Re: WIFI dongle problem/spotty ssh connection

Thu Jan 30, 2020 8:15 am

I tried to install on a RPi4:

Code: Select all

Linux raspberrypi 4.19.75-v7l+ #1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l GNU/Linux

Code: Select all

pi@raspberrypi:~ $ sudo wget http://downloads.fars-robotics.net/wifi-drivers/install-wifi -O /usr/bin/install-wifi
--2020-01-30 09:04:22--  http://downloads.fars-robotics.net/wifi-drivers/install-wifi
Resolving downloads.fars-robotics.net (downloads.fars-robotics.net)... 82.68.133.179
Connecting to downloads.fars-robotics.net (downloads.fars-robotics.net)|82.68.133.179|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 21478 (21K)
Saving to: ‘/usr/bin/install-wifi’

/usr/bin/install-wifi           100%[====================================================>]  20.97K  30.8KB/s    in 0.7s    

2020-01-30 09:04:23 (30.8 KB/s) - ‘/usr/bin/install-wifi’ saved [21478/21478]

pi@raspberrypi:~ $ sudo chmod +x /usr/bin/install-wifi
pi@raspberrypi:~ $ sudo install-wifi

 *** Raspberry Pi wifi driver installer by MrEngman.
 *** Performing self-update
 *** Relaunching after update

 *** Raspberry Pi wifi driver installer by MrEngman.

Your current kernel revision = 4.19.75-v7l+
Your current kernel build    = #1270

Checking for a wifi module to determine the driver to install.

Your wifi module is Bus 001 Device 004: ID 0bda:f179 Realtek Semiconductor Corp. 

And it uses the 8188fu driver.


Your Pi revision number is 
c03111
You have a Pi 4 v1.1
Checking for a 8188fu wifi driver module for your current kernel.
There is a driver module available for this kernel revision.
Downloading the 8188fu driver, 8188fu-4.19.75-v7l-1270.tar.gz.
Installing the 8188fu driver.

Installing driver config file rtl8188fu.conf.
mv rtl8188fu.conf /etc/modprobe.d/.
Installing driver module rtl8188fu.ko.
install -p -m 644 rtl8188fu.ko /lib/modules/4.19.75-v7l+/kernel/drivers/net/wireless
Loading and running the 8188fu driver, rtl8188fu.ko.
pi@raspberrypi:~ $ sudo reboot now
before:

Code: Select all

pi@raspberrypi:~ $ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether dc:a6:32:24:e6:34  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 9  bytes 524 (524.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9  bytes 524 (524.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.193  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::43c1:655a:db92:ca93  prefixlen 64  scopeid 0x20<link>
        inet6 2001:1716:460b:c940:c8ad:4667:5cf6:2cc0  prefixlen 128  scopeid 0x0<global>
        inet6 fdaa:bbcc:ddee:0:9400:7c8f:aa08:ad0a  prefixlen 64  scopeid 0x0<global>
        inet6 2001:1716:460b:c940:53b6:7d32:780c:859e  prefixlen 64  scopeid 0x0<global>
        ether dc:a6:32:24:e6:35  txqueuelen 1000  (Ethernet)
        RX packets 662  bytes 176921 (172.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 461  bytes 79594 (77.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
after:

Code: Select all

pi@raspberrypi:~ $ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether dc:a6:32:24:e6:34  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 9  bytes 524 (524.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9  bytes 524 (524.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:e0:09:30:39:5b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.193  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 2001:1716:460b:c940:53b6:7d32:780c:859e  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::43c1:655a:db92:ca93  prefixlen 64  scopeid 0x20<link>
        inet6 fdaa:bbcc:ddee:0:9400:7c8f:aa08:ad0a  prefixlen 64  scopeid 0x0<global>
        inet6 2001:1716:460b:c940:c8ad:4667:5cf6:2cc0  prefixlen 128  scopeid 0x0<global>
        ether dc:a6:32:24:e6:35  txqueuelen 1000  (Ethernet)
        RX packets 363  bytes 115813 (113.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 331  bytes 60685 (59.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
I'm pretty much assuming that the adapter is faulty.

MrEngman
Posts: 3946
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: WIFI dongle problem/spotty ssh connection

Thu Jan 30, 2020 9:03 pm

I don't understand why your wifi module doesn't work so I suppose it is possible it is faulty.

My wifi modules are
wifi-8188ftv-1.png
wifi-8188ftv-1.png (143.57 KiB) Viewed 456 times
and
wifi-8188ftv-2.png
wifi-8188ftv-2.png (206.44 KiB) Viewed 456 times
Can you post a link to where you got your wifi from.


MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

floripaolo
Posts: 30
Joined: Thu Jun 14, 2018 10:16 am

Re: WIFI dongle problem/spotty ssh connection

Fri Jan 31, 2020 4:24 am

I would prefer not to mention the place I got it from. They are a German company with a really good reputation and they offered already to refund. Btw I have the adapter on your first image.

I'll let you know how it develops...

floripaolo
Posts: 30
Joined: Thu Jun 14, 2018 10:16 am

Re: WIFI dongle problem/spotty ssh connection

Wed Feb 05, 2020 8:46 am

MrEngman wrote:
Thu Jan 30, 2020 9:03 pm
I don't understand why your wifi module doesn't work so I suppose it is possible it is faulty.

My wifi modules are wifi-8188ftv-1.pngand wifi-8188ftv-2.png

Can you post a link to where you got your wifi from.


MrEngman
I got a refund. What external USB driver would you recommend if you had to consider range as the main reason not to use the onboard wifi?
Thanks!

Return to “Beginners”