(2019-05-11, 19:20)MrBuyakah Wrote: Looks like the release of Libreelec 9.0.2 has fixed the ethernet performance issue.  I have removed the workaround from my Chromebox and getting ~27MBps to my local NAS.

(2019-05-11, 09:36)Matt Devo Wrote:

(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   

 relevant part of my quote emphasized 

(2019-05-12, 12:43)petecat1 Wrote: Sorry, but can I check...The Backup is created by the script prior to flashing, is that done automatically when I run the script, and if so, how do I access it later?  Or is it a step I needed to follow during the setup and now its too late to go back? 

(2019-05-12, 22:19)Matt Devo Wrote:

(2019-05-12, 12:43)petecat1 Wrote: Sorry, but can I check...The Backup is created by the script prior to flashing, is that done automatically when I run the script, and if so, how do I access it later?  Or is it a step I needed to follow during the setup and now its too late to go back? 

 the script prompts you to create a backup on USB when flashing the UEFI/Full ROM firmware. No backup is created or needed when using the RW_LEGACY firmware 

(2019-05-13, 12:30)petecat1 Wrote: I think I know the answer to this already but...If that backup was not created when flashing the UEFI/Full FOM firmware, then there is no way back?  Is there a hardware option?

(2019-05-13, 18:07)Matt Devo Wrote:

(2019-05-13, 12:30)petecat1 Wrote: I think I know the answer to this already but...If that backup was not created when flashing the UEFI/Full FOM firmware, then there is no way back?  Is there a hardware option?

there's always a way back, just need a firmware file to flash. For most devices, my script will provide an image extracted from the Recovery image for that device. But for some devices, Google uses a common firmware image and the Recovery process customizes it for the device - those I don't (yet) offer an image for. The 2018 Chromeboxes fall into that category unfortunately 

(2019-05-15, 13:08)petecat1 Wrote: So is that (Google's common firmware image) something I should be able to find and install?  I have the ChromeOS backup from the Chromebook Recovery Utililty, but I'm pretty sure thats no use to me until I get the BIOS back, right? 

(2019-05-15, 17:32)Matt Devo Wrote:

(2019-05-15, 13:08)petecat1 Wrote: So is that (Google's common firmware image) something I should be able to find and install?  I have the ChromeOS backup from the Chromebook Recovery Utililty, but I'm pretty sure thats no use to me until I get the BIOS back, right? 

the Recovery image is what gets downloaded/written to USB by the recovery tool (which you should not use until you actually need to restore ChromeOS. Restoring an older version can be very problematic). And yes, the Recovery media is not useful until you restore the stock firmware. There's nothing useful you can do with it at this time. If/when you actually want to revert back to stock, just PM me and I'll build you a custom stock firmware to flash back. Next time, listen to the script and make a backup ;-) 

(2019-05-18, 12:50)tredman Wrote: Is there any way to control the fan on the Chromebox? I'm currently running at cpu usage is 20% and 6% while watching iPlayer and the fan is very loud.

(2019-05-18, 18:37)Matt Devo Wrote:

(2019-05-18, 12:50)tredman Wrote: Is there any way to control the fan on the Chromebox? I'm currently running at cpu usage is 20% and 6% while watching iPlayer and the fan is very loud.

under a full Linux distro, the it87 kernel module (for the ITE IT87xxx series SuperIO chips) can be used (google 'it87 fan control').  Not aware of any option under LE.  I tweaked the fan profile so that it should be near silent under low CPU loads.  Perhaps your fan is simply going bad?

(2019-05-19, 10:58)tredman Wrote: Yes I suspect that too, the CB is quite old, must have had 3 or 4 years at least and as my tvh server it's always on  

(2019-05-11, 20:06)Matt Devo Wrote:

(2019-05-11, 19:20)MrBuyakah Wrote: Looks like the release of Libreelec 9.0.2 has fixed the ethernet performance issue.  I have removed the workaround from my Chromebox and getting ~27MBps to my local NAS.

yes, the 4.19.36 kernel includes a commit to (re)disable ASPM for the rt8169 driver, which fixes the issue

ref: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.19.36&id=1e4a7e7869acc57987d0e0b2ecf53b9a74fb911a