Accéder au contenu principal

/etc/X11/xorg.conf


#To setup bigger resolutions with Ubuntu in a Virtual Machine


#Section "Device"
#Identifier "VESA Framebuffer"
#Driver "vesa"
#VideoRam 4096
# Insert Clocks lines here if appropriate
#EndSection

Section "Device"
Identifier "Configured Video Device"
#Driver "vboxvideo"
EndSection

Section "Monitor"
Identifier "My Monitor"
HorizSync 31.5 - 150.0
VertRefresh 75-85
EndSection

Section "Screen"
Identifier "Screen 1"
Device "VESA Framebuffer"
Monitor "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32

# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

Subsection "Display"
Depth 8
Modes "1680x1050" "1280x1024" "1024x768" "800x600"
EndSubsection
Subsection "Display"
Depth 16
Modes "1680x1050" "1280x1024" "1024x768" "800x600"
EndSubsection
Subsection "Display"
Depth 24
Modes "1680x1050" "1600x1200" "1600x1000" "1280x1024" "1024x768" "800x600"
EndSubsection
Subsection "Display"
Depth 32
Modes "1680x1050" "1600x1200" "1600x1000" "1280x1024" "1024x768" "800x600"
EndSubsection

EndSection

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

EndSection

# commented out by update-manager, HAL is now used and auto-detects devices
# Keyboard settings are now read from /etc/default/console-setup
#Section "InputDevice"
#Identifier "Configured Mouse"
#Driver "vboxmouse"
#Option "CorePointer"
#EndSection

Commentaires

Posts les plus consultés de ce blog

Setting up Rust on Windows 10 with MSYS2 without installing Visual Studio

Setting up Rust on Windows 10 with MSYS2 without installing Visual Studio  1. Install MSYS2 2. Update MSYS2 and run : pacman -Sy && pacman -Syu  and install git and gcc: pacman -S git &&  pacman -S mingw-w64-x86_64-toolchain 3. Open the MSYS2 terminal and install the rust compiler with :  pacman -S mingw-w64-x86_64-rust You may stop here but you will miss the rustup package (which is not part of MSYS2) to manage the Rust compiler environment. To install rustup , follow the next steps. 4. Clone the rustup git repository :  git clone git@github.com:rust-lang/rustup.git --depth=1 5. Compile and run rustup: cd rustup cargo run --release 6. Once rustup detects the previously installed rust compiler and asks to uninstall it before you can continue. So, open a new MSYS2 terminal and uninstall rust :  pacman -R mingw-w64-x86_64-rust 7. Now back to the rustup terminal, choose yes to continue the installation. On the next question choose : custom ins...

Installing Ubuntu 16.04 on an Alienware Aurora R5

Installing Ubuntu 16.04 LTS on an Alienware Aurora R5 with NVIDIA GPU support (Dual boot Windows) I have compiled these instructions from my succesful installation on Nov 25. Would you be happy to live without Windows? If not use Dual Boot. This procedure is inspired from this DELL support page : http://www.dell.com/support/article/uk/en/ukbsdt1/SLN301754/en You can refer to the link above for additional steps and to see useful screenshots. However, please, make sure to take care about the GPU-related  steps below. Re-installing Windows 10 with BIOS Secure Boot to OFF First, check that have only one disk installed in your machine. I have found that having one disk only makes it easier to re-install Windows. Secondly, an important step is to create two USB Recovery disks. Use two USB memory sticks bigger than 16 GB supporting the USB 3.0 standard (file copy will be much faster). Use the first one to create a recovery disk for Windows 10, as a backup if the instal...

How to create an executable from a Scala project

I started to have fun with scala and I wanted to be able to package and launch a Scala executable. It is an eclipse project and it is already using Maven for dependency resolution. I found the following solutions (to confirm) 1. Use SBT as a build tool. SBT seems to support the Maven pom.xml files for dependency resolution. 2. Use Gary Boone's solution by wrapping the Scala project entry point into a Java static main function 3. Use mvn assembly : single plugin as described on stackoverflow