public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James M <dart@windeath.2y.net>
To: Gert Wollny <wollny@cns.mpg.de>
Cc: linux-kernel@vger.kernel.org, twaugh@redhat.com
Subject: Re: Parport/IMM/Zip Oops Revisited -- Filesys problem? Viro pleaselook
Date: Tue, 14 Nov 2000 18:00:44 -0600	[thread overview]
Message-ID: <3A11D22C.9E3AA068@windeath.2y.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10011150012390.684-100000@bolide.beigert.de>

Gert Wollny wrote:
> 
> Actually i never tried to mount in my testings, just did "modprobe imm". I
> did not even load sd.o, which reads the size of the medium. Output after
> successfull modprobe:
> kernel: imm: Version 2.04 (for Linux 2.4.0)
> kernel: imm_connect 1
> kernel: imm: Found device at ID 6, Attempting to use EPP 32 bit
> kernel: imm: Found device at ID 6, Attempting to use PS/2
> kernel: imm: Communication established at 0x378 with ID 6 using PS/2
> kernel: device_check 0
> kernel: scsi1 : Iomega VPI2 (imm) interface
> kernel: scsi : 2 hosts.
> kernel:   Vendor: IOMEGA    Model: ZIP 250           Rev: J.45
> kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
> 
> Even without a disk this works (if parport_pc is preloaded).
> 
> Anyway the disk in the drive was a 250MB vfat formatted one. But OTOH, the
> oops trace points to ext2.
> 
> For completeness: With the disk "modprobe sd"  gives

As you say, for completeness:

SCSI subsystem driver Revision: 1.00
parport0: PC-style at 0x378 [PCSPP]
parport0: irq 7 detected
imm: Version 2.04 (for Linux 2.4.0)
imm: Found device at ID 6, Attempting to use EPP 32 bit
imm: Found device at ID 6, Attempting to use SPP
imm: Communication established at 0x378 with ID 6 using SPP
scsi0 : Iomega VPI2 (imm) interface
  Vendor: IOMEGA    Model: ZIP 100           Rev: P.05
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi removable disk sda at scsi0, channel 0, id 6, lun 0
SCSI device sda: 196608 512-byte hdwr sectors (101 MB)
sda: Write Protect is off
 sda: sda4

As I noted in a previous posting to the list my Communication type is
misdetected as SPP when it really is EPP. The 101 MB size looks fishy
also as it usually reads 96 MB IIRC.

> 
> kernel: Detected scsi removable disk sda at scsi1, channel 0, id 6, lun 0
> kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors= 489532 [239 MB] [0.2 GB]
> kernel: sda: Write Protect is off
> kernel:  sda: sda4
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-15  0:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-07 22:33 Re:test11-pre1 - Parport/IMM/Zip Oops fixed James M
2000-11-13 22:26 ` Re:test11-pre1 Parport/IMM/Zip Oops fixed -- Are we in Florida? James M
2000-11-14 22:48   ` Parport/IMM/Zip Oops Revisited -- Filesys problem? Viro please look James M
2000-11-14 23:42     ` Gert Wollny
2000-11-15  0:00       ` James M [this message]
2000-11-15  2:26       ` Parport/IMM/Zip Oops Revisited -- Winbond James M
2000-11-15 11:08         ` Gert Wollny
2000-11-16 11:21         ` Parport/IMM/Zip LOCKUP Oops Revisited [patch included] Gert Wollny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A11D22C.9E3AA068@windeath.2y.net \
    --to=dart@windeath.2y.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twaugh@redhat.com \
    --cc=wollny@cns.mpg.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox