How to get cdrecord working in FC2?

[VJ]

Hi,
    After upgrading to FC2, I miss cdrecord because it does not work
anymore. I can use K3B but I need cdrecord also in some of my shell scripts.
On running it complains about being unable to open /dev/sg????? something
something(i forgot what number is shown in ????).

thanks in advance.
VJ

[Clint Harshaw]

VJ wrote:
> Hi,
>     After upgrading to FC2, I miss cdrecord because it does not work
> anymore. I can use K3B but I need cdrecord also in some of my shell scripts.
> On running it complains about being unable to open /dev/sg????? something
> something(i forgot what number is shown in ????).
>
> thanks in advance.
> VJ

Hello VJ:

There is a bug/feature associated with the latest 2.6.8.x kernels. A 
non-root user is not allowed to burn. Your choices are to either a) su 
to the root user burn or b) boot into an earlier kernel.

If neither of those suggestions will work (suppose you don't have the 
older kernel, for instance), then this tutorial may be of some use for you:

http://penguinsolutions.org/fedora/cdrw/

Hope this helps,
Clint

[VJ]

Thanks Clint, but I know about the root issue with kernel 2.6.8. I am able
to use K3b without ANY problem. It is cdrecord which seems to be the
problem. May be it has not been modified to work with kernel 2.6 (in old
kernel it needed ide-scsi module bit not any longer in 2.6).

Thanks and regards from
VJ

----- Original Message ----- 
From: "Clint Harshaw" 
To: "For users of Fedora Core releases" 
Sent: Tuesday, September 28, 2004 10:14 AM
Subject: Re: How to get cdrecord working in FC2?
> VJ wrote:
> > Hi,
> >     After upgrading to FC2, I miss cdrecord because it does not work
> > anymore. I can use K3B but I need cdrecord also in some of my shell

scripts.
> > On running it complains about being unable to open /dev/sg?????

something
> > something(i forgot what number is shown in ????).
> >
> > thanks in advance.
> > VJ
>
> Hello VJ:
>
> There is a bug/feature associated with the latest 2.6.8.x kernels. A
> non-root user is not allowed to burn. Your choices are to either a) su
> to the root user burn or b) boot into an earlier kernel.
>
> If neither of those suggestions will work (suppose you don't have the
> older kernel, for instance), then this tutorial may be of some use for

you:
> http://penguinsolutions.org/fedora/cdrw/
>
> Hope this helps,
> Clint
>
> -- 
> fedora-list mailing list
> [e-mail]
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list

[Michael Schwendt]

On Tue, 28 Sep 2004 10:36:16 +0100, VJ wrote:
> Thanks Clint, but I know about the root issue with kernel 2.6.8. I am able
> to use K3b without ANY problem. It is cdrecord which seems to be the
> problem. May be it has not been modified to work with kernel 2.6 (in old
> kernel it needed ide-scsi module bit not any longer in 2.6).

k3b uses cdrecord, too, so maybe your /etc/cdrecord.conf or command-line
options are wrong.

logrotates doesn't work

[jim martin]

Hi.. I have a FC1 Linux box act as a syslog server to
collect log from Router.  The log is store on the file
/home/ct/aufolognew  below are my content of
/etc/logrotate.conf and /etc/logrotate.d/syslog and i
found that after I do a 
(linux)#logrotate -f /etc/logrotate.d/syslog

the log will gone and the doesn't rotates daily.  Can
anyone guide me on this

more /etc/logrotate.conf 
# see "man logrotate" for details
# rotate log files weekly
#weekly

# keep 4 weeks worth of backlogs
#rotate 4

# create new (empty) log files after rotating old ones
#create

# uncomment this if you want your log files compressed
#compress

# RPM packages drop log rotation information into this
directory
include /etc/logrotate.d

# no packages own wtmp -- we'll rotate them here
/var/log/wtmp {
    monthly
    create 0664 root utmp
 }

/home/ct/aufolognew {

create 0777 root utmp
    rotate 30
    daily
    postrotate
    /sbin/killall -HUP syslogd
    endscript
}

