CoreELEC 8.95.4.42

here

CoreELEC (official): 8.95.4.42 (S912.arm)
CoreELEC-WZ:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/rawedid
00ffffffffffff0011ee530001010101001b0103809051780a0dc9a05747982712484c2108008180a9c0714fb300010101010101010108e80030f2705a80b0588a009f295300001e023a801871382d40582c45009f295300001e000000fc0044454e4f4e2d4156520a202020000000fd00173e0e883c000a2020202020200135020379f05f61605d5e5f621f101405130420223c3e12160307111502060165660e230f24350f7f073d1ec01507505f7e03570603677e035f7e01835f00006e030c003500b83c2f00800102030467d85dc401788001e50f03000006e3060d01eb0146d000450b908660768fe305df01e200cbe61146d000f00100000000000025

Im a little bit confused. In a further Version i dont have the 30hz Problem in Kodi. Before 8.95.4 i have >4K60Hz in Kodi.
On TV and AVR i dont have change some Settings. So i think it is a Problem (?) with new Coreelec or Kodi >Feature.

Whats your Opinion?

Same issue here. My TV is 2017. Before 8.95.4 it worked fine. Problem sticking at 8.95.3 is that you cannot install some addons using the older version because of dependency issues.

I just looking at the settings on my Denon AVR to see if there is anything i can change

Hello,

i became a test version of coreelec. This Version works very fine.
The Version 9.95.5 will be stable within i hink.

I have checked my Denon AVR X2300W and i believe any video conversion is off.

I think you have to set “Video Mode” to “Bypass”!

Paul

@cdu13a

Result! Issue resolved in CoreELEC-S905.arm-9.0-devel-1541942153.tar (funhouse).

Can confirm 2160p@60hz and no black screen issues running through Denon AVR

Nice work

You need to set your AVR to “Bypass” as paul69 said, otherwise you may not get HDR and won’t get 10bit output.

I tried on bypass and it made no difference to the 2160p@60hz, switched back to auto but will set it to bypass to make sure HDR works correctly.

That development release works on Auto for 2160p@60hz through my Denon AVR.

Thanks

It would be interesting to know whether it’ll also switch into 10 bit mode correctly.
What you should see is a 10bit YUV422 signal when viewing 4K HDR/10 bit content.

@TheCoolest

Its looking good so far. See https://discourse.coreelec.org/t/no-60hz-at-3840x2160p/2300

Hi.

Works fine with mecool k1 pro -> Yamaha RX-A3070 -> LG65UH6159, HDMI pass through on Amp, Deep Colour checked on TV.

Problem with 2160p/50Hz solved, thanks.

##############################################

CoreELEC

https://coreelec.org

##############################################

CoreELEC (official): 8.95.4.42 (S905.arm)
CoreELEC:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/disp_cap
480p60hz
576p50hz
720p60hz
1080i60hz
1080p60hz
720p50hz
1080i50hz
1080p30hz
1080p50hz
1080p25hz
1080p24hz
2160p30hz
2160p25hz
2160p24hz
smpte24hz
2160p50hz
2160p60hz
2160p50hz420
2160p60hz420
CoreELEC:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/edid
Rx Brand Name: GSM
Rx Product Name: LG
Manufacture Week: 1
Manufacture Year: 2016
Physical size(cm): 160 x 90
EDID Version: 1.3
EDID block number: 0x1
blk0 chksum: 0xae
Source Physical Address[a.b.c.d]: 3.3.0.0
YCC support 0x03, VIC (native 255):
ColorDeepSupport 0xb8 10/12/16/Y444 1/1/0/1
97 96 16 31 4 19 5 20 3 2 18 32 33 34 21 1 93 94 95 98 95 94 93 98 353 352
Audio {format, channel, freq, cce}
{1, 1, 0x7f, 0x07}
{1, 7, 0x7f, 0x07}
{2, 5, 0x07, 0x00}
{7, 6, 0x1f, 0x00}
{9, 5, 0x02, 0x00}
{10, 7, 0x06, 0x01}
{12, 7, 0x7e, 0x01}
{11, 7, 0x7e, 0x03}
Speaker Allocation: 0x5f
Vendor: 0xc03
MaxTMDSClock1 300 MHz
Vendor2: 0xd85dc4
MaxTMDSClock2 600 MHz
ColorMetry: 0xc0
SCDC: 1
RR_Cap: 0
LTE_340M_Scramble: 0
HDR DeepColor
checkvalue: 0xae870000
CoreELEC:~ #

Where can I find the version with Kodi v18 Leia (Beta 5)?

Take a look at the nightly thread:
https://discourse.coreelec.org/t/nightly-builds/

Hello-

First of all, thanks for CoreElec - Awesome work!

I found the correct dtb file for my box, booted to latest [CoreELEC 8.95.4.3 and could see the mouse cursor load, and limitations of the pop-up I know was there, but screen never changes from black.

Using Samsung 22inch monitor, resolution detected is 1080p. I also tried v 4.42 (latest test released 8 days ago) and had the same issue. Just for kicks, I tried multiple DTB files in same class, all boot black screen.

I downgraded (started fresh) to v 8.9.5.0 and it booted no problem in to the interface,

perhaps the boot to black screen issue is still prevalent for obscure boxes? T95N 1G/8G gxl_p212.dtb

I am happy to help resolve if you would like information, logs etc…

SirRedZ

The problem is not with the DTB, it’s with 4.3 and 4.42, please read the thread.

Hello. – Thanks for moving my post.

I should have mentioned originally, I did in fact try the latest test release before posting, same issue.
I also tried with analog video connection / hdmi on a 32inch Samsung TV.

All connections showed CE logo, but after only mouse on activity (but I could see the borders of the pop-up hiding when the mouse hits it stops on the edge.)

Thank you.

SirRedZ

Might be a stupid question, but did you take the DTB file from the device_trees folder on the root of the SD card?

What TV are you using with the box with the HDMI connection?
Can you still SSH into the box after it boots with a black screen?
If you can, read the first post and make sure that you don’t have anything configured that can break things with the new build.
Then post the output from the following commands:

cat /sys/devices/virtual/amhdmitx/amhdmitx0/disp_cap
cat /sys/devices/virtual/amhdmitx/amhdmitx0/edid
cat /sys/devices/virtual/amhdmitx/amhdmitx0/rawedid

Thanks for very quick reply.

I am using Samsung 22inch PC monitor, DVI - HDMI Connection. It is 1080p maximum
(SyncMaster 2233)

No ability to SSH.

I am now going to try the fix posted below.

SirRedZ

Thank you.

How do I do this? No SSH/ftp ability, and USB local on PC does not show that file system (Windows)

I’m stuck!

SrZ

Install Putty, it supports SSH. WinSCP supports SFTP and other file transfer protocols.
But if you can’t SSH into the box your problem is not the same as everyone else’s, unless you have some sort of network problem on the box.