Can't burn BD-R with BD-R/BD-RE capable (?) drive. DVD+R: OK.

kaza · 04-13-2010, 05:36 PM

Hello,

I attempted to backup some directories tree onto a BD-R disk
and it seems not to be recognized while doing the same onto
a DVD+R disk worked OK. I'm running FC11, kernel: 2.6.29.4-167.hpfs.fc11.x86_64 (recompiled with HPFS
support) with a GNOME desktop. I attempted the
burn with "CD/DVD Creator", "Brasero Disk Burner" and "K3b". With
all 3 it seems like the BD-R media isn't recognized as valid, although,
at least in "K3b" case the "Media info" shows what looks like a correct
data:

Medium
|-Type: BD-R Sequential (SRM)
|-Capacity: 2715:25:17 min 23.3 GB
|-Rewritable: no
|-Appendable: no
|-Empty: yes
|-Sessions: 0
-Supported writing speeds: 18x (3324 KB/s)

The media is of "Verbatim" so I think it's OK.
I also attempted this on 2 disks out of the pack
of 10 with the same result. The LG burner had been
bought at the beginning of 2009. Are there ways
to download+update its firmware under LINUX or DOS
(I still keep a DOS partition for diving computer interface
which insists on talking directly to the metal)?
The devices listed:

Code:

...>\ls -l /dev | grep cd
lrwxrwxrwx. 1 root root           3 2010-04-03 16:46 cdrom -> sr0
lrwxrwxrwx. 1 root root           3 2010-04-03 16:46 cdrw -> sr0
lrwxrwxrwx. 1 root root           3 2010-04-03 16:46 scd0 -> sr0
crw-rw----+ 1 root cdrom    21,   0 2010-04-03 16:46 sg0
brw-rw----+ 1 root cdrom    11,   0 2010-04-03 16:46 sr0

When I start k3b, I get the following output dumped into the terminal:

Code:

