About DVD burner

satimis · 04-15-2006, 11:26 AM

Hi folks,

FC3

Just installed a DVD burner, Sony Dru-820A, replacing the CD-writer. However
$ cat /etc/fstab

Code:

...
....

/dev/hdd                /media/cdrom1           auto    pamconsole,exec,noauto,fscontext=system_u:object_r:removable_t,managed 0 0
/dev/hdc                /media/cdrecorder1      auto    pamconsole,exec,noauto,fscontext=system_u:object_r:removable_t,managed 0 0

It seems nothing chnaged.

Test-burned a DVD iso image of about 3.2G on a blank-new DVD+RW with K3b. It finished in less than 30 seconds. I suspected it did not burn. But it displayed "successful"

# mount /dev/hdc /media/cdrom

Code:

mount: you must specify the filesystem type

# mount /dev/hdd /media/cdrom1

Code:

mount: No medium found

Please advise what will be the correct procedure. TIA

B.R.
satimis

Lenard · 04-15-2006, 02:05 PM

What does the command 'cdrecord -scanbus' minus the single quotemarks show??

Which versions of k3b, the cdrtools and dvd+rw-tools are installed??

satimis · 04-15-2006, 07:19 PM

Hi Lenard,

Tks for your advice.

Quote:

What does the command 'cdrecord -scanbus' minus the single quotemarks show??

# cdrecord -scanbus

Code:

        1,0,0   100) 'SONY    ' 'DVD RW DRU-820A ' '1.0a' Removable CD-ROM
        1,1,0   101) 'MATSHITA' 'CD-ROM CR-588   ' 'LS15' Removable CD-ROM
.....
....

Quote:

Which versions of k3b, the cdrtools and dvd+rw-tools are installed??

# rpm -qa | grep k3b
k3b-0.11.14-2

I think dvd+rw-tools having been installed because there is an option for burning DVD ISO image there. How to check them with command line?

I used the same IDE cable which was for CDWriter. Would it be correct? Or need to change another IDE cable for ATA133 HD?

I tested formatting DVD+RW. It also finished at about 10 second.

TIA

B.R.
satimis

Lenard · 04-16-2006, 10:00 AM

OK, the Sony Dru-820A is known, this is good.....

k3b is old and should be updated (lots of bug fixes and other improvements), I suspect the cdr-tools and dvd+rw-tools (this should be updated) packages are also old and should be updated. So a quick check is to compare your tools to mine, and mine are for x86_64 and it is the version number that really matters;

Code:

$ rpm -qa --queryformat="%{n}-%{v}-%{r}.%{arch}.rpm\n" 'k3b' 'cdr*' 'cdp*' 'dvd+rw*' | sort

My output;

cdparanoia-alpha9.8-27.1.x86_64.rpm
cdparanoia-devel-alpha9.8-27.1.x86_64.rpm
cdparanoia-libs-alpha9.8-27.1.i386.rpm
cdparanoia-libs-alpha9.8-27.1.x86_64.rpm
cdrdao-1.2.1-1.1.x86_64.rpm
cdrecord-2.01.01.0.a03-3.x86_64.rpm
cdrecord-devel-2.01.01.0.a03-3.x86_64.rpm
dvd+rw-tools-6.1-6.2.1.x86_64.rpm
k3b-0.12.15-1.x86_64.rpm

Where to get the updated versions.......

You might want to grab the binary k3b-0.12.14 packages from the k3b-redhat site instead of building your own (also have the latest KDE rpms and other updates available);

http://kde-redhat.sourceforge.net/

The updated dvd+rw-tools package, this requires a little bit of work to install as an rpm package;

http://fy.chalmers.se/~appro/linux/DVD+RW/tools/?S=A

get dvd+rw-tools-6.1.tar.gz and place the file in /usr/src/redhat/SOURCES then build the binary using spec file following (place the file in /usr/src/redhat/SPCES);

rpmbuild -ba dvd+rw-tools.spec

The cdrtools packages, this also requires a small bit of work;

http://download.fedora.redhat.com/pu...lopment/SRPMS/

get cdrtools-2.01.01.0.a03-3.src.rpm and cdparanoia-alpha9.8-27.1.src.rpm then build the binaries by something like;

rpmbuild --rebuild --recompile cdrtools-2.01.01.0.a03-3.src.rpm

Do the same for the cdparanoia-alpha9.8-27.1.src.rpm package.

The cdrdao-1.2.1-1.src.rpm is optional (but nice to have) the same build option applies.

As promised the dvd+rw-tools.spec file, modified for redhat based systems from the orginal spec file included in the unpacked source;

Code:

