For activating the ethernet bonding driver in the kernel, i downloaded the source tar.gz from TinkerOSv2.1.16 and recompiled it's kernel 4.4.132+ but it failed due to a faulty wlan driver called like "2T0x00".
I needed to reconfigure the kernel without this wlan driver (i never knew about the manufacturer) so it finished compiling successfull and put the new "zImage"kernel file in "/arch/arm/boot". Why there is an error in the sources of the TinkerOS?
Maybe you can fix that fault in the sources?
My new bonding kernel lost its + in it's name, it's now kernel 4.4.132 but it works fine and boot from the eMMC of the TinkerBoard S.
Any other tried kernels (4.4.267|4.9|5.4.114) wasn't able to boot from eMMC, why?
Im the dmesg/syslog i saw it couldn`t see the block device 179 and pointed the partition to 0,0 - zero pointer = Game over!
I'm sure a driver for the eMMC itself or the eMMC-Controller HS200 was missing.
Which driver was missing for the mmc?
For activating the ethernet bonding driver in the kernel, i downloaded the source tar.gz from TinkerOSv2.1.16 and recompiled it's kernel 4.4.132+ but it failed due to a faulty wlan driver called like "2T0x00". I needed to reconfigure the kernel without this wlan driver (i never knew about the manufacturer) so it finished compiling successfull and put the new "zImage"kernel file in "/arch/arm/boot". Why there is an error in the sources of the TinkerOS? Maybe you can fix that fault in the sources?
My new bonding kernel lost its + in it's name, it's now kernel 4.4.132 but it works fine and boot from the eMMC of the TinkerBoard S.
Any other tried kernels (4.4.267|4.9|5.4.114) wasn't able to boot from eMMC, why?
Im the dmesg/syslog i saw it couldn`t see the block device 179 and pointed the partition to 0,0 - zero pointer = Game over!
I'm sure a driver for the eMMC itself or the eMMC-Controller HS200 was missing. Which driver was missing for the mmc?