My raspberry pi 3 (didn't try the b+) had issues with powering the AD2, and adding a power supply to its barrel jack didn't help, so...
I had a couple of these Odroids laying around. I hadn't built them into infrastructure as who knows how long they'll be available? They're nice machines, and in the SBC category, I'd rate them between "Fast" and "Blazing fast" when used with EMMC. You'd think you were on a real computer.
Part of this is probably due to the work of this fellow making a debian distro with almost no fat - this thing boots like the wind, even compared to my "big and fast" boxes. As they say "just read the directions". I added chromium as directed here and it's great too.
This was so stripped down it didn't even have the usual direcories under /home/user, so I added ~/bin and ~/Public, and samba (via synaptic) and created a share of Public to make moving things around easier. I added my LANDNS (tellem and tellme) along with their .service files for systemD (yuck but it works).
Tightvnc gave me some fits at first, it either didn't want to autostart, or it would start and fail (and eat all the machine resources) or just not work (can't get name error).
While ssh -X works...I like VNC and have a ton of machines on my remina setup on my main boxes to admin or just run all the other stuff without having to break pose on the couch. So... this is what it took to make it work on Odroid-Stretch-Mate, the relevant text being:
Can you try removing everything from ~/.vnc/xstartup.turbovnc except:
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
exec /usr/bin/mate-session
? This will ensure that MATE is started directly rather than through the xinitrc mechanism. Perhaps it is the latter mechanism that it causing problems.
Other than the filename being a little different.
My own notes look like this:
Code: Select all
some trickery required to get tightvnc going on odroid-mate
A destop file needs to be in ~/.config/autostart and look like this:
[Desktop Entry]
Type=Application
Name=tightvnc
Comment=vnc server
Exec=vncserver :1
Startup Notify=false
We also have to change the ~/.vnc/xstartup to:
#!/bin/sh
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
exec /usr/bin/mate-session
After adding samba, and ~/Public, editing /etc/samba/smb.conf (no I don't make these crazy naming conventions) to add the share at the end looks like this:
Code: Select all
[pub]
comment = Public on LittleO
path = /home/odoid/Public
guest ok = yes
browseable = yes
writeable = yes
read only = no
This lashup runs Digilent's "Waveforms" software to drive the Analog Discovery2 as well as any other linux box I own, and through VNC at that, so I can be safely distant from things in the lab while doing tests with it. I can either use a wifi dongle (plan A) or plug it into the switch at the fusorPi that's fiber isolated from the rest of the network if there's too much noise for wifi to fly.
I can put up an image if anyone wants, or you can send me a self-addressed stamped SD card 16 gigs or bigger...Those new class A1 (on top of UHS 1 or 10) really do sing compared to the old days, but they're still SD cards. The EMMC on the odroid makes a ton of difference. I used the big passive heatsink for the XU4, but had the fans from the other version, and put those on top - it's somewhat overkill, but let me tell you, there is NO throttling ever. The fans are whiney - but this alerted me to various config problems that were eating resources and making the fan run when there shouldn't have been a need.
Note: These do actually need the 4 amp power supply they recommend. I did half of this with a jerry rigged 2 amp one, but started to have "issues"...and all went away on the big supply.