Fog_Watch wrote:
> On Wed, 27 May 2009 22:26:34 +1000
> Fog_Watch wrote:
>
> >
> > cdrecord: No such device or address. Cannot send SCSI cmd via
> > ioctl. cdrecord: No such device or address. prevent/allow medium
> > removal: scsi sendcmd: fatal error CDB: 1E 00 00 00 00 00
> > cmd finished a
On Wed, 27 May 2009 22:26:34 +1000
Fog_Watch wrote:
>
> cdrecord: No such device or address. Cannot send SCSI cmd via
> ioctl. cdrecord: No such device or address. prevent/allow medium
> removal: scsi sendcmd: fatal error CDB: 1E 00 00 00 00 00
> cmd finished after 0.000s timeout 200s
>
> The
Joerg Schilling wrote:
Rob Bogus wrote:
Unsupported, undocumented, self-written, run as root... for problems any
method which provides useful information is appropriate. This is not
I am sorry to see that you seem to be interested to further increase the
confusion.
Let me try to
Rob Bogus wrote:
> Unsupported, undocumented, self-written, run as root... for problems any
> method which provides useful information is appropriate. This is not
I am sorry to see that you seem to be interested to further increase the
confusion.
Let me try to help to reduce confusion.
Thom
Joerg Schilling wrote:
"Thomas Schmitt" wrote:
cdrecord -scanbus
Full record.
Something like this ?
scsibus0:
0,0,0 0) 'TSSTcorp' 'CDDVDW SH-S203B ' 'SB00' Removable CD-ROM
0,1,0 1) *
..
(This is a SATA attached drive. It appears
as SC
Joerg Schilling wrote:
"Thomas Schmitt" wrote:
Hi,
Fog_Watch:
cdrecord using ide-scsi returns an error that I don't understand.
...
cdrecord: No such device or address. Cannot send SCSI cmd via ioctl.
Joerg Schilling:
This is a Linux kernel problem, please ask the rel
"Thomas Schmitt" wrote:
> for me as bystander and programmer of burn
> software this is an interesting drama to watch.
>
> It might well be a futile effort, though.
> Especially since i do not know how crucial
> remote drive addressing is to you resp.
> whether remote burn program execution is
>
"Thomas Schmitt" wrote:
>
> > > > You could try cdrskin instead of cdrecord.
> > > > Same arguments as with cdrecord (but no rscsi).
> > cdrskin does not implement rscsi.
>
> With its ability to write to any open file
> descriptor (dev=stdio:/dev/fd/) it
> should be a matter of few hours to s
Hi,
> > /sys/bus/scsi/devices/1:0:0:0/scsi_generic:sg0
> Why do you check this? It is completely unimportant for the
> functionality of cdrtools.
Once it worked, now it does not work.
Questions: what changed, what is unusual now ?
> > > You could try cdrskin instead of cdrecord.
> > > Same argu
Hi,
for me as bystander and programmer of burn
software this is an interesting drama to watch.
It might well be a futile effort, though.
Especially since i do not know how crucial
remote drive addressing is to you resp.
whether remote burn program execution is
an alternative for you.
Whatever:
Fog_Watch wrote:
> On Sat, 30 May 2009 11:50:13 +0200
> "Thomas Schmitt" wrote:
> > Did you already disable ide-scsi and try
> >dev=REMOTE:u...@host:ATA:0,1,0
> >dev=REMOTE:u...@host:/dev/hdb
> > Maybe it works ...
> $ cdrecord dev=REMOTE:rs...@hostname:0,1,0 -scanbus
> Cdrecord-ProDVD-P
Ian wrote:
> On Fri, 29 May 2009 08:40:24 +0200
> "Thomas Schmitt" wrote:
>
> > ls -d /sys/bus/scsi/devices/0:0:0:0/*:*
> > (it should tell the various addresses of
> > the burner: sg?, sr0, 0:0:0:0 )
> # ls -d /sys/bus/scsi/devices/1\:0\:0\:0/*:*
> /sys/bus/scsi/devices/1:0:0:
On Sat, 30 May 2009 11:50:13 +0200
"Thomas Schmitt" wrote:
> Did you already disable ide-scsi and try
>dev=REMOTE:u...@host:ATA:0,1,0
>dev=REMOTE:u...@host:/dev/hdb
> Maybe it works ...
$ cdrecord dev=REMOTE:rs...@hostname:0,1,0 -scanbus
Cdrecord-ProDVD-ProBD-Clone 2.01.01a51 (i686-pc-linu
Hi,
> ... > # cdrecord dev=0,0,0 -dao -data dsl-1.1.iso
> # ls -d /sys/bus/scsi/devices/1\:0\:0\:0/*:*
> /sys/bus/scsi/devices/1:0:0:0/block:sr0
> /sys/bus/scsi/devices/1:0:0:0/scsi_device:1:0:0:0
> /sys/bus/scsi/devices/1:0:0:0/scsi_generic:sg0
Strange. On my system the first com
On Fri, 29 May 2009 08:40:24 +0200
"Thomas Schmitt" wrote:
> ls -d /sys/bus/scsi/devices/0:0:0:0/*:*
> (it should tell the various addresses of
> the burner: sg?, sr0, 0:0:0:0 )
# ls -d /sys/bus/scsi/devices/1\:0\:0\:0/*:*
/sys/bus/scsi/devices/1:0:0:0/block:sr0
/sys/bus/scsi/de
Fog_Watch wrote:
> On Thu, 28 May 2009 10:26:13 -0700
> Dave Platt wrote:
>
> > Possibly the user's kernel was configured without the
> > "legacy /proc/scsi support" feature being enabled?
> Correct. However, when "legacy /proc/scsi support" is enabled in a
> fresh kernel the performance and re
Hi,
> However, when "legacy /proc/scsi support" is enabled in a
> fresh kernel the performance and returned error remains the same.
That /proc/scsi stuff is for diagnostics. So no
remedy was to be expected. But what do you get now
from this ?
cat /proc/scsi/scsi
And from this ?
ls -d /sys/bu
On Thu, 28 May 2009 10:26:13 -0700
Dave Platt wrote:
> Possibly the user's kernel was configured without the
> "legacy /proc/scsi support" feature being enabled?
Correct. However, when "legacy /proc/scsi support" is enabled in a
fresh kernel the performance and returned error remains the same.
"Thomas Schmitt" wrote:
> Hi,
>
> Fog_Watch:
> > > cdrecord using ide-scsi returns an error that I don't understand.
> > > ...
> > > cdrecord: No such device or address. Cannot send SCSI cmd via ioctl.
>
> Joerg Schilling:
> > This is a Linux kernel problem, please ask the related people.
>
> > >
Ahum ... lots of files ...
"lots", "plethora", "overabundance"... yeah.
$ ls /sys/bus/scsi/devices
0:0:0:0 2:0:0:0 21:0:0:0 28:0:0:0 85:0:0:0
$ cat /sys/bus/scsi/devices/28:0:0:0/model
BD-RE GGW-H20L
$ ls -d /sys/bus/scsi/devices/28:0:0:0/scsi_generic*
/sys/bus/scsi/devic
Hi,
Dave Platt wrote:
> Possibly the user's kernel was configured without the
> "legacy /proc/scsi support" feature being enabled?
>
> The help data says "In Linux 2.6 this has been superseded by
> files in sysfs but many legacy applications rely on this."
Being such a legacy entity myself i will
If it does not work this way, there is a bug in the kernel code.
Something appears wrong, indeed.
The /proc tree seems truncated.
Possibly the user's kernel was configured without the
"legacy /proc/scsi support" feature being enabled?
The help data says "In Linux 2.6 this has been superse
On Thu, May 28, 2009 at 11:49:13AM +0200, Thomas Schmitt wrote:
> Something appears wrong, indeed.
> The /proc tree seems truncated.
My guess is he built his own custom kernel and left out a lot of
drivers that he needs.
--
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subjec
"Thomas Schmitt" wrote:
> > > Then try
> > > cdrecord dev=/dev/sr0 -dao ...
> > > [...]
> > > This is deprecated too. But maybe it works.
>
> Joerg Schilling:
> > Is there any reson to recommend _unsupported_ command line usage?
>
> For a test: yes.
Sorry but it does not help at all if you giv
Hi,
me:
> > Then try
> > cdrecord dev=/dev/sr0 -dao ...
> > [...]
> > This is deprecated too. But maybe it works.
Joerg Schilling:
> Is there any reson to recommend _unsupported_ command line usage?
For a test: yes.
After all, eject was able to send a
LOAD/UNLOAD MEDIUM command to the drive.
I
"Thomas Schmitt" wrote:
> > > cdrecord -scanbus
> > Full record.
>
> Something like this ?
>
> scsibus0:
> 0,0,0 0) 'TSSTcorp' 'CDDVDW SH-S203B ' 'SB00' Removable CD-ROM
> 0,1,0 1) *
> ..
>
> (This is a SATA attached drive. It appears
> as SCSI without ide-scsi
Hi,
> > cdrecord -scanbus
> Full record.
Something like this ?
scsibus0:
0,0,0 0) 'TSSTcorp' 'CDDVDW SH-S203B ' 'SB00' Removable CD-ROM
0,1,0 1) *
..
(This is a SATA attached drive. It appears
as SCSI without ide-scsi emulation.)
> > eject /dev/sr0
> Yes.
On Wed, 27 May 2009 16:43:44 +0200
"Thomas Schmitt" wrote:
snip
> Well, ide-scsi is said to be deprecated with
> kernel 2.6.
> One should at least find out a bit more
> before exposing oneself at LKML.
Sound ominous, but it looks like that is where I am heading.
>
> What do you get from this com
Hi,
Fog_Watch:
> > cdrecord using ide-scsi returns an error that I don't understand.
> > ...
> > cdrecord: No such device or address. Cannot send SCSI cmd via ioctl.
Joerg Schilling:
> This is a Linux kernel problem, please ask the related people.
> > 2.6.24-gentoo-r8
Well, ide-scsi is said to
Fog_Watch wrote:
> cdrecord using ide-scsi returns an error that I don't understand. The
> burner can be used with dev=ATA:0,1,0, so I can't see how it is a device
> problem.
>
> I am using ide-scsi for rscsi compatibility and remote burning.
>
> The error follows:
> # cdrecord dev=0,0,0 -dao
cdrecord using ide-scsi returns an error that I don't understand. The
burner can be used with dev=ATA:0,1,0, so I can't see how it is a device
problem.
I am using ide-scsi for rscsi compatibility and remote burning.
The error follows:
# cdrecord dev=0,0,0 -dao -data dsl-1.1.iso
Cdrecord-ProDV
31 matches
Mail list logo
