(2016-09-08, 05:02)Boulder Wrote: [ -> ]Maybe you should boot a live Linux distro from a USB stick and test if you have the same issue there. It would rule out the Chromebox hardware.
(2016-09-08, 06:37)Matt Devo Wrote: [ -> ] (2016-09-08, 05:35)A2K81 Wrote: [ -> ]I'd be happy to. Not sure I quite know how to go about that though!
download the Ubuntu 16.04 ISO. Use Rufus (assuming using a Windows machine) to write the ISO to USB. Power off Chromebox, insert USB, power on, press ESC for boot menu when prompted, select USB device.
I managed to get Ubuntu up and running on the Chromebox using USB, but the same problem happened there. Wouldn't connect to the internet until I restarted my router and the Chromebox. After restarts, worked fine in LibreELEC and Ubuntu. Again, no other devices in my home are experiencing any sort of connection issues.
(2016-09-12, 02:14)Matt Devo Wrote: [ -> ] (2016-09-12, 02:02)A2K81 Wrote: [ -> ] (2016-09-09, 07:53)nickr Wrote: [ -> ]Yes, SSH into your chromebox.
I can't SSH into the chromebox when this happens, it just times out on me.
I'd really recommend booting a Linux live USB as suggested earlier to determine if hardware or software issue. Either that, or backup your exiting LE config to USB and do a Soft Reset via the LE control panel
Based on my last post, do you think I should do a soft reset?
(2016-09-12, 01:37)Matt Devo Wrote: [ -> ] (2016-09-12, 01:29)samurai_k Wrote: [ -> ]Update, I finally was able to get to terminal using another technique. The following is what I did (as this is not documented in the wiki)
1. Boot up ChromeOS
2. Establish a network connection
3. Login as Guest
4. Hit [CTRL+ALT+T] This will launch Crosh in the browser.
5. Type in the command: Shell
This allowed me to finally get to the terminal where I could run the script...
that was going to be my next suggestion. The reason it's not documented in the wiki is because it's potentially problematic for some of the script functions, due to ChromeOS automatically mounting inserted USB/SD media. This can disrupt or cause a failure when backing up the stock firmware and/or creating the LibreELEC install media
Thanks. Good to know for next time (which I hope I don't have to deal with again).
You guys have built a great product out of LibreELEC. It is running like a champ on this Chromebox. Noticeable improvement in performance and stability, as well as everything just works (HDMI audio output and clear HDMI video output) with the LibreELEC Chromebox when compared with Windows 10 + Kodi Chromebox.
(2016-09-12, 02:51)A2K81 Wrote: [ -> ]Based on my last post, do you think I should do a soft reset?
no, if you can reproduce the problem with Ubuntu as well, then it's unlikely a software/config issue on the Chromebox, so resetting LibreELEC is unlikely to produce any useful results. If nothing changed recently on your router (fw update?), then it could just be the wireless card on the Chromebox has become flaky for some reason. If it were me, I'd use it as an excuse to upgrade to an Intel 7260-AC wifi card (vs the stock -abgn card) for $20 or so
i first upgraded legacy bios using you webpage and used option 3 to put onenelec on
sd card .
the chromebox wouldnt boot via sd card.
I then tried johnlewis.ie legacy rom , still the chromebox didnt boot from sd card .
i accidentally restored origional bios by following some guide on the net.
i intended to do a bios backup , but dont know how ?
I just want it that I can try out different os by booting from sd card or usb
so where do i go from here ?
what size of donation is required ?
(2016-09-12, 07:38)seamus_butler Wrote: [ -> ]i first upgraded legacy bios using you webpage and used option 3 to put onenelec on
sd card .
the chromebox wouldnt boot via sd card.
I then tried johnlewis.ie legacy rom , still the chromebox didnt boot from sd card .
i accidentally restored origional bios by following some guide on the net.
i intended to do a bios backup , but dont know how ?
I just want it that I can try out different os by booting from sd card or usb
so where do i go from here ?
what size of donation is required ?
use the Kodi E-Z Setup script to install/update the Legacy BIOS; when prompted, choose 'Y' to default to booting from USB in legacy boot mode. Redo the LibreELEC install on SD card (though I *highly* recommend using a USB3 flash drive, it will be a *lot* faster). Reboot, hit CTRL+L on the Developer Mode boot screen to boot in Legacy Boot mode, and the USB/SD install of LibreELEC should boot automatically. If it doesn't, reboot and try manually selecting it from the boot menu by pressing ESC when prompted and selecting the # for the USB/SD device. If it still doesn't work, post the error / take a pic etc. so I can see what's going on
how do i backup bios to sd card ?
is that johnlewis.ie script any good ?
i will try it again but want to avoid bricking chromebox.
(2016-09-12, 08:16)seamus_butler Wrote: [ -> ]how do i backup bios to sd card ?
is that johnlewis.ie script any good ?
i will try it again but want to avoid bricking chromebox.
there's no need to backup the firmware when only flashing the RW_LEGACY portion, because it's completely independent from ChromeOS, and has no ability to brick the box.
John Lewis's script and mine address different segments/needs of the ChromeOS user community. For Chromeboxes, mine is the way to go.
so its okay to try option 1 and a few days later option 2 with the Kodi E-Z Setup ?
thanks again.
(2016-09-12, 09:35)seamus_butler Wrote: [ -> ]so its okay to try option 1 and a few days later option 2 with the Kodi E-Z Setup ?
thanks again.
I'm really unclear as to what you're asking. Options 1 and 2 install GalliumOS and LibreELEC respectively in a dual boot setup on the internal SSD. So far, you've been talking about installing to an external USB/SD card (option 3).
i just want to make sure if I mess around with option 1 or 2 .......there isnt any problem
turning back system to chrome os 'triicky'
(2016-09-13, 08:14)seamus_butler Wrote: [ -> ]i just want to make sure if I mess around with option 1 or 2 .......there isnt any problem
turning back system to chrome os 'triicky'
no, it's quite trivial in fact. you power on in recovery mode, insert the recovery media, and wait 5 minutes or so
Hey, I'm having the below issue again. I actually removed the 2.0 hub assuming that was causing the attached hard drive to fail. It worked, and there is no issue. However, since it was needed previously, isn't it likely to start up again?
My question, has there been any form of update to remedy this yet or any better solution? I'd just pull from my NAS, but the wifi doesn't reach well nor can I plug in.
Suggestions?
-----
(2015-11-18, 12:08)lancastrian Wrote: [ -> ] (2015-11-18, 10:56)McButton Wrote: [ -> ]On my Chromebox, I notice that it doesn't always keep an external drive connected. I had a 2TB that would disco then reconnect, and my 6 does now too. I've used 4 different cables and 3 of the 4 ports. All the same issue. Also, when it idles for long periods of time, upon turning the system back on, it's no longer accessible, though it is clearly on.
Any ideas? I read somewhere about the USB 3.0 having some sort of power save mode that may disconnect and not allow a reconnect. Whether it's a temp or total disconnect, a reboot always fixes it. It's pretty annoying.
I had an issue writing to a portable HDD when connected to my Chromebox's USB 3.0 ports (it would disconnect/fail mid-transfer). In the end the workaround was attaching it via a cheap USB 2.0 hub - not as quick, but it worked, suggesting the problem was USB 3.0 related.
It's a strange one, because I connected the same drive directly to my dad's Chromebox - an identical HP CB1-030na with the exact same version of OpenELEC (and even the same add-ons) - without any issues whatsoever.
Another possible option, and one I've since taken, is to attach your HDD directly to your router (or NAS if you have one) and have your Chromebox retreive the files across your network. This also means you can access the files from other devices when your Chromebox is not switched on.
(2015-11-18, 21:00)Matt Devo Wrote: [ -> ] (2015-11-18, 20:48)McButton Wrote: [ -> ]Weird. I have a 2.0 hub, but wouldn't it still disco since it's routing through the chromebox 3.0? I have all my files on my cloud too. The drive is a backup. Cloud would be easier, but I don't want buffering. It's usually really good, but I'd rather keep it more of a stable source.
If I could access the 3.0 to ensure it always stayed live, I'd be set. I'll try the 2.0 route. It doesn't need to be faster to play my VIDS and all I transfer to it is from my laptop through the network.
No, since it forces the xhci controller into ehci/USB 2.0 mode
2nd point: I've been fighting the Chromebox "no audio on restore" issue for a year.
I applied the patch that MattDevo suggested at the time, but it never took hold. On my old TV, it was never an issue. The new TV must register the HDMI ports differently when it idles or something.
That said, is there a new, cool update or fix for this issue now?
Rather than just leave the box ON all the time, I'd rather just use "suspend" and hit a button to restore it from sleep.
Thanks in advance for any advice!
Somewhat in relation to McButton's post, if my Chromebox is on before any of my other equipment then I got no video out, extremely fustrating problem, currently trying to deal with an issue where the Chromebox is randomly turning on by itself, I think it's the PS3 BD remote(old one) which I recently connected to the Chromebox via Bluetooth, seems to be that after 30 mins or so, if I lift the PS3 remote it auto turns the Chromebox on(resumes it from suspended state)
Any ideas ?, been trying for days now to find a fix but nothing seems to work.