[Matt Devo]

I ran the commands & it was set to "Automatic". I was able to change the Broadcast RGB modes as u suggested, but they don't stick on reboot. So I am unable to confirm if forcing them prevents the TV from re-detecting the input as "PC" When I reboot, it returns to automatic. Im willing to do anymore testing on the issue you may have, thanks for spending time on looking for a fix!

xrandr --props output

as I said, put the command in an autostart script

try both of the settings I mentioned before (individually)

[Chilll]

I confirmed the settings stuck with the auto-start script but unfortunately it still renamed them to "PC"

[Matt Devo]

I confirmed the settings stuck with the auto-start script but unfortunately it still renamed them to "PC"

what if you power toggle the display after the Chromebox is booted?

also, have you looked/posted on the avsforums? if anyone knows, those guys would

[Matt Devo]

I confirmed the settings stuck with the auto-start script but unfortunately it still renamed them to "PC"

what if you power toggle the display after the Chromebox is booted?

also, have you looked/posted on the avsforums? if anyone knows, those guys would

ok did some searching for you on AVS, seems that if you rename the HDMI input label from 'PC' to something else (eg, 'Kodi') and/or change the input type, and that should prevent it from auto-switching to PC mode. For more info on PC mode, see: http://www.avsforum.com/forum/166-lcd-fl...hread.html

[Chilll]

I confirmed the settings stuck with the auto-start script but unfortunately it still renamed them to "PC"

what if you power toggle the display after the Chromebox is booted?

also, have you looked/posted on the avsforums? if anyone knows, those guys would

It will re select "PC" as the input if u power cycle the display. Yes I've searched rtings & several of the big avs threads on my TV model & saw some users mentioned having the same problem, but no one every replied back with a solution. They don't mention what media player they were using, but I tested my odroid c2 & rpi2 which neither had this problem. I dont have any other players to test it with.

I tried changing the "PC" input name to Kodi, once I powered both Chromebox & TV down then back on. It renamed the input back to "PC" everytime

[Matt Devo]

It will re select "PC" as the input if u power cycle the display. Yes I've searched rtings & several of the big avs threads on my TV model & saw some users mentioned having the same problem, but no one every replied back with a solution. They don't mention what media player they were using, but I tested my odroid c2 & rpi2 which neither had this problem. I dont have any other players to test it with.

I tried changing the "PC" input name to Kodi, once I powered both Chromebox & TV down then back on. It renamed the input back to "PC" everytime

sounds like Samsung has some serious firmware bugs related to that feature unfortunately

[Diodato]

I am having the same issue with my KS8000, Yamaha RX-A550 & Asus Chromebox running both Legacy/UEFI & Intel-openelc 6 / Libreelec 7.02. I tried flashing the UEFI firmware after having used the legacy firmware for years & can confirm the TV still resets the input to PC. I also picked up a JU7100 from 2015 & did not have this issue, but had to upgrade with the KS8000 sale that has been going on recently. The KS8000 is only TV of about 10 that I have tested it with that has this problem.

I swapped the Chromebox with an odroid c2 & it did not reset the input, so it is an isolated issue with the Chromebox, KS8000 & A/V receiver. I love my Chromebox & hopefully can get this resolved, but I don't think it will & my only solution is to replace it with a different box. Its worth the time saved having to select the input & reset all devices to get picture formatted properly with Movie mode selected every time I want to watch TV. At least with more 4K HEVC coming down the pipes, the Chromebox was going to be on its way out in the near future but not so soon . It served me well for few years thanks again to Mr Chromebox!

I am in the same boat. I don't have any AVR so my Chromebox (CN60) running LibreELEC is directly connected to the Samsung KS8000 (European).
Happens on all 4 HDMI inputs even though HDMI2 is suggested by Samsung for PC connection (labelled HDMI2/DVI).

