All of lore.kernel.org
 help / color / mirror / Atom feed
From: David van Hoose <davidvh@cox.net>
To: Riley Williams <Riley@Williams.Name>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: [2.4.21-rc1] Zipdrive messages too much
Date: Tue, 06 May 2003 16:18:48 -0500	[thread overview]
Message-ID: <3EB826B8.3030307@cox.net> (raw)
In-Reply-To: <BKEGKPICNAKILKJKMHCAEENJCKAA.Riley@Williams.Name>

The problem is that the zipdrive works perfectly in kernel 2.5.69-bk1 
without all of these messages. It floods me with these messages in 
2.4.21-rc1 though. That is why I think something got lost in a patch 
somewhere.

-David

Riley Williams wrote:
> Hi David.
> 
> I have a Zip-250 drive that works fine under Linux, but it's the EIDE model,
> not the parallel-SCSI version you appear to have. As a result, I don't know
> whether this is relevant, but...
> 
> I remember reading somewhere that there was a jumper on the parallel-SCSI
> zip drives that changed how it works, and I seem to recall that whilst the
> M$ Windows driver had no problem in either position, the Linux driver only
> worked in one position as the other was undocumented.
> 
> Not sure if that was ever sorted out as I haven't heard about it for
> years...
> 
> Best wishes from Riley.
> ---
>  * Nothing as pretty as a smile, nothing as ugly as a frown.
> 
> 
>  >>> Apr 23 11:41:35 aeon kernel: sda : READ CAPACITY failed.
>  >>> Apr 23 11:41:35 aeon kernel: sda : status = 1, message = 00, host = 0,
>  >>> driver = 08
>  >>> Apr 23 11:41:35 aeon kernel: Current sd00:00: sns = 70  2
>  >>> Apr 23 11:41:35 aeon kernel: ASC=3a ASCQ= 0
>  >>> Apr 23 11:41:35 aeon kernel: Raw sense data:0x70 0x00 0x02 0x00 0x00
>  >>> 0x00 0x00 0x11 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0xff
>  >>> 0xfe 0x01 0x00 0x00 0x00 0x00
>  >>> Apr 23 11:41:35 aeon kernel: sda : block size assumed to be 512 bytes,
>  >>> disk size 1GB.
>  >>> Apr 23 11:41:35 aeon kernel: sda: Write Protect is off
>  >>> Apr 23 11:41:35 aeon kernel:  sda: I/O error: dev 08:00, sector 0
>  >>> Apr 23 11:41:35 aeon kernel:  I/O error: dev 08:00, sector 0
>  >>> Apr 23 11:41:35 aeon kernel:  unable to read partition table
>  >>> Apr 23 11:41:35 aeon kernel: Device not ready.  Make sure there is a
>  >>> disc in the drive.
> 
>  > I added more SCSI logging support so the below is better info than the
>  > above. Sorry. Forgot the logging when I posted this. I knew it looked
>  > extra weird.
>  >
>  > sda : READ CAPACITY failed.
>  > sda : status = 1, message = 00, host = 0, driver = 08
>  > Current sd00:00: sense key Not Ready
>  > Additional sense indicates Medium not present
>  > sda : block size assumed to be 512 bytes, disk size 1GB.
>  > sda: Write Protect is off
>  >   sda: I/O error: dev 08:00, sector 0
>  >   I/O error: dev 08:00, sector 0
>  >   unable to read partition table
>  > Device not ready.  Make sure there is a disc in the drive.
>  >
>  > Hope this helps more.


       reply	other threads:[~2003-05-06 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BKEGKPICNAKILKJKMHCAEENJCKAA.Riley@Williams.Name>
2003-05-06 21:18 ` David van Hoose [this message]
2003-04-23 17:02 [2.4.21-rc1] Zipdrive messages too much David van Hoose
2003-05-06 18:20 ` Bill Davidsen
2003-05-06 18:53   ` David van Hoose
2003-05-06 19:08   ` David van Hoose

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=3EB826B8.3030307@cox.net \
    --to=davidvh@cox.net \
    --cc=Riley@Williams.Name \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.