[root@watcher ct]# more  /etc/logrotate.d/syslog
/home/ct/aufolognew /var/log/messages /var/log/secure
/var/log/maillog /var/log/
spooler /var/log/boot.log /var/log/cron {
    sharedscripts
    postrotate
        /bin/kill -HUP `cat /var/run/syslogd.pid 2>
/dev/null` 2> /dev/null || t
rue
    endscript
}

_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

logrotates doesn't work

[Paul Howarth]

jim martin wrote:
> Hi.. I have a FC1 Linux box act as a syslog server to
> collect log from Router.  The log is store on the file
> /home/ct/aufolognew  below are my content of
> /etc/logrotate.conf and /etc/logrotate.d/syslog and i
> found that after I do a 
> (linux)#logrotate -f /etc/logrotate.d/syslog
>
> the log will gone and the doesn't rotates daily.  Can
> anyone guide me on this
>
> more /etc/logrotate.conf 
> # see "man logrotate" for details
> # rotate log files weekly
> #weekly
>
> # keep 4 weeks worth of backlogs
> #rotate 4
>
> # create new (empty) log files after rotating old ones
> #create
>
> # uncomment this if you want your log files compressed
> #compress
>
> # RPM packages drop log rotation information into this
> directory
> include /etc/logrotate.d
>
> # no packages own wtmp -- we'll rotate them here
> /var/log/wtmp {
>     monthly
>     create 0664 root utmp
>  }
>
> /home/ct/aufolognew {
>     create 0777 root utmp
>     rotate 30
>     daily
>     postrotate
>     /sbin/killall -HUP syslogd
>     endscript
> }
>
> [root@watcher ct]# more  /etc/logrotate.d/syslog
> /home/ct/aufolognew /var/log/messages /var/log/secure /var/log/maillog /var/log/spooler /var/log/boot.log /var/log/cron {
>     sharedscripts
>     postrotate
>         /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null || true
>     endscript
> }

Why have you got two entries for rotation of /home/ct/aufolognew? One in 
/etc/logrotate.conf specifically for that file and another in 
/etc/logrotate.d/syslog to handle all syslog files.

Paul.

[Clint Harshaw]

VJ wrote:
> Thanks Clint, but I know about the root issue with kernel 2.6.8. I am able
> to use K3b without ANY problem. It is cdrecord which seems to be the
> problem. May be it has not been modified to work with kernel 2.6 (in old
> kernel it needed ide-scsi module bit not any longer in 2.6).
>
> Thanks and regards from
> VJ

If K3B is working, take a peek at the output logs to see the specific 
cdrecord commands it is using. Then you can use the same cdrecord 
commands from the terminal window.

Hope this helps,
Clint

[Pybe]

(Also see subj: "cdrecord, k3b, gtoaster hang (not using 2.6.8)" &
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124306)

I cant get cdrecord or k3b to work using an earlier kernel or as root.

Does anyone have any ideas, this is getting really silly now.

I have logged a bug and posted here and not recieved even a derogatory
comment about it probably being the 2.6.8 bug and Im just stupid or
something.

Is anyone out there who can help?

On Tue, 28 Sep 2004 05:56:12 -0400, Clint Harshaw
 wrote:
> VJ wrote:
> > Thanks Clint, but I know about the root issue with kernel 2.6.8. I am able
> > to use K3b without ANY problem. It is cdrecord which seems to be the
> > problem. May be it has not been modified to work with kernel 2.6 (in old
> > kernel it needed ide-scsi module bit not any longer in 2.6).
> >
> > Thanks and regards from
> > VJ
>
> If K3B is working, take a peek at the output logs to see the specific
> cdrecord commands it is using. Then you can use the same cdrecord
> commands from the terminal window.
>
> Hope this helps,
> Clint
>
> --
> fedora-list mailing list
> [e-mail]
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list

[Hardy Merrill]

This probably won't help, but I thought I'd include it
since I just did this last night and it worked for me.

My situation was that I downloaded the FC2 rescue iso
image and wanted to burn that to a CD.  Here's what I
did:

# su - root
  # cdrecord --dev=/dev/cdwriter <iso image name>
        (I looked in /dev and did 'ls cd*' and
         found the cdwriter device)

That's it - and that worked for me.

HTH.

Hardy Merrill

--- Pybe  wrote:
> (Also see subj: "cdrecord, k3b, gtoaster hang (not
> using 2.6.8)" &

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124306)
> I cant get cdrecord or k3b to work using an earlier
> kernel or as root.
>
> Does anyone have any ideas, this is getting really
> silly now.
>
> I have logged a bug and posted here and not recieved
> even a derogatory
> comment about it probably being the 2.6.8 bug and Im
> just stupid or
> something.
>
> Is anyone out there who can help?
>
> On Tue, 28 Sep 2004 05:56:12 -0400, Clint Harshaw
>  wrote:
> > VJ wrote:
> > > Thanks Clint, but I know about the root issue
>
> with kernel 2.6.8. I am able
> > > to use K3b without ANY problem. It is cdrecord
>
> which seems to be the
> > > problem. May be it has not been modified to work
>
> with kernel 2.6 (in old
> > > kernel it needed ide-scsi module bit not any
>
> longer in 2.6).
> > > Thanks and regards from
> > > VJ
> >
> > If K3B is working, take a peek at the output logs
>
> to see the specific
> > cdrecord commands it is using. Then you can use
>
> the same cdrecord
> > commands from the terminal window.
> >
> > Hope this helps,
> > Clint
> >
> > --
> > fedora-list mailing list
> > [e-mail]
> > To unsubscribe:
>
> http://www.redhat.com/mailman/listinfo/fedora-list
> >
>
> -- 
> fedora-list mailing list
> [e-mail]
> To unsubscribe:
> http://www.redhat.com/mailman/listinfo/fedora-list

__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail

[Pybe]

> --- Pybe  wrote:
> > (Also see subj: "cdrecord, k3b, gtoaster hang (not
> > using 2.6.8)" &
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124306)
> > I cant get cdrecord or k3b to work using an earlier
> > kernel or as root.
> >
> > Does anyone have any ideas, this is getting really
> > silly now.
> >
> > I have logged a bug and posted here and not recieved
> > even a derogatory
> > comment about it probably being the 2.6.8 bug and Im
> > just stupid or
> > something.
> >
> > Is anyone out there who can help?

On Tue, 28 Sep 2004 04:25:40 -0700 (PDT), Hardy Merrill
 wrote:
> This probably won't help, but I thought I'd include it
> since I just did this last night and it worked for me.
>
> My situation was that I downloaded the FC2 rescue iso
> image and wanted to burn that to a CD.  Here's what I
> did:
>
> # su - root
>   # cdrecord --dev=/dev/cdwriter <iso image name>
>         (I looked in /dev and did 'ls cd*' and
>          found the cdwriter device)
>
> That's it - and that worked for me.
>
> HTH.
>
> Hardy Merrill

Still just hangs using kernel-2.6.7-1.494.2.2 & cdrecord-2.01-0.a27.4.FC2.3

[root@help root]# cdrecord --dev=/dev/hdd FC2-i386-rescuecd.iso
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.01a27-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 .
Note: The author of cdrecord should not be bothered with problems in
this version.
scsidev: '/dev/hdd'
devname: '/dev/hdd'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.

No idea what DL means......
[root@help root]# ps waux | grep cdrecord
root      8513  0.0  1.0  6896 6896 pts/5    DL   12:34   0:00
cdrecord --dev=/dev/hdd FC2-i386-rescuecd.iso

There probably worth less now but there are multiple gmail invites to
the person that can get me burning cd's (even as root, i dont care) or
if you in the UK, Sussex area and manage to get me burning you can
have an old hp netserver lh II, dual pentium 233, 128mb ram, 3 x 4Gb
scsi & 2 x 9Gb scsi, cd-rom, hp surestore dat8 & a few dds2 8Gb tapes.

Pybe

[Paul Howarth]

Pybe wrote:
> Still just hangs using kernel-2.6.7-1.494.2.2 & cdrecord-2.01-0.a27.4.FC2.3
>
> [root@help root]# cdrecord --dev=/dev/hdd FC2-i386-rescuecd.iso
> 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.01a27-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 .
> Note: The author of cdrecord should not be bothered with problems in
> this version.
> scsidev: '/dev/hdd'
> devname: '/dev/hdd'
> scsibus: -2 target: -2 lun: -2
> Warning: Open by 'devname' is unintentional and not supported.
>
> No idea what DL means......
> [root@help root]# ps waux | grep cdrecord
> root      8513  0.0  1.0  6896 6896 pts/5    DL   12:34   0:00
> cdrecord --dev=/dev/hdd FC2-i386-rescuecd.iso

