VirtualBox/Higher Screen Resolution without installing VirtualBox Guest Additions
Higher Screen Resolution without installing VirtualBox guest additions
This is still experimental. As in tested by few people. You should always be able to undo these changes. Doesn't hurt to always have a recent backup, just in case. This is an alternative to using VirtualBox Guest Additions for higher screen resolution. See also #Security Considerations.
To get higher screen resolution without installing VirtualBox guest additions, create a file called, say /etc/X11/xorg.conf.d/00-virtualbox-monitor.conf.
If there's no such directory, you need to create it first:
sudo mkdir -p /etc/X11/xorg.conf.d
Open kdesudo kwrite /etc/X11/xorg.conf.d/00-virtualbox-monitor.conf in an editor with root rights.
With the following contents:
Section "Device" Identifier "VirtualBox-Device" Option "Monitor-default" "VirtualBox-Monitor" EndSection Section "Monitor" Identifier "VirtualBox-Monitor" VendorName "VirtualBox" ModelName "VirtualBox" HorizSync 1.0 - 1000.0 VertRefresh 1.0 - 1000.0 Option "MinClock" "1.0" Option "MaxClock" "10000.0" Option "Primary" "True" Option "PreferredMode" "1600x1200" EndSection Section "Screen" Identifier "MyScreen" Device "VirtualBox-Device" Monitor "VirtualBox-Monitor" EndSection
And restart kdm or reboot.
This will make Whonix come up in 1600x1200 mode by default.
You can change the default mode by changing the "PreferredMode" option in the "Monitor" section. You can dynamically switch modes from the command line with "xrandr --output default --mode [whatever]", and you can see a list of available modes with plain "xrandr".
You can also change screen resolution using the KDE graphical user interface, go to Start Menu -> System Settings -> Display and Monitor. If you want some screen resolution that isn't listed there (e.g. 1440x900), you can can try the next on your host:
vboxmanage setextradata "VM Name" "CustomVideoMode1" "1440x900x32"
If you do not see your Start Menu button anymore (because it's outside the screen), you can start Konsole and manually start System Settings by running systemsettings.
If Ubuntu 14.04 has a screen resolution of 640x480 you may be able to get 1024x768 by simply by running xdiagnose and changing any setting under Debug. Marking them all or unmarking "Enable automatic crash reporting", are reported to work. Reboot.
- It might be better not to maximize the Tor Browser window.
- To prevent accidentally maximizing a window, it is recommend to deactivate the following option: KDE -> System Settings -> Screen Edges -> Uncheck: Maximize Windows by dragging them to the top of the screen.
- It might also be better not to use the same screen resolution as on your host.
If this doesn't work for you for some reason or if you want to revert these changes, simply delete /etc/X11/xorg.conf.d/00-virtualbox-monitor.conf.
sudo rm /etc/X11/xorg.conf.d/00-virtualbox-monitor.conf
And restart kdm or reboot.
By anonymous user.
The reason you can't just get higher resolutions using xrandr "--newmode" and "--addmode" without an xorg.conf file appears to be that VirtualBox isn't providing EDID information to the default VESA driver. The driver therefore makes the conservative assumption that it can't drive the "monitor" with the high clock rates needed for larger display sizes. The above config file tells the driver that it can use an effectively infinite range of clock rates.
sudo apt-get install read-edid
sudo get-edid ; echo $?
get-edid: get-edid version 2.0.0 Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful VBE version 200 VBE string at 0xc7f10 "VirtualBox VBE BIOS http://www.virtualbox.org/" VBE/DDC service about to be called Report DDC capabilities Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function unsupported Call failed Reading next EDID block VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function unsupported Call failed The EDID data should not be trusted as the VBE call failed Error: output block unchanged 1
get-edid: get-edid version 2.0.0 Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 halt_sys: file ��y�*+, line -1216758308 Function unsupported Call successful VBE version 300 VBE string at 0xc4f55 "SeaBIOS VBE(C) 2011" VBE/DDC service about to be called Report DDC capabilities Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 halt_sys: file ��y�*+, line -1216720908 Function unsupported Call successful Reading next EDID block VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 halt_sys: file ��y�*+, line -1216720908 Function unsupported Call successful The EDID data should not be trusted as the VBE call failed Error: output block unchanged 1
How to use xserver-xorg-video-modesetting?
- No reply from maintainers of the xserver-xorg-video-modesetting package.
- No reply from debian-user mailing list.
- Maybe helpful:
sudo service kdm stop
sudo service kdm start
Impressum | Datenschutz | Haftungsausschluss
Conditions for Contributions to Whonix, then Edit! IP addresses are scrubbed, but editing over Tor is recommended. Edits are held for moderation. Whonix (g+) is a licensee of the Open Invention Network. Unless otherwise noted above, content of this page is copyrighted and licensed under the same Free (as in speech) license as Whonix itself.