EDIT: ok, to be clear, to end users this topic is not really that interesting…
but just so I dont come across as a complete geek, that is doing this for kicks, a quick explanation as to why Im doing this project.
the purpose of this ‘project’ is to upgrade the underlying OS used by Organelle from a system that is pretty dated to a new version of Linux that is fully supported, and much easier to continue upgrading.
as such, the user (rightly) never even notices Organelle running Linux, so why do they care?
the short answer is, in itself they don’t, they are only interested the potential it brings… which is more up to date software, and then with that patching possibilities … i.e. this is solely an ‘enabling project’
secondarily, newer versions of linux have much improved hardware support, so this is also a factor.
(hmm, depending on your other hardware perhaps this is the primary benefit )
anyway… thats it, from here on in the rest gets pretty geeky…
so I was looking at Kernels again… and decided to try a different tack!
and to cut to the chase,
Ive got a 4.14.6 kernel/system running on my Organelle, a fully up to date linux system
… just to manage expectations, im in early testing still, but its looking promising.
what I decided to try, was to see if there was a distro that would work with the Organelle/Cubox,
- Initially i tried using solid runs ‘attempts’ including ignition, and that failed , as did there manual install of ArchLinux.
- I then tried ArchLinux (arm) (cubox) , that also failed… (but this might not be a dead horse yet )
- so I moved to Armbian - BINGO… both the cut down debian 9 stretch and desktop ubuntu xenai, both boot successful.
so Armbian is doing something very useful…
tested and working : sound (both sgtl5000 & hdmi), graphics , wifi , usb stick
I upgraded the deb 9 minimum release, and no issues… so really its all current.
(only one issue Ive had, is it shutting down when playing youtube… not quite sure why yet)
only config i had to do so far (except wifi etc) was to select the correct DTB, otherwise it didnt see the sgtl5000
so why is this good?
well if its stable, then we know the 4.14 kernel does work , and we also have an example of u-boot successfully booting it, moving to a later kernel, and also up to date packages/distro all makes support easier.
@AndyCap has notice the perils of using older distros this, whilst trying to get the SCIDE working
Im quite excited to see if we can get the accelerated graphics work, and so get some more performance for OTC/ETC.
ok, so I need to think about where to go next?! or whats the goal?
I think there are a couple of options:
a) switch to debian/Armbian, perhaps use the Minimal install , and strip it back further even, install X with Lightweight WM.
b) look at what Armbian is doing with u-boot/kernel , and see if that can give us clues as to why ArchLinux(arm) is not booting.
c) switch to Ubuntu - strip it down - not really an option, but worth mentioning , as out of the box its so close.
(perhaps I might keep for a dev environment ;))
whats your thoughts @oweno? push with ArchLinux , or consider Debian?
from previous discussions, perhaps ArchLinux is not the best for this kind of application, because the rolling release idea could be problematic for specialist SoC.
having been playing/developing with Organelle_UI/PD etc, I suspect it wouldn’t take much to switch to a different distro (and end users wont see/care)… I think an hour or two.
of course… these is all a bit premature, my next step is to put mother host, pd and also otc on the debian release, and then run it for a bit, and see how it feels, check no audio drop outs etc.
once this is done, I will also rebuild the kernel (we have the kernel configs, yippee!), to change it to pre-emptive, and check the sgtl5000 code, to see if the previous fix is still needed.
the main thing to test though is stability, as ‘new kernels’ , can always have quirks
anyway, quite happy to have got this far today :