Yes, ping (which doesn’t count, as is either udp or icmp). Even for more weird, plain-old Telnet session doesn’t suffer at those times. Only SSH.
We really need to keep topics separate. Could you create a new one for this issue?
2 Likes
Could be some issue in encryption. If there 1 packet gets lost and not retransmitted by tcp (or broken again) it could break ssh.
@totkeks ack better 2 topics one for mt7996-led one for ssh hang there
Sorry about topic loaning. Didn’t have credentials to start my own.
You’re right. I mixed up the memory type when I wrote that, but not the commands.
run ubi_init installs to NAND,
run emmc_init installs to eMMC.
I corrected my message.
Just want to comment that finally I bought a cable Usb Ttl Ftdi Ft232rl locally and once have it installing the new images was a piece of cake.
As I said previously. How thoughtful of them to not mention that a serial cable was a must-have accessory and bought everithing in the same package.
Now I have the latest snapshot running from eMMC and some new problems arises (ETH ports stoped working, filesystem do not use all the eMMC space, ssh connection randomly gets disconnected, etc) But I will investigate and ask in another specific threads if needed. Thanks by your support
You seem to have completely forgotten one thing: It is and remains a developer and tinkering board. This means that various things can be assumed to be known and available. I hate people who don’t take the trouble to inform themselves in advance and think that they are getting a completely finished and ready-to-use product. People like that should just stick with the Fritzbox. It’s for end users, ready for immediate use and requires little or no knowledge.
2 Likes
Git pull this morning on openwrt’s repository and Mediatek patches, and voila, SSH woes are gone. 
Could you link to the commit? I tried to search through the most recent commits, but it’s really hard or impossible on a phone.
Is it possible that my WIFI card was burned with the latest sysupgrade?
I applied the latest sysupgrade and after the reboot it worked correctly for a few minutes and then hung. I connected via console and found that the boot (from eMMC) was interrupted. Assuming that there had been a problem with the upgrade I inserted the SD card with which I had installed the system and found that it hung at the same point.
I tried other images and found that they all interrupt the boot at the same point with the only exception of ubuntu but I could not find in the instructions the password with which the root user is configured.
This is the point at which the boot is interrupted. Can you think of something?
[ 13.331854] sfp sfp2: Host maximum power 3.0W [ 13.350917] mt7996e_hif 0001:01:00.0: assign IRQ: got 118 [ 13.356350] mt7996e_hif 0001:01:00.0: enabling device (0000 → 0002) [ 13.362727] mt7996e_hif 0001:01:00.0: enabling bus mastering [ 13.368534] mt7996e 0000:01:00.0: assign IRQ: got 115 [ 13.373595] mt7996e 0000:01:00.0: enabling device (0000 → 0002) [ 13.379609] mt7996e 0000:01:00.0: enabling bus mastering [ 13.462436] mtk-pcie-gen3 11300000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11300c00 data 1 [ 13.470950] mtk-pcie-gen3 11310000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11310c00 data 1 [ 13.525317] mt7996e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240809122254a [ 13.525317] [ 13.736609] mt7996e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20240809122249 [ 13.785651] mt7996e 0000:01:00.0: DSP Firmware Version: ____000000, Build Time: 20240809121650 [ 13.839000] mt7996e 0000:01:00.0: WA Firmware Version: ____000000, Build Time: 20240809122214 [ 14.241162] PPP generic driver version 2.4.2 [ 14.246017] NET: Registered PF_PPPOX protocol family [ 14.252492] kmodloader: done loading kernel modules from /etc/modules.d/* [ 19.181729] mtk_soc_eth 15100000.ethernet eth0: Link is Down [ 19.205059] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/internal link mode [ 19.213309] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 10Gbps/Full - flow control rx/tx [ 19.215290] mt7530-mmio 15020000.switch lan1: configuring for phy/internal link mode [ 19.230383] br-lan: port 1(lan1) entered blocking state [ 19.235653] br-lan: port 1(lan1) entered disabled state [ 19.240897] mt7530-mmio 15020000.switch lan1: entered allmulticast mode [ 19.247534] mtk_soc_eth 15100000.ethernet eth0: entered allmulticast mode [ 19.254513] mt7530-mmio 15020000.switch lan1: entered promiscuous mode [ 19.265666] mt7530-mmio 15020000.switch lan2: configuring for phy/internal link mode [ 19.274458] br-lan: port 2(lan2) entered blocking state [ 19.279699] br-lan: port 2(lan2) entered disabled state [ 19.284981] mt7530-mmio 15020000.switch lan2: entered allmulticast mode [ 19.291790] mt7530-mmio 15020000.switch lan2: entered promiscuous mode [ 19.301244] mt7530-mmio 15020000.switch lan3: configuring for phy/internal link mode [ 19.310027] br-lan: port 3(lan3) entered blocking state [ 19.315309] br-lan: port 3(lan3) entered disabled state [ 19.320563] mt7530-mmio 15020000.switch lan3: entered allmulticast mode [ 19.327433] mt7530-mmio 15020000.switch lan3: entered promiscuous mode [ 19.336104] mtk_soc_eth 15100000.ethernet eth1: configuring for inband/10gbase-r link mode [ 19.368442] br-lan: port 4(eth1) entered blocking state [ 19.373733] br-lan: port 4(eth1) entered disabled state [ 19.378993] mtk_soc_eth 15100000.ethernet eth1: entered allmulticast mode [ 19.386184] mtk_soc_eth 15100000.ethernet eth1: entered promiscuous mode [ 19.395684] mt7530-mmio 15020000.switch wan: configuring for phy/internal link mode [ 19.404187] br-wan: port 1(wan) entered blocking state [ 19.409328] br-wan: port 1(wan) entered disabled state [ 19.414507] mt7530-mmio 15020000.switch wan: entered allmulticast mode [ 19.421219] mt7530-mmio 15020000.switch wan: entered promiscuous mode [ 19.429861] mtk_soc_eth 15100000.ethernet eth2: configuring for inband/10gbase-r link mode [ 19.462145] br-wan: port 2(eth2) entered blocking state [ 19.467452] br-wan: port 2(eth2) entered disabled state [ 19.472715] mtk_soc_eth 15100000.ethernet eth2: entered allmulticast mode [ 19.479647] mtk_soc_eth 15100000.ethernet eth2: entered promiscuous mode
You can format log output using the “preformatted text” feature of editor here. That makes it much easier to read.
Also, did you press enter after connecting the console? This looks like the normal boot output on console. A login prompt only appears after you press enter.
This is the point where I feel extremely stupid 
Yes that was the problem about the boot stuck
Even that wifi still not starting and when I plug the eth cable from a laptop to get access to it ETH connection never starts
This is from serial console
root@CasaBarba:~# ifup
Interface not found
root@CasaBarba:~# iw
iw iwinfo
root@CasaBarba:~# iw
iw iwinfo
root@CasaBarba:~# iwinfo
phy0.0-ap0 ESSID: "CasaBarBa_2G"
Access Point: E6:38:02:15:FB:30
Mode: Master Channel: 6 (2.437 GHz) HT Mode: NOHT
Center Channel 1: 6 2: unknown
Tx-Power: 20 dBm Link Quality: unknown/70
Signal: unknown Noise: -81 dBm
Bit Rate: unknown
Encryption: mixed WPA2/WPA3 PSK/SAE (CCMP)
Type: nl80211 HW Mode(s): 802.11ac/ax/b/be/g/n
Hardware: 14C3:7990 14C3:6639 [MediaTek MT7996E]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy0
phy0.1-ap0 ESSID: "CasaBarBa_5G"
Access Point: E6:38:02:15:FB:40
Mode: Master Channel: unknown (unknown) HT Mode: NOHT
Center Channel 1: unknown 2: unknown
Tx-Power: 0 dBm Link Quality: unknown/70
Signal: unknown Noise: -81 dBm
Bit Rate: unknown
Encryption: mixed WPA2/WPA3 PSK/SAE (CCMP)
Type: nl80211 HW Mode(s): 802.11ac/ax/b/be/g/n
Hardware: 14C3:7990 14C3:6639 [MediaTek MT7996E]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy0
root@CasaBarba:~# [ 454.700803] mt7530-mmio 15020000.switch lan2: Link is Up - 1Gbps/Full - flow control rx/tx
[ 454.701393] br-lan: port 2(lan2) entered blocking state
[ 454.714292] br-lan: port 2(lan2) entered forwarding state
And this is from the laptop connected by eth port
└─$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
--- 192.168.1.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3057ms
┌──(nadie㉿Ferkali)-[~]
└─$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 74:d4:dd:4e:ff:e7 txqueuelen 1000 (Ethernet)
RX packets 74 bytes 25308 (24.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 105 bytes 39826 (38.8 KiB)
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 90 bytes 7060 (6.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 90 bytes 7060 (6.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.35 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 2802:8010:4931:c400:1c3a:cf3c:158a:a6f7 prefixlen 64 scopeid 0x0<global>
inet6 fe80::46d7:9dc8:c9fd:81fd prefixlen 64 scopeid 0x20<link>
ether 1c:ce:51:25:1a:b9 txqueuelen 1000 (Ethernet)
RX packets 98751 bytes 101009766 (96.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 53036 bytes 9418837 (8.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I answered myself
I reinstalled based on RC5 and now everything works again.
Thanks
Hi,
How did you manage to run the command and get it to work on an BP4?
I booted from openwrt’s openwrt-24.10.0-mediatek-filogic-bananapi_bpi-r4-sdcard.img.gz, and got this:
root@OpenWrt:~# fw_setenv bootcmd "env default bootcmd ; saveenv ; run ubi_init ; bootmenu 0"
Cannot parse config file '/etc/fw_env.config': No such file or directory
Failed to find NVMEM device
Error: environment not initialized
Sorry for the old post resurrection. You looked knowledgable 
Which mediatek patches did you take? I have got the same problem with ssh. The rest seems to work but just ssh via wifi is very slow.
Sorry, cannot recall any more.
The last time I built it, I used GitHub - Rahzadan/openwrt_bpi-r4_mtk_builder: OpenWRT Builder for BPI-R4 with Mediatek Feeds for the BE-14000 board and there doesn’t seem to be SSH problems.
1 Like
Huge thanks for posting that link, sysupgraded from vanilla 24.10, and it works perfectly. EDIT: There’s some idle CPU usage increase however, I think it’s due to the unnecessary CPU usage and thermals tracking which already exists in graphs.
Tempted to try that build as well, because the ssh freezes are killing me. Maddening.
Possible to upgrade from 24.10.2? Possible to downgrade back to 24.10.2??
Did you find a fix for this?
Hi,
My banana pi got put back in the box and relegated to the basement. I should try to flog it in a car boot sale.
Sorry, but I cannot be much more help.