Difference between revisions of "Talk:Intel graphics"

From ArchWiki
Jump to: navigation, search
m (moved Talk:Intel Graphics to Talk:Intel: Consistency with other major video chipset manufacturer articles. Though Intel makes more than just graphics chipsets, so does Nvidia. Majority of searches for "intel" are in reference to the video ch)
m (Blanked the page)
Line 1: Line 1:
I am going to remove the VideoRam calculation section soon as it is "no longer recommended"
 
The following is the xorg.0.log from following that section:
 
(WW) intel(0): VideoRam configuration found, which is no longer recommended.
 
(II) intel(0): Continuing with default 0kB VideoRam instead of 261120 kB.
 
--[[User:Sand Lee|Sand Lee]] 20:18, 2 June 2009 (EDT)
 
  
Actually I just noticed that the above section should fall under the Hotplug Disabled section, so I won't remove it, I'll just make it clearer. --[[User:Sand Lee|Sand Lee]] 20:38, 2 June 2009 (EDT)
 
 
== KMS ==
 
 
In the KMS section, the 'early' start way of doing things states that the file /etc/modprobe.d/modprobe.conf should be edited and appended to the FILES= section of mkinitcpio.conf. However, isn't it easier to put "i915.modeset=1" on the kernel line in grub? When doing so you don't need to rebuild the initramfs each time you want to try KMS or to temporarily disable it. You can simply edit the kernel line on the grub screen when booting. --[[User:Big gie|Big gie]] 10:53, 15 October 2009 (EDT)
 
 
::Thanks, I have added that to the wiki, so check that out whether it is OK. --[[User:Bubla|bubla]] 12:29, 20 October 2009 (EDT)
 
 
::I've made some re-writting of the KMS part. I mainly re-arranged it in more structured way. Is it fine? [[User:Big gie|Big gie]] 23:18, 8 November 2009 (EST)
 
 
::I think you still need to run mkinitcpio at least once after adding i915 to the modules in mkinitcpio.conf. --[[User:Grey|Grey]] 17:07, 21 November 2009 (EST)
 
 
::You're absolutely right. But that information is present under [[Intel_Graphics#Note for both "Simplest" and "Alternative"]]. It might be confusing though as that information is later in the page. But that information applies to both methods, so it could be duplicatyed into each section, or only once after... [[User:Big gie|Big gie]] 01:03, 22 November 2009 (EST)
 
 
:: My Eee when booting with that option gives me {{Codeline|Unknown boot option `i915.modeset=1': ignoring}}. KMS works though, as does plymouth. What gives? [[User:Daenyth|Daenyth]] 19:25, 1 December 2009 (EST)
 
 
::: That's normal. That option is meant for the "i915" module, which is not built into the kernel. Because it is not built-in, the kernel does not know what to do with it. But when the module is loaded (remember you added it to the MODULE section in mkinitcpio.conf?) from the ram disk, the kernel pass the option to it and KMS kicks in. The only way to prevent that would be to have KMS enabled by default (and still include i915 in MODULE) in the kernel. Since KMS is still considered experimental/beta/unstable/whatever, Arch's dev decided to keep it disabled by default. One day it migth become enabled by default though. [[User:Big gie|Big gie]]
 
 
::: kernel 2.6.32-1 in testing has intel kms enabled by default. --[[User:Shining|shining]] 07:19, 7 December 2009 (EST)
 
 
=="intel-legacy: ''Old and obsolete''?"==
 
I realize that they are ''for'' old cards, but are the packages in the repo obsolete? This description might be misleading.<br>
 
--[[User:Pacmanz|Pacmanz]] 18:45, 31 October 2009 (EDT)
 
 
intel-legacy is not compatible with xorg-server 1.7.x. When trying to upgrade your you'll get:
 
xorg-server conflicts with xf86-video-intel-legacy. Remove xf86-video-intel-legacy? [Y/n]
 
 
[[User:Karol|Karol]] 10:33, 11 December 2009 (EST)
 

Revision as of 19:14, 4 January 2010