Support for Zyxel GS1920 series (GS1920-24HP)

For Developers
41

You run a much better chance of getting this merged if you follow Submission Guidelines. For instance you are missing the Signed-off-by: line among other things.

42

Thanks for stating the facts that the commit is crap. Nevertheless cleanup is totally useless if no one helps here:

2 Likes
43

How can I help?
HPE switch for testing available

1 Like
44

Compile, install, test and report your findings. If everything works for your usecase report that as well.

Thx.

1 Like
45

@plappermaul thank you for the work.

Sucessfully compiled and tftp booted the initramfs-kernel.bin from your commit 0cac0f11d2f4ede5d6832bdedfc5235fa35639bf

Switching works, means I can pass traffic through the switch.

On the otherhand the network interface of the switch is not reachable by IPv4 or IPv6. Cannot ping to or from the switch.

Bootlog differences I have found comparing 5.15 with 6.6:

[    0.268868] RCU Tasks Trace: Setting shift to 0 and lim to 1 rcu_task_cb_adjust=1.
...
[    2.468692] Probing RTL838X eth device pdev: 818b8000, dev: 818b8010
...
[   11.163195] i2c-gpio i2c-gpio-0: Slow GPIO pins might wreak havoc into I2C/SMBus bus timing
[   11.191720] i2c-gpio i2c-gpio-0: using lines 549 (SDA) and 550 (SCL)
[   11.213709] i2c-gpio i2c-gpio-1: Slow GPIO pins might wreak havoc into I2C/SMBus bus timing
[   11.242106] i2c-gpio i2c-gpio-1: using lines 559 (SDA) and 560 (SCL)
[   11.264060] i2c-gpio i2c-gpio-2: Slow GPIO pins might wreak havoc into I2C/SMBus bus timing
[   11.292484] i2c-gpio i2c-gpio-2: using lines 563 (SDA) and 564 (SCL)
[   11.314440] i2c-gpio i2c-gpio-3: Slow GPIO pins might wreak havoc into I2C/SMBus bus timing
[   11.342853] i2c-gpio i2c-gpio-3: using lines 567 (SDA) and 568 (SCL)
...
[   23.353958] rtl8214fc_power_set: Powering off COPPER (port 24) <--- 5.15 powers off Fiber and powers on Copper at this stage.
[   23.404396] rtl8214fc_power_set: Powering on FIBRE (port 24)
[   23.444703] rtl83xx-switch switch@1b000000 lan25 (uninitialized): PHY [mdio-bus:18] driver [Realtek RTL8214FC] (irq=POLL)
[   23.509838] rtl8214fc_power_set: Powering off COPPER (port 25)
[   23.560254] rtl8214fc_power_set: Powering on FIBRE (port 25)
[   23.600654] rtl83xx-switch switch@1b000000 lan26 (uninitialized): PHY [mdio-bus:19] driver [Realtek RTL8214FC] (irq=POLL)
[   23.665744] rtl8214fc_power_set: Powering off COPPER (port 26)
[   23.717030] rtl8214fc_power_set: Powering on FIBRE (port 26)
[   23.758272] rtl83xx-switch switch@1b000000 lan27 (uninitialized): PHY [mdio-bus:1a] driver [Realtek RTL8214FC] (irq=POLL)
[   23.823200] rtl8214fc_power_set: Powering off COPPER (port 27)
[   23.874051] rtl8214fc_power_set: Powering on FIBRE (port 27)
[   23.914488] rtl83xx-switch switch@1b000000 lan28 (uninitialized): PHY [mdio-bus:1b] driver [Realtek RTL8214FC] (irq=POLL)
[   23.954449] rtl838x-eth 1b00a300.ethernet eth0: entered promiscuous mode
....

Both bootlogs available

46

Thank you.

See PR explanation. You must revert the buggy VLAN commit that is already in 5.15. Afterwards network connectivity should work again.

1 Like
47

Done, works fine.

PR LGTM

Thank you for this contribution!