The reason a DVI-to-VGA adapter works on your PC & laptop is that DVI includes analog (RGB) pins. The adapter is passive; It just connects the red analog output of the PC to the red analog input of the monitor, ditto for green and blue. They are included on most PCs and laptops for backward compatibility.
HDMI-to-DVI cables are also passive, but ...
This is an X power-saving thing.
Firstly, you may need to install xset, a lightweight application that controls some X settings.
apt-get install x11-xserver-utils
Now open up your ~/.xinitrc file (if you don't have one then create it) and enter this:
xset s off # don't activate screensaver
xset -dpms # disable DPMS (Energy Star) features....
The other solutions here did not work for me (fresh Raspbian, boot to GUI). Instead, this worked:
Open up /etc/lightdm/lightdm.conf using your favorite text editor (I prefer nano).
Look for the line #xserver-command=X. Change it to xserver-command=X -s 0 dpms
It should be at line 87 if things don't change.
Save and reboot.
Presuming you are logged in as the same user that's running the X display, this is fairly easy. First you need to know the display identifier; if there is only one running instance, it is probably :0. To check, use who. You'll see output including stuff like this:
goldilocks pts/5 2015-02-16 07:18 (:1)
goldilocks pts/6 2015-02-16 07:18 (...
The driver for the screen provides an interface through /sys/. To turn the screen on you can use the command:
echo 0 > /sys/class/backlight/rpi_backlight/bl_power
and to turn it off:
echo 1 > /sys/class/backlight/rpi_backlight/bl_power
the brightness can be adjusted using:
echo n > /sys/class/backlight/rpi_backlight/brightness
where n is some ...
Simple! :) Buy TWO Raspberry Pies and hook them up with ethernet cable. Then use synergy to hook up the two systems in a virtual multihead config. See http://synergy-foss.org/ for more details.
Apart from that - there's not much you can do now as hdmi & composite cannot be used simultaneously.
This may change once we find out more about how to use the ...
A television or monitor will require either an HDMI input for video and audio or a composite video cable for video and a 3.5mm stereo cable for audio. If sound is not required then the minimum will be a composite video connection.
The issue is going to be drivers. As most products sold do not have open source drivers, it is up to someone with the know how to reverse engineer them. Because of this, if the device is not extremely popular, it is likely not going to be supported.
I have not used one of these personally but sites do exist with hardware databases. The accuracy of the ...
I think @Jivings answer may be better, but I have it in my notes to do this:
Install apt-get install x11-xserver-utils
Append these lines:
@xset s noblank
@xset s off
Possibly also comment out the line that says @xscreensaver -no-splash, so the complete file should look something like this:
You want a HDMI Type A to HDMI Type A; they are the most common cable used to connect DVD players to TVs.
Any type of cable should do. If you want to watch high-quality video and listen to high-quality audio, it's worth spending a little more on the cable. For example, gold connectors will the contact between the cable and the connectors on the RPi or the ...
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 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 ...
I have developed lazycast that is designed to work on Raspberry Pi 3. lazycast follows (most of) the wifi display specification (commercially known as Miracast) and uses wifi p2p (commercially known as WiFi Direct) to set up a connection. I have tested it with Windows 8.1 and 10 sources. It requires no modification (using the built-in wifi) to the hardware ...
Personal experience tells me it's pretty excellent. I have used X-forwarding over SSH and it performs well, as if executing natively. I've had multiple forwarded windows on the go at once, including Eclipse and Chromium.
I've also played with forwarding mouse and keyboard using from my desktop to the Pi using x2x which works by using the Pi X session as a ...
The issue was caused by the length of my HDMI cable which was 3M 1.4a HDMI spec.
It is because the default power output on the HDMI connector is sometimes not enough for longer cables causing the zits, in order to fix this you should edit your config.txt file in the root of your SD card (will be visible under windows explorer, if the text file does not ...
This is not a direct answer to your question (hopefully you do get one) but a little bit of explanation that might help you to solve questions like this yourself. It seems to me a lot of people are coming to the pi with little or no previous linux experience and this would be a good idea.
Operating systems you may be more familiar with (eg, windows) have a ...
To access an UNIX server from a Windows client, my preferred combination is PuTTY + Xming. Xming is easy to install, lightweight, fast, stable, and works pretty well overall.
The procedure (also explained here):
Enable the X11 forwarding option in PuTTY (Configuration > Connection > SSH > X11 > Enable X11 forwarding)
Start Xming on your Windows machine: ......
An active HDMI to VGA adapter would be much better quality than and active Composite video (RCA) to VGA adapter. Both would be much more expensive than a passive adapter however.
Active HDMI to VGA adapters
A quick check using google shopping suggests that an active HDMI to VGA adapter will cost around £50 ($80) and should support 1920x1080 resolution if ...
That display of information you see is Xorg starting up. The reason is starts but doesn't show anything is because there is no graphical output connected to the Pi, such as a monitor or TV. Thus Xorg doesn't know how to handle the XSession.
There are a few possible solutions, depending on what you are trying to achieve.
If you have a screen connected to ...
Assuming you're using LXDE (wheezy/debian default Window Manager on RPi, as explained by goldilocks):
In your home directory (/home/pi) there is a directory called:
(mind the dot before config, the full path is /home/pi/.config/lxpanel)
When you rename or remove this directory it will be re-created on the next startup of X, using the ...
Following answer from reddit was helpful:
The yellow-white-red ports are for composite video (yellow) and stereo audio (red and white). These plugs typically use RCA connectors.
The Pi has an RCA composite video out, and a 3.5mm audio out jack (the same thing you'd find on a smartphone, iPod etc, i.e. a "headphone jack")
So, to connect the Pi to your TV, ...