Date: Thu, 2 Oct 2008 22:29:03 +0200 From: Szilveszter Adam <sziszi@bsd.hu> To: freebsd-x11@freebsd.org Subject: Re: DRI not working Message-ID: <20081002202903.GB1831@baranyfelhocske.buza.adamsfamily.xx> In-Reply-To: <1222916611.1684.35.camel@wombat.2hip.net> References: <48DD9ECD.40309@ahhyes.net> <1222524191.1662.3.camel@wombat.2hip.net> <20080927165901.GA1508@baranyfelhocske.buza.adamsfamily.xx> <1222916611.1684.35.camel@wombat.2hip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Robert,
Sorry for only getting back to you now; I compiled up a kernel with your
patch in the morning but then had to rush off to work.
Patch applied cleanly to my recent -CURRENT sources.
On Wed, Oct 01, 2008 at 11:03:31PM -0400, Robert Noland wrote:
> Ok, can you guys give this patch a try? I think the memory failures are
> un-related and we probably need to try and figure that out separately.
> This patch should be rejecting the second head during the probe phase,
> so drm should not report *anything* about it.
That's quite correct, drm is now not attaching to vgapci1.
dmesg after patch (may wrap):
vgapci0: <VGA-compatible display> port 0x1800-0x1807 mem
0xe0000000-0xe7ffffff,0xd0000000-0xd007ffff irq 11 at device 2.0 on pci0
agp0: <Intel 8285xM (85xGM GMCH) SVGA controller> on vgapci0
agp0: detected 8060k stolen memory
agp0: aperture size is 128M
drm0: <Intel i852GM/i855GM GMCH> on vgapci0
vgapci0: child drm0 requested pci_enable_busmaster
info: [drm] AGP at 0xe0000000 128MB
info: [drm] Initialized i915 1.6.0 20080312
vgapci1: <VGA-compatible display> mem
0xe8000000-0xefffffff,0xd0080000-0xd00fffff at device 2.1 on pci0
So, no trace of drm attaching in the second case.
Unfortunately, this is about all the patch changed :-( the intel(4)
driver still thinks that this card is not even capable of hw-accelerated
2d.
> One of you said something about X also reporting both heads? If that is
> true and remains so with this patch, could you send me X logs? I'll try
> and get someone to look into the Intel 2d driver and see what is going
> on with it.
No, looking at the log only the primary one is used now, so that's ok.
The problem spot seems to be this:
(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 (0xd0000000,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) <= THIS
(WW) intel(0): xf86AllocateGARTMemory: allocation of 4 pages failed
(Cannot allocate memory) <= THIS TOO
(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.
Any ideas?
The full log is available.
--
Regards:
Szilveszter ADAM
Budapest
Hungary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081002202903.GB1831>