Summary:	Toolchain to master DVD+RW/+R media
Name:		dvd+rw-tools
Version:	6.1
Release: 6.2.1
License:	GPL
Group:		Applications/Multimedia
Source:		http://fy.chalmers.se/~appro/linux/DVD+RW/tools/dvd+rw-tools-%{version}.tar.gz
#Source1: 	index.html
#Patch: 		dvd+rw-tools-5.17.4.8.6.manpatch
#Patch10: 	dvd+rw-tools-5.21.4.10.8-excl.patch
URL:		http://fy.chalmers.se/~appro/linux/DVD+RW/
Requires:	mkisofs >= 2.0
BuildRoot:	%{_tmppath}/%{name}-root
BuildRequires:	kernel-headers 

%description
Collection of tools to master DVD+RW/+R media. For further
information see http://fy.chalmers.se/~appro/linux/DVD+RW/.

%prep
%setup -q  -n %{name}-%{version}
#%patch -p1 -b .manpatch
#%patch10 -p1 -b .excl

%build
export CFLAGS="$RPM_OPT_FLAGS"
export CXXFLAGS="$RPM_OPT_FLAGS"

make
# cp %SOURCE1 index.html

%install
rm -rf %{buildroot}
%makeinstall

# mkdir -p %{buildroot}%{_prefix}/bin
mkdir -p %{buildroot}%{_docdir}/%{name}-%{version}-%{release}
# mkdir -p %{buildroot}%{_mandir}/man1

# cd %{_builddir}/%{name}-%{version}
# cp -a	growisofs dvd+rw-format dvd+rw-booktype	\
# 	%{buildroot}%{_prefix}/bin
#cp -a	index.html 				\
#	%{buildroot}%{_docdir}/%{name}-%{version}-%{release}
# cp -a growisofs.1* %{buildroot}%{_mandir}/man1

%clean
rm -rf %{buildroot}

%files
%defattr(-,root,root)
%{_prefix}/bin/*
%doc %{_docdir}/%{name}-%{version}-%{release}
%{_mandir}/man1/growisofs.1*

%changelog
* Fri Feb 24 2006 Andy Polyakov <appro@fy.chalmers.se>
- Initial packaging.

satimis · 04-16-2006, 10:36 AM

Hi Lenard,

Tks for your effort and detail advice.

The DVD Writer is not for this FC3 box. It is for a newly built AMD_64 box.

Please let me informing you the whole story. I tried couple days to install FC5_64 on the new AMD_64 box from the CDs download from Internet, encountering lot of problem and having burned sets of CDs. Finally I managed to get FC5_64 installed on the new box. It is now running. I want to make another round but this time prepared using the installing DVD instead. However I have FC5_64 DVD ISO image download on the FC3 box before. So I moved the DVD writer to the FC3 box temporarily only for burning the FC5_64 ISO image on DVD.

To make my work easiler, is there a simple way to tranfer the DVD ISO image from FC3 box to FC5 box via the NIC on both boxes? Because even I manage installing the DVD writer on the FC3. I have to move the writer back to FC5_64 box later. The FC5_64 box has an onboard NIC. I haven't setup its broadband connection yet.

Please advise. TIA

B.R.
satimis

satimis · 04-17-2006, 10:24 AM

Hi Lenard,

I got FC5_64 DVD ISO image burned successfully on DVD+RW running FC3. The DVD Writer needs a 80 wire IDE cable.

Sony DRU-820A did not come with an IDE cable. At time of purchase I asked the computer shop what IDE cable I needed. I'm going to replace the existing Sony CD Writer. The guy told me using the old IDE cable. At that time I could not recall the number of wire of the IDE cable. I asked him again whether I need an IDE cable used on ATA133/100 HD. He confirmed not necessary just retaining the old IDE cable.

B.R.
satimis

Lenard · 04-17-2006, 04:42 PM

Well I'm glad you got the image burned. Yes you do need an 80-wire IDE cable for most DVD writers, do not know why the guy at the computer shop did not know this. Most come with the cable unless it is from an OEM shipment.

To answer your question about transfers, it can be done by a crossover ethernet cable and setting static IP addresses on both systems or thru a hub or using a router with some open ethernet ports and dhcp could also have be used. Using ssh is one meathod to accomplish the transfer, read all about it here;

http://www.openssh.com/

satimis · 04-17-2006, 06:53 PM

Hi Lenard,

Tks for your advice and URL.

In the past I did lot of transferring data between computers using SSH via NIC and crossover cable. Unfortunately I forgot the steps. Hoping that I can find a crossover cable in store.

Quote:

... setting static IP addresses on both systems

Where to set the static IP address? What address shall I use?

TIA

B.R.
satimis

Lenard · 04-20-2006, 07:24 AM

Sorry, this thread seems to have been dropped by my radar ;(

Just use the 192.168.XXX.XXX static address range set each as a unique address, i.e. 192.168.1.1 and 192.168.1.2 and each as it's own gateway using system-config-network.

satimis · 04-24-2006, 05:33 AM

Quote:

Originally Posted by Lenard

Sorry, this thread seems to have been dropped by my radar ;(

Just use the 192.168.XXX.XXX static address range set each as a unique address, i.e. 192.168.1.1 and 192.168.1.2 and each as it's own gateway using system-config-network.

Noted with tks.

satimis