Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!disco.iinet.net.au!news.uoregon.edu!vixen.cso.uiuc.edu!newsfeed.internetmci.com!in2.uu.net!news.eden.com!arlut.utexas.edu!geraldo.cc.utexas.edu!brazile
From: brazile@math.utexas.edu (Jason Brazile)
Newsgroups: comp.unix.bsd.misc,comp.unix.bsd.freebsd.misc
Subject: Re: FreeBSD 2.1 and SyQuest
Date: 24 May 1996 01:07:53 GMT
Organization: Department of Mathematics, University of Texas at Austin
Lines: 119
Message-ID: <4o3259$q4c@geraldo.cc.utexas.edu>
References: <832891962.8850.0@cisex73.demon.co.uk>
NNTP-Posting-Host: lanczos.ma.utexas.edu
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.misc:1099 comp.unix.bsd.freebsd.misc:19944
In article <832891962.8850.0@cisex73.demon.co.uk>,
<andys@cityscape.co.uk> wrote:
>I am having various problems with getting a SyQuest EZ135 to work
>correctly under FreeBSD 2.1(January), these include:-
>
>Formatting the cartridge
I used the syquest provided msdos program to do this although I do it
mostly to check out the media. This may not be needed.
>crc errors
??
There were a couple of times that I noticed what seemed to be hardware
problems but when I played with SCSI cables/termination, everything was
fine.
>Machine locking out other devices if the cartridge isn't present
If the device is on but there are no cartridges, then the controller
gets stuck at the probe. However if I unmount and remove a cartridge
after I'm up I don't notice any problems.
>FreeBSD thinking is 250Mb instead of 135Mb (DOS & BIOS are OK)
See disktab entry below.
>Can anyone send me any info, help or guidance with anything to do
>on getting a SyQuest working with FreeBSD, I will then construct
>and entry for the FAQ.
Here is what I do (this is for NetBSD, but should also work for FreeBSD):
1) use sqprep.exe to verify a new cartridge is defect free. I have
about 8 of them and only 1 had problems - I returned it.
2) use pfdisk to set the pc partitioning.
Boot unix
3) make an appropriate disktab entry
4) disklabel
5) newfs
In more detail:
1) Here is the mdir listing of the diskette:
Volume in drive A has no label
Directory for A:/
IBMBIO COM 33430 5-11-92 5:00a
IBMDOS COM 37394 5-11-92 5:00a
COMMAND COM 47845 5-11-92 5:00a
SQPREP EXE 195661 6-19-95 3:49p
SQDRIVER SYS 17627 10-31-95 9:50a
CONFIG SYS 69 2-29-96 3:01a
DOSCAM SYS 40688 11-16-94 1:46p
ASPICAM SYS 2242 10-31-94 3:39p
PFDISK EXE 17590 8-24-93 5:47p
9 File(s) 1061888 bytes free
Here is what config.sys has in it:
device=a:\doscam.sys
device=a:\aspicam.sys
device=a:\sqdriver.sys
Note that for other SCSI controllers, you would probably use something
else besides aspicam.sys. But that's MSDOS stuff that I try to know as
little of as possible.
2) I usually just create one "fdisk" partition of type BSD (165).
3) Here are disktab entries I use:
ez135unix|Syquest EZ Drive 135MB: \
:ty=winchester:dt=SCSI:se#512:nt#5:ns#52:nc#1008:rm#3600:\
:pa#262080:oa#0:ba#8192:fa#1024:ta=4.2BSD: \
:pc#262080:oc#0: \
:pd#262080:od#0:
ez135unixboot|Syquest EZ Drive 135MB: \
:ty=winchester:dt=SCSI:se#512:nt#5:ns#52:nc#1008:rm#3600:\
:pa#196560:oa#0:ba#8192:fa#1024:ta=4.2BSD: \
:pb#65520:ob#196560:tb=swap: \
:pc#262080:oc#0: \
:pd#262080:od#0:
The first one is to make the whole disk just one partition. The second
is what I use to include a swap partition when I am making a boot
cartridge.
Actually here is the entry I made up based on what the controller told
me about the geometry during autoconfiguration under NetBSD. If you want
to boot off of it though, you have to use what your BIOS thinks is the
geometry.
ez135real|Syquest EZ Drive 135MB: \
:ty=winchester:dt=SCSI:se#512:nt#1:ns#82:nc#3195:rm#3600:\
:pa#261990:oa#0:ba#8192:fa#1024:ta=4.2BSD: \
:pc#261990:oc#0: \
:pd#261990:od#0:
4) disklabel -w -B sd1 ez135unix
You only need the -B if you want to install boot blocks.
5) newfs /dev/rsd1a
Now you are all set to go.
These steps are from memory so check it out before submitting it to the FAQ.
Jason