[dracozny]

Anyone else having problems with freezing on the Asus i3 running openelec stable? Most of the time it seems to occur when going to suspend or waking up. The light on the box will be on but no video. Just today the screen froze on playback of a stream. I could hit stop and navigate around the menus (I could hear the ticking sound as the cursor moves) but the screen was still frozen on the video.

[Matt Devo]

Anyone else having problems with freezing on the Asus i3 running openelec stable? Most of the time it seems to occur when going to suspend or waking up. The light on the box will be on but no video. Just today the screen froze on playback of a stream. I could hit stop and navigate around the menus (I could hear the ticking sound as the cursor moves) but the screen was still frozen on the video.

please see the OP on providing the info needed to troubleshoot issues.

[dracozny]

Anyone else having problems with freezing on the Asus i3 running openelec stable? Most of the time it seems to occur when going to suspend or waking up. The light on the box will be on but no video. Just today the screen froze on playback of a stream. I could hit stop and navigate around the menus (I could hear the ticking sound as the cursor moves) but the screen was still frozen on the video.

please see the OP on providing the info needed to troubleshoot issues.

well aware of that bit, I was merely asking if others were having similar troubles first before digging into logs and such.

[dartrio]

Hi,
I just bought a Asus M004U w/ 4GB of RAM. I want to run a dual-boot with Openelec. I go through the procedure, no problems except when I get to the point of booting into Openelec. When I hit control L, it gets a boot error saying:

"Booting from Hard Disk.... It appears your computer has only 639K of low ("DOS") RAM. This version of Syslinux needs 9K to boot. If you got this message in error, hold down the Ctrl key while booting, and I will take your word for it. Boot error"

And then it's stuck. As far as I can determine you have to power cycle it to get off this screen. Booting into ChromeOS (Cntrl D) works fine. The holding down the control key doesn't do anything. I doing the dual boot procedure again but the results were the same. So then I went for the non-dual boot option, booting just Openelec, and this worked fine.

I've googled around but haven't found any real answers for what makes this happen and how to get rid of it. This problem is mentioned in a couple of posts in this thread (3835 and 2606) but I didn't see anything about fixing it.

I'd really like to run it dual boot, but I'm stuck as to how to get there. Right now it's running Openelec only. I'd be willing to put Chrome back and try to get it to dual boot again, if there's something's I'm doing wrong, or something else to try. Any ideas?

Thanks in advance for the help.

[Matt Devo]

Hi,
I just bought a Asus M004U w/ 4GB of RAM. I want to run a dual-boot with Openelec. I go through the procedure, no problems except when I get to the point of booting into Openelec. When I hit control L, it gets a boot error saying:

"Booting from Hard Disk.... It appears your computer has only 639K of low ("DOS") RAM. This version of Syslinux needs 9K to boot. If you got this message in error, hold down the Ctrl key while booting, and I will take your word for it. Boot error"

And then it's stuck. As far as I can determine you have to power cycle it to get off this screen. Booting into ChromeOS (Cntrl D) works fine. The holding down the control key doesn't do anything. I doing the dual boot procedure again but the results were the same. So then I went for the non-dual boot option, booting just Openelec, and this worked fine.

I've googled around but haven't found any real answers for what makes this happen and how to get rid of it. This problem is mentioned in a couple of posts in this thread (3835 and 2606) but I didn't see anything about fixing it.

I'd really like to run it dual boot, but I'm stuck as to how to get there. Right now it's running Openelec only. I'd be willing to put Chrome back and try to get it to dual boot again, if there's something's I'm doing wrong, or something else to try. Any ideas?

Thanks in advance for the help.

hitting [CTRL-L] after SeaBIOS has loaded is what causes that error; [CTRL-L] is only valid on the developer mode boot screen, not once a payload has run.

If you want to go back to a dual boot setup, you'll need to restore the stock firmware (which you backed up), then restore ChromeOS and re-run the script (assuming you re-installed OpenELEC to the entire ssd after flashing the custom firmware. If not, you can just restore the stock firmware and should be good to go).

[Matt Devo]

well aware of that bit, I was merely asking if others were having similar troubles first before digging into logs and such.

