Mega Omega Software Release!
-
After upgrading one on my omegas, i couldn't connect to it via ssh over my local network wifi. Upon inspecting
/etc/config/wirelessi discovered that wireless settings were changed and became a mixture of my previous config before upgrade and defaults. For example, SSID has changed to "Omega-xxxx", while the password was the same as i need for the local wifi connection. It became a mix of access point and standard client setup.I ended up resetting the device (10 second press on button on the expansion dock) and re-running
wifisetup
-
@Andrei-Railean Thanks for letting us know! We will take a look at the upgrade process today and see what's the issue.
-
Ahh great update looks very slick and super stoked that the OLED expansion is working so well now. Just one quibble really and that is the repo mismatch still seems to be there:
opkg install tinc
Installing tinc (1.0.26-1) to root...
Downloading http://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/packages/packages/tinc_1.0.26-1_ar71xx.ipk.
Collected errors:- satisfy_dependencies_for: Cannot satisfy the following dependencies for tinc:
- kernel (= 3.18.20-1-7bed08fa9c06eb8089e82c200340ec66) *
- opkg_install_cmd: Cannot install package tinc.
root@Omega-1956:~# uname -a
Linux Omega-1956 3.18.23 #1 Fri Dec 4 02:26:08 UTC 2015 mips GNU/Linux
Are there any new repo updates we can use?
Great work otherwise. Thanks!
-
@t-nt It doesn't look like you are getting the Onion repo. I can't test till later today. @Lazar-Demin are the downloads supposed to automatically use the Onion repo, or is this something that needs to be configured?
-
@Chris-Ward The Onion repo currently has only part of the packages offered by the default OpenWRT repo. For stuff that's not on our repo, opkg still uses the default OpenWRT one. We are still in the process of compiling more packages over to our own repo.
-
Ah. Ok, that sounds like a good way to do it - gets the Onion repo partially out. Thanks.
-
@Chris-Ward @T-NT The Onion Repo is available by default, but as Boken said, it only offers some packages and the default OpenWRT Repos are still in use as well.
I was able to access all of the repos ok just now:
root@Omega-1302:~# opkg update Downloading http://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/packages/base/Packages.gz. Updated list of available packages in /var/opkg-lists/chaos_calmer_base. Downloading http://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/packages/base/Packages.sig. Signature check passed. Downloading http://repo.onion.io/omega/packages/Packages.gz. Updated list of available packages in /var/opkg-lists/chaos_calmer_onion. Downloading http://repo.onion.io/omega/packages/Packages.sig. Signature check passed. Downloading http://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/packages/packages/Packages.gz. Updated list of available packages in /var/opkg-lists/chaos_calmer_packages. Downloading http://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/packages/packages/Packages.sig. Signature check passed.Let me know if you still experience any issues.
-
Great update! And exciting to see the OLED support!
Interestingly, I can use oled-exp to write characters to the display that the web interface can't handle. E.g. attempting to write anything with parentheses (either opening or closing or both) in the web interface fails silently, but when using it in a quoted string in oled-exp it works fine. My suspicion is that something is not getting properly quoted/escaped from the web interface but I haven't poked into it to see.
-
@fader Yeah, we just encountered this bug as well, and we are working to fix it!
-
@Boken-Lin said:
@Chris-Ward The Onion repo currently has only part of the packages offered by the default OpenWRT repo. For stuff that's not on our repo, opkg still uses the default OpenWRT one. We are still in the process of compiling more packages over to our own repo.
Ahh well that explains that. Well if you can see your way to making tinc a priority that would be a great help. It is the only thing that is really stopping me using the Omega in a real world scenario. I need to tie it into it's own vpn because I want to put it on the same network at other smart sensors and stuff I use.
But like I say the rest of the work is fantastic and I cannot believe how clear and crisp the OLED display is. I positively squealed with delight when I saw my own images scrolling across the display
-
@T-NT It definitely is one of our highest priority items on the list
-
Just a quick update:
The OLED Expansion guide is up on the wiki!
I'll be adding more to it in the coming days but feel free to post any feedback.And I forgot to mention in the original post:
After upgrading to version 0.0.5 of the firmware, the/rootdirectory and every file in it will be preserved when doing any future firmware updates!
-
@Lazar-Demin Regarding:
- After upgrading to version 0.0.5 of the firmware, the /root directory and every file in it will be preserved when doing any future firmware updates
Cool. I will now remove /root/ from my /etc/sysupgrade.conf
-
@Kit-Bishop Lol, we've just found it really convenient to keep all the files we are working on under the
~directory.
-
@Boken-Lin Agreed!
That's why I have /root/ in my /etc/sysupgrade.conf !
-
@Boken-Lin Can the next firmware bake in the ps2/ps3 and other common and cheap cams? I know that it may run counter to your all's commercial endeavors, but I feel it would allow for wider adoption due to lowering the BOM on hobbyists making DIY webcams.
-
Thanks so much for the
opkg nodejs! Much easier than the hoop-jumping I was about to go through with the thumb drive installation! Any word about theIoT.jsbuild?
-
@Kit-Bishop said:
@Boken-Lin Agreed!
That's why I have /root/ in my /etc/sysupgrade.conf !Keep it in
/etc/sysupgrade.conf! The change was to include it there by default on all Omegas!
-
@Craig-Soich we're working on it but right now we're planning on releasing a slightly newer NodeJS version before IoTJS
-
This post is deleted!
