Re: ide-scsi - write_g1: scsi sendcmd: fatal error

2009-05-28 Thread Thomas Schmitt
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.

Re: ide-scsi - write_g1: scsi sendcmd: fatal error

2009-05-28 Thread Joerg Schilling
Thomas Schmitt scdbac...@gmx.net 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

Re: ide-scsi - write_g1: scsi sendcmd: fatal error

2009-05-28 Thread Thomas Schmitt
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. If the

Re: ide-scsi - write_g1: scsi sendcmd: fatal error

2009-05-28 Thread Joerg Schilling
Thomas Schmitt scdbac...@gmx.net 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 give

Re: ide-scsi - write_g1: scsi sendcmd: fatal error

2009-05-28 Thread Greg Wooledge
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 subject

Re: ide-scsi - write_g1: scsi sendcmd: fatal error

2009-05-28 Thread Dave Platt
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

Re: ide-scsi - write_g1: scsi sendcmd: fatal error

2009-05-28 Thread Thomas Schmitt
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 now

Re: ide-scsi - write_g1: scsi sendcmd: fatal error

2009-05-28 Thread Dave Platt
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*

Re: ide-scsi - write_g1: scsi sendcmd: fatal error

2009-05-28 Thread Joerg Schilling
Thomas Schmitt scdbac...@gmx.net 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.

Re: ide-scsi - write_g1: scsi sendcmd: fatal error

2009-05-28 Thread Fog_Watch
On Thu, 28 May 2009 10:26:13 -0700 Dave Platt dpl...@radagast.org 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