From: "Olaf Frączyk" <olaf@cbk.poznan.pl>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 BUG - can't write DVD-RAM - reported as write-protected
Date: Tue, 09 Mar 2004 08:59:25 +0100 [thread overview]
Message-ID: <1078819165.1525.1.camel@venus.local.navi.pl> (raw)
In-Reply-To: <20040307105911.GH23525@suse.de>
On Sun, 2004-03-07 at 11:59, Jens Axboe wrote:
> On Fri, Mar 05 2004, Olaf Fr?czyk wrote:
> > On Fri, 2004-03-05 at 09:23, Jens Axboe wrote:
> > > On Thu, Mar 04 2004, Olaf Fr?czyk wrote:
> > > > Hi,
> > > > I switched to 2.6.3 from 2.4.x serie.
> > > > When I mount DVD-RAM it is mounted read-only:
> > > >
> > > > [root@venus olaf]# mount /dev/dvdram /mnt/dvdram
> > > > mount: block device /dev/dvdram is write-protected, mounting read-only
> > > > [root@venus olaf]#
> > > >
> > > > In 2.4 it is mounted correctly as read-write.
> > > >
> > > > Drive: Panasonic LF-201, reported in Linux as:
> > > > MATSHITA DVD-RAM LF-D200 A120
> > > >
> > > > SCSI controller: Adaptec 2940U2W
> > >
> > > What does cat /proc/sys/dev/cdrom/info say? Do you get any kernel
> > > messages in dmesg when the rw mount fails?
> >
> > I get nothing in /var/log/dmesg and in /var/log/messages
> > In /proc/sys/dev/cdrom/info I get:
> > [olaf@venus olaf]$ cat /proc/sys/dev/cdrom/info
> > CD-ROM information, Id: cdrom.c 3.20 2003/12/17
> >
> > drive name: sr1 sr0 hdc
> > drive speed: 0 16 44
> > drive # of slots: 1 1 1
> > Can close tray: 1 1 1
> > Can open tray: 1 1 1
> > Can lock tray: 1 1 1
> > Can change speed: 1 1 1
> > Can select disk: 0 0 0
> > Can read multisession: 1 1 1
> > Can read MCN: 1 1 1
> > Reports media changed: 1 1 1
> > Can play audio: 1 1 1
> > Can write CD-R: 0 1 1
> > Can write CD-RW: 0 1 1
> > Can read DVD: 1 0 0
> > Can write DVD-R: 0 0 0
> > Can write DVD-RAM: 1 0 0
> > Can read MRW: 0 0 1
> > Can write MRW: 0 0 1
> >
> > The one I'm mounting is /dev/scd1.
> > As there is capablity to write-protect DVD-RAM disk (like a 1.44"
> > Floppy), I think that the linux kernel interprets some message from
> > device in wrong way.
>
> Please repeat with this patch applied and send back the results, thanks.
>
> ===== drivers/cdrom/cdrom.c 1.48 vs edited =====
> --- 1.48/drivers/cdrom/cdrom.c Mon Feb 9 21:58:21 2004
> +++ edited/drivers/cdrom/cdrom.c Sun Mar 7 11:58:40 2004
> @@ -645,9 +645,12 @@
> {
> disc_information di;
>
> - if (cdrom_get_disc_info(cdi, &di))
> + if (cdrom_get_disc_info(cdi, &di)) {
> + printk("cdrom: read di failed\n");
> return 0;
> + }
>
> + printk("cdrom: erasable: %d\n", di.erasable);
> return di.erasable;
> }
>
I get:
cdrom: read di failed
Regards,
Olaf
next prev parent reply other threads:[~2004-03-09 7:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 21:15 Olaf Frączyk
2004-03-05 8:23 ` Jens Axboe
2004-03-05 11:45 ` Olaf Frączyk
2004-03-05 20:51 ` Daniel Egger
2004-03-07 10:59 ` Jens Axboe
2004-03-09 7:59 ` Olaf Frączyk [this message]
2004-03-09 9:12 ` Jens Axboe
2004-03-11 1:48 ` Thomas Duda
2004-03-12 20:03 ` News on: " Thomas Duda
2004-03-14 11:17 ` Olaf Frączyk
2004-03-14 11:22 ` Jens Axboe
2004-03-14 11:23 ` Jens Axboe
2004-03-23 14:50 ` Olaf Frączyk
2004-03-23 15:23 ` Jens Axboe
2004-03-23 15:36 ` Olaf Frączyk
2004-03-23 15:32 ` Olaf Frączyk
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=1078819165.1525.1.camel@venus.local.navi.pl \
--to=olaf@cbk.poznan.pl \
--cc=axboe@suse.de \
--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®