Re: X problem ibook 2.2
On Thu, Apr 15, 2004 at 02:56:24PM +0200, Michel Dänzer wrote:
> On Tue, 2004-04-13 at 08:02, Sven Luther wrote:
> >
> > On Thu, Apr 08, 2004 at 06:57:10PM +0200, Michel Dänzer wrote:
> > > On Thu, 2004-04-08 at 17:31, Sven Luther wrote:
> > > >
> > > > BTW, where is : VMAP_4_ARGS supposed to be defined ?
> > >
> > > In the DRI CVS Makefile. You can just drop the guards, the idea is that
> > > this code should only be used in drm-trunk-module-src if the current,
> > > better solution doesn't work.
> >
> > Well, this didn't fix the problem, and i have no time to investigate
> > this in the next month or so.
>
> Note that the fact that you get a lockup probably means that AGP does
> get enabled, and it might be a different problem.
That was before i loaded the agpgart module first. When i do that, X
works fine, but there is no DRI. The message is :
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:10.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmGetBusid returned ''
(II) RADEON(0): [drm] DRM interface version 1.0
(II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:00:10.0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xeb2e7000
(II) RADEON(0): [drm] mapped SAREA 0xeb2e7000 to 0x3001a000
(II) RADEON(0): [drm] framebuffer handle = 0x98000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(II) RADEON(0): [agp] Mode 0x07000207 [AGP 0x106b/0x0027; Card 0x1002/0x4c57]
(II) RADEON(0): [agp] 8192 kB allocated with handle 0xed2eb000
(II) RADEON(0): [agp] ring handle = 0x00000000
(EE) RADEON(0): [agp] Could not map ring
(EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI.
(II) RADEON(0): [agp] You may want to make sure the agpgart kernel module
is loaded before the radeon kernel module.
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xeb2e7000 at 0x3001a000
and this in /var/log/syslog :
Apr 15 07:30:06 debian kernel: Linux agpgart interface v0.99 (c) Jeff
Hartmann
Apr 15 07:30:06 debian kernel: agpgart: Maximum main memory to use for
agp memory: 565M
Apr 15 07:30:06 debian kernel: agpgart: Detected Apple UniNorth/Pangea
chipset
Apr 15 07:30:06 debian kernel: agp: configuring for size idx: 4
Apr 15 07:30:06 debian kernel: agpgart: AGP aperture is 16M @ 0x0
Apr 15 07:30:32 debian kernel: [drm] AGP 0.99 Aperture @ 0x00000000 16MB
Apr 15 07:30:32 debian kernel: [drm] Initialized radeon 1.7.0 20020828
on minor 0
Apr 15 07:30:32 debian kernel: [drm:radeon_unlock] *ERROR* Process 518
using kernel context 0
> > Michel, do you think it would make sense to backport a more recent copy
> > of the drm modules to the older kernel, or do you see problems in doing
> > this ?
>
> I do think that would be the best solution, preferably upstream.
Well, i am maybe not the best person to do the backport upstream, but
maybe let's already get it working in the debian package, and then
strong of the experience suggest it happens upstream ?
Friendly,
Sven Luther
Reply to: