(2014-06-07, 03:57)blahfod Wrote: I think i might have a problem on my hands.

Got my chromebox home today and intended to install standalone openelec as per this thread.

what has happenned:

activated developer mode, removed write protect screw
booted the script as per the thread
ran the script to create a openelec install disk successfully
returned to the main menu
ran the script to create standalone coreboot installer firmware and created a back up of stock firmware, chrome box suggested a reboot, so i rebooted, and now nothing boots.
I can't get any boot menu, no matter what usb stick i have inserted, nothing boots, i press escape and no menu comes up, i have tried the recovery procedure (paprer clip and reboot) and still nothing shows up? i followed the script to a letter, what has happened? and how to a get something to boot to start this over again?

thanks in advance
blahfod

(2014-06-07, 05:45)Matt Devo Wrote:

(2014-06-07, 03:57)blahfod Wrote: I think i might have a problem on my hands.

Got my chromebox home today and intended to install standalone openelec as per this thread.

what has happenned:

activated developer mode, removed write protect screw
booted the script as per the thread
ran the script to create a openelec install disk successfully
returned to the main menu
ran the script to create standalone coreboot installer firmware and created a back up of stock firmware, chrome box suggested a reboot, so i rebooted, and now nothing boots.
I can't get any boot menu, no matter what usb stick i have inserted, nothing boots, i press escape and no menu comes up, i have tried the recovery procedure (paprer clip and reboot) and still nothing shows up? i followed the script to a letter, what has happened? and how to a get something to boot to start this over again?

thanks in advance
blahfod

are you connecting to a TV or monitor? It seems that the resolution used on the SeaBIOS boot screen is not one that all TVs can handle. You can always try blindly selecting your USB installer by pressing [ESC] then [2] and seeing if the installer screen comes up. You might have to play with the timing though. I just reset / reflashed both my i3 and celeron ChromeBoxes here to make sure everything is ok with the files/script, and it appears to be.

(2014-06-06, 05:42)Netix Wrote:

(2014-06-06, 05:40)mdumont1 Wrote:

(2014-06-05, 19:27)Netix Wrote: I have overscan problem in Ubuntu and with the Chromebox itself. In ChromeOS, I can fix the overscan issue with the built-in tools but not in Ubuntu. My 2009 50inch panasonic plasma tv is the problem there's no option to turn off overscan on that tv. I think I will get overscan issue with chromium since it doesn't keep the xbmc settings but goes fullscreen :/

I have this same issue but luckily XBMC (and thus OpenELEC) has the ability to calibrate the screen similarly to how ChromeOS does to compensate for the overscan. Check http://wiki.xbmc.org/index.php?title=Settings/System#Video_calibration...

I know that I can fix the overscan issue within XBMC but can you try the chromium browser to see what happen?

(2014-06-07, 06:07)rampagewsu Wrote: Created an account just to comment on this. I had the same problem as blahfod...exact same.

I blind booted, escape, then 2 and voila! It worked. I'm using a hdmi to DVI cable on a POS 1680x1050 monitor for reference.

Thanks Matt! You saved my night.

(2014-06-07, 06:29)blahfod Wrote: Thanks Matt,

you are the best!!!

(2014-06-07, 06:49)mdumont1 Wrote:

(2014-06-06, 05:42)Netix Wrote:

(2014-06-06, 05:40)mdumont1 Wrote: I have this same issue but luckily XBMC (and thus OpenELEC) has the ability to calibrate the screen similarly to how ChromeOS does to compensate for the overscan. Check http://wiki.xbmc.org/index.php?title=Settings/System#Video_calibration...

I know that I can fix the overscan issue within XBMC but can you try the chromium browser to see what happen?

I tried the Chromium browser in OpenELEC with the overscan settings set in XBMC and unfortunately the overscan is still there for the browser.

You may want to try playing the xrandr --transform option in Ubuntu to see if you can adjust the picture to compensate for the overscan.

