Home_greyopenFATE - openSUSE feature tracking > #307139
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Enable KMS for Intel Graphics cards

Feature state

openSUSE-11.2
Rejected Information
openSUSE-11.3
Done

Description

Since in the Intel Graphics Release 2009Q2 kernel modesetting is the recommended method, please enable CONFIG_DRM_I915_KMS in the kernel config.

In the current factory kernel (August 03) CONFIG_DRM_RADEON_KMS is set even though the code is considered unstable and depends on CONFIG_STAGING, however the more stable and recommended CONFIG_DRM_I915_KMS is not set. Please enable this option too.

Discussion


icons/user_comment.png A. J. wrote: (8 years ago)

Stefan, could you comment on this, please?

icons/user_comment.png S. D. wrote: (8 years ago)

We didn't enable KMS for radeon by intention. See Bug #527910 for more details.

icons/user_comment.png S. K. wrote: (8 years ago)

kms support is in our kernels, CONFIG_DRM_I915_KMS is about the default and we won't change the default not yet. Boot with i195.modeset=1 if you know your machine supports it. For those machines we might add it automatically, but not via kernel default.

icons/user_comment.png S. D. wrote: (8 years ago)

KMS on my 945GM machine at home still gave me a black screen last time I tried (Kernel 2.6.30, xorg-server 1.6.2, xf86-video-intel 2.8.0, libdrm 2.4.11, Mesa 7.5.0) whereas UMS works. Thus I'm not sure whether we want to make KMS the default now. I'm going to try again with latest X/Kernel stack soon.

icons/user_comment.png S. D. wrote: (8 years ago)

Apparently KMS on 945GM improved a lot with latest X.Org/Kernel (xorg-server 1.6.3/Kernel 2.6.31-rc5). No longer black screen. Even switching to Linux console and back works. I'm trying to use this one regularly now.

icons/user_comment.png R. B. wrote: (8 years ago)

It would be nice to make it default if it seems stable enough.

icons/user_comment.png M. H. wrote: (8 years ago)

How many different systems have actually been tested successfully so far? Your statement is pretty bold...

But we should consider to make KMS the default on i915,i945, i965, and G33. I haven't tested G33 yet, though. i8** are IMHO too little tested, maybe they don't work at all, i815 at least probably doesn't work.

icons/user_comment.png R. K. wrote: (8 years ago)

Any progress here for M8? Can we expect enabled KMS (especially i´m interested in i915) Or still should i activate by adding i915.modeset=1? And i´d like to ask, how about is with UXA? Is it default already?

icons/user_comment.png S. D. wrote: (8 years ago)

No changes here to expect for final release, since we're afraid of a lot of regressions if making KMS the default. So you still need to specify i915.modeset=1. There is nothing left in the driver than UXA. So yes, it's the default meanwhile.

icons/user_comment.png K. K. wrote: (8 years ago)

I am currently running openSUSE 11.2 with drm.ko and i915.ko added to the initrd and the following kernel command line:

root=/dev/disk/by-label/rootfs resume=/dev/disk/by-label/swapfs i915.modeset=1 splash=silent quiet showopts

My chipset is i915GM. The only problem I see at the moment is that the splash=silent parameter isn't regarded and I see a framebuffer console with boot messages instead of the splash graphic. The dmesg has the following lines

Linux agpgart interface v0.103
agpgart-intel 0000:00:00.0: Intel 915GM Chipset
agpgart-intel 0000:00:00.0: detected 7932K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xc0000000

[drm] Initialized drm 1.1.0 20060810
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: setting latency timer to 64
i2c-adapter i2c-1: unable to read EDID block.
i915 0000:00:02.0: LVDS-1: no EDID data
[drm] DAC-6: set mode 640x480 0
i2c-adapter i2c-1: unable to read EDID block.
i915 0000:00:02.0: LVDS-1: no EDID data
[drm] TV-12: set mode NTSC 480i 0
bootsplash 3.1.6-2004/03/31: looking for picture...
bootsplash: silentjpeg size 115769 bytes
bootsplash: does not fit into framebuffer.
bootsplash: ...found (1280x800, 27301 bytes, v3).
render error detected, EIR: 0x00000010
page table error
  PGTBL_ER: 0x00000100
[drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
render error detected, EIR: 0x00000010
page table error
  PGTBL_ER: 0x00000100
[drm] LVDS-8: set mode 1280x800 16
Console: switching to colour frame buffer device 156x46
[drm] fb0: inteldrmfb frame buffer device
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

icons/user_comment.png K. K. wrote: (8 years ago)

Ehhh... the textbox mangled messages

Linux agpgart interface v0.103 
agpgart-intel 0000:00:00.0: Intel 915GM Chipset
agpgart-intel 0000:00:00.0: detected 7932K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xc0000000
[drm] Initialized drm 1.1.0 20060810
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: setting latency timer to 64
i2c-adapter i2c-1: unable to read EDID block.
i915 0000:00:02.0: LVDS-1: no EDID data
[drm] DAC-6: set mode 640x480 0
i2c-adapter i2c-1: unable to read EDID block.
i915 0000:00:02.0: LVDS-1: no EDID data
[drm] TV-12: set mode NTSC 480i 0
bootsplash 3.1.6-2004/03/31: looking for picture...
bootsplash: silentjpeg size 115769 bytes
bootsplash: does not fit into framebuffer.
bootsplash: ...found (1280x800, 27301 bytes, v3).
render error detected, EIR: 0x00000010
page table error
PGTBL_ER: 0x00000100
[drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
render error detected, EIR: 0x00000010
page table error
PGTBL_ER: 0x00000100
[drm] LVDS-8: set mode 1280x800 16
Console: switching to colour frame buffer device 156x46
[drm] fb0: inteldrmfb frame buffer device
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

icons/user_comment.png M. H. wrote: (8 years ago)

Suspend to disk is currently broken when KMS is enabled on many i915 machines. Issue is known upstream, yet there hasn't been progress for months now.

KMS doesn't improve anything, at least on i915 machines. Resume from StR isn't faster (which was claimed), most machines have the native resolution as a VESA mode for the console, framebuffer reallocation works with user mode setting as well.

So there's currently no reason to switch the default.

icons/user_comment.png K. K. wrote: (8 years ago)

On my machine I am able to suspend and successfully resume from disk any number of times if I set HIBERNATION_METHOD=kernel  in a file in /etc/pm/config.d/.

With HIBERNATION_METHOD=userspace (which is the default) I get a GPU Hang when splashy displays on resume, which requires a reboot to get a working system again.

If I recompile the suspend-0.80 package with --disable-splashy, I am able to resume  from StD successfully again. So I would suggest that the problem lies in the userspace resume (espacially splashy) and not in the kernel.

icons/user_comment.png A. J. wrote: (8 years ago)

AFAIK Egbert is working on this, so setting this to implementation. If this is false, please send it back to me...

icons/user_comment.png S. D. wrote: (8 years ago)

This has already been implemented for openSUSE 11.3.

Last change: 8 years ago
Voting
Score: 13
  • Negative: 0
  • Neutral: 0
  • Positive: 13
Tags
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint