Bug#595511: linux-image-2.6.32-5-686: Blacklisting KMS for i8xx makes xorg intel driver unusable on these chipsets

2010-09-07 Thread Ben Hutchings 
On Sun, Sep 05, 2010 at 02:25:25PM +0200, Cesare Leonardi wrote:
 On 09/04/2010 08:00 PM, Soenke wrote:
 the recent update of linux-image-2.6.32 to 2.6.32-21 disables KMS for
 i8xx chipsets. This causes the xorg-video-intel driver to hang on X
 startup on my system.

 Yes, the situation for your i855 and previous intel chipset is in a bad  
 shape.
 For example look this (but there are other similar reports):
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594623

 It's both a kernel and a xserver-xorg-video-intel problem, but more the  
 latter. The kernel team is probably waiting to know if KMS should be  
 enabled or not for these chipsets and is working in concert with the  
 Ubuntu one for a common solution.
[...]

The Debian kernel team works closely with the X Strike Force regarding
DRM/KMS drivers, and we generally follow their advice on what options and
patches to use.

We're not working with Ubuntu on this, though we did follow their lead in
blacklisting those chips.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100907122723.ga11...@decadent.org.uk

Bug#595511: linux-image-2.6.32-5-686: Blacklisting KMS for i8xx makes xorg intel driver unusable on these chipsets

2010-09-07 Thread Cesare Leonardi 

On 09/07/2010 02:27 PM, Ben Hutchings wrote:

On Sun, Sep 05, 2010 at 02:25:25PM +0200, Cesare Leonardi wrote:

It's both a kernel and a xserver-xorg-video-intel problem, but more the
latter. The kernel team is probably waiting to know if KMS should be
enabled or not for these chipsets and is working in concert with the
Ubuntu one for a common solution.


[...]


We're not working with Ubuntu on this, though we did follow their lead in
blacklisting those chips.


Thanks for the explanation.

That was the message where i saw some collaboration between Debian and 
Ubuntu on this UMS/KMS problem:

http://lists.debian.org/debian-kernel/2010/09/msg00041.html

Cesare.



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c86bec5.3020...@gmail.com

Bug#595511: linux-image-2.6.32-5-686: Blacklisting KMS for i8xx makes xorg intel driver unusable on these chipsets

2010-09-05 Thread Cesare Leonardi 

On 09/04/2010 08:00 PM, Soenke wrote:

the recent update of linux-image-2.6.32 to 2.6.32-21 disables KMS for
i8xx chipsets. This causes the xorg-video-intel driver to hang on X
startup on my system.


Yes, the situation for your i855 and previous intel chipset is in a bad 
shape.

For example look this (but there are other similar reports):
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594623

It's both a kernel and a xserver-xorg-video-intel problem, but more the 
latter. The kernel team is probably waiting to know if KMS should be 
enabled or not for these chipsets and is working in concert with the 
Ubuntu one for a common solution.
On the X driver front, seems that the intel-gfx upstream developers are 
working to make KMS usable for our chipsets too, to avoid that 
distributions choose to fallback to UMS, to render the driver more 
maintenable and to make easier to port new features also to these 
not-so-new chipsets. From what i've read seems that on these chipsets 
there will be some performance penality in exchange to stability.

Looking here, seems there were lot of work recentely:
http://lists.freedesktop.org/archives/intel-gfx/

We will see when these changes will be released and if will be suitable 
for Squeeze.


Ciao.

Cesare.



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c838c35.3050...@gmail.com

Bug#595511: linux-image-2.6.32-5-686: Blacklisting KMS for i8xx makes xorg intel driver unusable on these chipsets

2010-09-04 Thread Soenke 
Package: linux-2.6
Version: 2.6.32-21
Severity: important


Hello everyone,

the recent update of linux-image-2.6.32 to 2.6.32-21 disables KMS for i8xx
chipsets. This causes the xorg-video-intel driver to hang on X startup on my
system. While X works with the vesa driver, it does not seem to have any 
support for an external monitor, 
xv or hardware acceleration, which I consider a serious drawback. The 
functionality of my laptop (ThinkPad X40)
is greatly reduced, hence the important tag. 
It would be helpful to have a way to switch KMS back on for these chips for 
configurations or systems where it works fine.

Regards,

soenke


-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-21) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Wed Aug 25 14:28:12 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=UUID=7d1dda14-2a82-4a6e-8456-684843390f30 
ro quiet

