From: Floydsmith@aol.com
To: linux-kernel@vger.kernel.org, linux-tape@vger.kernel.org
Cc: Floydsmith@aol.com
Subject: idetape broke in 2.4.x-2.4.9-ac5 (write OK but not read) ide-scsi works in 2.4.4
Date: Sat, 1 Sep 2001 11:03:12 EDT [thread overview]
Message-ID: <93.f9abf44.28c252b0@aol.com> (raw)
Now, I can get everything (my ide ls-120 and ide HP 8Gig tape) to work in
2.2.18. I can also get both to work in 2.4.4 (and earlier 2.4.x) but only
with what I believe is an unnecessay "workarround" - namely by configuring
IDESCSI into the kernel (SCSI emulation) and then using boot param
hdc=ide-scsi. However, I feel, that I should not have to do that with any
kernel (that is, SCSI emulation should be optional for this device) because
this was the case for 2.2.18.
If I try not to use SCSI emulation for all 2.4.x kernels (including:
Kernel 2.4.9-ac5 on i686
then
ide-tape: ht0: I/O error, pc = 8, key = 5, asc = 2c, ascq = 0
tar: /dev/ht0: Cannot read: Input/output error
(writes work OK though)
As mentioned above, scsi emulation works for 2.4.4 (reads and writes). But if
turned on in 2.4.9-ac5, then I get
/dev/st0: No such device
So, with kernels above 2.4.4, I can't use the drive at all (or at least can't
"read" with it which makes it useless).
The ideal situtation (at least for me) would be to have 2.4.x kernels behave
like the 2.2.x ones, that is, scsi emulation would not need to be turned on
for these ide drives (that is, it would be optional) and I would go back to
using /dev/ht0.
Floyd,
next reply other threads:[~2001-09-01 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-01 15:03 Floydsmith [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-01 18:08 idetape broke in 2.4.x-2.4.9-ac5 (write OK but not read) ide-scsi works in 2.4.4 Mikael Pettersson
[not found] <mailman.999367801.660.linux-kernel2news@redhat.com>
2001-09-04 0:14 ` Pete Zaitcev
2001-09-04 22:34 Mikael Pettersson
2001-09-28 3:40 ` Pete Zaitcev
2001-09-28 9:15 ` Mikael Pettersson
2001-09-29 2:35 ` Pete Zaitcev
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=93.f9abf44.28c252b0@aol.com \
--to=floydsmith@aol.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tape@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