If LibreElec's GUI is set to 1920x1080p @59.94 or @60 the TV recognizes the signal as coming from a PC and will disable certain viewing modes and many picture settings. And it is completely independent of the Limited or Full RGB settings of Kodi.
Any other refresh rate for progressive full HD or any refresh frequency for interlaced will not trigger the "PC mode".
Of course the same applies when Kodi automatically changes the refresh rate depending on the video material (and if Kodi is set to change the display refresh rate). So any "interlaced" video file (29.97/30/59.97/60) will cause the TV to activate the "PC signal" mode.


This happens only with the Chromebox.

• my PS3 outputs 1920x1080@60p and the TV doesn't switch to "PC mode".
  
• my Pioneer BDP-140 BD player outputs 1920x1080@60p and the TV doesn't switch to "PC mode".
  
• my Wii U player outputs 1920x1080@60p (limited RGB) and the TV doesn't switch to "PC mode".
  

I can play with the HDMI settings of these devices: resolution, interlaced/progressive, refresh rate, full/limited scale and the TV will not recognize the source as a "PC". Only Chromebox (tested both Jarvis/Krypton).

ok did some searching for you on AVS, seems that if you rename the HDMI input label from 'PC' to something else (eg, 'Kodi') and/or change the input type, and that should prevent it from auto-switching to PC mode. For more info on PC mode, see: http://www.avsforum.com/forum/166-lcd-fl...hread.html

Thanks for your effort but renaming or changing the icon for a specific input doesn't matter. You can't set the "tupe" only name and icon. As soon as the Chromebox outputs Full HD @ 59.97 or @60Hz the TV renames the HDMI input to "PC" and changes accordingly the icon.
I'm on the latest firmware 1142, maybe this was a solution with previous firmwares.
Also the North American KS8000 model is different than the European. Thanks Samsung for the confusing model names....

sounds like Samsung has some serious firmware bugs related to that feature unfortunately

Well, I wouldn't blame Samsung so fast. Like I wrote above this happens only with a Chromebox and does not happen with three other devices.

Any ideas?

[squidly1]

hi all

so I messed up !!

Used Matt's script a few years back to install openelec in dual boot mode on my Asus chrombox. Recently changed to Libreelec. Only having one problem - that being HDMI handshake ( I think)
whereas on occasion when turning on the system Chromebox- Sony AV Receiver - TV , the tv is blank. Have to power off/on the Chromebox - the unit reboots and all is ok till next time.

I found a "solution" using a custom EDID http://wiki.openelec.tv/index.php/Config...#tab=Intel

of course I screwed up royally and now when it boots I get

Error in mount_flash: most_common: could not mount LABEL=SYSTEM
cant acess tty job control turned off

I did take a screen shot of a file this procedure edited called extlinux.conf .
My original setting was boot-LABEL-KERN-C disk-LABEL-ROOT-C tty quiet
the instructions had me change it to boot=LABEL=System disk=LABEL=Storage ssh quiet

so my questions are..
is there any way from chromos to edit or delete the files from libreelec ?
if not or still will not boot whats the best way to proceed? run the script again ?

thanks ever so much

[Matt Devo]

hi all

so I messed up !!

Used Matt's script a few years back to install openelec in dual boot mode on my Asus chrombox. Recently changed to Libreelec. Only having one problem - that being HDMI handshake ( I think)
whereas on occasion when turning on the system Chromebox- Sony AV Receiver - TV , the tv is blank. Have to power off/on the Chromebox - the unit reboots and all is ok till next time.

I found a "solution" using a custom EDID http://wiki.openelec.tv/index.php/Config...#tab=Intel

of course I screwed up royally and now when it boots I get

Error in mount_flash: most_common: could not mount LABEL=SYSTEM
cant acess tty job control turned off

I did take a screen shot of a file this procedure edited called extlinux.conf .
My original setting was boot-LABEL-KERN-C disk-LABEL-ROOT-C tty quiet
the instructions had me change it to boot=LABEL=System disk=LABEL=Storage ssh quiet

so my questions are..
is there any way from chromos to edit or delete the files from libreelec ?
if not or still will not boot whats the best way to proceed? run the script again ?

thanks ever so much