** Not tainted

** Kernel log:
[  186.960072] uhci_hcd :00:1d.0: power state changed by ACPI to D3
[  187.65] ACPI: Preparing to enter system sleep state S3
[  187.180190] Disabling non-boot CPUs ...
[  187.180289] Extended CMOS year: 2000
[  187.180289] Back to C!
[  187.180289] CPU0: Thermal monitoring enabled (TM2)
[  187.180289] Extended CMOS year: 2000
[  187.180335] ACPI: Waking up from system sleep state S3
[  187.712190] pci :00:02.1: restoring config space at offset 0x5 (was 0x0, 
writing 0xd008)
[  187.712196] pci :00:02.1: restoring config space at offset 0x4 (was 0x8, 
writing 0xe808)
[  187.712203] pci :00:02.1: restoring config space at offset 0x1 (was 
0x90, writing 0x93)
[  187.756061] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[  187.764071] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[  187.764078] uhci_hcd :00:1d.0: restoring config space at offset 0xf (was 
0x100, writing 0x10b)
[  187.764090] uhci_hcd :00:1d.0: restoring config space at offset 0x8 (was 
0x1, writing 0x1821)
[  187.764102] uhci_hcd :00:1d.0: restoring config space at offset 0x1 (was 
0x280, writing 0x281)
[  187.772072] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[  187.780071] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[  187.788071] uhci_hcd :00:1d.1: power state changed by ACPI to D0
[  187.796071] uhci_hcd :00:1d.1: power state changed by ACPI to D0
[  187.796077] uhci_hcd :00:1d.1: restoring config space at offset 0xf (was 
0x200, writing 0x20b)
[  187.796089] uhci_hcd :00:1d.1: restoring config space at offset 0x8 (was 
0x1, writing 0x1841)
[  187.796102] uhci_hcd :00:1d.1: restoring config space at offset 0x1 (was 
0x280, writing 0x281)
[  187.804071] uhci_hcd :00:1d.1: power state changed by ACPI to D0
[  187.812071] uhci_hcd :00:1d.1: power state changed by ACPI to D0
[  187.812078] uhci_hcd :00:1d.2: restoring config space at offset 0xf (was 
0x300, writing 0x30b)
[  187.812091] uhci_hcd :00:1d.2: restoring config space at offset 0x8 (was 
0x1, writing 0x1861)
[  187.812103] uhci_hcd :00:1d.2: restoring config space at offset 0x1 (was 
0x280, writing 0x281)
[  187.812121] ehci_hcd :00:1d.7: restoring config space at offset 0xf (was 
0x400, writing 0x40b)
[  187.812139] ehci_hcd :00:1d.7: restoring config space at offset 0x4 (was 
0x0, writing 0xd010)
[  187.812148] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 
0x290, writing 0x2900102)
[  187.820074] ehci_hcd :00:1d.7: power state changed by ACPI to D0
[  187.828071] ehci_hcd :00:1d.7: power state changed by ACPI to D0
[  187.828125] ata_piix :00:1f.1: restoring config space at offset 0x9 (was 
0x0, writing 0x5000)
[  187.828138] ata_piix :00:1f.1: restoring config space at offset 0x1 (was 
0x285, writing 0x287)
[  187.828183] Intel ICH :00:1f.5: restoring config space at offset 0x1 
(was 0x297, writing 0x293)
[  187.828211] Intel ICH Modem :00:1f.6: restoring config space at offset 
0x1 (was 0x295, writing 0x291)
[  187.844043] sdhci-pci :02:00.1: restoring config space at offset 0x3 
(was 0x80, writing 0x804000)
[  187.844050] sdhci-pci :02:00.1: restoring config space at offset 0x1 
(was 0x210, writing 0x2100106)
[  187.844069] e1000 :02:01.0: restoring config space at offset 0xf (was 
0xff0100, writing 0xff010b)
[  187.844083] e1000 :02:01.0: restoring config space at offset 0x6 (was 
0x1, writing 0x7001)
[  187.844089] e1000 :02:01.0: restoring config space at offset 0x4 (was 
0x0, writing 0xd020)
[  187.844095] e1000 :02:01.0: restoring config space at offset 0x3 (was 
0x0, writing 0x4008)
[  187.844102] e1000 :02:01.0: restoring config space at offset 0x1 (was 
0x230, writing 0x2300117)
[  187.891603] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[  187.891796] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[  187.891808]