(2014-08-14, 03:21)A2K81 Wrote: [ -> ]$#@! I've upgraded my firmware, OE 4.1.3 and used all of the recommended settings from the wiki. Live TV streams are still causing hard freezing after about an hour of straight viewing, necessitating that the Acer be unplugged and plugged back in.
Any other ideas that haven't been described above? My wife is getting pissed lol.
'Live TV streams' doesn't exactly give any info about format, resolution, deinterlacing, etc. How about posting a log?
(2014-08-14, 04:32)Stereodude Wrote: [ -> ]Can the Chromebox boot from a SD card in the reader?
yes, just like any other bootable USB device
Is it a USB 2.0 or 3.0 SD card reader?
I have a hp chromebox with windows 8.1 installed using your guide here to install the standalone bios (seabios I believe). It only seems to boot up if i have it hooked up to my ASUS 24" monitor via hdmi, if I have it hooked up to my Sony 32" television it will not show any picture or boot. My TV just reports no signal. If I plug it into my ASUS monitor it will then boot, then I simply have to plug it into my TV for it to work... which is tiresome. I've tested many other OS's with it and they all seem to have the same issue. My guess is my television isn't sending a proper signal to say hey im here, go ahead and power on! Besides that this thing is an awesome XBMC/windows/steam stream system! Any one have an opinion or maybe solution besides new tv... might just do that eventually. EDIT:: Also running DXDIAG on windows..my hp box system model reports as Panther..Thought that was the asus one...
(2014-08-14, 07:27)johntriger Wrote: [ -> ]I have a hp chromebox with windows 8.1 installed using your guide here to install the standalone bios (seabios I believe). It only seems to boot up if i have it hooked up to my ASUS 24" monitor via hdmi, if I have it hooked up to my Sony 32" television it will not show any picture or boot. My TV just reports no signal. If I plug it into my ASUS monitor it will then boot, then I simply have to plug it into my TV for it to work... which is tiresome. I've tested many other OS's with it and they all seem to have the same issue. My guess is my television isn't sending a proper signal to say hey im here, go ahead and power on! Besides that this thing is an awesome XBMC/windows/steam stream system! Any one have an opinion or maybe solution besides new tv... might just do that eventually. EDIT:: Also running DXDIAG on windows..my hp box system model reports as Panther..Thought that was the asus one...
I'm really not sure why it wouldn't boot when connected to your TV, it's not something I've been able to reproduce, but HDMI handshaking issues are a widespread problem across various displays/devices it seems. Perhaps something like HDMI Doctor would help?
Panther (Asus) and Zako (HP) are identical firmware wise, save for a slightly more aggressive cooling profile and A/C adapter detection for the HP, so I use the same firmware (originally developed for Panther) for both.
So i was able to get back to the chrome os. I wiped out the ubuntu on the partitioned drive and redid everything. I asked it to boot to ubuntu after 30 but now it just seems to boot up to ubuntu command line. I dont even get to the dev page or anything. I dont recall it asking me how much space I wanted to give to the linux os com to think about it.
(2014-08-14, 18:20)jjgalambos Wrote: [ -> ]So i was able to get back to the chrome os. I wiped out the ubuntu on the partitioned drive and redid everything. I asked it to boot to ubuntu after 30 but now it just seems to boot up to ubuntu command line. I dont even get to the dev page or anything. I dont recall it asking me how much space I wanted to give to the linux os com to think about it.
if your issue was not allocating enough space, you'll need to use the recovery USB to reset the partitions to their defaults, then re-run the script. That's the only way to get it to ask you for the partition size again. I'd recommend 6-8GB
(2014-08-14, 18:22)Matt Devo Wrote: [ -> ] (2014-08-14, 18:20)jjgalambos Wrote: [ -> ]So i was able to get back to the chrome os. I wiped out the ubuntu on the partitioned drive and redid everything. I asked it to boot to ubuntu after 30 but now it just seems to boot up to ubuntu command line. I dont even get to the dev page or anything. I dont recall it asking me how much space I wanted to give to the linux os com to think about it.
if your issue was not allocating enough space, you'll need to use the recovery USB to reset the partitions to their defaults, then re-run the script. That's the only way to get it to ask you for the partition size again. I'd recommend 6-8GB
For some reason I cannot get back to the DEV page so I can insert the USB stick and reimage. I tried pushing crtl d but it goes straight to ubuntu command line. I can get to the boot sequence where it asks me to boot either usb or main drive. Am i missing something
Hi Matt,
I've just bought the ASUS Chromebox and went straight to you blog to install OpenELEC, but I'm facing an issue here.
I've search this forum, several users had the same issue, but I'm not able to resolve using the suggestions given to them.
I've "Put in Developer Mode" and "Disable Firmware Write Protect" (steps 1.1 and 1.2).
My next steps:
- Used the console to download your script and used the option 1 to create the new partition (selected 9)
- After the reboot, selected again option 1 to download and install the OpenELEC.
- Selected option 3 (boot options) and option 1 (short boot / OpenELEC default)
- Reboot
Here starts the issue, I get the message:
SeaBIOS (version rel-1.7.5-10-g8e966c6-20120729-MattDevo)
Booteing from Hard Disk...
And hangs here.
I then tried again the option 1 (installed the OpenELEC again), but doesn't work.
I've also changed the boot order, but selecting CTRL + L sends me again to the same screen.
Any advise?
Thanks for your help
(2014-08-14, 21:01)jtadeia Wrote: [ -> ]Hi Matt,
I've just bought the ASUS Chromebox and went straight to you blog to install OpenELEC, but I'm facing an issue here.
I've search this forum, several users had the same issue, but I'm not able to resolve using the suggestions given to them.
I've "Put in Developer Mode" and "Disable Firmware Write Protect" (steps 1.1 and 1.2).
My next steps:
- Used the console to download your script and used the option 1 to create the new partition (selected 9)
- After the reboot, selected again option 1 to download and install the OpenELEC.
- Selected option 3 (boot options) and option 1 (short boot / OpenELEC default)
- Reboot
Here starts the issue, I get the message:
SeaBIOS (version rel-1.7.5-10-g8e966c6-20120729-MattDevo)
Booteing from Hard Disk...
And hangs here.
I then tried again the option 1 (installed the OpenELEC again), but doesn't work.
I've also changed the boot order, but selecting CTRL + L sends me again to the same screen.
Any advise?
Thanks for your help
you forgot to do step 1.3. From the wiki: A factory reset is not needed on a Standalone setup, but must be performed prior to any dual-boot installation.
I haven't been able to figure out what causes the issue, but a factory reset prior to a dual-boot install fixes it
Do you meen:
"1.3 Update the Legacy BIOS" ?
Can I do that using the script now or do I have to do all over again?
Thanks for the quick reply
(2014-08-14, 21:14)jtadeia Wrote: [ -> ]Do you meen:
"1.3 Update the Legacy BIOS" ?
Can I do that using the script now or do I have to do all over again?
Thanks for the quick reply
where are you looking at for instructions? I don't have a blog, everything I've done is either in this thread or on the ChromeBox page of the XBMC wiki, which is linked in my signature. Other people have copied the wiki at various points, but none are up to date (like any site that copies content rather than linking to the original).
oh Shi&%$.
I was looking at geekfreely blogspot ch openelec-on-asus-chromebox
My mistake, I have the 1.3 step now. Is it Ok to do the factory reset even if I have 2 partitions already?
Sorry for the confusion
(2014-08-14, 21:21)jtadeia Wrote: [ -> ]oh Shi&%$.
I was looking at geekfreely blogspot ch openelec-on-asus-chromebox
My mistake, I have the 1.3 step now. Is it Ok to do the factory reset even if I have 2 partitions already?
Sorry for the confusion
yes, the factory reset will (mostly) return the box to its original state: the hard drive is re-imaged, and the legacy firmware restored to the original.
afterwards, you will just need to re-run the script (twice) like you did originally.
I got the USB with the software, I insert the USB when it prompts (in the revovery menu), the screen stays black for about 40 seconds and then returns to my ChromeOS
it's not factory restoring