home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!mintaka.lcs.mit.edu!ai-lab!hal.gnu.ai.mit.edu!jimc
- From: jimc@hal.gnu.ai.mit.edu (James Carpenter)
- Newsgroups: comp.os.linux
- Subject: Re: Seagte ST-01 with Quantum Prodrive ELS
- Date: 29 Dec 1992 06:48:43 GMT
- Organization: Massachusetts Institute of Technology
- Lines: 42
- Message-ID: <1hoscbINNm8i@life.ai.mit.edu>
- References: <1hgbmcINNcbe@life.ai.mit.edu> <1hgc14INNchj@life.ai.mit.edu>
- NNTP-Posting-Host: hal.gnu.ai.mit.edu
-
- I have things working a little bit better now. And I have linux working with
- it also!
-
- But the keyboard still hangs (see below).
-
- I have that AUTO_IRQ thing enabled and at boot the first line on the screen
- says something about a "wild interrupt" (I think thats it) for IRQ 1
- (keyboard). What does this mean and could it be related to my problems?
-
- I know this isn't really Linux now so I guess I should move it over to
- comp.sys.ibm.pc.hardware (including this note). Is there any place else I
- should look for help?
-
-
- I have solved half of my ST-01 problems. I have the hard drive working
- PERFECTLY now but the keyboard still hangs. The drive can be working, turned
- off, or unpluged, and sooner or later the keyboard will hang. I've done all
- the things with the jumpers (changing IRQ, base address, & 0W/S) but nothing.
- There is nothing special about my machine (that I know of, poor docs.) and
- there is NO cache. And I know its not a problem with the operating system.
-
- I just noticed something... The keyboard doesn't hang totally SOMETIMES. It
- looks like sometimes the keys just get all messed up, BAD. For example "v"
- SOMETIMES transmits TWO carriage returns. "d" is a backspace. And most other
- letters transmit stuff above 128 (It likes the line stuff i.e. 179). And one
- of the keys will turn the Scrool Lock light on. Next time it hangs the keys
- can transmit something totally different.
-
- I know this isn't my keyboard. I tried a different type keyboard.
-
- PLEASE tell me that someone else out there has had the same problem. I don't
- want to be the only guy thats gone through this :-)
-
- P.S. I fixed the drive problem by pulling a jumper on the motherboard that
- controlled something called "pipeline". Could someone tell me what this is
- so I can figure what isn't going to work now without it.
-
- --
-
- Jim Carpenter
- CARPENTER@Eisner.DECUS.Org
- jimc@gnu.ai.mit.edu
-