2016-09-24, 20:26
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
(2016-09-26, 19:59)McButton Wrote: 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....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
Thanks guys!
(2016-09-24, 20:26)stevie_boy_84 Wrote: 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 screenthat 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)
(2016-09-27, 19:24)tredman Wrote: Right the odd problem I had with 4k display has returned.sounds like a situation that's a candidate for force-loading the EDID at startup. There are instructions on the LE wiki for doing so, which I linked a few pages back. Just be sure to capture/extract the EDID when it's actually working
If I connect my Chromebox to the display from boot I get nothing displayed, xrandr via SSH shows no display.
Connecting after boot occasionally triggers the display to work correctly, but not always. Likewise sometimes a reboot triggers the display to work.
Chromebox works perfectly on a 1080p TV and display in LE is manually forced to 1080p50. I'm running latest 7.90 005 LE.
Any ideas how I can fix this, I'd really like to keep the box but this is a right PITA.
(2016-09-27, 19:24)tredman Wrote: Right the odd problem I had with 4k display has returned.sounds like a situation that's a candidate for force-loading the EDID at startup. There are instructions on the LE wiki for doing so, which I linked a few pages back. Just be sure to capture/extract the EDID when it's actually working
If I connect my Chromebox to the display from boot I get nothing displayed, xrandr via SSH shows no display.
Connecting after boot occasionally triggers the display to work correctly, but not always. Likewise sometimes a reboot triggers the display to work.
Chromebox works perfectly on a 1080p TV and display in LE is manually forced to 1080p50. I'm running latest 7.90 005 LE.
Any ideas how I can fix this, I'd really like to keep the box but this is a right PITA.
(2016-09-27, 19:24)tredman Wrote: Right the odd problem I had with 4k display has returned.sounds like a situation that's a candidate for force-loading the EDID at startup. There are instructions on the LE wiki for doing so, which I linked a few pages back. Just be sure to capture/extract the EDID when it's actually working
If I connect my Chromebox to the display from boot I get nothing displayed, xrandr via SSH shows no display.
Connecting after boot occasionally triggers the display to work correctly, but not always. Likewise sometimes a reboot triggers the display to work.
Chromebox works perfectly on a 1080p TV and display in LE is manually forced to 1080p50. I'm running latest 7.90 005 LE.
Any ideas how I can fix this, I'd really like to keep the box but this is a right PITA.
(2016-09-30, 14:16)Matt Devo Wrote:I thought you might say that(2016-09-27, 19:24)tredman Wrote: Right the odd problem I had with 4k display has returned.sounds like a situation that's a candidate for force-loading the EDID at startup. There are instructions on the LE wiki for doing so, which I linked a few pages back. Just be sure to capture/extract the EDID when it's actually working
If I connect my Chromebox to the display from boot I get nothing displayed, xrandr via SSH shows no display.
Connecting after boot occasionally triggers the display to work correctly, but not always. Likewise sometimes a reboot triggers the display to work.
Chromebox works perfectly on a 1080p TV and display in LE is manually forced to 1080p50. I'm running latest 7.90 005 LE.
Any ideas how I can fix this, I'd really like to keep the box but this is a right PITA.
(2016-09-30, 14:18)tredman Wrote: At the moment I just cant get it to work full stop, so no chance to grab an EDIDIt can be grabbed not only by Chromebox.
(2016-09-30, 14:29)bbsc Wrote:Good shout. I have a Pi2 I could use.(2016-09-30, 14:18)tredman Wrote: At the moment I just cant get it to work full stop, so no chance to grab an EDIDIt can be grabbed not only by Chromebox.
Why not to connect a laptop via HDMI and use Monitor Asset Manager (if you run Windows)?
(2016-09-30, 14:16)Matt Devo Wrote:(2016-09-27, 19:24)tredman Wrote: Right the odd problem I had with 4k display has returned.sounds like a situation that's a candidate for force-loading the EDID at startup. There are instructions on the LE wiki for doing so, which I linked a few pages back. Just be sure to capture/extract the EDID when it's actually working
If I connect my Chromebox to the display from boot I get nothing displayed, xrandr via SSH shows no display.
Connecting after boot occasionally triggers the display to work correctly, but not always. Likewise sometimes a reboot triggers the display to work.
Chromebox works perfectly on a 1080p TV and display in LE is manually forced to 1080p50. I'm running latest 7.90 005 LE.
Any ideas how I can fix this, I'd really like to keep the box but this is a right PITA.
(2016-09-30, 14:32)bbsc Wrote:Tried running the edid command on my pi to try and grab it then move to the Chromebox. However I just get:(2016-09-30, 14:30)tredman Wrote: Good shout. I have a Pi2 I could use.In any case it will be the very same EDID
##############################################
# LibreELEC #
# http://libreelec.tv #
##############################################
LibreELEC (community) Version: 7.90.005
Kitchen:~ # ls /sys/class/drm
ls: /sys/class/drm: No such file or directory
Kitchen:~ # cat /sys/class/drm/card0-HDMI-A-1/status
cat: can't open '/sys/class/drm/card0-HDMI-A-1/status': No such file or directory
Kitchen:~ # grep ": connected" /var/log/Xorg.0.log | head -n 1grep: /var/log/Xorg.0.log: No such file or directory
Kitchen:~ #
(2016-10-02, 19:40)tredman Wrote:Never mind, managed to get the Chromebox to display and grabbed the edid from it. Rebooted several times and its still working(2016-09-30, 14:16)Matt Devo Wrote:(2016-09-27, 19:24)tredman Wrote: Right the odd problem I had with 4k display has returned.sounds like a situation that's a candidate for force-loading the EDID at startup. There are instructions on the LE wiki for doing so, which I linked a few pages back. Just be sure to capture/extract the EDID when it's actually working
If I connect my Chromebox to the display from boot I get nothing displayed, xrandr via SSH shows no display.
Connecting after boot occasionally triggers the display to work correctly, but not always. Likewise sometimes a reboot triggers the display to work.
Chromebox works perfectly on a 1080p TV and display in LE is manually forced to 1080p50. I'm running latest 7.90 005 LE.
Any ideas how I can fix this, I'd really like to keep the box but this is a right PITA.
(2016-09-30, 14:32)bbsc Wrote:Tried running the edid command on my pi to try and grab it then move to the Chromebox. However I just get:(2016-09-30, 14:30)tredman Wrote: Good shout. I have a Pi2 I could use.In any case it will be the very same EDID
Code:##############################################
# LibreELEC #
# http://libreelec.tv #
##############################################
LibreELEC (community) Version: 7.90.005
Kitchen:~ # ls /sys/class/drm
ls: /sys/class/drm: No such file or directory
Kitchen:~ # cat /sys/class/drm/card0-HDMI-A-1/status
cat: can't open '/sys/class/drm/card0-HDMI-A-1/status': No such file or directory
Kitchen:~ # grep ": connected" /var/log/Xorg.0.log | head -n 1grep: /var/log/Xorg.0.log: No such file or directory
Kitchen:~ #
Any ideas?