...>k3b &
[1] 6314
...>kbuildsycoca running...
(K3bDevice::HalConnection) initializing HAL >= 0.5
Mapping udi /org/freedesktop/Hal/devices/storage_model_BD_RE__GGW_H20L to device /dev/sr0
/dev/sr0 resolved to /dev/sr0
/dev/sr0 is block device (0)
/dev/sr0 seems to be cdrom
bus: 0, id: 0, lun: 0
(K3bDevice::Device) /dev/sr0: init()
(K3bDevice::Device) /dev/sr0 feature: CD Mastering
(K3bDevice::Device) /dev/sr0 feature: CD Track At Once
(K3bDevice::Device) /dev/sr0 feature: CD-RW Media Write Support
(K3bDevice::Device) /dev/sr0 feature: DVD Read (MMC5)
(K3bDevice::Device) /dev/sr0 feature: DVD+R
(K3bDevice::Device) /dev/sr0 feature: DVD+RW
(K3bDevice::Device) /dev/sr0 feature: DVD+R Double Layer
(K3bDevice::Device) /dev/sr0 feature: BD Read
(K3bDevice::Device) /dev/sr0 feature: BD Write
(K3bDevice::Device) /dev/sr0 feature: DVD-R/-RW Write
(K3bDevice::Device) /dev/sr0 feature: Rigid Restricted Overwrite
(K3bDevice::Device) /dev/sr0 feature: Layer Jump Recording
(K3bDevice::Device) /dev/sr0 feature: HD-DVD Read
(K3bDevice::Device) /dev/sr0 unknown profile: 2
(K3bDevice::Device) /dev/sr0: dataLen: 60
(K3bDevice::Device) /dev/sr0: checking for TAO
(K3bDevice::Device) /dev/sr0: checking for SAO
(K3bDevice::Device) /dev/sr0: checking for SAO_R96P
(K3bDevice::Device) /dev/sr0: checking for SAO_R96R
(K3bDevice::Device) /dev/sr0: checking for RAW_R16
(K3bDevice::Device) /dev/sr0: checking for RAW_R96P
(K3bDevice::Device) /dev/sr0: checking for RAW_R96R
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/sr0: GET PERFORMANCE dataLen = 56
(K3bDevice::Device) /dev/sr0: GET PERFORMANCE successful with reported length: 52
(K3bDevice::Device) /dev/sr0:  Number of supported write speeds via GET PERFORMANCE: 3
(K3bDevice::Device) /dev/sr0 : 26973 KB/s
(K3bDevice::Device) /dev/sr0 : 17982 KB/s
(K3bDevice::Device) /dev/sr0 : 8991 KB/s
(K3bDevice::DeviceManager) setting current write speed of device /dev/sr0 to 3324
/dev/sr0 resolved to /dev/sr0
(K3bDevice::DeviceManager) dev /dev/sr0 already found
(K3bDevice::DeviceManager) found config entry for devicetype: HL-DT-ST BD-RE  GGW-H20L
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
Devices:
------------------------------
Blockdevice:    /dev/sr0
Generic device: 
Vendor:         HL-DT-ST
Description:    BD-RE  GGW-H20L
Version:        YL03
Write speed:    3324
Profiles:       DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, HD DVD-ROM, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE
Read Cap:       DVD-ROM, DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+RW Dual Layer, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, HD DVD-ROM, HD DVD-R, BD-ROM, BD-R, BD-RE
Write Cap:      DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-R, CD-RW, BD-R, BD-RE
Writing modes:  SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential Recording + POW
Reader aliases: /dev/sr0
------------------------------
DiskInfo:
Mediatype:       BD-R Sequential (SRM)
Current Profile: BD-R Sequential (SRM)
Disk state:      empty
Empty:           1
Rewritable:      0
Appendable:      0
Sessions:        0
Tracks:          0
Layers:          1
Capacity:        2715:25:17 (LBA 12219392) (25025314816 Bytes)
Remaining size:  2715:25:17 (LBA 12219392) (25025314816 Bytes)
Used Size:       00:00:00 (LBA 0) (0 Bytes)
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/sr0: GET PERFORMANCE dataLen = 56
(K3bDevice::Device) /dev/sr0: GET PERFORMANCE successful with reported length: 52
(K3bDevice::Device) /dev/sr0:  Number of supported write speeds via GET PERFORMANCE: 3
(K3bDevice::Device) /dev/sr0 : 26973 KB/s
(K3bDevice::Device) /dev/sr0 : 17982 KB/s
(K3bDevice::Device) /dev/sr0 : 8991 KB/s

What does the message "GET CONFIGURATION length det failed."
means? Is this a symptom for the problem of non-existant
"BD-R" write mode? The version of the "dvd+rw-tools":

Code:

...>rpm -qa | grep dvd+rw
dvd+rw-tools-7.1-3.fc11.x86_64

In "k3b", when I select Settings -> Configure -> Devices
There is the following info displayed under "Writer Drives":

Code:

HL-DT-ST BD-RE GGW-H20L

System device name: /dev/sr0 (0,0,0)
Interface type: Generic SCSI
Vendor: HL-DT-ST
Description: BD-RE GGW-H20L
Firmware: YL03
Wrires CD-R: yes
Writes CD-RW: yes
Reads DVD: yes
Writes DVD-R(W): yes
Writes DVD-R Dual Layer: yes
Writes DVD+R(W): yes
Writes DVD+R Dual Layer: yes
Buffer size: 2.0 MB
Cdrdao driver: auto
CD-Text capable: auto
Supports burnfree: yes
Write modes: SAO, TAO, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P,
RAW/R96R, Restricted Overwrite, Layer Jump,
Random Recording, Sequential Recording,
Sequential Recording +POW

I see that there is no BD-R/BD-RE write capability listed
despite the fact that the drive is correctly detected and it
(at least, in theory) is a BluRay drive. When the "k3b" started,
among other things dumped to the terminal were the lines:

(K3bDevice::Device) /dev/sr0 feature: BD Read
(K3bDevice::Device) /dev/sr0 feature: BD Write

What's the difference between the above 2 lines and what
k3b reports under "Writer drives": does the
"K3bDevice::Device" report what the device driver is
capable of while "Writer drives" reports the actual
hardware capabilities? Is it vice versa? It would be
very strange if a BluRay drive doesn't have the BD-R/BD-RE
capability that are even part of its model name.

I also attempted to start "k3b" as a root with the same results.
Any ideas as to what am I missing here?

Thanks in advance for any help,
kaza.

H_TeXMeX_H · 04-14-2010, 05:10 AM

I would try using growisofs:
http://fy.chalmers.se/~appro/linux/DVD+RW/Blu-ray/
http://www.stephencuppett.com/wordpr...-ray-in-linux/

kaza · 04-14-2010, 04:46 PM

Hi H_TeXMeX_H,
thanks for the help.

Just before I started following the procedure for
burning a BluRay with "growisofs" I looked at the HCL
section and found a review of the burner I have which
states that a firmware update to Y05 is needed (I currently
have Y03 version). I went to the LG site and needless to say,
the only way to upgrade the firmware was under windows
(and I don't have it on my PC). So, does it means I'm stuck
with the Y03 firmware (unless I'll take the burner out,
carry it to a friends PC where it hopefully will be
recognized, update the firmware and return the burner
to my PC)? Is there any hope for the firmware update app
to work inside a Windows virtualization under LINUX?
What virtual environment would you (or anyone else) suggest
(I'm entirely newbie in this regard)?

I'll attempt to write BD-R directly with "growisofs" with the current
firmware "Y03" and I'll see what happens...

TIA for any help,
kaza.

H_TeXMeX_H · 04-15-2010, 01:22 PM

I've successfully flashed firmware to my DVD-RW drive using wine (to make it region-free). But, know that it is NOT that safe, I can't imagine it's any worse that using Window$, tho. I don't recommend using a virtual machine, because many of them don't actually implement devices properly, and it probably won't be recognized and the update won't work. I know I tried updating a video driver under a VM and the driver couldn't see the card. But, you can also try that, there's a chance it'll work. You can definitely also connect it to another computer and update it, then bring it back, which may be the safest option. It's your choice, but there's always a small chance of bricking the drive, I've never managed to brick one there, even using wine.

I would try wine, but remember that it is not 100% safe to do so, something may go wrong, don't blame me if it does

Definitely do NOT try flashing BIOS using wine, although some people have done it successfully.

kaza · 04-17-2010, 02:35 AM

Quote:

Originally Posted by H_TeXMeX_H

I've successfully flashed firmware to my DVD-RW drive using wine (to make it region-free). But, know that it is NOT that safe, I can't imagine it's any worse that using Window$, tho. I don't recommend using a virtual machine, because many of them don't actually implement devices properly, and it probably won't be recognized and the update won't work. I know I tried updating a video driver under a VM and the driver couldn't see the card. But, you can also try that, there's a chance it'll work. You can definitely also connect it to another computer and update it, then bring it back, which may be the safest option. It's your choice, but there's always a small chance of bricking the drive, I've never managed to brick one there, even using wine.

I would try wine, but remember that it is not 100% safe to do so, something may go wrong, don't blame me if it does :) Definitely do NOT try flashing BIOS using wine, although some people have done it successfully.

Hi H_TeXMeX_H,
thanks for the help.

I'll start reading about wine (I haven't started yet doing
anything on regard of virtualization) and try updating the
firmware (which'll take a few good days at least - during a week
I work over 12 hours a day which doesn't leaves much time for my
home PC). I'm taking a note that it might not be 100% safe,
the responsibility for the results is solely on me.
When you write about not updating the BIOS, do you
mean the mainboard BIOS? My mainboard is ASUS M3A79-T Deluxe
which has an ability to flash the BIOS without booting any OS,
while still in the BIOS setup so there is no need for virtual
environment for this.

As for my attempt to directly burn the BD-R with "growisofs":

At first I attempted to burn the contents of a large directories tree
and got failues because of a VERY long file names used for some files,
together with a suggestion to use "-joliet-long" switch. I used it,
got fewer failures on long names but stil some names were too long
even for running with this switch. So, I decreased the tree (I'm
just doing a test) to only two directories which I knew contain
files of not too long names. The disk started spinning and progress
indication started to be displayed but at the end it failed with
"Input/Output error". Here's the output into the terminal:

Code:

growisofs -Z /dev/sr0 -R -J -joliet-long /home/user/ARCHIVE /home/user/rpmbuild


Using KERNE004.RPM;1 for  /home/user/rpmbuild/RPMS/x86_64/kernel-debuginfo-common-2.6.29.4-167.hpfs.fc11.x86_64.rpm (kernel-debug-2.6.29.4-167.hpfs.fc11.x86_64.rpm)
/dev/sr0: pre-formatting blank BD-R for 24.8GB...
/dev/sr0: "Current Write Speed" is 6.1x4390KBps.
  0.63% done, estimate finish Thu Apr 15 01:56:17 2010
  0.79% done, estimate finish Thu Apr 15 01:40:29 2010
.
.
.
 99.69% done, estimate finish Thu Apr 15 00:24:22 2010
 99.85% done, estimate finish Thu Apr 15 00:24:22 2010
Total translation table size: 0
Total rockridge attributes bytes: 8040676
Total directory bytes: 18393088
Path table size(bytes): 64970
Max brk space used 4d86000
3159794 extents written (6171 MB)
builtin_dd: 3159808*2KB out @ average 0.8x4390KBps
/dev/sr0: flushing cache
/dev/sr0: closing track
/dev/sr0: closing session
:-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error

After the burn, I can see the disk and I can see files and directories
on it but:

1) It seems like the contents of "ARCHIVE" and "rpmbuild" became
merged into a root directory of the burned disk. I remember that
when I was dealing with long file names errors, I saw warnings
about "merging" and that "growisofa is not a tar" (or something
like this". I think I have to look better at the avaliable
switches to preserve the tree "as is".

2) In some of the directories on a burned disk which are empty
on the original disk I found some files (incomplete) that
clearly shouldn't be there. So it seems the "Input/Output error"
is real - the data hasn't been preserved as it should be.

