(2019-04-27, 00:07)TonyPh12345 Wrote: Heya, Matt!

Quick question. I’m replacing a CN60 with a CN65. Ive been dual booting to LibreELEC Leia on the former. Do you know if it’s safe to do a LibreELEC full backup from the CN60 and restore it on the 65, or are there hardware specific things in the original load that won’t work?

(2019-04-27, 00:14)Matt Devo Wrote:

(2019-04-27, 00:07)TonyPh12345 Wrote: Heya, Matt!

Quick question. I’m replacing a CN60 with a CN65. Ive been dual booting to LibreELEC Leia on the former. Do you know if it’s safe to do a LibreELEC full backup from the CN60 and restore it on the 65, or are there hardware specific things in the original load that won’t work?

 should be fine, though some settings may need adjustment after restoring. Do note that dual booting on the CN65 is currently broken due to something Google did in a recent firmware/OS update.

(2019-04-27, 00:20)TonyPh12345 Wrote: Yeah, I read up on that before I posted. I’m assuming that just a single-boot direct to Libre is the right choice in the setup script? I’m not too concerned about Chrome at this point... 

(2019-04-27, 01:13)Matt Devo Wrote:

(2019-04-27, 00:20)TonyPh12345 Wrote: Yeah, I read up on that before I posted. I’m assuming that just a single-boot direct to Libre is the right choice in the setup script? I’m not too concerned about Chrome at this point... 

it's what I'm running here

(2019-04-28, 23:10)TonyPh12345 Wrote: A separate but related question: Both of my CN60s were upgraded to latest LibreELEC (9.0.1) installed using your script, but about a month or six weeks apart. The first updated one suffers from the Ethernet performance issue (which I fixed according to the steps in the wiki, thank you!) but the more recently updated one (about 3 weeks ago?) does not. Is that because you integrated the PCI kernel boot option change into your script? They’re otherwise identical. Same hardware and same Libre version.

Quote:Also, neither of them seem to have an issue with dual boot, except for the fact they insist on repairing the file system when booting into Chrome mode. Is that the issue you refer to above? If so, I’ll probably live with that with no problem because the Dual Boot config (IMHO) is so much easier to manage and I am very afraid of the high likelihood of the recovery USB image getting lost in this household full of electronics (and kids).

...or is there a unique issue to the 65? 

(2019-04-30, 14:20)petecat1 Wrote: I have a new Asus Chromebox 3.  I loaded your Firmware Utility Script, selected the Install RW Legacy Firmware, then booted, selected Boot from USB, and it started to install FreePBX as usually occurs when I install it from this USB.  After the usual initial questions about versions etc, it started to load, and after a couple of lines went blank, and nothing further appeared to happen.
To see if it was my USB that was faulty, I tried installing Ubuntu from another USB and got:  graphics initialization failed      Error setting up gfxboot      boot:
Both of these USBs have worked recently on an older Chromebox.
Can I do anything about it?  ( I have not removed the WP screw yet...wanted to get through this part first, as I have done in the past.)

By the way, thanks for this great service.  A donation is on its way!

(2019-04-30, 16:16)Matt Devo Wrote:

(2019-04-30, 14:20)petecat1 Wrote: I have a new Asus Chromebox 3.  I loaded your Firmware Utility Script, selected the Install RW Legacy Firmware, then booted, selected Boot from USB, and it started to install FreePBX as usually occurs when I install it from this USB.  After the usual initial questions about versions etc, it started to load, and after a couple of lines went blank, and nothing further appeared to happen.
To see if it was my USB that was faulty, I tried installing Ubuntu from another USB and got:  graphics initialization failed      Error setting up gfxboot      boot:
Both of these USBs have worked recently on an older Chromebox.
Can I do anything about it?  ( I have not removed the WP screw yet...wanted to get through this part first, as I have done in the past.)

By the way, thanks for this great service.  A donation is on its way!

RW_LEGACY / Legacy Boot Mode is not currently working on the CN65 due to bug in Google's firmware, nothing I can do other than encourage people to file bug reports with Google 

