Maybe ask the people at Promwad if they can name a product.
2 Likes
I can get most of the info out of those headers, but for the tables only the access registers are listed. I can't seem to find the RTL8380/RTL8390 table details inside this source dump, so I assume tigershark/bumblebee are also missing.
This has been successful for me in the past. Just add 'bond0' to any bridge and it will be treated like any other port including VLAN tagging etc.
config interface 'bond0'
option proto 'bonding'
list slaves 'eth0'
list slaves 'eth1'
option bonding_policy '802.3ad'
option all_slaves_active '0'
option link_monitoring 'off'
option min_links '0'
option ad_actor_sys_prio '65535'
option ad_select 'stable'
option lacp_rate 'slow'
option xmit_hash_policy 'layer2'
2 Likes
No link monitoring and slow LACP, doesn't that cause problems if one physical port goes offline?
1 Like
Then it is without the tables.
Not really. I had to add those lines so it would play nice with an Ubiquiti switch. They are not necessary.
1 Like
How to upgrade from Openwrt 23.05 to Openwrt 24/25 on Zyxel GS1900-8 v1 (a1) without using serial connection?
fw_printenv
root@OpenWrt:~# fw_printenv
baudrate=115200
boardmodel=ZyXEL_GS1900_8
bootargs=console=ttyS0,115200 mem=64M quiet
bootcmd=cst fcTest; boota
bootdelay=0
ethact=rtl8380#0
ethaddr=5C:E2:8C:F6:DD:43
ipaddr=192.168.1.1
netmask=255.255.255.0
serverip=192.168.1.111
stderr=serial
stdin=serial
stdout=serialSummary
cat /proc/mtd
root@OpenWrt:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 00010000 00010000 "u-boot-env2"
mtd3: 00100000 00010000 "jffs"
mtd4: 00100000 00010000 "jffs2"
mtd5: 006d0000 00010000 "firmware"
mtd6: 00320000 00010000 "kernel"
mtd7: 003b0000 00010000 "rootfs"
mtd8: 00100000 00010000 "rootfs_data"
mtd9: 006d0000 00010000 "runtime2"
Just do it (tm).
It'll need to resize the partition, so backup settings and flash. If it doesn't come up then it's time to buy a USB serial adapter. I had two of these, they're quite easy to add serial too. I put an RJ45 socket inside mine connected to the pin header so I could open the chassis a pop in a cisco console adapter.
2 Likes
Could you advice on steps to lower possibility of serial connection requirement ?
Using serial connection scenario looks very straight forward to me with loading openwrt kernel first and writing firmware then, but I prefer to try without using serial connection.
You can flash an initramfs version first. This is guaranteed to fit into the firmware partition and at the same time has the new flash layout. Once this is flashed, restart and flash the regular sysupgrade image. You lose all your settings.
3 Likes
Sounds ideal. Which cli command would I use to flash initramfs to firmware partition?
The regular sysupgrade command, i.e. sysupgrade initramfs.bin. I don't remember if you have to use -F to force the upgrade, but I think it's required.
1 Like
Thanking you @andyboeh , it worked exactly the way you projected.
Gemini thought the same way as you did. Claude & GPT suggested not to proceed, because of potential brick 
1 Like
Remember that it's very unlikely to actually brick these. At worst it's removing a few screws and buying $20 of hardware to access the serial console. 
2 Likes
@howels thanks for your input too.
I know, and I have used serial comms for last 30 years itās just lack of time, usualā¦ 