I think I should proceed with updating the firmware (after
reading about and installing wine), after that I'll repeat
the burn experiment.

TIA for any ideas/suggestions/etc.,
kaza.

H_TeXMeX_H · 04-17-2010, 09:11 AM

Try the '-graft-points' option, this should get rid of issues with directory layout.

It looks like it burned properly, but failed to close the session, which is a bit strange, not sure why that would be. Maybe see:
http://www.mail-archive.com/cdwrite@.../msg13071.html
http://osdir.com/ml/cdwrite@other.de.../msg00013.html
http://club.myce.com/f143/cant-close...-s525u-308505/
http://www.mail-archive.com/cdwrite@.../msg13227.html

kaza · 04-18-2010, 04:33 PM

Hi H_TeXMeX_H,
thanks for the help.

I've read the "readme.txt" bundled with the firmware
updater of the BluRay drive and it states that the firmware
update Y05 has the following changes:

------------------
Version History
------------------
YL05
- Write strategy improvement for new BD-R and BD-RE Media
(BD-R : 24kinds, BD-RE : 4kinds)

YL04
- Addition of write strategy

Since I had a suspicion that a burn resulted in a wrong data
being written and the doc states that write strategy changes
were done between firmware versions Y03 (current) and Y05,
I think I should first update the firmware and only after that
resume burn attempts. So, now the problem is: how to
update the firmware under LINUX (I don't have Windows on my PC).
I installed "wine" and was able to start the "GGWH20L_YL05.exe"
app. At first the window opened with an empty drive name
(and the doc warns against attempting to update firmware
if the drive isn't detected, although I'm not sure it would
even start attempting if it sees no drive). After some thinking
I realized that I did it without any disk in the drive, therefore
the drive is unmounted. So I inserted the previously burned disk,
waited until the process of its recognition and mounting complete,
started again "wine GGWH20L_YL05.exe" and this time I had the
drive detected and I thought it'll be easy from this point.
But I was wrong: when I clicked the "update" button, I've got
a prompt "remove disk from the drive". Needless to say, doing so
(only by typing "eject", pressing the button on the drive does
nothing) reverted to the state of unrecognized drive. "Catch 22"...
I did some searching, didn't find any description of a problem
close to mine but found many references that "wine" can't
access the hardware directly, thus it's impossible to update
firmware under it.

So, what now: am I really stuck with the only option of
dismantling the drive and taking it to a friend with Windows
to upgrade the firmware in his PC?

TIA for any ideas,
kaza.

H_TeXMeX_H · 04-19-2010, 06:59 AM

With wine, there is a chance it won't detect the drive. Run 'winecfg' and click the autodetect drives button in one of the tabs. Try wine again, if it still doesn't detect it, then you have to use something else.

So you can also try a VM (with likely the same result as wine), but the safest thing is to use a Window$ computer, so take it out and connect it to another computer, then bring it back.

kaza · 04-19-2010, 08:54 AM

Hi H_TeXMeX_H,
thanks for the help.

Well, I attempted to change things with "winecfg" but nothing changed.
That means, I'll have to find when one of my friends can
spare some time during some weekend to dismantle his PC for me to
update the firmware. That is, unless someone will have an idea
how to "fool" the firmware update program into thinking there is no
disk in the drive while there is...

TIA for any ideas,
kaza.

H_TeXMeX_H · 04-19-2010, 12:55 PM

Oh, just one more note, you did run wine as root, right ? You should run it as root if you want any chance of detecting the drive, much less flashing the drive.

Note also that running wine as root in and of itself constitutes a risky act, and is dangerous.

kaza · 04-21-2010, 03:19 PM

Well, I attempted to run "wine" as root at some point but got the error:

Code:

<root@localhost.localdomain>.../download>wine GGWH20L_YL05.exe
wine: '/root/.wine' is a 32-bit prefix, it cannot be used with wow64 Wine.

Now I realize I should've solve this problem before attempting
to run "wine".

Thanks,
kaza.

H_TeXMeX_H · 04-21-2010, 03:36 PM

Wait a minute, do you have 64-bit wine ? If so, do NOT attempt to run the firmware update. Use 32-bit wine or use another computer.

kaza · 04-22-2010, 12:05 PM

Quote:

Originally Posted by H_TeXMeX_H

Wait a minute, do you have 64-bit wine ? If so, do NOT attempt to run the firmware update. Use 32-bit wine or use another computer.

Thanks for the advice.
I'll try finding a Windows PC to update the firmware.

I wasn't aware that wine is installed differently
for the "root" and for a normal user.

Out of curiosity:

1) What would happen when attempting to update firmware
under 64-bit wine?