(2014-06-07, 12:58)Netix Wrote: Thx for the feedback. Tried a bunch of thing in Ubuntu. Xrandr transform only fix it a bit and xrandr custom resolution doesn't work, screen goes black and I have to revert back to the supported one :/

With the Xrandr transform if I set it up to apply at boot it's messing up my xbmc video calibration so..

(2014-06-07, 06:07)rampagewsu Wrote:

(2014-06-07, 05:45)Matt Devo Wrote:

(2014-06-07, 03:57)blahfod Wrote: I think i might have a problem on my hands.

Got my chromebox home today and intended to install standalone openelec as per this thread.

what has happenned:

activated developer mode, removed write protect screw
booted the script as per the thread
ran the script to create a openelec install disk successfully
returned to the main menu
ran the script to create standalone coreboot installer firmware and created a back up of stock firmware, chrome box suggested a reboot, so i rebooted, and now nothing boots.
I can't get any boot menu, no matter what usb stick i have inserted, nothing boots, i press escape and no menu comes up, i have tried the recovery procedure (paprer clip and reboot) and still nothing shows up? i followed the script to a letter, what has happened? and how to a get something to boot to start this over again?

thanks in advance
blahfod

are you connecting to a TV or monitor? It seems that the resolution used on the SeaBIOS boot screen is not one that all TVs can handle. You can always try blindly selecting your USB installer by pressing [ESC] then [2] and seeing if the installer screen comes up. You might have to play with the timing though. I just reset / reflashed both my i3 and celeron ChromeBoxes here to make sure everything is ok with the files/script, and it appears to be.

Created an account just to comment on this. I had the same problem as blahfod...exact same.

I blind booted, escape, then 2 and voila! It worked. I'm using a hdmi to DVI cable on a POS 1680x1050 monitor for reference.

Thanks Matt! You saved my night.

(2014-06-07, 12:58)Netix Wrote:

(2014-06-07, 06:49)mdumont1 Wrote:

(2014-06-06, 05:42)Netix Wrote: I know that I can fix the overscan issue within XBMC but can you try the chromium browser to see what happen?

I tried the Chromium browser in OpenELEC with the overscan settings set in XBMC and unfortunately the overscan is still there for the browser.

You may want to try playing the xrandr --transform option in Ubuntu to see if you can adjust the picture to compensate for the overscan.

Thx for the feedback. Tried a bunch of thing in Ubuntu. Xrandr transform only fix it a bit and xrandr custom resolution doesn't work, screen goes black and I have to revert back to the supported one :/

With the Xrandr transform if I set it up to apply at boot it's messing up my xbmc video calibration so..

(2014-06-07, 16:45)Matt Devo Wrote:

(2014-06-07, 12:58)Netix Wrote: Thx for the feedback. Tried a bunch of thing in Ubuntu. Xrandr transform only fix it a bit and xrandr custom resolution doesn't work, screen goes black and I have to revert back to the supported one :/

With the Xrandr transform if I set it up to apply at boot it's messing up my xbmc video calibration so..

that's because XBMC is applying its corrections on top of the R&R transform. You need to set R&R first, then recalibrate XBMC.

(2014-06-07, 18:07)jsp1 Wrote:

(2014-06-07, 12:58)Netix Wrote:

(2014-06-07, 06:49)mdumont1 Wrote: I tried the Chromium browser in OpenELEC with the overscan settings set in XBMC and unfortunately the overscan is still there for the browser.

You may want to try playing the xrandr --transform option in Ubuntu to see if you can adjust the picture to compensate for the overscan.

Thx for the feedback. Tried a bunch of thing in Ubuntu. Xrandr transform only fix it a bit and xrandr custom resolution doesn't work, screen goes black and I have to revert back to the supported one :/

With the Xrandr transform if I set it up to apply at boot it's messing up my xbmc video calibration so..

