[m0ngr31]

Got my Chromebox setup yesterday with this script! It's brilliant, thanks a ton for making it! My only suggestion so far would be for it to have an extra option to download XBMC only instead of all the other desktops so it'd just boot into that.

Other than that, it's been great. It's locked up a few times, but if it happens again, I'll post some logs. Also, is the processor supposed to be hitting 70%/20% at all times when it's just sitting there?

If you want something that boots directly into XBMC, OpenELEC is the easiest solution; otherwise, you're on your own.

If you're dual booting Ubuntu and only have a single 2GB stick of RAM, and haven't manually updated the kernel, then yeah there are some CPU usage issues, as noted in the wiki.

Ok, good to know. I'm running it for some other server stuff besides XBMC, so that's why I was using Ubuntu. If OpenELEC is built on Ubuntu or something, maybe I'll just use that...

EDIT
Just looked at OpenELEC. Definitely not built on Ubuntu, I'll stick with what I've got now and just order another stick of RAM.

[Stereodude]

yeah, I don't think it's ever completely silent, but the HP could be using a different fan. Care to take it apart and snap a pic?

I guess I could. It was a bit of a pain to open up to remove the write protect screw though. I should probably also point out I have rather sensitive hearing.

define "worked" - there's only a limited number of situations where you can make a direct comparison between the two. Are we talking at the SeaBIOS boot menu? in a specific OS?

Yes, at the boot menu. Pressing 1 or 2 with it doesn't work with Coreboot. However, I could CTRL+D or CTRL+U with it when it had the stock SeaBIOS. The Lenovo keyboard/mouse work fine in OpenELEC once its running.

[Matt Devo]

Yes, at the boot menu. Pressing 1 or 2 with it doesn't work with Coreboot. However, I could CTRL+D or CTRL+U with it when it had the stock SeaBIOS. The Lenovo keyboard/mouse work fine in OpenELEC once its running.

those are two completely different "stages" of booting, so not directly comparable. Some wireless USB kb/mouse require a bit of extra setup, which is not done by coreboot/SeaBIOS. I assume it doesn't work to hit ESC to bring up the boot menu either.

[Stereodude]

I assume it doesn't work to hit ESC to bring up the boot menu either.

From memory I think that's correct. Once I got OpenELEC installed to the internal SSD I haven't been trying it. I know I needed a real wired USB keyboard to boot from a USB device to install or update OpenELEC.

[Matt Devo]

From memory I think that's correct. Once I got OpenELEC installed to the internal SSD I haven't been trying it. I know I needed a real wired USB keyboard to boot from a USB device to install or update OpenELEC.

updating openelec doesn't require USB booting, just a network file copy and reboot

[Stereodude]

updating openelec doesn't require USB booting, just a network file copy and reboot

Hmm... Well, I got a special test build from sraue to fix a crashing issue and wasn't sure how to install it other than put it on a USB stick and do a repair/update install. I'm pretty darn new to XBMC/Kodi and OpenELEC. I certainly don't know all the ins and outs yet.

[Matt Devo]

Hmm... Well, I got a special test build from sraue to fix a crashing issue and wasn't sure how to install it other than put it on a USB stick and do a repair/update install. I'm pretty darn new to XBMC/Kodi and OpenELEC. I certainly don't know all the ins and outs yet.

there's these wonderful things called wikis that have lots of useful information on them, including, in this case, how to update

[Stereodude]

there's these wonderful things called wikis that have lots of useful information on them, including, in this case, how to update

Who knew...

[Stereodude]

Matt, is there any way to force the fan speed from a SSH session (or similar) so I can listen to the fan to figure out what fan speeds I want without having to build & reflash the firmware over and over?

[Matt Devo]

Matt, is there any way to force the fan speed from a SSH session (or similar) so I can listen to the fan to figure out what fan speeds I want without having to build & reflash the firmware over and over?

not to my knowledge

[mit-s2k]

Hi Matt,

Just got my box, and your script has helped a lot. Initially I dual booted ChromeOS and Ubuntu, which worked well and was a lot of fun to play around with. Now I'm attempting to install Windows 8.

