Matt, just a useful tip for the Wiki. I've found plugging in a Logitech Unifying USB Receiver that came with my wireless mouse causes a standard USB keyboard plugged in at the same time to not work at the boot pompt. Removed the Unifying USB receiver caused the USB keyboard to work again. This took me some time to find a solution as I thought all my USB flash drives weren't compatible!
I am assuming your script has been updated to install the latest version, correct?
(2015-01-28, 08:32)babyboy84 Wrote: [ -> ]Hi Matt
First i want to thank you for what you did .I installed successfully duall boot for my Asus chrome box Intel I3 and kodi they plays all my mov files without a hipcup. However i have a problem which i need help from you to find a solution for it.
Im currently connecting chromebox to my denon 3312i receiver --> my projector. The problem is everytime i turn on chrome box, the video keeps flickering so many time and then it is off completely( it happens in both Chrome OS and openelec).I have to turn off my receiver and then turn it on again but the same problem will be back in couple minutes later. I don't have this problem if i use blu ray player instead of chrome box. I just did factory reset ( back to factory firmware ) and the problem was gone. No more flickering screen and the video output is stable. I know you created your own firmware and put it in your script so i just want to ask you if you have any clue how to fix this problem?
Thank you
when did you do the dual boot setup? It possible the issue was caused by a configuration option set for the video BIOS, which in the latest version of the script has been reverted to the stock config (meaning, the video output behavior now should be consistent with the stock firmware)
(2015-01-28, 15:40)plinkyplonky Wrote: [ -> ]Matt, just a useful tip for the Wiki. I've found plugging in a Logitech Unifying USB Receiver that came with my wireless mouse causes a standard USB keyboard plugged in at the same time to not work at the boot pompt. Removed the Unifying USB receiver caused the USB keyboard to work again. This took me some time to find a solution as I thought all my USB flash drives weren't compatible!
I'm not able to reproduce that here, with any of the 4 unifying receivers +kb/mice I have. sounds like it might be a weird coincidence? either way, I'm pretty clean on the wiki that if you see the 'Press ESC for boot menu' text, it's a keyboard issue, not a USB drive one
(2015-01-28, 16:29)oval61251 Wrote: [ -> ]I am assuming your script has been updated to install the latest version, correct?
um, context? latest version of what?
(2015-01-28, 17:51)Matt Devo Wrote: [ -> ] (2015-01-28, 16:29)oval61251 Wrote: [ -> ]I am assuming your script has been updated to install the latest version, correct?
um, context? latest version of what?
Last time I ran your script was over the summer and installed openELEC 4.2.1, now that 5.0.0 is out I was wondering if your script reflected that update for Kodi
(2015-01-28, 18:11)oval61251 Wrote: [ -> ]Last time I ran your script was over the summer and installed openELEC 4.2.1, now that 5.0.0 is out I was wondering if your script reflected that update for Kodi
of course, and the changelog at the bottom of the first post reflects this. But the script isn't designed to update the installed OS (OE/Ubuntu etc), just setup and install it. Updates are handled thru the normal mechanism for the installed OS. OpenELEC wiki has info on updating, and is linked to from the ChromeBox wiki
(2015-01-28, 18:22)Matt Devo Wrote: [ -> ] (2015-01-28, 18:11)oval61251 Wrote: [ -> ]Last time I ran your script was over the summer and installed openELEC 4.2.1, now that 5.0.0 is out I was wondering if your script reflected that update for Kodi
of course, and the changelog at the bottom of the first post reflects this. But the script isn't designed to update the installed OS (OE/Ubuntu etc), just setup and install it. Updates are handled thru the normal mechanism for the installed OS. OpenELEC wiki has info on updating, and is linked to from the ChromeBox wiki
Right, I understand that I just wanted to know in the event there was an issue I could just rerun your script and start from scratch.
(2015-01-28, 17:51)Matt Devo Wrote: [ -> ] (2015-01-28, 15:40)plinkyplonky Wrote: [ -> ]Matt, just a useful tip for the Wiki. I've found plugging in a Logitech Unifying USB Receiver that came with my wireless mouse causes a standard USB keyboard plugged in at the same time to not work at the boot pompt. Removed the Unifying USB receiver caused the USB keyboard to work again. This took me some time to find a solution as I thought all my USB flash drives weren't compatible!
I'm not able to reproduce that here, with any of the 4 unifying receivers +kb/mice I have. sounds like it might be a weird coincidence? either way, I'm pretty clean on the wiki that if you see the 'Press ESC for boot menu' text, it's a keyboard issue, not a USB drive one
I had exactly the same issue, was driving me nuts! Tried several keyboards and then once I removed the unifying receiver it worked
(2015-01-28, 20:59)snarby2014 Wrote: [ -> ] (2015-01-28, 15:40)plinkyplonky Wrote: [ -> ]Matt, just a useful tip for the Wiki. I've found plugging in a Logitech Unifying USB Receiver that came with my wireless mouse causes a standard USB keyboard plugged in at the same time to not work at the boot pompt. Removed the Unifying USB receiver caused the USB keyboard to work again. This took me some time to find a solution as I thought all my USB flash drives weren't compatible!
I had exactly the same issue, was driving me nuts! Tried several keyboards and then once I removed the unifying receiver it worked
if either of you want to help debug the issue, send me a PM. Just need you to pull the firmware boot log with both devices connected
can anybody help me with my hp chrome box install standalone openelec using with ir605 MCE usb. I put it on suspend mode and i can wake up normal if just couple hours of sleep/suspend but if i'm not using it for extended time like 24 hours or something, i can't wake it up at all, then i pulled the usb ir out, the box automatically turn on, so i think the problem laying between the usb dongle and the chrome box, hopefully with some scripts or ssh command can fix this.
(2015-01-29, 05:21)tml2k2 Wrote: [ -> ]can anybody help me with my hp chrome box install standalone openelec using with ir605 MCE usb. I put it on suspend mode and i can wake up normal if just couple hours of sleep/suspend but if i'm not using it for extended time like 24 hours or something, i can't wake it up at all, then i pulled the usb ir out, the box automatically turn on, so i think the problem laying between the usb dongle and the chrome box, hopefully with some scripts or ssh command can fix this.
firmware version/date (from SeaBIOS boot screen)
OE version
log file (ssh in, run 'dmesg | pastebinit' and provide generated URL)
(2015-01-29, 06:08)Matt Devo Wrote: [ -> ] (2015-01-29, 05:21)tml2k2 Wrote: [ -> ]can anybody help me with my hp chrome box install standalone openelec using with ir605 MCE usb. I put it on suspend mode and i can wake up normal if just couple hours of sleep/suspend but if i'm not using it for extended time like 24 hours or something, i can't wake it up at all, then i pulled the usb ir out, the box automatically turn on, so i think the problem laying between the usb dongle and the chrome box, hopefully with some scripts or ssh command can fix this.
firmware version/date (from SeaBIOS boot screen)
OE version
log file (ssh in, run 'dmesg | pastebinit' and provide generated URL)
i'm using coreboot jan 7 for standalone boot
openelec 5.0
url
http://sprunge.us/iPHh
(2015-01-29, 06:18)tml2k2 Wrote: [ -> ]i'm using coreboot jan 7 for standalone boot
openelec 5.0
url http://sprunge.us/iPHh
sorry if I wasn't clear - need the dmesg log to be taken right after you experience the 'fail to wakeup' condition. Attempt to power on via remote a few times, then use the power button to wake from suspend and take the log after.
(2015-01-29, 06:35)Matt Devo Wrote: [ -> ] (2015-01-29, 06:18)tml2k2 Wrote: [ -> ]i'm using coreboot jan 7 for standalone boot
openelec 5.0
url http://sprunge.us/iPHh
sorry if I wasn't clear - need the dmesg log to be taken right after you experience the 'fail to wakeup' condition. Attempt to power on via remote a few times, then use the power button to wake from suspend and take the log after.
i did exactly what you told so here it is
http://sprunge.us/IJQB
(2015-01-29, 07:30)tml2k2 Wrote: [ -> ]i did exactly what you told so here it is
http://sprunge.us/IJQB
that log shows the system was successfully resumed by your MCE remote. Is that not what happened in this case?
(2015-01-29, 07:36)Matt Devo Wrote: [ -> ] (2015-01-29, 07:30)tml2k2 Wrote: [ -> ]i did exactly what you told so here it is
http://sprunge.us/IJQB
that log shows the system was successfully resumed by your MCE remote. Is that not what happened in this case?
no, this i just follow to what you told me to do, as i described earlier usually after it stand by for at least 15 hrs or something for it to happen, i think i have to use it util it happened again then i'll post the new one for you to check it out.