From: Grozdan Nikolov <microchip@chello.be>
To: linux-kernel@vger.kernel.org
Subject: imm module issues
Date: Sat, 10 Mar 2007 16:00:28 +0100 [thread overview]
Message-ID: <200703101600.28449.microchip@chello.be> (raw)
Hi,
I've compiled the 2.6.20.2 kernel today (I took the SuSE HEAD kernel instead
of the vanilla one) and I'm having issues with the "imm" module. I still use
a ZIP drive here for small backups and the "imm" module worked flawless on
kernel 2.6.18.8 but with kernel 2.6.20.2 I get error messages that the device
is offline even if the device is switched on and has a ZIP disk inside of it.
This is what I get from "dmesg" (Sorry for posting this here if it's the wrong
place, but I wasn't sure if I should report this to Novell's bugzilla because
I'm using the SuSE head kernel which is not officially supported)
imm: Version 2.05 (for Linux 2.4.0)
imm: Found device at ID 6, Attempting to use EPP 32 bit
imm: Communication established at 0x378 with ID 6 using EPP 32 bit
scsi1 : Iomega VPI2 (imm) interface
scsi 1:0:6:0: Direct-Access IOMEGA ZIP 250 L.58 PQ: 0 ANSI: 2
sd 1:0:6:0: scsi: Device offlined - not ready after error recovery
sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sd 1:0:6:0: rejecting I/O to offline device
sda : READ CAPACITY failed.
sda : status=0, message=00, host=1, driver=00
sda : sense not available.
sd 1:0:6:0: rejecting I/O to offline device
sda: Write Protect is off
sda: Mode Sense: 00 00 00 00
sd 1:0:6:0: rejecting I/O to offline device
sda: asking for cache data failed
sda: assuming drive cache: write through
sd 1:0:6:0: Attached scsi removable disk sda
sd 1:0:6:0: Attached scsi generic sg0 type 0
--
go openSUSE go!
reply other threads:[~2007-03-10 15:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200703101600.28449.microchip@chello.be \
--to=microchip@chello.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox