(2019-02-03, 04:06)Matt Devo Wrote:

(2019-02-03, 03:56)sow07 Wrote: Which faq?  Yours doesn't mention it.  There's the LibreElec FAQ but don't see anything there.  Or the Kodi FAQ/Linux FAQ.  

I ask because I believe I'm seeing this issue and am anxious to work around it but can't find information about it anywhere I've looked.  Can you provide a link?

I misspoke, I should have said Kodi Chromebox wiki page (the one linked in my sig) rather than FAQ 

(2019-02-02, 20:41)Matt Devo Wrote:

(2019-02-02, 20:33)Rrrr Wrote: Hi Matt,

After years and years of happily using my CN60, I decided to upgrade Kodi and look for how this is done.
I went back to your original web pages and was gladly surprised you are still there!
Thank you so much for your years of amazing support on this.

Using EZ script, I wanted to install LE 9.0, but was offered LE 9.0 beta version (8.95.001) or 8.0 (Kodi 17.6).

I chose LE 9.0 beta, but the download failed to extract (twice). 
Downloading 8.0 worked fine, so that's what I have now.

Do you plan to upload 9.0 final version ?
Best,

  
I don't upload anything, my script just points to current LibreELEC release. I've just now updated it for the 9.0 release, so new installs should work, and you can of course upgrade manually as usual. There is a LAN performance bug in the kernel used for 9.0.0 (and the 8.9x betas) that needs to be worked around, info on the FAQ  

(2019-02-03, 16:55)Rrrr Wrote: I booted with CRTL-D then CTRL+ALT+F2
Downloading the E-Z script was not easy and required several tries:

curl: failed to connect to mrchromebox. tech port 443: Connection timed out

In the script I selected 2 for dual boot update.

After repartitioning and Updating bootloader, I get this:

Error: failed to download syslinux: check your internet connection and try again.

My internet connection seems fine. Is this the LAN bug or is your server offline?

I am unsure if I can reboot now and will have access again or if the repartitioning has damaged the boot process.

Info:
* ifconfig gives me the IP;
* SSH to IP fails. 

(2019-02-03, 18:15)Leclair Wrote: Hi everyone,

I have an ASUS CN60 that was previously setup in dual-boot mode (ChromeOS + LibreElec).

Two days ago, it froze on the Kodi Krypton screen. So I decided to factory reset and try updating to Matt's UEFI firmware and going standalone. 

At this point, I've used the LibreElec USB-CD Creator to write 'Generic x86_64' version of LibreElec to a USB.

With the USB in the Chromebox, it is not booting from USB. It keeps going to this screen:

If I press ESC before this screen it brings me to the Boot Options Settings. From there I can get to this screen:

I follow the onscreen instructions to install LibreElec to my Chromebox. Unfortunately, once I reboot, I'm back to the UEFI Interactive Shell v.2.2 screen.

I'm obviously doing something wrong. I've tried 3 different USB sticks in every different USB port on my Chromebox. Still nothing.

Thanks for any help you can provide.
 

---

 

(2019-02-03, 20:17)Matt Devo Wrote: If your internal drive is listed first and it's still dumping you to the EFI shell, means that booting from the internal drive is failing and it's falling over to the EFI shell 

(2019-02-03, 21:03)Leclair Wrote: Thanks Matt,

I followed your instructions and the Internal Hard Drive is listed first. Does that mean my internal drive is toast and maybe the reason it froze in the first place?

When the USB with LibreElec installer is plugged in, it will run and I can use Kodi. I don't know how to get it to install on the internal hard drive. 

(2019-02-03, 21:16)Matt Devo Wrote: Edit: just did a clean firmware flash + LibreELEC install on a Haswell Chromebox, and only issue was a hiccup on the first reboot where it still tried to boot the (now removed) USB.  What happens when you select the internal Hard Disk from the Boot Manager menu? 

(2019-02-03, 21:43)Leclair Wrote:

