Joerg Schilling wrote:
Bill Davidsen [EMAIL PROTECTED] wrote:
Paragraph 4.3.7 DVD+R Dual Layer is much more detailed
about the layer hop. Nevertheless there is a statement
which makes me believe it is worth a try to just write
to it as to a fat DVD+R.
That seems to work. I did
Bill Davidsen [EMAIL PROTECTED] wrote:
As for both complete surfaces, the last volume was only 6.7GB or so, and
read back fine. So having to write an image covering both complete
surfaces (what you said) doesn't seem required.. Did you ever try just
writing an 8GB image to a DL, without
Thomas Schmitt wrote:
Hi,
Bill Davidsen:
I did recently discover that it [cdrskin] has limitations
doing odd raw burns, but that's not a usual requirement,
Would it be indiscrete to ask for the use case and what
cdrecord write mode option you wanted to apply ?
Not in the least, I
Bill Davidsen [EMAIL PROTECTED] wrote:
Thomas Schmitt wrote:
Hi,
Bill Davidsen:
I did recently discover that it [cdrskin] has limitations
doing odd raw burns, but that's not a usual requirement,
Would it be indiscrete to ask for the use case and what
cdrecord write
Bill Davidsen [EMAIL PROTECTED] wrote:
Joerg Schilling wrote:
Bill Davidsen [EMAIL PROTECTED] wrote:
http://www.arklinux.org/projects/dvdrtools/
This page is temporarily down because of spammer attacks; until it
comes back, you can download dvdrtools from svn ...
Joerg Schilling wrote:
Bill Davidsen [EMAIL PROTECTED] wrote:
http://www.arklinux.org/projects/dvdrtools/
This page is temporarily down because of spammer attacks; until it
comes back, you can download dvdrtools from svn ...
Now who would do a thing like that?
Who can
Hi,
How about if I just try a burn with raw96r and see if that works?
Worth a try. But man cdrecord says:
-raw Set RAW writing mode. Using this option defaults
to -raw96r
So probably you cannot expect better results than with
cdrecord -raw.
During my adventures in google i
Thomas Schmitt [EMAIL PROTECTED] wrote:
Hi,
How about if I just try a burn with raw96r and see if that works?
Worth a try. But man cdrecord says:
-raw Set RAW writing mode. Using this option defaults
to -raw96r
So probably you cannot expect better results than with
On Friday 27 July 2007 17:52, Thomas Schmitt wrote:
This does not match the current problem.
pengsens' drive refuses on any write mode which yields
this message in wodim's output
Supported modes:
while in bug=413960 the according message is:
Supported modes: TAO PACKET SAO SAO/R96P
Hi,
The failure depends on timing between wodim and hal. IMHO there is
a chance that it fails earlier if hal polls the drive in the right moment.
Not impossible, i have to confess.
But reading wodim's source for write-mode detection
i have to conclude that hald would have to _reliably_
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
On Friday 27 July 2007 17:52, Thomas Schmitt wrote:
This does not match the current problem.
pengsens' drive refuses on any write mode which yields
this message in wodim's output
Supported modes:
while in bug=413960 the according message
Thomas Schmitt [EMAIL PROTECTED] wrote:
But reading wodim's source for write-mode detection
i have to conclude that hald would have to _reliably_
sabotage at least half a dozen consequtive attempts
to set the write parameters by mode page 05h.
If this part of wodim has bot been bastardized,
Chris Ahlstrom wrote:
* Greg Wooledge [EMAIL PROTECTED] [2007-07-27 11:55:19 -0400]:
On Fri, Jul 27, 2007 at 09:59:36AM -0400, Chris Ahlstrom wrote:
Perhaps I am talking out of turn here, but isn't this mailing list
restricted to covering the Debian fork (reference
Thomas Schmitt wrote:
Hi,
me:
growisofs claims to be able, cdrecord claims to be able.
Joerg Schilling:
I cannot speak for growisofs but cdrecord is definitely able to correctly
copy DVD-Video with DVD+R/DL and driveropts=layerbreak=#
claims does not mean i doubt it. I
Joerg Schilling wrote:
Thomas Schmitt [EMAIL PROTECTED] wrote:
But reading wodim's source for write-mode detection
i have to conclude that hald would have to _reliably_
sabotage at least half a dozen consequtive attempts
to set the write parameters by mode page 05h.
If this part of
Hi,
Bill Davidsen:
I did recently discover that it [cdrskin] has limitations
doing odd raw burns, but that's not a usual requirement,
Would it be indiscrete to ask for the use case and what
cdrecord write mode option you wanted to apply ?
libburn contains code for raw write modes and i
Hi,
Vladimir Nadvornik:
I think that updating wodim is a good idea anyway,
me:
Agreed.
Joerg Schilling:
NO
Independend of the question wether to use cdrecord,
wodim or cdrskin, it makes sense to upgrade from
earlier wodims to 1.1.6.
It eases the hald problem if one uses the block device
Bill Davidsen [EMAIL PROTECTED] wrote:
http://www.arklinux.org/projects/dvdrtools/
This page is temporarily down because of spammer attacks; until it
comes back, you can download dvdrtools from svn ...
Now who would do a thing like that?
Who can understand the
Bill Davidsen [EMAIL PROTECTED] wrote:
Paragraph 4.3.7 DVD+R Dual Layer is much more detailed
about the layer hop. Nevertheless there is a statement
which makes me believe it is worth a try to just write
to it as to a fat DVD+R.
That seems to work. I did some backups that way,
Thomas Schmitt [EMAIL PROTECTED] wrote:
Independend of the question wether to use cdrecord,
wodim or cdrskin, it makes sense to upgrade from
earlier wodims to 1.1.6.
What do you gain from using a probably less defective
version of a dead fork from an old version of cdrecord
if you have the
Hi,
me:
Eduard Bloch was told that there is no problem if
only we userland applications coordinate neatly.
Joerg Schilling:
Alan Cox [...] with his answers to Mr. Bloch, he was correct,
but I did not see him writing this claim.
That's what i understand from this statement by Alan Cox
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
On Friday 27 July 2007 12:00, Joerg Schilling wrote:
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
Hi,
It might be this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413960
(LG drive on /dev/sg)
It is fixed in wodim 1.1.6.
On Friday 27 July 2007 12:00, Joerg Schilling wrote:
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
Hi,
It might be this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413960
(LG drive on /dev/sg)
It is fixed in wodim 1.1.6.
This is a bug _introduced_ by wodim!
It never has
* Joerg Schilling [EMAIL PROTECTED] [2007-07-27 15:23:48 +0200]:
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
I just verified the bug with the original cdrtools-2.01.01a30,
Sorry, but this kind of communication is not helpful, you claim things that
you do not prove.
If you have
On Fri, Jul 27, 2007 at 09:59:36AM -0400, Chris Ahlstrom wrote:
Perhaps I am talking out of turn here, but isn't this mailing list
restricted to covering the Debian fork (reference
http://lists.debian.org/debian-devel-announce/2006/09/msg2.html)?
No, this mailing list predates 2006 by
Hi,
Vladimir Nadvornik:
It might be this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413960
This does not match the current problem.
pengsens' drive refuses on any write mode which yields
this message in wodim's output
Supported modes:
while in bug=413960 the according message is:
Chris Ahlstrom wrote:
* Joerg Schilling [EMAIL PROTECTED] [2007-07-27 15:23:48 +0200]:
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
I just verified the bug with the original cdrtools-2.01.01a30,
Sorry, but this kind of communication is not helpful, you claim things that
you do
* Thomas Schmitt [EMAIL PROTECTED] [2007-07-27 18:05:05 +0200]:
Chris Ahlstrom:
Perhaps I am talking out of turn here, but isn't this mailing list
restricted to covering the Debian fork (reference
http://lists.debian.org/debian-devel-announce/2006/09/msg2.html)?
Thomas Schmitt [EMAIL PROTECTED] wrote:
For wodim problem reports i would post to
[EMAIL PROTECTED]
although it is labeled as developer mailing list.
pengseng's problem with the drive is surely a development issue.
This list is dead since 3 months as the package is..
Jörg
--
Joerg Schilling wrote:
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
On Friday 27 July 2007 12:00, Joerg Schilling wrote:
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
Hi,
It might be this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413960
(LG drive on /dev/sg)
It is
Chris Ahlstrom [EMAIL PROTECTED] wrote:
I don't mean alternate front ends, but engines. Is there a good site
with a feature matrix? This site, though amusing, does not have one:
http://en.wikipedia.org/wiki/Cdrecord
The world is not yet ready for free information there are always
Chris Ahlstrom [EMAIL PROTECTED] wrote:
Perhaps I am talking out of turn here, but isn't this mailing list
restricted to covering the Debian fork (reference
http://lists.debian.org/debian-devel-announce/2006/09/msg2.html)?
That is surely my primary interest, at any rate.
If your hobby
Chris Ahlstrom [EMAIL PROTECTED] wrote:
What about dvdrtools and dvd+rw-tools? I use the latter, but just
discovered the former. It looks like the dvdrtools web site is down,
though.
It is not down, it's Webmaster did just delete all the content that was
related to this project that is
Hi,
It might be this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413960
(LG drive on /dev/sg)
It is fixed in wodim 1.1.6.
--
Vladimir Nadvornik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Greg Wooledge [EMAIL PROTECTED] wrote:
On Fri, Jul 27, 2007 at 09:59:36AM -0400, Chris Ahlstrom wrote:
Perhaps I am talking out of turn here, but isn't this mailing list
restricted to covering the Debian fork (reference
http://lists.debian.org/debian-devel-announce/2006/09/msg2.html)?
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
Hi,
It might be this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413960
(LG drive on /dev/sg)
It is fixed in wodim 1.1.6.
This is a bug _introduced_ by wodim!
It never has been in the original cdrtools.
Note that recently,
On Friday 27 July 2007 15:23, Joerg Schilling wrote:
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
On Friday 27 July 2007 12:00, Joerg Schilling wrote:
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
Hi,
It might be this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413960
Hi,
Chris Ahlstrom:
Perhaps I am talking out of turn here, but isn't this mailing list
restricted to covering the Debian fork (reference
http://lists.debian.org/debian-devel-announce/2006/09/msg2.html)?
cdwrite@other.debian.org is an unmoderated support and discussion
list about burning
* Greg Wooledge [EMAIL PROTECTED] [2007-07-27 11:55:19 -0400]:
On Fri, Jul 27, 2007 at 09:59:36AM -0400, Chris Ahlstrom wrote:
Perhaps I am talking out of turn here, but isn't this mailing list
restricted to covering the Debian fork (reference
Vladimir Nadvornik [EMAIL PROTECTED] wrote:
Everything is described in the debian bugreport, including cause of the
problem and a fix. You can't claim that the bug was introduced by wodim
if you have not read it.
The debian bug report describes a bug that is not present in the original
* Joerg Schilling [EMAIL PROTECTED] [2007-07-27 18:23:15 +0200]:
The world is not yet ready for free information there are always trolls
that write incorrect claim into a wiki.
You are entirely free to correct it, I understand.
http://www.arklinux.org/projects/dvdrtools/
This
Chris Ahlstrom [EMAIL PROTECTED] wrote:
* Joerg Schilling [EMAIL PROTECTED] [2007-07-27 18:23:15 +0200]:
The world is not yet ready for free information there are always trolls
that write incorrect claim into a wiki.
You are entirely free to correct it, I understand.
There are trolls
Hi,
Chris Ahlstrom:
But are there any other CD/DVD writing engines out their?
Yes. libburn supports CD and single layer DVD with
capabilities according to MMC-5. (That is about what
growisofs can do - minus the capability to fabricate
ISO-9660 multi-session on random access media which got
no
Thomas Schmitt [EMAIL PROTECTED] wrote:
I also wonder where to find some advice about burning dual-layer DVDs.
I couldn't do it before. Might have been my old Liteon drive, which
later stopped working completely.
growisofs claims to be able, cdrecord claims to be able.
I cannot speak
Hi,
me:
growisofs claims to be able, cdrecord claims to be able.
Joerg Schilling:
I cannot speak for growisofs but cdrecord is definitely able to correctly
copy DVD-Video with DVD+R/DL and driveropts=layerbreak=#
claims does not mean i doubt it. I just did
not test it myself. Different from
Hi,
I want to use cdrecord to burn a CD,
wodim: No write mode specified.
You are actually using the cdrecord fork of the cdrkit
project, which is affiliated with Debian.
Original cdrecord is available at
ftp://ftp.berlios.de/pub/cdrecord/alpha/
Most recent is
cdrtools-2.01.01a31.tar.gz
pengsens [EMAIL PROTECTED] wrote:
I have two CD-RW/DVD±RW Drives:
use cdrecord -scanbus can see:
1,0,0 100) 'HL-DT-ST' 'DVD-RAM GSA-H30N' '1.05' Removable CD-ROM
2,0,0 200) 'TSSTcorp' 'CD/DVDW TS-H653A' 'CM00' Removable CD-ROM
I want to use cdrecord to burn a CD, when cdrecord -v
. Trouble? Contact
[EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/cdrecord-problems-tf4140203.html#a11778707
Sent from the cdwrite mailing list archive at Nabble.com.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
Thomas Schmitt [EMAIL PROTECTED] wrote:
I want to use cdrecord to burn a CD,
wodim: No write mode specified.
You are actually using the cdrecord fork of the cdrkit
project, which is affiliated with Debian.
Original cdrecord is available at
ftp://ftp.berlios.de/pub/cdrecord/alpha/
Hi,
I have tried all these modes such as tao, sao, dao, raw, etc. but none of
these would work , I think may be linux kernel support to my new drive is
not very good
The Linux kernel does not provide support for a
particular drive. It rather forwards the MMC
commands of our burn programs
* Joerg Schilling [EMAIL PROTECTED] [2007-07-25 13:58:05 +0200]:
Correct, but it does not make sense at all to try wodim.
Give it up, man!
Cdrecord deals with the deficits of the Linux SCSI address schemes
--
Tux rox!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Chris Ahlstrom [EMAIL PROTECTED] wrote:
* Joerg Schilling [EMAIL PROTECTED] [2007-07-25 13:58:05 +0200]:
Correct, but it does not make sense at all to try wodim.
Give it up, man!
Come back to reality and stop whining on a dead fork.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling
Thomas Schmitt [EMAIL PROTECTED] wrote:
Hi,
I have tried all these modes such as tao, sao, dao, raw, etc. but none of
these would work , I think may be linux kernel support to my new drive is
not very good
The Linux kernel does not provide support for a
particular drive. It rather
Hi all,
Joerg Schilling:
Correct, but it does not make sense at all to try wodim.
Chris Ahlstrom:
Give it up, man!
Let me clarify the technical side of the problem.
It is interesting enough.
Number one of the try-to-do list is original cdrecord.
Nevertheless i rather do not expect it to have
Thomas Schmitt [EMAIL PROTECTED] wrote:
Number one of the try-to-do list is original cdrecord.
Nevertheless i rather do not expect it to have
much more success than wodim as the affected code
seems to be quite old.
The maintainers of wodim did change a lot of things that
better should stay
* Joerg Schilling [EMAIL PROTECTED] [2007-07-25 14:16:02 +0200]:
Chris Ahlstrom [EMAIL PROTECTED] wrote:
* Joerg Schilling [EMAIL PROTECTED] [2007-07-25 13:58:05 +0200]:
Correct, but it does not make sense at all to try wodim.
Give it up, man!
Come back to reality and stop
Chris Ahlstrom [EMAIL PROTECTED] wrote:
* Joerg Schilling [EMAIL PROTECTED] [2007-07-25 14:16:02 +0200]:
Chris Ahlstrom [EMAIL PROTECTED] wrote:
* Joerg Schilling [EMAIL PROTECTED] [2007-07-25 13:58:05 +0200]:
Correct, but it does not make sense at all to try wodim.
Give it
= 4096 KB
wodim: Drive does not support TAO recording.
wodim: Illegal write mode for this drive.
It cannot detect the support mode. Can anyone help me with this ? Thanks a
lot !!!
--
View this message in context:
http://www.nabble.com/cdrecord-problems-tf4140203.html#a11776606
Sent from the cdwrite
From: Dan [EMAIL PROTECTED]
Hi everyone,
Ok, since it's been a while and people were forgetting what the problem
is I decided to start a thread with a short summary of my problem,
what's been tried, and some new info. Thanks to everyone who's replied
before.
the new info: I swapped out my TDK
Hi everyone,
Ok, since it's been a while and people were forgetting what the problem
is I decided to start a thread with a short summary of my problem,
what's been tried, and some new info. Thanks to everyone who's replied
before.
the new info: I swapped out my TDK 440n dvd burner for a sony
Dan wrote:
On Sat, 2004-07-17 at 19:19, Bill Davidsen wrote:
lsof and see what process is causing the problem.
Here's a ps -A and lsof of when I kill as much as I can and still have
the problem:
PID TTY TIME CMD
1 ?00:00:02 init
2 ?00:00:01 migration/0
3 ?
From: Bill Davidsen [EMAIL PROTECTED]
Dan wrote:
On Sat, 2004-07-17 at 19:19, Bill Davidsen wrote:
lsof and see what process is causing the problem.
Here's a ps -A and lsof of when I kill as much as I can and still have
the problem:
PID TTY TIME CMD
1 ?
On Mon, 19 Jul 2004, Joerg Schilling wrote:
From: Bill Davidsen [EMAIL PROTECTED]
Dan wrote:
On Sat, 2004-07-17 at 19:19, Bill Davidsen wrote:
lsof and see what process is causing the problem.
Here's a ps -A and lsof of when I kill as much as I can and still have
the
From: Rob Bogus mail account [EMAIL PROTECTED]
On Mon, 19 Jul 2004, Joerg Schilling wrote:
From: Bill Davidsen [EMAIL PROTECTED]
Dan wrote:
On Sat, 2004-07-17 at 19:19, Bill Davidsen wrote:
lsof and see what process is causing the problem.
Here's a ps -A and lsof of when I
On Sat, 2004-07-17 at 19:19, Bill Davidsen wrote:
lsof and see what process is causing the problem.
Here's a ps -A and lsof of when I kill as much as I can and still have
the problem:
PID TTY TIME CMD
1 ?00:00:02 init
2 ?00:00:01 migration/0
3 ?
Hi,
when Joerg says volume management, he does NOT refer to
LVM/RAID stuff; he means automounters and things like that.
(And my untrained eyes don't see anything wrong with the
ps output. But you don't want to trust me here.)
On Sun, Jul 18, 2004 at 01:28:34PM -0400, Dan wrote:
On Sat,
Looks like you have another unfriendly application running that
tries simultanous access to the drive :-(
Jrg
Ok, I tried exiting out of all programs I could (stopping just about
every service, getting out of X, etc.) ps -A shows only pretty minimal
processes running, though I can show the
From: Dan [EMAIL PROTECTED]
Ok, I tried exiting out of all programs I could (stopping just about
every service, getting out of X, etc.) ps -A shows only pretty minimal
processes running, though I can show the list if you want. I also tried
umounting and rmmoding supermount, lsof | grep cdrom
On Fri, 2004-07-16 at 10:22, Joerg Schilling wrote:
If you are sure that you did kill all volmgt programs too, as the Linux
Kernel develpers.
Sorry but this is definitely not a cdrecord issue.
Jrg
hmmm, I do run lvm and software raid on this box, do you think those may
have
From: Dan [EMAIL PROTECTED]
I'm having problems burning cds with my TDK 440n DVD+/-rw drive,
burning dvds with growisofs works fine. It's not the drive's hardware,
as I've tested burning cds in windows on another box and it's working
ok. Burning cds with cdrecord did work in the past, but
Hi there,
I'm having problems burning cds with my TDK 440n DVD+/-rw drive,
burning dvds with growisofs works fine. It's not the drive's hardware,
as I've tested burning cds in windows on another box and it's working
ok. Burning cds with cdrecord did work in the past, but I've since
updated
From: Antonio Pagliaro [EMAIL PROTECTED]
I am running Suse 7.3 with kernel 2.4.10 and
Cdrecord 1.11a05 (i686-suse-linux).
My Cd writer is a Waitec Storm 24.
I have problems writing audio both in dummy
mode or in real mode.
I use gcombust or the command line:
cdrecord -v -eject fs=4m speed=2
Dear all,
I am running Suse 7.3 with kernel 2.4.10 and
Cdrecord 1.11a05 (i686-suse-linux).
My Cd writer is a Waitec Storm 24.
I have problems writing audio both in dummy
mode or in real mode.
I use gcombust or the command line:
cdrecord -v -eject fs=4m speed=2 dev=0,0,0 -dao *.wav
cdrecord
On Sat, Oct 20, 2001 at 12:38:01AM +0200, Aldo Maggi wrote:
...
afterward, as per examples in man cdrecord i launched:
cdrecord -v dev=4,0 -dao -useinfo *.wav
but.it did not work :
...
Sending CUE sheet...
cdrecord: SAO writing not available or not implemented for this drive.
Cdrecord
my distro is debian 2.2r3 burner philips cdd2600 cdrecord ver 1.8
i loaded from cdrom (ide) the audio tracks by cdda2wav into an empty
dir in hdb3
i can listen to them via xmms
afterward, as per examples in man cdrecord i launched:
cdrecord -v dev=4,0 -dao -useinfo *.wav
but.it did not work
From: Aldo Maggi [EMAIL PROTECTED]
my distro is debian 2.2r3 burner philips cdd2600 cdrecord ver 1.8
i loaded from cdrom (ide) the audio tracks by cdda2wav into an empty
dir in hdb3
i can listen to them via xmms
afterward, as per examples in man cdrecord i launched:
cdrecord -v dev=4,0 -dao
I'm working with the latest cdrecord win32 alfa version (V1.11a04 24/6/01).
The Mkisofs and cygwin1.dll are also the latest version.
Statistically, only 1 out of 4 records attempts succeed.
Per the other 3, I'm encountering SCSI error write_g1 0x8 (Busy).
This error always comes
From: [EMAIL PROTECTED]
I'm working with the latest cdrecord win32 alfa version (V1.11a04 24/6/01).
The Mkisofs and cygwin1.dll are also the latest version.
Statistically, only 1 out of 4 records attempts succeed.
Per the other 3, I'm encountering SCSI error write_g1 0x8 (Busy).
78 matches
Mail list logo