See "man ps"; D means the process is in an uninterruptible sleep (usually this 
happens when waiting on I/O), and L means "has pages locked into memory (for 
real-time and custom IO)".

Do you know if this drive works in any other O.S.? It might actually be a 
hardware problem.

Paul.

[Pybe]

> See "man ps"; D means the process is in an uninterruptible sleep (usually this
> happens when waiting on I/O), and L means "has pages locked into memory (for
> real-time and custom IO)".
>
> Do you know if this drive works in any other O.S.? It might actually be a
> hardware problem.
>
> Paul.

It does work in windows 2000 fine.

[Paul Howarth]

Pybe wrote:
> > See "man ps"; D means the process is in an uninterruptible sleep (usually this
> > happens when waiting on I/O), and L means "has pages locked into memory (for
> > real-time and custom IO)".
> >
> > Do you know if this drive works in any other O.S.? It might actually be a
> > hardware problem.
> >
> > Paul.
>
> It does work in windows 2000 fine.

Is the cable to the CD writer shared with any other device, such as a hard 
disk? That might cause problems - see the -immed option to cdrecord.

Paul.

[Pybe]

> Is the cable to the CD writer shared with any other device, such as a hard
> disk? That might cause problems - see the -immed option to cdrecord.

There are 4 ide devices ide1 has 2 hard drives and ide2 has cdrw and cdrom

Tried cdrecord --dev=/dev/hdd -immed blah.iso and still hangs exactly the same.

Pybe

[Paul Howarth]

Pybe wrote:
> > Is the cable to the CD writer shared with any other device, such as a hard
> > disk? That might cause problems - see the -immed option to cdrecord.
>
> There are 4 ide devices ide1 has 2 hard drives and ide2 has cdrw and cdrom
>
> Tried cdrecord --dev=/dev/hdd -immed blah.iso and still hangs exactly the same.

Try:

strace cdrecord --dev=/dev/hdd blah.iso

You might at least find out which system call is causing the hang.

Paul.

[Filippos Klironomos]

> There are 4 ide devices ide1 has 2 hard drives and ide2 has cdrw and cdrom
>
> Tried cdrecord --dev=/dev/hdd -immed blah.iso and still hangs exactly the same.

Woooooa! Slow down! You don't want to corrupt your hard disk! Some of
those 4 ide devices are your partitions on your hard disk that have
FC2 and whatever else installed on your system. Don't play around with
them and especially when you have root privileges!

Now your problem is most likely a ATAPI problem. I used to get the
same response from cdrecord when I had SCSI emulation on for my ATAPI
CD burner. So one thing you should do is turn it off and try to use
cdrecord. Here are the steps:

First go to /boot/grub/grub.conf and back it up just in case:

cd /boot/grub
cp grub.conf grub.conf.BAK

Then edit grub.conf with your favorite editor and see if there is a command:

hdx=ide-scsi

on the kernel command line that you are using. Notice that "x" is the
letter for the ide device that your CD is using so it can be anything.
If there is this command delete ONLY that and leave the rest intact.
Save and exit from your editor.

Now go to your /etc/modprobe.conf file and see if there is an option:

options ide-cd ignore=hdx

where "x" again pertains to your ide letter. Comment that part out by
putting a hash "#" in front of it. Now you are ready to go. If your
kernel was compiled with native ATAPI support then by rebooting your
system to the same kernel your device should be ready to use. If you
give:

cdrecord -scanbus dev=ATAPI

cdrecord should respond with your ATAPI device numbers identified.

Good luck!

[Pybe]

On Tue, 28 Sep 2004 09:15:25 -0400, Filippos Klironomos
 wrote:
> Now your problem is most likely a ATAPI problem. I used to get the
> same response from cdrecord when I had SCSI emulation on for my ATAPI
> CD burner. So one thing you should do is turn it off and try to use
> cdrecord. Here are the steps:
>
> First go to /boot/grub/grub.conf and back it up just in case:
>
> cd /boot/grub
> cp grub.conf grub.conf.BAK
>
> Then edit grub.conf with your favorite editor and see if there is a command:
>
> hdx=ide-scsi
>
> on the kernel command line that you are using. Notice that "x" is the
> letter for the ide device that your CD is using so it can be anything.
> If there is this command delete ONLY that and leave the rest intact.
> Save and exit from your editor.
>
> Now go to your /etc/modprobe.conf file and see if there is an option:
>
> options ide-cd ignore=hdx
>
> where "x" again pertains to your ide letter. Comment that part out by
> putting a hash "#" in front of it. Now you are ready to go. If your
> kernel was compiled with native ATAPI support then by rebooting your
> system to the same kernel your device should be ready to use. If you
> give:

This is a clean FC2 install so none of this applies.
> cdrecord -scanbus dev=ATAPI
>
> cdrecord should respond with your ATAPI device numbers identified.
>
> Good luck!

This worked and listed the drives, but k3b still hangs as root and on
previous kernel and cdrecord still hangs trying to write an iso.

Thanks
Pybe

On Tue, 28 Sep 2004 09:15:25 -0400, Filippos Klironomos
 wrote:
> > There are 4 ide devices ide1 has 2 hard drives and ide2 has cdrw and cdrom
> >
> > Tried cdrecord --dev=/dev/hdd -immed blah.iso and still hangs exactly the same.
>
> Woooooa! Slow down! You don't want to corrupt your hard disk! Some of
> those 4 ide devices are your partitions on your hard disk that have
> FC2 and whatever else installed on your system. Don't play around with
> them and especially when you have root privileges!
>
> Now your problem is most likely a ATAPI problem. I used to get the
> same response from cdrecord when I had SCSI emulation on for my ATAPI
> CD burner. So one thing you should do is turn it off and try to use
> cdrecord. Here are the steps:
>
> First go to /boot/grub/grub.conf and back it up just in case:
>
> cd /boot/grub
> cp grub.conf grub.conf.BAK
>
> Then edit grub.conf with your favorite editor and see if there is a command:
>
> hdx=ide-scsi
>
> on the kernel command line that you are using. Notice that "x" is the
> letter for the ide device that your CD is using so it can be anything.
> If there is this command delete ONLY that and leave the rest intact.
> Save and exit from your editor.
>
> Now go to your /etc/modprobe.conf file and see if there is an option:
>
> options ide-cd ignore=hdx
>
> where "x" again pertains to your ide letter. Comment that part out by
> putting a hash "#" in front of it. Now you are ready to go. If your
> kernel was compiled with native ATAPI support then by rebooting your
> system to the same kernel your device should be ready to use. If you
> give:
>
> cdrecord -scanbus dev=ATAPI
>
> cdrecord should respond with your ATAPI device numbers identified.
>
> Good luck!

[Jeff Vian]

On Tue, 2004-09-28 at 07:46, Pybe wrote:
> > Is the cable to the CD writer shared with any other device, such as a hard
> > disk? That might cause problems - see the -immed option to cdrecord.
>
> There are 4 ide devices ide1 has 2 hard drives and ide2 has cdrw and cdrom
>
> Tried cdrecord --dev=/dev/hdd -immed blah.iso and still hangs exactly the same.

Which device is the cdrw?  hdc or hdd?

Confirm you are doing this only to the cdrw.
> Pybe

[Filippos Klironomos]

> Which device is the cdrw?  hdc or hdd?
>
> Confirm you are doing this only to the cdrw.
> > Pybe

Best tesl ever is to see where /dev/cdrom points to:

ls -l /dev/cdrom

If that's your only CD device that's the device you should be writing
things on. If you have multiple CD drives then do a

ls -l /dev/cd*

to figure them out and see which is which either by

cdrecord -scanbus dev=ATAPI

or though your kernel logs during boot:

egrep -i -C2 -e "DVD|CD" /var/log/dmesg

[Pybe]

On Tue, 28 Sep 2004 13:13:11 -0400, Filippos Klironomos
 wrote:
> > Which device is the cdrw?  hdc or hdd?
> >
> > Confirm you are doing this only to the cdrw.
> > > Pybe
>
> Best tesl ever is to see where /dev/cdrom points to:
>
> ls -l /dev/cdrom
>
> If that's your only CD device that's the device you should be writing
> things on. If you have multiple CD drives then do a
>
> ls -l /dev/cd*
>
> to figure them out and see which is which either by
>
> cdrecord -scanbus dev=ATAPI
>
> or though your kernel logs during boot:
>
> egrep -i -C2 -e "DVD|CD" /var/log/dmesg

Or just cat /proc/sys/dev/cdrom/info and you can see which can do what
which can be more definate.

[Filippos Klironomos]

On another note I just realized that the module is called 'ide_cd' and
not 'ide-cd'!!!!!
So it won't hurt if you try:

modprobe ide_cd

and see what happens! If the module is there (and it should) then you
should have finally your CD drive back!

[Alexander Dalloz]

Am Fr, den 01.10.2004 schrieb Filippos Klironomos um 3:59:
> On another note I just realized that the module is called 'ide_cd' and
> not 'ide-cd'!!!!!
> and see what happens! If the module is there (and it should) then you
> should have finally your CD drive back!

The FC2 kernel does not ship with an ide-cd.ko or ide_cd.ko module.

Alexander

[Pybe]

On Fri, 01 Oct 2004 17:11:17 +0200, Alexander Dalloz
 wrote:
> Am Fr, den 01.10.2004 schrieb Filippos Klironomos um 3:59:
> > On another note I just realized that the module is called 'ide_cd' and
> > not 'ide-cd'!!!!!
> > and see what happens! If the module is there (and it should) then you
> > should have finally your CD drive back!
>
> The FC2 kernel does not ship with an ide-cd.ko or ide_cd.ko module.

Does that help me towards solving the problem, where do I go from here?

[Randy Kelsoe]

Pybe wrote:
> Still just hangs using kernel-2.6.7-1.494.2.2 & cdrecord-2.01-0.a27.4.FC2.3
>
> [root@help root]# cdrecord --dev=/dev/hdd FC2-i386-rescuecd.iso
> 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.01a27-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 .
> Note: The author of cdrecord should not be bothered with problems in
> this version.
> scsidev: '/dev/hdd'
> devname: '/dev/hdd'
> scsibus: -2 target: -2 lun: -2
> Warning: Open by 'devname' is unintentional and not supported.
>
> No idea what DL means......
> [root@help root]# ps waux | grep cdrecord
> root      8513  0.0  1.0  6896 6896 pts/5    DL   12:34   0:00
> cdrecord --dev=/dev/hdd FC2-i386-rescuecd.iso
>
> There probably worth less now but there are multiple gmail invites to
> the person that can get me burning cd's (even as root, i dont care) or
> if you in the UK, Sussex area and manage to get me burning you can
> have an old hp netserver lh II, dual pentium 233, 128mb ram, 3 x 4Gb
> scsi & 2 x 9Gb scsi, cd-rom, hp surestore dat8 & a few dds2 8Gb tapes.

First, look at your /etc/grub.conf entry for your present kernel, and 
make sure you don't have have an 'ide-scsi' entry for your burner.

