No, the Pi Zero does not support ethernet over HDMI.
Unfortunately the schematics for the Pi Zero are not available (edited: an overview schematics is available now, see updated information below). However since it is essentially an minimized Pi 1 I'd bet that the HDMI circuitry is (nearly) the same - though the Pi 1 features a standard sized HDMI connector ...
Those are explained here: https://www.raspberrypi.org/documentation/configuration/config-txt/video.md
There is also this: https://www.raspberrypi.org/documentation/configuration/hdmi-config.md -- But if the group 1, mode 16 as above works, you don't have to worry about all that.
Open /boot/config.txt and apply this settings:
hdmi_force_hotplug=1 to force hot plugin of your screen,
increase config_hdmi_boost to boost the signal. Lower values are meant to be for short HDMI cables, larger for longer ones. But this can also apply for (older) HDMI displays, whose HDMI receivers are not sensitive enough, irrespective of cable length.
tvservice is not the best to turn off and on the screen.
Much better way to do this (found after a day of searching) is using vcgencmd command (more on this here).
vcgencmd display_power 0 turns off the screen
vcgencmd display_power 1 turns on the screen
This allows the Qt application to be visible on the screen after turning it off and back on.
There is a few things you can try:
1) Edit /etc/rc.local and add the following lines above exit 0:
# Disable HDMI
this will turn off the display, but only somewhere during the boot sequence
2) add hdmi_blanking setting to your /boot/config.txt
I found the follwing settings here:
hdmi_blanking=0: HDMI Output will be blank when DPMS ...
CEA modes are intended for TV, they include plenty of interlaced and progressive modes, usually with 25/50/100Hz (PAL) or 30/60/120Hz (NTSC) frame rates and TV resolutions of 288/480/576/720/1080 scan lines. DMT modes are intended for computer monitors, therefore there are none of the interlaced modes, the resolutions are 640/720/800/1024/1280 and the frame ...
The best information I can find suggests that it's possible to output 4K resolutions, but at fairly miserable frame rates. The Pi 3 has the same GPU as the Pi 2, so the information should still be valid:
I have managed to get 3840 x 2160 (4k x 2k) at 15Hz on a Seiki E50UY04
cec-client can tell you the commands it knows
echo h | cec-client -s -d 1
There are a bunch of things that cec can do, that aren't on the list though too. You can press buttons on your remote and see the raw data being passed.
By playing back those same bytes, you can simulate the same functions.
That cable is most likely a DisplayPort-to-HDMI cable not a HDMI-to-DisplayPort cable (mind the direction). While there are DP ports able to support HMDI signals (DisplayPort Dual-mode) HDMI does not support DP directly. Since HDMI data transmission is very different from DP there will be no simple (passive) cable that just re-routes some signal lines on the ...
There's a command line utility, tvservice built into Raspbian that will tell you the state of the HDMI.
To detect the full state, you can use the command: tvservice -s. On my RPi this currently outputs:
state 0x40001 [NTSC 4:3], 720x480 @ 60.00Hz, interlaced
The states (that I've gathered) are as follows:
0x40001 Not initialized and HDMI cable is ...
While the official Raspberry schematics don't tell a thing about these components we can learn from the picture of the PCB that they are connected to the paired pins 1 and 3, 4 and 6, 7 and 9, 10 and 12 - that's all the differential signal and clock lines.
Since the devices have just four pads (not six) they are not dual-rail clamp ESD protectors, e.g. see ...
HDMI-HDMI cable is the best option.
It is cheapest when compared to HDMI-DVI cable or HDMI-VGA converter etc., Advantage is via HDMI-HDMI you get audio as well. Some Monitors also have RCA slot. Disadvantage in using RCA cable is resolution of screen is very bad.
If you want to use the PI exclusively as a HTPC or media center, you could use a distribution geared towards such applications. OpenELEC/XBMC /RasBMC seem to be the obvious choice. I did try OpenELEC at one time, but getting WiFi to work reliably on it seemed to be a pain.
Here's how I went about using Raspbian (since I use the RPi for tasks other than ...
I used the following to calibrate my display https://github.com/ukscone/set_overscan
I found this on http://www.raspberrypi.org/forums/viewtopic.php?p=305797&sid=4fe5fc284854fe3723841f79ea2c6546#p305797
The Raspberry Pi Foundation claims unambiguously that a VGA adapter on the GPIO header "means you can use it as a secondary monitor alongside HDMI" (from here). You should certainly be able to do that via USB; for evidence of the the pi running multi-headed, see comments below. The exception, of course, is trying to use the HDMI and the RCA video ...
To /boot/config.txt add:
You will have to reboot to make that effective (this applies to anything in config.txt), but the display should work now if you plug it in after boot. However, the resolution may not be set as correctly as it is when booted with the screen attached. To ensure that, set an explicit mode as explained here.
There are a few options. In increasing order of difficulty.
You can buy USB touch screen from somewhere like elo touch, but be prepared to spend
~$400 for a resistive 15" screen.
You could buy a touch overlay kit from ebay and apply it to an ordinary hdmi monitor.
Finally, you could buy and lvds to hdmi convertor from somewhere like
Try verifying the output of the file:
The part card0-HDMI-A-1 may be a little different (verify the parent directory for the correct file) and the content should be connected or disconnected. Also works for another connections, like VGA, LVDS, etc.
After this, simply make a script like:
while [ 1 ]
tvservice --explicit="DMT 35 HDMI"
This powers on HDMI explicitly with "DMT mode 35" which is 60 HZ at 1280x1024 pixels.
There is also tvservice --off if you've got enough.
For more information try both
tvservice --help and looking here for a tabular listing of modes.
Based on the type of flashing of the green (ACT) LED, you can figure out what is wrong (or at least what ballpark it's in) by looking at this page.
Too long didn't read version:
Green LED: ACT LED
------ Red LED: PWR LED
No PWR LED - No power.
PWR LED Blinking - Not enough power.
PWR LED but no ACT LED (For Pi 1s) - Problem with SD card.
I am using xset dpms force off to turn off the display. This command uses Display Power Management Signaling.
In a cron job, you'll need to set the DISPLAY variable, so that the crontab entries become something like:
0 22 * * * DISPLAY=:0 xset dpms force off
0 7 * * * DISPLAY=:0 xset dpms force on
Make sure the X server is started with -...
Most laptop hdmi ports are output not input. They are designed to connect a laptop to a monitor.
There are a few that have hdmi input.
You could use VNC Viewer on your laptop to view the Pi screen (by enabling VNC in Pi Configuration) over wifi/network.
In addition to @Krzystof 's excellent answer, I would quote what I read in this post:
Include the hdmi_ignore_cec_init=1 switch in /boot/config.txt.
Then in Settings>System>Input devices>Peripherals>CEC turn off the option: "Make XBMC the active source at start".