I have not found kmod-rtc-pcf8563 in any of the official OpenWrt repositories as a separate package. I could be mistaken, but it appears that you will have to build your own regardless of which device you use (Onion Omega or otherwise). Onion might build it special for you if you ask.

Newest OpenWrt v18 repo
https://downloads.openwrt.org/releases/18.06.4/targets/ramips/mt76x8/kmods/4.14.131-1-310e67ce48c0c3cc8b8d5e327035259a/

Newest OpenWrt v17 repo
https://downloads.openwrt.org/releases/17.01.7/targets/ramips/mt7688/packages/

Newest OpenWrt snapshot repo
https://downloads.openwrt.org/snapshots/targets/ramips/mt76x8/kmods/

Newest Onion repo
http://repo.onioniot.com/omega2/packages/core/

@György-Farkas damn, I was hoping this wasn't the case. Thanks for your help though.

@György-Farkas thanks for the reply.

I have two CP210x devices, one connected to UART0 (115200 8 N 1) and another to UART1 (9600 8 N 1).

I then have two instances of PuTTY running, one connected to UART0 and another to UART1.

The UART0 screen has a command prompt, and I can successfully issue commands, but UART1 screen has no such prompt.

I can successfully issue this command on UART0 to UART1:

echo "test" > /dev/ttyS1

On the UART1 screen, I see:

test

Also, I notice when I type anything into the UART1 screen, I immediately see it echoed verbatim on the UART0 screen. UART1 doesn't seem to be able to issue/run commands. I'm interested in using command prompt on the UART1 to be able to issue commands. Is this possible?

Hello,

I am using an Omega2S+, and while I can successfully connect to UART0 for a serial command line (using a CP210x USB to UART), I have had no luck for UART1 and UART2. Is this even possible? If so, how would I enable it?

The Omega2S Datasheet indicates that:

There are three (3) 2-pin Serial UARTs available. The UART logic level is 3.3V.
The default bootloader and operating system use UART0 to provide serial command line access.

For reference, here are the pin assignments for the Omega2S+ that I am using:

I've explored https (ssl) on nginx, uhttpd, and lighttpd. I've only had success with lighttpd. Your best bet is to use that instead of nginx.

@Douglas-Kryder all great information, thank you. Your guess of a new wifi driver release seems realistic. If it doesn't arrive by July (which would be nearly 1 year late) then it probably won't ever come. I'll start testing the official lede builds with Onion packages and report back my findings.

@Douglas-Kryder thanks for the info.

I'll explore the official latest lede firmware.

Two questions/concerns about the official lede firmware:

1. If I want to continue using the Onion Omega OLED, would it be as simple as including the Onion opkg repo and installing packages such as oled-exp and libonionoledexp?

2. Any idea what wifi performance looks like on the latest lede builds? From what I've read there were wifi woes and performance issues with the open source driver. That said, in the recent months the openwrt (lede) github repo for the MediaTek MT7688 mac80211 driver seems to have had an uptick in developer commits.

Hi All,

I'm currently developing on the Omega 2+ and am confused as to how I should handle maintaining the latest firmware/kernel/package builds.

I notice that the latest Onion firmware build v0.1.10-b160 (http://repo.onion.io/omega2/images/) is from March 1, 2017 and is running kernel version 4.4.46-1-611bddde2031bc44b7d050f62495d77

Let's assume I want to upgrade all packages on my Omega 2+, for example "kmod-fs-ext4". When I run "opkg install kmod-fs-ext4" opkg gives me the following dependency error:

Upgrading kmod-fs-ext4 on root from 4.4.46-1 to 4.4.74-1...
Downloading http://repo.onion.io/omega2/packages/core/kmod-fs-ext4_4.4.74-1_mipsel_24kc.ipk
Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-fs-ext4:
 *      kernel (= 4.4.74-1-97eec485b1ee24d5b1ca0357d1dd7304) *
 * opkg_install_cmd: Cannot install package kmod-fs-ext4.

On the surface this seems like an easy fix, install the specified kernel first then try again.

From browsing http://repo.onion.io/omega2/packages/core/ I can see that the newest three kernel builds are as follows (all newer than what is found on b160):

kernel_4.4.46-1-a034340f992dd68b87dc5b7a57950bb..> 02-Mar-2017 19:50                 790
kernel_4.4.46-1-70b845231417daffde6a00b449f8955..> 20-Apr-2017 21:44                 791
kernel_4.4.74-1-97eec485b1ee24d5b1ca0357d1dd730..> 19-Sep-2017 15:39                 781

This is where I get confused...

• Is updating the kernel considered safe?

• Are specific kernels more stable than others?

• Will it likely break other installed packages?

• If I update to kernel 4.4.74 does that mean I need to update all other currently installed kmods as well (to avoid incompatibility)?

• What is the best approach to using the latest packages releases while maintaining compatibility? (eg. update kernel first, then update kmods, then update all other packages?)

• Is there an easy way I can incorporate the latest kernel and packages into a .bin for me to flash?

• Not a critique of Onion, but any idea why Onion would build new kernels and packages, but not build a new firmware to include them?

I went ahead and decided to install the new 4.4.74 kernel, but when I update "kmod-usb-net" to kmod-usb-net_4.4.74-1_mipsel_24kc I am presented with the following opkg error:

Downloading http://repo.onion.io/omega2/packages/core/kmod-usb-net_4.4.74-1_mipsel_24kc.ipk
Configuring kmod-usb-net.
failed to find a module named usbnet
Collected errors:
 * pkg_run_script: package "kmod-usb-net" postinst script returned status 255.
 * opkg_configure: kmod-usb-net.postinst returned 255.

I have noticed that many other kmod packages that rely on the 4.4.74 also report the same "255" error. Any idea why this is happening?