What I did to get my burner working (it's also /dev/hdd), was to edit my 
/etc/cdrecord.conf file. Here are the uncommented lines from my 
cdrecord.conf:

CDR_DEVICE=PLEXTOR
        CDR_FIFOSIZE=4m
        PLEXTOR=        ATA:1,1,0       -1      -1      burnfree

You can call your burner anything you want, just substitute PLEXTOR 
above for whatever you want to call your drive. Once you get your 
cdrecord.conf file edited:

cdrecord -v yourfilename.iso

will burn an iso image.

[Pybe]

On Tue, 28 Sep 2004 09:26:19 -0500, Randy Kelsoe  wrote:
> First, look at your /etc/grub.conf entry for your present kernel, and
> make sure you don't have have an 'ide-scsi' entry for your burner.
>
> What I did to get my burner working (it's also /dev/hdd), was to edit my
> /etc/cdrecord.conf file. Here are the uncommented lines from my
> cdrecord.conf:
>     CDR_DEVICE=PLEXTOR
>     CDR_FIFOSIZE=4m
>     PLEXTOR=        ATA:1,1,0       -1      -1      burnfree
>
> You can call your burner anything you want, just substitute PLEXTOR
> above for whatever you want to call your drive. Once you get your
> cdrecord.conf file edited:
>
> cdrecord -v yourfilename.iso
>
> will burn an iso image.

This still results in the same hang.

Thanks
Pybe

[Stuart Sears]

On Tue 28 September 2004 18:24, Pybe wrote:
> On Tue, 28 Sep 2004 09:26:19 -0500, Randy Kelsoe

wrote:
> > First, look at your /etc/grub.conf entry for your present kernel, and
> > make sure you don't have have an 'ide-scsi' entry for your burner.

this is correct. ide-scsi is no longer necessary with the 2.6 series kernels.
> > What I did to get my burner working (it's also /dev/hdd), was to edit my
> > /etc/cdrecord.conf file. Here are the uncommented lines from my
> > cdrecord.conf:
> >     CDR_DEVICE=PLEXTOR
> >     CDR_FIFOSIZE=4m
> >     PLEXTOR=        ATA:1,1,0       -1      -1      burnfree

this will probably work if you have the _correct_ device numbers

I have read your mails, but have missed any posting containing the actual 
output of 
cdrecord -scanbus dev=ATAPI
a literal cut-and paste will help.
e.g on my system I get 
# ---- #
[stuart@behemoth stuart]$ cdrecord dev=ATAPI -scanbus
Cdrecord-Clone 2.01a27-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg 
Schilling
<snip loads of unneeded output>
scsibus0:
        0,0,0     0) 'FREECOM_' 'DVD+/-RW4B      ' '1.33' Removable CD-ROM
<snip more numbers>

ths would make my entry in /etc/cdrecord.conf:
CDR_DEVICE=FREECOM
CDR_FIFOSIZE=4m
FREECOM=        ATA:0,0,0       -1      -1      burnfree
                                    ^^^ 
although as mentioned before the CDR_DEVICE string can be set to anything you 
like. The numbers must match, however.

any help?

Stuart

[Pybe]

On Tue, 28 Sep 2004 20:20:23 +0100, Stuart Sears  wrote:
> this is correct. ide-scsi is no longer necessary with the 2.6 series kernels.
> > > What I did to get my burner working (it's also /dev/hdd), was to edit my
> > > /etc/cdrecord.conf file. Here are the uncommented lines from my
> > > cdrecord.conf:
> > >     CDR_DEVICE=PLEXTOR
> > >     CDR_FIFOSIZE=4m
> > >     PLEXTOR=        ATA:1,1,0       -1      -1      burnfree
>
> this will probably work if you have the _correct_ device numbers
>
> I have read your mails, but have missed any posting containing the actual
> output of
> cdrecord -scanbus dev=ATAPI
> a literal cut-and paste will help.
> e.g on my system I get
> # ---- #
> [stuart@behemoth stuart]$ cdrecord dev=ATAPI -scanbus
> Cdrecord-Clone 2.01a27-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg
> Schilling
>
> <snip loads of unneeded output>
> scsibus0:
>         0,0,0     0) 'FREECOM_' 'DVD+/-RW4B      ' '1.33' Removable CD-ROM
> <snip more numbers>
>
> ths would make my entry in /etc/cdrecord.conf:
> CDR_DEVICE=FREECOM
> CDR_FIFOSIZE=4m
> FREECOM=        ATA:0,0,0       -1      -1      burnfree
>                                     ^^^
> although as mentioned before the CDR_DEVICE string can be set to anything you
> like. The numbers must match, however.

This did work and bring up somthing yesterday, but now it just hangs
like the rest.

[root@help root]# cdrecord -scanbus dev=ATAPI
Cdrecord-Clone 2.01a27-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 .
Note: The author of cdrecord should not be bothered with problems in
this version.
scsidev: 'ATAPI'
devname: 'ATAPI'
scsibus: -2 target: -2 lun: -2
Warning: Using ATA Packet interface.
Warning: The related libscg interface code is in pre alpha.
Warning: There may be fatal problems.
Using libscg version 'schily-0.8'.
scsibus0:

[root@help root]# ps waux | grep cdrecord
root      5482  0.0  0.0  2824  460 pts/0    D    09:16   0:00
cdrecord -scanbus dev=ATAPI