*BSD News Article 2048


Return to BSD News archive

Path: sserve!manuel!munnari.oz.au!uunet!gatech!bloom-beacon!eru.mt.luth.se!lunic!sunic!ugle.unit.no!nuug!nntp.uio.no!bootes.sds.no!toreh
From: toreh@bootes.sds.no (Tore Haraldsen)
Newsgroups: comp.unix.bsd
Subject: 386BSD & AHA1542B & CDC94171-9 Disk problem
Message-ID: <1992Jul19.121003.27453@ulrik.uio.no>
Date: 19 Jul 92 12:10:03 GMT
Sender: news@ulrik.uio.no (Mr News)
Reply-To: tha@ulrik.uio.no
Organization: Statens Datasentral A/S, SDS, Norway
Lines: 58
Nntp-Posting-Host: 192.68.77.217

First I must tell you I installed 386BSD 0.1 on a noname 50MHz 486 clone
with Quantum 240Mb IDE disk and T4000 graphics card and 3C503 ethernet
card with no problems whatsoever!! Real smooth!

So I decided to try it on my home machine too, but that was not easy...

My home machine is a Nokia/ICL 386 Deskside with original Intel boards,
	8Mb memory, 256Kb cache,
	Paradise VGA
	4 comports & parallel printer port.
	AHA1542B
		CDC9471-9 312MB disk @scsi-id 0
		Archive A2150S streamer @scsi-id 2
		Two floppy drives (0 = 1.44, 1 = 1.2)
	3C503 ethernet card (the old 8-bit type)
This system have been running DOS5.0, SCO ODT1.0, 1.1 and then 2.0beta
with no problems whatsoever, though SCO stuff would never see COM3-4.

To 386BSD:

When booting the Tiny disk, I get scsi errors and when rebooting back
to dos (to run kermit and write to you), I loose COM1-2.

The 386BSD boot reports like this:

	<banner...>
	pc0<color> at 0x60 irq 1 on isa
	com1 at 0x3f8 irq 4 on isa
	com2 at 0x2f8 irq 3 on isa
	fd0 at 0x3f0 irq 6 drq 2 on isa (I left out the 1.44&1.2 info)
	as0 at 0x330 irq 11 drq 5 on isa
	ec0 at 0x250 irq 9 iomem 0xd8000
	changing root device to fd0a
	as0b: controller error 0x16 reading fsbn 0
	scsi sense: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
	as0b: controller error 0x16 reading fsbn 0
	scsi sense: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
after which it teells me I got no swap and proceeds all the way to the
prompt. I can navigate the floppy disk, but I cannot touch the SCSI disk
without getting those two error messages (the sense prints 30 zeroes).

Since I had backups of everything (thank u, streamer!), I tore down the
whole disk, ran scsi low level formatting, and tried to boot Tiny with
the virgin disk.

No deal, same error.

I then reinstalled DOS-5.0 in a 120MB partition, restored the contents
and checked that everything was ok. Booted Tiny.

No deal, same error.

I am out of ideas now. Maybe my CDC SCSI disk have strange habits, I
don't know. Maybe the sky will fall in over me, I don't know.

Anybody got some hints, what can I do?

-- Tore Haraldsen