2) I looked both in /root/.wine and in ~user/.wine to see if there is
any hint to 32 or 64 bitness but didn't see anything, at least
not anything obvious. Where should I look for this info?

3) Where can I get more info about the differences between 32 and
64 bit wine and other wine details?

TIA,
kaza.

H_TeXMeX_H · 04-22-2010, 12:25 PM

1) Most likely it won't work, but it can be more complicated, in which case it may do harm.

2) Not sure, see below.

3)
http://wiki.winehq.org/Wine64ForPackagers
http://wiki.winehq.org/Wine64

kaza · 05-07-2010, 02:43 PM

Hello again,

It took me some time to upgrade the drive firmware from Y03 to Y05 in another PC
(with Windows). After re-installing the drive into my PC I started the "k3b" - and
nothing changed: just as before, the BD-R empty media got detected but the list
of capabilities goes only as high as DVD-R/DVD-RW, no BD-R. And using a command
line to directly call the "growisofs" resulted in almost the same output:

Code:

growisofs -Z /dev/sr0 -R -J -joliet-long -graft-points -gui -l -exclude-list /home/user/backup_files/exclude_list /home/user
Executing 'mkisofs -R -J -joliet-long -graft-points -gui -l -exclude-list /home/user/backup_files/exclude_list /home/user | builtin_dd of=/dev/sr0 obs=32k seek=0'
I: -input-charset not specified, using utf-8 (detected in locale settings)
Using OFFICE000 for  /office (OFFICE)
Using FLOWPLAYER_COMMERCIAL_3_000.SWF for  ./rr_moved/flowplayer.commercial-3.1.1.swf (flowplayer.commercial-3.1.1.swf)
Using FLOWPLAYER_COMMERCIAL_3_001.SWF for  ./rr_moved/flowplayer.commercial-3.1.1.swf (flowplayer.commercial-3.1.1.swf)
Using STATUSBAR000 for  ./rr_moved/statusbar (statusbar)
.
.
.
Using ET_EXPANDED_00M.EVOLUTION_MAIL_;1 for  /home/user/.evolution/mail/config/et-expanded-mbox:_home_user_.evolution_mail_local_1_Uri (et-expanded-mbox:_home_user_.evolution_mail_local_Outbox)
/dev/sr0: pre-formatting blank BD-R for 24.8GB...
/dev/sr0: "Current Write Speed" is 6.1x4390KBps.
  0.34% done, estimate finish Fri May  7 20:31:50 2010
  0.35% done, estimate finish Fri May  7 20:26:47 2010
