[Matt Devo]

Try disabling the automatic refresh rate adjustment and see if the problem persists

[teki4u]

Thanks, I'll try the patches and confirm if it resolves the issue.

Please post the packages to download IF you compile it and IF it works. Would be great if you can do 3.19 and 4.3+

[loki05]

Hey guys,

I just recently updated to the latest Openelec build (v6.0) using the openelec dev addon.....all is well, but when trying to launch chromium browser...nothing happens. I tried uninstalling the addon and reinstalling it...same nothing. anyone know if it stopped on this release? or any advice? thx!

[Grumpyman]

Try disabling the automatic refresh rate adjustment and see if the problem persists

Thanks Matt

That worked

[onyx00]

Having issues here as well - was running without issue on 5.x and then upgraded and now menus and other on-screen displays hang. If I try to bring up a menu or even the pop-up that says "Working" comes up, the video keeps playing but the menu/etc. remains and you cannot exit out of it.

Will post a debug log soon as I get a chance but wanted to post in case others had the same issue and thought they might be "crazy."

[nickr]

@onyx00 I solved that by renaming guisettings.xml and redoing all my config.

[Matt Devo]

script update 2015-11-30:

- Update coreboot to latest upstream commit
- Update SeaBIOS to version 1.9.0
- Add support for the Broadwell-based Asus ChromeBox CN62 (all CPU/GPU options)

[InfoJunky]

pop-up that says "Working" comes up, the video keeps playing

After manually updating to the "64-6.0.98-fritsch" build suggested in the wiki, I'm experiencing a similar (maybe) issue.

About half the time when I start playing a movie, I get the small pop-up that says "Working" with the spinning circle and it freezes. The movie continues to play,
but the box becomes unresponsive from remote input and the pop-up remains for about 5 minutes.

It eventually goes away and the box becomes responsive again. The video is not affected.

[Matt Devo]

After manually updating to the "64-6.0.98-fritsch" build suggested in the wiki, I'm experiencing a similar (maybe) issue.

About half the time when I start playing a movie, I get the small pop-up that says "Working" with the spinning circle and it freezes. The movie continues to play,
but the box becomes unresponsive from remote input and the pop-up remains for about 5 minutes.

It eventually goes away and the box becomes responsive again. The video is not affected.

I'm unable to reproduce this here. Is this on an upgrade from 5.0.8? Where is your content located? If a network location, does the issue occur with local content (or connected USB) as well?

[bobandy]

Since the ethernet MAC address is stored in the firmware, if you are setting up multiple ChromeBoxes, you need to do a firmware backup for each, since restoring the same backup to multiple boxes will result in them having the same MAC address, and cause serious network issues.

How does coreboot get the mac address if you're flashing over the stock firmware which it's contained in? Is it possible to manually change the MAC address in the custom coreboot firmware? Basically Im replacing some older boxes with these to save space/power for a lab setup and would like to change them to the already spoofed mac addresses our local network policies are configured with. I could spoof in software after OS boot but this would be a more elegant solution. I understand this would be a fringe issue that's way outside the scope of this walk-through, but I figured the worst you could say was "that's a waste of my time" (and completely understandable). Any insight over this would be greatly appreciated.

Finally, a giant thank you to the team for y'alls work.

[Matt Devo]

How does coreboot get the mac address if you're flashing over the stock firmware which it's contained in? Is it possible to manually change the MAC address in the custom coreboot firmware? Basically Im replacing some older boxes with these to save space/power for a lab setup and would like to change them to the already spoofed mac addresses our local network policies are configured with. I could spoof in software after OS boot but this would be a more elegant solution. I understand this would be a fringe issue that's way outside the scope of this walk-through, but I figured the worst you could say was "that's a waste of my time" (and completely understandable). Any insight over this would be greatly appreciated.

Finally, a giant thank you to the team for y'alls work.

