I still fail to burn ISO even to blank CDs. The same for SAO or DAO
to blank and than burn.
I tried to "play" a bit with the few customizable fields in the Brasero
plugins, basically two:
cdrdao (enable the "--driver generic-mmc-raw" flag)
and
growisofs (allow the use of DAO),
but the prob
Hi,
i wrote:
> > My only idea which does not need a code change is to employ the wodim
> > plugin of Brasero and to hope that it burns by write type SAO.
Mauro Sacchetto wrote:
> Which way?
Good question.
I have wodim installed. But last time when i tried, the wodim item was
greyed out in the pl
Il 15/11/21 14:58, Thomas Schmitt ha scritto:
My only idea which does not need a code change is to employ the wodim
plugin of Brasero and to hope that it burns by write type SAO.
If so, then the drive would not get lost after a successful burn run.
Which way?
Thanx!
m
Hi,
Mauro Sacchetto wrote:
> sg_raw /dev/sr0 be 00 ff ff ff ff 00 00 01 10 00 00 --outfile=tdb_data.bin
> After this, the drive is unavailable
Well, then we have found:
- The immediate cause of the problem: READ CD with LBA -1.
- A good suspect in Brasero: Function brasero_medium_track_written_
Il 14/11/21 14:25, Thomas Schmitt ha scritto:
The main question is:
Is the drive unusable afterwards ?
(I.e. do i have identified the culprit for your drive problem ?)
I put the CD into the drive, mount and umount it: all goes.
I lauch che command and obtain:
Hi,
i made the experiments which i mentioned in the previous mail:
- The Pioneer drive does not go mad from READ CD for LBA -1 or from
READ CD MSF for sector 00:01:74.
- The ASUS drive does not go mad from READ CD MSF for sector 00:01:74.
- The TSSTcorp drive tolerates READ CD MSF for sector
Hi,
Mauro Sacchetto wrote:
> samiel@darkstar:~$ sg_raw /dev/sr0 be 00 ff ff ff ff 00 00 01 10 00 00
> --outfile=tdb_data.bin
> SCSI Status: Check Condition
>
> Sense Information:
> Fixed format, current; Sense key: Illegal Request
> Additional sense: Unaligned write command
Now we know from where
Il 14/11/21 12:02, Thomas Schmitt ha scritto:
Hi,
i now have clear evidence from a run of
sg_raw /dev/sr0 be 00 ff ff ff ff 00 00 01 10 00 00 --outfile=tdb_data.bin
that the read attempt for sector 0x (= -1) brings the
ASUS DRW-24D5MT into the unusable state.
@ Mauro Sacchetto:
Co
Hi,
i now have clear evidence from a run of
sg_raw /dev/sr0 be 00 ff ff ff ff 00 00 01 10 00 00 --outfile=tdb_data.bin
that the read attempt for sector 0x (= -1) brings the
ASUS DRW-24D5MT into the unusable state.
@ Mauro Sacchetto:
Could you please try to reproduce this finding after
Hi,
Mauro Sacchetto wrote:
> brasero -g --brasero-media-debug > log 2>&1
(After knowing the magic words i find man pages in the web which have it.)
In the log from a successful Copy job with the Pioneer drive (sr1) i do
not see the message about "TDB".
But in the log of an immediate failure wit
I'm not sure it is what are you searching for,
but Brasero produces a log launching from console it by :
brasero -g --brasero-media-debug > log 2>&1
Then , I choose "Disk copy" and find ~/log
Il 12/11/21 13:25, Thomas Schmitt ha scritto:
I was not able to talk Brasero into showing me its s
Hi,
am i too stupid or is there really no user option to set write type SAO ?
Neither clicking around in Brasero's GUI nor searching for
BRASERO_BURN_FLAG_DAO in the source brings any insight.
I want to burn a blank CD with SAO in order to check whether this avoids
the problem with the ASUS driv
Hi,
the "Copy" task yields very interesting results:
A closed CD-R and a closed CD-RW which were written by write type SAO
don't spoil the drive.
Inserting a closed TAO CD-RW (burnt by Brasero) spoils the drive.
This spoiling is in effect already when the dialog window of Brasero asks
me to subm
Il 11/11/21 22:49, Thomas Schmitt ha scritto:
Hi,
Mauro Sacchetto wrote:
that is (more or less): "Impossible to block unity".
"unit", maybe ? The device.
Yes, sorry for my bad English.
After Brasero fails, it's impossible to erase the CD with K3,
Either Brasero did its evil deed befor
Hi,
Mauro Sacchetto wrote:
> that is (more or less): "Impossible to block unity".
"unit", maybe ? The device.
> After Brasero fails, it's impossible to erase the CD with K3,
Either Brasero did its evil deed before trying to lock the unità or the
failure to do so did not prevent further access
On Mon, 08 Nov 2021 at 17:15:26 +0100, Thomas Schmitt wrote:
> I start Brasero and a window pops up which says it cannot mount the CD.
> (How stupid can Brasero and udisks become ? Is there any limit ?)
My understanding is that udisks does not automatically mount anything on
its own (it's designed
On Testing / Cinnamon it's impossible too "copy a disk"
(another voice of Brasero menu)
The CD-RW seems to be recognized and the burning begins,
but fails with:
Session error : Impossibile bloccare l'unità ((null))
(brasero_burn_record brasero-burn.c:2854)
that is (more or less): "Impossibl
Hi,
i managed to start fvwm2 (by Ctrl+Alt+F2 in the XFCE login window and
startx /usr/bin/fvwm2) and tried whether Brasero and ASUS drive have a
better relationship then.
They don't. It's as bad as with XFCE.
The Brasero run was started with a blank CD-RW in the drive and came,
with two pauses of
I again carried out a small experiment (as a simple user as I am) and
precise,
or rather I correct, what was stated in a previous email.
Burning an ISO to a blank CD-RW (after: wodim dev=/dev/sr0 -v
blank=fast) won't work either:
This is brasero-session.log:
Hi,
what i believe to have learned so far:
- The problem is a co-operation of ASUS DRW-24D5MT and Brasero or
some software which Brasero employs. This other software (if involved
at all) does not strike with K3B (tested by Mauro Sacchetto) or
non-GUI burn programs like wodim or xorriso.
-
I smoothly burned the same ISO with Brasero to a DVD + RW, and the media
was recognized immediately.On the other hand, the identification of the
CD-RW is much slower (apart from the fact that the burn then fails) and
this suggests that something else "occupies" the disc already, which is
why
Hi,
the spoiled ASUS drive does not seem to be a direct result of an attempt
to read audio CD sectors from a data CD.
The drive is rather too tolerant in that aspect. The MMC-5 specs say
that it should throw error 5,64,00 "ILLEGAL MODE FOR THIS TRACK", but
the drive doesn't.
It does not go bad ei
Hi,
Mauro Sacchetto wrote:
> I actually managed to burn a blank CD-RW with brasero as well.
> The problem arises when the CD-RW already has content.
Not for me. Blank CDs behave better with the automounter (but not with
the prompt window which offers me to start the file manager).
But when they a
I actually managed to burn a blank CD-RW with brasero as well. The
problem arises when the CD-RW already has content. Do you have any idea
what software might be doing this anomalous attempt, which is to try to
read the data CD as if it were audio? Given their modest cost, I can of
course also
Hi,
the drive and Brasero work with DVD+RW, unformatted DVD-RW, and
formatted DVD-RW.
No bad symptoms to see, except that i get molested by the automounter
and that i often have to repeatedly double click the drive field and
the "Burn" button before burning begins.
These successes give me the ide
Hi,
Mauro Sacchetto wrote:
> I don't have the option of using more than one burner.
I could try with more USB burners. But we already know that it is a
problem between Brasero or its helper software on one side and the
firmware of ASUS DRW-24D5MT on the other side.
There may be other burner firmw
I don't have the option of using more than one burner.
I had done a simple experiment by installing Brasero (obviously with all
its dependencies) on the partition where I have Stable with KDE. So
different kernel and different version of Brasero. The behavior is the
same as that found in Testin
Hi,
i booted kernel 4.19.0-17 which stems from a Debian 10 upgrade.
Same as with 5.10-rc3:
I started up brasero with empty tray of all drives. After inserting the
CD-RW into the ASUS, brasero does not see it. xorriso shows that the
drive is already in the bad state.
So i did a power cycle with
Hi
i have to correct my previous report:
> The obscure SCSI error 5,21,04 "Unaligned write" appears only with the ASUS.
It appears with the PIONEER too, but not with the TSSTcorp drive.
(And Brasero spoils the ASUS even if the message does not appear.)
Nevertheless, i riddle what SCSI command c
Hi,
Mauro Sacchetto wrote:
> I installed on testing (kernel 5.14...) the kernel 5.10 from stable
> (backports), but I received the same error
So i fired up my experimental machine which has Debian 10 but kernel
5.10.0-rc3 cloned from git branch "linux-block" and modified to fix
a few bugs in modu
I eject the CD-RW, inser it again and try to mount it:
root@darkstar:~# mount /home/samiel/debian-11.1.0-amd64-netinst.iso
/media/cdrom
mount: /media/cdrom0: WARNING: source write-protected, mounted read-only.
So the drive itself is still operational after the mishap.
Yes, but only as root,
Hi,
Mauro Sacchetto wrote:
> samiel@darkstar:~$ xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed
> $isoimage
> [...]
> xorriso : UPDATE : 378 of 378 MB written (fifo 0%) [buf 100%] 0.0x.
> xorriso : UPDATE : Thank you for being patient. Working since 728 seconds.
> Writing to '/dev/sr0' com
==
samiel@darkstar:~$ isoimage=/home/samiel/debian-11.1.0-amd64-netinst.iso
samiel@darkstar:~$ xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed
$isoimage
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.
xorriso : NOTE :
Hi,
(No need to Cc: me, i am subscribed to the bug report 998718.
If you are subscribed too and don't want to be Cc:ed, then tell me.)
> thanx for your quick reply
That's because new udevadm said "XORRISO". I found the bug report by my
evening patrol with Google.
---
thanx for your quick reply
dmesg tell me:
=
[23315.697087] sr 5:0:0:0: [sr0] tag#16 FAILED Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[23315.697092] sr 5:0:0:0: [sr0] tag#16 CDB: Prevent/Allow Medium
Removal 1e 00 00 00
Hi,
i am upstream programmer of libburn, which might be in charge of
burning underneath Brasero. Regrettably i cannot interpret Brasero's
messages unless they come from libburn or libisofs. So i am not sure
whether i can help with fixing Brasero.
The statement by other software that no medium is
Package: Brasero
Version: 3.12.3-1
I work on Debian Testing (Bookworm) with Cinnamon, always kept up to
date. The problem I point out is related to the burning of ISO to CD-RW
using Brasero. I state that from the console using wodim I can both
erase CD-RW and burn an ISO. Instead, if I proceed
37 matches
Mail list logo
