Indeed if network manager does not work, the ethernet won't get an IP automatically. Perhaps the ssv6051 driver makes the network manager crash? (you may try to blacklist the driver).
The ssv6051 driver is the same as legacy, but some things have been necessarily changed to work on mainline kernel. In your case, it is not just a problem of the detection of the chip, but there is some kind of communication issue because the driver can't read the efuse from the chip (that, in fact, is the reason of the bad detection).
Impossibile, perhaps you did not follow the instructions correctly (ie: erase the internal eMMC first)
ssv6051 driver is crap, in your particular case for some reason is not able to detect correctly the chip version and indefies it as ssv6051q, instead it is ssv6051p, but I don't know the reason.
For the ethernet part, it usually just works in the uttermost majority of situations, there has never been the need to do adjustments on any board, so it sounds strange that on yours it does not work.
Thank you for this amazing project. It truly revived this old TV Box from the dead.
Firstly, I want to share my experience with my my board (HK1 Mini), which might be useful to others.
Booting mainline kernel builds from SD card was not possible, but It booted successfully once flashed to eMMC. On the other hand, legacy booted from SD card just fine.
Bricked my board using build "Armbian_23.08.0-trunk_Rk322x-box_bookworm_current_6.1.39_minimal", but then recovered using original firmware, FactoryTool and MaskROM.
For my eMMC chip (Samsung KLMAG2GEAC-B002) I have posted the pins below to enter MaskROM mode.
Everything works on legacy build (Armbian_22.02.0-trunk_Rk322x-box_bullseye_legacy_4.4.194_minimal).
However, Ethernet and WiFi on newer kernel versions does not. The build I am using is "Armbian_23.5.1_Rk322x-box_bookworm_current_6.1.30".
This is where I'm stuck and ask for help.
This board uses the SSV6051 network chip and rk322x-config detects it correctly, but does not give me the option to select the driver like it did on legacy build.
I have tested all the LED configs, but none fix the issue on mainline, while the default config worked perfectly on legacy.
SSV6200 driver and NetworkManager throw a bunch of errors on startup.
Here I have attached the logs and DTS/DTB. I would greatly appreciate it if you could take a look.
Tell me if the DTB is incorrect in any way because binwalk found multiple locations from the backup.
hk1mini.dtb
hk1mini.dts
armbian-hardware-monitor.log
Thank you!
---
HK1 Mini Board (RK3229-D4-V02)
MaskROM pins for Samsung KLMAG2GEAC-B002 (or B001 - the last number is unclear)