X11VNC headless resolution [obsolete thread]

[simplesi]

I use x11vnc since I like looking at the main display that the RPi would show on a screen and its all fine when I've an HDMI monitor connected.

But if run headless, then the vnc display looks like 640x480.

Is there a method of setting this to something like 1024x768 as trying to run Scratch in 640x480 is a bit tricky

regards

Simon

[mister_wavey]

I don't know how to get x11vnc to increase the cr@ppy 640x480 resolution, but I've managed to get 1920x1080 working via tightvncserver, which I believe runs a new X instance for each client connection, rather than sharing the existing X instance, but, hey.

$ sudo apt-get install tightvncserver

$ vncserver :1 -geometry 1920x1080 -depth 24

then hit your pi's IP address with :1 at the end in your vnc viewer

[simplesi]

yeh - I know it works fine if I install tightvncserver but

I want to be able to convince pupils that what they are seeing on an XP Laptop VNC viewer screen is exactly what's running on the RPi so they can fully comprehend that their Scratch programs are actually running on the RPi and not their laptop

We are going to run the RPi's on robots so can't really connect a real screen while they are running along so need to use a VNC viewer:)

But before we untether them from the a monitor/kbd/mouse, I'd like to prove that using a VNC viewer is identical to using the monitor/kbd/mouse.

I don't want them to have to get into rpi:5900 vs rpi:5901 territory as I just intend having a VNC shortcut on laptop1 that connects to rp1, laptop2 to rpi2 etc


regards

Simon

[simplesi]

Well - simply uncommenting

Code: Select all

hdmi_force_hotplug=1

from /boot/config.txt

which forces it to use HDMI gives me a workable display so that'll prob do for the moment

Simon

[PeterT]

In /boot/config.txt, I set

hdmi_force_hotplug=1

and

hdmi_group=2
hdmi_mode=16 (1024x768@60Hz)

Then I ran x11vnc with -configure 1024x600, which is the resolution of my netbook screen

[Dixie]

Peter T

You're a legend! You just made my x11vnc desktop much easier to use!

Thanks

[solar3000]

Have you also tried forwarding X?
No software needed and no modifications on the RPi.

[simplesi]

How do you do that then?

Simon

[chris57100]

When you connect to the Pi with SSH you activate the X11 forwarding (-X option or look in you session parameters, depends of the tool you use to connect), install a X11 server on your laptop (i have a Mac where i have a X11 server) and when in SSH you start a X11 command then it displays the result on the screen of your laptop.

[ghans]

MobaXTerm on Windows does this.


ghans

[simplesi]

This is about getting the normal LXDE screen up remotely - not a remote terminal session

And I think we are sorted now ta

Simon

[clarkster]

Has anyone figured out how to make a higher resolution using X11VNC in headless mode?

I've tried this command....
hdmi_force_hotplug=1

alone and with....

hdmi_group=2
hdmi_mode=69 and 51 and 35

Nothings seems to give me a higher resolution than I get with only having hdmi_force_hotplug=1 alone.

When I boot with a TV attached, I get a much higher resolution on the TV screen and on my VNC client. I'd like to get this resolution when I am headless.

Anyone know how?

[arold]

I have the same problem as clarkster.

Has anyone manage to resolve this?

I have access to only 2 resolutions when no screen is plugged to the RPi:

If "hdmi_force_hotplug=1" is commented I get a resolution of 656x416 and if it is uncommented I get a resolution of 1184x624.

Changing the values of "hdmi_group" or "hdmi_mode" has no impact. Adding the "-geometry 1360x768" option to the x11vnc server only stretch those resolutions.

[calvin]

I have found a solution that seems to work for me. Ymmv.

1. Make sure hdmi_force_hotplug=1 is commented in /boot/config.txt
The following doesn't seem to have any effect is hdmi_force_hotplug=1 is set. The vnc resolution is always 1184x624 if it's set.
2. Use fbset prior to starting X to change the resolution via the geometry (-g) command.
*NOTE: This must be done before X is started for the first time. Even if you shut down X, run fbset and the restart X, it does not seem to have any effect. A reboot is required to change the resolution after X has been started for the first time. I'm not sure why.
ie.
for 1280x720, 16 bit color:

Code: Select all

fbset -g 1280 720 1280 720 16

for 1920x1080 (1080p), 16 bit color:

Code: Select all

fbset -g 1920 1080 1920 1080 16

3. Start X

Code: Select all

startx

Alternatively, if you have X set to start at boot, you'll need to insert a script into init.d containing the fbset command and create a symlink in your default runlevel rc.d folder (probably rc2.d) starting with S with a lower number than the script that starts X so it runs first. I personally have X set to disable at boot and start it manually via ssh, so I haven't tried implementing this. The most proper way would probably be to create the init script and use update-rc.d to create the symlinks, there are guides online on how to accomplish that.

Hope this helps. Best of luck.

[arold]

Thank you very much calvin! That solved the resolution problem for me too!!!

I have a standard Raspbian install where X start automatically. I didn't really knew in which file to put your command so I decided try adding a cron job that will be executed at every boot.

In a terminal, I entered:

Code: Select all

crontab -e

Afterwards, I simply added this line at the end of the file.

Code: Select all

@reboot /bin/fbset -g 1366 768 1366 768 16

After a reboot, I could VNC into the RPi and get a 1366x768 resolution!

I also noticed that, when using this solution, the fact that "hdmi_force_hotplug" is commented or not has no importance at all.

Thanks again to everyone!

[lettcco]

I stumbled upon a problem(?) with the crontab -e setting:

omxplayer or mpg123 will stop working afterward. something along the line of ALSA fatal error.

Removing @reboot ... entry in crontab and reboort restore player functionality.

Anyone else has encounter this?

[thirtythr33]

Hey everyone! I know this is an old thread, but it was the first I stumbled upon when trying to fix this same issue for myself.

It's very easy to change the VNC resolution.

Menu > Preferences > Raspberry Pi Configuration > Click "Set Resolution" and from there it should be self explanatory. No need to un-comment any code or even touch the console if your goal is to use the graphical interface anyway.

[FalcoGer]

I have hdmi_force_hotplug commented in in that file, as is hdmi_group and hdmi_mode.

If I set that as PeterT explains to

hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=16 (1024x767@60Hz)

Does the Pi still find a monitor which may be connected at one point? Does it set the screen resolution accordingly? If not, does it at least do that when the monitor is connected at boot time?

Also what's that hdmi group and mode?

[icyerasor]

I tried a lot of the suggested solutions. None worked.
Finally switched to latest Raspbian 10 (buster) distribution - and voila.. worked by simply setting the desired resolution through the system "Preferences > RaspberryPi configuration".
So everyone that still faces troubles: make extra sure you're using an up to date Raspbian-OS.

I couldn't get it working (only almost with a non-resizing desktop area; while the virtual screenspace resized and moving windows outisde was possbile) for the latest ubuntu mate for example.

[mahjongg]

I tried a lot of the suggested solutions. None worked.

that's because the "solutions" were from years ago describing a different version of the OS, so they were completely obsolete for the latest Raspbian.

please look at the posting data before replying.

If you are still using a version of Raspbian that old, then don't!
please only use the latest version of Raspbian, as we only truly support that.

If you have any questions about this topic, start a new thread, don't revive old threads, or google will keep finding them.