Have you considered using the display port with an adapter for vga? Assuming your television has vga inputs this would be the most likely route to achieve native resolution and alleviate the problem altogether. Of course you would need another way to pull audio, maybe through the hdmi if you use a receiver. I have an older LCD with pc type resolution (currently serving bedroom duty) and it only works without overscan by inputting a vga signal. Just a thought, not sure if it is applicable in your case...maybe try it with a different pc before investing in an adapter.

(2014-06-07, 18:12)Netix Wrote:

(2014-06-07, 16:45)Matt Devo Wrote:

(2014-06-07, 12:58)Netix Wrote: Thx for the feedback. Tried a bunch of thing in Ubuntu. Xrandr transform only fix it a bit and xrandr custom resolution doesn't work, screen goes black and I have to revert back to the supported one :/

With the Xrandr transform if I set it up to apply at boot it's messing up my xbmc video calibration so..

that's because XBMC is applying its corrections on top of the R&R transform. You need to set R&R first, then recalibrate XBMC.

Well if I set the Xrandr transform to apply at boot, it take around ~2sec to switch from the native resolution to the fixed resolution therefore messing my xbmc config because even If I set it after the R&R transform, it resets every time I reboot.

Don't know If I'm able to explain myself correctly (english is my second language) :/

(2014-06-07, 18:07)jsp1 Wrote:

(2014-06-07, 12:58)Netix Wrote: Thx for the feedback. Tried a bunch of thing in Ubuntu. Xrandr transform only fix it a bit and xrandr custom resolution doesn't work, screen goes black and I have to revert back to the supported one :/

With the Xrandr transform if I set it up to apply at boot it's messing up my xbmc video calibration so..

Have you considered using the display port with an adapter for vga? Assuming your television has vga inputs this would be the most likely route to achieve native resolution and alleviate the problem altogether. Of course you would need another way to pull audio, maybe through the hdmi if you use a receiver. I have an older LCD with pc type resolution (currently serving bedroom duty) and it only works without overscan by inputting a vga signal. Just a thought, not sure if it is applicable in your case...maybe try it with a different pc before investing in an adapter.

No VGA inputs on my tv but I do have a S-Video, think I could use that ?

(2014-06-06, 06:39)Veronica Wrote:

(2014-06-05, 06:35)Netix Wrote:

(2014-06-05, 06:24)jsp1 Wrote: Chromium browser runs in OE, I can't confirm flash support though....sorry.

Thank you. I was wondering because I'm having some issue with Ubuntu.

I'm currently running Ubuntu 14.04 with the new coreboot. Everything ran fine for 6 days and now after plugin in a Flirc, I'm having the freezing issue again. Also, since I've updated the coreboot I can't set XBMC to sleep after a certain time because when I wake it up there's no more sound coming out. When I go in sounds setting in Ubuntu there's no device appearing beneath output, I have to hard reboot to make it work again.

And the same stupid overscan problem I'm having since the beginning (Stupid old panasonic tv that can't turn off overscan) make me unable to use the web browser to watch anything. I've tried to ask on ubuntu forum but no luck : http://ubuntuforums.org/showthread.php?t=2226141

I have the same setup, what Ubuntu kernel are you using? Also did you try the flirc fix matt posted: http://ubuntuforums.org/showthread.php?t=2203116&p=13007838#post13007838
I don't own flirc and not sure if in the latest 3.14.x kernel the fix is already there but give it a try. I have kernel 3.14.04 and after 4 , 5 reboots xbmc freeze is almost gone and plex crash is gone.
What settings do you have to not make it freeze?

@matt could you explain better what does this mean if you can:

Quote: Just some obersvations:

I agree with Chris, this is a context restore.

IPEHR: 0x780c0000 => 3DSTATE_VF

We have several mesa bugs with this as the IPEHR (according to Ken)

3DSTATE_VF is the last state loaded (other than the resource streamer).

Is about the freezing issue some of us is experiencing. I have a log too but is a bit more of 3mb and it doesn't let me upload it in the BUG tracker, I'll have to get a new log or post the pastebin link in here.