cat /boot/config.txt
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_ignore_cec_init=1
gpu_mem_1024=256
vcgencmd set_logging level=2097152
level=2097152
vcdbg log msg | paste-log
debug_sym: OpenVideoCoreMemoryFileWithOffset: Unable to open ‘/dev/vc-mem’: Permission denied(13)
Unable to open videocore memory access: -13
i noticed that the mointor remains black if i plug the hdmi cable after boot on the pi.
Do sudo vcdbg log msg | paste-log.
sudo vcdbg log msg | paste-log
001082.939: HDMI:EDID version 1.3, 1 extensions, screen size 60x34 cm
001083.004: HDMI:EDID features - videodef 0x80 !standby !suspend active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
001083.098: HDMI:EDID found preferred DMT detail timing format: 1920x1200p @ 60 Hz (68)
001083.139: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
001083.237: HDMI:EDID standard timings block x 8: 0xD100 81C0 0101 0101 0101 0101 0101 0101
001083.291: HDMI:EDID found DMT format: code 69, 1920x1200p @ 60 Hz (16:10) in standard timing 0
001083.345: HDMI:EDID found DMT format: code 85, 1280x720p @ 60 Hz (16:9) in standard timing 1
001096.359: HDMI:EDID parsing v3 CEA extension 0
001096.396: HDMI:EDID monitor support - underscan IT formats:no, basic audio:yes, yuv444:yes, yuv422:yes, #native DTD:1
001096.436: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
001096.479: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
001096.520: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
001096.563: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
001096.597: HDMI:EDID found CEA format: code 4, 1280x720p @ 60Hz (native)
001096.623: HDMI:EDID does not understand CEA format code 0
001096.644: HDMI:EDID does not understand CEA format code 0
001096.668: HDMI:EDID does not understand CEA format code 0
001096.690: HDMI:EDID does not understand CEA format code 0
001096.713: HDMI:EDID does not understand CEA format code 0
001096.735: HDMI:EDID does not understand CEA format code 0
001096.758: HDMI:EDID does not understand CEA format code 0
001096.780: HDMI:EDID does not understand CEA format code 0
001096.804: HDMI:EDID does not understand CEA format code 0
001096.826: HDMI:EDID does not understand CEA format code 0
001096.849: HDMI:EDID does not understand CEA format code 0
001096.872: HDMI:EDID does not understand CEA format code 0
001096.895: HDMI:EDID does not understand CEA format code 0
001096.917: HDMI:EDID does not understand CEA format code 0
001096.940: HDMI:EDID does not understand CEA format code 0
001096.962: HDMI:EDID does not understand CEA format code 0
001096.986: HDMI:EDID does not understand CEA format code 0
001097.037: HDMI:EDID found audio format 2 channels PCM, sample rate: 32|44|48 kHz, sample size: |20|24 bits
001097.056: HDMI:EDID found HDMI VSDB length 5
001097.083: HDMI:EDID HDMI VSDB has physical address 1.0.0.0
001097.099: HDMI:EDID HDMI VSDB has no extension fields
001097.144: HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
001097.243: HDMI:EDID filtering out DMT format: 1920x1200p @ 60 Hz (69) with pixel clock 193 MHz and hfp:136 hs:200 hbp:336
001097.306: HDMI:EDID preferred mode remained as DMT (68) 1920x1200p @ 60 Hz with pixel clock 154 MHz
001108.063: HDMI:Setting property pixel encoding to Default
001108.083: HDMI:Setting property pixel clock type to PAL
001108.101: HDMI:Setting property content type flag to No data
001108.120: HDMI:Setting property fuzzy format match to enabled
001287.349: hdmi: HDMI:>>>>>>>>>>>>>Rx sensed, reading EDID<<<<<<<<<<<<<
001299.510: hdmi: HDMI:EDID version 1.3, 1 extensions, screen size 60x34 cm
001299.581: hdmi: HDMI:EDID features - videodef 0x80 !standby !suspend active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
001299.680: hdmi: HDMI:EDID found preferred DMT detail timing format: 1920x1200p @ 60 Hz (68)
001299.726: hdmi: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
001299.827: hdmi: HDMI:EDID standard timings block x 8: 0xD100 81C0 0101 0101 0101 0101 0101 0101
001299.886: hdmi: HDMI:EDID found DMT format: code 69, 1920x1200p @ 60 Hz (16:10) in standard timing 0
001299.946: hdmi: HDMI:EDID found DMT format: code 85, 1280x720p @ 60 Hz (16:9) in standard timing 1
001312.964: hdmi: HDMI:EDID parsing v3 CEA extension 0
001313.007: hdmi: HDMI:EDID monitor support - underscan IT formats:no, basic audio:yes, yuv444:yes, yuv422:yes, #native DTD:1
001313.053: hdmi: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
001313.098: hdmi: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
001313.145: hdmi: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
001313.188: hdmi: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
001313.229: hdmi: HDMI:EDID found CEA format: code 4, 1280x720p @ 60Hz (native)
001313.256: hdmi: HDMI:EDID does not understand CEA format code 0
001313.283: hdmi: HDMI:EDID does not understand CEA format code 0
001313.309: hdmi: HDMI:EDID does not understand CEA format code 0
001313.336: hdmi: HDMI:EDID does not understand CEA format code 0
001313.361: hdmi: HDMI:EDID does not understand CEA format code 0
001313.388: hdmi: HDMI:EDID does not understand CEA format code 0
001313.414: hdmi: HDMI:EDID does not understand CEA format code 0
001313.440: hdmi: HDMI:EDID does not understand CEA format code 0
001313.465: hdmi: HDMI:EDID does not understand CEA format code 0
001313.491: hdmi: HDMI:EDID does not understand CEA format code 0
001313.517: hdmi: HDMI:EDID does not understand CEA format code 0
001313.544: hdmi: HDMI:EDID does not understand CEA format code 0
001313.568: hdmi: HDMI:EDID does not understand CEA format code 0
001313.595: hdmi: HDMI:EDID does not understand CEA format code 0
001313.621: hdmi: HDMI:EDID does not understand CEA format code 0
001313.647: hdmi: HDMI:EDID does not understand CEA format code 0
001313.672: hdmi: HDMI:EDID does not understand CEA format code 0
001313.729: hdmi: HDMI:EDID found audio format 2 channels PCM, sample rate: 32|44|48 kHz, sample size: |20|24 bits
001313.750: hdmi: HDMI:EDID found HDMI VSDB length 5
001313.778: hdmi: HDMI:EDID HDMI VSDB has physical address 1.0.0.0
001313.796: hdmi: HDMI:EDID HDMI VSDB has no extension fields
001313.844: hdmi: HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
001313.950: hdmi: HDMI:EDID filtering out DMT format: 1920x1200p @ 60 Hz (69) with pixel clock 193 MHz and hfp:136 hs:200 hbp:336
001314.019: hdmi: HDMI:EDID preferred mode remained as DMT (68) 1920x1200p @ 60 Hz with pixel clock 154 MHz
001314.042: hdmi: HDMI: hotplug attached with HDMI support
001314.113: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
001316.580: hdmi: HDMI: power_on to DMT mode WUXGA rb
001319.753: hdmi: HDMI: Action callback added to queue to happen at frame 0
001336.730: *** Restart logging
001338.307: Read command line from file ‘cmdline.txt’
root=/dev/mmcblk0p2 rootfstype=ext4 rootwait quiet osmcdev=rbp1
001839.900: Loading ‘kernel.img’ to 0x8000 size 0x7069b0
001839.943: No kernel trailer (run mkknlimg to fix) - assuming DT-capable
001842.778: Loading ‘bcm2708-rpi-b.dtb’ to 0x70e9b0 size 0x33a1
001890.153: dtparam: uart0_clkrate=3000000
001926.878: dtparam: arm_freq=950000000
001928.994: Unknown dtparam ‘arm_freq’ - ignored
001929.033: dtparam: core_freq=450000000
001936.304: dtparam: cache_line_size=32
001946.669: Device tree loaded to 0x16fec700 (size 0x3807)
001947.758: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined
003617.859: vchiq_core: vchiq_init_state: slot_zero = 0x56880000, is_master = 1
003621.537: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
003625.674: TV service:host side not connected, dropping notification 0x00000002, 0x00000002, 0x00000044
028576.409: hdmi: HDMI:Setting property pixel clock type to PAL
028576.587: hdmi: HDMI: power_on to DMT mode WUXGA rb
028576.622: hdmi: HDMI: Action detach added to queue to happen at frame 1633
028576.635: hdmi: HDMI: Action change_mode added to queue to happen at frame 1633
028576.648: hdmi: HDMI: Action attach added to queue to happen at frame 1633
028576.663: hdmi: HDMI: Action start_mode added to queue to happen at frame 1633
028576.678: hdmi: HDMI: Action callback added to queue to happen at frame 1635
028576.694: hdmi: HDMI: Action stop_3d_mode added to queue to happen at frame 1635
028576.708: hdmi: HDMI: Action unmute added to queue to happen at frame 1636
http://paste.osmc.io/eseyaracar
I will take a stab at adding support for this mode today.
Your display doesn’t advertise 24p mode though, which means video won’t be playing at the correct fps.
ok cool, thank you very much for you support sam.
does that mean i can do a dist-upgrade from the development-source soon?
is that a problem?
I will let you know when I have something to test.
It depends how good your eyes are, if you are used to it with a Pi, then I guess it will be ok, but you may want to consider a better display in the future. I’m quite surprised they’d call it Cinema Display if it can’t do 24Hz, but maybe it’s the adapter.
ok, the display is old but it should be good quality so i assume it has to do with the adapter.
ok i will try to wait patiently 
Took a stab at this this afternoon:
I will build this for you and let you know when it’s ready.
If possible, can you get the serial number or model number of the display. I googled the Cinema Display but it seems like there are a lot of models around.
Sam
Hi
Try running sudo apt-get update && sudo apt-get dist-upgrade again now. I can’t guarantee the modelines are accurate but would be good to know what modes are advertised now. The issue may be the adapter however.
Sam
Hi Sam
something went wrong with the installation. now i am not able to boot up anymore.
i tried to reinstall the device, but somehow the device does not seem to recognize my sdcards (i tried two of them). I did everything i found on the forum to get the installer running, switched sd-cards, re-downloaded the image, copied the image manually using dd command - nothing worked. if i check on the sd-card there are still the two files but no installer.log. i think the device ist completely ignoring the sd-cards. i am a little disappointed i have to admit … Is it possible that the device is broken already or does the installer which is supposed to grab the image from the card not work properly? honestly i also dont get why you would make an internal storage with no other possibility to get access than this faulty (?) installer anyway. wouldnt it be much easier to handle this exactly like the Pi does, with all the possibility to do full disk backups and restores with dd? also i do not understand why you sell a micro-sd in your shop even if the vero has a normal size sd-reader. is there another slot somewhere i did not notice i could try (a descriptive image of the hardware ports somewhere on the homepage would be nice) ?
bendsch
Hi
I’m sorry to hear you are disappointed. The primary use case for the Vero 2 is on a TV. This is the first report of trying to get a Cinema Display to work, so I am appreciative of your patience.
It’s not really possible for the Vero 2 to break in the manner you describe. The first way to check what’s going on would be to connect it to a TV or another display. Until you get a working picture, it is hard to speculate what’s going on. For example, your IP address may have just changed…
How have you concluded that the installer is faulty? We test each image before we release it on the website. Regarding the use of dd, you can still do this to make backups of your Vero 2, I don’t really understand the question here
We sell micro SD cards on the Store because we sell storage that can work in the Vero OR the Raspberry Pi. Our SD cards come with an adapter for full sized cards so they can be used in PCs or the Vero 2 easily.
i forgot to mention that i got another monitor to do all this re-installation thing.
With “installer” i mean the script/program that should be running on the vero when i boot up with a prepared sd-card. if i try to boot up the screen shows the image above.
hmm, i dont exactly understand how i can clone a backed up image to the internal storage. i allways have to use the installer to re-format the internal drive, don’t i?
Ok i understand that. the aim of my question here was to find out if there maybe is another slot or card reader i could try.
Bendsch
We will get you up and running, don’t worry.
The error above can occur if you get sudden powerloss which can cause some corruption. You may have pulled the plug because you couldn’t shut down properly (no screen to see anything).
Not really – as you see above, you are in ‘recovery mode’. You can boot to that any time by holding SHIFT. You could then attach an SD card or even a USB drive and use dd if=/dev/vero-nand/root of=/dev/sda (or vice versa) to take backups. You also need to backup /dev/boot to backup the kernel.
Sam
Do you have a link to the SD card you are using?
i think it worked now, but it happened while screen was black (i did not see the installer come up). anyway on the sd-card now there is the following log:
Thu Jan 1 00:00:06 1970 Starting OSMC installer
Thu Jan 1 00:00:11 1970 Detecting device we are running on
Thu Jan 1 00:00:11 1970 Mounting boot filesystem
Thu Jan 1 00:00:11 1970 Trying to mount to MNT_BOOT (/mnt/boot)
Thu Jan 1 00:00:11 1970 Using device->boot: /dev/mmcblk0p1 and FS: fat32
Thu Jan 1 00:00:11 1970 No preseed file was found
Thu Jan 1 00:00:11 1970 Creating root partition
Thu Jan 1 00:00:13 1970 Calling fmtpart for partition /dev/vero-nand/root and fstype ext4
Thu Jan 1 00:00:24 1970 Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=2 blocks, Stripe width=1024 blocks
415344 inodes, 1660928 blocks
83046 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1702887424
51 block groups
32768 blocks per group, 32768 fragments per group
8144 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Allocating group tables: 0/51 done
Writing inode tables: 0/51 done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: 0/51 done
Thu Jan 1 00:00:24 1970 From a root partition of /dev/vero-nand/root, I have deduced a base device of /dev/vero-nand/roo
Thu Jan 1 00:00:24 1970 Mounting root
Thu Jan 1 00:00:24 1970 Trying to mount to MNT_ROOT (/mnt/root)
Thu Jan 1 00:00:24 1970 Using device->root: /dev/vero-nand/root
Thu Jan 1 00:00:24 1970 Extracting files to root filesystem
Thu Jan 1 00:00:24 1970 Starting extract progress…
Thu Jan 1 00:01:37 1970 Extraction of root filesystem completed
Thu Jan 1 00:01:37 1970 Configuring bootloader
Thu Jan 1 00:01:37 1970 Configuring bootloader: moving /boot to appropriate boot partition
Thu Jan 1 00:01:46 1970 Configuring boot cmdline
Thu Jan 1 00:01:46 1970 Configuring /etc/fstab
Thu Jan 1 00:01:46 1970 Successful installation. Dumping log and rebooting system
i am not sure if everything went right …
It looks like the installation was successful. Are you saying that the screen is still black? I’m not talking about the Cinema Display here but the screen that you used before when you showed me the recovery screen.
It looks like i am back up again. on the other display everything looks ok, so big thank you so far.
Now i attached the cinema display again, installed the new distribution from the developer repo and did a reboot. unfortunately the screen is still black.
I also tried to switch display and back while running as you suggested but without luck so far (no picture).
Please let me know if i should do some further testing.
Bendsch
