[Matt Devo]

All standalone:

Matt: I just updated the firmware on my Asus, no problems.
Then did an update on my HP, it now just gives a blank screen through my hdmi switch (which goes to my Pioneer plasma) It works fine if I connect it to my pc monitor. Also works if connected directly to the plasma. (Although doesn't seem to come farther than grub atm)

Any obvious reasons why that is so?


Edit: this happens when I booted with partmagic on my plasma: http://i67.tinypic.com/5d6lgp.jpg (upside down pic, sorry)
This is in 32bit mode, 64bit mode happens to work fine.

Edit2: after a reflash, partmagic works fine in both 32 and 64bit, Kodibuntu boots without getting stuck on grub, but I don't get a picture through my hdmi switch, only when connected directly to my display. I do use the headless firmware, but that shouldn't matter, and my Asus works fine.

edit3: Exchanged the HDMI cable, works fine now. I vaguely remember someone else had the same problem when updating the firmware..any reason why the Chromebox is more sensitive to cable issues now, and why it only is a problem with the HP?

so both boxes hooked to the same switch/display? And have different behavior?

[Soli]

Yes, actually both boxes with the exact same cable and input.
The HP is my old unit which belongs to a friend, I just have it temporarily to reclone my Kodibuntu install to it (since for some reason it gives a screen screen when using vaapi in Kodi 17, no doubt having something to do with egl/ mesa/vaapi ppas, whereas my own install works fine)

[Matt Devo]

Yes, actually both boxes with the exact same cable and input.
The HP is my old unit which belongs to a friend, I just have it temporarily to reclone my Kodibuntu install to it (since for some reason it gives a screen screen when using vaapi in Kodi 17, no doubt having something to do with egl/ mesa/vaapi ppas, whereas my own install works fine)

I don't have any explanation then, but I will say that kodibuntu is long dead; if you need something "more" than LibreELEC I'd follow fritsch's instructions in the Linux/Live forum for a minimal Ubuntu 16.04 server -based setup

[Soli]

Kodibuntu doesn't have anything to do with it, the same would happen with whatever software is running. The HP unit worked perfectly well until the firmware was updated and rebooted.

Kodibuntu works for me, so I'm gonna keep using it until at least 18.04..

[Soli]

Well suddenly my Asus doesn't work through the HDMI switch either. I'm sure that it did at first, since that after I upgraded the firmware, I rebooted with partmagic to clone the system.

It seems I can blame a faulty HDMI cable then, which of course works with everything else. I really hate it when mysterious pc sh** happen to me.

[imbored]

1/2 are unrelated to your dual boot installation. maybe try https://www.reddit/com/chromeos ?
3 - you did the factory reset/recovery process beforehand, and ran the dual boot install 2x as per the instructions?

Thanks for taking the time to reply. Not sure what was up w/ the dual boot, but yes I had done the install 2x. I reverted to bone stock and decided to go standalone and do full GalliumOS. Loved the OS. Still having audio over HDMI issues. After many long nights of research it appears it's a common thing amongst folk w/ older receivers. Minimum sample rate is set at 44.1 when it needs to be 48.8 for the receiver to recognize it. At this point I can't admit defeat of the little chromebox, but I cannot bring myself to purchase a brand new receiver to cover up what it can't do. I'm just going Windows 10 and watching for a Gallium or Libre patch that allows the change of that sample rate.

Thanks again and keep up the good work.

[Matt Devo]

Kodibuntu doesn't have anything to do with it, the same would happen with whatever software is running. The HP unit worked perfectly well until the firmware was updated and rebooted.

Kodibuntu works for me, so I'm gonna keep using it until at least 18.04..

I wasn't blaming Kodibuntu as the potential source of the issue, just pointing out its unsupported status (both officially and here)

Thanks for taking the time to reply. Not sure what was up w/ the dual boot, but yes I had done the install 2x. I reverted to bone stock and decided to go standalone and do full GalliumOS. Loved the OS. Still having audio over HDMI issues. After many long nights of research it appears it's a common thing amongst folk w/ older receivers. Minimum sample rate is set at 44.1 when it needs to be 48.8 for the receiver to recognize it. At this point I can't admit defeat of the little chromebox, but I cannot bring myself to purchase a brand new receiver to cover up what it can't do. I'm just going Windows 10 and watching for a Gallium or Libre patch that allows the change of that sample rate.

Thanks again and keep up the good work.

a minimum sample rate or 48.8KHz is somewhat common, and can easily be set via an entry in advancedsettings.xml - see http://www.xbmc4xbox.org.uk/wiki/UserDat...3Caudio.3E. No need to change OSes, though I think LE might have some additional handling for this via the GUI settings as well

[stevie_boy_84]

Random question: Anyone having issues where Chromebox (OpenElec, Jarvis) requires 2 button presses to get a video to play? It was 1 for over a year. I haven't changed anything. My other non-chrome box works fine. I figured it was my Flirc messing up, but my Yatsee remote on my phone also requires it. Any ideas? I'd do a log, but I'm not home today. Also, if it's just a stupid fix....

Thanks guys!

can't say I've seen that, a log file would definitely help clarify whats going on. Also, I'd recommend upgrading to LibreELEC, as that's the supported distro now. Upgrading is as easy as a manual upgrade (download .tar file, copy to update folder, reboot). Full instructions on www.libreelec.tv

Yes it's the same keyboard with the USB dongle that I originally used, I am hitting ctrl+d from the second I turn the computer on but it still just goes to seabios then a blank screen

that is odd, but seems the easiest thing to do at this point would be to try a different one (wired or wireless doesn't matter, just not using the built-in Bluetooth)

Hi I have now tried the original keyboard, a bluetooth keyboard and have just tried a USB keyboard, and still I am having the same issue, cannot access the boot menu by pushing ESC or enter verified boot mode by pushing the space bar to re-enable, am really at a loss as to where to go from here? Do I just have to accept that I now have 200 quids worth of paper weight?

[Matt Devo]

Hi I have now tried the original keyboard, a bluetooth keyboard and have just tried a USB keyboard, and still I am having the same issue, cannot access the boot menu by pushing ESC or enter verified boot mode by pushing the space bar to re-enable, am really at a loss as to where to go from here? Do I just have to accept that I now have 200 quids worth of paper weight?

re-reading your posts, you said that if you inserted the ChromeOS recovery USB, it automatically boots that. That means it should boot any properly formatted USB without keyboard input. So create a bootable Linux USB (I'd recommend GalliumOS), boot that, then run the script again and reset the firmware boot flags/GBB flags back to factory default.

[Soli]

I wasn't blaming Kodibuntu as the potential source of the issue, just pointing out its unsupported status (both officially and here)

I know too well it's unsupported but I need the patched bluez4 to get the BD remote to work to my liking. I don't like how it works in LE, and I can't be bothered to spend the time learning how to reconfigure the buttons and sleep the remote after a certain time (instead of sleeping when the screensaver kicks in)

[stevie_boy_84]

Hi I have now tried the original keyboard, a bluetooth keyboard and have just tried a USB keyboard, and still I am having the same issue, cannot access the boot menu by pushing ESC or enter verified boot mode by pushing the space bar to re-enable, am really at a loss as to where to go from here? Do I just have to accept that I now have 200 quids worth of paper weight?

re-reading your posts, you said that if you inserted the ChromeOS recovery USB, it automatically boots that. That means it should boot any properly formatted USB without keyboard input. So create a bootable Linux USB (I'd recommend GalliumOS), boot that, then run the script again and reset the firmware boot flags/GBB flags back to factory default.

I have installed galliumOS onto a USB flash drive using Win32 Disk Imager, still exactly the same when i boot, OS verification page followed by seabios followed by blank screen

[Matt Devo]

I have installed galliumOS onto a USB flash drive using Win32 Disk Imager, still exactly the same when i boot, OS verification page followed by seabios followed by blank screen

so how did you manage to boot the ChromeOS recovery media? And if you can still do so, then we can possiblyre-run the script from there and set your GBB flags back

[stevie_boy_84]

I have installed galliumOS onto a USB flash drive using Win32 Disk Imager, still exactly the same when i boot, OS verification page followed by seabios followed by blank screen

so how did you manage to boot the ChromeOS recovery media? And if you can still do so, then we can possiblyre-run the script from there and set your GBB flags back

I booted it using the recovery media on usb but as I said before it just took me to a blank screen or a screen with the chrome logo and nothing else, with the gallium am I supposed to do anything in particular when I boot up, put the USB in before I power up e.g?

[Matt Devo]

I booted it using the recovery media on usb but as I said before it just took me to a blank screen or a screen with the chrome logo and nothing else, with the gallium am I supposed to do anything in particular when I boot up, put the USB in before I power up e.g?

yes, you have to have the USB inserted before powering on - how else would it know to not boot from the internal SSD?

if you can boot the recovery media, you can try opening a shell terminal via CTRL-ALT-F2 as per the script instructions

[stevie_boy_84]

I booted it using the recovery media on usb but as I said before it just took me to a blank screen or a screen with the chrome logo and nothing else, with the gallium am I supposed to do anything in particular when I boot up, put the USB in before I power up e.g?

yes, you have to have the USB inserted before powering on - how else would it know to not boot from the internal SSD?

if you can boot the recovery media, you can try opening a shell terminal via CTRL-ALT-F2 as per the script instructions

I have somehow managed to get into the developer console but last time I did that logging in as user chronos didn't work

After localhost login: I have typed "chronos"
And now there is a line of script that says
chronos@localhost ~ $

Where do I go from here?