Red Hat Bugzilla – Bug 164523
Add Blu Ray cdrom media support
Last modified: 2011-02-02 09:52:18 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc3 Firefox/1.0.6
Description of problem:
The new Blu-ray cdrom 8gb media and Cdrom 8gb drives are not supported.
When I put a Blu-ray 8gb media and tried to use k3b, I got the message that
the media was not supported. Also, when I was setting up to make DVD, k3b displayed of availble was 4gb and not 8gb as supported by the Blu-Ray DVD and Blu-Ray media.
When making a DVD the program worked perfectly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Get a Blu-ray DVD writer with media
2.put a Blu-ray media into the CD writer
3.Try to burn an 8gb cdrom
Actual Results: K3b reported bad media and an incorrect size.
Expected Results: The cdtools should recognize the 8gb size and the Blu-ray media.
these are new in the market place, so I am not supprised this is not in the
cd tools as of yet. But, they will need to be supported.
cdrtools has nearly full support for bluray, so k3b should be able to burn
it(but I don't think it does). So how well does fedora support bluray as of now?
we use cdrkit ... no cdrtools anymore because of License issues.
changed component re comment #2
Please do not use cdrkit because of it's license issues.
cdrkit is in conflict with GPL and Copyright and cannot
be legally distributed.
The original software has no license issues, this has been
aproved by the Sun Legal depatement.
this bug is open since 2005 ?
before i spend 200+ eur,
does fedora support Blu-Ray RE 25/50GB or not ?
if yes, how ?
cdrecord or dvdrecord or growisofs or ... ?
$ rpm -qf `which growisofs`
$ rpm -qf `which cdrecord`
$ head /usr/share/doc/wodim-1.1.8/COPYING
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
cdrkit, like the programs from which it was derived, is distributed as free software under the terms of the GNU GPL version 2. (Note, this is not "version 2 or later" as you see in many software projects.)
apropos, does fedora support lightscribe ?
The original cdrtools include BluRay support since July 2007.
You would need to tell RedHat to upgrade to the free original software.
dvd+rw-tools has bluray support
... as of version 7.0 dvd+rw-tools support even Blu-ray Disc:-)
i had no problems with cdrecord between 2001 - ?2005/2006?
then my really bad cdrecord(clone) experiences started and i switched to growisofs and went never back.
could you compare once again both packages or
could it be possible to include both packages and change it with eg.
# alternatives --set cdrecord
$ rpm -qf `which cdrecord` `which wodim`
$ wodim --version
Copyright (C) 2006 Cdrkit suite contributors
Based on works from Joerg Schilling, Copyright (C) 1995-2006, J. Schilling
$ cdrecord --version
Cdrecord-Clone 2.01 (cpu-pc-linux-gnu) Copyright (C) 1995-2004 J�rg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla
Note: The author of cdrecord should not be bothered with problems in this version.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
There are many discussions about the license problem (e.g. bug 507108) and I can't say anything new.
For your question about Lightscribe support in Fedora: there is no package supporting Lightscribe in official release, as far as I know. But there are several projects, that are not part of official release, and they are working properly in Fedora (e.g. http://fedorasolved.org/multimedia-solutions/lightscribe-for-linux).
Because the main question about Blu-Ray support is already answered (comment #7) and I think there is nothing else to discuss, I'm closing this as not a bug.