Talk:Intel

Rename to xf86-video-*
Intel sounds a little ambiguous, especially if we'd like to add something about Intel CPUs or so on. Maybe it'd be better to rename this to xf86-video-intel or like that? -- MGorny 06:57, 19 October 2011 (UTC)


 * That's the name of the driver. Also the man page is named like this. Astaecker 08:58, 19 October 2011 (UTC)


 * Even though the name may be unambiguous in the context of graphics drivers, it's not in the context of gentoo. +1 from me for the name change to what the package is named in gentoo. --Few 09:30, 19 October 2011 (UTC)


 * How about moving it to "X/Intel"? /Ni1s 21:45, 24 October 2011 (UTC)


 * In the interest of avoiding strange hierarchies I suggest either "xf86-video-intel" or something like "Intel (Xorg driver)". Eroen

Ivy Bridge OpenCL support
With regards to this edit: Ivy Bridge -- the hardware -- supports OpenCL, but there isn't any software support for it in Linux at this time. --Mattst88 19:03, 29 December 2012 (UTC)


 * I added a note
 * Astaecker 07:45, 30 December 2012 (UTC)

mesa broken
When following the directions laid out by this wiki, I found that dri was broken. To fix this I added a line to package.use >=media-libs/mesa-10.0.3 video_cards_i915 video_cards_i965 video_cards_intel gallium vdpau amd then ran emerge --changed-use =media-libs/mesa-10.0.3 This game me; linux-vdso.so.1 (0x00007ffff49ff000) libdrm_intel.so.1 => /usr/lib64/libdrm_intel.so.1 (0x00007f59c448f000) libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007f59c4283000) libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f59c4058000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f59c3e3a000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f59c3c36000) libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libstdc++.so.6 (0x00007f59c3932000) libm.so.6 => /lib64/libm.so.6 (0x00007f59c362f000) libc.so.6 => /lib64/libc.so.6 (0x00007f59c3287000) libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1 (0x00007f59c3070000) libpciaccess.so.0 => /usr/lib64/libpciaccess.so.0 (0x00007f59c2e67000) /lib64/ld-linux-x86-64.so.2 (0x00007f59c4d4e000) libz.so.1 => /lib64/libz.so.1 (0x00007f59c2c50000)
 * 1) ldd /usr/lib/mesa/i965_dri.so

Problem solved. It might be a good idea to update this wiki with the use settings for mesa.

"intel" USE flag
In the features support table the "intel" USE flag is listed for all 7 generations. In the driver section the "intel" USE flag is used only for generations 1-2. This is contradictory. Unfortunately I don't know which configuration is the right one. Fturco (talk) 13:49, 16 March 2014 (UTC)
 * https://wiki.gentoo.org/index.php?title=Intel&action=history above "talk" poster gave me ssh to their box, set, tested, and they confirmed intel is not required for their gen 3+ hardware. they had i915, and got some error messages regarding 965.  i would of linked against a forum thread but lost it and the search on forums is absolutely horrible. 666threesixes666 (talk) 21:11, 18 March 2014 (UTC)  remove the intel and further test it.
 * 09:13, 16 January 2013‎ Astaecker (Talk | contribs)‎ . . (3,525 bytes) (+522)‎ . . (Add "VIDEO_CARDS" column to feature matrix; inline inflexible template for proper step to step instructions) looks like they are template examples, and not necessarily tested. 666threesixes666 (talk) 21:14, 18 March 2014 (UTC)
 * it occured to me that i had a POS blade, and that it might have intel graphics. i plug it in, it has i915.  so i test it, and i reverted something i shouldn't of.  libdrm requires the intel flag.  regardless, the wiki can be flawed, but the os will tell you what is what.  this is coming from a fresh build of gentoo, and not a mangled revdep rebuild, or emerge -uND @world. 666threesixes666 (talk) 02:59, 19 March 2014 (UTC)

CONFIG_FRAMEBUFFER_CONSOLE=y
Still gives black screen after grub on my Thinkpad x220. 4.3.2 kernel. Upd: but adding acpi_osi="Linux" solves the issue. --Dtr (talk) 12:44, 16 December 2015 (UTC)

Introduce instructions to omit xf86-video-intel on Gen 4+
Other distros have started phasing out xf86-video-intel in favor of the modesetting driver which the latter is more advanced on Gen 4 and later Intel GPUs Should we provide instructions to this effect here? --Grknight (talk) 14:36, 16 August 2016 (UTC)