From: R-ealitY <jalves@santiagonet.com.br>
To: linux-kernel@vger.kernel.org
Subject: MATSHITA CR-581 doesn't work under 2.4.17
Date: Thu, 07 Feb 2002 18:24:01 -0200 [thread overview]
Message-ID: <3C62E261.4030703@santiagonet.com.br> (raw)
Hi. I have a MATSHITA CR-581 which works under 2.2.19 but not 2.4.17.
Here's the dmesg output:
2.2.19:
hdc: MATSHITA CR-581, ATAPI CDROM drive
hdc: ATAPI 4X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.11
VFS: Disk change detected on device ide1(22,0)
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
2.4.17:
hdc: MATSHITA CR-581, ATAPI CD/DVD-ROM drive
hdc: ATAPI 4X CD-ROM drive, 128kB Cache, DMA
Uniform CD-ROM driver Revision: 3.12
VFS: Disk change detected on device ide1(22,0)
hdc: irq timeout: status=0xd8 { Busy }
hdc: DMA disabled
hdc: ATAPI reset complete
hdc: tray open
end_request: I/O error, dev 16:00 (hdc), sector 64
isofs_read_super: bread failed, dev=16:00, iso_blknum=16, block=32
lsmod:
2.2.19:
ide-cd 24288 1 (autoclean)
cdrom 27264 0 (autoclean) [ide-cd]
isofs 16864 1 (autoclean)
2.4.17:
ide-cd 25008 0 (autoclean)
cdrom 27008 0 (autoclean) [ide-cd]
isofs 24976 0 (autoclean)
inflate_fs 18032 0 (autoclean) [isofs]
The error appears when I try to mount it:
$ mount /mnt/cdrom
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
or too many mounted file systems
mount output from 2.2.19:
/dev/hdc on /mnt/cdrom type iso9660 (ro,noexec,nosuid,nodev,user=borracho)
Anybody know what's wrong with the 2.4.17 driver ?
next reply other threads:[~2002-02-08 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 20:24 R-ealitY [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-07 13:46 Jose Alves
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=3C62E261.4030703@santiagonet.com.br \
--to=jalves@santiagonet.com.br \
--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
all inboxes | Powered by JetHome®