Help getting XWindow X386mono to run, please (SLS 1.01, 99pl8)

Help getting XWindow X386mono to run, please (SLS 1.01, 99pl8)

Post by Martin Bae » Wed, 23 Jun 1993 03:54:11



Hi,

I have a Compaq Deskpro 386/25e with
a noname (it says Nytech) 14" color monitor
a noname VGA (not SVGA) card
Genius serial mouse (Model No GM-F303)
a 115MB AT-bus HD and
Linux 99pl8 (SLS 1.01)

The Problem:
Due to the noname graphic card I have no idea how to get XWindow to run.
When I do startx the screen blackens after a few seconds and there is a
lot of shuffling on the HD with pauses. And then nothing more happens.
If I move the mouse, again shuffling.
But the screen stays black Ctrl-Alt-Del, Alt-F1 -- F8 don't work
and after I do Ctrl-Alt-Backspace the machine is halted.
I tried it hours on end. Read what there was to read, but ... :-(
Is there anybody who dit get it to run with a normal VGA card?
I would be happy with the monochrome mode. :-)

Greetings, martin.


One World, One People Please.

Here is some output I captured with running 'nohup startx'
so the output was appendet to nohup.out...
Nohup was not the problem because just running 'startx' gave same results.
---------------try 1:--------------------

 1 Setting TCP SO_LINGER: Protocol not available
 2 no SIOCGIFCONF
 3 XFree86 Version 1.2 / X Window System
 4 (protocol Version 11, revision 0, vendor release 5000)
 5 Configured drivers:
 6   VGA2 (monochrome VGA):
 7       et4000, et3000, pvga1, gvga, tvga8900c, tvga9000, tvga8900b,
 8       generic
 9   HGA2 (monochrome HGA):
10       hga6845
11 (using VT number 7)
12
13 Mouse: type: MouseSystems, device: /dev/mouse, baudrate: 1200
14 FontPath set to "/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/75dpi/"
15 VGA2: generic (mem: 64k (using 64k) numclocks: 4)
16 VGA2:   clocks:  25.2  28.3  17.3   0.0
17 VGA2: Mode "640x480": mode clock =  25.0, clock used =  25.2
18 VGA2: Virtual resolution set to 800x600
19 VGA2: Using non-banked mono vga mode
20 XCsetroot, written by Thomas Wu and Davor Matic (c) 1990, MIT Fishbowl
21 XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
22       after 196 requests (196 known processed) with 10 events remaining.
23       The connection was probably broken by a server shutdown or KillClient.
24
25 waiting for X server to shut down XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
26       after 50 requests (35 known processed) with 0 events remaining.
27       The connection was probably broken by a server shutdown or KillClient.
28 XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
29       after 33 requests (31 known processed) with 0 events remaining.
30       The connection was probably broken by a server shutdown or KillClient.
---
I numbered the lines and of the ohter outputs I only included the lines that
were different and the last line.

---------------try 2:--------------------
...
16 VGA2:   clocks:  25.2  28.3  17.4   0.0
...
21 XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
22       after 196 requests (196 known processed) with 20 events remaining.
...
30       The connection was probably broken by a server shutdown or KillClient.
---
Interstingly the clocks are different.

---------------try 3:--------------------
...
16 VGA2:   clocks:  25.2  28.3  13.8  17.3
...
20 XCsetroot, written by Thomas Wu and Davor Matic (c) 1990, MIT Fishbowl
---
Here I tured the computer off without doing Ctrl-Alt-Backspace.

---------------try 4:--------------------
...
16 VGA2:   clocks:  25.2  28.3  17.4  17.5
......
21 XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
22       after 2005 requests (2005 known processed) with 0 events remaining.
23       The connection was probably broken by a server shutdown or KillClient.
24
25 waiting for X server to shut down xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
26 XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
27       after 55 requests (46 known processed) with 0 events remaining.
28       The connection was probably broken by a server shutdown or KillClient.
---
Here I moved the mouse a bit and hit some buttons.

---------------try 7:--------------------
...
16 VGA2:   clocks:  25.2  28.3  17.4   0.0
...
18 VGA2: Virtual resolution set to 640x480
...
22 waiting for X server to shut down xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
23 XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
24       after 33 requests (33 known processed) with 0 events remaining.
25       The connection was probably broken by a server shutdown or KillClient.
---
Setting the Virtual resolution to 640x480 didn't help either.

 
 
 

1. : 0.99pl8 (SLS 1.01) TCP/IP fails with "potential" IRQ 9 conflict

Hi everybody,

I wonder if anyone would be able to shed light onto the following problem:

I am trying to set up TCP/IP for Linux 0.99pl8 (SLS Rel. 1.01) on my box, a
Gateway 486/33C.  My card is an (old?!) Western Digital 8003E, configured
to the following values:

                    int         =       5
                    mem         =       D0000
                    mem start   =       D0000
                    mem end     =       D2000

At bootup, Linux detects my card correctly and prints the following message:

        "Detected wd8003-old using IRQ 9 with shared memory d0000-d1fff"
        "wd.c by Donald Becker [etc.]"

Hmmm, IRQ 9?  Now how could that be?  Anyways, I ignored the above and went
about editing the relevant files to set myself up on the network here:
/etc/hosts, /etc/domain, hostcvt.build, reboot.

After rebooting, 'hostname' correctly identified my box; also, I was able
to telnet in loopback-mode and actually send mail to myself.  However,
telnet-ing to another system on the network proved futile (I paraphrase):

    "Timeout detected, jiffy failure, potential interrupt conflict IRQ 9"

What might I be doing wrong ? If the above information proves insufficient,
let me know what is needed to better pin-point the problem, and I'll go
about finding it...

Any help is much appreciated.

Dan.

Linux: Way cool!

|-----------------------------------------------------------------------|
|   Dan Kesch,                      Tel. (203) 298-8888 ext. 7142       |

|-----------------------------------------------------------------------|

2. DAT Changers and Linux?

3. Getting smail to work with SLS 1.01

4. Unix and Sybase / Oracle and NT - Integration experience - Permanent-Toronto - Dynamic Company and working environment!

5. Help: DPT SCSI controller with SLS 1.01

6. transfer file from HP9000 to Solaris

7. Need help w/TCP-IP (SLS 1.01)

8. Looking for Sr. Unix Admin. in N. VA

9. SLS 1.01

10. SLS 1.01 won't boot

11. SLS 1.01 A2 Problems...

12. SLS 1.01 small probs...

13. Compiling tin 1.18 on SLS 1.01