Re: [PARPORT] Parallel Zip and SuSE 6.3 - Similar problem in RedHat 6.1

From: Eric Morgan (gemorgan@home.com)
Date: Mon Mar 27 2000 - 05:03:33 EST

  • Next message: Tim Waugh: "Re: [PARPORT] Parallel Zip and SuSE 6.3 - Similar problem in RedHat 6.1"

    Some more information:

    mount -t vfat /dev/sda6 /mnt/zip
    mount: block device /dev/sda6 is write-protected, mounting read-only
    mount: /dev/sda6 is not a valid block device
    ^ I can actually get this to happen with any sda# by repeatedly firing off
    the mount command using the up arrow enter...

    more /proc/scsi/scsi
    Attached devices:
    Host: scsi0 Channel: 00 Id: 06 Lun: 00 <- what does all this mean?
      Vendor: IOMEGA Model: ZIP 100 Rev: D.09
      Type: Direct-Access ANSI SCSI revision: 02

    more /proc/scsi/ppa/0
    Version : 2.03 (for Linux 2.2.x)
    Parport : parport0
    Mode : EPP 32 bit

    Eric Morgan wrote:

    > I am having troubles installing my zip drive. I need some education as I
    > am sort of a Linux novice.
    >
    > I have RH6.1 kernel 2.2.12 unmodified from default installation, P366 OC
    > to 550, Abit BM6 MB, 64Meg SDRAM, Zip100.
    >
    > Couple of basic questions first:
    > How do I tell what options were set for the current kernel?
    > What is the difference between ECP and EPP and which is best for ZIP?
    >
    > I have set my pp to EPP instead of EPP+ECP on this lists advice from
    > 1999 (never read that it was fixed).
    > I do this:
    > insmod parport
    > insmod parport_pc
    > insmod ppa -> ZIP drive spins up and light comes on
    > mount -t vfat /dev/sda4 /mnt/zip -> mount: /dev/sda4 is not a valid
    > block device
    >
    > insmod parport_probe
    > more /proc/parport/0/autoprobe
    > MODEL:Unknown device;
    > MANUFACTURER:Unknown vendor;
    >
    > if I change to modprobe no difference.
    >
    > I read somewhere in this list about the conf.modules file so I threw
    > this in with no change in results:
    > alias parport_lowlevel parport_pc
    > alias scsi_hostadapter ppa
    > options parport_pc io=0x378 irq=7
    >
    > Also I must be using dmesg wrong because I get something entirely
    > different from what others are reporting back. I get something like
    > this:
    >
    > ATAPI device hdc:
    > Error: Not ready -- (Sense key=0x02)
    > (reserved error code) -- (asc=0x3a, ascq=0x01)
    > The failed "Test Unit Ready" packet command was:
    > "00 00 00 00 00 00 00 00 00 00 00 00 "
    > VFS: Disk change detected on device ide1(22,0)
    > ATAPI device hdc:
    > Error: Not ready -- (Sense key=0x02)
    > (reserved error code) -- (asc=0x3a, ascq=0x01)
    > The failed "Test Unit Ready" packet command was:
    > "00 00 00 00 00 00 00 00 00 00 00 00 "
    > ATAPI device hdc:
    > Error: Not ready -- (Sense key=0x02)
    > (reserved error code) -- (asc=0x3a, ascq=0x01)
    > The failed "Prevent/Allow Medium Removal" packet command was:
    > "1e 00 00 00 00 00 00 00 00 00 00 00 "
    > ATAPI device hdc:
    > Error: Not ready -- (Sense key=0x02)
    > (reserved error code) -- (asc=0x3a, ascq=0x01)
    > The failed "Test Unit Ready" packet command was:
    > "00 00 00 00 00 00 00 00 00 00 00 00 "
    > VFS: Disk change detected on device ide1(22,0)
    > ATAPI device hdc:
    > Error: Not ready -- (Sense key=0x02)
    > (reserved error code) -- (asc=0x3a, ascq=0x01)
    > The failed "Test Unit Ready" packet command was:
    > "00 00 00 00 00 00 00 00 00 00 00 00 "
    > ATAPI device hdc:
    > Error: Not ready -- (Sense key=0x02)
    > (reserved error code) -- (asc=0x3a, ascq=0x01)
    > The failed "Prevent/Allow Medium Removal" packet command was:
    > "1e 00 00 00 00 00 00 00 00 00 00 00 "
    >
    > Am I getting so many of these it fills completely dmesg? What are these
    > messages telling me anyway (cant be good =)? Im pretty sure hdc is one
    > of my ide cdroms...
    >
    > Please educate me a little.
    > Thanks in advance,
    > Eric

    -- To unsubscribe, send mail to: linux-parport-request@torque.net --
    -- with the single word "unsubscribe" in the body of the message. --



    This archive was generated by hypermail 2b29 : Mon Mar 27 2000 - 05:09:44 EST