.
.
.
 99.99% done, estimate finish Fri May  7 17:34:44 2010
 99.99% done, estimate finish Fri May  7 17:34:44 2010
Total translation table size: 0
Total rockridge attributes bytes: 11199068
Total directory bytes: 26284032
Path table size(bytes): 99086
Max brk space used 6778000
6404847 extents written (12509 MB)
builtin_dd: 6404848*2KB out @ average 1.0x4390KBps
/dev/sr0: flushing cache
/dev/sr0: closing track
/dev/sr0: closing session
:-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error

After the burning, the directories tree on the disk resembles the original
one and few randomly selected files seems to be OK, although I haven't make
a full compare of all data files yet. When I started "k3b" (with the previously
burned BD-R disk in the drive) I've got what looks like the same output
as before upgrading the firmware:

Code:

k3b
kbuildsycoca running...
(K3bDevice::HalConnection) initializing HAL >= 0.5
Mapping udi /org/freedesktop/Hal/devices/storage_model_BD_RE__GGW_H20L to device /dev/sr0
/dev/sr0 resolved to /dev/sr0
/dev/sr0 is block device (0)
/dev/sr0 seems to be cdrom
bus: 0, id: 0, lun: 0
(K3bDevice::Device) /dev/sr0: init()
(K3bDevice::Device) /dev/sr0 feature: CD Mastering
(K3bDevice::Device) /dev/sr0 feature: CD Track At Once
(K3bDevice::Device) /dev/sr0 feature: CD-RW Media Write Support
(K3bDevice::Device) /dev/sr0 feature: DVD Read (MMC5)
(K3bDevice::Device) /dev/sr0 feature: DVD+R
(K3bDevice::Device) /dev/sr0 feature: DVD+RW
(K3bDevice::Device) /dev/sr0 feature: DVD+R Double Layer
(K3bDevice::Device) /dev/sr0 feature: BD Read
(K3bDevice::Device) /dev/sr0 feature: BD Write
(K3bDevice::Device) /dev/sr0 feature: DVD-R/-RW Write
(K3bDevice::Device) /dev/sr0 feature: Rigid Restricted Overwrite
(K3bDevice::Device) /dev/sr0 feature: Layer Jump Recording
(K3bDevice::Device) /dev/sr0 feature: HD-DVD Read
(K3bDevice::Device) /dev/sr0 unknown profile: 2
(K3bDevice::Device) /dev/sr0: dataLen: 60
(K3bDevice::Device) /dev/sr0: checking for TAO
(K3bDevice::Device) /dev/sr0: checking for SAO
(K3bDevice::Device) /dev/sr0: checking for SAO_R96P
(K3bDevice::Device) /dev/sr0: checking for SAO_R96R
(K3bDevice::Device) /dev/sr0: checking for RAW_R16
(K3bDevice::Device) /dev/sr0: checking for RAW_R96P
(K3bDevice::Device) /dev/sr0: checking for RAW_R96R
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/sr0: GET PERFORMANCE dataLen = 56
(K3bDevice::Device) /dev/sr0: GET PERFORMANCE successful with reported length: 52
(K3bDevice::Device) /dev/sr0:  Number of supported write speeds via GET PERFORMANCE: 3
(K3bDevice::Device) /dev/sr0 : 26973 KB/s
(K3bDevice::Device) /dev/sr0 : 17982 KB/s
(K3bDevice::Device) /dev/sr0 : 8991 KB/s
(K3bDevice::DeviceManager) setting current write speed of device /dev/sr0 to 3324
/dev/sr0 resolved to /dev/sr0
(K3bDevice::DeviceManager) dev /dev/sr0 already found
(K3bDevice::DeviceManager) found config entry for devicetype: HL-DT-ST BD-RE  GGW-H20L
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
Devices:
------------------------------
Blockdevice:    /dev/sr0
Generic device: 
Vendor:         HL-DT-ST
Description:    BD-RE  GGW-H20L
Version:        YL05
Write speed:    3324
Profiles:       DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, HD DVD-ROM, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE
Read Cap:       DVD-ROM, DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+RW Dual Layer, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, HD DVD-ROM, HD DVD-R, BD-ROM, BD-R, BD-RE
Write Cap:      DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-R, CD-RW, BD-R, BD-RE
Writing modes:  SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential Recording + POW
Reader aliases: /dev/sr0
------------------------------
DiskInfo:
Mediatype:       BD-R Sequential Pseudo Overwrite (SRM+POW)
Current Profile: BD-R Sequential Pseudo Overwrite (SRM+POW)
Disk state:      incomplete
Empty:           0
Rewritable:      0
Appendable:      1
Sessions:        0
Tracks:          1
Layers:          1
Capacity:        2686:17:45 (LBA 12088320) (24756879360 Bytes)
Remaining size:  1262:56:32 (LBA 5683232) (11639259136 Bytes)
Used Size:       1423:21:13 (LBA 6405088) (13117620224 Bytes)
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/sr0: GET CONFIGURATION length det failed.
(K3bDevice::Device) /dev/sr0: GET PERFORMANCE dataLen = 56
(K3bDevice::Device) /dev/sr0: GET PERFORMANCE successful with reported length: 52
(K3bDevice::Device) /dev/sr0:  Number of supported write speeds via GET PERFORMANCE: 3
(K3bDevice::Device) /dev/sr0 : 26973 KB/s
(K3bDevice::Device) /dev/sr0 : 17982 KB/s
(K3bDevice::Device) /dev/sr0 : 8991 KB/s

