Login at Kodi Home

nickr · 2014-12-02, 07:09

(2014-12-02, 05:45)TonyPh12345 Wrote: Hey, folks!

I'm having several problems using the install script in post 1.

When selecting dual boot with OpenELEC, wget throws an error that the certificates don't match.
Same when checking for BIOS update.

I was able to successfully install Ubuntu, though.

When running XBMC in Ubuntu, I'm finding it impossible to get HD Audio... Everything is just sent 5.1, no DTS HD MA. Is this an Ubuntu-issue?

The Ubuntu audio option is set to HDMI, as is XBMC.

Finally, is it possible to get it to boot straight into XBMC without having to log in and start XBMC manually?

Thanks!!!

Re audio, do you have pulseaudio installed? This only goes up to 5.1 DTS/AC3 I believe. Get rid of it or start xbmc with

AE_SINK=ALSA xbmc

wrxtasy · 2014-12-02, 07:18

Does anyone have feedback on the Netflix video quality through the Chrome browser when running a single boot XBMCbuntu setup ?

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

(2014-12-02, 07:02)prattmd Wrote:
(2014-12-01, 22:30)prattmd Wrote: OK, I followed everything and used mini.iso and installed ubuntu server
The usb is recognized as sda so I installed the system and grub to sdb

I was able to boot into ubuntu using legacy bios hd boot

Yay

Now, though, if I use cntrl-d to go to Chromeos, it says the system is corrupted
Any ideas?

ok, so I installed to dev/sdb7 and installed grub to dev/sdb7 instead of the MBR
Now, ubuntu won't boot AND chrome os wont boot

Any other ideas?

I'll look into it tomorrow and report back with the correct config.

(2014-12-02, 07:18)wrxtasy Wrote: Does anyone have feedback on the Netflix video quality through the Chrome browser when running a single boot XBMCbuntu setup ?

I had no issues getting full HD / 5.1 from Neflix via Chrome in Ubuntu 14.10 when I tested a week or two back

1leafsfan · (This post was last modified: 2014-12-02, 17:23 by 1leafsfan.)

I'm getting the booting kernel error. I first got it when trying to dual boot, after reading this thread the simple CTRL D got me going again. So I tried a standalone install. I selected to backup to USB and it seemed to finish then rebooted on it's own. I tried pressing ESC (just once) but it went back to booting Kernel. I can't seem to get out of this loop now. CTRL D doesn't seem to work, ESC doesn't bring up a boot menu.

I should have known better than to try this late at night.

**Edit So after searching and reading it looks like I need to try a different keyboard. I have been using a logitech wireless which seems to work for the first menus but it seems to be a somewhat common issue that it won't work after getting past the first few steps of installing OpenElec. I'm also going to try and get a few different USB keys incase the one I have can't be read.

Human_USB · 2014-12-02, 14:50

Howdy,

I just got my ChromeBox because of this thread, and love it! Using Kodi 14 rc1 based OpenELEC, I cannot turn on BlueTooth...... is this normal?

TonyPh12345 · 2014-12-02, 15:58

(2014-12-02, 07:09)nickr Wrote:
(2014-12-02, 05:45)TonyPh12345 Wrote: When running XBMC in Ubuntu, I'm finding it impossible to get HD Audio... Everything is just sent 5.1, no DTS HD MA. Is this an Ubuntu-issue?

The Ubuntu audio option is set to HDMI, as is XBMC.

Re audio, do you have pulseaudio installed? This only goes up to 5.1 DTS/AC3 I believe. Get rid of it or start xbmc with

AE_SINK=ALSA xbmc

Yep, it is using Pulse... I'll give that envvar a try this evening.

@matt Devo, any idea why the script is bombing out for OpenELEC installs? I tried inserting the "--no-check-certificate" option in the sh script where the wget is used to dropbox, but that just caused a "403" error and still won't download the syslinux file.

On a separate note, looks like this Asus Chromebox is headed back to Amazon -- the Wired Ethernet socket is not working. Even in native ChromeOS (virgin bootup) it insists on WiFi only, even though my network is working fine with other devices on the same cable.

Thanks, y'all!

rmilyard · 2014-12-02, 16:23

Matt Devo I haven't read though this entire post. I have my Chromebox running the latest 4.2.1 I think (at work so can't check). I see that 5.0 RC1 was release. Do you have an easy way to upgrade to this to try out?

Matt Devo · (This post was last modified: 2014-12-02, 17:48 by Matt Devo.)

(2014-12-02, 14:28)1leafsfan Wrote: I'm getting the booting kernel error. I first got it when trying to dual boot, after reading this thread the simple CTRL D got me going again. So I tried a standalone install. I selected to backup to USB and it seemed to finish then rebooted on it's own. I tried pressing ESC (just once) but it went back to booting Kernel. I can't seem to get out of this loop now. CTRL D doesn't seem to work, ESC doesn't bring up a boot menu.

I should have known better than to try this late at night.

CTRL-D/L don't work with the standalone firmware, only the stock one. If pressing ESC doesn't work to bring up the boot menu (but you do see the 'press ESC' text), then try another keyboard. And be sure to only press ESC once, since more than that will auto-boot the internal HDD.

(2014-12-02, 14:50)Human_USB Wrote: Howdy,

I just got my ChromeBox because of this thread, and love it! Using Kodi 14 rc1 based OpenELEC, I cannot turn on BlueTooth...... is this normal?

I just did a clean install of OE 5.0 RC1 (4.97.1) and have no issues enabling bluetooth via Settings-->OpenELEC-->Services-->Bluetooth. Are you not able to do so?

(2014-12-02, 15:58)TonyPh12345 Wrote: Yep, it is using Pulse... I'll give that envvar a try this evening.

@matt Devo, any idea why the script is bombing out for OpenELEC installs? I tried inserting the "--no-check-certificate" option in the sh script where the wget is used to dropbox, but that just caused a "403" error and still won't download the syslinux file.

On a separate note, looks like this Asus Chromebox is headed back to Amazon -- the Wired Ethernet socket is not working. Even in native ChromeOS (virgin bootup) it insists on WiFi only, even though my network is working fine with other devices on the same cable.

Thanks, y'all!

I'm not seeing any such issues here, just tested an OE dual boot install.

(2014-12-02, 16:23)rmilyard Wrote: Matt Devo I haven't read though this entire post. I have my Chromebox running the latest 4.2.1 I think (at work so can't check). I see that 5.0 RC1 was release. Do you have an easy way to upgrade to this to try out?

just do a manual upgrade as per the wiki/OE wiki, then enable automatic updates

rmilyard · 2014-12-02, 18:08

(2014-12-02, 17:29)Matt Devo Wrote:
(2014-12-02, 14:28)1leafsfan Wrote: I'm getting the booting kernel error. I first got it when trying to dual boot, after reading this thread the simple CTRL D got me going again. So I tried a standalone install. I selected to backup to USB and it seemed to finish then rebooted on it's own. I tried pressing ESC (just once) but it went back to booting Kernel. I can't seem to get out of this loop now. CTRL D doesn't seem to work, ESC doesn't bring up a boot menu.

I should have known better than to try this late at night.

CTRL-D/L don't work with the standalone firmware, only the stock one. If pressing ESC doesn't work to bring up the boot menu (but you do see the 'press ESC' text), then try another keyboard. And be sure to only press ESC once, since more than that will auto-boot the internal HDD.

(2014-12-02, 14:50)Human_USB Wrote: Howdy,

I just got my ChromeBox because of this thread, and love it! Using Kodi 14 rc1 based OpenELEC, I cannot turn on BlueTooth...... is this normal?

I just did a clean install of OE 5.0 RC1 (4.97.1) and have no issues enabling bluetooth via Settings-->OpenELEC-->Services-->Bluetooth. Are you not able to do so?

(2014-12-02, 15:58)TonyPh12345 Wrote: Yep, it is using Pulse... I'll give that envvar a try this evening.

@matt Devo, any idea why the script is bombing out for OpenELEC installs? I tried inserting the "--no-check-certificate" option in the sh script where the wget is used to dropbox, but that just caused a "403" error and still won't download the syslinux file.

