[Matt Devo]

Is the keyboard issue only for wireless keyboards or wired as well?

I wrote the OpenElec image to my SD card. When I put it in the Chromebox and turn the power on, it automatically brings me to the OpenElec Boot screen without pressing ESC. It asks to 1) run installer or 2) run live. I can't select anything on this screen. I've tried 2 wireless keyboards and 1 wired now, without any luck.

I'm assuming it's the keyboard, but just wanted to confirm before I go buy another one to test.


Thanks.

I've never seen the issue where a keyboard doesn't work in the OpenELEC installer. What model keyboards have you tried? For the wireless ones, if they have a power switch, have you tried toggling it off/on?

[lancastrian]

I'm experiencing an issue with my HP Chromebox (dual boot ChromeOS and OpenElec) where the portable hard drive (1TB Samsung M3) frequently disconnects when I try to copy new files to it, either in the Kodi file manager or via my phone or PC. This doesn't happen in normal use, e.g. reading files, only when writing. I'd say > 80% it will lose connection to the hard drive and require a restart. It's not a problem I've had when using the hard drive with my PC, but I couldn't rule out a fault with the hard drive itself. I've tried copying from other USB devices and from the Chomebox's SSD but it makes no difference.

Is this something anyone else has experienced or has a cause for? The only similar thing I've found when searching was someone whose Asus Chromebox was behaving similarly with a 1TB Seagate drive. Their theory was that it was a USB 3.0 issue and that using a USB 2.0 hub remedied the situation.

Has anyone got any thoughts on it? I'd ideally prefer to use USB 3.0, but if downgrading to USB 2.0 is going to fix it I'll guess I'll buy a USB 2.0 hub.

[Leclair]

Is the keyboard issue only for wireless keyboards or wired as well?

I wrote the OpenElec image to my SD card. When I put it in the Chromebox and turn the power on, it automatically brings me to the OpenElec Boot screen without pressing ESC. It asks to 1) run installer or 2) run live. I can't select anything on this screen. I've tried 2 wireless keyboards and 1 wired now, without any luck.

I'm assuming it's the keyboard, but just wanted to confirm before I go buy another one to test.


Thanks.

I've never seen the issue where a keyboard doesn't work in the OpenELEC installer. What model keyboards have you tried? For the wireless ones, if they have a power switch, have you tried toggling it off/on?

I've tried a Logitech K400r (wireless), an HP KBI (wireless), and a Onn HK2026 (cheap wired Walmart keyboard).

I did try toggling the power switch on the Logitech and pressing the "Connect" button on the HP to no avail.

When I originally set up my Chromebox with the dual-boot setup (Chrome OS + OpenElec), I used the HP keyboard and it worked fine.

I was trying to do a factory reset on my Chromebox by flashing the Chrome recovery media, but then realized that was the wrong thing to do.

I was doing all of this because I wanted to redo the dual-boot because I couldn't get into Chrome. I assumed I did something wrong because Ctrl-D wasn't working. Now I'm under the impression it was my keyboard the entire time.

I will be testing 2 more keyboards tonight, a wired Lenovo SK-8825 and a wireless Lenovo KBRF-3971. I will post the results.

[Arse4life]

Is the keyboard issue only for wireless keyboards or wired as well?

I wrote the OpenElec image to my SD card. When I put it in the Chromebox and turn the power on, it automatically brings me to the OpenElec Boot screen without pressing ESC. It asks to 1) run installer or 2) run live. I can't select anything on this screen. I've tried 2 wireless keyboards and 1 wired now, without any luck.

I'm assuming it's the keyboard, but just wanted to confirm before I go buy another one to test.


Thanks.

I've never seen the issue where a keyboard doesn't work in the OpenELEC installer. What model keyboards have you tried? For the wireless ones, if they have a power switch, have you tried toggling it off/on?

I've tried a Logitech K400r (wireless), an HP KBI (wireless), and a Onn HK2026 (cheap wired Walmart keyboard).

I did try toggling the power switch on the Logitech and pressing the "Connect" button on the HP to no avail.

