Monitor no output (through HDMI to DVI adaptor)

[gam01hr]

Hi everybody,

I bought the pine64 2GB version, than I burn the 'Debian Linux Jessie with Mate GUI Image' on the SD card according to the wiki page.
After powering the board, there is nothing on PC monitor, no action, no output. The system boots fine, serial console by EXP connector works, SSH by 'Putty' works.

Please can you advice me what's wrong? My monitor doesn't have HDMI but have DVI. To connect it I use HDMI-DVI adaptor like this: http://www.officeworks.com.au/shop/offic...-cohddviad
I used to use this adaptor with same PC monitor and with Raspberry PI and it was working.

When I use it with pine64 and plug and unplug the monitor cable I get message (on serial console) like this:
[   55.600051] hdmi_clk_disable_prepare()L176
[   62.557231] hdmi_clk_enable_prepare()L161

---

Also startx doesn't work:
debian@pine64:~$ sudo startx
[sudo] password for debian:


X.Org X Server 1.16.4
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-arm64 aarch64 Debian
Current Operating System: Linux pine64 3.10.102-0-pine64-longsleep #7 SMP PREEMP T Fri Jun 17 21:30:48 CEST 2016 aarch64
Kernel command line: console=tty0 console=ttyS0,115200n8 no_console_suspend disp .screen0_output_mode=720p60 earlycon=uart,mmio32,0x01c28000 mac_addr=36:c9:e3:f1 :b8:05 root=/dev/mmcblk0p2 ro rootwait
Build Date: 11 February 2015 01:19:23AM
xorg-server 2:1.16.4-1 (http://www.debian.org/support)
Current version of pixman: 0.32.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Sat Nov 12 14:40:10 2016
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
modprobe: FATAL: Module g2d_23 not found.
modprobe: FATAL: Module mali_drm not found.
modprobe: FATAL: Module sunxi_cedar_mod not found.
SunxiMaliDRI2_Init: drmOpen failed!

[MarkHaysHarris777]

Hi everybody,

I bought the pine64 2GB version, than I burn the 'Debian Linux Jessie with Mate GUI Image' on the SD card according to the wiki page.
After powering the board, there is nothing on PC monitor, no action, no output. The system boots fine, serial console by EXP connector works, SSH by 'Putty' works.

Please can you advice me what's wrong? My monitor doesn't have HDMI but have DVI. 

Yes;  with that monitor use the hdmi-->vga adpater plug that is carried by the pine store;  I use the adapter with my VGA | DVI  Samsung monitor and works very well.  This will not work on the older monitors that have ONLY vga and are 3:4. 
It does work well with the VGA DVI monitors ( wide screens ) that are LCD flat panels ( either LG or Samsung ).

---

Note:  the hdmi-->DVI cables DO NOT work with these monitors;  however,  the hdmi-->vga adapter plug does work... then just standard vga cable from there ( vga both ends ).

---

Note2:  also,  I want to commend you for verifying 'yourself' that your machine is in fact booting by using the serial console ( serial TTL usb bridge cable ) and then ssh to access the machine even though the hdmi interface is not working yet.   And, I want to emphasize to everyone else that when the pine board apparently does not boot ( this is the cause right here, the hdmi video isn't working but the board really is booting up! )

---

Note3:   moved and pinned thread in  HDMI Port;

[gam01hr]

Mark thank you for help. It seem's that the cabling makes this issue. Visualy checked, one pin (18) in my HDMI-DVI adaptor is cracked. I'll try another Monitor and another adaptor test.

[dkryder]

i had this issue with a couple devices and ended up getting a switch that takes input from device and outputs to a monitor selection.
https://www.amazon.com/gp/product/B017RW...UTF8&psc=1

[MarkHaysHarris777]

i had this issue with a couple devices and ended up getting a switch that takes input from device and outputs to a monitor selection.
https://www.amazon.com/gp/product/B017RW...UTF8&psc=1

wow...

...  that switch is fabulous, if not a little pricey !     Very nice...   

[dkryder]

well, i had a 25 buck gift certificate so that helped. my other option was to replace 2 dvi monitors with a couple cheap hdmi and that figures to be near $200US. i think the biggest gain for me was not having to deal with the hassle factor of swapping out 2 monitors between 4 devices. it is now done by a remote. so that fact helps me rationalize the price.

[gam01hr]

I bought new HDMI to DVI-D cable and tried but still no output to monitor (Samsung SyncMaster 920BM)
I have tried my old Raspberry Pi A+ as well with the same cable and monitor and it was working properly.
What's wrong with my pine64? Anyone does have 'DVI-D plug' monitor connected directly to pine64 by HDMI cable or reduction ?
Is there something wrong with the Linux config?
Here is log
debian@pine64:~$ dmesg | grep -i "disp"
[ 0.000000] Kernel command line: console=tty0 console=ttyS0,115200n8 no_console_suspend disp.screen0_output_mode=720p60 earlycon=uart,mmio32,0x01c28000 mac_addr=36:c9:e3:f1:b8:05 root=/dev/mmcblk0p2 ro rootwait
[ 7.525863] [DISP]disp_module_init
[ 7.526275] [DISP] disp_boot_para_parse,line:301:of_property_read disp.boot_disp fail
[ 7.526299] [DISP] boot_disp:0x0
[ 7.526874] [DISP] disp_sys_script_get_item,line:193:of_find_compatible_node allwinner,sunxi-lcd1 fail
[ 7.527033] [DISP] disp_sys_script_get_item,line:193:of_find_compatible_node allwinner,sunxi-lcd1 fail
[ 7.527191] [DISP] disp_sys_script_get_item,line:193:of_find_compatible_node allwinner,sunxi-lcd1 fail
[ 7.528284] [DISP] disp_boot_para_parse,line:301:of_property_read disp.fb_base fail
[ 7.528307] [DISP] fb_base:0x0
[ 7.593930] [DISP]disp_module_init finish
[ 10.828771] [DISP] disp_boot_para_parse,line:301:of_property_read disp.boot_disp fail
[ 10.843032] [DISP] boot_disp:0x0
[ 11.577377] [DISP] disp_device_attached_and_enable,line:159:attched ok, mgr0<-->device1, type=4, mode=10
[ 12.052308] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[ 12.067744] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 12.790324] systemd[1]: Starting Initialize Sunxi disp2 HDMI output mode...
[ 13.427482] systemd[1]: Started Initialize Sunxi disp2 HDMI output mode.
[ 18.901255] [DISP] disp_ioctl,line:1558:para err in disp_ioctl, cmd = 0x0,screen id = 65536

Please could you try this $dmesg | grep -i "disp" on you board and share result?

[gam01hr]

I'm reading this thread: http://forum.pine64.org/showthread.php?tid=1127
@aminhb: In case you want to use Linux then check whether your display supports any of the following resolutions:
Code:
480i
576i
480p
576p
720p50
720p60
1080i50
1080i60
1080p24
1080p50
1080p60

Does this mean I cannot use 'Debian Linux Jessie with Mate GUI Image' and 4:3 Monitor (1280x1024)?

[dkryder]

monitors are funky. you *should* be able to get 720p . that translates to 1280x720.

[pfeerick]

Does this mean I cannot use  'Debian Linux Jessie with Mate GUI Image' and 4:3 Monitor (1280x1024)?

Probably not using the DVI, as those are the resolutions the pine64 is capable of outputting (or are currently supported anyway). However, your monitor also supports VGA input - try using that instead. I have a cheap (eBay special) powered HDMI to VGA adapter (which is very similar to the Comsol HDMI to VGA adapter sold at OfficeWorks, but was a lot cheaper), and that works with the pine64 regardless of the fact that it is current set to 1080p HDMI output - the display went to its 1280x1028 native resoltuion and just looks squashed, but you could improve that either using the sunxi-disp-tool or a suitable uEnv.txt entry to set a lower resoution 720p - it will still be squashed as it is still a widescreen resolution on a 4:3 display.

Before trying the VGA adapter, try the 720p resolution (set disp.screen0_output_mode=1280x720p60 in the extraargs of your uEnv.txt or use the sunxi-disp-tool), and see if your monitor will accept that, as it is within it's resolution range, but it may not be a supported mode.