(2019-05-01, 12:26)petecat1 Wrote: Wow.  Devastated.  And no other way to boot/install from USB at all?  Is that why it doesn't work to just do  sudo crossystem dev_boot_usb=1  ?  or  sudo crossystem dev_boot_legacy=1   ?   Which is what worked on the CN60, from memory... 

(2019-05-02, 03:31)Matt Devo Wrote:

(2019-05-01, 12:26)petecat1 Wrote: Wow.  Devastated.  And no other way to boot/install from USB at all?  Is that why it doesn't work to just do  sudo crossystem dev_boot_usb=1  ?  or  sudo crossystem dev_boot_legacy=1   ?   Which is what worked on the CN60, from memory... 

 you can boot/install from USB after flashing my UEFI Full ROM firmware, you just can't do it via Legacy Boot Mode / dual booting with ChromeOS.

dev_boot_usb has nothing to do with this. It simply enables booting ChromeOS/ChromiumOS from USB via CTRL+U.

dev_boot_legacy enables booting Legacy Boot Mode (CTRL+L), but also requires a valid legacy boot/RW_LEGACY firmware. LBM itself is completely broken/unusable on the CN65 (and all other 2018 Chromebox models). 

(2019-05-03, 01:55)petecat1 Wrote: That is superb, and has worked to get me up and running.  Can you point me to a solution to this:  It seems there might be an issue with the kernel on this distro: It is FreePBX (an Asterisk based distro) latest version SNG7 and runs on Centos 7.5 with kernel 3.10.0-862.2.3  ( I think that is the whole string)   I'm getting  Kernel panic - not syncing: Hard LOCKUP 
This version definitely works after installing using the Legacy Boot Mode on the CN60.  On this occasion, it ran through the installation process like usual, but on re-boot it locks up.
I can install and run Ubuntu 18.04 just fine, and can access the terminal from there.   Any help most appreciated. 

(2019-05-03, 05:21)Matt Devo Wrote:

(2019-05-03, 01:55)petecat1 Wrote: That is superb, and has worked to get me up and running.  Can you point me to a solution to this:  It seems there might be an issue with the kernel on this distro: It is FreePBX (an Asterisk based distro) latest version SNG7 and runs on Centos 7.5 with kernel 3.10.0-862.2.3  ( I think that is the whole string)   I'm getting  Kernel panic - not syncing: Hard LOCKUP 
This version definitely works after installing using the Legacy Boot Mode on the CN60.  On this occasion, it ran through the installation process like usual, but on re-boot it locks up.
I can install and run Ubuntu 18.04 just fine, and can access the terminal from there.   Any help most appreciated. 

 that's easy, the 3.10 kernel is simply too old / doesn't support the hardware. I wouldn't run anything below 4.14 or so on the CN65. 

(2019-05-06, 04:29)petecat1 Wrote: I can probably get a workaround by installing on older version of FreePBX via Ubuntu.  But my question is this:  If there is no option to restore the Stock Firmware via your script for this model (ie choosing option 9)....is there any way to re-load my backup of the ChromeOS and restore to the original state? 

(2019-05-06, 04:44)Matt Devo Wrote:

(2019-05-06, 04:29)petecat1 Wrote: I can probably get a workaround by installing on older version of FreePBX via Ubuntu.  But my question is this:  If there is no option to restore the Stock Firmware via your script for this model (ie choosing option 9)....is there any way to re-load my backup of the ChromeOS and restore to the original state? 

 You can absolutely restore the stock firmware (using a backup created by the script prior to flashing) via the script, I'm not sure why you would think that option is unavailable.  But I'm not sure why you would want to if you plan is to run Ubuntu 

(2019-05-11, 08:36)petecat1 Wrote: I get this in red text: Unfortunately I don't have a stock firmware available to download for 'FIZZ' at this time. 

Quote: You can absolutely restore the stock firmware (using a backup created by the script prior to flashing) via the script, I'm not sure why you would think that option is unavailable.  But I'm not sure why you would want to if you plan is to run Ubuntu