Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!olivea!uunet!demon!ronald
From: ronald@gate.demon.co.uk (Ronald Khoo)
Newsgroups: comp.unix.bsd
Subject: It works, thanks, a few problems (Re: New scsi system beta3 (part 1 of 10))
Message-ID: <BvqCEE.6FB@gate.demon.co.uk>
Date: 7 Oct 92 02:32:37 GMT
References: <1992Oct3.035858.13004@tfs.com>
Organization: Demon Systems Ltd.
Lines: 68
julian@tfs.com (Julian Elischer) wrote:
> # This is a shell archive.
Verily! Well, I've just tried it out with a aha 1742 and a horrid
cheapo disc we had lying around, and didn't have too many problems.
I started out with a stock 0.1, added Terry's beta patch kit, and, after
upgrading to gcc 1.42 (2.2.2 is being compiled at the moment)
the next step was to try out Julian's driver.
My problems were:
a) had to create a zero length pio.h file to keep aha1742.c
happy (perhaps should omit the #include line from the .c file ?)
Just curious: what is pio.h ?
b) locore.s didn't seem to have outl and inl defined.
My 386 is close to nonexistent, so I guessed this:
(is it right ?)
.globl _inl
_inl: movl 4(%esp),%edx
subl %eax,%eax # clr eax, presumably unnecessary ?
NOP
inl %dx,%eax
ret
.globl _outl
_outl: movl 4(%esp),%edx
NOP
movl 8(%esp),%eax
outl %eax,%dx
NOP
ret
c) The readme isn't quite clear about bootblocks to use ..
Does it refer to using the standard asboot/bootas ?
Disklabel seems to be unhappy if I don't specify them at all,
but I don't actually want to boot off the slow old SCSI,
since it's fine for archival use, but not much else.
But for reference, I'd like to know which bootblocks the
README refers to.
d) I agree that a system for encoding target/luns into the system
would be nice. The old drive I'm playing with seems to
answer to ALL LUNs that the probe asks for, so the probe
sees 8 devices where there is only one. I got fed up
so I hacked the probe to look for LUN-0 only, and that
seems to work fine, but I'd be interested to hear of a
neater way to cope with old kit like this.
e) it seems to be a fairly large driver, and I didn't seem to
be able to delete the tape and cd sub-drivers (but then
I haven't tried very hard yet). So I had to take quite
a lot of stuff out of my kernel to get it small enough to
boot.
f) I guessed that the geometry to use in calculating disktab
was the rigid geometry as reported by the probe and not the
BIOS remapped geometry ? Well it seems to work like that.
Does this not have implications for /386bsd lying beyond
1024 cylinders or am I barking up the wrong tree ?
Lots of questions I know, but I'm sure lots of people would ask the same
ones, so may I perhaps suggest that the author include a Q&A section
in his next distrib ?
In any case, thank you for your wonderful work.