[Debburn-devel] LG CH08LS10 not burning CDs
surfed
god at youhavechoice.com
Thu Jan 28 18:12:44 UTC 2010
Also i have read in one forum that switching from ahci to ide in sata mode
solved it for one drive, cant check on my box as nothing will boot if i do.
All Disks tested where CD-R and DVD-R and DVD-DL in TAO. I even tried Nero4
for linux with no luck.
Sascha
On Thu, Jan 28, 2010 at 1:40 AM, Thomas Schmitt <scdbackup at gmx.net> wrote:
> Hi,
>
> > I had a similar problem with the Dell XPS M1340. I had recently
> > updated the firmware for my DVDRW to the latest version (support for
> > Win 7) , I couldn't burn anything in Arch (K3B, Nero, CLI), but could
> > in Windows 7 (Nero). I downgraded it back to vA108 and it works
> > again.
>
> Frightening.
> This sounds like LG would implant bugs to fight
> bugs in Windows.
>
>
> > http://bbs.archlinux.org/viewtopic.php?id=86595
> > In xfburn I got these error:
> > Failure: SCSI error on write(272,16): [5 21 02] Invalid address
>
> This answers the question whether libburn is
> affected, too. :(
>
> Was that a CD ? Write mode TAO ?
> Afaik, xfurn has a choice button TAO/SAO.
>
>
> > http://ubuntuforums.org/showthread.php?p=8728991
> > BraseroWodim stderr: CDB: 2A 00 FF FF FF 6A 00 00 1F 00
> > ...
> > BraseroWodim stderr: Sense Code: 0x30 Qual 0x05
> > (cannot write medium - incompatible format) Fru 0x0
>
> The media is not ready to get written at address
> -150, which is the normal start point for SAO.
> That would mean the CUE sheet of the SAO session
> did not get into effect ... for some reason.
>
> Richard reported about TAO failure, too.
> TAO needs no other preparation than sending a
> mode page 5 with write type TAO.
>
>
> What media are affected ? Anything else but
> CD-R , CD-RW, DVD-R , DVD-RW ?
>
> ------------------------------------------------
>
> It is hard to imagine how this could get broken
> by leaning towards some Windows peculiarities.
>
> Call me stubborn, but for now i still believe
> in a second process reading from the drive.
> The effects of the firmware changes would in my
> theory be caused by different vulnerability for
> disturbance.
>
> The single-user mode tests would prove or
> falsify my theory. Same kernel, same burn
> program, but no uncoordinated processes.
>
>
> > A common pattern i find is that a lot of these are
> > Dell laptops.
>
> One point against my theory.
> The host hardware should have few influence.
>
>
> > And i am not saying all LG drives have this issue, not at all, most
> > work great.
>
> I will probably return a mad Samsung SH-S223C
> and might possibly get an LG for it.
> (SH-S223C rev SB02, DVD-RW with multi-session
> broken. Not known yet whether systematic or
> individual. Elsewise a fine drive.)
>
> But if i tell the dealer that the LG is even more
> broken than the Samsung, then he will not believe
> me anything any more.
>
> There is a surprising wealth of unpleasant drive
> behavior recently. Pioneer, LG, Samsung, no brand
> seems safe.
>
>
> > I had recently updated the firmware for my DVDRW
> > to the latest version (support for Win 7)
>
> Is there any info why Windows 7 would need a
> firmware upgrade of the drive ?
>
> The MMC usage model is much like client-server.
> The computer is the client and the drive is the
> server. Both communicate via commands from SCSI
> sub-specs MMC, SPC, SBC (regardless whether ATA,
> USB, SCSI, SATA).
> So the normal thing is (was ?) that both sides
> obey the specs and all works well.
>
> We open sourcers need to find out what's going
> on there.
>
>
> Have a nice day :)
>
> Thomas
>
>
> _______________________________________________
> Debburn-devel mailing list
> Debburn-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/debburn-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debburn-devel/attachments/20100128/a8972bc5/attachment.htm>
More information about the Debburn-devel
mailing list