[Libburn] lite-on 52327s

[Tiago Cogumbreiro]

A Seg, 2004-01-12 =E0s 21:37, Derek Foreman escreveu:
> On Mon, 12 Jan 2004, Tiago Cogumbreiro wrote:
>=20
> > A Seg, 2004-01-12 =E0s 18:26, Derek Foreman escreveu:
> > > If you have one of these drives, do _NOT_ use it in conjunction wit=
h
> > > libburn.
> > >
> > > I just lost my second one in 3 days.
> > >
> > > I honestly have no reason to believe libburn is doing anything that=
 is
> > > damaging this hardware.  But after 2 dead drives, I'm becoming quit=
e
> > > paranoid.
> > >
> > > I will post a follow up as soon as I have more information.
> > >
> > Ack! This is strange news... Is this in anyway strangely connected to
> > the Mandrake problem with LG drives? Maybe they both use the same bro=
ken
> > hardware...
>=20
> The LG problem was truly bizarre. LG decided to use the flush
> cache command opcode for their own vendor unique firmware upload comman=
d
> on some of their cd readers.
>=20
> The mandrake kernel sent flush cache to all devices on shut down (to ge=
t
> the hard drives to commit cache to the disk), and the LG cd readers
> destroyed their firmware.
>=20
> Since all burns end with a flush cache command, lite-on better not be
> using it for firmware uploads :)
>=20
> Also, after the drive failed, I tried re-uploading the latest firmware
> from windows xp, and it succeeded with no change in operation.
>=20
> I'm quite puzzled by this.  The last thing I did with the latest drive =
was
> read a cd I'd burnt with libburn.  Everything seemed fine.  I shut down
> the machine, booted up this morning, and it didn't recognize any discs =
at
> all.
>=20
> The first one died while I was blanking with libburn when it still had =
the
> "flood the device with test unit ready commands" bug.  Which, while
> stupid, really shouldn't damage hardware.
Bug? I implemented that part :D=20
That's the way to get the drive's progress. It's on the mmc specs... oh
well... I just check the cvs and it still has that part, at least the
public one... this will of course mean no blanking progress meter
>=20
> It really seems impossible that libburn could be responsible, but I hav=
e a
> second dead drive here.
>=20
> I've sent an email to lite-on technical support.  hopefully they'll get
> back to me before I have to return this drive to the store (really crap=
py
> return policy... I have 4 days left to take it back.)
>=20
> _______________________________________________
> Libburn mailing list
> Libburn@pdx.freedesktop.org
> http://pdx.freedesktop.org/cgi-bin/mailman/listinfo/libburn