On Mon, Nov 30, 2009 at 11:44:13PM +0100, Joerg Schilling wrote:
José Romildo Malaquias j.romi...@gmail.com wrote:
Then please test again with -v
It works. See attached the output of the command:
# script -f -c /var/tmp/CDRTOOLS/opt/schily/bin/cdrecord -v -sao -eject
speed=8
José Romildo Malaquias wrote:
On Mon, Nov 30, 2009 at 11:44:13PM +0100, Joerg Schilling wrote:
José Romildo Malaquias j.romi...@gmail.com wrote:
Then please test again with -v
It works. See attached the output of the command:
# script -f -c
On Monday 30 November 2009 03:21:08 daid kahl wrote:
Forgive the top-post, but I would like to say I was very impressed by
the analysis of Joerg Schilling.
Given the issue appears resolved, I can't help myself:
When I bought this notebook in january and first installed gentoo,
cdrecord
José Romildo Malaquias j.romi...@gmail.com wrote:
Then please test again with -v
It works. See attached the output of the command:
# script -f -c /var/tmp/CDRTOOLS/opt/schily/bin/cdrecord -v -sao -eject
speed=8 fs=256m driveropts=burnfree /var/tmp/image.iso /var/tmp/cdrecord.log
This is
José Romildo Malaquias j.romi...@gmail.com wrote:
On Fri, Nov 20, 2009 at 04:48:25PM +0100, Joerg Schilling wrote:
José Romildo Malaquias j.romi...@gmail.com wrote:
There was a report for broken Pioneer formware that hits in -v mode and
causes the firmware from the drive to through
Forgive the top-post, but I would like to say I was very impressed by
the analysis of Joerg Schilling.
Given the issue appears resolved, I can't help myself:
When I bought this notebook in january and first installed gentoo,
cdrecord used to work. Then at some point ago (probably after some
On 11/29/2009 8:21 PM, daid kahl wrote:
When I bought this notebook in january and first installed gentoo,
cdrecord used to work. Then at some point ago (probably after some
update) it has stopped working with the behaviour I have described
above.
This is every single story of Gentoo and
José Romildo Malaquias j.romi...@gmail.com wrote:
BTW: this may be caused by the fact that you did not simply add debug=2
but at the same time removed -V.
I have run the cdrecord command again, this time passing -V and debug=2:
$ script -f -c cdrecord -vvv -V debug=2 -sao -eject speed=8
On Fri, Nov 20, 2009 at 01:36:27PM +0100, Joerg Schilling wrote:
José Romildo Malaquias j.romi...@gmail.com wrote:
BTW: this may be caused by the fact that you did not simply add debug=2
but at the same time removed -V.
I have run the cdrecord command again, this time passing -V and
joerg.schill...@fokus.fraunhofer.de (Joerg Schilling) wrote:
José Romildo Malaquias j.romi...@gmail.com wrote:
BTW: this may be caused by the fact that you did not simply add debug=2
but at the same time removed -V.
I have run the cdrecord command again, this time passing -V and
José Romildo Malaquias j.romi...@gmail.com wrote:
There was a report for broken Pioneer formware that hits in -v mode and
causes the firmware from the drive to through away the data before writing
it to the medium.
Do you mean a test without -V or -v ?
Without -v, as in this case
José Romildo Malaquias j.romi...@gmail.com wrote:
Do you mean a test without -V or -v ?
Without -v, as in this case cdrecord does not read the drives buffer fill
ratio.
It seems that there is a bug in Pioneer firmware that is triggered by
calling
SCSI get buffer cap (0x5C)and
José Romildo Malaquias j.romi...@gmail.com wrote:
On Mon, Nov 16, 2009 at 03:43:12PM +0100, Joerg Schilling wrote:
José Romildo Malaquias j.romi...@gmail.com wrote:
To find the reason for the following Impossible because
illegal error situation:
Executing 'test unit ready' command
On Mon, Nov 16, 2009 at 03:43:12PM +0100, Joerg Schilling wrote:
José Romildo Malaquias j.romi...@gmail.com wrote:
To find the reason for the following Impossible because
illegal error situation:
Executing 'test unit ready' command on Bus 0 Target 6, Lun 0 timeout 40s
CDB: 00 00 00 00 00
José Romildo Malaquias j.romi...@gmail.com wrote:
To find the reason for the following Impossible because
illegal error situation:
Executing 'test unit ready' command on Bus 0 Target 6, Lun 0 timeout 40s
CDB: 00 00 00 00 00 00
cdrecord: Input/output error. test unit ready: scsi sendcmd: fatal
José Romildo Malaquias j.romi...@gmail.com wrote:
You may try to call cdrecord -v -checkdrive -V
and have a look at the SCSI read buffer command.
Unfortanatly I do not know how to deal with the output of the above
command. So I am attaching it here (cdrecord0.log) and maybe someaone
On Wed, Nov 11, 2009 at 06:03:39PM +0100, Joerg Schilling wrote:
José Romildo Malaquias j.romi...@gmail.com wrote:
[...]
OK, the drive does not support the read buffer command, this is why cdrecord
cannot do a DMA speed test.
But you have a massive problem in the linux kernel that needs to
José Romildo Malaquias j.romi...@gmail.com wrote:
Did you ever write a DVD-R with this hardware?
Yes I have written some DVD-R discs with this hardware. When I bought
the notebook and installed gentoo in last January, burning with cdrecord
(from cdrtools) used to work. Sometime later (about
José Romildo Malaquias j.romi...@gmail.com wrote:
Most of the requested information can be found in the attached log file.
I do not know how to get the ATIP data on the media used. But I can say
Call cdrecord -atip
For the medium state, I would need the output from cdrecord -minfo
before
On Mon, Nov 09, 2009 at 10:11:40AM +0100, Joerg Schilling wrote:
José Romildo Malaquias j.romi...@gmail.com wrote:
Most of the requested information can be found in the attached log file.
I do not know how to get the ATIP data on the media used. But I can say
Call cdrecord -atip
By
Hello.
Burning dvds with Cdrecord-ProDVD-ProBD-Clone 2.01.01a67 on my Dell
Vostro 1510 notebook is always failing.
The device is identified as TEAC DVD+-RW DVW28SLC and can write at 8x
speed.
The process starts and reports writing at 14.5x, but the media is not
burnt. cdrecord reaches but does
José Romildo Malaquias j.romi...@gmail.com wrote:
Hello.
Burning dvds with Cdrecord-ProDVD-ProBD-Clone 2.01.01a67 on my Dell
Vostro 1510 notebook is always failing.
The device is identified as TEAC DVD+-RW DVW28SLC and can write at 8x
speed.
The process starts and reports writing at
On Sun, Nov 08, 2009 at 05:35:50PM +0100, Joerg Schilling wrote:
José Romildo Malaquias j.romi...@gmail.com wrote:
Hello.
Burning dvds with Cdrecord-ProDVD-ProBD-Clone 2.01.01a67 on my Dell
Vostro 1510 notebook is always failing.
The device is identified as TEAC DVD+-RW DVW28SLC and
On Sun, Nov 08, 2009 at 11:23:50PM -0200, José Romildo Malaquias wrote:
On Sun, Nov 08, 2009 at 05:35:50PM +0100, Joerg Schilling wrote:
José Romildo Malaquias j.romi...@gmail.com wrote:
[...]
Burning dvds with Cdrecord-ProDVD-ProBD-Clone 2.01.01a67 on my Dell
Vostro 1510 notebook is
24 matches
Mail list logo
