From: Martin McCormick <martin@dc.cis.okstate.edu>
To: blinux-list@redhat.com
Subject: Re: Sony cd writer problem (Martin)
Date: Mon, 21 Oct 2002 10:21:51 -0500 [thread overview]
Message-ID: <200210211521.g9LFLpG72474@dc.cis.okstate.edu> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]
When I give the command
mkisofs -l -R -q /home/martin/dsp |cdrecord -dev=/dev/scd0 -dummy -
I get
scsidev: '/dev/scd0'
devname: '/dev/scd0'
scsibus: -2 target: -2 lun: -2
cdrecord: Read-only file system. Cannot open '/dev/scd0'.
Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
If you do run cdrecord -scanbus, it tells you to run
cdrecord -scanbus for possible targets. How special! And, yes,
I was root when I ran those commands.
The messages that give a minus 2 for the target and LUN
ar the last useful messages. I think all the rest are just
attempts by cdrecord to make sense of the situation and be
helpful.
If I try one of the syntax suggestions of just the target
and the LUN as in 0,0 instead of 0,0,0, I start getting my old
familiar /dev/pg0 routine again.
I did check in to a couple of other possibilities which,
like many long shots, turned out to be dead ends. I put in
parallel printer support with no change and also checked on the
parallel IDE kernel support which is so far off the mark that it
can't possibly be the reason for this problem.
The other system I have access to that works does not
have a /dev/pg0 and doesn't seem to need it.
"Willem van der Walt<vdwaltw@health.gov.za>" writes:
>Hi,
>What does some thing like
>eject /dev/scd0
>produce? Does it open the drive or complain about the device?
>That 0,0,0 should also be known to the system as /dev/scd0
>regards, Willem
>
>
>--
>Willem van der Walt
>Information Services Directorate
>Department of Health
>South Africa
>tel: 27 12 3120700
>
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
next reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Martin McCormick [this message]
` Willem van der Walt<vdwaltw@health.gov.za>
-- strict thread matches above, loose matches on Subject: below --
Martin McCormick
Martin McCormick
` L. C. Robinson
Willem van der Walt<vdwaltw@health.gov.za>
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=200210211521.g9LFLpG72474@dc.cis.okstate.edu \
--to=martin@dc.cis.okstate.edu \
--cc=blinux-list@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).