you really gave us nothing to go on. There aren't any known issues which would cause a lack of video output on resume from suspend (sounds like a HDMI issue with your TV or AVR) or cause the video to freeze and the audio to keep playing (that bug was fixed long ago). The whole reason I put that bit in the OP was to try and limit the number of posts like yours which neither clearly describe a specific problem (or problems) nor give enough info about your configuration to even begin to speculate or tell you what to check

[dartrio]

Hi,
I just bought a Asus M004U w/ 4GB of RAM. I want to run a dual-boot with Openelec. I go through the procedure, no problems except when I get to the point of booting into Openelec. When I hit control L, it gets a boot error saying:

"Booting from Hard Disk.... It appears your computer has only 639K of low ("DOS") RAM. This version of Syslinux needs 9K to boot. If you got this message in error, hold down the Ctrl key while booting, and I will take your word for it. Boot error"

And then it's stuck. As far as I can determine you have to power cycle it to get off this screen. Booting into ChromeOS (Cntrl D) works fine. The holding down the control key doesn't do anything. I doing the dual boot procedure again but the results were the same. So then I went for the non-dual boot option, booting just Openelec, and this worked fine.

I've googled around but haven't found any real answers for what makes this happen and how to get rid of it. This problem is mentioned in a couple of posts in this thread (3835 and 2606) but I didn't see anything about fixing it.

I'd really like to run it dual boot, but I'm stuck as to how to get there. Right now it's running Openelec only. I'd be willing to put Chrome back and try to get it to dual boot again, if there's something's I'm doing wrong, or something else to try. Any ideas?

Thanks in advance for the help.

hitting [CTRL-L] after SeaBIOS has loaded is what causes that error; [CTRL-L] is only valid on the developer mode boot screen, not once a payload has run.

If you want to go back to a dual boot setup, you'll need to restore the stock firmware (which you backed up), then restore ChromeOS and re-run the script (assuming you re-installed OpenELEC to the entire ssd after flashing the custom firmware. If not, you can just restore the stock firmware and should be good to go).

Thanks Matt, That was what I needed to know. I was hitting CTRL-L at the developer mode boot screen, but the keyboard (Microsoft natural keyboard 4000) was evidently bouncing , sending a second CTRL-L after it had started running the payload. I was setting this all up along-side my regular computer and using a KVM switch to share the monitor/keyboard. That may have also played a part.

I restored ChromeOS, re-ran the script, and re-installed OpenElec onto a second partition. But now, using a different keyboard, it works fine. CTRL-L goes right into OpenElec.

Thanks again for the help.

[alandee]

Hi, I'm feeling a little lost and confused and .. stupid at the moment .. the script I thought had worked a treat .. but I'm kinda stuck.
I've run through the standalone openelec script and i'm installing on a celeron asus box..
I've run the script once, and i'm, in hindsight pretty sure the image didn't download, or the usb that was utilised was kaput..
I can press escape to get to the boot menu, but if i try and boot from a recovery image on usb it just turns off the screen..
I'm not really sure how to move forward .. i can always get to the boot menu, i can always select a usb or whatever, but trying to run the recovery image, so that i can try start again just throws up a bit of text too quick to read then the screen turns off and stays off .. if i try to install openelec from an image it does the same .. i have hdmi cable connected..and i've tried with display port cable as well.

i've read through a couple of dozen pages, but haven't really gotten more than things like ctrl -L ctrl-D etc, but have no idea where i would do that or how to get back to square one to start again .. i'm generally able to nut this stuff out, but feel at the moment like i should be smelling toast ..

any assistance greatly received...
cheers,
al.

[Matt Devo]

Hi, I'm feeling a little lost and confused and .. stupid at the moment .. the script I thought had worked a treat .. but I'm kinda stuck.
I've run through the standalone openelec script and i'm installing on a celeron asus box..
I've run the script once, and i'm, in hindsight pretty sure the image didn't download, or the usb that was utilised was kaput..
I can press escape to get to the boot menu, but if i try and boot from a recovery image on usb it just turns off the screen..
I'm not really sure how to move forward .. i can always get to the boot menu, i can always select a usb or whatever, but trying to run the recovery image, so that i can try start again just throws up a bit of text too quick to read then the screen turns off and stays off .. if i try to install openelec from an image it does the same .. i have hdmi cable connected..and i've tried with display port cable as well.

