Posts made by Colin Hogben

Thanks @Venet and @luz for your comments. I can see from your other posts that you've been frunstrated by this issue for a long time.

I'm not sure that I'd have bought an Onion Omega2+ if I'd thought it was effectively a closed-source system.

I found this OpenWRT forum post describing how the hash is calculated - adding any kernel modules will change it.

I was able to build a set of firmware and packages using WereCatf''s source fork, but I really need to use the same kernel version and equivalent configuration to generate compatible kernel modules.

Could the Onion devs please supply the .config they used to generate the latest release?

Hi,
I'm tring to set up a webcam on my Omega2+ by following the Projects
Book.

The project does not cover the possibility of using a webcam other than the one linked to (which costs several times more than the Omega2+ and dock combined). I have an existing webcam available which is supported by Linux (Playstation Eye), but it requires a kernel module which is not included by default. From my point of view, that's quite understandable, though I would expect that an inexperienced user - e.g. one who did not know what the date command did - would be flummoxed at this stage.

However, I had determined elsewhere that the webcam requires the
gspca-ov534 kernel module. Having enabled the lede-project repos as per the project instructions, I found that a package kmod-video-gspca-ov534 is available, but this will not install due to kernel version requirements - it expects 4.4.61 compared to 4.4.46 on the Omega2+ (n.b. I have updated the firmware to the latest version
i.e. 0.1.10).

I didn't find any Onion docs describing how to cross-compile for the
Omega2+, only the orginal Omega. The following forum posts give some clues, but no definitive information:

https://community.onion.io/topic/1523/so-close-hfs-support/5
https://community.onion.io/topic/1756/request-kernel-module-kmod-cryptodev
https://community.onion.io/topic/1592/project-docker-omega2-sdk-for-cross-compilation-cmake-support
https://community.onion.io/topic/1298/omega2-cross-compiler-and-kernel-sources/4
https://community.onion.io/topic/1134/guide-to-cross-compilation-for-omega2/7
https://community.onion.io/topic/1139/omega2-cannot-install-kmod-fs-ext4-kmod-usb-storage-extra-kernel-version-mismatch
https://community.onion.io/topic/1775/how-can-i-get-the-source-code-of-omega2-s-firmware/3

What I did try was to pull the sources tree from lede-project onto my ubuntu x86_64 system, enable
the relevant modules via menuconfig and build everything. That
succeeded and built image and modules for 4.4.61, so then I checked
out the commit just before the kernel was bumped to 4.4.47 and built
again. This time I got kmod packages for 4.4.46, but they still
wouldn't install due to a different hash in the kernel version.

The fork in https://github.com/OnionIoT/source was no help - all
branches have include/kernel-version.mk at 4.4.39 or 4.4.38.

Am I on the right track? Are extra kernel module packages available
somewhere already? Or where can I get the correct version of the
sources to build compatible kernel modules?

In the GPIO Tool, I select GPIO 15 (blue LED) in the Omega[2+] view, set it to Output and Sync, and then switch to Expansion Dock layout. I can then change the output value OK, but if I press Sync, an enormous rotating cog appears, and remains until I select a different GPIO pin.

(Pins 15,16,17, connected to the RGB LED on the expansion dock, do not appear to be available to select in the doc layout option.)

In the GPIO Tool, if I select GPIO 15 (in Omege[2+] layout) then change the direction from Input to Output, the blue LED immediately turns on. However, the Value control is not changeable until the Sync button is pressed. Then, changing the value has immediate effect on the hardware, but the icon colour is not updated until the Sync button is pressed again.

It seems a little odd that the hardware should be affected (maybe through the cloud) but the local user interface changes require additional actions by the user.

In the console GPIO Tool, if I select Board Layout -> Omega2+, the background displays as a broken image symbol. By comparison, in the cloud version, selecting Board Layout -> Omega yields a valid image.

My Omega2+ is registered with the Onion Cloud and is shown as online. I can successfully turn the LEDs on & off using the GPIO app. However, when I click on my device in Device Explorer, I get a message:

“Device Error
There was a problem accessing your device”.

Is there any way to get more information about this error, either from the cloud side or from the Omega2+?

Having installed the onion-console-terminal package, I find that some keys are ignored, namely the "-"/"_" key and the "#"/"~" key. This is with Firefox on Ubuntu.

Assuming you have your Omega2+ set up and connected to the internet, you can install these packages from the command line (which you can access either via ssh or via the USB serial interface). E.g.

root@Omega-B287:/# opkg install onion-console-editor
Installing onion-console-editor (0.2-1) to root...
Downloading http://repo.onion.io/omega2/packages/onion-console-editor_0.2-1_mipsel_24kc.ipk.
Configuring onion-console-editor.

Similarly for onion-console-terminal and onion-console-webcam