CD burning problem with FC3

Place to discuss Fedora and/or Red Hat

CD burning problem with FC3

Postby dishawjp » Fri Dec 17, 2004 8:30 pm

Hi All,

Here I am, back with another problem. I can't seem to burn CD's with FC3. I've tried the default Gnome burner, k3b and xcdroast, all with no luck. I was beginning to think that it was a hardware problem, but when I booted back to FC2, I was able to burn OK. Running cdrecord --scanbus gives me the following:
Code: Select all
[dishawjp@eunix ~]$ cdrecord --scanbus
Cdrecord-Clone 2.01-dvd (i686-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.
scsidev: 'ATA'
devname: 'ATA'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c        1.83 04/05/20 Copyright 1997 J. Schilling').
scsibus0:
        0,0,0     0) 'ATAPI   ' 'DVD-ROM 16X     ' '582F' Removable CD-ROM
        0,1,0     1) 'MSI     ' 'CD-RW MS-8348   ' '120D' Removable CD-ROM
        0,2,0     2) *
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) *
        0,6,0     6) *
        0,7,0     7) *
[dishawjp@eunix ~]$

Which would seem to indicate that cdrecord can find the device. But issuing the following command for cdrecord gives me the following output:
Code: Select all
[dishawjp@eunix ~]$ cdrecord -v -eject speed=8 /media/cdrecorder /home/dishawjp/docs/
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01-dvd (i686-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.
TOC Type: 1 = CD-ROM
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c        1.83 04/05/20 Copyright 1997 J. Schilling').
Driveropts: 'burnfree'
SCSI buffer size: 64512
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 1
Vendor_info    : 'ATAPI   '
Identifikation : 'DVD-ROM 16X     '
Revision       : '582F'
Device seems to be: Generic mmc2 DVD-ROM.
Current: 0x0000
Profile: 0x0010
Profile: 0x0008
cdrecord: Sorry, no CD/DVD-Recorder or unsupported CD/DVD-Recorder found on this target.
[dishawjp@eunix ~]$ cdrecord -v -eject speed=8 /dev/cdrecorder /home/dishawjp/pics/other/
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01-dvd (i686-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.
TOC Type: 1 = CD-ROM
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c        1.83 04/05/20 Copyright 1997 J. Schilling').
Driveropts: 'burnfree'
SCSI buffer size: 64512
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 1
Vendor_info    : 'ATAPI   '
Identifikation : 'DVD-ROM 16X     '
Revision       : '582F'
Device seems to be: Generic mmc2 DVD-ROM.
Current: 0x0000
Profile: 0x0010
Profile: 0x0008
cdrecord: Sorry, no CD/DVD-Recorder or unsupported CD/DVD-Recorder found on this target.

I tried both /dev/cdrecorder and /media/cdrecorder and even /dev/hdb as the device in the command with the same results. It appears that the major problem is that it's not finding my cdburner, just my DVD drive. Both drives are ATAPI

Any thoughts on how to get this going? It's not too important for now, but I will want to be able to do backups sometime.

Oh, in case it helps, my fstab is below, it will probably wrap, but maybe give someone a clue anyway:
Code: Select all
@eunix ~]$ more /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
/dev/hdd3               swap                    swap    defaults        0 0
/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0
/dev/hdb                /media/cdrecorder       auto    pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
/dev/hda                /media/cdrom            auto    pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
/dev/fd0                /media/floppy           auto    pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
[dishawjp@eunix ~]$

As always, any help greatly appreciated.

Jim
dishawjp
administrator
administrator
 
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY

Postby Void Main » Fri Dec 17, 2004 8:59 pm

I am confused by your command line. Are you trying to burn an ISO? You give it two directory names in your cdrecord command line and no device name and you can't burn a directory directly with cdrecord (that I am aware of). If you want to burn a directory you have to add it to an ISO first via mkisofs. It appears to be defaulting to "/dev/cdrom" for the device which is probably listed in your /etc/cdrecord.conf as the default. If you want to use a different device you would use the "dev=/dev/otherdevice" which you didn't give in your command line.

I am also confused about the way you have your drives arranged. Are you running an IDE hard drive? It looks like you have your CD and DVD drives as master and slave on ide0 and your hard drive as slave on ide1. Normally you put the hard drive first (hda) and then your CD either as a slave to it or as a master on the secondary ide. You can find out what device your CD and DVD are on in either dmesg output or /var/log/messages*:

# dmesg | grep "CD"

or

# grep " hd." /var/log/messages*
User avatar
Void Main
Site Admin
Site Admin
 
Posts: 5705
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA

Postby Ice9 » Sat Dec 18, 2004 3:26 am

Which kernel are you running?
This has probably nothing to do with your problem but when I was running kernel 2.6.8 I couldn't burn anything.
A post on the k3b mailing list said something about known bugs in 2.6.8, so I upgraded to 2.6.9 and all was fine again.
Ice9
guru
guru
 
Posts: 577
Joined: Thu Jan 09, 2003 12:40 am
Location: Belgium

Postby Void Main » Sat Dec 18, 2004 6:29 am

Ice9 wrote:Which kernel are you running?
This has probably nothing to do with your problem but when I was running kernel 2.6.8 I couldn't burn anything.
A post on the k3b mailing list said something about known bugs in 2.6.8, so I upgraded to 2.6.9 and all was fine again.


The eariliest kernel that comes with FC3 is 2.6.9-1.667. I have never had a problem with any FC3 kernels. It's just not going to work with the command line he used in his quote.
User avatar
Void Main
Site Admin
Site Admin
 
Posts: 5705
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA

Postby Ice9 » Sat Dec 18, 2004 6:42 am

The eariliest kernel that comes with FC3 is 2.6.9-1.667

Sorry, FC3 didn't las on my drive long enough for me to remember the kernel version. :)
Ice9
guru
guru
 
Posts: 577
Joined: Thu Jan 09, 2003 12:40 am
Location: Belgium

Postby dishawjp » Sat Dec 18, 2004 7:17 am

Voidmain and Ice9,

Thanks. One problem is that I was tired last night and did screw up the command line. After failing to burn in k3b, xcdroast, and the gnome nautilus burner thing, I was just trying to get a command line to show errors. No matter what I do, it just hangs on "preparing to burn."

Using a proper command for cdrecord, I get:
Code: Select all
[dishawjp@eunix ~]$ cdrecord -v -eject speed=8 -dev=/dev/cdwriter /home/dishawjp/docs
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01-dvd (i686-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.
TOC Type: 1 = CD-ROM
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/cdwriter'
devname: '/dev/cdwriter'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c        1.83 04/05/20 Copyright 1997 J. Schilling').
SCSI buffer size: 64512
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 1
Vendor_info    : 'MSI     '
Identifikation : 'CD-RW MS-8348   '
Revision       : '120D'
Device seems to be: Generic mmc CD-RW.
Current: 0x0009
Profile: 0x0008
Profile: 0x0009 (current)
Profile: 0x000A
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-2 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1806336 = 1764 KB

and it just hangs.

The kernel should not be the issue, but it is 2.6.9-1.667.

Thanks for the help and sorry I sent you chasing a bad lead.

Jim
dishawjp
administrator
administrator
 
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY

Postby Void Main » Sat Dec 18, 2004 7:46 am

Although nothing you have done should cause cdrecord to hang, I am still confused as to what "/home/dishawjp/docs" is. By the name I would assume that it is a directory and not an ISO. I am curious if you tried becoming root (su -) and running it (it appears that you are not root now). In addition to that I am curious if you have tried running it without the "speed=8" and "-eject" options? Again, that *should not* cause it to hang, just trying to see if they have any effect.
User avatar
Void Main
Site Admin
Site Admin
 
Posts: 5705
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA

Postby dishawjp » Sat Dec 18, 2004 10:25 am

Voidmain,

It is a directory. Actually a directory with subdirectories each containing documents which should be backed up. For the moment, I'm just mounting my FC2 drive (hdc2) and copying them to there.

In the past I have always been able to get the GUI programs (xcdroast, k3b or more recently nautilus) to handle this for me and have only used cdrecord to burn downloaded .iso images. I guess I wrongly assumed that cdrecord would work similarly to the GUI programs based on it.

Do I need to make a .iso file containing those directories and their contents first? If so, I know the that the command to do this is mkisofs. I just finished reading through the man pages and am a bit confused. Would the command to do this be:

mksiofs -pathspec /home/dishawjp/docs -allow-lowercase backup.iso

to get a .iso file containing the subdirectories and their contents converted file named backup.iso?

I still don't think that this is the *cause* of my CD burning problem, but it would still be a good thing to know about.

Running the command without the "speed=8" and the "-eject" parameters gives:
Code: Select all
[dishawjp@eunix ~]$ cdrecord -v -dev=/dev/cdwriter /home/dishawjp/docs
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01-dvd (i686-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.
TOC Type: 1 = CD-ROM
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/cdwriter'
devname: '/dev/cdwriter'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling').
SCSI buffer size: 64512
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 1
Vendor_info    : 'MSI     '
Identifikation : 'CD-RW MS-8348   '
Revision       : '120D'
Device seems to be: Generic mmc CD-RW.
Current: 0x0009
Profile: 0x0008
Profile: 0x0009 (current)
Profile: 0x000A
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-2 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1806336 = 1764 KB


But of course this is not a .iso file, so that may be part of the problem. But even that won't explain why the other programs die at the "preparing to write" stage.

Jim
dishawjp
administrator
administrator
 
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY

Postby Void Main » Sun Dec 19, 2004 11:00 am

Yes, you can not use cdrecord to burn a directory full of files directly. k3b and the other GUI utilities are nothing more than wrappers to mkisofs and cdrecord that makes doing this a little easier. Did you try running k3b from a shell prompt as root to see if there are any more detailed errors? Also did you try and burn an ISO as root using cdrecord?

Also, you have updated your system since you first installed it right? You need to make sure you are running the updated "udev" package and not the stock one.
User avatar
Void Main
Site Admin
Site Admin
 
Posts: 5705
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA

Postby dishawjp » Sun Dec 19, 2004 1:43 pm

Voidmain,

The system is fully updated. I pulled these error messages out of my /var/log/messages files from the last time I tried to burn. This was using the nautilus CD burner utility. At the recommendation of a poster on another list, I did make a modification to my /etc/cdrecord.conf file, but that has made no difference. I changed the last line to:
cdrom= /dev/cdwriter -1 -1 burnfree

It had read:
cdrom= /dev/cdrom -1 -1 burnfree

I'm not sure that that change should be kept, since cdrecord was accessing the proper drive before and there has been no change by changing that line.

Code: Select all
Dec 19 13:36:48 localhost kernel: cdrom: This disc doesn't have any tracks I recognize!
Dec 19 13:37:30 localhost kernel: hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 19 13:37:30 localhost kernel: hdb: status error: error=0x00
Dec 19 13:37:30 localhost kernel: hdb: drive not ready for command
Dec 19 13:37:30 localhost kernel: hdb: status timeout: status=0xd0 { Busy }
Dec 19 13:37:30 localhost kernel: hdb: status timeout: error=0xd0LastFailedSense 0x0d
Dec 19 13:37:30 localhost kernel: hdb: DMA disabled
Dec 19 13:37:30 localhost kernel: hdb: drive not ready for command
Dec 19 13:37:30 localhost kernel: hdb: ATAPI reset complete
Dec 19 13:37:30 localhost kernel: hdb: status error: status=0x08 { DataRequest }
Dec 19 13:37:30 localhost kernel: hdb: status error: error=0x01IllegalLengthIndication
Dec 19 13:37:30 localhost kernel: hdb: drive not ready for command
Dec 19 13:37:35 localhost kernel: hdb: status timeout: status=0xd0 { Busy }
Dec 19 13:37:35 localhost kernel: hdb: status timeout: error=0xd0LastFailedSense 0x0d
Dec 19 13:37:35 localhost kernel: hdb: drive not ready for command
Dec 19 13:37:35 localhost kernel: hdb: ATAPI reset complete
Dec 19 13:37:37 localhost kernel: hdb: request sense failure: status=0x51 { DriveReady SeekComplete Error }
Dec 19 13:37:37 localhost kernel: hdb: request sense failure: error=0x50LastFailedSense 0x05
Dec 19 13:37:37 localhost kernel: hdb: request sense failure: status=0x51 { DriveReady SeekComplete Error }
Dec 19 13:37:37 localhost kernel: hdb: request sense failure: error=0x50LastFailedSense 0x05
Dec 19 13:39:18 localhost gconfd (dishawjp-3017): Exiting

If I insert a CD, the nautilus burner program starts automatically. I can then select some random files to burn and it quickly goes through the "creating CD image" stage, then hangs on the "preparing to write" stage. At first the little "CD icon" on the dialog box is spinning and the CD drive spins up, but the light on the CD drive stays green (it normally changes to red when burning) it speeds up and slows down a few times, and then just hangs. Sometimes Xwindows hangs to the point that I have to open a virtual terminal to reboot. Other times the mouse will work and I can reboot normally. I have let it sit for well over 5 minutes at times to see if it was just taking its time thinking about things, but it has never even tried to burn.

Any other thoughts?

Jim
dishawjp
administrator
administrator
 
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY

Postby Void Main » Sun Dec 19, 2004 4:15 pm

Jim, the main thing I have been trying get you to do is try running cdrecord and k3b as root to see if it might be permissions related. You haven't indicated whether you tried that or not. Also, I assume you tried a different blank CD.
User avatar
Void Main
Site Admin
Site Admin
 
Posts: 5705
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA

Postby dishawjp » Sun Dec 19, 2004 5:09 pm

Hi Voidmain,

Sorry about not answering that question. I have tried k3b and the nautilus burner as root as well as normal user. I booted directly to root, not even an "su - " but right into root and there was no difference. I have also tried two different brands of CD's and several of each. I have some real "cheapies" and some Memorex ones, but that also seems to make no difference.

Since I'm not totally clear on the syntax for mkisofs to make a .iso file, I'm staying away from cdrecord for now.

The output from starting k3b as root in the terminal is:
Code: Select all
[root@eunix ~]# k3b
Link points to "/tmp/ksocket-root"
Link points to "/tmp/kde-root"
kbuildsycoca running...
Reusing existing ksycoca

And then it just hangs there. In the k3b dialog box it stops with "starting dao writing at 10x speed"

After shutting k3b down, in the terminal window, I get these additional error messages:
Code: Select all
Launched ok, pid = 3370
ALSA lib pcm_hw.c:549:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:549:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:549:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  7
  Minor opcode:  0
  Resource id:  0x34007cb
[root@eunix ~]# Mutex destroy failure: Device or resource busy
ICE default IO error handler doing an exit(), pid = 3330, errno = 0
ICE default IO error handler doing an exit(), pid = 3367, errno = 0
ALSA lib pcm_hw.c:549:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:549:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:549:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe


and the prompt never returned. Hope this mens something to you.
Jim
dishawjp
administrator
administrator
 
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY

Postby Void Main » Sun Dec 19, 2004 5:43 pm

I found a thread where they seem to have the same problem as you:

http://www.linuxfactors.com/forum/showt ... post126126

It appears there have been some changes made to cdrecord that may cause this problem with certain drives. In the thread I linked to above the guy bought a new drive which solved his problem. Of course that is a little extreme. I would have grabbed the source for cdrecord and compiled it, maybe even an earlier version if necessary, but I'll bet the current one could be compiled with options that would make it work for you. You might try that:

http://www.fokus.gmd.de/research/cc/glo ... ecord.html

You might also just try installing the FC2 version and see if that works. Of course if it does you would have to exclude it in your apt.conf so it doesn't get replaced on an upgrade.
User avatar
Void Main
Site Admin
Site Admin
 
Posts: 5705
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA

Postby dishawjp » Sun Dec 19, 2004 6:10 pm

Thanks again Voidmain!

I'm not too sure exactly how I'll approach this yet. I may take a look around at the cost for a supported CDburner, or maybe just wait and see if cdrecord gets fixed. Now that I'm reasonably sure what the problem is and that I'm not the only one with this problem I can take a bit of a "wait and see" stance. If it's getting close to time to do some serious burning I will probably just install cdrecord from FC2, or if I see a good enough deal on a more compliant burner, maybe I'll just pick one of those up and save myself some grief.

Thanks again for all your help!

Jim
dishawjp
administrator
administrator
 
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY

Postby dishawjp » Tue Dec 28, 2004 7:45 pm

And the good news is.......

I replaced my CD burner, a MSI which worked well under all versions of RH8-FC2 with a new Memorex 52x32x52x model and it burns like a champ!

As Voidmain suggested, the changes made to cdrecord used in FC3 must have created problems with my drive. I spent $49.99 at CompUSA and now everything is good . At least for burning CD's.

Now if I can jsut get my $!@##%%^$##ing modem to work :-)

Jim
dishawjp
administrator
administrator
 
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY


Return to Fedora/Red Hat

Who is online

Users browsing this forum: No registered users and 1 guest

cron