(2015-03-29, 21:28)Matt Devo Wrote: [ -> ] (2015-03-29, 21:23)fma965 Wrote: [ -> ]"- add script option for USB boot default for standalone firmware"
How would i run the script from a standalone firmware? just use chromium? great work.
yeah, or pretty much any non-OE linux
OK thanks.
(2015-03-29, 18:45)Matt Devo Wrote: [ -> ] (2015-03-29, 16:50)movie78 Wrote: [ -> ]Chromebox Issue
Images get blurry when it is a fast paced action movie
I have a video with FPS and motion bars test
Please help me if you can..
Thanks!
Chromebox FPS Motion bar test
almost certain that's not a chromebox issue, it's an issue with your TV's video processing. How about a link to the source video so others can test/confirm?
Here is the Test files i used.
Motion Test files
I get "You already have the latest firmware (20150226)" when i run the firmware update script but i know that that is not the latest firmware released by Matt. Anyone can help me?
(2015-03-29, 17:36)zagor64 Wrote: [ -> ]I have an older TV (Samsung HLT-6187S circa 2008) and have been using xbmc/kodi for years using a windows based HTPC. Never had an issue with HDMI handshake. I recently switched over to openelec since I replaced my HTPC with the Asus chromebox. Both my older HTPC and the chromebox have HDMI handshake issues with my TV now that openelec is installed on both of them. When switching input to the chromebox/htpc all I get on the screen is a switching between a pink screen and a snow static screen. The TV senses that there is a signal because other wise it wouldn't allow switching to that input. Changing inputs to another input and them back does not help however, turning the TV off and then back on fixes the problem until the next time. Unplugging the HDMI cable and plugging it back in also fixes the issue. I rather not have to turn the tv on and off or unplug/replug the HDMI cable every time I want to use kodi especially with the WAF being an issue. Any ideas on how to fix this issue?
Yes, I had similar problems and compiled a kernel using
drm-intel-nightly and I no longer have handshake issues.
It seems these fixes are destined for kernel version 4.1.
(2015-03-30, 16:24)valeron94 Wrote: [ -> ]I get "You already have the latest firmware (20150226)" when i run the firmware update script but i know that that is not the latest firmware released by Matt. Anyone can help me?
The last entry in the change log (post #1 in this thread) about a new firmware version is on 20150226:
------------------------------------------------------------------
2015-02-26 -- v3.13
------------------------------------------------------------------
- synchronized coreboot and SeaBIOS to latest upstream codebases
So I have no idea what you're talking about.
(2015-03-30, 16:44)naloj Wrote: [ -> ] (2015-03-30, 16:24)valeron94 Wrote: [ -> ]I get "You already have the latest firmware (20150226)" when i run the firmware update script but i know that that is not the latest firmware released by Matt. Anyone can help me?
The last entry in the change log (post #1 in this thread) about a new firmware version is on 20150226:
------------------------------------------------------------------
2015-02-26 -- v3.13
------------------------------------------------------------------
- synchronized coreboot and SeaBIOS to latest upstream codebases
So I have no idea what you're talking about.
Latest release as of today is 2015-03-29 -- v3.16, while i have the 2015-02-26 -- v3.13 but this time the update script doesn't succeed to update the firmare on my chromebox (I've already updated it several times)
(2015-03-30, 17:43)valeron94 Wrote: [ -> ]Latest release as of today is 2015-03-29 -- v3.16, while i have the 2015-02-26 -- v3.13 but this time the update script doesn't succeed to update the firmare on my chromebox (I've already updated it several times)
you don't have v3.13 of anything; you have the latest firmware version, which is 2015-02-26 as per the changelog. The firmware isn't updated every time the script is -- only when needed.
You seem to think every script update includes a firmware update, which it does not.
Ah ok, now i get it. Thank you and keep the good work going
sorry guys about this question i'm about to ask.....I am running asus chromebox with openelec standalone for the past year i would say and love it. I've updated to the latest openelec 5.07 and really having no issues. Do you recommend I should update the coreboot or anything regarding this firmware/script? Also, since i"m in stand alone, is there a way to get to command line and run update script if needed? i tried the ctrl alt f2, and the screen just goes blank. Many thanks, love this damn thing.
(2015-03-30, 20:39)loki05 Wrote: [ -> ]sorry guys about this question i'm about to ask.....I am running asus chromebox with openelec standalone for the past year i would say and love it. I've updated to the latest openelec 5.07 and really having no issues. Do you recommend I should update the coreboot or anything regarding this firmware/script? Also, since i"m in stand alone, is there a way to get to command line and run update script if needed? i tried the ctrl alt f2, and the screen just goes blank. Many thanks, love this damn thing.
in first page
Quote:Updating the coreboot Firmware (standalone)
-------------------------------------------------------------
As of version 3.0 of the script, you can simply re-download/re-run the script under any Linux distro with a full bash shell. The dual-boot related options will be disabled, but the Standalone Setup / coreboot firmware update option will be available.
If you are running a Linux distro which does not have a full bash shell, such as OpenELEC, you should use my standalone firmware updater script from an SSH terminal. This script is only intended to update a ChromeBox already running my custom coreboot firmware (via the EZ setup script), and will not work under ChromeOS/ChromiumOS.
Code:
curl -L -O http://goo.gl/HSZer4
bash HSZer4
Note: the bash command will require using the 'sudo' prefix if not running OpenELEC (since with OE, you are always logged in as the root user). Additionally, this script must be run immediately after booting, otherwise it may fail to detect the current firmware version.
First off thanks Matt for all your hard work. I have 4 Chromeboxes (all OE Standalone) and they all work great but the one that is connected to an older 720p Samsung LCD TV. This Chromebox turns on to either an all black screen or a screen that flashes green and black if the correct HDMI input isn't selected before turning the Chromebox on. Since the HDMI input doesn't show up in the input options of my TV until the Chromebox is turned on, the only way for me to get the Chromebox to work is to switch HDMI inputs with my digital cable box, then power the Chromebox on once my TV is on the proper input. If I do that, it boots up perfectly.
I think I may try to buy an HDMI switch so I don't have to change inputs and see if that works but was wondering if anyone else has found another solution to this problem. Also, it's definitely not the Chromebox because when I plug it into a different 1080p TV, it works perfectly.
something has gone weird with my chromebox - not sure if it was a bodged update but it was ok this morning, then it crashed so I power cycled it, and now it wont boot - just get the bootloader text, then a moving cursor that goes across the screen line by line - nothing loads no matter how long I leave it.
I think its just openelec has screwed up, so I am ok to reinstall it - but whats the best openelec boot image to use to reinstall the thing - just fromt he official site and a generic x86 build?
(2015-03-30, 20:39)loki05 Wrote: [ -> ]sorry guys about this question i'm about to ask.....I am running asus chromebox with openelec standalone for the past year i would say and love it. I've updated to the latest openelec 5.07 and really having no issues. Do you recommend I should update the coreboot or anything regarding this firmware/script? Also, since i"m in stand alone, is there a way to get to command line and run update script if needed? i tried the ctrl alt f2, and the screen just goes blank. Many thanks, love this damn thing.
I don't recommend updating if everything is working well. As much as I test each update, there's no guarantee that it will work better (or won't break something) with your particular hardware, so there's no reason to risk it.
(2015-03-30, 21:21)kcallawa Wrote: [ -> ]First off thanks Matt for all your hard work. I have 4 Chromeboxes (all OE Standalone) and they all work great but the one that is connected to an older 720p Samsung LCD TV. This Chromebox turns on to either an all black screen or a screen that flashes green and black if the correct HDMI input isn't selected before turning the Chromebox on. Since the HDMI input doesn't show up in the input options of my TV until the Chromebox is turned on, the only way for me to get the Chromebox to work is to switch HDMI inputs with my digital cable box, then power the Chromebox on once my TV is on the proper input. If I do that, it boots up perfectly.
I think I may try to buy an HDMI switch so I don't have to change inputs and see if that works but was wondering if anyone else has found another solution to this problem. Also, it's definitely not the Chromebox because when I plug it into a different 1080p TV, it works perfectly.
easiest workaround would be to use a script to toggle the video output off, wait ~5s (or however long it takes your TV to switch to the correct input), then turn the video output back on. If we're talking about powering on from fully off, then use an autostart script; if from suspend/resume, then you can modify the existing suspend script in the wiki (for toggling audio on resume from suspend).
(2015-03-30, 21:35)bob808 Wrote: [ -> ]something has gone weird with my chromebox - not sure if it was a bodged update but it was ok this morning, then it crashed so I power cycled it, and now it wont boot - just get the bootloader text, then a moving cursor that goes across the screen line by line - nothing loads no matter how long I leave it.
I think its just openelec has screwed up, so I am ok to reinstall it - but whats the best openelec boot image to use to reinstall the thing - just fromt he official site and a generic x86 build?
the standard generic x86_64 (diskimage version)
Thanks Matt for the quick reply. That sounds like it's above my knowledge level so I guess I will just buy an HDMI switch and see how that works out.