Difference between revisions of "Talk:Intel graphics"

From ArchWiki
Jump to: navigation, search
(KMS)
(KMS)
Line 18: Line 18:
  
 
::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)
 
::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)
  
 
=="intel-legacy: ''Old and obsolete''?"==
 
=="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>
 
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)
 
--[[User:Pacmanz|Pacmanz]] 18:45, 31 October 2009 (EDT)

Revision as of 00:25, 2 December 2009

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. 

--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. --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. --Big gie 10:53, 15 October 2009 (EDT)

Thanks, I have added that to the wiki, so check that out whether it is OK. --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? 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. --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... Big gie 01:03, 22 November 2009 (EST)
My Eee when booting with that option gives me Template:Codeline. KMS works though, as does plymouth. What gives? Daenyth 19:25, 1 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.
--Pacmanz 18:45, 31 October 2009 (EDT)