Subject: Re: ZIP Drive/Panic
To: None <mcmahill@alum.mit.edu>
From: Bill Studenmund <wrstuden@loki.stanford.edu>
List: port-mac68k
Date: 12/05/1997 19:31:17
> I just purchased a zip drive to use on my Mac IIci with NetBSD and
> am having some problems. I followed the How-To (using silver lining
> for partitioning) and managed to get illegal instruction traps over
> and over again.
>
> One question about the How-To, it has 6144 blocks for eschatology
> which I thought we didn't need? Also, I am planning on using the
> disk for backups and archiving some old stuff so am I correct in
> assuming I also don't need the swap partition either? (I guess thats
> actually 2 questions). Anyway, I have tried both the #'s from the
> How-To and also
Right.
> 194036 blocks for A/UX Root&Usr Slice0
> with the rest for HFS.
>
> Mkfs (1.45) seems to run ok, I have tried the How-To numbers
> (using the appropriate number for file system size) and also
> tried what ever defaults came up.
>
> When I boot NetBSD (single user)
>
> NetBSD 1.3_ALPHA (GENERIC) #48: Fri Nov 7 16:25:23 PST 1997
> allen@c610:/usr/src/sys/arch/mac68k/compile/GENERIC
> Apple Macintosh IIci (68030)
> .
> .
> .
> ncrscsi0 at obio0
That's probably a problem. The Zip drive doesn't like the ncrscsi driver.
:-( Try the sbc driver.
> scsibus0 at ncrscsi0: 8 targets
> sd0 at scsibus0 targ 0 lun 0: <QUANTUM, LP80S 980809404, 3.3> SCSI2 0/direct fixed
> sd0: 80MB, 921 cyl, 4 head, 44 sec, 512 bytes/sect x 164139 sectors
> sd1 at scsibus0 targ 1 lun 0: <QUANTUM, FIREBALL1080S, 1Q09> SCSI2 0/direct fixed
> sd1: 1042MB, 3835 cyl, 4 head, 139 sec, 512 bytes/sect x 2134305 sectors
> cd0 at scsibus0 targ 5 lun 0: <MATSHITA, CD-ROM CR-8004A, 2.0a> SCSI2 5/cdrom removable
> sd2 at scsibus0 targ 6 lun 0: <IOMEGA, ZIP 100, F.09> SCSI2 0/direct removable
> sd2: drive offline
> ^^^ This is with the zip ejected. With the zip in, I get 96MB, 96cyl, 64heads,32sectors
Sounds like what mine does.
> .
> .
>
> Then
> disklabel sd2
>
> prints out some of the right stuff, but gives a kernel panic (illegal instruction
> trap) at about the point where the prompt should come back.
>
> fsck -f /dev/sd2a
>
> gives a kernel panic. after making it to the point of "marking file system clean"
>
> newfs /dev/sd2a
>
> gives a kernel panic. towards the end (after listing where the super block
> backups are).
What kind of panic? The debugger should come up, and you can type "t"
to get a stack trace.
Take care,
Bill