Login at Kodi Home

kilbo · 2014-10-29, 18:11

Hi,
Did one standalone install...went flawlessly. Followed instructions as before (?) and the second install shows Matts SeaBIOS installed but Booting from Hard Disk is stalled and XBMC is not loading.
Can someone point me in the direction I need to correct whatever has gone wrong. Do I need to do a restore and a do over? Thanks!

Matt Devo · 2014-10-29, 21:33

(2014-10-29, 18:11)kilbo Wrote: Hi,
Did one standalone install...went flawlessly. Followed instructions as before (?) and the second install shows Matts SeaBIOS installed but Booting from Hard Disk is stalled and XBMC is not loading.
Can someone point me in the direction I need to correct whatever has gone wrong. Do I need to do a restore and a do over? Thanks!

just reinstall OpenELEC, or whatever OS you want to use. If the SeaBIOS version tag has my name in it then the firmware installed correctly, so it's just an OS/bootloader issue.

z06gal · 2014-10-30, 01:09

I hope someone can help me out. I have followed the instructions for a standalone OpenElec on my chrome box but cannot get past the booting from hard disc screen. I have the recovery disc in but nothing happens when pressing escape. How do i get a boot menu? Everything seemed to go fine with the script but I am stuck at this point. Thanks for any help Wink

Robin

Matt Devo · 2014-10-30, 02:05

(2014-10-30, 01:09)z06gal Wrote: I hope someone can help me out. I have followed the instructions for a standalone OpenElec on my chrome box but cannot get past the booting from hard disc screen. I have the recovery disc in but nothing happens when pressing escape. How do i get a boot menu? Everything seemed to go fine with the script but I am stuck at this point. Thanks for any help

Robin

not sure if you're just mixing up terms, but after running the script, you should have the OpenELEC install media on USB, not any recovery disc/media. Are you getting the 'Press ESC for boot menu' text? If so, and pressing ESC doesn't work, then your keyboard isn't being properly initialized and you need to use a different one. If you're not seeing the 'Press ESC...' text, then your USB install media isn't being recognized, and you should use a different USB stick, creating the OpenELEC installer using the instructions on the wiki / on their site.

adun79 · (This post was last modified: 2014-10-30, 02:11 by adun79.)

I'm having trouble with setting the boot options again

At first I did a standalone install (XBMCbuntu), didn't like it and decided to go dual boot OE (default, 1 sec) + ChromeOS.

Everything is good, except when I reboot and try to get in to Chrome the only thing that works is [CTRL]+D, no [CTRL]+L or ESC. I also have to do it almost instantly otherwise I get the "booting from hard disk"

SeaBIOS is rel-1.7.5-82-g8dfa2cf-20141016. When I reinstalled the stock firmware, I kept getting errors while using the one that I backed-up (something about sda/usb missing IIRC) so I just went with the curl command

Now when I try setting the boot options to 30 sec delay it says "3Tfu5W: line 529: set_gbb_flags.sh: command not found" and "Boot options successfully set ...legacy bios doesn't need update etc", except it doesn't work. I still boot instantly into OE, unless I quickly press [CTRL]+D

What's going on?

Matt Devo · (This post was last modified: 2014-10-30, 02:21 by Matt Devo.)

(2014-10-30, 02:10)adun79 Wrote: Now when I try setting the boot options to 30 sec delay it says "3Tfu5W: line 529: set_gbb_flags.sh: command not found" and "Boot options successfully set ...legacy bios doesn't need update etc", except it doesn't work. I still boot instantly into OE, unless I quickly press [CTRL]+D

What's going on?

just to be clear, you're having trouble running that option via the script from ChromeOS? I haven't checked it lately as I don't have ChromeOS on my dev box currently, but I can reload it and check if its causing a problem. The 'set_gbb_flags.sh' command exists only within ChromeOS, and only for the root user.

as a workaround, you can always set the flags manually from a ChromeOS shell prompt:

Code:
sudo set_gbb_flags.sh 0x0

will reset it to ChromeOS default / 30s delay; use 0x488 for ChromeOS + 1s delay.

adun79 · 2014-10-30, 03:23

(2014-10-30, 02:18)Matt Devo Wrote: just to be clear, you're having trouble running that option via the script from ChromeOS? I haven't checked it lately as I don't have ChromeOS on my dev box currently, but I can reload it and check if its causing a problem. The 'set_gbb_flags.sh' command exists only within ChromeOS, and only for the root user.

as a workaround, you can always set the flags manually from a ChromeOS shell prompt:

Code:
sudo set_gbb_flags.sh 0x0

will reset it to ChromeOS default / 30s delay; use 0x488 for ChromeOS + 1s delay.

Yes, running the script from ChromeOS. I can't do it from OE, can I?

Basically I reboot from OE, press [CTRL]D quickly, get in to ChromeOS, press [CTRL] [ALT] F2 and run the script

