[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: solaris cdrecord BH08LS20 drive BD-R problems


> > > JM20329 versus JM20336
> > Did it have positive effect on Solaris machine?
> Yes, only windows has a good driver for JM20336

Stunning. One would expect that USB is
standardized enough to plug any compliant device
into any compliant computer.
I could accept the need for a special driver if
it was about a computer side controller. But i
understand you exchanged the one on the drive
side of the cable.

Somehow that first USB-SATA bridge did not
really implement the USB usage model.


> So cdrecord will work after Jörg prepares his
> workaround for the LG drive firmware bug. :-D

Did you already try cdrecord with the new
bridge ?
Maybe the drive firmware is ok but had no chance
to prove this to cdrecord yet.


Although ... this here looks really a bit strange
> $ growisofs -Z /dev/scd0=image.iso -use-the-force-luke=spare:none
> /dev/scd0: "Current Write Speed" is 8.2x4390KBps.
> ...
> builtin_dd: 4270960*2KB out @ average 1.9x4390KBps

Obviously the drive announces much more speed
than 2x. Scrolling back to 9 Oct 2009,
dvd+rw-mdiainfo output:

> Mounted Media:        41h, BD-R SRM
> Current Write Speed:  8.0x4495=35964KB/s
> Write Speed #0:       8.0x4495=35964KB/s
> Write Speed #1:       6.0x4495=26973KB/s
> Write Speed #2:       4.0x4495=17982KB/s
> Write Speed #3:       2.0x4495=8991KB/s

"8.2x4390KBps" would rather be "KiB" than "KB"
so it is indeed the same as "8.0x4495=35964KB/s".

cdrecord -minfo told on 15 Oct:
> Manufacturer:     'RITEK'
> Media type:       'BR2'

Google finds me
It looks that the media are nominally 4x.
Right ?

Hard to say whether 
did not have the desired effect or the USB
bridge did not deliver enough bandwidth resp.
too much latency so that the drive decided to
slow down to 2x.

Clarifying experiments would be:
  growisofs without -use-the-force-luke=spare:none
  cdrskin (Linux only) which will surely not
          format BD-R automatically.
          E.g.: cdrskin -v dev=5,0,0 image.iso
          (derived from your cdrecord command as
           reported 14 Oct 2009)

Have a nice day :)


Reply to: