@crispyoz regarding user space DT overlays: there's a much more convenient solution by now (actually, it seems to have existed for a long time already), the dtbocfg loadable kernel module by Ichiro Kawazome, which I packaged for OpenWrt here. The only thing required for that to work is that the kernel is compiled with CONFIG_OF_OVERLAY=y. Much easier than patching the kernel sources. This all works fine, but I have a general problem with 24.10 on the MT7688 (not on other targets): it consumes waaaay to much CPU time doing I/O, and I could not yet track it down. Performance is normal for everything else, but when there is only a bit more of I/O going on, say a network download AND a serial output streaming some data, it sometimes stalls for seconds. I have no idea yet what that is. Does 24.10 run smoothly for you?

@MK I agree with @crispyoz that rc.local is the lowest impact file. To make it even more low impact, I would suggest adding a uci defaults file that changes rc.local instead of overwriting the default rc.local. UCI defaults are generally used to pre-configure the UCI configuration (/etc/config) in your images. But we also use this mechanism to pre-configure other things, like the login banner for example: https://github.com/OnionIoT/OpenWRT-Packages/blob/openwrt-23.05/omega2-base/files/etc/uci-defaults/14_banner More info on uci defaults here: https://openwrt.org/docs/guide-developer/uci-defaults

After having looked at the issue we realized that the issue is in the install file that we used. We mistakenly used the file for an Omega2+ install while using and Omega2 module. The two FW files are exactly the same in terms of byte size, however the content is quite different and results in the module not being able to boot properly. Here is an image of the log thinking it is an Omega2+ module despite not being one:

@luz very interesting. Thank you for the contribution. I did the same thing. But with a different logic. Run the "master" board every minute she try, by wifi, to connect to an omega-... connect on ssh (with key accept by default yes) without sshpass. After a successful connection ssh she inject a script that downloads the .bin from a repository on the LAN and starts the sysupgrade. (by wifi) I tested it with 100pz in 2 houres, all automatic. I can create many masters... and do everything faster. But my version is sh + python script Onion Omega2+ is the best! €€€

@andrew-khoo Here you are: http://repo.onion.io/omega/images/ CHANGELOG.md

@TypeSeven see the changelog: https://github.com/OnionIoT/source/blob/openwrt-18.06/CHANGELOG.md

if there is a newer settings app it would be in the new omega2 pro build which supposedly soon will be ported to the omega2.

Hi György, I took a somewhat more.. um... muscular approach... I tarred up all my customisations, shipped them out and did a restore to factory settings. Then I got exactly that error. Fortunately, there was an /sbin/block to call and I can now get on with what I was trying to do. Some documentation needs updating however Thanks and peace! chris

Enjoy

@Ulf-Zimmermann glad to hear that it works now. The wifisetup command shouldn't make any changes to /etc/config/network, what changes were you expecting it to make?

alzeih compiled a list here. I recommend taking a look at this thread. This project might interest you. AFAIK Onion hasn't released a .config file for the default firmware. But if someone finds that, I too would be interested.

@Sycol said in Kernel Panic! No Working init found.: I ran the firmware update from the webapp for my 2+. It bricked. I've noticed that my problem is with the kernel.Ive tried with this http://community.onion.io/topic/1154/omega-2-usb-firmware-install-after-brick-resolved but i cant even get the menu with the reset up. Try this way please: power OFF your Omega2+ press and hold down the Reset button (the momentary push button between the FW_RST pin and the +3.3V) switch the Omega's power ON and after this you should see the UBoot menu on the serial console... Good luck!

Have you tried to do a factory reset thru console command ... plus you might need to downgrade it thru serial ... download an older image and install it using .. sysupgrade -f image.bin

@Dave-Walmsley Yeah it is, I tried the command line and it worked well!