(01-26-2020, 03:55 AM)brent.thierens Wrote: It would surprise me if Linux tools would work, since normally nothing has been changed. I'm trying right now to get an updated Linux kernel with more flags (the mrfixit kernel) under CrOS. Hopefully that solves something for this.
When I enable Linux, I get an error on the stage 'creating disk image'. Any chance you can find the error causing this? Maybe, there is just a package missing to create the vm image or so. Other errors after that might be a result from that. Can the tools be enabled from terminal so we have some log output?
I had a hunch they probably wouldn't but tested and added it for anyone curious. Did this build utilize that mainline u-boot I sent you? I felt insanely quicker than the original builds from ayufan.
I think one of the vital tools missing is lxc. When I open a crosh tab and type lxc list, I get a message that lxc cannot be found. I haven't found a way to initiate the install through crosh, yet, unfortunately, but I'll keep looking. (If anyone else knows how, please share!) I think someone got some one earlier in the thread posted a snippet of output from their attempt to install. Hopefully they included the command they used.
Just found a CloudReady ticket that might hold some helpful things. One suggestion so far has been to try running the install again, and then checking /var/logs. I'm also seeing indications (at least by the CLoudReady staff) that Crostini may only work on 64bit installs. That could just be a CloudReady thing, though. I'm curious now whether CrOS for gru or kevin is armhf or arm64.
After having just read this post https://forum.pine64.org/showthread.php?...6#pid58156 I'm also curious if we can do something similar with one of Arnold the Bat's generic ARM builds.
