hI -
I'm trying to run linux-solo on Ubuntu 5.10 with kernel 2.6.15.1.
This machine is a PIII and has an AGP radeon 9200SE (Rv280).
I can boot into X and get direct rendering with this kernel and (newly
compiled) modules.
My drm modules are from cvs ca. 1/25/2006
I run the server and test app as root.
I run sample_server, and all appears OK (using radeon_dri.so driver lib
in miniglx.conf):
[EMAIL PROTECTED]:/home/pdev/src/solo/Mesa/progs/miniglx#
[miniglx] probed chipset 0x5964
got MMIOAddress 0xb7dfc000 offset 134217728
shared virtual width is 1280
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmGetBusid returned ''
[drm] added 8192 byte SAREA at 0xd089b000
[drm] mapped SAREA 0xd089b000 to 0xb7dfa000, size 8192
[drm] framebuffer handle = 0xe0000000
[drm] register handle = 0xff8f0000
[gart] AGP enabled at 2x
[gart] 8192 kB allocated with handle 0x00000001
[gart] ring handle = 0xf8000000
[gart] ring read ptr handle = 0xf8101000
[gart] vertex/indirect buffers handle = 0xf8102000
[gart] AGP texture map handle = 0xf8302000
Using 8 MB AGP aperture
Using 1 MB for the ring buffer
Using 2 MB for vertex/indirect buffers
Using 1 MB for AGP textures
Will use back buffer at offset 0x600000
Will use depth buffer at offset 0xb00000
Will use 114688 kb for textures at offset 0x1000000
in drmCreateContext
[drm] Added 32 65536 byte vertex/indirect buffers
[drm] dma control initialized, using IRQ 11
[drm] Initialized kernel gart heap manager, 5111808
color tiling disabled
page flipping disabled
[miniglx] Setting mode: visible 1280x1024 virtual 1280x1024x32
[miniglx] Readback mode: visible 1280x1024 virtual 1280x1024x32
RADEONEngineRestore
Next I try to run miniglxtest (again as root) but get an error --
glxCreateContext fails, ultimately in drmCreateContext
[EMAIL PROTECTED]:/home/pdev/src/solo/Mesa/progs/miniglx# ./miniglxtest
[miniglx] probed chipset 0x5964
CreateNotify
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: drmOpenMinor returns 4
drmOpenByBusid: drmGetBusid reports PCI:1:0:0
Authorize - magic 1
drmCreateContext: err in ioctl, errno=13
>>> drmCreateContext failed
Error: glXCreateContext failed
DestroyNotify
I trace the code to drm/libdrm/xf86drm.c: drmCreateContext
In that method is an ioctl call,
ioctl(fd, DRM_IOCTL_ADD_CTX, &ctx)
Now I'm at my limit of understanding. I've placed some dbg stmts in the
ioctl function
(drm/linux-core/drm_context.c: drm_addctx()), and the ioctl method
_appears_ to run to
completion and return 0 (hence success). (I see these outputs in dmesg.)
A check inside drmCreateContext shows that an error (13) is in fact
returned by that method.
An strace shows the following at the ioctl call:
ioctl(4, 0xc0086420, 0xbfd0d758) = -1 EACCES (Permission denied)
Well, I believe that, though I don't understand why I'm getting this error.
I've read some comments on dri-devl from last summer regarding DRM and
root/non-root privs. Could I be getting caught up
by those requirements? Can anyone suggest how I debug/solve this problem?
Thanks,
Dan
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
