Sorry, that was incorrectly worded. I men you are trying to write to a file system that is not mounted.

I'm a newer user to Arch and Linux in general. I've got a pretty robust installation running on my computer with Fluxbox, PCManFM and SLiM for the graphical side (if these matter). Everything's running pretty well at the moment except I'd like to be able to auto-mount USB storage devices. Without adding the udev rule as mentioned here (because I would like the mounting to persist through a terminal window popping open), what's the best way to have things auto-mount like they do in Ubuntu or Windows? By this I mean I would plug in a USB flash drive and it'd automatically be mounted to somewhere like /media/<device name>/ and any user (or the one running x? or something) would have permissions to view/edit/execute.

@crispyoz I already did it but didn't work, got the same message

@Nagarjuna-Reddy So it seems the underlying issue is that your DHCP server is either not accessible or is not providing dhcp service correctly. Using static IP is a fix but your IP, routing and DNS should be provided by your DHCP server on your network.

@Nagarjuna-Reddy I see that you published in another post, and I think you were able to make your custom board start correctly, you should post the solution here, so that other people can get feedback from the experience.

@Nagarjuna-Reddy said in Onion 365 days: @crispyoz Hi Sir, I am facing few problems, When i am running while loop python programs in boot mode(it means when the power comes automatically program should execute)after my reboot command is not executing. For that i have added in /etc/rc.local file start-stop-deamon -b -S -x python /root/hello.py after added this command i am able to executing Reboot command also. So this is the only way we have to do or any other options are there?. Thank you. I will try your methods to increase my knowledge.

There is, of course, the Nova https://hologram.io/store/nova-global-cellular-modem/36 One problem I came across a while back was installing the Hologram Python SDK but any modem you get these days should be pretty easy to interface with a socket setup to the Hologram Cloud

@CAP-33 Great Here you are a more elegant (and easily scriptable) way. Run the below mentioned commands either on the Serial Console or connect with ssh your Omega's AP (192.168.3.1 by default): # Omega2 v0.2.0 b186 root@Omega-5533:~# uci set network.wwan.hostname='your_client_hostname' root@Omega-5533:~# uci commit network # Check the result (this is not mandatory of course): root@Omega-5533:~# uci show network network.loopback=interface network.loopback.ifname='lo' network.loopback.proto='static' network.loopback.ipaddr='127.0.0.1' network.loopback.netmask='255.0.0.0' network.globals=globals network.globals.ula_prefix='fd1d:48c4:7633::/48' network.wlan=interface network.wlan.type='bridge' network.wlan.proto='static' network.wlan.ipaddr='192.168.3.1' network.wlan.netmask='255.255.255.0' network.wlan.ip6assign='60' network.wan=interface network.wan.ifname='eth0' network.wan.proto='dhcp' network.wwan=interface network.wwan.ifname='apcli0' network.wwan.proto='dhcp' network.wwan.hostname='your_client_hostname' # release (with USR2) the lease root@Omega-5533:~# kill -USR2 `pidof udhcpc` # renew (with USR1) the lease root@Omega-5533:~# kill -USR1 `pidof udhcpc` Good luck!

@cas Yes, you are right - the key: edit the the first post Thanks!

Scratch the "anywhere" part. Double checked just now and it works everywhere BUT the terminal application.

We have the same problem in this topic: https://community.onion.io/topic/1481/losing-data-after-power-off/8 Have you solved the problem?

@Costas-Costas said in [resolved] Help, My Omega2 plus can't start successfully: @Pierre-Rossinès said in [resolved] Help, My Omega2 plus can't start successfully: @ccs-hello The worst part is that sometimes they work, sometimes they don't. That's the problem I have with my 2+'s wired up to AMS1117's. They will normally run for 24 to 36 hours and then fail. Don't know if they get too hot, run out of memory or receive a power spike. When I reboot them sometimes they boot up and sometimes they don't. If they don't bootup after a few tries I leave them for perhaps 30 to 60 minutes and generally they do bootup. Bit of a mystery. My Omega 2+ had a similar problem in that it would not reboot after it had been running a while (10 or 15 minutes was enough). After sitting unpowered for a while, it would happily boot again and run without apparent issue. Guessing that there was an intermittent thermally sensitive connection somewhere on the board that affected start up, I reflowed the solder on all exposed connections with an SMD hot air tool and the problem seems to have gone away. So with a sample set of one, it looks like a manufacturing defect in my case. My Omega 2 (not plus) didn't have this particular issue. Both had problems during boot when running from inadequate power. The symptom of that problem is running normally through startup, as monitored on the serial port, to the point where wifi was first brought up, about 18-20 seconds into the boot sequence. At that point they would reset and repeat this process indefinitely.

Hi everyone, I have the same problem. I have upgraded my Omega2+ to 0.1.10 b160 but i'm losing pkg and data after power off (or reboot). I would like to prove the sync command but i can't find it. I suppose that my omega2+ has fully initialized because the orange led is blinking all the time and I use the console after 2 minutes after boot.

I have the two little holes in the golden metal strips too, but no solder as you do. Btw, your photos are really sharp for the size! Nicely done! There's a component soldered sideways near the SD card connector edge, the edge opposite to the card entrance. Not sure if it's connected or not because it's darker there.

@administrators @Global-Moderators sent the following bug report from the web browser but as there is no confirmation you received it I have duplicated it here. Omega 2 is not yet available in your GPIO Tool. Path to the Omega 2 image is incorrect. You are sending http over https i.e. the tiny image at http://i.imgur.com/YLj4Oj6.png

I don't know the answer myself, but if it were important for me, I would compare the pinout of the Omega and the Omega2+ from Onion's documentation.