in the stock firmware, the MAC address is stored in a 4kb fixed-size/fixed location section called the VPD, vital product data. I read and store the VPD section into a file, vpd.bin, which I then add vpd.bin to the custom coreboot firmware file which the script downloads prior to flashing. If you have a ChromeBox already running my custom firmware, the easiest way to change the MAC address in firmware is to read the firmware from flash into a file, search for and hex-edit the MAC string, and write it back.

If this is something you need/would like to have scripted/automated for your particular use, shoot me an email at [email protected] to discuss further.

[InfoJunky]

I'm unable to reproduce this here. Is this on an upgrade from 5.0.8? Where is your content located? If a network location, does the issue occur with local content (or connected USB) as well?

Yes I believe I upgraded from 5.0.8. It had been working flawlessly for me.

My content is located on a few external drives plugged into a raspberry pi B+, wired to my network, and shared up via Samba.

I haven't tried playing any local content, but I'll give it a go once I have time to fight my family off of the TV.

Thank you Sir, for your prompt response.

Sláinte

[pvagner]

I'm on celeron based HP Chromebox. I am slowly searching in the thread trying to find an answer to a simple question. I would like to dual boot chrome OS and Arch linux. I have completed the device preparation i.e. removed write protect screw, put my device into developer mode, ran the first stage of EZ setup script. I have selected option 1 to dual boot ubuntu. This is what the generic linux instructions advise. Now I do have arch linux image written to an USB key, I can see its boot however it can't fully load. I am not able to copy and paste the output however it prints a lot of kernel modules and it won't continue booting.
Do I need to redo the setup selecting open elec and then try to boot arch linux again or is there something else I can do in order to successfully boot install image of arch linux?
I am connecting my Chromebox into an older Grundig TV.

[Matt Devo]

I'm on celeron based HP Chromebox. I am slowly searching in the thread trying to find an answer to a simple question. I would like to dual boot chrome OS and Arch linux. I have completed the device preparation i.e. removed write protect screw, put my device into developer mode, ran the first stage of EZ setup script. I have selected option 1 to dual boot ubuntu. This is what the generic linux instructions advise. Now I do have arch linux image written to an USB key, I can see its boot however it can't fully load. I am not able to copy and paste the output however it prints a lot of kernel modules and it won't continue booting.
Do I need to redo the setup selecting open elec and then try to boot arch linux again or is there something else I can do in order to successfully boot install image of arch linux?
I am connecting my Chromebox into an older Grundig TV.

no, you're on the right path. If you didn't boot ChromeOS after running the first stage of the dual boot setup, you need to do that, since that's what actually resizes the partitions. Then, re-run the EZ setup script and update the legacy BIOS. Finally, reboot into legacy mode and install arch using the instructions on their wiki: https://wiki.archlinux.org/index.php/Chr..._Chrome_OS. You can skip the part where you run the ChrUbuntu script to repartition since my script does the same thing.

[pvagner]

I've already booted chrome OS and the partition sizes are okay.
I think I am running your latest seabios at least it indicates so when pressing ctrl+l on the boot screen.
Should I run EZ setup script again to update the seabios or can I just try booting arch from USB?
I have read the wiki article you have pointed me to and I think I have found nothing new for me in there.
What I'm doing:
0) power off chromebox,
1) insert the USB drive,
2) Power on Chromebook,
3) When the boot screen appears I press ctrl+l
4) As the seabios screen appears I press ESC
5) I press number 2 on the keyboard
6) Arch boot promp comes up, the unit beeps and I can choose to boot 64 or 32 bit build.
7) I press the enter key to accept the default which should boot 64 bit.
8) After a little while I realize the text on the screen no longer scrols displaying new stuff and a few bottom lines only contain listing various kernel modules.
9) I've tried to wait long while e.g. two hours in this state but nothing has changed so definatelly something is going wrong.
I am booting october 2015 image. I will try some older images just in case this one is screwed somehow but I believe I am doing it right.