Talk:Intel graphics

From ArchWiki
Revision as of 07:11, 2 June 2013 by Zman0900 (Talk | contribs)

Jump to: navigation, search

Setting gamma and brightness

Intel offers no way to adjust these at the driver level. Luckily these can be set with xgamma and xrandr.

Adding acpi_backlight=vendor to the kernel boot line allows the backlight to be changed on the Intel HD 3000 via xbacklight without root access. Perhaps a note could be added to provide this option. papabean (talk) 02:40, 14 January 2013 (UTC)

acpi_backlight=vendor stopped working a few kernels ago. (No. I did not revert to be certain).

However, intel-gpu-tools in the community repository includes the intel_backlight utility which allows one to manually set the backlight level.

papabean (talk) 04:36, 11 February 2013 (UTC)

Best performance options

In my experience (i5 CPU w/ HD4000, Z77 mobo) the best performance can be had with the following options:

  • SNA acceleration method
  • Vertical sync enabled
  • TearFree option enabled
  • i915.semaphores=1 kernel option turned on

Using the ck kernel specific to the CPU architecture also seems to make the video performance more consistent, but not necessarily any faster.

Disable VSYNC

I suggest that the restoration of this entry, it was very useful

To disable VSYNC, adjust /etc/X11/xorg.conf.d/20-intel.conf in Section "Device" the string Option "SwapbuffersWait" "false".

Alternatively, set vblank_mode to 0 in ~/.drirc and make sure that driver is set to dri2:

<device screen="0" driver="dri2">
   <application name="Default">
   <option name="vblank_mode" value="0"/>

Weathered Colors

Is there a way to do the equivalent of xrandr --output HDMI3 --set "Broadcast RGB" "Full" without having X running? I have two identical monitors (Asus VH222H), one connected to my dvi port (HDMI1), the other to the hdmi port (HDMI3). Both support full range rgb, but the one connected to hdmi always boots set to limited range. Its easily fixed with the xrandr set command, but I don't like running that all the time and it also doesn't work if I go straight to a vt after booting. It would be nice to put it in a systemd job.

Perhaps I should file a bug report with the kernel? The auto detect is more sophisticated than just HDMI == limited range tv, right?