Bug#231529: X-Window-System can't be started with kernel 2.6.0

2004-02-07 Thread Georg Colle
enabled (II) GLINT(0): direct rendering disabled (II) GLINT(0): Initializing Xv driver rev. 4 (II) GLINT(0): Xv frontend scaler 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) Keyboard "Generic Keyboard" handled by legacy driver (**) Option "Protocol" "ImPS/2" (**) Configured Mouse: Protocol: "ImPS/2" (**) Option "CorePointer" (**) Configured Mouse: Core Pointer (**) Option "Device" "/dev/psaux" (EE) xf86OpenSerial: Cannot open device /dev/psaux No such device. (EE) Configured Mouse: cannot open input device (EE) PreInit failed for input device "Configured Mouse" (II) UnloadModule: "mouse" (**) Option "Protocol" "ImPS/2" (**) Generic Mouse: Protocol: "ImPS/2" (**) Option "SendCoreEvents" "true" (**) Generic Mouse: always reports core events (**) Option "Device" "/dev/input/mice" (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such device. (EE) Generic Mouse: cannot open input device (EE) PreInit failed for input device "Generic Mouse" (II) UnloadModule: "mouse" (WW) No core pointer registered No core pointer Fatal server error: failed to initialize core devices When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.0.log". Please report problems to [EMAIL PROTECTED] //*** schnapp * Greetings, Georg Colle.

Bug#231529: X-Window-System can't be started with kernel 2.6.0

2004-02-09 Thread Georg Colle
kdm or xserver-xfree86 can't be responsible for X-System not starting, because they do very well with kernel 2.4.24-2. I think the problem is due to the configuration of kernel-image-2.6.0-1-686 version: 2.6.0-2 and my report should better have been sent to Herbert Xu, its maintainer. Greetings