So it seems I'm back at square 1...

Let's concentrate on the first occurrence of problems in each of the
two ways I attempted to make the burn:

1) What's the meaning of the error mesage at the end of "growisofs":

:-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error

What is "CDB"?

2) What's the meaning of the error while starting the "k3b":

(K3bDevice:

evice) /dev/sr0: GET CONFIGURATION length det failed.

It almost looks (to me, at least, a VLSI engineer) like a device driver
made a series of successful reads from the device registers and then
when it made a read from a register where it expected to find a length
of some configuration record it got an unexpected value, which means:
the drive behaves not according to "spec" which the device driver expects.
How can I debug this? Where is the code intimately dealing with the
hardware registers so I can look at the sources? Is it the "dvd+rw-tools"?

rpm -qa | grep dvd\+rw
dvd+rw-tools-7.1-3.fc11.x86_64

Is there anywhere a documentation of the registers programming model
of that drive (LG "GGW-H20L" model)?

3) Had anyone successfully burned BD-R media using k3b on this drive?
Had anyone successfully burned BD-R/BD-RE media on drive of any other
manufacturer/model (in case I'll decide I want to get rid of that drive
and to replace it with something else)?

4) Does the kernel version is relevant for my problem? I'm currently
using "2.6.29.4-167.hpfs.fc11.x86_64". I downloaded and installed
"2.6.30.10-105.2.23.fc11.x86_64" but I haven't yet recompiled it
with HPFS support so I'm still booting the "2.6.29.4-167.hpfs.fc11.x86_64".

5) Are there any BIOS settings that might be relevant to this problem? The drive
is connected to the first SATA port and I remember there are BIOS settings
for SATA ports behaving like regular IDE or some other setting (forgot).

Thanks in advance for any ideas,
kaza.