FYI, on the latest firmware, I just did it manually.

mkdir /home

edit /etc/passwd and add the user with 'x' in the passwd portion, /home/{username} for the home directory. You can either use groupid 100 (users, already in /etc/group) or add a group specifically for the user. (e.g. add user with id starting at 1000, add a group matching the username with the same id - probably a good idea to add the user to users also in the /etc/group)

Once the username is in /etc/passwd run:

passwd {username}
to set the passwd

mkdir /home/{username}

to create whatever you specified as the home directory, then

chown {username}.{groupname} /home/{username}

replacing the stuff in {} obviously with your values.
At that point, log out, log back in with the user in question. e.g. ssh myuser@myonion.local or whatever your ip is

OK, so I checked on the hologram dashboard and apparently they block incoming connections. They have downloads for something called 'spacebridge' but it won't run on arm. I tried installing the python version and it fails during setup.py for the requests install.

So, is there a way to tunnel to it just using ssh or is this spacebridge proprietary crap absolutely necessary to connect to your device over the hologram service? If so, the service is rather useless to me - connecting to my own device was sorta the whole reason I got a cellular modem. The fact that I can't seem to do it without some proprietary wrapper software for which there is no open source is rather disappointing for something that is supposed to be a development platform.

I followed the instructions to set up the hologram, it appears to be connected and working, but when I try to connect to the IP, I don't seem to get anywhere. I tried http, ssh and ping.

This was using the instructions as worded at https://onion.io/2bt-using-hologram-expansion/

So how do I actually go about connecting to it via the net?

Why is it that the latest version I see on the repository is 0.2.0 b192 but oupgrade is saying repo firmware version is 0.1.10 b160?

oupgrade

Device Firmware Version: 0.2.0 b192
Checking latest version online...
Repo Firmware Version: 0.1.10 b160
Comparing version numbers
Device firmware is up to date!

I ordered one of the bundles that included the mini-USB shield, the larger USB shield and the arduino footprint shield. If I use the mini shield, I seem to have no problems. If I use the arduino footprint shield and don't plug anything onto the GPIO, I have no problems. But if I use the larger USB shield with-or-without anything on the GPIO or the arduino shield with something plugged into the GPIO, they seem to start up just fine but if I come back a few minutes later, it is powered down and pressing reset and/or flipping the switch will not seem to power it back up. (I have to disconnect the USB and plug it back in)

My power sources should be more than sufficient (they were the largest USB-plug based power sources I could find at the time. One is a 10 port hub with a high-capacity charge plug at 2.5a and the other is a 5-port anker power-hub that I use to power my raspberry pi's. Also capable of 2.5-to-3.0 amp per connector)

Is there something in these shields or the plates that would trigger an auto-power-down mode? This morning I just connected the ethernet connector on the larger USB shield and it still powered down by the time I got to work. The arduino board still seems to be running but only because I didn't put anything on the GPIO.

FYI, on the latest firmware, I just did it manually.

mkdir /home

edit /etc/passwd and add the user with 'x' in the passwd portion, /home/{username} for the home directory. You can either use groupid 100 (users, already in /etc/group) or add a group specifically for the user. (e.g. add user with id starting at 1000, add a group matching the username with the same id - probably a good idea to add the user to users also in the /etc/group)

Once the username is in /etc/passwd run:

passwd {username}
to set the passwd

mkdir /home/{username}

to create whatever you specified as the home directory, then

chown {username}.{groupname} /home/{username}

replacing the stuff in {} obviously with your values.
At that point, log out, log back in with the user in question. e.g. ssh myuser@myonion.local or whatever your ip is

I was just looking at the wiki post about setting up the cross compiler environment for making custom flash binary files. It tells you how to add packages and set the onion target. But it makes no mention as to whether or not it is necessary to add in the onion specific files to the configuration or not. Are they included in the default .config if you follow those instructions or is there a copy of the .config you use in building the default image(s) somewhere?

Did I ask how to configured a power source for my iOmega? I asked if there is any way to speed up my ala carte portion of my order. I did this on the instruction of the email support address which said, and I quote:

Please create a thread in https://community.onion.io/ and we will respond to you there.

Regards,
Senthooran

This after I asked the same question in an email. I guess that was a lie. Oh wait, I got responses. Just not to the actual question I asked. (hint: it's in the SUBJECT)

I posted one of the $9 support donations in exchange for the Omega 2 plus package back last year. Having worked quite a deal with Raspberry Pi, ESP8266, Arduino, ATTiny, etc. I assumed I could just hook it up to a 3.3v power source and work with it. As I was waiting for them to start shipping, I also decided to post one of the bundle submissions once they announced the original package was actually on it's way -- and I did.
The first Omega 2 finally showed up a few weeks ago and around the same time I got the survey link to select my preferred docks/shields for the bundle I had just recently added. I filled it out and then also tacked on a mini-USB dock 'ala carte' as well as the GPRS/GSM shield.

When I finally went to hook the Omega 2 up, it got stuck in a boot loop using just my peg-board power supply. I saw on various forums that quick boot looping was likely a sign of not enough power. I then dug out a beefier 3.3v buck converter and plugged it to the iomega power. The boot went much further but still eventually froze, I'm guessing when it was trying to start the WiFi. Further reading on forums showed that a number of people were running into this, generally when they were trying to power it directly as I was. The guesses as to the problem was noise or inconsistency in the power source.
Most of the recommendations were to use one of the docks that had capacitors to buffer the power input properly and most of the responses were that using a dock solved the problem(s) for those who had been getting the same freeze-up that I was.

In the meantime, I can't use my Omega 2 apparently until I either figure out how to build a capacitor buffer myself to meet it's needs or until my docks show up. Yet there seems to be no hints yet that my dock order has even been fulfilled no less shipped.

I'm wondering if there is any way I can get at least the mini-USB dock that I ordered ala-cart (separate from the bundle) shipped early so I can start playing with my existing Omega 2 while waiting for the second one and the other bundle-docks/shields to arrive?

SW

OK, Now something else. It finishes the boot and I get a root@(none):/# prompt then it reads

[ 18.774680] EEPROM:Read from [factory] offset 0x0,length 0x400.

and the device no longer responds to keyboard input.

OK, I think I isolated the problem. The USB source I was using wasn't providing enough juice.