I first tried to install it after I used your script to dual boot ChromeOS and Ubuntu. I rebooted, entered legacy boot (Ctrl-L), and then hit Esc to go into SeaBIOS's boot menu and select USB boot. I then proceeded to install Windows on the whole disk (deleting all other partitions using the Windows' installer partition tool). It seemed to install successfully, copying over all the files, until it rebooted. Then I did Ctrl-L and selected boot from disc (SSD) and then Windows showed a Windows 8 BSOD (a face) and reported the error "Page Fault in a Non Paged Area" (underscores in between, don't know exact formatting). In the same line, it looked like it said something about "Display" also -- could not read it, it was too blurry. After an automatic restart, Windows boots and shows the error "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation".

I then recovered ChromeOS and re-downloaded your script and did the standalone coreboot install/update (option 5) and attempted to reinstall Windows, to the exact same result. Any input on how you got Windows to install, and what this error is trying to tell me? Thanks!

[JonniMR]

Matt?

Can anyone help me here.

My Chromebox wont boot it goes to a black screen and displays the following at the top left corner:

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
#_

Not sure what happened here.

Anyone know what caused this?

[DocG]

Hi Matt,

Just got my box, and your script has helped a lot. Initially I dual booted ChromeOS and Ubuntu, which worked well and was a lot of fun to play around with. Now I'm attempting to install Windows 8.

I first tried to install it after I used your script to dual boot ChromeOS and Ubuntu. I rebooted, entered legacy boot (Ctrl-L), and then hit Esc to go into SeaBIOS's boot menu and select USB boot. I then proceeded to install Windows on the whole disk (deleting all other partitions using the Windows' installer partition tool). It seemed to install successfully, copying over all the files, until it rebooted. Then I did Ctrl-L and selected boot from disc (SSD) and then Windows showed a Windows 8 BSOD (a face) and reported the error "Page Fault in a Non Paged Area" (underscores in between, don't know exact formatting). In the same line, it looked like it said something about "Display" also -- could not read it, it was too blurry. After an automatic restart, Windows boots and shows the error "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation".

I then recovered ChromeOS and re-downloaded your script and did the standalone coreboot install/update (option 5) and attempted to reinstall Windows, to the exact same result. Any input on how you got Windows to install, and what this error is trying to tell me? Thanks!

If the write-protect screw is out and you've flashed Coreboot, Windows should just install. It did for me without issues. Doesn't run without issues, but that's a different matter.

[DocG]

Matt?

Can anyone help me here.

My Chromebox wont boot it goes to a black screen and displays the following at the top left corner:

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
#_

Not sure what happened here.

Anyone know what caused this?

So everything was working, you've been running... what setup?? Then you did a clean shutdown, and next time you tried to boot up your machine you were greeted with that message?

[Matt Devo]

Can anyone help me here.

My Chromebox wont boot it goes to a black screen and displays the following at the top left corner:

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
#_

Not sure what happened here.

that happened to me once with OpenELEC after an improper shutdown. I just did what it said and ran the fsck utility from the command line. Don't remember the exact parameters offhand though.

Hi Matt,

Just got my box, and your script has helped a lot. Initially I dual booted ChromeOS and Ubuntu, which worked well and was a lot of fun to play around with. Now I'm attempting to install Windows 8.

I first tried to install it after I used your script to dual boot ChromeOS and Ubuntu. I rebooted, entered legacy boot (Ctrl-L), and then hit Esc to go into SeaBIOS's boot menu and select USB boot. I then proceeded to install Windows on the whole disk (deleting all other partitions using the Windows' installer partition tool). It seemed to install successfully, copying over all the files, until it rebooted. Then I did Ctrl-L and selected boot from disc (SSD) and then Windows showed a Windows 8 BSOD (a face) and reported the error "Page Fault in a Non Paged Area" (underscores in between, don't know exact formatting). In the same line, it looked like it said something about "Display" also -- could not read it, it was too blurry. After an automatic restart, Windows boots and shows the error "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation".

I then recovered ChromeOS and re-downloaded your script and did the standalone coreboot install/update (option 5) and attempted to reinstall Windows, to the exact same result. Any input on how you got Windows to install, and what this error is trying to tell me? Thanks!

sounds like you have an issue with your installation media, as I've never seen that, and I've installed Win8 on the CB a handful of times