I'm not sure if you're just using the wrong terminology here, but what you need to be booting from is the OpenELEC installation media (not the ChromeOS recovery media), which you should have created using the script after flashing the custom firmware. If that's what you're trying to boot and it's not working (which isn't uncommon), then just re-create the installation media (possibly using another USB stick); the instructions are on the OpenELEC wiki, and are linked to on the ChromeBox wiki page.

[alandee]

Thanks Matt,
yes, I understand what you're saying, but when I try to boot from the openelec media, the screen turns off, black, then no signal .. so I don't know what it's actually doing past the seabios screen. I've left it to see if it was just going to install in the dark, and then reboot or something, but after an hour or so, I assumed it wasn't going to happen I've tried this with both the d/l image and the tar and make my own image on a couple of different sticks, I'll keep persevering if there is nothing other than something unknown, but it all sounded soooo easy ! I would have thought, possibly incorrectly, that if the stick was identified correctly and starts the very first clear screen and micro text install then switches off I might have an incorrect image, but I'm utilising the generic openelec one.

I thought I would try going back to chrome os to restart the whole process, but the same thing happens .. that is the screen goes black and then turns off ... ( hence the confused ramblings of last night )
I'll try again tonight on displayport connection as the hdmi is just not working past the seabios screen, although I would have thought the HDMI was more universal.. and I'll try a couple of different sticks as well ? but it seems like more of the same, pretty sure the variety of sticks should have covered any issue there..

[Matt Devo]

Thanks Matt,
yes, I understand what you're saying, but when I try to boot from the openelec media, the screen turns off, black, then no signal .. so I don't know what it's actually doing past the seabios screen. I've left it to see if it was just going to install in the dark, and then reboot or something, but after an hour or so, I assumed it wasn't going to happen I've tried this with both the d/l image and the tar and make my own image on a couple of different sticks, I'll keep persevering if there is nothing other than something unknown, but it all sounded soooo easy ! I would have thought, possibly incorrectly, that if the stick was identified correctly and starts the very first clear screen and micro text install then switches off I might have an incorrect image, but I'm utilising the generic openelec one.

I thought I would try going back to chrome os to restart the whole process, but the same thing happens .. that is the screen goes black and then turns off ... ( hence the confused ramblings of last night )
I'll try again tonight on displayport connection as the hdmi is just not working past the seabios screen, although I would have thought the HDMI was more universal.. and I'll try a couple of different sticks as well ? but it seems like more of the same, pretty sure the variety of sticks should have covered any issue there..

sounds to me like your display doesn't support whatever resolution the OpenELEC installer is setting, or there's some breakdown in the HDMI handshaking process. I've only ever seen this behavior before when using a DisplayPort->HDMI cable, never with a straight HDMI connection. I'd try using another display and/or boot a different live USB (like Ubuntu) just to verify things are working past the bootloader.

[alandee]

Groovy, I'll give it another crack when I get home tonight with a different screen, and i'll pop an ubuntu live on a couple of different sticks. Thanks.

[vicmack]

Im having a really hard time. Followed all instructions used all links provided for dual boot, installed open elec, all went well but then it wouldnt open, AND I cannot get chrome and I cannot get onto the script page so cant try again. I tried recovering it again with flash drive but no joy, screen just go s blank have i broken my box? .

[Matt Devo]

Im having a really hard time. Followed all instructions used all links provided for dual boot, installed open elec, all went well but then it wouldnt open, AND I cannot get chrome and I cannot get onto the script page so cant try again. I tried recovering it again with flash drive but no joy, screen just go s blank have i broken my box? .

your description of what you did and the problem are way too vague. What exact steps did you take, in what order? What does "wouldn't open" mean? Why can't you boot ChromeOS? What happens when you try to do so? Obviously you broke something, but we need to figure out what in order to determine how to fix things

[vicmack]

Hi Matt, - sorry let me start again. I followed this you tube video https://www.youtube.com/watch?v=9gQgSDdZuLY and used the links Lon suggested. I followed it to the letter. I did struggle to get out of the script page, I pressed "q" like it said but nothing happened so I turned the box off, however it seemed I had managed to install open elec, and when the box re booted, open elec was on the screen but it was just frozen I could not use it in any way. So I turned off the box when I tried to re boot, same thing. So I put in the chrome recovery disk and tried to start over again. I ran the recovery but it does not allow me to get to the chrome os, the screen is just blank. I just tried again and now I cant even run recovery.Do you think Ive bricked the box?