Hdmi safemode

sam_nazarko · 27 July 2016 11:40

Hi

Unfortunately without a Cinema Display at hand, it’s really hard for me to generate a good, valid modeline for this device. I will see what I can do, but I am not certain that we can get a 1920x1200 mode without having this monitor at hand to test.

In the interim, with the new kernel, it would be good to see if the new mode that I added is at least being selected by the kernel.

Can you run the commands in Hdmi safemode - #8 by sam_nazarko again, and change echo 720p to echo 1200p this time?

bendsch · 27 July 2016 11:56

i already did that and still got no picture.

isn’t it possible to copy the modeline from the Pi?

sam_nazarko · 27 July 2016 11:58

Please post the output

I will check. It should just be DMT mode 68. I copied the generated values but this seems to not work for your display.

Dumping EDID from sudo tvservice -d edid.dat on Pi may help

bendsch · 27 July 2016 12:24

sorry to be a pain, but what output do you mean?

sudo tvservice -d edid.dat
Written 256 bytes to edid.dat

cat edid.dat
???4?`?<"x ?UE?$IK???(<??p?#@0 6D!rQ? n(UĎ!?MDP Adapter
?0K
?
?#qR?# e
rQ? n(UĎ!rQ? n(UĎ!rQ? n(UĎ!rQ? n(U[V!?

sam_nazarko · 27 July 2016 12:30

The output of the commands in the post I linked to (e.g. cat disp_cap).

You need to upload the edid to Dropbox or something, as it’s a binary. You can also email it as an attachment to sam at osmc dot tv.

bendsch · 27 July 2016 12:40

cat /sys/class/display/mode
720p

echo 1200p | sudo tee /sys/class/display/mode
1200p

i sent it to you via email.

sam_nazarko · 27 July 2016 12:43

My guess is the adapter isn’t reporting the 1200p mode correctly, so the kernel is refusing to switch to it.

bendsch · 27 July 2016 12:44

cat /sys/class/amhdmitx/amhdmitx0/disp_cap
720p*

so what could be the reason why it is working on the pi?

sam_nazarko · 27 July 2016 12:52

Not sure – if you are defining a hdmi_mode in config.txt, then it’s being explicitly forced, and the EDID is ignored. I’m not sure why you have to use hdmi_safemode though…

It is hard for me to assess the problem without the monitor or adapter at hand

bendsch · 27 July 2016 12:55

my config.txt is posted here. i realized i don’t even need the safe-mode entry.

sam_nazarko · 27 July 2016 13:06

The EDID you sent me shows:


Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   34 90 60 10 00 00 00 00 2a 13
version:         01 03
basic params:    80 3c 22 78 2a
chroma info:     03 20 a7 55 45 96 24 11 49 4b
established:     00 00 00
standard:        d1 00 81 c0 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:    28 3c 80 a0 70 b0 23 40 30 20 36 00 07 44 21 00 00 1a
descriptor 2:    01 1d 00 72 51 d0 1e 20 6e 28 55 00 c4 8e 21 00 00 1e
descriptor 3:    00 00 00 fc 00 4d 44 50 20 41 64 61 70 74 65 72 0a 20
descriptor 4:    00 00 00 fd 00 30 4b 0b 96 14 00 0a 20 20 20 20 20 20
extensions:      01
checksum:        d2

Manufacturer: MDP Model 1060 Serial Number 0
Made week 42 of 2009
EDID version: 1.3
Digital display
Maximum image size: 60 cm x 34 cm
Gamma: 2.20
DPMS levels: Off
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
Standard timings supported:
  1920x1200@60Hz
  1280x720@60Hz
Detailed mode: Clock 154.000 MHz, 519 mm x 324 mm
               1920 1968 2000 2080 hborder 0
               1200 1203 1209 1235 vborder 0
               +hsync -vsync 
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
               1280 1390 1430 1650 hborder 0
                720  725  730  750 vborder 0
               +hsync +vsync 
Monitor name: MDP
Monitor ranges (GTF): 48-75Hz V, 11-150kHz H, max dotclock 200MHz
Has 1 extension blocks
Checksum: 0xd2 (valid)

CEA extension block
Extension version: 3
31 bytes of CEA data
  Video data block
    VIC 04 1280x720@60Hz (native)
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
    VIC 00 Unknown mode 
  Audio data block
    Linear PCM, max channels 1
    Supported sample rates (kHz): 48 44.1 32
    Supported sample sizes (bits): 24 20 16
  Vendor-specific data block, OUI 000c03 (HDMI)
    Source physical address 1.0.0.0
  Unknown tag 0, length 0 (raw 00)
  Unknown tag 0, length 0 (raw 00)
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
               1280 1390 1430 1650 hborder 0
                720  725  730  750 vborder 0
               +hsync +vsync 
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
               1280 1390 1430 1650 hborder 0
                720  725  730  750 vborder 0
               +hsync +vsync 
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
               1280 1390 1430 1650 hborder 0
                720  725  730  750 vborder 0
               +hsync +vsync 
Detailed mode: Clock 74.250 MHz, 603 mm x 342 mm
               1280 1390 1430 1650 hborder 0
                720  725  730  750 vborder 0
               -hsync -vsync analog composite 
Checksum: 0xe7 (valid)

EDID block does NOT conform to EDID 1.3!
    Detailed block string not properly terminated

I can try and work with this. The monitor seems to advertise that it supports 720p VIC Mode 4, so I am not sure why you cannot get a picture with the 720p mode which is already baked in to the kernel. It would probably be good to see if we can get that working first.

If you set hdmi_mode=4 on your Pi, do you get a 720p image?

bendsch · 27 July 2016 14:29

the pi seems to completely ignore the hmdi_mode=4 setting in the config.txt. i still get a picture with full resolution (1200p).

sam_nazarko · 27 July 2016 14:31

Check how you spelled it.

And paste config.txt

bendsch · 27 July 2016 14:36

arm_freq=950
force_turbo=1
over_voltage=6
core_freq=450
start_x=1
sdtv_aspect=1
disable_overscan=1
gpu_mem_256=112
gpu_mem_512=144
sdram_freq=450
hdmi_mode=4
hdmi_ignore_cec_init=1
gpu_mem_1024=256

its spelled correctly in the config …

sam_nazarko · 27 July 2016 14:37

I think you also need to add hdmi_group = 1 to set CEA modes.

bendsch · 27 July 2016 14:39

ok, now the settings seem to be effective and therefor i get no picture.

sam_nazarko · 27 July 2016 14:41

This seems to suggest that the screen is advertising 720p and 1200p, even though 720p does not work for your display. Weirdly, it seems to advertise the 720p as the preferred / native CEA Mode.

I have generated a 1200p modeline but my suspicion is that the reason it’s not working may be because the monitor or adapter are not reporting the correct supported settings.

Last thing I can think of is maybe you need hdmi_mode=19 (720p50), but it is advertising a preferred mode of 720p60…

bendsch · 27 July 2016 15:10

mode 19 does not work either.

the only two resoltion that work in kodi are:

1920x1200p
640x480p

there are two more showing but they both dont work (means screen becomes black):

720x480p
1280x720

on my macbook i see the following resolutions when connecting the cinema display (they all work):

1920x1200p
1600x1000
1280x800
1024x640

sam_nazarko · 27 July 2016 15:30

I would have to patch Kodi as well to support this modeline, but I need the kernel to switch you in to this mode first.

Can you try this?

sudo -s
systemctl stop mediacenter
echo "1200p" > /sys/class/display/mode
cat /sys/class/display/mode (show output)
journalctl | paste-log

I should be able to add support for 1280x800 for you, but understand if this isn’t ideal.

bendsch · 27 July 2016 15:34

osmc@osmc:~$ sudo -s
root@osmc:/home/osmc# systemctl stop mediacenter
root@osmc:/home/osmc# echo “1200p” > /sys/class/display/mode
root@osmc:/home/osmc# cat /sys/class/display/mode
1200p

root@osmc:/home/osmc# journalctl | paste-log
http://paste.osmc.io/osolotilic