Re: Sony cd writer problem (Martin)

Re: Sony cd writer problem (Martin)

[Martin McCormick]

"Willem van der Walt<vdwaltw@health.gov.za>" writes:
>What does some thing like 
>eject /dev/scd0
>produce? Does it open the drive or complain about the device?

	Actually, neither.  It complains about the eject command.

	/dev/scd0 is known by the system and works fine at least
when I am mounting a CDROM for reading.

	Before using the SCSI emulation, this device was
/dev/cdrom so that behavior is exactly as it should be.

	This is the darndest problem I have come across yet.  If
I type

mount /dev/scd0 /mnt

I can read the disk as if it was a SCSI device.  I don't know
what else to try.

	By the way, my utmost thanks to everybody who has had a
suggestion.  I think I have either done something very odd in the
setup or kernel building process or we have a bug of some kind.
This just doesn't add up.

Re: Sony cd writer problem (Martin)

[L. C. Robinson]

A few hints:
On our systems here, we have:
ls -l /dev/cdrom                 
lrwxrwxrwx   1 root     root            8 Feb 28  2001 /dev/cdrom -> /dev/sr0
for our CD-RWs

Also from ... doc/cdrtools-cdrecord-1.10/README.ATAPI:
   5.  In the /etc/lilo.conf file add an append line for ide-scsi, in
   my case:
        append = "hdc=ide-scsi hdd=ide-scsi"

And from ... doc/cdrtools-cdrecord-1.10/README.linux:
   -       Linux driver design oddities ******************************************
        Although cdrecord supports to use dev=/dev/sgc, it is not recommended
        and it is unsupported.

        The /dev/sg* device mapping in Linux is not stable! Using dev=/dev/sgc
        in a shell script may fail after a reboot because the device you want
        to talk to has moved to /dev/sgd. For the proper and OS independent
        dev=<bus>,<tgt>,<lun> syntax read the man page of cdrecord.

Hope that helps, LCR

On Sat, 26 Oct 2002, Martin McCormick wrote:

> "Willem van der Walt<vdwaltw@health.gov.za>" writes:
> >What does some thing like 

> >produce? Does it open the drive or complain about the device?
> 
> 	Actually, neither.  It complains about the eject command.
> 
> 	/dev/scd0 is known by the system and works fine at least
> when I am mounting a CDROM for reading.
> 
> 	Before using the SCSI emulation, this device was
> /dev/cdrom so that behavior is exactly as it should be.
> 
> 	This is the darndest problem I have come across yet.  If
> I type
> 
> mount /dev/scd0 /mnt
> 
> I can read the disk as if it was a SCSI device.  I don't know
> what else to try.
> 
> 	By the way, my utmost thanks to everybody who has had a
> suggestion.  I think I have either done something very odd in the
> setup or kernel building process or we have a bug of some kind.
> This just doesn't add up.

-- 
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid

People buy MicroShaft for compatibility, but get incompatibility and
instability instead.  This is award winning "innovation".  Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html

Re: Sony cd writer problem (Martin)

[Martin McCormick]

	I have great but inbarrassing news.  It looks as though I
accidentally turned off /dev/sg support when building the kernel.
 I may have edited the Kermit script I used to cary on the dialog
that builds the kernel and then thrown away the edit.  Anyway, I
was building kernels with no generic SCSI support module.

	It started working perfectly as soon as I put the generic
support back in.  Now we know what terrible things happen when
one  has no generic support.  It basically tries to work, but
there is still nodriver that cdrecord can use.

	I thank all of you for your help.

"L. C. Robinson" writes:
>A few hints:
>On our systems here, we have:
>ls -l /dev/cdrom                 
>lrwxrwxrwx   1 root     root            8 Feb 28  2001 /dev/cdrom -> /dev/sr0
>for our CD-RWs

Re: Sony cd writer problem (Martin)

[Willem van der Walt<vdwaltw@health.gov.za>]

Hi,
If cdrecord -scanbus does not show one the scsi devices, but the message
to run cdrecord -scanbus, in my experience, it does not pick up the 
cdwriter.
I had this under kernel 2.2 and the reasons was one of the following:
The ide cdrom driver loded and grabed the cdwriter as an ide device and
saw it as a cdrom.  
To prevent this from happening one puts a statment in lilo.conf like:
append="hdc=ide-scsi" after the root=/dev/hd5 or what ever.
If that allone did not work i used to do:
modprobe ide-scsi before i ran cdrecord -scanbus.
hth Willem

On Mon, 21 Oct 2002, Martin McCormick wrote:

> 	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
> >
> 
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
> 

-- 
Willem van der Walt
Information Services Directorate
Department of Health
South Africa
tel: 27 12 3120700

Re: Sony cd writer problem (Martin)

[Martin McCormick]

[-- 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
>

Sony cd writer problem (Martin)

[Willem van der Walt<vdwaltw@health.gov.za>]

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