While 98% of the boxes out there have the same Broadcom RTL8211F chip inside, there are occasionally other chips used, and they can be using a different bus slot which requires a different device-tree and/or maybe an additional driver in the image. As a start, share the system log (assuming you can access SSH over WiFi).
Usage of banned add-ons means no support.
The log doesn't show any Ethernet related errors so next step is to open up the box and take pics of the board inside so we can see what Ethernet chip is being used. It probably needs something based on Q200 (as Q201 is for 10/100 designs) but with a different Ethernet PHY chip described in device-tree.
Q200 is external PHY to support 10/100/1000 chips, but the kernel does 'magic' to ensure it works with all varieties of PHY chip; the upstream kernel avoid magic and requires us to be specific. Q201 is for internal PHY boxes and supports 10/100 max.
The image only shows the Wireless/BT module so is not helpful. I'd need to see a pic of the entire board on both sides.
NB: The boot log under CE might also be useful, the log is quite verbose.
Kodi log isn't useful, it doesn't contain anything about the kernel setup. Run "dmesg | paste" after clean boot (assuming CE has a paste function like LE).
Thanks. The log omits most of the early boot, but there's an ID clue about the Ethernet device and that allowed me to dredge up some older threads in the LE/CE forums. It seems to have a problem ZTE chip and I'm not sure support for this has ever been fully resolved, but it gives me some ideas to test. I'm away for a few days but will have a look a custom device-tree later next week.
0.520527@2] eth0: PHY ID 03815c11 at 1 IRQ POLL (stmmac-0:01) active^ that's the important bit
I'm away for a few days but will have a look a custom device-tree later next week.
Thank you, much appreciated.
Thanks. The log omits most of the early boot, but there's an ID clue about the Ethernet device and that allowed me to dredge up some older threads in the LE/CE forums. It seems to have a problem ZTE chip and I'm not sure support for this has ever been fully resolved, but it gives me some ideas to test. I'm away for a few days but will have a look a custom device-tree later next week.
Code0.520527@2] eth0: PHY ID 03815c11 at 1 IRQ POLL (stmmac-0:01) active^ that's the important bit
Hi, any luck? Also, would it be possible to install LE to internal? Can I try with installtointernal command?
No progress due to other priorities over the last week. Read: https://wiki.libreelec.tv/hardware/amlogic#install2internal
No progress due to other priorities over the last week. Read: https://wiki.libreelec.tv/hardware/amlogic#install2internal
I don't understand why, but this script was never available under the name install2internal, and it's even referred to by that name in the official documentation, but in fact its original name was always installtointernal.
I still have this script in my legacy build, and I've even received feedback from users who couldn't run the install2internal script. Of course, if it has a different name, how the hell would it run?! I don't know who started spreading this typo, but it's already driving me crazy...
installtointernal -> This is the correct name, it's always been this!
