Lucil

It's difficult to guess all the needed libs. I've installed the 32bit userland and now I get an "Illegal instruction" error. So that's why I was thinking of installing a complete 32bit build. Somewhat like RPi guys do and I guess it's because of them my ARM app build is 32bit, as the most widespread platform.

Would it be possible to use a 32bit build made for another board?

It's a comercial app, sources are closed. All platforms are supported (win, lin, mac), but ARM is provided just as a courtesy and I don't know if a 64 bit build can be made available.

I'm trying to run an executable on an OrangePi Prime. The message is: -bash: <filename>: No such file or directory The output of the file command on the executable is: <filename>: ELF 32-bit LSB executable, ARM, EABI5 version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 2.6.32, BuildID[sha1]=xxx, not stripped The app runs fine on OrangePi One, OrangePi Zero and Raspberry Pi.

Thanx, nice work with the script!

Zram maybe was not intended for creating ram drives. But it's fit to the task and it has the benefit it does not swap the contents of the ramdrive. So I'm not talking about system swap or system logs. Simply if using it in the above scenario (fast db storage) would crap the other components of it already running.

I have an OrangePi Prime with 2 GB RAM. I'm running a server-like node.js app that does constant writes to .json files and text log files. Let's call it "database storage". The app is not otherwise RAM intensive, can run fine on 512 MB boards. I'm thinking of putting all my RAM to use and move the database storage to a RAM disk made with Zram. Do you see any potential problems and interference with the way Zram is configured for this board?

Not bad, but limited. This would be a good always-on low power linux server. I tried with UserLAnd, but results are not good.

Yes, I was thinking of adapting a solution based on ... and the rest of the explanation on sunxi website.

I'm trying to get something beyond Android on a Jide Remix Mini. Originally sold as an "Android PC", it's now unsupported by manufacturer. The configuration is not bad: Allwinner A64 SOC and my unit has 2GB of RAM and 16 GB eMMC. Unfortunately, linux-sunxi lists it as (yet) unsupported. I'm not that knowledgeable with image building, so any help would be appreciated.

Explaining Computers has published a test somewhat suited to this topic, however I asked here first. He does a mix of testing with Linux, Windows and Android, picking what's best for every platform. As I see it, the most important part of a SBC is the C part: computer. Therefore, computer usage would mean computer-like software. If I wanted to use Android, many phones are more powerful than SBCs and Android software is geared towards phones anyway, not TV screens or monitors. So I would exclude Android and focus on the (general) computer part. That would mean Linux or Windows. My conclusion so far is, however, Android is better supported than Linux when it comes to desktop-like performance. I don't find the appeal of SBCs in the hundreds of dollars range. I'm talking home use, not industrial. I the hundreds of dollars range there's a lot of flexibility and you can build your own "SBC" much more powerful than SBCs. For example, I don't see what's all the fuss with the Latte Panda. Perhaps youtubers got it for free and that's why they are singing praises. Back in 2012 I bought an Asus Transformer tablet, it's Atom powered, it has 2 GB of RAM, came with Windows 8 and runs Windows 10 to this day. And it cost as much as a Latte Panda, but I already got 7 years of usage (and productivity and entertainment) out of it, I didn't have to wait 'till 2018. And it has it's own touch screen and keyboard and touch pad so no cables and no extra hardware to purchase. What I'm trying to say is I see the appeal of SBCs only below 100 dolars. Preferably way below.

Which do you think is the current SBC better suited as a (light) desktop? I think it would not be the one with the fastest CPU, but the one with the better software support for graphics acceleration and general usage. I have bee using a Raspberry Pi and it's fine, but it chokes because of insufficient memory.

In the context of this topic, after removing network-manager and configuring the network "the old way", via /etc/network/interfaces, what is the proper way to make sure that the WiFi radio is not emitting? I plan to place my OPi Zero next to the router (wired connection) and I want to make sure there's no unneeded radio interference. My /etc/network/interfaces: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp

I can confirm that removing network-manager and configuring the interfaces via /etc/network/interfaces does the trick (at least for now).

It's not just Ubuntu related. The Debian image has the same problem. And while we're on networking-related issues, with wi-fi conn my Opi Zero runs for about 36 hours, then locks and needs a hard reboot. It has always done that, but there's nothing useful in the logs. It just freezes. I suspect a wifi driver problem, some kind of overflow perhaps. "Solved" it with a daily cron reboot. Mine is HW rev. 1.5, mfg in March this year (according to the sticker), if it matters.

Obviously I'm using the wired connection. Trying the other sugestions above and will report back. LE: I found a solution... sort of. I did a clean install of an Armbian image (both mainline images work). Booted the first time without the ethernet cable inserted and I inserted the cable after the boot activity stopped (after about a minute). The device did get an IP address this time. I logged in through SSH and configured wireless. And now it works via wireless, onboard adapter. Thinking way back, it is possible that the first time I did the same, configured wireless on the first boot and then used it like that for months. The problems actually began when I moved and repurposed the device and tried to use it wired. Maybe the wired connection was acting all along. As for the suggestions above, I tried configuringit with static network info, but it didn't solve anything. Haven't tried the serial over USB yet.

How do I do this? It would be great for debugging - to see what's actually going on.

Yes, that's why I think it's strange. I don't know how to insert the conn details in the image. I don't think I can run tcpdump on the router, as its a TP Link with the stock firmware. As for running out of address space, no, I've tried rebooting the routher, but it has no effect. The box is smart enough to assign the same address to the same MAC. Presumably it's a difference between the image built a few months ago (I think april or may) and today. And because the older OrangePi supplied images work. And because with the older jesse image it boots the first time.

I've been using an OrangePi Zero hw rev. 1.5 for a few months with no issues, using the Stretch mainline image (4.x kernel). Suddenly the filesystem became read-only. I thought it was a SD card issue so I burned a fresh armbian to a new card. But the device does not show up in the DHCP pool with an allocated IP. Being withought a HDMI connector, an OPi Zero must be accessed via SSH. I've tried all versions, mainline and legacy. Only with Jessie legacy image, it gets an IP from the DHCP pool just on the very first boot. After that, it does not show up. I've tried the images provided by OrangePI and their Ubuntu and Raspbian images work. They have Ubuntu 14.x and Raspbian Jessie. Another strange behavior: the device has different MACs, depending an the distribution used. I think maybe it's something related to this, being one of those el-cheapo adapters with no proper MAC?