> Since this is most likely a DRI related issue, I'm cross-posting to > dri-devel. Thank you. I am reading this from the list archives and it chopped out the email addresses, so I can not CC there. Feel free to carbon copy there again if needed. > > Her system is running Linux 2.6.3 kernel. > > > > Linux agpgart interface v0.100 (c) Dave Jones > > agpgart: Detected an Intel i815 Chipset. > > agpgart: Maximum main memory to use for agp memory: 93M > > agpgart: detected 4MB dedicated video ram. > > agpgart: AGP aperture is 64M @ 0xe8000000 > > [drm] Initialized i830 1.3.2 20021108 on minor 0 > > So, is it an i81x or an i830/i845/i865? The X log seems to indicate > i815, but the i830 kernel module is loaded. Try using the i810 kernel > module. The i830 support is built-in to the kernel. My kernel config contains: CONFIG_SERIO_I8042=y CONFIG_AGP=y CONFIG_AGP_ALI=m CONFIG_AGP_ATI=m CONFIG_AGP_AMD=m CONFIG_AGP_AMD64=m CONFIG_AGP_INTEL=y CONFIG_AGP_NVIDIA=m CONFIG_AGP_SIS=m CONFIG_AGP_SWORKS=m CONFIG_AGP_VIA=m CONFIG_DRM=y CONFIG_DRM_TDFX=m CONFIG_DRM_GAMMA=m CONFIG_DRM_R128=m CONFIG_DRM_RADEON=m CONFIG_DRM_I810=m CONFIG_DRM_I830=y CONFIG_DRM_MGA=m CONFIG_DRM_SIS=m Should I make CONFIG_DRM_I830 a module instead? > > I have tried with and without i810 module. It didn't seem to change anything when I loaded the /lib/modules/2.6.3/kernel/drivers/char/drm/i810.ko module. Below is from scanpci: pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x1130 Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1132 Intel Corp. 82815 CGC [Chipset Graphics Controller] So I think it is an i815. I wonder if the built-in i830 support is causing this issue? I am not sure where I chose that configuration. It appears that CONFIG_DRM_I830=y is the default i386 config (as provided with linux-2.6.3 source and defined in linux-2.6.3/arch/i386/defconfig). Also, I noticed a CONFIG_DRM_I810_XFREE_41 in another configuration. Is it related? I don't see any mention of it in linux-2.6.3 source. I see that the knoppix-kernel-headers-2.4.22-xfs.config Linux kernel configuration has CONFIG_DRM_I830=m (and CONFIG_DRM_I810=m). That Knoppix config also has: CONFIG_DRM_NEW=y Is that related? needed? I don't see any mention of it in linux-2.6.3 source. I do see CONFIG_XFREE86_VERSION usage in linux-2.6.3/drivers/char/drm/drm.h and linux-2.6.3/drivers/char/drm/i810_drm.h. Is that related? If so, how should it be used? > > What should I do so she can use GL applications? > > In the mean time, try setting LIBGL_ALWAYS_INDIRECT in her .profile (or > whatever) or disabling DRI. So, I rebuilt my kernel with CONFIG_DRM_I830=m. I loaded i810 module instead and now it appears that glxinfo doesn't crash XFree86. Using a GL-based xscreensaver still does crash X. (This was on a different machine, but with same motherboard.) I also tried loading the i830 module, but still X crashes. Then I exported LIBGL_ALWAYS_INDIRECT=1 to the environment before running startx on the testing system, and still xscreensaver crashes X. The error is: Fatal server error: Caught signal 11. Server aborting To try the xscreensaver, I used "xscreensaver-command --select 201". (Some other numbers, like 199, show a screensaver, but 200 and 201 crash X.) Jeremy C. Reed http://www.pugetsoundtechnology.com/ ps. Please carbon-copy me on replies. Thank you. _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