you can either mount the partition and edit the file from ChromeOS (using vim), or just reinstall using the script. To do the former, from a terminal shell in ChromeOS:

Code:

mkdir /tmp/system
sudo mount /dev/sda6 /tmp/system
sudo vim /tmp/system/extlinux.conf
(edit / save file)
sudo umount /tmp/system
sudo reboot

changing the volume labels was unnecessary / broke things; all you needed to do was add the parts related to the EDID loading

[BoxFreak]

I suspect my second Asus Chromebox (CN60) is somehow broken. After clean install (tried several times with OE and LE) system just hangs randomly. Hanging doesn't seem to be related to any activity I'm doing, and it can happen while watching video, or while accessing Kodi menus and settings. How to troubleshoot what could be the faulty part of hardware? I can always try rams and ssd from my other box, but is there some easier way? I've already tried with different PSU's and WLAN / Ethernet, but it doesn't matter at all.

[squidly1]

hi all

so I messed up !!

Used Matt's script a few years back to install openelec in dual boot mode on my Asus chrombox. Recently changed to Libreelec. Only having one problem - that being HDMI handshake ( I think)
whereas on occasion when turning on the system Chromebox- Sony AV Receiver - TV , the tv is blank. Have to power off/on the Chromebox - the unit reboots and all is ok till next time.

I found a "solution" using a custom EDID http://wiki.openelec.tv/index.php/Config...#tab=Intel

of course I screwed up royally and now when it boots I get

Error in mount_flash: most_common: could not mount LABEL=SYSTEM
cant acess tty job control turned off

I did take a screen shot of a file this procedure edited called extlinux.conf .
My original setting was boot-LABEL-KERN-C disk-LABEL-ROOT-C tty quiet
the instructions had me change it to boot=LABEL=System disk=LABEL=Storage ssh quiet

so my questions are..
is there any way from chromos to edit or delete the files from libreelec ?
if not or still will not boot whats the best way to proceed? run the script again ?

thanks ever so much

you can either mount the partition and edit the file from ChromeOS (using vim), or just reinstall using the script. To do the former, from a terminal shell in ChromeOS:

Code:

mkdir /tmp/system
sudo mount /dev/sda6 /tmp/system
sudo vim /tmp/system/extlinux.conf
(edit / save file)
sudo umount /tmp/system
sudo reboot

changing the volume labels was unnecessary / broke things; all you needed to do was add the parts related to the EDID loading

Thanks Matt ! They don't call ya Mister Chromebox for nothing. Hardest part was remembering vim commands. Note to self - a little knowledge is dangerous

[Matt Devo]

Thanks Matt ! They don't call ya Mister Chromebox for nothing. Hardest part was remembering vim commands. Note to self - a little knowledge is dangerous

I can't ever remember anything besides :wq!, have to look it up every time I use it

[ggp759]

Hi. I have a Asus Chromebox with libreelec build from May 2016. I tried to update to a recent build and i got the message that i have to resize the partition. I read on the wiki that i have to do a clean install from a usb. I created the usb with the Libreelec tool but how do i force it to boot from a usb and do a clean install? Upon restarting it boots from hard disk again. Any help? greatly appreciated. Thanks.

[Matt Devo]

Hi. I have a Asus Chromebox with libreelec build from May 2016. I tried to update to a recent build and i got the message that i have to resize the partition. I read on the wiki that i have to do a clean install from a usb. I created the usb with the Libreelec tool but how do i force it to boot from a usb and do a clean install? Upon restarting it boots from hard disk again. Any help? greatly appreciated. Thanks.

press ESC when prompted to bring up the boot menu, then select the USB from the list

[ggp759]

Hi. I have a Asus Chromebox with libreelec build from May 2016. I tried to update to a recent build and i got the message that i have to resize the partition. I read on the wiki that i have to do a clean install from a usb. I created the usb with the Libreelec tool but how do i force it to boot from a usb and do a clean install? Upon restarting it boots from hard disk again. Any help? greatly appreciated. Thanks.

press ESC when prompted to bring up the boot menu, then select the USB from the list

ok got it. thanks