adun79 · 2014-10-30, 03:39

I tried to do it manually and I got "command not found". I think it's a problem with ChromeOS, I did an update yesterday, maybe something changed

I'll do a factory reset later and see what happens. I'll let you know

z06gal · 2014-10-30, 04:31

(2014-10-30, 02:05)Matt Devo Wrote:
(2014-10-30, 01:09)z06gal Wrote: I hope someone can help me out. I have followed the instructions for a standalone OpenElec on my chrome box but cannot get past the booting from hard disc screen. I have the recovery disc in but nothing happens when pressing escape. How do i get a boot menu? Everything seemed to go fine with the script but I am stuck at this point. Thanks for any help

Robin

not sure if you're just mixing up terms, but after running the script, you should have the OpenELEC install media on USB, not any recovery disc/media. Are you getting the 'Press ESC for boot menu' text? If so, and pressing ESC doesn't work, then your keyboard isn't being properly initialized and you need to use a different one. If you're not seeing the 'Press ESC...' text, then your USB install media isn't being recognized, and you should use a different USB stick, creating the OpenELEC installer using the instructions on the wiki / on their site.

It was the keyboard Matt. It worked when I ran the script but did not when I went to boot menu. I switched usb ports and it worked. Thank you so much for this script. To say that it helps is an understatement Wink

Matt Devo · 2014-10-30, 04:37

(2014-10-30, 03:39)adun79 Wrote: I tried to do it manually and I got "command not found". I think it's a problem with ChromeOS, I did an update yesterday, maybe something changed

I'll do a factory reset later and see what happens. I'll let you know

log into ChromeOS (as a guest is fine) and tell me what the version is so I can test / attempt to replicate here. Also which brand ChromeBox you have

adun79 · 2014-10-30, 07:29

(2014-10-30, 04:37)Matt Devo Wrote:
(2014-10-30, 03:39)adun79 Wrote: I tried to do it manually and I got "command not found". I think it's a problem with ChromeOS, I did an update yesterday, maybe something changed

I'll do a factory reset later and see what happens. I'll let you know

log into ChromeOS (as a guest is fine) and tell me what the version is so I can test / attempt to replicate here. Also which brand ChromeBox you have

It's 38.0.2125.110 (64bit). The box is HP with 2 gigs of ram

flekz · 2014-10-30, 11:47

Hi
I have been referred here due to problems I am having trying to install OpenElec on my Intel NUC. I dont have an SSD as I wanted to install the OS on the USB stick. Really hope you can help as I'm close to giving up and returning it.

I have the N2820 (read N2830) model NUC and have done the following;

- made a bootable USB stick (8gb Patriot Supersonic XT) via the Windows tool
- gone into the Intel's BIOS and unticked UEFI boot and ticked Legacy boot, and made sure the boot from USB box is ticked
- got the USB stick showing on my boot priority list
- hit enter on the USB option to boot from it

Result: "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key"

I then have tried the following:

- upgrading the BIOS from 0032 to 0034, 0038, 0039 (but not 0040 as someone mentioned a problem with this)
- booting from same Patriot USB stick but via different USB ports (2.0 and 3.0)
- booting from 2 other cheapo USB sticks in various USB ports

Result: "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key", every time.

So. What can I do? I would be very grateful if you are able to help with the following:

- As mentioned, I can see my USB stick in the boot priority list. Isn't this the stage most people have a problem getting to?
- Is there anything I have done regarding the BIOS settings that is wrong, or may have missed? I'm not technical enough to understand it all, just followed instructions.
- Any other suggestion as to why it's not booting from the stick, despite it showing up?
- If all fails with booting from my USB, what are my options? If I buy an SSD for the OS do I still need to boot it from USB (i.e. same problem will occur?)?

Sorry for the long post and all the bullet points Smile

Thanks in advance!

Hannes The Hun · 2014-10-30, 14:07

flekz, as it seems that you found the NUC thread, may we ignore your post here?

flekz · 2014-10-30, 14:55

By all means, if it is not relevant to this thread and you cannot offer advice...

I was initially asked to post here, before finding an NUC thread.

thanks

Matt Devo · (This post was last modified: 2014-10-30, 18:47 by Matt Devo.)

(2014-10-30, 14:55)flekz Wrote: By all means, if it is not relevant to this thread and you cannot offer advice...

I was initially asked to post here, before finding an NUC thread.

thanks

looks like nickr had his wires crossed when he directed you here. While the ChromeBox is essentially a Haswell Celeron NUC, it uses an open-source firmware/BIOS, rather than a UEFI BIOS like the NUC. And that firmware has no user-facing settings at all.

(2014-10-30, 07:29)adun79 Wrote: It's 38.0.2125.110 (64bit). The box is HP with 2 gigs of ram

fixed / script updated. Google moved the location of the command outside of the normal executable paths, those jerks.