VIM3 problem Wifi/Ethernet

Hello to everyone, I have a vim3 pro 4+32gb with debian 10 buster installed(from krescue), It is connected to wlan0 and eth0 (I can view both in the router’s devices information), so the problem is that vim3 can’t establish a connection, it crash and reconnect to wifi, my ssh session crash for “client_loop: send disconnect: Broken pipe” every about 2 minutes.

Obvliusly I have connected the x2 Wifi Antenna

I have 5.9.0-rc2 kernel

Hi, include in your post the developer of Krescue, Hyphop, insert an “@” in front of his nickname.

NEWS*
I have tried to install(always from Krescue) Ubuntu 20.04.1 LTS (Focal Fossa) with 5.7.0 aarch64 kernel but the problem is the same :frowning:

uname -a

Linux Khadas 5.7.0 #0.9.1 SMP Tue Jun 2 17:07:41 CST 2020 aarch64 aarch64 aarch64 GNU/Linux

@hyphop can you help me?

Note: Now I can establish connect with ssh but when I connect my telegram bots the vim3 can’t establish the connection because:

2021-01-17 15:05:19,403 | [INFO] → The server closed the connection
2021-01-17 15:05:19,404 | [INFO] → Connection closed while sending data
2021-01-17 15:05:19,425 | [INFO] → Closing current connection to begin reconnect…
2021-01-17 15:05:19,523 | [INFO] → Connecting to 149.154.167.91:443/TcpFull…
2021-01-17 15:05:22,617 | [INFO] → Connection to 149.154.167.91:443/TcpFull complete!

