Posts made by Seth Hall

@Brad-Buskey Brad, what device (device name), did you use to mount your SD card? Can you provide an example of how you mounted your SD card? Thanks.

I just upgraded my Omega2+ to v0.1.9 b149 and I can now see my SD card as mmc0:

Mon Jan 16 19:41:54 2017 kern.info kernel: [ 4.731010] mmc0: new high speed SDHC card at address 0007
Mon Jan 16 19:41:54 2017 kern.info kernel: [ 4.822031] mmcblk0: mmc0:0007 SD32G 29.0 GiB
Mon Jan 16 19:41:54 2017 kern.info kernel: [ 4.915117] mmcblk0: p1 p2 p3

Now, how do I mount this device, and especially, as an expansion/overlay for the root partition?

 Thanks,
                Seth

Solved!

Jan 23: After reformatting my 32Gb microSD card, I was able to mount it successfully as /mnt/sda1. The sequence of instructions I followed is below.

Note that my SD card had been formatted for a bootable Fedora test installation previously, which left me with several unneeded and unwanted partitions, e.g.,

Mon Jan 16 19:41:54 2017 kern.info kernel: [ 4.915117] mmcblk0: p1 p2 p3

I reformatted the /dev/mccblk0 device, which removed these unwanted partitions and left me with the "0" partition, e.g., the whole device, as follows:

mkfs.ext4 /dev/mmcblk0

then mounted the new 32Gb partition thus:

mkdir /mnt/sda0
mount /dev/mmcblk0 /mnt/sda0

yielding this:

root@Omega-7117:/etc# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 5632 5632 0 100% /rom
tmpfs 62880 200 62680 0% /tmp
/dev/mtdblock6 25728 13856 11872 54% /overlay
overlayfs:/overlay 25728 13856 11872 54% /
tmpfs 512 0 512 0% /dev
/dev/mmcblk0 29767652 45080 28187392 0% /mnt/sda0

Life is good! Now I'll try to create an overlay so that I'll have plenty of space on the 'root' device for a development environment. I'll post back when I've succeeded.

Later Jan 23:

Following up on using my microSD to expand the root file system, I used the "exroot with pivot-root" technique described here:

  https://wiki.onion.io/Tutorials/Using-USB-Storage-as-Rootfs

but with appropriate references to my new SD device, and it worked perfectly. I now have a ~30gb root partition to work with, and this partition will be updated with all firmware updates I may chose to apply in the future. Nice. Here is what my file systems look like now:

root@Omega-7117:/# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 5632 5632 0 100% /rom
tmpfs 62880 268 62612 0% /tmp
/dev/mmcblk0 29767652 102380 28130092 0% /
tmpfs 512 0 512 0% /dev
/dev/mmcblk0 29767652 102380 28130092 0% /tmp/run/mountd/mmcblk0

Hope this helps.

@Kit-Bishop Thanks very much. I eventually found the Setup Code button (I am not sure why I'd missed it for so long!), and now I am able to connect to my device(s).

I must say that this should not have been as hard to sort out as is seemed; I think what is needed is a very simple, step-by-step guide, which the little blue "i" button definitely does not provide. If we hope for a high adoption rate for the Omega, initial "getting started" support is going to have to improve, and fast.

Now, onward and upward with Cloud Compile!

Hmm... I wasn't aware that one needed to do anything locally prior to connecting a device to the Cloud, although it makes sense. I can get to my device locally and see all of the 'console' options, including the "Onion Cloud Seetings: Setup Code". So what is the Setup Code? And where do I find it?

Hi,

I am trying to connect two of my Omegas to the Cloud, and am not having any luck. I can register a new device in the Device Manager, and receive a new device ID, but the device status is always "offline". I also cannot edit the Local IP filed in the Device Manager.

I use Firefox on a Windows 7 system, and I can access my two devices locally without difficulty. I have updated the firmware to v0.1.1 b308, and device-client is 0.5-1. I am also using root-pivot to expand my file system to 32Gb.

My Wifi connection is good, and I can ping multiple non-local servers. I cannot ping cloud.onion.io however.

How am I supposed to actually connect my devices to the cloud?? Should this be happening automatically as long as my device it power up? I'm obviously missing something!

Thanks, Seth

@Rudy-Trujillo Try to keep it positive, you know? We're all in this together after all.

I too have been trying the pivot-overlay approach to expand my root fiilesystem so that I may add new development tools.

I am able to 'see', mount, and touch my ext4 formatted USB drive, but I am not able to edit my /etc/config/fstab file, since the partition is reported as 'read-only'. What am I missing? How can I get around this?

My password is not being accepted when logging in through the Console terminal app. I am able to log into the console using 'root' and my new password (e.g., not onioneer.), and serial port communications is working fine; firmware is 0.0.6 b275.

This behavior is identical on all five of the Omegas I have. What might be the problem?

Just received my new Omegas and am very pleased. Now I am trying to enlarge the root file system so that I can start development, and decided to try using the

I am trying to implement a 32GB USB stick as a root /overlay, and my /etc file system is read-only, so I can't modify the /etc/config/fstab file appropriately to enable /overlay.

FYI, I earlier attempt to install Python in the 16MB root and of coarse ran out of space (what a dummy!) Now I don't know how to reclaim this space from the broken Python installation. I don't know if this is related to the read-only condition mentioned above.

Lastly, if I simply wanted to go back to the state of a factory new Open WRT installation and start again, how would I go about that? I ask because I have five new Omegas and intend to brick at least some of them