It took me about 2 months to get the feed-back sorted. I eventually got a direct link from the HelpDesk to sort it. Having shipped more products, Helpdesk is probably even busier than before but there must be something wrong with the delay you are quoting.
The initial survey link would not work for me: e-mail addresses are NOT case sensitive, so my e-mail was probably stored all lower-case regardless of what I typed. However, it seems the feed-back system IS case sensitive, which may had the survey failing... No way I could get this working without helpdesk link AND the insight I needed to try e-mail ALL lower-case on the survey.
3 months ago, I got a reply to my helpdesk ticket in a couple of weeks. If you got no reply for 2 months, I would suggest editing the initial ticket, making sure it is still open and there is your e-mail adress and Pledge number on the right hand side. If it is closed or if you needed to open a new ticket, you might refer to the old ticket number, date, and please make sure to provide your email address, kick start number and seat tight. Helpdesk system shall acknowlege your request with a warning
Due to our recent wildly successful Kickstarter and Indiegogo campaigns we are dealing with a significantly higher volume of tickets than usual. A support representative will be reviewing your request and will send you a personal response typically within 7-10 business days.
If you are inquiring about a Kickstarter pledge or Onion Store order, it helps us process and respond to your ticket faster if you have included details such as your backer #, order #, etc. If you have already, thanks! If you have not done so yet, please send a follow-up reply with any relevant information so we can speed up the investigation.
Once the survey has been sorted, it took me another couple of months to receive my kits. I am happy to say they were configured after a couple of days trying different things. I am certain Omega is a great product which can only improve in time and I would only suggest you to order MORE than what you need in the very short term to accomodate for future delays in product delivery and possible mishaps with configuration...
The amber LED on your Omega should turn on and then start blinking...
It’s possible that your Omega will behave a little differently: if the amber LED on your Omega turns on and remains on, wait for about a minute, and your Omega will have booted.
Most probably it will not blinking because your Omega's firmware is fairly old.
Connect your PC to the Omega’s WiFi Network
The Omega hosts it’s own WiFi network access point. Lets connect your computer to it. The WiFi network is named the same as your Omega and the default password is 12345678
The Setup Wizard
Open your favourite browser (Google Chrome is a good choice here and now) and navigate to... http://192.168.3.1
You have now arrived at the Setup Wizard...
I hope so. :slight_smile:
Thanks Setup Wizard, but my Omega's wifi never turns on.
Thanks very much everyone for the help. Really appreciate it. I am going to try and send this Omega back + The Power Station as there is clearly something wrong with the hardware somewhere. Surprised it was broken out the box. I hope they will be able to replace it.
I have tried contacting them via onion support (https://onion.freshdesk.com/support/tickets) and via the Indiegogo campaign where I bought it, for a refund. I have had no replies so far. I wonder if I will they will replace my dud Omega.
The square IC in that board is a USB-serial chip (most likely CP2102.)
Usually when it was hit by high voltage even in a brief moment, it will be damaged and causing shortage.
BTW, the power switcher IC (5 --> 3.3V IC, the 5-pin one) may have also died.
This IC is very useful since it has the special "zero droipout" design.
On the other hand, it will also meet its instant death when power supply goes above 5.5V, even briefly.
wifi is not booting i can not log in it's stuck at the screen that i posted
Again, until you solve the serial noise you are just wasting everyone's time - especially your own.
Without clean output you cannot determine what the actual stopping state is. The only clean output you posted was from a different device, not the problem device, so it is meaningless. Don't assume that power and serial solutions that work on one will work on the other, as you are in the domain of edge cases.
Without clean input you can't even know if there is an actual problem, or if noise inputs are being interpreted as a user request to halt the bootup and remain in u-boot.
rpc.nfsd: Unable to access /proc/fs/nfsd errno 2 (No such file or directory).
Please try, as root, 'mount -t nfsd nfsd /proc/fs/nfsd' and then restart rpc.nfsd to correct the problem
satisfy_dependencies_for: Cannot satisfy the following dependencies for nfs-kernel-server:
kmod-fs-nfsd * kmod-fs-nfs *
opkg_install_cmd: Cannot install package nfs-kernel-server.
root@Omega-8D69:~# uname -a
Linux Omega-8D69 4.4.46 #0 Thu Feb 2 23:46:03 2017 mips GNU/Linux
Hi to all. A had the same problem, but change the router password and set only alpha numeric password (without expecual characters) and the connection work. I don't know how but I expend a Lot of time trying to connect. i made a lot of test on the router (CISCO Linksys Smart WIFI EA2700) change bandwidth, wifi type, channels and does'nt work. The last test was change the password and works.
Thanks all, I went through the process again and now it's saving the console and other files.
I think the problem may have been in my patience. When installing, I would restart it if there was a really long period of no feedback. I let it work longer this time during all the steps and saw it continue doing more stuff. It might be that I just couldn't expect it to work as fast as I thought.