hot@integow.uucp (Roland van Hout) (04/29/91)
A while ago several versions of a driver were posted here
for the Seagate st01/st02 SCSI adapter card, originally from
a mr. Grenier if I'm not mistaken.
I saved 2 releases of them. Last week somebody gave me such
a st01 beast as a present, and a college of mine wanted to try
his SCSI WREN V (702 Mb unformatted) on this interface.
Since the WREN nowadays also says Seagate, and the driver files
were easily installed we thought it would work in a few minutes.
Also in the files for the driver the were a few references to
ESIX Rev D and it sounded like there were no problems.
When the bios was installed the WREN was recognized by the st01.
After we relinked our kernel it looked like it died on bootup,
but after a few minutes the startup screen was displayed,
with 5 scsi error messages "sending reset to scsi bus" or something
similar.
After you booted up and tried to access the scsi devices, the whole
system seems to hang!
Is there anyone who has this st01 up and running under Esix or Interactive,
how old/new are the sources? Did you have to make patches to the original?
The ROM BIOS has a version 3.2 and the st01 manual was talking about revision
2.2 or something. The interrupt we use is IRQ 5, memory adress is default,
but no BIOS installed! And also the 0WS jumper installed.
We are running on a 25 Mhz 386 no cache , but the board can be
reconfigured in it's CHIPS-set, like the NEAT at-boards, but we use the
default normally, but also tried settings with waitstates, io command
cycle delays etc. etc. etc.
Thanx
Roland
hot@integow.uucp
--
UUCP: ..!uunet!mcsun!hp4nl!integow!hot or hot@integow.UUCP
Roland van Hout, Sr. software engineer, Integrity software consultants,
Pelmolenlaan 2, 3447 GW Woerden, Netherlands,
tel +31 3480-30131, fax +31 3480-30182tin@smsc.sony.com (Le Tin) (04/30/91)
In article <1583@integow.uucp> hot@integow.uucp (Roland van Hout) writes: > >A while ago several versions of a driver were posted here >for the Seagate st01/st02 SCSI adapter card, originally from >a mr. Grenier if I'm not mistaken. The original st01 driver was from Tatu Ylonen, and was for Microport 386 UNIX v3.00e. I and several others ported to Interactive. During my porting effort, I kept in touch with Tatu and received his permissions to release my port to the net. Mike Grenier and another person did not. Since then I've received messages from Tatu that he consider me to be the official "keeper" of the st01 driver source. >I saved 2 releases of them. Last week somebody gave me such >a st01 beast as a present, and a college of mine wanted to try >his SCSI WREN V (702 Mb unformatted) on this interface. >Since the WREN nowadays also says Seagate, and the driver files >were easily installed we thought it would work in a few minutes. >Also in the files for the driver the were a few references to >ESIX Rev D and it sounded like there were no problems. >When the bios was installed the WREN was recognized by the st01. >After we relinked our kernel it looked like it died on bootup, >but after a few minutes the startup screen was displayed, >with 5 scsi error messages "sending reset to scsi bus" or something >similar. >After you booted up and tried to access the scsi devices, the whole >system seems to hang! The driver as released by Grenier has timing problems, as you had found out. I've received reports from others of panics and lock ups. The current driver I am using is quite stable, it drives an ST02 with a CDC Wren III (150MB formatted) connected. The Wren III happens to be my Usenet news disk, so it gets heavy usage. I am running Interactive v2.0.2. Since I've been very busy lately with a new job, I have not had time till recently to work on it. I am currently working on integrating the raw character device additions that Mike did and to get the driver to work under SVR4. I don't have money right now for a SCSI tape drive, so that will have to wait. >Is there anyone who has this st01 up and running under Esix or Interactive, >how old/new are the sources? Did you have to make patches to the original? >The ROM BIOS has a version 3.2 and the st01 manual was talking about revision >2.2 or something. The interrupt we use is IRQ 5, memory adress is default, >but no BIOS installed! And also the 0WS jumper installed. >We are running on a 25 Mhz 386 no cache , but the board can be >reconfigured in it's CHIPS-set, like the NEAT at-boards, but we use the >default normally, but also tried settings with waitstates, io command >cycle delays etc. etc. etc. You don't need the ROM BIOS that comes with the ST01/ST02 board. That's only needed for DOS (note: you don't need it for VPIX either). I removed mine because it seems to boot faster without the BIOS. My system also uses the C&T chipset, and have adjustable bus clock. I've tested the driver with the bus at both 6.67MHz and 10MHz without any problems. --Tin -- .---------------------------------------------------------------------- . Tin Le Work Internet: tin@smsc.Sony.COM . Sony Microsystems UUCP: {uunet,mips}!sonyusa!tin . Work: (408) 944-4157 Home Internet: tin@szebra.uu.net
mike@atc.SP.Unisys.COM (Mike Grenier) (05/01/91)
From article <1991Apr29.220501.26017@smsc.sony.com>, by tin@smsc.sony.com (Le Tin): > In article <1583@integow.uucp> hot@integow.uucp (Roland van Hout) writes: >>After you booted up and tried to access the scsi devices, the whole >>system seems to hang! > > The driver as released by Grenier has timing problems, as you had found > out. I've received reports from others of panics and lock ups. His problem appears to have nothing to do with *timing* problems but instead with not having jumpered his board for the correct memory address with what the driver expects. There is a constant in the beginning of scsi.c that says where the card is mapped at and my distribution did not use the default settings as that conflicted with the AMI bios in NEAT bios chipset on my motherboard. You can either change the define in the source or strap your card differently. *** EVERYONE - please inform me if you are having timing or other problems *** . I have not had any reports to date. > The > current driver I am using is quite stable, it drives an ST02 with a CDC > Wren III (150MB formatted) connected. The Wren III happens to be my > Usenet news disk, so it gets heavy usage. I am running Interactive v2.0.2. If it was so stable, I wouldn't have had to modify it! The basic ST-01 driver had problems when more than one request was pending on multiple drives at the same time. With one drive, as appears to be the case with your system, the basic driver worked fine but it began to have trouble with multiple drives. Consider : 1) Start a request on drive 0 (it may then disconnect) 2) Start a request on drive 1 3) drive 0 reconnects before step 2 has begun bus arbitration. Drive 1's bus arbitration will fail (as it should) but recovery doesn't appear correct. In all fairness, my version of the driver that was psoted awhile back didn't handle that case well either but it does now! -Mike Grenier mike@cimcor.mn.org