Short of taking the box, power supply and a tv/monitor down the mountain, not really. I'm not sure if this clears up anything but I tried running the command in the shell and it said 0Warning: Failed to create the file setup-kodi.sh: Read-only file system
curl: (23) Failed writing body (0 !=1113)
(2016-05-16, 00:21)docsuess84 Wrote: [ -> ]Short of taking the box, power supply and a tv/monitor down the mountain, not really. I'm not sure if this clears up anything but I tried running the command in the shell and it said 0Warning: Failed to create the file setup-kodi.sh: Read-only file system
curl: (23) Failed writing body (0 !=1113)
The 'cd ~;' should put you in a writable location, do that after 'shell' before the script commands
Sorry for the confusion. I did write the cd~ part. Do I write that directly in front of the commands? I typed shell cd~ and hit enter which then changed the crosh to chronos@
localhost and then I put in the commands as originally instructed.
'shell' enter 'cd ~' enter, then the rest starting with curl.
Hmm, cd~ gives command not found
Sorry, autocorrect deleted the space in between cd and the tilde
Well, I tried the script via logging in as a guest but got the same result. I guess I will have to take it into town and try doing it somewhere with better internet service. Thanks for walking me through it the best you could. Truly a lesson in patience.
(2016-05-16, 02:59)docsuess84 Wrote: [ -> ]Well, I tried the script via logging in as a guest but got the same result. I guess I will have to take it into town and try doing it somewhere with better internet service. Thanks for walking me through it the best you could. Truly a lesson in patience.
that seems very odd that a small (8mb) file would be getting corrupted on multiple attempts, unless your ISP is doing some really bad things. Just to be sure nothing is wrong on this end, what device are you attempting to set up?
(2016-05-16, 03:08)Matt Devo Wrote: [ -> ] (2016-05-16, 02:59)docsuess84 Wrote: [ -> ]Well, I tried the script via logging in as a guest but got the same result. I guess I will have to take it into town and try doing it somewhere with better internet service. Thanks for walking me through it the best you could. Truly a lesson in patience.
that seems very odd that a small (8mb) file would be getting corrupted on multiple attempts, unless your ISP is doing some really bad things. Just to be sure nothing is wrong on this end, what device are you attempting to set up?
It's an Asus Chromebox, the standard one. The only other thing I could think of is that I run a cellular modem as our ISP. It's our only option at the moment and only has 2G coverage so it's the equivalent of dial-up. I've never had an issue with corrupted files before though.
sorry if being asked already, whats the latest version with the cool egl stuff? i currently using oe 6.0.398 iirc
decided to check krypton, i've installed milhouse daily generic builds of libreelec (on old sandy bridge box) - looks stable
will it be good choice for a chromebox as well?
(2016-05-16, 04:45)docsuess84 Wrote: [ -> ]It's an Asus Chromebox, the standard one. The only other thing I could think of is that I run a cellular modem as our ISP. It's our only option at the moment and only has 2G coverage so it's the equivalent of dial-up. I've never had an issue with corrupted files before though.
yeah I just tested here on my Chromebox, no issues, so not sure why you're having difficulties =(
(2016-05-16, 22:15)sh33p Wrote: [ -> ]sorry if being asked already, whats the latest version with the cool egl stuff? i currently using oe 6.0.398 iirc
decided to check krypton, i've installed milhouse daily generic builds of libreelec (on old sandy bridge box) - looks stable
will it be good choice for a chromebox as well?
The Krypton-based LE builds are an excellent option if you don't mind testing bleeding edge stuff, and work perfectly well on Haswell/Broadwell Chromeboxes. Once they reach alpha status I'll include it as an option in the script.
Thanks Matt, any estimation on when they going to reach the alpha status?
Sent from my LG-H815
(2016-05-18, 05:09)sh33p Wrote: [ -> ]Thanks Matt, any estimation on when they going to reach the alpha status?
well, typically OE/LE ships nightly builds until they hit beta, vs numbered alpha builds; I don't have any special insight into when that will happen. You can run Milhouse's LE8/Kodi 17 nightly builds if you want which are reasonably stable now.
Are you sure that the LE test builds are stable or at least semi stable, I read in the thread that a lot of Intel users are having trouble running them, didn't read anything specifically chromebox related though.
Also the last time I tried the builds, estuary was at the very beginning stage and had a lot of bugs and a lot unfinished skinning. Just wondering how it looks now.
I'm still running 15.2 egl. Considering an upgrade, I don't know.
(2016-05-18, 16:43)ilovethakush Wrote: [ -> ]Are you sure that the LE test builds are stable or at least semi stable, I read in the thread that a lot of Intel users are having trouble running them, didn't read anything specifically chromebox related though.
Also the last time I tried the builds, estuary was at the very beginning stage and had a lot of bugs and a lot unfinished skinning. Just wondering how it looks now.
I'm still running 15.2 egl. Considering an upgrade, I don't know.
from what I've read, it's Braswell users having issues with the new (4.6.0) kernel. Can't say I've run into any showstopping issues while testing, but can't comment on long-term use obviously since always flashing new nightly builds. I run LE 7.0.1 on my main box for now.