Re: Terminal Gets allocated, but X does not work

From: Sukhdeep Singh Sodhi ([email protected])
Date: Mon May 21 2001 - 14:06:55 CEST

Next message: [email protected]: "Re: Starting with muLinux"
Previous message: [email protected]: "Re: Starting with muLinux"
In reply to: Michele Andreoli: "Re: Terminal Gets allocated, but X does not work"
Next in thread: Michele Andreoli: "Re: Terminal Gets allocated, but X does not work"
Reply: Michele Andreoli: "Re: Terminal Gets allocated, but X does not work"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi Michel,

    This is the the log when I used the fvwm95 window manager.
XFree86 Version 3.1.2 / X Window System
(protocol Version 11, revision 0, vendor release 6000)
Operating System: Linux
Configured drivers:
  VGA16: server for 4-bit colour VGA (Patchlevel 0):
      et4000, et4000w32, et4000w32i, et4000w32p, ncr77c22, ncr77c22e,
      vgawonder, tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga9000,
      oti067, oti077, oti087, cl6410, cl6412, cl6420, cl6440, generic
  MONO: server for interlaced and banked monochrome graphics adaptors
        (Patchlevel 0):
      hgc1280, sigmalview, apollo9, hercules
(using VT number 7)

XF86Config: /usr/X11R6/lib/X11/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 1200
(**) VGA16: Graphics device ID: "Generic VGA"
(**) VGA16: Monitor ID: "My Monitor"
(--) VGA16: Mode "800x600" needs hsync freq of 35.16 kHz. Deleted.
(--) VGA16: Mode "1024x768" needs hsync freq of 35.52 kHz. Deleted.
(--) VGA16: Mode "640x480" needs hsync freq of 36.46 kHz. Deleted.
(--) VGA16: Mode "800x600" needs hsync freq of 37.88 kHz. Deleted.
(--) VGA16: Mode "800x600" needs hsync freq of 48.08 kHz. Deleted.
(--) VGA16: Mode "1024x768" needs hsync freq of 48.36 kHz. Deleted.
(--) VGA16: Mode "1024x768" needs hsync freq of 56.48 kHz. Deleted.
(--) VGA16: Mode "1280x1024" needs hsync freq of 51.02 kHz. Deleted.
(--) VGA16: Mode "1024x768" needs hsync freq of 62.50 kHz. Deleted.
(--) VGA16: Mode "1280x1024" needs hsync freq of 64.25 kHz. Deleted.
(--) VGA16: Mode "1280x1024" needs hsync freq of 78.86 kHz. Deleted.
(--) VGA16: Mode "1280x1024" needs hsync freq of 81.13 kHz. Deleted.
(--) VGA16: Mode "320x240" needs hsync freq of 39.38 kHz. Deleted.
(--) VGA16: Mode "400x300" needs hsync freq of 35.16 kHz. Deleted.
(--) VGA16: Mode "400x300" needs hsync freq of 37.88 kHz. Deleted.
(--) VGA16: Mode "400x300" needs hsync freq of 48.08 kHz. Deleted.
(--) VGA16: Mode "480x300" needs hsync freq of 35.16 kHz. Deleted.
(--) VGA16: Mode "480x300" needs hsync freq of 37.80 kHz. Deleted.
(--) VGA16: Mode "480x300" needs hsync freq of 39.56 kHz. Deleted.
(--) VGA16: Mode "480x300" needs hsync freq of 48.00 kHz. Deleted.
(**) FontPath set to
"/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/misc/"
(**) VGA16: chipset: generic
(--) VGA16: videoram: 256k (using 256k)
(**) VGA16: clocks: 25.20 28.30
(--) VGA16: Maximum allowed dot-clock: 90.000 MHz
(**) VGA16: Mode "640x480": mode clock = 25.175, clock used = 25.200
(--) VGA16: There is no mode definition named "800x600"
(--) VGA16: Removing mode "800x600" from list of valid modes.
(**) VGA16: Virtual resolution set to 640x480

Working Till here // This is a comment I inserted in the the xinit script to
check the tnumber of times it was executed

X connection to :0.0 broken (explicit kill or server shutdown).

xinit: connection to X server lost.

waiting for X server to shut down

This is the log file when I used afterstep

XFree86 Version 3.1.2 / X Window System
(protocol Version 11, revision 0, vendor release 6000)
Operating System: Linux
Configured drivers:
  VGA16: server for 4-bit colour VGA (Patchlevel 0):
      et4000, et4000w32, et4000w32i, et4000w32p, ncr77c22, ncr77c22e,
      vgawonder, tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga9000,
      oti067, oti077, oti087, cl6410, cl6412, cl6420, cl6440, generic
  MONO: server for interlaced and banked monochrome graphics adaptors
        (Patchlevel 0):
      hgc1280, sigmalview, apollo9, hercules
(using VT number 7)

Working Till here
X connection to :0.0 broken (explicit kill or server shutdown).

X connection to :0.0 broken (explicit kill or server shutdown).

xinit: connection to X server lost.

waiting for X server to shut down

I still get just a blank screen when I try to start X windows. When I use
afterstep the colour is yellow, when fvwm95 is used the colour is skyblue.

When I move the mouse I see a Vertical line moving across the screen and no
mouse pointer. The icons are also not visible

Thanks and Regards

Sukhdeep

----- Original Message -----
From: "Michele Andreoli" <[email protected]>

> On Fri, May 18, 2001 at 05:16:06PM +0530, Sukhdeep Singh Sodhi nicely
wrote:
> > screen- i am using the default window manager)
> >
> > The errmsg in "/var/log/startx.log" states
> >
> > " xinit: Connection to X server lost
> >
> > waiting for X server to shutdown "
> >
> > Could you help me the solution to this problem.
> >
>
> Surely, the log was more narrative. Please, a complete log
> might help.
>
> Michele
>
>
> --
> I keep trying to locate a meeting of Quantum Physicists. But everytime
> they set a meeting time, the location changes. And vice versa -- Anonymous
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Next message: [email protected]: "Re: Starting with muLinux"
Previous message: [email protected]: "Re: Starting with muLinux"
In reply to: Michele Andreoli: "Re: Terminal Gets allocated, but X does not work"
Next in thread: Michele Andreoli: "Re: Terminal Gets allocated, but X does not work"
Reply: Michele Andreoli: "Re: Terminal Gets allocated, but X does not work"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.6 : Sat Feb 08 2003 - 15:27:18 CET