Re: Need help
Joerg Schilling wrote: Bill Davidsen [EMAIL PROTECTED] wrote: cdrecord works without real problems on Linux-2.6 if you install it correctly suid root. Unfortunately run everything as root is not going to happen on many systems, some years ago capabilities were added to Linux, and those are the proper way to do access rather than bypassing all security checks. Also, the last time I looked the notes you provided only worked if security was disabled, selinux won't let you do what you were suggesting. Looks like you are uninformed :-( I know about capabilities. Currently there is no more than something in pre-alpha state that could later become a fine grained security modell (once there is support in userland). You are confused. NSA selinux and capabilities are two totally different things. Capabilities have been in Linux since somewhere in 2.2, and are hardly pre-alpha. Check out man privileges on Solaris for more information on what makes a ready to use system in this area. I'm discussing the shortcomings of cdrecord under Linux. Once Linux implements a user ready version of the current experimental interface, it would make sense to let cdrtools use this interface. The capability library has been around for years. Some old versions do not but this is caused by non-cooperative acting from the Linux Kernel maintainers: they did introduce a severe incompatible interface change after cdrtools had been put into a code freeze state for releasing. Caused by fixing a serious security issue... Once the first exploit was out it did have to be done quickly, and it did impact applications (not just yours). It came at a bad time in your code cycle, but making it sound as if the change was made just because they felt like it is simply not true. Allowing any SCSI command to go to devices was a hole allowing the bad guys to wipe out firmware on hard drives as well as burners, and had to be stopped immediately. You are again uninformed: The security issue was: sending of SCSI commands was possible on file descriptors opened with O_RDONLY. The correct fix for this security bug was to require O_RDWR instead of O_RDONLY. That is like saying that I have to open a file for read and write just to read it. Most people don't think allowing general write permission of raw devices is a correct fix. The correct fix was to allow a program to write SCSI commands (such as seek and read) with O_READ, but not to let other commands through. And it did take some time to get the list of allowed commands correct for the general case. And there are cases where odd vendor commands are blocked to non-root. Agreed it's not perfect, but it does keep people from reconfiguring the firmware when given read access. This did not harm interfaces but cure the problem. The problem was that Mr. Torvalds did introduce an incompatible interface change instead although many people on LKML did send their protest mails. Given a choice of more security or more convenience, I choose security. I don't insult people who make other choices, their priorities may be different from mine. The choice was made to default to restricted, and allow several methods to change that choice. -- bill davidsen [EMAIL PROTECTED] CTO TMR Associates, Inc Doing interesting things with small computers since 1979 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help
On Wed, Jan 10, 2007 at 01:41:21PM -0800, Shim, JaiX K wrote: I tried cdrecord -scanbus. But I got the following error message. cdrecord: No such file or directory. Cannot open SCSI driver. Sounds like you run Linux 2.6. If you want any help, you're going to have to tell us a lot more detail -- which version of cdrecord, which operating system, etc. (Although if your platform is Linux 2.6, all the help you'll get is don't try to run cdrecord -scanbus on Linux 2.6, or possibly we've attempted a workaround for Linux 2.6 in cdrecord version xx.yy.zz, and you can try that.) Also, your Subject: line is abysmal. Some people filter which messages they'll read based on that, and yours screams unhelpable or spammer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help
Greg Wooledge [EMAIL PROTECTED] wrote: On Wed, Jan 10, 2007 at 01:41:21PM -0800, Shim, JaiX K wrote: I tried cdrecord -scanbus. But I got the following error message. cdrecord: No such file or directory. Cannot open SCSI driver. Sounds like you run Linux 2.6. If you want any help, you're going to have to tell us a lot more detail -- which version of cdrecord, which operating system, etc. (Although if your platform is Linux 2.6, all the help you'll get is don't try to run cdrecord -scanbus on Linux 2.6, or possibly we've attempted a workaround for Linux 2.6 in cdrecord version xx.yy.zz, and you can try that.) This is wrong! cdrecord works without real problems on Linux-2.6 if you install it correctly suid root. ftp://ftp.berlios.de/pub/cdrecord/alpha/ http://cdrecord.berlios.de/old/private/problems.html Some old versions do not but this is caused by non-cooperative acting from the Linux Kernel maintainers: they did introduce a severe incompatible interface change after cdrtools had been put into a code freeze state for releasing. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help
Bill Davidsen [EMAIL PROTECTED] wrote: cdrecord works without real problems on Linux-2.6 if you install it correctly suid root. Unfortunately run everything as root is not going to happen on many systems, some years ago capabilities were added to Linux, and those are the proper way to do access rather than bypassing all security checks. Also, the last time I looked the notes you provided only worked if security was disabled, selinux won't let you do what you were suggesting. Looks like you are uninformed :-( Currently there is no more than something in pre-alpha state that could later become a fine grained security modell (once there is support in userland). Check out man privileges on Solaris for more information on what makes a ready to use system in this area. On Solaris, cdrecord really runs without root privileges. On Solaris, /usr/bin/cdrecord is a shell script with the following content: #!/bin/sh pfexec `dirname $0`/`basename $0`.bin $@ The file /etc/security/exec_attr contains the following entries for cdrtools: Basic Solaris User:solaris:cmd:::/usr/bin/cdrecord.bin:privs=file_dac_read,sys_devices,proc_lock_memory,proc_priocntl,net_privaddr Basic Solaris User:solaris:cmd:::/usr/bin/cdda2wav.bin:privs=file_dac_read,sys_devices,proc_priocntl,net_privadd Basic Solaris User:solaris:cmd:::/usr/bin/readcd.bin:privs=file_dac_read,sys_devices,net_privaddr Once Linux implements a user ready version of the current experimental interface, it would make sense to let cdrtools use this interface. Some old versions do not but this is caused by non-cooperative acting from the Linux Kernel maintainers: they did introduce a severe incompatible interface change after cdrtools had been put into a code freeze state for releasing. Caused by fixing a serious security issue... Once the first exploit was out it did have to be done quickly, and it did impact applications (not just yours). It came at a bad time in your code cycle, but making it sound as if the change was made just because they felt like it is simply not true. Allowing any SCSI command to go to devices was a hole allowing the bad guys to wipe out firmware on hard drives as well as burners, and had to be stopped immediately. You are again uninformed: The security issue was: sending of SCSI commands was possible on file descriptors opened with O_RDONLY. The correct fix for this security bug was to require O_RDWR instead of O_RDONLY. This did not harm interfaces but cure the problem. The problem was that Mr. Torvalds did introduce an incompatible interface change instead although many people on LKML did send their protest mails. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help
On Don, 11 Jan 2007, Joerg Schilling wrote: Mr. Torvalds did introduce an incompatible interface change instead although many people on LKML did send their protest mails. Not again ... Mr. Schilling, we know all this already. You don't have to iterate everything billion times, nobody is anyway believing you in this. Norbert --- Dr. Norbert Preining [EMAIL PROTECTED]Università di Siena Debian Developer [EMAIL PROTECTED] Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- CHICAGO (n.) The foul-smelling wind which precedes an underground railway train. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help
Joerg Schilling wrote: Greg Wooledge [EMAIL PROTECTED] wrote: On Wed, Jan 10, 2007 at 01:41:21PM -0800, Shim, JaiX K wrote: I tried cdrecord -scanbus. But I got the following error message. cdrecord: No such file or directory. Cannot open SCSI driver. Sounds like you run Linux 2.6. If you want any help, you're going to have to tell us a lot more detail -- which version of cdrecord, which operating system, etc. (Although if your platform is Linux 2.6, all the help you'll get is don't try to run cdrecord -scanbus on Linux 2.6, or possibly we've attempted a workaround for Linux 2.6 in cdrecord version xx.yy.zz, and you can try that.) This is wrong! cdrecord works without real problems on Linux-2.6 if you install it correctly suid root. Unfortunately run everything as root is not going to happen on many systems, some years ago capabilities were added to Linux, and those are the proper way to do access rather than bypassing all security checks. Also, the last time I looked the notes you provided only worked if security was disabled, selinux won't let you do what you were suggesting. That was some time ago, I did put get current docs on my todo list, probably won't happen until tomorrow. ftp://ftp.berlios.de/pub/cdrecord/alpha/ http://cdrecord.berlios.de/old/private/problems.html Some old versions do not but this is caused by non-cooperative acting from the Linux Kernel maintainers: they did introduce a severe incompatible interface change after cdrtools had been put into a code freeze state for releasing. Caused by fixing a serious security issue... Once the first exploit was out it did have to be done quickly, and it did impact applications (not just yours). It came at a bad time in your code cycle, but making it sound as if the change was made just because they felt like it is simply not true. Allowing any SCSI command to go to devices was a hole allowing the bad guys to wipe out firmware on hard drives as well as burners, and had to be stopped immediately. -- bill davidsen [EMAIL PROTECTED] CTO TMR Associates, Inc Doing interesting things with small computers since 1979
Re: Need help
On Thu, Jan 11, 2007 at 02:57:15PM +0100, Joerg Schilling wrote: cdrecord works without real problems on Linux-2.6 if you install it correctly suid root. ftp://ftp.berlios.de/pub/cdrecord/alpha/ http://cdrecord.berlios.de/old/private/problems.html I looked at the HTTP link above. It does not contain any of the words setuid, suid or root. It doesn't even contain the word install, except as part of installation, and that's only in the paragraph that says ATAPI is supported. So I don't really see why you gave us that URL. Some old versions do not [...] Where old means anything not in my alpha/ subdirectory? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help
Hi, I tried cdrecord -scanbus. But I got the following error message. cdrecord: No such file or directory. Cannot open SCSI driver. Can you help me please? Looks like you stirred up other much older quarrels. These quarrels are the reason why we got some wealth of cdrecord compatible programs. Better too many than too few. The original: You might expect help from Joerg Schilling, the author of cdrecord, if you use his newest release, from ftp://ftp.berlios.de/pub/cdrecord/alpha To my knowledge current is: ftp://ftp.berlios.de/pub/cdrecord/alpha/cdrtools-2.01.01a23.tar.gz (For some reason this address does not work for me currently. traceroute ends at funnel.fokus.fraunhofer.de ) Proper problem reports are indeed on topic here cdwrite@other.debian.org but see below for some hints. Project cdrkit: cdrkit contains program wodim which stems from cdrecord and is therefore very very compatible. http://cdrkit.org Current seems to be http://cdrkit.org/releases/cdrkit-1.1.1.tar.gz I guess problem reports can be submitted to [EMAIL PROTECTED] My own effort: cdrskin is the cdrecord compatibility wrapper of libburn http://scdbackup.sourceforge.net/cdrskin_eng.html current is (i'm sure) http://scdbackup.sourceforge.net/cdrskin-0.2.6.pl02.tar.gz Bug reports and requests can be mailed to [EMAIL PROTECTED] or submitted at http://libburnia.pykix.org/newticket If you picked the recent release of one of above projects and then still have the problem: please give some info wether you were superuser and on what operating system ... If it is Linux, one reason might be the lack of sg devices. So the output of this could be interesting: ls -l /dev/sg[0-9]* lsmod | grep sg Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help
[EMAIL PROTECTED] wrote: The original: You might expect help from Joerg Schilling, the author of cdrecord, if you use his newest release, from ftp://ftp.berlios.de/pub/cdrecord/alpha To my knowledge current is: ftp://ftp.berlios.de/pub/cdrecord/alpha/cdrtools-2.01.01a23.tar.gz (For some reason this address does not work for me currently. traceroute ends at funnel.fokus.fraunhofer.de ) It did work 3 hours ago... and I did just send a bug report to our sysadmin for the network. Project cdrkit: cdrkit contains program wodim which stems from cdrecord and is therefore very very compatible. I cannot recommend it as it is not very compatible, In fact, it is incompatible by intention and it is mainly a frozen version of a one year old cdrtools. During the last year, I did e.g. fix several dozen old bugs in mkisofs that are still present in this packet. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Need help
Hello, I tried cdrecord -scanbus. But I got the following error message. cdrecord: No such file or directory. Cannot open SCSI driver. Can you help me please? Jay Shim
Need Help To Numb the Pain?
Screw Name Brand= Go Generic http://www.myyv.com/p/coupon/ferimus Renounce your announcements myyv.coms.php Two roads diverged in a wood, and II took the one less travelled by.
Re: Need help splitting a directory
At 10:06 PM +0530 10/20/04, _N4R3N_ wrote: hi I want to split a directory in to two sub directories If my home dir is 1000 Mb I can't write it completely on one cd So i want to split it in to two directories namely 1)naren.bak.1 2)naren.bak.2 so that my /home/naren directory will be split in to two temporary directories .. so that i can write the images of thus formed using mkisofs on two cdroms Is mkisofs incapable of writing ISO-9660 volume sets ? Volume sets can be comprised of up to 32767 volumes, probably more than enough for your largest directory :-) -- Larry Kilgallen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help splitting a directory
On 20 Oct, _N4R3N_ wrote: hi I want to split a directory in to two sub directories If my home dir is 1000 Mb I can't write it completely on one cd So i want to split it in to two directories namely 1)naren.bak.1 2)naren.bak.2 No need to do that! Have a look at http://www.serice.net/shunt -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help splitting a directory
_N4R3N_ wrote: hi I want to split a directory in to two sub directories If my home dir is 1000 Mb I can't write it completely on one cd So i want to split it in to two directories namely 1)naren.bak.1 2)naren.bak.2 so that my /home/naren directory will be split in to two temporary directories .. so that i can write the images of thus formed using mkisofs on two cdroms and afterwards i also need help how do i combine them again. so that after copying two backup directories from the cdrom naren.bak.1 and naren.bak.2 in to /tmp directory I want to combine this two to make it again one directory say naren How do i do this I won't say this is the best thing to do, but the simple solution is links. Create as many subdirectories as you need, filled with links to the appropriate files, then back up each to a CD. I have some tools which help with this, but until I find time to get my ftp server back up I have no easy way to release them. I use that as motivation to get to rebuilding the server ;-) -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help splitting a directory
_N4R3N_ [EMAIL PROTECTED] wrote: I want to split a directory in to two sub directories If my home dir is 1000 Mb I can't write it completely on one cd So try a 80 minute blank and use the following command: cdrecord dev=b,t,l -v -sao driveropts=gigarec=1.4 out.iso on a Plextor Premium writer :-) Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Need help splitting a directory
hi I want to split a directory in to two sub directories If my home dir is 1000 Mb I can't write it completely on one cd So i want to split it in to two directories namely 1)naren.bak.1 2)naren.bak.2 so that my /home/naren directory will be split in to two temporary directories .. so that i can write the images of thus formed using mkisofs on two cdroms and afterwards i also need help how do i combine them again. so that after copying two backup directories from the cdrom naren.bak.1 and naren.bak.2 in to /tmp directory I want to combine this two to make it again one directory say naren How do i do this any ideas Thanks for reading... -- I would have changed the world but god never gave me the source code -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Need help with pxupgrade on MacOS X
I am looking for a person who own a Plextor CD/DVD writer installed in a MacOS X machine. To fix the problem (caused by Apples unability to define a clean and decent SCSI generic transport interface), I would first need the output from something like: pxupgrade dev=IOCompactDiscServices -l or pxupgrade dev=IODVDServices -l I am interested in the output line that looks like: PLEXTOR DVDR PX-708A V1b04 (HA:0 ID:0) See ftp://ftp.berlios.de/pub/cdrecord/firmware/plextor/ Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) If you don't have iso-8859-1 [EMAIL PROTECTED](work) chars I am Jorg Schilling URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Re: Need help with Sony DW-U10A
Hi! I've just purchased my first dvd-writer and it works as well as it is possible! All of you write about the problems! What kind of problem are you writing about??? Just normally make the contact between dvd-writer and your PC (IDE cable, for example secondary master), and Windows XP realizes this hardware, no need any installation! Just use : NERO 6!!! This software recorded my first dwd-rw disc completely!There were no problems! Have a lot of fun! Laci from Hungary (If you have any suggestion, just mail me! [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help with Sony DW-U10A
Hi! I've just purchased my first dvd-writer and it works as well as it is possible! All of you write about the problems! What kind of problem are you writing about??? Just normally make the contact between dvd-writer and your PC (IDE cable, for example secondary master), and Windows XP realizes this hardware, no need any installation! Just use : NERO 6!!! This software recorded my first dwd-rw disc completely!There were no problems! Have a lot of fun! Laci from Hungary (If you have any suggestion, just mail me! [EMAIL PROTECTED])
Re: Need help with Sony DW-U10A
Memorex DVD-R with a 900MB ISO9660 image using growisofs. It did not have any problems at all and the disc is mountable and readable just fine. Two other times, growisofs has begun the burning, made it to about 30%, and then quit with what appeared to be the same type of sense error that cdrecord/ dvdrecord had. Three options: - Media poorly supported by unit firmware. Reportedly Sony is not as picky as NEC, but it's also known for not being able to record some brands. Poor media support can manifest itself in most bizarre way. Try another brand, update firmware, etc; - Recorder hadware defect. The fact that you can record CD does not exclude the possibility that circuitry engaged during DVD recording is rotten. Talk to your vendor; - Bad media batch. Unlike as you apparently tried for example DVD+RW; :-[ LBA=0h, SENSE KEY=5h/ASC=30h/ASCQ=10h ] :-[ media is not formatted or unsupported ] ^^^ It means every word of it. These same errors happen whether or not I'm using ide-scsi to access the drive. I will point out that the one time growisofs successfully burned, I was NOT using ide-scsi. But I do not know if this is relevant to the problem. It's hardly relevant. It's between your unit and media. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help with Sony DW-U10A
Memorex DVD-R with a 900MB ISO9660 image using growisofs. It did not have any problems at all and the disc is mountable and readable just fine. Two other times, growisofs has begun the burning, made it to about 30%, and then quit with what appeared to be the same type of sense error that cdrecord/ dvdrecord had. Three options: - Media poorly supported by unit firmware. Reportedly Sony is not as picky as NEC, but it's also known for not being able to record some brands. Poor media support can manifest itself in most bizarre way. Try another brand, update firmware, etc; - Recorder hadware defect. The fact that you can record CD does not exclude the possibility that circuitry engaged during DVD recording is rotten. Talk to your vendor; - Bad media batch. Unlike as you apparently tried for example DVD+RW; :-[ LBA=0h, SENSE KEY=5h/ASC=30h/ASCQ=10h ] :-[ media is not formatted or unsupported ] ^^^ It means every word of it. These same errors happen whether or not I'm using ide-scsi to access the drive. I will point out that the one time growisofs successfully burned, I was NOT using ide-scsi. But I do not know if this is relevant to the problem. It's hardly relevant. It's between your unit and media. A.
Need help with Sony DW-U10A
I have a Sony DW-U10A model DVD +/- R/RW drive, which IIRC is simply the OEM version of the Sony DRU-500A. Even if not, I have read reports that both the DRU-500A and the DW-U10A should work in Linux. I have firmware revision 1.1d. I am running Linux 2.4.19-xfs on an AMD Athlon CPU and I have 512MB of RAM. There are 2 IDE hard drives on the first bus and the DVDRW is the only device on the secondary bus. I have 32bit mode and DMA both enabled for this drive. At first I tried using cdrecord-ProDVD, but it failed with the CHECK STATUS message. It failed with Sony brand DVD-Rs, and Memorex DVD-Rs and Memorex DVD+RWs. However it was able to write a few MB to the DVD-Rs (both brands) before exiting with this error: cdrecord-prodvd: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 00 00 00 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 30 10 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x30 Qual 0x10 (medium not formatted) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.005s timeout 100s write track data: error after 0 bytes cdrecord-prodvd: A write error occured. cdrecord-prodvd: Please properly read the error message above. cdrecord-prodvd: Input/output error. close track/session: scsi sendcmd: no error CDB: 5B 01 02 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) and leaving me with ruined discs. This happened no matter what type of file I tried to burn, ISO9660 image or anything else. I tried several different times using both DAO and RAW. Only about 3 times did it even begin writing to the disc and then top. Every other time it gave me that error before it could even start (and left the disc untouched and still usable for later). I have decided now that I do not wish to use cdrecord-ProDVD because of the licensing issue. Sorry Jorg, please do not reply to this and tell me that all my problems would go away if I used ProDVD and that my firmware/hardware/ kernel is garbage. I have already made up my mind. I then tried using the hacked up dvdrecord fork in the dvdrtools package. It had exactly the same problems as cdrecord-ProDVD. I also tried simply using the patched-cdrecord that reportedly works with the DW-U10A. It had the same problems. It would detect the media, but give me a sense error before it could write, and if it did write, it would certainly not get very far before quitting. I should mention I have tried all of the above using ide-scsi (for cdrecord-hacked, dvdrecord, and cdrecord-ProDVD) and then using just regular ATAPI (dev=ATAPI:0,0,0) on the ProDVD. This did not appear to change any results. I have had the most success with growisofs. I have successfully written 1 Memorex DVD-R with a 900MB ISO9660 image using growisofs. It did not have any problems at all and the disc is mountable and readable just fine. Two other times, growisofs has begun the burning, made it to about 30%, and then quit with what appeared to be the same type of sense error that cdrecord/ dvdrecord had. The two partial-but-unsuccessful burns were with a 900MB image, the other time the image was about 2.1GB. Those are the only three times growisofs has even begun to record. Every other time, it won't even start and complains about a sense error. As for DVD+RWs, growisofs has not yet successfully done a preformat. dvd +rw-format has not either. growisofs begins, and goes for a few minutes before stopping with this error: :-[ LBA=0h, SENSE KEY=5h/ASC=30h/ASCQ=10h ] :-[ media is not formatted or unsupported ] :-( write failed: Invalid argument Using dvd+rw-format with this same type of disc, I get: * formatting |- [unable to CLOSE SESSION (5h/30h/10h)]: Invalid argument These same errors happen whether or not I'm using ide-scsi to access the drive. I will point out that the one time growisofs successfully burned, I was NOT using ide-scsi. But I do not know if this is relevant to the problem. This drive has no problems reading any of the good media I already have data recorded to, and it has no problems while using cdrecord for burning CDRs and CDRWs or blanking CDRWs. I have searched around and cannot find any other help, so I turn to you nice people and ask what do I do to make this drive reliably burn DVDs? I would like if at all possible to use the dvd+rw-tools package and growisofs. Any other information ask me and I will provide. Every time I've tried to burn, I have been root and stopped as many other processes as possible to let the CPU focus on the burning. For reasons of other patches, updating the kernel is not an option as this time. From what I read around here, this doesn't help many people anyway. Greg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Need help with Sony DW-U10A
I have a Sony DW-U10A model DVD +/- R/RW drive, which IIRC is simply the OEM version of the Sony DRU-500A. Even if not, I have read reports that both the DRU-500A and the DW-U10A should work in Linux. I have firmware revision 1.1d. I am running Linux 2.4.19-xfs on an AMD Athlon CPU and I have 512MB of RAM. There are 2 IDE hard drives on the first bus and the DVDRW is the only device on the secondary bus. I have 32bit mode and DMA both enabled for this drive. At first I tried using cdrecord-ProDVD, but it failed with the CHECK STATUS message. It failed with Sony brand DVD-Rs, and Memorex DVD-Rs and Memorex DVD+RWs. However it was able to write a few MB to the DVD-Rs (both brands) before exiting with this error: cdrecord-prodvd: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 00 00 00 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 30 10 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x30 Qual 0x10 (medium not formatted) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.005s timeout 100s write track data: error after 0 bytes cdrecord-prodvd: A write error occured. cdrecord-prodvd: Please properly read the error message above. cdrecord-prodvd: Input/output error. close track/session: scsi sendcmd: no error CDB: 5B 01 02 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) and leaving me with ruined discs. This happened no matter what type of file I tried to burn, ISO9660 image or anything else. I tried several different times using both DAO and RAW. Only about 3 times did it even begin writing to the disc and then top. Every other time it gave me that error before it could even start (and left the disc untouched and still usable for later). I have decided now that I do not wish to use cdrecord-ProDVD because of the licensing issue. Sorry Jorg, please do not reply to this and tell me that all my problems would go away if I used ProDVD and that my firmware/hardware/ kernel is garbage. I have already made up my mind. I then tried using the hacked up dvdrecord fork in the dvdrtools package. It had exactly the same problems as cdrecord-ProDVD. I also tried simply using the patched-cdrecord that reportedly works with the DW-U10A. It had the same problems. It would detect the media, but give me a sense error before it could write, and if it did write, it would certainly not get very far before quitting. I should mention I have tried all of the above using ide-scsi (for cdrecord-hacked, dvdrecord, and cdrecord-ProDVD) and then using just regular ATAPI (dev=ATAPI:0,0,0) on the ProDVD. This did not appear to change any results. I have had the most success with growisofs. I have successfully written 1 Memorex DVD-R with a 900MB ISO9660 image using growisofs. It did not have any problems at all and the disc is mountable and readable just fine. Two other times, growisofs has begun the burning, made it to about 30%, and then quit with what appeared to be the same type of sense error that cdrecord/ dvdrecord had. The two partial-but-unsuccessful burns were with a 900MB image, the other time the image was about 2.1GB. Those are the only three times growisofs has even begun to record. Every other time, it won't even start and complains about a sense error. As for DVD+RWs, growisofs has not yet successfully done a preformat. dvd +rw-format has not either. growisofs begins, and goes for a few minutes before stopping with this error: :-[ LBA=0h, SENSE KEY=5h/ASC=30h/ASCQ=10h ] :-[ media is not formatted or unsupported ] :-( write failed: Invalid argument Using dvd+rw-format with this same type of disc, I get: * formatting |- [unable to CLOSE SESSION (5h/30h/10h)]: Invalid argument These same errors happen whether or not I'm using ide-scsi to access the drive. I will point out that the one time growisofs successfully burned, I was NOT using ide-scsi. But I do not know if this is relevant to the problem. This drive has no problems reading any of the good media I already have data recorded to, and it has no problems while using cdrecord for burning CDRs and CDRWs or blanking CDRWs. I have searched around and cannot find any other help, so I turn to you nice people and ask what do I do to make this drive reliably burn DVDs? I would like if at all possible to use the dvd+rw-tools package and growisofs. Any other information ask me and I will provide. Every time I've tried to burn, I have been root and stopped as many other processes as possible to let the CPU focus on the burning. For reasons of other patches, updating the kernel is not an option as this time. From what I read around here, this doesn't help many people anyway. Greg
Need help please
K. Matthew Victor wrote: Sorry, let us try this again, somehow I clipped out the files.matt Greetings, I need advise as to what might've become bollixed after a kernel upgrade. Problem: Unable to mount the scsi (real, native, scsi cd burner for reading). Symptoms: mount /dev/sr0 will immediately spool up the cd-r/w after 3-5 minutes of running a message is printed: media not found. Or sometimes: too many files systems mounted, or bad block, or wrong file system type. At this point if one does cdrecord -scanbus the device will have been removed from the bus, invocation of Xcdroast will confirm by stating : something on the scsi bus has changed, please run config. A reboot (hard boot) later and everything is back on the bus and addressable, one may burn cd's but not read them from the native scsi device. The IDE cdrom works fine and is running in scsi emulation. I have mucked about changing /etc/fstab device names and relinking (/dev/scd0 instead of /dev/sr0, etc.) to no difference. Also noted are links in the home dir. that were never there before, deleting these cause no problems but they are returned at each reboot. The mount point /cdrom seems to have been added to at the time of the kernel update also (the mount point dir. /cdrom now has a subdir. //cdrom0 which makes no sense to me) the additional sub directory will always reinstall if removed at subsequent reboots. DAMN annoying, as my Microlite BackupEdge/RecoverEdge software is now an expensive virtual boat anchor. It requires that the cdr/w device be able to read and write. I was thinking the there is something someplace about max_devices sometimes needing to be reset with the 2.4.18 and upward kernels (at least on Debian), and dim memory vaguely recollects some type of scsi wait/time out issues with some cd devices, BUT, I am not sure where or how to proceed. System: Debian 3.0,2.4.19-k6, Attached are some files I hope will be descriptive and helpful. NOTE: these are from a state where the cd burner is recognized and would run through cdrecord or what you will. As a quick after thought, I wonder if perhaps the proper Cdr. device in the 2.4. series for cdrecord, cdparanioa might not be an sg designation? If so how to set/ find proper sg#? I've never understood the hdc: FX3400S, ATAPI CD/DVD-ROM drive thing as it is clearly being controlled through ide_scsi and is fully usable (being mountable as a cdrom which it is, not a cdr/w). any help will be very welcome, I don't have a clue what next to try. tia, matthew Character devices: 1 mem 2 pty/m%d 3 pty/s%d 4 tts/%d 5 cua/%d 6 lp 7 vcs 9 st 10 misc 13 input 14 sound 21 sg 29 fb 108 ppp 116 alsa 128 ptm 136 pts/%d 162 raw 180 usb Block devices: 1 ramdisk 3 ide0 7 loop 11 sr 22 ide1 nodev rootfs nodev bdev nodev proc nodev sockfs nodev tmpfs nodev shm nodev pipefs cramfs nodev ramfs nodev devfs nodev devpts ext3 ext2 iso9660 nodev usbdevfs nodev usbfs nodev autofs -001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0070-007f : rtc 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 0100-0101 : OPL3-SA control 0170-0177 : ide1 01f0-01f7 : ide0 0213-0213 : isapnp read 02f8-02ff : serial(set) 0300-0301 : MPU401 UART 0376-0376 : ide1 0378-037a : parport0 0388-0389 : OPL2/3 (left) 038a-038b : OPL2/3 (right) 03c0-03df : vga+ 03f6-03f6 : ide0 03f8-03ff : serial(set) 0a79-0a79 : isapnp write 0cf8-0cff : PCI conf1 0e84-0e87 : CS4231 c000-cfff : PCI Bus #01 dc00-dcff : Adaptec AHA-2930CU ffa0-ffaf : Acer Laboratories Inc. [ALi] M5229 IDE ffa0-ffa7 : ide0 ffa8-ffaf : ide1 0 dev_max(currently)=9 max_active_device=4 (origin 1) scsi_dma_free_sectors=144 sg_pool_secs_aval=320 def_reserved_size=32768 32768 hostchanid lun typeopens qdepth busyonline HP HP35480A1009 YAMAHA CRW2100S1.0H HP C7670A 3925 MITSUMI CD-ROM FX3400S!Bu01 0 0 0 0 1 0 2 0 1 0 0 4 0 5 0 2 0 1 0 0 6 0 3 0 2 0 1 1 0 0 0 5 0 5 0 1 uid busycpl scatg isa emul Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8 Adaptec 2930CU SCSI adapter aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs SCSI host adapter emulation for IDE
Re: Need help with cdrecord/rscsi
Hi Jörg On Wed, 2002-06-12 at 00:23, Joerg Schilling wrote: [...] o How can I use remote devices without being root on the client machine? Not possible because of UNIX restictition, but PLEASE RTFM for cdrecord. Probably I didn't make myself clear here: I just found out that making cdrecord suid root does infact work. It didn't orginally for me but that was apparently due to a different problem. So, I'm a happy camper with regards to this. o How can I use rscsi without having to have rshd running on the server=20 machine? Impossible o Is there a way to use ssh instead of rsh? Why? ssh is way too slow for cd writing. Hm...I think it depends. This is between the machines in question: andree@aurich:~/downloads/kernelscp linux-2.2.17.tar.bz2 jever: Password: linux-2.2.17.tar.bz2 100% || 13727 KB00:02 Between 2 and 3 seconds for 13+MB should be sufficient for CD writing don't you think. Or is there a hidden latency problem somewhere? A good reason to use ssh/sshd would be encryption of the datastream in situations where you want to use it across a non-trusted net. If you have a ssh aware rcmd(3) implementation it should work. I'll check that out, thanks! Would that give me encryption of the data? I fear not, as rcmd is rcmd and doesn't come with encryption... Other questions: What is your opinion on http://sourceforge.net/projects/linux-iscsi? I understand that this is only a client to access iSCSI services. Are you aware of any server iSCSI development for Linux? This would pretty much be what rscsi is doing, wouldn't it? The RSCSI idea is more than 5 years old and has been finally implemented short before the ISCSI idea came up. If you believe that ISCSI makes sense, write a ISCSI transport implementaion for libscg and send it to me... I'm using SANE to access a remote scanner just as I'm trying to access a remote CD writer via cdrecord/rscsi. This prompts me to ask the question whether you've ever contemplated to turn cdrecord into a library just like the SANE folks did? Sorry, I contacted the SANE people many times to use my scsi trnaport implementaion. They don't like it because their implementation is so InSANE that it is not possible to integrate a SCSI trabsport with a clean interface :-( That is quite sad to hear as it sounds like triplication of effort. My understanding is that iSCSI is an open (?) industry standard which can be implemented by anyone. (Well, anyone that understands the matter, ie. not me, so don't hold your breath... ;-) ) This to my mind gives it an edge over rscsi and whatever SANE is doing. I quite like the SANE approach as it doesn't require me to run rshd but comes with its own custom-purpose daemon. This is purely from a user perspective without any insight in the actual implementation of course. What I really meant with my library question is this: In the SANE world you have e.g. aurich:/usr/binldd xsane libsane.so.1 = /usr/lib/libsane.so.1 (0x40014000) In other words, the functionality is encapsulated in a library. Wouldn't it be nice to have something like: aurich:/usr/binldd gtoaster libcdrecord.so.1 = /usr/lib/libcdrecord.so.1 (0x40014000) I'd dare say that making the cdrecord functionality available as a library should have a number of advantages over calling a separate program. What is your opinion on this? Best regards Andree -- Andree Leidenfrost Sydney - Australia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help with cdrecord/rscsi
Hi Jörg Make sure that .rhost is set up correctly. The permissions of ~rscsi/.rhosts were a bit, er, liberal. It works now, as root I can do cdrecord dev=REMOTE:[EMAIL PROTECTED] -scanbus on the client machine and I get a list of SCSI targets on the server machine. READ the README's for remote SCSI! What do you mean? How do you think did I get as far as I did before contacting the mailing list? ;-) Seriously, I tried to do the preferred method from README.rscsi.gz as a starting point. Are there other READMEs for remote SCSI? If so, I'd be keen to find out whether they have information regarding the following: o How can I use remote devices without being root on the client machine? o How can I use rscsi without having to have rshd running on the server machine? o Is there a way to use ssh instead of rsh? Note: I am not necessarily argueing with the security of the setup suggested. My primary concern is that I have to have rshd running on the server machine which I normally don't. Other questions: What is your opinion on http://sourceforge.net/projects/linux-iscsi? I understand that this is only a client to access iSCSI services. Are you aware of any server iSCSI development for Linux? This would pretty much be what rscsi is doing, wouldn't it? I'm using SANE to access a remote scanner just as I'm trying to access a remote CD writer via cdrecord/rscsi. This prompts me to ask the question whether you've ever contemplated to turn cdrecord into a library just like the SANE folks did? Best regards Andree -- Andree Leidenfrost Sydney - Australia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help with cdrecord/rscsi
Jörg Are you saying I can only use rscsi as user root on the client machine even though cdrecord is setuid root on the client machine? As root I get: jever:/home/andree# cdrecord dev=REMOTE:[EMAIL PROTECTED] -scanbus -d dev: REMOTE:[EMAIL PROTECTED] speed: 4 fs: 4194304 Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: 'REMOTE:[EMAIL PROTECTED]' devname: 'REMOTE:[EMAIL PROTECTED]' scsibus: -1 target: -1 lun: -1 scg__open(REMOTE:[EMAIL PROTECTED]) -1,-1,-1 Warning: Using remote SCSI interface. cdrecord: locuser: 'root' rscsiuser: 'rscsi' host: '192.168.1.1' Permission denied. cdrecord: Success. Cannot get connection to remote host. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. I have added root to .rhosts on the server machine and I can logon using rsh/rlogin without password to account rscsi no problem. So, why do I get 'Permission denied.' and in the next line 'cdrecord: Success. [...]'? I don't normally only use ssh and don't have rshd installed. Is there a chance to get it to work with ssh and without having to be root on the client system. Best regards Andree -- Andree Leidenfrost Sydney - Australia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Need help with cdrecord/rscsi
Hi I am trying to setup remote CD burner access between 2 Debian woody boxes (kernel 2.4.18). There seems to be some kind of access/authentication problem as /tmp/RSCSI does not even get created when trying to access the remote CD burner. The session looks like this: andree@jever:~cdrecord dev=REMOTE:rscsi@aurich: -scanbus -d dev: REMOTE:rscsi@aurich: speed: 4 fs: 4194304 Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: 'REMOTE:rscsi@aurich:' devname: 'REMOTE:rscsi@aurich:' scsibus: -2 target: -2 lun: -2 scg__open(REMOTE:rscsi@aurich:) -2,-2,-2 Warning: Using remote SCSI interface. cdrecord: locuser: 'andree' rscsiuser: 'rscsi' host: 'aurich' rcmd: socket: m cdrecord: Permission denied. Cannot get connection to remote host. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. From the mailing list archive I gather that other people were bitten by this before. So, if anyone has figured it out: Please share your wisdom with a desperate soul! ;-) 'rlogin -l rscsi aurich' works fine, ie. I get access to the machine without providing a password and rscsi starts. /home/rscsi/.rhosts looks like this: jever andree (I tried what README.rscsi says, ie. just providing the user name with the same error but I can then not logon using rlogin without a password.) /etc/default/rscsi looks like this: DEBUG=/tmp/RSCSI USER=* ACCESS=** -1 -1 -1 -1 Permissions of the binaries are as follows: -rwsr-xr-x 1 root root 181160 Apr 9 19:44 /usr/bin/cdrecord -rwsr-xr-x 1 root root 61544 Apr 9 19:44 /usr/sbin/rscsi cdrecord locally on the machine with the CD writer works fine: andree@aurich:~cdrecord -scanbus Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling Linux sg driver version: 3.1.22 Using libscg version 'schily-0.5' scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) 'IBM ' 'DCAS-34330 ' 'S65A' Disk 0,5,0 5) 'IOMEGA ' 'ZIP 100 ' 'E.08' Removable Disk 0,6,0 6) * 0,7,0 7) * scsibus1: 1,0,0 100) 'RICOH ' 'CD-R/RW MP7120A ' '1.10' Removable CD-ROM 1,1,0 101) 'PIONEER ' 'DVD-ROM DVD-115 ' '1.22' Removable CD-ROM 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * If there is any other information that is required, please, let me know and I'll provide it. Thanks a lot for your time best regards Andree -- Andree Leidenfrost Sydney - Australia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi question, need HELP
Mike R. Cannon wrote: I am trying to write cdroms with my IDE drive. At this point I can't even mount a cdrom in it. Below is my configuration: more /boot/grub/grub.conf | grep ide kernel /vmlinuz-2.4.7-10 ro root=/dev/sda3 hdc=ide-scsi kernel /vmlinuz ro root=/dev/sda3 hdc=ide-scsi /sbin/lsmod Module Size Used by vmnet 16864 6 vmmon 17856 0 (unused) eepro100 16032 1 af_packet 11872 0 (autoclean) ide-scsi7648 0 ide-cd 26544 0 cdrom 27552 0 [ide-cd] ide-mod65008 0 [ide-scsi ide-cd] rtc 5536 0 (autoclean) more /etc/fstab | grep cdrom1 /dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,kudzu,ro 0 0 ls -al /dev/cdrom1 lrwxrwxrwx1 root root9 Dec 3 22:31 /dev/cdrom1 - /dev/scd0 more /etc/modules.conf options ide-cd ignore=hdc alias scd0 sr_mod pre-install sg modprobe ide-scsi pre-install sr_mod modprobe ide-scsi pre-install ide-scsi modprobe ide-cd cdrecord -scanbus Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling Linux sg driver version: 3.1.20 Using libscg version 'schily-0.5' scsibus0: 0,0,0 0) 'COMPAQPC' 'DDYS-T18350N' 'B93E' Disk 0,1,0 1) * 0,2,0 2) 'COMPAQPC' 'DDYS-T18350N' 'B93E' Disk 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * -- Mike Cannon Infrastructure Systems Administrator Vice President for Information Technology Purdue University 1061 Freehafer Hall (FREH) West Lafayette, IN 47907-1061 office phone: 765.494.6357 office fax: 765.496.1380 email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Mike Cannon Infrastructure Systems Administrator Management Information Purdue University 1061 Freehafer Hall (FREH) West Lafayette, IN 47907-1061 office phone: 765.494.6357 office fax: 765.496.1380 email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi question, need HELP
Mike,
I am pretty sure that your problem is ide-cd.o.
If you remove ide-cd.o from your system and instead use
ide-scsi.o, sr_mod.o (for CDROM support), and sg.o (for the CD
burner interface), that you should be OK.
As I understand ide-{cd,floppy,tape}.o, these modules basically
take over the ATAPI (scsi over IDE) interface for the devices in
question and impelement limited device interfaces to avoid the need
to have scsi support in the kernel. ide-scsi.o will not talk to
devices that have been claimed by ide-{cd,floppy,tape}.o.
Adam J. Richter __ __ 4880 Stevens Creek Blvd, Suite 104
[EMAIL PROTECTED] \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 Free Software For The Rest Of Us.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
