startx hangs Linux kernel 2.0.6 on RedHat 3.0.3 + RedHat updates

startx hangs Linux kernel 2.0.6 on RedHat 3.0.3 + RedHat updates

Post by Matthew D. Langst » Fri, 19 Jul 1996 04:00:00



***********
Video Card: Diamond Stealth64 Video 2001 series (2121/2201) w/2Mb RAM
X server  : S3: accelerated server for S3 graphics adaptors (Patchlevel 0)
**********

        I had X running fine with vanilla RedHat 3.0.3 + updates
(i.e. the Linux 1.2.13 kernel plus the updated RPM modules at

        I then upgraded to the 2.0.x Linux kernel using the RPM
modules at

(I'm actually using the 2.0.6 Linux kernel sources instead of the ones
from the RPM module kernel-source-2.0-1.i386.rpm, which just contains
the older 2.0.0 Linux kernel sources).

        Now when I `startx' a few messages fly by the screen (the ones
you see when you do a `X -probeonly') but then the screen goes black
and the keyboard and mouse are unresponsive.  I'll I can do at this
point is push the reset button.

        This actually hangs the kernel.  I've verified this by doing a
`rlogin' into my Linux machine (over Ethernet) from another computer
and then doing a `startx' on my Linux machine.  The `rlogin' session
hangs, and I can no longer `ping' my Linux machine either.

        Here's the output from `X -probeonly':

XFree86 Version 3.1.2 / X Window System
(protocol Version 11, revision 0, vendor release 6000)
Operating System: Linux
Configured drivers:
  S3: accelerated server for S3 graphics adaptors (Patchlevel 0)
      mmio_928, s3_generic
(using VT number 7)

XF86Config: /usr/X11R6/lib/X11/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) Mouse: type: PS/2, device: /dev/mouse, baudrate: 1200,
       3 button emulation (timeout: 50ms)
(**) S3: Graphics device ID: "Diamond Stealth64 Video 2001 series (2121/2201)"
(**) S3: Monitor ID: "Sony Multiscan 17seII"
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
(--) S3: card type: PCI
(--) S3: chipset:   Trio64 rev. 531
(--) S3: chipset driver: mmio_928
(--) S3: videoram:  2048k
(--) S3: Ramdac type: s3_trio64
(--) S3: Ramdac speed: 135
(--) S3: Using Trio32/64 programmable clock (MCLK 54.886 MHz)
(--) S3: Maximum allowed dot-clock: 135.000 MHz
(**) S3: Mode "640x480": mode clock =  31.500
(**) S3: Mode "800x600": mode clock =  50.000
(**) S3: Mode "1024x768": mode clock =  85.000
(**) S3: Mode "1280x1024": mode clock = 135.000
(--) S3: Operating RAMDAC in pixel multiplex mode
(--) S3: Using 6 bits per RGB value
(**) S3: Virtual resolution set to 1280x1024

        I've seen that others have posted to comp.os.linux.x reporting
similar problems.  Has anyone understood this problem yet?  Any
solutions?

        I understand that there are beta versions of XFree86 (3.1.2E
being the latest?).  Perhaps upgrading may help me.  Unfortunately, I
haven't seen an RPM package of the XFree86 beta releases.  Has anyone
else?
--
Matt Langston
SLD, Stanford Linear Accelerator Center

http://www.slac.stanford.edu/~langston
(415) 926-3279

--
--
Matt Langston
SLD, Stanford Linear Accelerator Center

http://www.slac.stanford.edu/~langston
(415) 926-3279

 
 
 

startx hangs Linux kernel 2.0.6 on RedHat 3.0.3 + RedHat updates

Post by Patrick K. Roumanof » Sat, 20 Jul 1996 04:00:00



> ***********
> Video Card: Diamond Stealth64 Video 2001 series (2121/2201) w/2Mb RAM
> X server  : S3: accelerated server for S3 graphics adaptors (Patchlevel 0)
> **********

My video card is a STB Trio64V+, but the behavior is the same.
Well, I don't have the answer, but I have the same problem, I upgraded my
slackware 3.0 (linux 1.2.13) with linux 2.0.7, I carefully followed the
upgrade instructions, and here is what I got:

- under linux 2.0.7 (booting from a floppy) startx hangs the machine
        (even with a previous "cp /usr/X11/bin/XF86_S3 /dev/null"
        or a previous "cat /usr/X11/bin/X >dev/null" as advertised
        in several answers for this kind of problem) though, I can
        still kill the server with (Ctrl+Alt+backspace) or (Ctrl+Atl+F2)
        and the `X -probeonly' works fine.

- under linux 1.2.13 (booting from another floppy) startx works
        perfectly fine, so I know that my modelines are properly
        configured for my harware.

from this two results, I deduce that my XF86config file is working fine
and that the reported problem comes from some tricky configuration files
that I am unable to track down.

Any help is welcome

pkr

"To err is human, to really screw-up, you need a computer"