Hey,
I'm trying to burn stuff to cd using cdrecord and cd Creator (built into Nautilus) but it seems they don't really see my burner correctly.

The following is the output of cdr

# cdrecord -scanbus
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 <warly@mandrakesoft.com>.
Note: The author of cdrecord should not be bothered with problems in this version.
Linux sg driver version: 3.5.31
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.80-RH '@(#)scsi-linux-sg.c 1.80 04/03/08 Copyright 1997 J. Schilling').
scsibus0:
0,0,0 0) ' ' 'USB Reader ' '1.00' Removable Disk
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *

However, I think that 0,0,0 is supposed to by my cd writer. When I go into my hardware browser, under CDROM drives, it says: CW088D ATAPI CD-R/RW. So, Fedora knows it's there, why doesn't cdrecord?

I used to run Fedora Core 1 and burnt cds with no problem. But since I installed FC2, I can't seem to get it to work.

Any help would be greatly appreciated. Thanks in advance.

Is it an internal or external burner? I don't have experience with external burners, but I can give you some very good hints for internal burners.

Is the burner really a scsi device? Check in the proc system. In /proc/scsi you can cat the files in there and it's subdirectories to find info on your scsi devices. In /proc/ide you can cat the files there to see information on your ide interface. If, by chance, you were in /proc/ide and you cat'd the 'model' file in, say, hdd, you have an IDE burner.

To get this working in your system, you have to make sure ide-scsi is compiled in to your kernel, and then add an append line in your boot manager. In lilo, you would add append="hdd=ide-scsi" if your IDE burner is attached to /dev/hdd (you checked it in the proc system earlier). Rerun lilo after you add this to your lilo.conf, then reboot.

When you run cdrecord -scanbus again, you should hopefully see your burner show up in the list. Good luck!

The same answer applies to Grub

Sometimes a kernel parameter helps to make sure the kernel doesn't use ide drivers on the device
so you can use the ide-scsi module

suppose your cdwriter is hdd (use "dmesg | less" or similar) the line for lilo
would be
append="hdd=ide-cd"

you can use it also on the lilo prompt if that is visible (maybe [tab] key)
and type the name of you kernel followed by a space and the append



for grub it will be very similar.

in case you see the scsi device appearing with "cdrecord -scanbus" after
this, it is probably the solution.

Tlowk

First of all, thanks to everyone for your replies.

Now I'm pretty sure it is an ide drive. I don't know how to use the cat command that d0odman was talking about, but in the /proc/ide directory, I find a directory called hdd (the burner) and within that directory I find a text file called model and within that is the name of the drive.

I'm not sure about all this lilo and grub stuff, but I tried adding the line append="hdd=ide-scsi" in /boot/grub/grub.conf in the section that boots Fedora. I rebooted and nothing changed.

Before I posted I reference my copy of the Red Hat Linux Bible. It gave the following instructions which I tried.

1. remove the ide-cd module with the line options ide-cd ignore=hdd

2. Reboot

3. modprobe -a ide-scsi

4. check cdrecord -scanbus

This doesn't help me though. If there is any more information you need just ask. I don't think I can even read from the drive.

By the way, it is an internal drive.

in your /boot/grub/gub.conf are lines like this:

kernel /vmlinuz-2.4.something ro root=/dev/hda3 hdd=ide-scsi

at the end you can add the hdd=ide-scsi

Tlowk

Hey,
Thanks for the suggestion. I tried that and it didn't seem to work. I thought for clarification I'd post my grub.conf:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,2)
# kernel /vmlinuz-version ro root=/dev/hda6
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,2)/grub/splash.xpm.gz
title Fedora Core (2.6.8-1.521)
root (hd0,2)
kernel /vmlinuz-2.6.8-1.521 ro root=LABEL=/ rhgb quiet append="hdd=ide-scsi"
initrd /initrd-2.6.8-1.521.img
title Windows XP
rootnoverify (hd0,1)
chainloader +1

Also for clarification, that's all I did, add the append statement in grub.conf. I tried the other suggestions and when they didn't work, I changed everything back. So, if there's something else I'm supposed to do, let me know.

Thanks again for all your help.

EDIT: The append statement is on the same line as the line beginning with kernel...

Check out tlowk's post. I'm not familiar with grub, but he's given you a hint. You don't do append="hdd=ide-scsi" at the end of your kernel line in your grub.conf You just add "hdd=ide-scsi" at the end. You'd add an append statement if you were using lilo.

Hi,

Even though you have FC1 listed on the side as your distro, the grub.conf seems to say that you have FC2. ....
title Fedora Core (2.6.8-1.521)

That being the case, scsi emulation isn't being used, so you don't need that line in the grub.conf ...append="hdd=ide-scsi"

You can verify that by looking in the /etc/sysconfig/hwconf
On my FC2 box, it looks like this...
class: CDROM
bus: IDE

Where it looks like this on the FC1 box .....
class: CDROM
bus: SCSI

So, that leaves us with no idea what the problem is except maybe an issue with that version of cdrecord. Maybe the first thing I would try is the command:
yum update and see what comes down the pipe.

Awesome, removing the append and the quotes did it. Thanks a lot.

And to homey, I updated my info, it should say FC2 now. I had the same thing happen, scsi on FC1 ide on FC2. Weird.

Thanks again.

Here's an interesting thing that I thought I might add:

I recently did a fresh install of FC2 and upon installing, cdrecord identified the driver correctly, as FC1 used to do. However, after updating, it went back to identifying it the same way it used to.

I'm not sure what exactly I updated that caused it to do this since i just used yum to update all outdated software.

Any ideas? I wouldn't mind reverting back to the old version of whatever it was that causes the problem. Thanks.