home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!network.ucsd.edu!sdcrsi!equalizer!timbuk.cray.com!hemlock.cray.com!overby
- From: overby@cray.com (Glen Overby)
- Subject: It Boots (Re: problems bringing up 386BSD 0.1)
- Message-ID: <1992Jul21.090445.7901@hemlock.cray.com>
- Lines: 27
- Organization: /dev/null
- References: <michaelv.711604391@help.cc.iastate.edu> <greg.711645054@hibp1.ecse.rpi.edu> <1992Jul20.212320.20786@hemlock.cray.com>
- Date: 21 Jul 92 09:04:45 CDT
-
- /* yes, a folowup to my own posting */
- In article <1992Jul20.212320.20786@hemlock.cray.com> overby@cray.com I wrote:
- >I, too, am a member of the "It Won't Boot" clan.
-
- No longer!
-
- Last night I woke up with an idea in my head. A WD controler that isn't
- really there; a poorly documented jumper in the Seagate manual. Could it
- be...
-
- The Seagate ST01, ST02 controlers have a "compatability" register that emulate
- the AT disk controler's register at 0x1F4. This is documented in Section 3.5
- in the ST01, ST02 SCSI Host Adapter Product Manual, Seagate pub number
- 36027-002 Rev G. When JP6 is enabled, the controler responds to I/O address
- 0x1F4 as an AT controler would.
-
- This jumper describes the register very poorly; it talks about both hard disk
- controlers and 360K floppies at the same time.
-
- When I moved this jumper to the "disabled" position, the 386BSD 'install' disk
- booted fine.
-
- Now to recompile with my ST02 driver, and I'll be up and running!
-
- And to think that just maybe I could have had 0.0 up two months ago...
-
- Glen Overby
-