2 ssh clients (so that I can cut/paste the output - happens locally too.) client 1 $ startx (x starts, log goes to (II) Mouse0: ps2EnableDataReporting: succeeded) client 2 carl@LinuxBook1 xc $ xine This is xine (X11 gui) - a free video player v0.9.23. (c) 2000-2003 The xine Team. (xine starts. on X console, move the mouse over the DVD button (or any other button). after about 2 seconds, X stops, additional lines in log file starting with "*** If unresolved " ) X connection to :0.0 broken (explicit kill or server shutdown). $ I am guessing this isn't enough info. let me know what I can do. It is very repeatable. Here is the "interesting" part of Xorg.0.log - the full files will be attached. Release Date: 18 December 2003 X Protocol Version 11, Revision 0, Release 6.7 Build Operating System: Linux 2.6.6-rc3-bk11 i686 [ELF] Current Operating System: Linux LinuxBook1 2.6.6-rc3-bk11 #4 Tue May 18 07:16:34 GMT 2004 i686 Build Date: 18 May 2004 (==) I810(0): Write-combining range (0xd0000000,0x4000000) (II) I810(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) I810(0): Setting dot clock to 25.2 MHz [ 0x13 0x3 0x40 ] [ 21 5 4 ] (II) I810(0): chose watermark 0x22009000: (tab.freq 25.2) (II) I810(0): xf86BindGARTMemory: bind key 2 at 0x00000000 (pgoffset 0) (WW) I810(0): xf86AllocateGARTMemory: allocation of 1024 pages failed (Cannot allocate memory) (II) I810(0): No physical memory available for 4194304 bytes of DCACHE (II) I810(0): xf86BindGARTMemory: bind key 3 at 0x00800000 (pgoffset 2048) (II) I810(0): Adding 512 scanlines for pixmap caching (II) I810(0): Allocated Scratch Memory (II) I810(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Horizontal and Vertical Lines Offscreen Pixmaps Setting up tile and stipple cache: 21 128x128 slots 5 256x256 slots (==) I810(0): Backing store disabled (==) I810(0): Silken mouse enabled (**) I810(0): Direct rendering disabled (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (**) Option "Protocol" "IMPS/2" (**) Mouse0: Device: "/dev/psaux" (**) Mouse0: Protocol: "IMPS/2" (**) Option "CorePointer" (**) Mouse0: Core Pointer (**) Option "Device" "/dev/psaux" (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5" (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: Buttons: 5 (II) Keyboard "Keyboard0" handled by legacy driver (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (II) Mouse0: ps2EnableDataReporting: succeeded *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. (II) I810(0): xf86UnbindGARTMemory: unbind key 2 (II) I810(0): xf86UnbindGARTMemory: unbind key 3
Created attachment 300 [details] Xorg.0.log
Created attachment 301 [details] system.twmrc
Created attachment 302 [details] xorg.conf
Created attachment 303 [details] 2.6.6 kernel .config
Created attachment 304 [details] modules.conf mainly to show the this line: options i810fb vram=8 accel=1 mtrr=1 but the crash happens without it too, but there was some discussion about i810, so there it is.
Do you still see this problem with 6.8.2?
Closing. Re-open if problem persists with X.Org 6.8.2 and provide new log details.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.