When I originally set up my Chromebox with the dual-boot setup (Chrome OS + OpenElec), I used the HP keyboard and it worked fine.

I was trying to do a factory reset on my Chromebox by flashing the Chrome recovery media, but then realized that was the wrong thing to do.

I was doing all of this because I wanted to redo the dual-boot because I couldn't get into Chrome. I assumed I did something wrong because Ctrl-D wasn't working. Now I'm under the impression it was my keyboard the entire time.

I will be testing 2 more keyboards tonight, a wired Lenovo SK-8825 and a wireless Lenovo KBRF-3971. I will post the results.

I learned my lesson with a wireless keyboard. I bought a cheap $9 wired keyboard and no problems afterwards!

[jeffjoker]

Thanks a lot, this worked just fine with my chromebox !!
Just a quick question about coreboot (I installed in standalone mode, steps 5 and 6), is there a way to have it boot automatically upon power ?
I intend to shut it down between 2 usages for current saving and because the other devices on the same multi plug (don't want to have 2) will be powered off (using the plug switch).
I wanted the chromebox to boot auto when I switch on the multi plug.

Thanks and regards

[Matt Devo]

Thanks a lot, this worked just fine with my chromebox !!
Just a quick question about coreboot, is there a way to have it boot automatically upon power ?
I intend to shut it down between 2 usages for current saving and because the other devices on the same multi plug (don't want to have 2) will be powered off (using the plug switch).
I wanted the chromebox to boot auto when I switch on the multi plug.

Thanks and regards

you're in luck -- I actually just recently had a customer request this feature for a custom build. I have it working, but still deciding on how to implementi it to make it user selectable. PM me and I'll send you something to test

[Soli]

Matt:
Just read this at http://www.extremetech.com/computing/132...s-device/2

"Even though you’ll be in Ubuntu at this point, your device will still boot Chrome OS by default. To change the default boot OS, you can simply issue the command sudo cgpt add -i 6 -P 5 -S 1 /dev/sda to make Ubuntu the default, or sudo cgpt add -i 6 -P 0 -S 1 /dev/sda to make Chrome OS the default"
I guess -P is the partition, and -S the timeout.

Is this still the case? I don't see it mentioned in the wiki. I don't dual boot at this time, but I thought I might take a stab at it on my spare Chromebox. (ChromeOS is very Mom-friendly after all..) Might be a bit safer changing the default boot if you change your mind after the initial firmware flash, than having to reflash the firmware with some other defaults.

[Matt Devo]

That's for older ChromeOS devices without the legacy boot option - it's not relevant here. Changing the default boot for Haswell Chromeboxes is just as easy, but requires a different command (and the firmware write protect disabled); I just automate it in my script

[Byrdi]

I have got the following error:

Code:

***Error in check_disks: could not repair filesystem, dropping to debug shell, try to run 'fsck' manually: ***
    ### Starting debugging shell... type exit to quit ###
    sh: can't access tty; job control turned off
    #_

But after attemping to use fsck/dev/sda (6 and 7) as stated on the wiki
It said not found:

Code:

sh; fsck/dev/sda6: not found

Since then I have even tried to do all sda 1 through 16 still without any luck

Is there any way to fix this without doing a fresh install?
And how do I prevent it in the first place (heard something about shutdown/suspend settings but I didn't quite get it)

Thanks in advance

[mpednault]

Alright, this may have already been asked but...

The overview in the instructions on the wiki list removing the screw (disabling write protect) and then putting it in developer mode. The Matt lists those steps in opposite order. I'm getting my Chromebox today and am trying to be sure I know and understand the procedures before I get started.

[hdmkv]

From wiki:

System-->Settings-->Videos-->Acceleration: Enable HQ Scalers for scalings above:20%
System-->Settings-->Videos-->Acceleration: Use VC-1 VAAPI:Selected (de-select if you have interlaced VC-1 content)
System-->Settings-->Videos-->Acceleration: Prefer VAAPI render method:Selected

What does 20% for scalings do? Re: VC-1, with latest firmware/OE build, should one still deselect VC-1 VAAPI for 1080i (29.97) VC-1 content?

[Matt Devo]

But after attemping to use fsck/dev/sda (6 and 7) as stated on the wiki
It said not found:

Code:

sh; fsck/dev/sda6: not found

Since then I have even tried to do all sda 1 through 16 still without any luck

Is there any way to fix this without doing a fresh install?
And how do I prevent it in the first place (heard something about shutdown/suspend settings but I didn't quite get it)

you're missing the space between fsck and /dev/sda[#].
the issue is caused most often by an improper shutdown, it just wants you to run a filesystem check to ensure things are good before booting.

Alright, this may have already been asked but...

The overview in the instructions on the wiki list removing the screw (disabling write protect) and then putting it in developer mode. The Matt lists those steps in opposite order. I'm getting my Chromebox today and am trying to be sure I know and understand the procedures before I get started.

doesn't make a bit of difference. I've edited the OP to be in sync with the wiki (so, remove the screw first).

From wiki:

System-->Settings-->Videos-->Acceleration: Enable HQ Scalers for scalings above:20%
System-->Settings-->Videos-->Acceleration: Use VC-1 VAAPI:Selected (de-select if you have interlaced VC-1 content)
System-->Settings-->Videos-->Acceleration: Prefer VAAPI render method:Selected

What does 20% for scalings do? Re: VC-1, with latest firmware/OE build, should one still deselect VC-1 VAAPI for 1080i (29.97) VC-1 content?

it means that it will use HQ (CPU intensive) scaling algorithms when going from say 720p to 1080p, but not when say scaling a 1080p file based on video calibration / overscan compensation.

I'm not aware that interlaced VC-1 is fixed, so yes, deselect it still. This may change with Isengard, in which case I'll update the wiki.

[Byrdi]

you're missing the space between fsck and /dev/sda[#].
the issue is caused most often by an improper shutdown, it just wants you to run a filesystem check to ensure things are good before booting.

I feel so stupid. Thanks a lot though.
Also thanks in general for making such an easy way to install OpenELEC on my chromebox.
Keep up the good work.

[Leclair]

Is the keyboard issue only for wireless keyboards or wired as well?

I wrote the OpenElec image to my SD card. When I put it in the Chromebox and turn the power on, it automatically brings me to the OpenElec Boot screen without pressing ESC. It asks to 1) run installer or 2) run live. I can't select anything on this screen. I've tried 2 wireless keyboards and 1 wired now, without any luck.

I'm assuming it's the keyboard, but just wanted to confirm before I go buy another one to test.


Thanks.

I've never seen the issue where a keyboard doesn't work in the OpenELEC installer. What model keyboards have you tried? For the wireless ones, if they have a power switch, have you tried toggling it off/on?

I've tried a Logitech K400r (wireless), an HP KBI (wireless), and a Onn HK2026 (cheap wired Walmart keyboard).

I did try toggling the power switch on the Logitech and pressing the "Connect" button on the HP to no avail.

When I originally set up my Chromebox with the dual-boot setup (Chrome OS + OpenElec), I used the HP keyboard and it worked fine.

I was trying to do a factory reset on my Chromebox by flashing the Chrome recovery media, but then realized that was the wrong thing to do.

I was doing all of this because I wanted to redo the dual-boot because I couldn't get into Chrome. I assumed I did something wrong because Ctrl-D wasn't working. Now I'm under the impression it was my keyboard the entire time.

I will be testing 2 more keyboards tonight, a wired Lenovo SK-8825 and a wireless Lenovo KBRF-3971. I will post the results.

Neither of the Lenovo keyboards mentioned above work. So that's 5 keyboards tested so far. And the HP keyboard was previously used to install the dual-boot (ChromeOS + OpenElec) no problem.

Options?

[Matt Devo]

Neither of the Lenovo keyboards mentioned above work. So that's 5 keyboards tested so far. And the HP keyboard was previously used to install the dual-boot (ChromeOS + OpenElec) no problem.

Options?

I'd then guess that another connected USB device (possibly the USB install media) is causing an issue during the USB init/boot device iteration process