(2019-02-03, 21:16)Matt Devo Wrote: Edit: just did a clean firmware flash + LibreELEC install on a Haswell Chromebox, and only issue was a hiccup on the first reboot where it still tried to boot the (now removed) USB.  What happens when you select the internal Hard Disk from the Boot Manager menu? 

 It goes back to the main Boot Settings screen.  

(2019-02-03, 20:03)Matt Devo Wrote:

(2019-02-03, 16:55)Rrrr Wrote: I booted with CRTL-D then CTRL+ALT+F2
Downloading the E-Z script was not easy and required several tries:

curl: failed to connect to mrchromebox. tech port 443: Connection timed out

In the script I selected 2 for dual boot update.

After repartitioning and Updating bootloader, I get this:

Error: failed to download syslinux: check your internet connection and try again.

My internet connection seems fine. Is this the LAN bug or is your server offline?

I am unsure if I can reboot now and will have access again or if the repartitioning has damaged the boot process.

Info:
* ifconfig gives me the IP;
* SSH to IP fails. 

  
my server isn't showing any issues, can't really control the vast swath of internet between it and everyone else though.

the LAN issue affects Linux kernel 4.19+, so not ChromeOS.

rebooting would leave you in the same state you are now, You simply need to reinstall LE until it works   

(2019-02-04, 12:45)Rrrr Wrote: Loading ChromeOS
With 2 different USB memory keys and an SD card I did not manage to have CN60 ChromeOs recognise there is an O/S on the memory device upon insertion.
 

Quote:The next day back to EZ script
As per your reply, this time I managed to download LibreElec after selecting 2 for dual boot update:
LibreElec download complete: installing...
cp: error writing '/tmp/System/SYSTEM': No space left on device.

Please can you confirm what this means? My understanding is my partitions may be too small so I have to:
1. Perform a factory reset (I'll have to try again, any tips?);
2. Reinstall EZ script and run it again (is there another way?). 

(2019-02-04, 05:33)Matt Devo Wrote: can you manually boot from the internal SSD via Boot Maintenance Manager -> Boot From File -> <first SATA partition> -> EFI -> BOOT -> bootx64.efi ?

If not, that would indicate a bad install somehow - but you said the installer succeeds?

(2019-02-04, 19:35)Leclair Wrote: When I try that, there is nothing in the SATA partition. 

Quote:At first I thought the install succeeded, but I've now realized that it installed on the USB stick and is running from there. And every time I reboot, LibreElec re-installs on the USB and I start from scratch again. 

Quote:  I've tried with Ubuntu installer as well. Same thing happens. Runs from the USB stick. Tried with ChromeOS recovery, but it crashes every time, but I believe I read somewhere that ChromeOS wouldn't work anyway.

Quote:When I boot with the USB stick in, I get the screen that says to type 'live or run' or wait for installer to begin. I've done all 3 and the same thing happens every time. LibreElec installs and then runs from the USB. 

Quote:meaning no files/folders are listed? Then you're not installing to the internal drive

Quote: are you not selecting the internal storage as the install target?

(2019-02-04, 17:32)Matt Devo Wrote:

(2019-02-04, 12:45)Rrrr Wrote: Loading ChromeOS
With 2 different USB memory keys and an SD card I did not manage to have CN60 ChromeOs recognise there is an O/S on the memory device upon insertion.

Recovery Mode is just picky about USB media and port used, that's all there is to it.

Quote:The next day back to EZ script
As per your reply, this time I managed to download LibreElec after selecting 2 for dual boot update:
LibreElec download complete: installing...
cp: error writing '/tmp/System/SYSTEM': No space left on device.

Please can you confirm what this means? My understanding is my partitions may be too small so I have to:
1. Perform a factory reset (I'll have to try again, any tips?);
2. Reinstall EZ script and run it again (is there another way?). 

Quote:the error means what it says, not enough room for ChromeOS to download/extract the LibreELEC image before copying to the partitions set up for it. Whatever value you used for the LibreELEC partition last time, go 2GB less this time. You will have to do a factory reset (to reset the partitions to stock) and then re-run the EZ-setup script (resize them). I'm baffled as to why you are having some much trouble with this.