Re: [Dri-devel] DRI segfaults after debian update
Michel Dänzer wrote: What's the kernel message printed when loading the module, in particular the version? The only thing I could think of is that you're using an Alan Cox kernel and have configured it for the wrong XFree86 version or something. I've tried with 2.4.9-ac11, but the DRI was correctly configured for XFree 4.1, and also with vanilla 2.4.14 and 2.4.16. I've just noticed something strange, though : even though the xserver packages are all 4.1.0-9, it seems the server itself hasn't been completely updated : XFree86 Version 4.0.99.3 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 26 April 2001 (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor=The XFree86 Project compiled for 4.0.99.3, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.1 From what I understand, this means I've been trying to use the DRI modules for 4.1 with a partially 4.0 xserver. I say partially because some other parts of the server appear to be correct 4.1 : (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 So I figure I only have to get the server back to speed with a correct, fully 4.1 version, and things should work again. The single remaining problem is that I have no idea how to do that without blowing my distribution to pieces. I've tried reinstalling packages like xserver-common, to no avail. -- Daniel ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
On Mon, 2001-12-03 at 12:27, Daniel Polombo wrote: XFree86 Version 4.0.99.3 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 26 April 2001 (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor=The XFree86 Project compiled for 4.0.99.3, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.1 From what I understand, this means I've been trying to use the DRI modules for 4.1 with a partially 4.0 xserver. I say partially because some other parts of the server appear to be correct 4.1 : (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 So I figure I only have to get the server back to speed with a correct, fully 4.1 version, and things should work again. The single remaining problem is that I have no idea how to do that without blowing my distribution to pieces. I've tried reinstalling packages like xserver-common, to no avail. The X server and its modules are in xserver-xfree86. If reinstalling that doesn't fix this, you have a non-distribution X which is picked up. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
On Mon, Dec 03, 2001 at 01:40:12PM +0100, Daniel Polombo wrote: Michel Dänzer wrote: The X server and its modules are in xserver-xfree86. If reinstalling that doesn't fix this, you have a non-distribution X which is picked up. There was indeed an X11R6-DRI in which some things were picked up, including the wrong XFree86. I fixed that, and now the X server announces itself as a 4.1.0.1, as do all the libs : (II) Loading /usr/X11R6/lib/modules/linux/libdrm.a (II) Module drm: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.1 However, this still doesn't work, and I still get the same error : ambre:~$ /usr/lib/xscreensaver/gears drmR128Clear: return = -22 Sounds like your kernel driver isn't uptodate. If you type 'dmesg' to look at the kernel messages the r128 kernel module should identify itself as version 2.1.6. Alan. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
Alan Hourihane wrote: Sounds like your kernel driver isn't uptodate. If you type 'dmesg' to look at the kernel messages the r128 kernel module should identify itself as version 2.1.6. Looks good to me : ambre:~$ dmesg | grep -i r128 [drm] Initialized r128 2.1.6 20010405 on minor 0 -- Daniel ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
On Mon, 2001-12-03 at 14:11, Daniel Polombo wrote: Alan Hourihane wrote: Sounds like your kernel driver isn't uptodate. If you type 'dmesg' to look at the kernel messages the r128 kernel module should identify itself as version 2.1.6. Looks good to me : ambre:~$ dmesg | grep -i r128 [drm] Initialized r128 2.1.6 20010405 on minor 0 What does a client say when you start it with LIBGL_DEBUG=verbose? Just another stab in the dark ;) -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
On Mon, Dec 03, 2001 at 02:11:33PM +0100, Daniel Polombo wrote: Alan Hourihane wrote: Sounds like your kernel driver isn't uptodate. If you type 'dmesg' to look at the kernel messages the r128 kernel module should identify itself as version 2.1.6. Looks good to me : ambre:~$ dmesg | grep -i r128 [drm] Initialized r128 2.1.6 20010405 on minor 0 Then we need to see the full /var/log/XFree86.0.log file. Alan. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
On Mon, Dec 03, 2001 at 02:34:56PM +0100, Daniel Polombo wrote: Alan Hourihane wrote: Then we need to see the full /var/log/XFree86.0.log file. Here it comes (attached). O.k. That looks good. What does the last 10 or so lines of 'dmesg' say ? Alan. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
Alan Hourihane wrote: O.k. That looks good. What does the last 10 or so lines of 'dmesg' say ? I'm not sure this is what you want, but : [drm:r128_cce_vertex] *ERROR* process 27792 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28769 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28771 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28801 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28843 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28846 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28848 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 29033 using buffer owned by 0 -- Daniel ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
On Mon, Dec 03, 2001 at 03:02:35PM +0100, Daniel Polombo wrote: Alan Hourihane wrote: O.k. That looks good. What does the last 10 or so lines of 'dmesg' say ? I'm not sure this is what you want, but : I need the output from the loading of the drm module to when these *ERROR*'s started. Alan. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
Alan Hourihane wrote: I need the output from the loading of the drm module to when these *ERROR*'s started. Here it is, all un-edited. [drm] AGP 0.99 on Intel i815 @ 0xe400 64MB [drm] Initialized r128 2.1.6 20010405 on minor 0 uhci.c: USB Universal Host Controller Interface driver v1.1 PCI: Found IRQ 11 for device 00:1f.2 PCI: Sharing IRQ 11 with 02:06.0 PCI: Sharing IRQ 11 with 02:06.1 PCI: Sharing IRQ 11 with 02:0f.0 PCI: Sharing IRQ 11 with 02:0f.1 PCI: Sharing IRQ 11 with 02:0f.2 PCI: Setting latency timer of device 00:1f.2 to 64 uhci.c: USB UHCI at I/O 0xdce0, IRQ 11 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected usb.c: registered new driver hid hid-core.c: v1.8 Andreas Gal, Vojtech Pavlik [EMAIL PROTECTED] hid-core.c: USB HID support drivers mice: PS/2 mouse device common for all mice kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.15, 06 Nov 2001 on ide0(3,6), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.15, 06 Nov 2001 on ide0(3,7), internal journal EXT3-fs: mounted filesystem with ordered data mode. hub.c: USB new device connect on bus1/2, assigned device number 2 NTFS driver v1.1.20 [Flags: R/O MODULE] input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse ® with IntelliEye] on usb1:2.0 cs: IO port probe 0x0c00-0x0cff: clean. cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7 cs: IO port probe 0x0a00-0x0aff: clean. eth0: Setting promiscuous mode. device eth0 entered promiscuous mode device lo entered promiscuous mode [drm:r128_cce_vertex] *ERROR* process 640 using buffer owned by 0 VFS: Disk change detected on device ide0(3,64) ISO 9660 Extensions: Microsoft Joliet Level 3 ISO 9660 Extensions: RRIP_1991A device eth0 left promiscuous mode device lo left promiscuous mode [drm:r128_cce_vertex] *ERROR* process 27792 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28769 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28771 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28801 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28843 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28846 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 28848 using buffer owned by 0 [drm:r128_cce_vertex] *ERROR* process 29033 using buffer owned by 0 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
On Thu, 2001-11-29 at 11:56, Daniel Polombo wrote: Michel Dänzer wrote: No, the Debian XFree86 packages always go into /usr/X11R6. /usr/X11R6-DRI is a popular place for custom DRI CVS builds. Well, it still doesn't work with the new 2.4.16 kernel (using the r128 module from the kernel tree). The xlibmesa and xserver versions are identical : root@ambre:/lib# dpkg -l | grep xserver-xf ii xserver-xfree8 4.1.0-9the XFree86 X server root@ambre:/lib# dpkg -l | grep xlibmesa ii xlibmesa-dev 4.1.0-9XFree86 version of Mesa 3D graphics library ii xlibmesa3 4.1.0-9XFree86 version of Mesa 3D graphics library The libs used seem to be the right ones : root@ambre:/lib# ldd /usr/lib/xscreensaver/gears libGL.so.1 = /usr/X11R6/lib/libGL.so.1 (0x40025000) libGLU.so.1 = /usr/X11R6/lib/libGLU.so.1 (0x4008d000) root@ambre:/lib# dpkg -L xlibmesa3 /usr/X11R6/lib/libGL.so.1.2 /usr/X11R6/lib/libGLU.so.1.3 root@ambre:/lib# ls -l /usr/X11R6/lib/libGL.so.1 /usr/X11R6/lib/libGLU.so.1 lrwxrwxrwx1 root root 27 nov 12 14:25 /usr/X11R6/lib/libGL.so.1 - /usr/X11R6/lib/libGL.so.1.2 lrwxrwxrwx1 root root 28 nov 12 14:25 /usr/X11R6/lib/libGLU.so.1 - /usr/X11R6/lib/libGLU.so.1.3 And still : root@ambre:~# /usr/lib/xscreensaver/gears drmR128Clear: return = -22 root@ambre:~# tail -1 /var/log/syslog Nov 29 11:55:10 ambre kernel: [drm:r128_cce_vertex] *ERROR* process 1024 using buffer owned by 0 Is there any more information I can provide? Strace logs? Some more heavy debugging, maybe? What's the kernel message printed when loading the module, in particular the version? The only thing I could think of is that you're using an Alan Cox kernel and have configured it for the wrong XFree86 version or something. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
On Mon, 2001-11-19 at 10:03, Daniel Polombo wrote: Michel Dänzer wrote: My first guess would have been a wrong version of the kernel module, but the one from the 2.4.14 kernel should work. Could there be a stray libGL, e.g. in /usr/local, that gets picked up? You can check with ldd. I thought for a moment that was the problem, as I got a new libGL in /usr/X11R6-DRI/lib, and the upgrade modified my ld.so.conf accordingly, but the old one in /usr/X11R6/lib doesn't work any better (and they _are_ different files). I haven't checked yet, but I suspect the new location is the one used by the debian unstable (sid). No, the Debian XFree86 packages always go into /usr/X11R6. /usr/X11R6-DRI is a popular place for custom DRI CVS builds. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
Michel Dänzer wrote: First make sure that both xserver-xfree86 and xlibmesa3 are the same versions, namely 4.1.0-x. Both are indeed 4.1.0-9. My first guess would have been a wrong version of the kernel module, but the one from the 2.4.14 kernel should work. Could there be a stray libGL, e.g. in /usr/local, that gets picked up? You can check with ldd. I thought for a moment that was the problem, as I got a new libGL in /usr/X11R6-DRI/lib, and the upgrade modified my ld.so.conf accordingly, but the old one in /usr/X11R6/lib doesn't work any better (and they _are_ different files). I haven't checked yet, but I suspect the new location is the one used by the debian unstable (sid). -- Daniel ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI segfaults after debian update
On Wed, 2001-11-14 at 13:41, Daniel Polombo wrote: I am using the DRI on my Dell Latitude C800 with a Rage 128, and it has been working very well for quite some time now. I have recently updated my debian woody (weekly apt-get upgrade), though, and from then on, things suddenly stopped working. I'm not sure which libs were upgraded, though, as it was a rather heavy upgrade. First make sure that both xserver-xfree86 and xlibmesa3 are the same versions, namely 4.1.0-x. Initial (working) configuration : - kernel 2.4.9-ac11 - using the kernel's r128.o as a module - debian woody (testing) - XFree 4.1.0-7 To try and correct the problem, I upgraded first to a sid (debian unstable) to get newer packages. This got my Xfree version to 4.1.0-9. Since this did no good, I also upgraded the kernel to vanilla 2.4.14. Still no good. Direct rendering is enabled : $ glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes But if I try to run a 3D app : $ /usr/lib/xscreensaver/gears drmR128Clear: return = -22 Strace'ing the stuff indicates the culprit might be an ioctl not recognized by the driver : ioctl(4, 0x40146449, 0xb638)= -1 EINVAL (Invalid argument) write(2, drmR128Clear: return = -22\n, 27) = 27 And, lastly, the system logs the following error : [drm:r128_cce_vertex] *ERROR* process 16181 using buffer owned by 0 I would appreciate any kind of input on the subject, as this is very frustrating! My first guess would have been a wrong version of the kernel module, but the one from the 2.4.14 kernel should work. Could there be a stray libGL, e.g. in /usr/local, that gets picked up? You can check with ldd. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
