DRI not working
Robert Noland
rnoland at FreeBSD.org
Fri Oct 3 12:01:43 UTC 2008
On Fri, 2008-10-03 at 13:09 +1000, Alex wrote:
> Robert Noland wrote:
> > Ok, I found a RELENG_7 test box. It does apply and build cleanly.
> >
> > robert.
> >
> >
>
> Hi Robert,
>
> Thank you for the patch. The patch applied cleanly and I was able to
> rebuild cleanly as well.
>
> Unfortunately I am seeing the same symptoms as Szilveszter. DRM is no
> longer attaching to both heads, which is good. So perhaps the remainder
> of the issue is with the intel driver?
>
> From dmesg:
> ==========
>
> vgapci0: <VGA-compatible display> port 0xc000-0xc007 mem
> 0xf0000000-0xf7ffffff,0xfaf80000-0xfaffffff irq 11 at device 2.0 on pci0
> agp0: <Intel 82855GME (855GME GMCH) SVGA controller> on vgapci0
> agp0: detected 892k stolen memory
> agp0: aperture size is 128M
> drm0: <Intel i852GM/i855GM GMCH> on vgapci0
> info: [drm] AGP at 0xf0000000 128MB
> info: [drm] Initialized i915 1.5.0 20060119
> vgapci1: <VGA-compatible display> mem
> 0xe8000000-0xefffffff,0xfaf00000-0xfaf7ffff at device 2.1 on pci0
> pci0: <serial bus, USB> at device 29.0 (no driver attached)
>
> From Xorg logs:
> ============
>
> (II) intel(0): I830CheckAvailableMemory: 964608 kB available
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 8, (OK)
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 8, (OK)
> drmOpenByBusid: Searching for BusID pci:0000:00:02.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 8, (OK)
> drmOpenByBusid: drmOpenMinor returns 8
> drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
> (II) [drm] DRM interface version 1.2
> (II) [drm] DRM open master succeeded.
> (II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
> (II) intel(0): [drm] framebuffer mapped by ddx driver
> (II) intel(0): [drm] added 1 reserved context for kernel
> (II) intel(0): X context handle = 0x1
> (II) intel(0): [drm] installed DRM signal handler
> (**) intel(0): Framebuffer compression
> enabled
>
> (**) intel(0): Tiling
> enabled
>
> (==) intel(0): Write-combining range (0xfaf80000,0x80000) was already
> clear
> (==) intel(0): VideoRam: 131072
> KB
>
> (II) intel(0): Attempting memory allocation with tiled
> buffers.
>
> (WW) intel(0): xf86AllocateGARTMemory: allocation of 10 pages
> failed
>
> (Cannot allocate
> memory)
>
> (WW) intel(0): xf86AllocateGARTMemory: allocation of 4 pages
> failed
>
> (Cannot allocate
> memory)
Ok, so both of you are seeing the same memory failures with tiling
enabled. Let me check with some of the intel guys and see if they have
any insight.
robert.
> (WW) intel(0): Disabling HW cursor because the cursor memory allocation
> failed.
> (II) intel(0): Tiled allocation
> successful.
>
> (--) intel(0): DRI is disabled because it needs HW cursor, 2D accel and
> AGPGART.
>
> Let us know if you discover anything else. I really appreciate your time
> spent on this.
>
> Thanks again!
> Alex
>
> _______________________________________________
> freebsd-x11 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-unsubscribe at freebsd.org"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20081003/0f6c89da/attachment.pgp
More information about the freebsd-x11
mailing list