On a separate note, looks like this Asus Chromebox is headed back to Amazon -- the Wired Ethernet socket is not working. Even in native ChromeOS (virgin bootup) it insists on WiFi only, even though my network is working fine with other devices on the same cable.

Thanks, y'all!

I'm not seeing any such issues here, just tested an OE dual boot install.

(2014-12-02, 16:23)rmilyard Wrote: Matt Devo I haven't read though this entire post. I have my Chromebox running the latest 4.2.1 I think (at work so can't check). I see that 5.0 RC1 was release. Do you have an easy way to upgrade to this to try out?

just do a manual upgrade as per the wiki/OE wiki, then enable automatic updates

Maybe I am blind but not seeing this.

Matt Devo · 2014-12-02, 18:10

(2014-12-02, 18:08)rmilyard Wrote: Maybe I am blind but not seeing this.

http://wiki.openelec.tv/index.php/Updating_OpenELEC

oval61251 · 2014-12-02, 18:54

Is it possible to play emulators with in OpenELEC? I was doing some reading and it sounds like you need a special build of XBMC/Kodi, any plans for this or am I mistaken?

Matt Devo · 2014-12-02, 21:14

(2014-12-02, 18:54)oval61251 Wrote: Is it possible to play emulators with in OpenELEC? I was doing some reading and it sounds like you need a special build of XBMC/Kodi, any plans for this or am I mistaken?

not really the right place for this question; the OpenELEC forums would probably be better

1leafsfan · 2014-12-03, 01:03

(2014-12-02, 18:08)rmilyard Wrote: [quote='Matt Devo' pid='1851229' dateline='1417534143']
[quote='1leafsfan' pid='1851120' dateline='1417523339']
I'm getting the booting kernel error. I first got it when trying to dual boot, after reading this thread the simple CTRL D got me going again. So I tried a standalone install. I selected to backup to USB and it seemed to finish then rebooted on it's own. I tried pressing ESC (just once) but it went back to booting Kernel. I can't seem to get out of this loop now. CTRL D doesn't seem to work, ESC doesn't bring up a boot menu.

I should have known better than to try this late at night.

CTRL-D/L don't work with the standalone firmware, only the stock one. If pressing ESC doesn't work to bring up the boot menu (but you do see the 'press ESC' text), then try another keyboard. And be sure to only press ESC once, since more than that will auto-boot the internal HDD.

Plugged in a USB keyboard and the ESC key worked as you all knew it would Smile

I was shocked at how quickly it installed OpenElec.

billyvnilly · 2014-12-03, 05:40

I followed steps AFAIK, and I'm not getting the option to boot into openelec. I chose 30 seconds + ChromeOS. And I exited developer mode. When i power off and restart, there is no option to choose the boot (blank screen into the chromeOS) I see that it should say "esc." on the black screen... and ctrl+d or ctrl+l also dont seem to do anything? Was I supposed to always stay in developer mode? The fact that Lon admits doing something wrong in his setup, confuses me even more. I followed the steps on the wiki, and have just finished watching his video, and just confused.

Matt Devo · (This post was last modified: 2014-12-03, 06:18 by Matt Devo.)

(2014-12-03, 05:40)billyvnilly Wrote: I followed steps AFAIK, and I'm not getting the option to boot into openelec. I chose 30 seconds + ChromeOS. And I exited developer mode. When i power off and restart, there is no option to choose the boot (blank screen into the chromeOS) I see that it should say "esc." on the black screen... and ctrl+d or ctrl+l also dont seem to do anything? Was I supposed to always stay in developer mode? The fact that Lon admits doing something wrong in his setup, confuses me even more. I followed the steps on the wiki, and have just finished watching his video, and just confused.

you should not have exited developer mode - tried to make that explicit on the wiki.

Assuming you already performed the factory reset as per my instructions, you'll just need to re-enter developer mode, re-download/re-run the script, and re-run the 2nd stage of the OE dual boot setup. Once that's done, then you will be able to boot into either ChromeOS or OpenELEC via [CTRL-D] / [CTRL-L] on the developer boot screen.

If you didn't do the factory reset the first time around, do that, then start from scratch.

Lon's video is more confusing than helpful IMO.