Difference between revisions of "Talk:Uvesafb"

From ArchWiki
Jump to navigation Jump to search
m (New .conf file location: re + close)
(Disabling KMS really needed nowadays ?)
Line 7: Line 7:
 
Edited "Define a Resolution" and "Listing Resolutions" sections to reflect this change. --Sonoran 12 April 2012
 
Edited "Define a Resolution" and "Listing Resolutions" sections to reflect this change. --Sonoran 12 April 2012
 
:Thanks :-) For fixes like this, it's enough to include a summary of your edit in the 'Summary' text field (just above the 'Save page', 'Show preview' and 'Show changes' buttons). -- [[User:Karol|Karol]] 18:07, 12 April 2012 (EDT)
 
:Thanks :-) For fixes like this, it's enough to include a summary of your edit in the 'Summary' text field (just above the 'Save page', 'Show preview' and 'Show changes' buttons). -- [[User:Karol|Karol]] 18:07, 12 April 2012 (EDT)
 +
 +
== Disabling KMS really needed nowadays ? ==
 +
 +
Adding i915.modeset=0 gave me "no device found" errors while trying to set up Xorg.
 +
 +
At last after losing quite some time I finally set i915.modeset=1, and tada : a good looking framebuffer and a working X server, no pitch-black screen.
 +
 +
Maybe the use of this has obsolete. I have intel module version 2.18, xorg 1.12.1 and a 3.3.3-1-ARCH kernel with an Intel GMA 3000 chipset.

Revision as of 06:24, 25 April 2012

In /etc/mkinitcpio.conf, there's FBRES value. Shouldn't it albo be set to FBRES="1280x800"? You should have mention that there's no need to load 915resolution daemon. --Husio 15:56, 25 June 2008 (EDT)

New .conf file location

As of v86d 0.1.10-3, /etc/modprobe.d/uvesafb.conf has been moved to /usr/lib/modprobe.d/uvesafb.conf. Edited "Define a Resolution" and "Listing Resolutions" sections to reflect this change. --Sonoran 12 April 2012

Thanks :-) For fixes like this, it's enough to include a summary of your edit in the 'Summary' text field (just above the 'Save page', 'Show preview' and 'Show changes' buttons). -- Karol 18:07, 12 April 2012 (EDT)

Disabling KMS really needed nowadays ?

Adding i915.modeset=0 gave me "no device found" errors while trying to set up Xorg.

At last after losing quite some time I finally set i915.modeset=1, and tada : a good looking framebuffer and a working X server, no pitch-black screen.

Maybe the use of this has obsolete. I have intel module version 2.18, xorg 1.12.1 and a 3.3.3-1-ARCH kernel with an Intel GMA 3000 chipset.