Vim3 do this in a loop for about each bot
The problem is not my code or telegram because this in a raspberry pi 4 didn’t happen(tried until 2 days ago)

ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.187 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 xxxx::xxxx:xxxx:xxxx:xxxx prefixlen 64 scopeid 0x20
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 32413413 bytes 30934974483 (30.9 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 28783052 bytes 4449294520 (4.4 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 6

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

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.184 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 xxxx::xxxx:xxxx:xxxx:xxxx prefixlen 64 scopeid 0x20
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 17968 bytes 3516247 (3.5 MB)
RX errors 0 dropped 8 overruns 0 frame 0
TX packets 198 bytes 16961 (16.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

X = censored

our debian images not to much tested
pls try ubuntu focal or bionic

and provie more info soft kernel logs etc … - because difficult understand what wrong

2 Likes

Thanks for your answer.

Info about my vim3 pro:

inxi -F

System: Host: Khadas Kernel: 5.7.0 aarch64 bits: 64 Console: tty 0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa)

Machine: Type: ARM Device System: Khadas VIM3 details: N/A

CPU: Topology: 6-Core (2-Die) model: ARMv8 v8l variant-1: cortex-a73 variant-2: cortex-a53 bits: 64 type: MCP MCM
Speed: 2208 MHz min/max: 100/1800:2208 MHz Core speeds (MHz): 1: 1800 2: 1800 3: 2208 4: 2208 5: 2208 6: 2208

Graphics: Device-1: meson-g12a-mali driver: panfrost v: kernel
Device-2: meson-g12a-dw-hdmi driver: meson_dw_hdmi v: N/A
Display: server: X.org 1.20.9 driver: meson_dw_hdmi tty: 152x62
Message: Advanced graphics data unavailable in console for root.

Audio: Device-1: meson-g12a-dw-hdmi driver: meson_dw_hdmi
Device-2: axg-sound-card driver: axg_sound_card
Sound Server: ALSA v: k5.7.0

Network: Device-1: meson-axg-dwmac driver: meson8b_dwmac
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: xx:xx:xx:xx:xx:xx
Device-2: pwm-clock driver: pwm_clock
IF-ID-1: wlan0 state: up mac: xx:xx:xx:xx:xx:xx

Drives: Local Storage: total: 29.12 GiB used: 3.66 GiB (12.6%)
ID-1: /dev/mmcblk2 model: BJTD4R size: 29.12 GiB

Partition: ID-1: / size: 28.07 GiB used: 3.60 GiB (12.8%) fs: ext4 dev: /dev/mmcblk2p2
ID-2: /boot size: 239.7 MiB used: 60.1 MiB (25.1%) fs: vfat dev: /dev/mmcblk2p1

Sensors: Message: No sensors data was found. Is sensors configured?

Info: Processes: 244 Uptime: 12h 54m Memory: 3.67 GiB used: 1.70 GiB (46.3%) Init: systemd runlevel: 5 Shell: bash

Last Kern logs:

cat kern.log

Jan 18 01:01:48 localhost kernel: [ 4.535326] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet] (irq=31)
Jan 18 01:01:48 localhost kernel: [ 4.549164] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found
Jan 18 01:01:48 localhost kernel: [ 4.549173] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW
Jan 18 01:01:48 localhost kernel: [ 4.549179] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode
Jan 18 01:01:49 localhost kernel: [ 6.384868] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4359-sdio for chip BCM4359/9
Jan 18 01:01:49 localhost kernel: [ 6.387819] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
Jan 18 01:01:49 localhost kernel: [ 6.408909] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4359/9 wl0: Sep 20 2019 20:22:36 version 9.87.51.11.34 (edb7293@shgit) (r711217) FWID 01-c7feb1ee
Jan 18 01:01:50 localhost kernel: [ 6.848850] ieee80211 phy0: brcmf_dongle_roam: WLC_SET_ROAM_TRIGGER error (-52)
Jan 18 01:01:51 localhost kernel: [ 8.384877] meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Jan 18 01:01:51 localhost kernel: [ 8.384903] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jan 18 01:01:54 localhost kernel: [ 10.785611] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 18 01:01:58 localhost kernel: [ 15.616362] rfkill: input handler disabled
Jan 18 01:02:04 localhost kernel: [ 21.045688] Bluetooth: RFCOMM TTY layer initialized
Jan 18 01:02:04 localhost kernel: [ 21.045730] Bluetooth: RFCOMM socket layer initialized
Jan 18 01:02:04 localhost kernel: [ 21.045752] Bluetooth: RFCOMM ver 1.11
Jan 18 01:12:31 localhost kernel: [ 648.954400] rc rc0: two consecutive events of type space

cat dmesg
[ 4.535326] kernel: meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet] (irq=31)
[ 4.538498] kernel: Bluetooth: hci1: BCM: chip id 121
[ 4.539179] kernel: Bluetooth: hci1: BCM: features 0x0e
[ 4.540700] kernel: Bluetooth: hci1: BCM4359C0
[ 4.540712] kernel: Bluetooth: hci1: BCM4359C0 (003.001.006) build 0000
[ 4.549164] kernel: meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found
[ 4.549173] kernel: meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW
[ 4.549179] kernel: meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode
[ 4.581166] kernel: Adding 262140k swap on /dev/zram1. Priority:5 extents:1 across:262140k SSFS
[ 4.586568] kernel: zram2: detected capacity change from 0 to 268435456
[ 4.620825] kernel: Adding 262140k swap on /dev/zram2. Priority:5 extents:1 across:262140k SSFS
[ 4.621993] kernel: zram3: detected capacity change from 0 to 268435456
[ 4.657746] kernel: Adding 262140k swap on /dev/zram3. Priority:5 extents:1 across:262140k SSFS
[ 4.659150] kernel: zram4: detected capacity change from 0 to 268435456
[ 4.716823] kernel: Adding 262140k swap on /dev/zram4. Priority:5 extents:1 across:262140k SSFS
[ 5.421579] kernel: Bluetooth: hci1: BCM4359C0 (003.001.006) build 0268
[ 6.384868] kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4359-sdio for chip BCM4359/9
[ 6.387819] kernel: brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 6.408909] kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4359/9 wl0: Sep 20 2019 20:22:36 version 9.87.51.11.34 (edb7293@shgit) (r711217) FWID 01-c7feb1ee
[ 6.848850] kernel: ieee80211 phy0: brcmf_dongle_roam: WLC_SET_ROAM_TRIGGER error (-52)
[ 8.384877] kernel: meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 8.384903] kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

I noted that in netstat -t(almost 270 TCP connections) in various moments, some of that connection change ESTABLISHED to FIN_WAIT2 and then change FIN_WAIT2 to ESTABLISHED in random way.

In addition, in iwconfig eth0 seems to be “no wireless extensions.”

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:“TIM-xxxxxxxxx”
Mode:Managed Frequency:5.18 GHz Access Point: xx:xx:xx:xx:xx:xx
Bit Rate=24 Mb/s Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=70/70 Signal level=-12 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:92 Invalid misc:0 Missed beacon:0

I check dmesg -c
Result:

