You are viewing bgoglin

Brice Goglin's Blog - Debian/X.org notes - Bug triaging while waiting for DRM 2.6.33

Mar. 7th, 2010

12:59 - Debian/X.org notes - Bug triaging while waiting for DRM 2.6.33

Previous Entry Share Next Entry

Almost nothing interesting happened recently in X.org in Debian. But interesting things are coming soon.


First, radeon KMS and DRI2 will enter unstable soon. xserver-xorg-video-radeon 1:6.12.191-1 is currently in experimental. People seem to be happy with it so far, and upstream is taking very good care of bug reports as usual.

The next 2.6.32 kernel will contain DRM from 2.6.33. It first means that the radeon KMS driver not in staging anymore. Once this new kernel is uploaded, I'll put the new xserver-xorg-video-radeon in unstable (6.13.0 is expected soon, but 6.12.191 already looks good so far).

DRM from 2.6.33 will also brings nouveau support. It means that we will build libdrm-nouveau and upload a new xserver-xorg-video-nouveau. However, it also means that we need somebody to maintain this. And nobody in the team has a nvidia board to test packages so... If you want nouveau in Debian, please help.


While waiting for all these, we have been triaging the BTS a bit. Kibi is helping a lot by triaging recent intel bugs (many regressions fixed in recent kernels). I spent some time during the week-end triaging some old bugs. I closed more than a hundred of them, and pinged another hundred. We still have more than 1100 bugs open. It is not so bad compared to 1500-2000 when nobody maintains X (aka often), but still way too much.

Some of my bug closing might look a bit rude. But we had so many bug reports a couple years ago that are irrelevant today. Keeping them open would be meaningless. For instance, many input problems are obsolete since a lot of the input code was rewritten, we switched to input-hotplug, and then hal to udev. Another example is intel lockups (we had a lot of them after driver 2.2 arrived). But XAA and EXA were dropped in favor of UXA, DRI1 was dropped for DRI2, and KMS arrived. So it's useless to keep these obsolete and irrelevant bugs that cannot be debugged nowadays.


As usual, the Debian X team needs a lot of help. Again, if you want nouveau in Debian, please help.

(Permanent link

Comments:

From:(Anonymous)
Date:March 8th, 2010 14:54 (UTC)
(Link)
I didn't really expected that the DRM from .33 will be pulled. Can't wait to test it with the new libdrm-nouveau and xserver-xorg-video-nouveau.
From:jae [launchpad.net]
Date:March 11th, 2010 03:32 (UTC)

hardware?

(Link)
Would an nvidia card help? If so are there certain ones that are needed more than others?
From:vvill.myopenid.com
Date:March 12th, 2010 08:12 (UTC)

2.6.33-2 framebuffer kms

(Link)

I just upgraded a sid cli only install to a minimal X using 2.6.33-2-686
The chipset is a 915g desktop.
2.6.33-2-686 brought libapt-pkg-perl and linux-base as deps.
linux-base automatically switched several config files to be UUID based.
KMS is on and configured..
I double checked this morning from a cold boot and found the kernels builtin frambuffer "vesafb on this machine" hogged /dev/fb0 not allowing inteldrmfb to acquire /dev/fb0 and caused drm loading and kms to fail.
A warm reboot fixed the frambuffer and drm problems.


dmesg | grep {onsole,fb,agp,drm}
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
[    0.609455] Console: switching to colour frame buffer device 128x48
[    2.228461] Console: switching to colour dummy device 80x25
[    2.228809] Console: switching to colour frame buffer device 128x48
[    0.192576] pci 0000:00:1c.0:   bridge window [mem 0xcfb00000-0xcfbfffff 64bit pref]
[    0.250146] pci 0000:00:1c.0:   bridge window [mem 0xcfb00000-0xcfbfffff 64bit pref]
[    0.250439] pci_bus 0000:05: resource 2 [mem 0xcfb00000-0xcfbfffff 64bit pref]
[    0.557474] vesafb: framebuffer at 0xd0000000, mapped to 0xf7c80000, using 6144k, total 32448k
[    0.557482] vesafb: mode is 1024x768x32, linelength=4096, pages=9
[    0.557487] vesafb: scrolling: redraw
[    0.557492] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[    0.661410] fb0: VESA VGA frame buffer device
[    2.226523] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
[    2.325521] fb0: inteldrmfb frame buffer device
[    1.600483] Linux agpgart interface v0.103
[    1.612315] agpgart-intel 0000:00:00.0: Intel 915G Chipset
[    1.777772] agpgart-intel 0000:00:00.0: detected 32508K stolen memory
[    1.854777] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[    1.826307] [drm] Initialized drm 1.1.0 20060810
[    2.063897] [drm] set up 31M of stolen space
[    2.067002] [drm] initialized overlay support
[    2.226523] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
[    2.325521] fb0: inteldrmfb frame buffer device
[    2.325600] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

From:vvill.myopenid.com
Date:March 17th, 2010 17:29 (UTC)

kms

(Link)
I did a debootstrap install of sid on an intel 865g chipset desktop a couple of days ago. With the Sid 2.6.32-3-686 kernel, kms is now on with 2.6.32-3-686 as well as with the 2.6.33-2-686 kernel from experimental.
I also upgraded Lenny 2.6.26 to squeeze 2.6.32-3-686 on the intel 915g chipset machine yesterday and I still had to make the manual entries in
/etc/initramfs-tools/modules
intel_agp
drm
i915 modeset=1
than update the initrd.img to get kms on and drm loaded...
So I'm removing the old configuration entries from /etc/initramfs-tools/modules and letting Debain automatically configure X in Sid on both intel 915 and 865 machines..
And now I use the same /etc/initramfs-tools/modules entries with testing installs...
I have a fairly new default Lenny install on a mobile intel 830 that I'll double check upgrading to squeeze and than sid...
From:vvill.myopenid.com
Date:March 28th, 2010 08:15 (UTC)

2.6.32.4 on i830

(Link)
Toshiba Satellite 1200-S212 mobile i830 Celeron 1200-pS212
1) drm loads i915 loads
2) no framebuffer is loaded by default, if adding gfxpayload in grub-pc efifb gets loaded on this machine and the screen works fine at it's max res 1024x768x32
3)If I disable KMS everything else works OK, but with KMS enabled as soon as inteldrmfb is switched on I get screen blanking... I think because I only have 8MB of video ram, which is probably fairly common on these older laptops..

