Mega Omega Software Release!
Awesome, thanks for the update and detailed change info! Looking forward to the documentation releases.
Good job on the update and on giving us NodeJS!
@Lazar-Demin Sorry to be picky after all the good work you people have done, but a couple of issues:
I had previously done the pivot-overlay method from https://wiki.onion.io/Tutorials/Using-USB-Storage-as-Rootfs to give me more space - it was all working well.
However, the upgrade to 0.0.5 b233 over wrote my /etc/config/fstab file and I no longer had access to /overlay on my USB
I hand edited /etc/config/fstab back to reference /overlay but then my Omega believed it was still on the earlier version - so I will need to do the pivot-overlay procedure again Not a big deal since I wont' loose anything I can't recover, but perhaps this should be addressed in a future release.
Which brings me to the second point - in looking for the details for https://wiki.onion.io/Tutorials/Using-USB-Storage-as-Rootfs to check that I was getting the details right I found the Omega Wiki doesn't seem to be available now - https://wiki.onion.io/Home gives a 502 Bad Gateway response
@Kit-Bishop Don't worry, that's what we are here for! We won't stop until all the issues have been addressed.
- We will make sure we don't erase /etc/config/fstab file since some users will be using the pivot-overlay method.
- Wiki is back up. It was overloaded for some reason. Sorry about that!
- Good idea about preserving /etc/config/fstab
- Have seen Wiki is back up - thanks
@Boken-Lin All back to where I was - just had to reinstall a couple of opkg packages after redoing the pivot-overlay stuff
Sorry - me again with another problem.
Accessing Editor in Console shows no files:
This is with both Chrome and Firefox
I wonder if this may be being caused by the last used path no longer existing. I don't remember whether or not I had deleted anything - it is possible. However, Editor should just use a default path in this case.
@Boken-Lin I've been doing a bit more digging and think the problem comes from here in onion-file-provider.html:
Still digging to see if I can find the cause and/or fix it.
@Kit-Bishop Can you download this file: https://s3-us-west-2.amazonaws.com/onion-cdn/community/console/console.tar.gz. This is a tarball of the console that I am testing (and didn't find any error). you just need to delete the
/wwwdirectory on your Omega, and replace it with the content of the tarball.
Please let me know if it does anything. If not, I will take a look at it again tomorrow morning.
@Boken-Lin Using the tar.gz file you supplied, it all works
At this stage, I don't know why, though I did have to flush my browser data first.
I then did a file comparison between what you sent me and what was originally in my /www directory (I preserved it first). The files were identical and when I restored my original /www files, everything worked.
My suspicion at this stage is that my problem was originally caused by something that the browser had cached.
I had to clear cache individually on Chrome and Firefox before each worked properly.
If there is nothing that can be done for dealing with invalid information coming from cached browser data, it might be an idea to document somewhere that clearing of cached browser data might be needed.
Anyway, thanks again for your advice and help. I'm all happy here
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
@Andrei-Railean Thanks for letting us know! We will take a look at the upgrade process today and see what's the issue.
T NT last edited by
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...
- 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.
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.