[ 3.834538] brcmfmac: F1 signature read @0x18000000=0x17294359
[ 3.837806] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4359-sdio for chip BCM4359/9
[ 3.846563] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac4359-sdio.khadas,vim3.txt failed with error -2
[ 4.094953] meson_vdec: module is from the staging directory, the quality is unknown, you have been warned.
[ 4.104438] debugfs: Directory ‘ff800280.cec’ with parent ‘regmap’ already present!
[ 4.535326] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet] (irq=31)
[ 4.549164] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found
[ 4.549173] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW
[ 4.549179] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode
[ 6.384868] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4359-sdio for chip BCM4359/9
[ 6.387819] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 6.408909] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4359/9 wl0: Sep 20 2019 20:22:36 version 9.87.51.11.34 (edb7293@shgit) (r711217) FWID 01-c7feb1ee
[ 6.848850] ieee80211 phy0: brcmf_dongle_roam: WLC_SET_ROAM_TRIGGER error (-52)
[ 8.384877] meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 8.384903] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 10.785611] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 15.616362] rfkill: input handler disabled
[ 21.045688] Bluetooth: RFCOMM TTY layer initialized
[ 21.045730] Bluetooth: RFCOMM socket layer initialized
[ 21.045752] Bluetooth: RFCOMM ver 1.11
[ 648.954400] rc rc0: two consecutive events of type space
[63812.243790] fuse: init (API version 7.31)

still cant see something special from your logs :wink:

  1. can u check just ethernet with disabled wifi
  2. same but disabled ethernet with enabled wifi
  3. try to clarify crash reasons for me - and i will make some suggestions

It looks be fix by typing:

sudo cp /lib/firmware/brcm/brcmfmac4359-sdio.txt /lib/firmware/brcm/brcmfmac4359-sdio.khadas,vim3.txt

And then reboot

its was solution for u ? now system work properly ?

for example this it tested fw list for wifi by me

root@Krescue:/# ls -l1 /lib/firmware/brcm/
lrwxrwxrwx    1 root     root            17 Jan 20 05:02 brcmfmac43430-sdio.bin -> fw_bcm43438a1.bin
-rw-r--r--    1 root     root          1003 Sep  6 16:19 brcmfmac43430-sdio.txt
lrwxrwxrwx    1 root     root            20 Jan 20 05:02 brcmfmac43455-sdio.bin -> fw_bcm43455c0_ag.bin
-rw-r--r--    1 root     root          1644 Sep  6 16:19 brcmfmac43455-sdio.txt
-rw-r--r--    1 root     root        526383 Sep  6 16:19 brcmfmac4356-sdio.bin
-rw-r--r--    1 root     root          2844 Sep  6 16:19 brcmfmac4356-sdio.txt
lrwxrwxrwx    1 root     root            19 Jan 20 05:02 brcmfmac4359-sdio.bin -> fw_bcm4359c0_ag.bin
lrwxrwxrwx    1 root     root            21 Jan 20 05:02 brcmfmac4359-sdio.khadas,vim2.txt -> brcmfmac4359-sdio.txt
lrwxrwxrwx    1 root     root            21 Jan 20 05:02 brcmfmac4359-sdio.khadas,vim3.txt -> brcmfmac4359-sdio.txt
lrwxrwxrwx    1 root     root            18 Jan 20 05:02 brcmfmac4359-sdio.txt -> nvram_ap6359sa.txt
-rw-r--r--    1 root     root           184 Sep  6 16:19 config.txt
-rw-r--r--    1 root     root        374608 Sep  6 16:19 fw_bcm43438a1.bin
-rw-r--r--    1 root     root        483181 Sep  6 16:19 fw_bcm43455c0_ag.bin
-rw-r--r--    1 root     root        595758 Sep  6 16:19 fw_bcm4359c0_ag.bin
-rw-r--r--    1 root     root           956 Sep  6 16:19 nvram_ap6212.txt
-rw-r--r--    1 root     root          1003 Sep  6 16:19 nvram_ap6212a.txt
-rw-r--r--    1 root     root          1644 Sep  6 16:19 nvram_ap6255.txt
-rw-r--r--    1 root     root          2844 Sep  6 16:19 nvram_ap6356.txt
-rw-r--r--    1 root     root          5861 Sep  6 16:19 nvram_ap6359sa.txt
-rw-r--r--    1 root     root          5861 Sep  6 16:19 nvram_ap6398s.txt

It looks yes but I’m not sure.