Squeeze.......
squeeze with 2.6.32-3 KMS emabled by default
dmesg | egrep "onsole|fb|agp|drm"
[ 0.004000] Console: colour dummy device 80x25
[ 0.004000] console [tty0] enabled
[ 0.647998] Console: switching to colour frame buffer device 128x48
[ 0.000000] BIOS-e820: 00000000ffb80000 - 00000000ffc00000 (reserved)
[ 0.000000] #3 [0000100000 - 000053fb10] TEXT DATA BSS ==> [0000100000 - 000053fb10]
[ 0.000000] Allocating PCI resources starting at 20000000 (gap: 10000000:efb80000)
[ 0.605152] efifb: probing for efifb
[ 0.605306] efifb: framebuffer at 0xe8000000, mapped to 0xd0000000, using 3072k, total 3072k
[ 0.605320] efifb: mode is 1024x768x32, linelength=4096, pages=1
[ 0.605328] efifb: scrolling: redraw
[ 0.605338] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.690806] fb0: EFI VGA frame buffer device
[ 2.010804] intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/945GME/965G/965GM chipsets
[ 2.046048] intelfb: Version 0.9.6
[ 2.063705] intelfb 0000:00:02.0: PCI INT A -> Link[LNKA] -> GSI 10 (level, low) -> IRQ 10
[ 2.081838] intelfb: Cannot reserve FB region.
[ 1.705485] Linux agpgart interface v0.103
[ 2.390772] agpgart-intel 0000:00:00.0: Intel 830M Chipset
[ 2.410509] agpgart-intel 0000:00:00.0: detected 8060K stolen memory
[ 2.431484] agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xe8000000

commenting out /etc/modprobe.d/i915-kms.conf/#i915 modeset=1
and updating the initrd image suppresses loading of intelfb and everything elase works ok..

Sid....
I grabbed dmesg blindly from a blank screen in sid 2.6.32-4-686
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 5.484998] Console: switching to colour frame buffer device 100x37
[ 1.658937] Linux agpgart interface v0.103
[ 1.836008] agpgart-intel 0000:00:00.0: Intel 830M Chipset
[ 1.836613] agpgart-intel 0000:00:00.0: detected 8060K stolen memory
[ 1.851950] agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xe8000000
[ 1.963598] [drm] Initialized drm 1.1.0 20060810
[ 4.411110] [drm] set up 15M of stolen space
[ 4.726519] [drm] DAC-6: set mode 640x480 0
[ 5.348147] [drm] LVDS-8: set mode 800x600 16
[ 5.490989] fb0: inteldrmfb frame buffer device
[ 5.491482] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

again commenting /etc/modprobe.d/i915-kms.conf/#i915 modeset=1
updating initrd image, reboot, adding the edit "set gfxpayload=1024x768x32,1024x768 to grub-pc and this is dmesg | egrep "onsole|fb|agp|drm"
[ 0.000000] BIOS-e820: 00000000ffb80000 - 00000000ffc00000 (reserved)
[ 0.000000] Allocating PCI resources starting at 10000000 (gap: 10000000:efb80000)
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-4-686 root=UUID=972958bf-aa7c-4a54-a79b-b6df5f6fba8e ro quiet
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.640210] efifb: probing for efifb
[ 0.640350] efifb: framebuffer at 0xe8000000, mapped to 0xd0000000, using 3072k, total 3072k
[ 0.640358] efifb: mode is 1024x768x32, linelength=4096, pages=1
[ 0.640362] efifb: scrolling: redraw
[ 0.640369] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.682952] Console: switching to colour frame buffer device 128x48
[ 0.725157] fb0: EFI VGA frame buffer device
[ 1.082083] Linux agpgart interface v0.103
[ 1.082248] agpgart-intel 0000:00:00.0: Intel 830M Chipset
[ 1.082852] agpgart-intel 0000:00:00.0: detected 8060K stolen memory
[ 1.084582] agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xe8000000
[ 2.124507] [drm] Initialized drm 1.1.0 20060810
[ 2.439279] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0