Problems setting up video on RedHat 2.1

Problems setting up video on RedHat 2.1

Post by John C Slimi » Tue, 19 Aug 1997 04:00:00



I am having problems getting the video set up
correctly on the following:

Software: RedHat 2.1 (January 1995)

Machine: Pentium P75, 16MB
Monitor: MAG 15T (upto 85 Mhz, 256 colors at 1024x768)
Video Card: Generic with Cirrus Logic GD5446,
            1 MB memory, 64 bit Graphics adapters, PCI

I can get this to work only as VGA16.
startx prints the following:
VGA16: Generic Video Boards
VGA16: Monitor ID Generic Multisync
       chipset: generic
       videoram: 1024K
       clocks: 25.22  28.32  31.49  36.07
       max allowed dot clock: 90 Mhz
       Mode 800x600_2  clock=36.  clock used 36.07
       Mode 640x480_2  clock=25.175  clock used 25.220
       Virtual resolution set to 1024x768

Symptom: xterm provides 2 (two) xterm screens with 2
       cursors, as well as disappearing as I move down
       the screen. When I set virtual resolution to
       800x600 the xterm problem mostly goes away, but
       then gs produces screens that are essentially
       unreadable.

Any ideas?

And a BIG THANK YOU in advance.

 
 
 

1. More Info on Diamond Stealth 64 Video 2001 + RedHat 2.1 Problem

I previously described a problem I have when running RedHat 2.1 on
a 150Mhz Pentium system with a NCR 810 PCI SCSI adapter and a
Diamond Stealth 64 Video 2001 PCI graphics board. The system hangs
trying to access the SCSI disk I run Linux from when I try to start
the X server. Win NT and Win95 work perfectly.

Several people replied saying they have the same problem so there's
something going on here and we don't know what it is.

I went to the computer store where I bought my computer (it's only
a week old) to exchange the Stealth card for another one (the one
they gave me only had 1MB but I paid for a 2MB card). While I was
there I got the tech to put the new board into a system running
Linux and try to bring up X. This worked. I thought I might be having
an IRQ problem and showed me how the AMI bios lets you specify which
IRQ a PCI device is to have.

So I went home and looked the what the Award BIOS on my ASAS TP4N
motherboard did about this. It only let me explicity set the IRQ to
14 or 15, or to have it automatically selected. (Does anybody know
why they limit my selection to 14 and 15?). So, I did some fooling
around with these and once I got the X server to start, although it
appeared to hang in a different way this time, maybe because of my
messing with the IRQs.

So, I booted Win95 and used the Device Manager there to see what
IRQ things are really getting. It turns out that 14 and 15 are
taken by the IDE channels on the motherboard, the NCR was given IRQ 11,
and the Stealth got 10.

I booted Linux and made careful note of the IRQs there. The NCR again
got 11 but I couldn't see what the Stealth got. How do I see this?

I bet there is some sort of IRQ conflict causing the hang but I don't
know enough about how IRQs work with PCI devices to know what to do.
Any suggestions?

Jon
--
Anything you read here is my opinion and in no way represents the Univ. of Cal.

"I deal with dreamers, and telephone screamers." -- Joni Mitchell

2. Conner 420MB Tape Drive supported in Linux?

3. Setting up ppp with Redhat 2.1

4. Q: pppd 2.1.2c broken over kernel 1.2.7?

5. Setting up PPP on RedHat 2.1

6. Organization: Arco Chemical Company

7. ATI XclaimVR and video on YDL 2.1 problem

8. 2nd HD problems

9. YDL 2.1 Video Problems: 9500/132

10. 2.1 Gbyte Linux 3.0.0 April 96 install goof-ups...

11. InterNetNews 2.1 lock ups on FreeBSD 3.0

12. UPS debugger on FreeBSD 2.1.x

13. x86 2.1 Video problems