Have you tried downloading the latest firmware to /tmp/ on the Omega and doing a sysupgrade /tmp/<firmware-image> manually?

If your Omega has network, you can pull the firmware from an ssh shell and perform the upgrade.

If your Omega doesn't have upstream connectivity, you can scp (or pscp on windows) the firwmare image downloaded to your workstation/laptop over to the Omega to perform a manual upgrade.

Have you tried downloading the latest firmware to /tmp/ on the Omega and doing a sysupgrade /tmp/<firmware-image> manually?

If your Omega has network, you can pull the firmware from an ssh shell and perform the upgrade.

If your Omega doesn't have upstream connectivity, you can scp (or pscp on windows) the firwmare image downloaded to your workstation/laptop over to the Omega to perform a manual upgrade.

I'm using golang, for MQTT over ssl. The solution in our code was to use tcps for the connector and port 8333.

Granted, we're using certificates already in the ca-bundle (Amazon) for the upstream message broker, so we don't need to finagle self-signed certs.

What language are you using?

I'm going to pass on watching the video, but instead here are some tips on the setup scripts.

If you're just interested in how the wifi is configured, take a look at /usr/bin/wifisetup for the guts of the process.

If you're interested in all of the backend behind the web first-time configuration, examine the content under /www/OnionOS/static/js.

rc.local paradigm works just fine on the Omega.

Your issue would be OBVIOUS if you would post your rc.local, but instead have everyone guessing as to what you're doing and why it's not working.

My guesses:

• You haven't made rc.local executable. Make sure to chmod +x the file.
• You are trying to run python3, but you likely haven't specified a shell interpreter in a hash-bang at the top - so python can't be found because there's no set executable search path.
• You don't have python3, or it's not found in the executable search path (have you tried hardcoding the full path: /usr/bin/python3?)

Before saying "no, no, no" to these (admitted) guesses, consider actually posting your full rc.local along with the output of which python3 and ls -l /etc/rc.local. Those should provide an immediate answer to your issue.

I'm sorry that you're having issues with loading the kernel modules. It's a commonly-hit wall.

If you're using 4.14.81, you'll need kmod-spi-bitbang, kmod-spi-gpio and kmod-spi-gpio-custom.

mazer@snowball:~# ssh root@192.168.3.1
root@192.168.3.1's password: 


BusyBox v1.28.3 () built-in shell (ash)

   ____       _             ____
  / __ \___  (_)__  ___    / __ \__ _  ___ ___ ____ _
 / /_/ / _ \/ / _ \/ _ \  / /_/ /  ' \/ -_) _ `/ _ `/
 \____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/
 W H A T  W I L L  Y O U  I N V E N T ?  /___/
 -----------------------------------------------------
   Ω-ware: 0.3.2 b237
 -----------------------------------------------------
root@Omega-73D6:~# uname -r
4.14.81
root@Omega-73D6:~# lsmod | grep spi
regmap_spi              1274  0 
spi_bitbang             2661  1 spi_gpio
spi_gpio                5424  0 
spidev                  6336  0 
root@Omega-73D6:~# opkg list-installed | grep spi
kmod-spi-bitbang - 4.14.81-1
kmod-spi-dev - 4.14.81-1
kmod-spi-gpio - 4.14.81-1
kmod-spi-gpio-custom - 4.14.81-1
spi-tools - 1-cc6a41fdcec60610703ba6db488c621c64952898

Edit: added the package versions

@György-Farkas

If you're attempting to install 4.14.81-1, you don't have the most recent firmware/sources.

You've also moved to gpio?

Following my process, I am able to install every kmod in the current target repository.

Whenever you get this message it means that the kernel that you're running and the kmod packages in the repository are out of sync.

My recommendation would be:

• Upgrade your firmware. The most-recent version appears to be b237 as of 2020-04-07.
• On reboot, enable the target repository, which would be kmod-mii_4.14.171-1_mipsel_24kc.ipk as of 2020-04-07.

Then attempt to install the kernel module again.

@WickedCreations

Getting gcc and gdb (and g++ and golang, etc.) is still supported.

The howto's have broken links, but the gist of the process is sound. The gcc and gdb packages are still available through opkg package management.

I develop on Omega2+ hardware which requires a supplemental storage device due to the size of the development packages (e.g., I require a microSD because of the limited on-device storage). I do not know if this is true for the Omega2Pro (which is the heading under which your post has been entered -- you're shotgunning posts all over the place, so perhaps next time you might consider crafting your own new thread).

The general process is:

• Update your firmware to the most recent found at the official repository. Depending on where/when you acquired your device, the kernel and package configuration might be outdated. Updating your firmware is usually the best approach to assure the kernel, firmware, and available packages are all in sync.
• Get your system to boot to external storage. The howto for this is still up to date and valid (although there's been an unnecessary step in the documented process for quite some time, it's benign). My recommendation is to do this after updating your firmware, as I've had situations where new firmware doesn't recognize the UUIDs for the partitions created under the previous firmware, making /overlay no longer mount correctly at boot.
• Edit /etc/opkg/distfeeds.conf and enable the repo where gcc can be pulled from. You will likely also want to enable the repo where libgcc and libstdcpp are found.
• Issue opkg update ; opkg install gcc gdb
• If it reports missing packages, find the repo that provides the missing package and enable it; update and repeat.
  ** Which repo has the files that you need? Visit the links and check
  ** Should you enable all repos? No. As @Jesuso discovered.

In the long term, I would highly recommend learning how to create your own firmware and packages so that you don't need to depend on valid links. The docker build image works extremely well for crafting your own customized Omega2 experience and the documentation provided at the github repo is (currently) the most up-to-date documentation for doing so.