ls -l1 /lib/firmware/brcm/

lrwxrwxrwx 1 root root 33 gen 19 21:36 BCM43430A1.hcd -> /lib/firmware/brcm/BCM43438A1.hcd
-rw-r–r-- 1 root root 38644 gen 19 03:17 BCM43438A0.hcd
-rw-r–r-- 1 root root 33376 gen 19 03:17 BCM43438A1.hcd
-rw-r–r-- 1 root root 47080 gen 19 03:17 BCM4345C0.hcd
lrwxrwxrwx 1 root root 32 gen 19 21:36 BCM4354A2.hcd -> /lib/firmware/brcm/BCM4356A2.hcd
-rw-r–r-- 1 root root 60602 gen 19 03:17 BCM4356A2.hcd
-rw-r–r-- 1 root root 67687 gen 19 03:17 BCM4359C0.hcd
-rw-r–r-- 1 root root 374608 gen 19 03:17 brcmfmac43430-sdio.bin
-rw-r–r-- 1 root root 1003 gen 19 03:17 brcmfmac43430-sdio.txt
-rw-r–r-- 1 root root 483181 gen 19 03:17 brcmfmac43455-sdio.bin
-rw-r–r-- 1 root root 1644 gen 19 03:17 brcmfmac43455-sdio.txt
-rwxr-xr-x 1 root root 555412 gen 19 03:17 brcmfmac4356-sdio.bin
-rw-r–r-- 1 root root 2844 gen 19 03:17 brcmfmac4356-sdio.txt
-rw-r–r-- 1 root root 637347 gen 19 03:17 brcmfmac4359-sdio.bin
-rw-r–r-- 1 root root 6096 gen 18 19:22 brcmfmac4359-sdio.khadas,vim3.txt
-rw-r–r-- 1 root root 6096 gen 19 03:17 brcmfmac4359-sdio.txt
-rw-r–r-- 1 root root 184 gen 19 03:17 config.txt
-rw-r–r-- 1 root root 309352 gen 19 03:17 fw_bcm43438a0_apsta.bin
-rw-r–r-- 1 root root 326074 gen 19 03:17 fw_bcm43438a0.bin
-rw-r–r-- 1 root root 326074 gen 19 03:17 fw_bcm43438a0_p2p.bin
-rw-r–r-- 1 root root 374608 gen 19 03:17 fw_bcm43438a1_apsta.bin
-rw-r–r-- 1 root root 374608 gen 19 03:17 fw_bcm43438a1.bin
-rw-r–r-- 1 root root 374608 gen 19 03:17 fw_bcm43438a1_p2p.bin
-rw-r–r-- 1 root root 483181 gen 19 03:17 fw_bcm43455c0_ag_apsta.bin
-rw-r–r-- 1 root root 483181 gen 19 03:17 fw_bcm43455c0_ag.bin
-rw-r–r-- 1 root root 483181 gen 19 03:17 fw_bcm43455c0_ag_p2p.bin
-rwxr-xr-x 1 root root 555412 gen 19 03:17 fw_bcm4356a2_ag_apsta.bin
-rwxr-xr-x 1 root root 555412 gen 19 03:17 fw_bcm4356a2_ag.bin
-rwxr-xr-x 1 root root 555412 gen 19 03:17 fw_bcm4356a2_ag_p2p.bin
-rwxr-xr-x 1 root root 637347 gen 19 03:17 fw_bcm4359c0_ag_apsta.bin
-rwxr-xr-x 1 root root 637347 gen 19 03:17 fw_bcm4359c0_ag.bin
-rw-r–r-- 1 root root 637347 gen 19 03:17 fw_bcm4359c0_ag_p2p.bin
-rw-r–r-- 1 root root 1003 gen 19 03:17 nvram_ap6212a.txt
-rw-r–r-- 1 root root 956 gen 19 03:17 nvram_ap6212.txt
-rw-r–r-- 1 root root 1644 gen 19 03:17 nvram_ap6255.txt
-rw-r–r-- 1 root root 2844 gen 19 03:17 nvram_ap6356.txt
-rw-r–r-- 1 root root 6096 gen 19 03:17 nvram_ap6359sa.txt

News: sorry for the fake solution, anyway the problem after a reboot it’s back…
In particular after that I upgraded the system and fenix

sudo apt update
sudo apt full-upgrade
sudo do-fenix-full-upgrade
sync
reboot
1 Like