[559] in linux-scsi channel archive
IN-2000 and Linux, some progress
daemon@ATHENA.MIT.EDU (Stephen Walton)
Tue Aug 29 19:44:10 1995
Date: Tue, 29 Aug 1995 09:16:12 -0700 (PDT)
From: Stephen Walton <swalton@galileo.csun.edu>
To: linux-scsi@vger.rutgers.edu
Summary: Everex 486/33, 8 MB RAM, TVGA card. IN-2000 SCSI host adapter
with latest BIOS (version 887-1.3). HP C2247 1 GB disk and Exabyte
8200 tape drive, terminators on latter. NE-2000 Ethernet card; system
on LAN. Slackware 2.3.0 distribution except for kernel (see below).
Status up until now: system is somewhat better with a newly recompiled
custom version 1.2.13 kernel, which includes no SCSI or Ethernet
drivers except the ones for the cards I have. I also changed the
IN-2000 I/O space from its factory default setting of 110h-11Fh to
200H-20F. The company tells me that the former setting conflicts with
some (undocumented) addresses used by 3COM Ethernet cards. Finally, I
moved the IRQ on the NE-2000 to 5 from 2. With the latter setting,
the Linux kernel was claiming it was at IRQ 9 (?).
However, while more stable, the system is still acting as if the
virtual memory subsystem doesn't work. When recompiling the 1.2.13
kernel under 1.2.8, I couldn't get it to work very well unless I
turned off the -pipe option. Even now, weird things happen, like
e-mail from cron to root complaining about not being able to find
"/usr/lib,atrun" (sic) or, just now, an attempt to build the 1.3.21
kernel attempting to give gcc the "-fomit-frale-pointer" switch. So
far, I've not been able to access the Exabyte drive from the Linux
side at all, but it works fine with the ASPI MS/DOS tar which I have.
Any more ideas? I'm going to give the 1.3.21 kernel a spin just to
see what happens.
Stephen Walton, California State University, Northridge
"Be careful what you wish for; you might get it." swalton@csun.edu
