Color depth mismatch after update to 3.14.29-130-osmc

Help and Support Vero 4K / Vero 4K +
1

I have updated my Vero 4K to version 3.14.29-130-osmc and I got a black screen after reboot. I was able to see the splash screen during boot but no video output when Kodi started. Previous version (129) was fine.

After digging into various post in this forum I think that the latest update is forcing my display to use 10bit color depth even it doesn’t support it.

It’s working after I type:
echo '444,8bit' > /sys/class/amhdmitx/amhdmitx0/attr
systemctl restart mediacenter

Is this by a mistake or on purpose? I would need that workaround to persist after reboot.

2

Thanks for the feedback. We will fix that. Meanwhile if you add echo 8bit > /sys/class/amhdmitx/amhdmitx0/attr to rc.local it will persist.

3

Thank you for confirmation. I’ve already convinced my systemd to run the workaround script at boot.

1 Like
4

Just to add to our library, could you post cat /sys/class/amhdmitx/amhdmitx0/edid and cat /sys/class/amhdmitx/amhdmitx0/rawedid for us and remind us the make/models of your gear?

5

Here you are:

cat /sys/class/amhdmitx/amhdmitx0/edid

Rx Brand Name: FUS
Rx Product Name: MYRICA
Manufacture Week: 0
Manufacture Year: 1990
Physical size(cm): 71 x 40
EDID Version: 1.3
EDID block number: 0x0
blk0 chksum: 0xec
Source Physical Address[a.b.c.d]: 0.0.0.0
YCC support 0x00, VIC (native 3):
ColorDeepSupport 0x00 10/12/16/Y444 0/0/0/0
3 4 16
Audio {format, channel, freq, cce}
Speaker Allocation: 0x00
Vendor: 0x0
MaxTMDSClock1 0 MHz
SCDC: 0
RR_Cap: 0
LTE_340M_Scramble: 0

checkvalue: 0x00000000

and

cat /sys/class/amhdmitx/amhdmitx0/rawedid

00ffffffffffff001ab37c0501000000000a0103804728780a0320a75545962411494b2f8c0081c081808bc0010101010101010101011a1d008051d01c2040803500c58f2100001e000000fd00324b1e400b000a202020202020000000fc004d5952494341205633322d310a000000ff003030303030310a20202020202000ec

6

wow, retro!

7

Yep! One of the first LCD panels. Still works at 100% without a glitch.

8

I’m intrigued. Just so I get it right, can you post a full debug log of the startup process, please?

What resolutions are you offered by Kodi? AFAICT, you should only be able to set 720p. 1080p may be offered but ought to fail.

When was this thing made? It appears to be 28 years old!

9

IIRC we add 1990 + year in kernel; so year is probably set to 0 and kernel is adding 1990 to it.

11

It’s Fujitsu-Siemens Myrica V32-1, manufactured in the year 1999. Logs are here.

1 Like
12

Amazing. Claims to be brighter than my 2017 Panasonic 4k. Enjoy!

I will see if we can coax its max resolution of 1080i out of it.

13

Kodi offers the following resolutions (yes, they are the same):
1280x720p
1280x720p

The panel has the maximum resolution of 1366 x 768 pixels.

14

They are 60Hz and 59.9Hz FWIW. Kodi is confused because it’s only sending one EDID block and a 1080i mode isn’t advertised in that. I assume you are connecting via the DVI input.

15

If you have updated to the December release, I would be interested if you can now set the resolution to 1080i on your TV.

16

KODI offers the following resolutions for my TV now:

  • 1280x720p
  • 1920x1080p
  • 1920x1080i

I can set 1920x1080i and it’s working. There is also no need to manually override the color depth to 8bits any more.

Thank you for your assistance.

2 Likes