CD-Writing problem in linux

neo77777 · 08-31-2002, 09:19 AM

As per CD-Writting HOW-TO

Quote:

The device file name representing your CD-Writer has to be passed to the driver in the Linux kernel. Example: hdb=ide-scsi. Such a setting should be added to lilo.conf or chos.conf if the driver is statically compiled into your kernel, which seems to be the most common setup.

I don't know if things changed since v2.2, except GRUB addiion. I'd recompile kernel to modularize ide-scsi emulation. This is common now.

neo77777 · 08-31-2002, 09:25 AM

Plus this chunk from the same howto (Linux Documentation Project CD-Writing HOWTO)

Quote:

2.1.3. Compiling missing kernel modules (optional)

You don't need to read this section if you hardware is already
sucessfully recognized and configured by the previously described
configuration steps.

The Linux kernel can be equipped with drivers for various features.
You can compile the drivers into the kernel image statically or you
can compile them as a module for on-demand loading. The last method is
preferred for drivers not essential for bringing your Linux-system
into life, because your kernel will be smaller and faster then.
However, some drivers are essential for the system to come up and you
shouldn't compile them as a module. Example: if your system lives on
an IDE hard disk, you must have the driver for IDE hard disks in the
kernel -- not as a module.

There are three different types of CD-writers: SCSI, IDE/ATAPI and
external writers that work through the parallel port. The table shows
how to configure the Linux kernel for those hardware types. The first
column of the table is the section of the kernel configuration menu,
where you can find the setting. The second column is the description
of the feature (taken from the kernel configuration menu, too). The
third column gives the name of the resulting module. The columns named
SCSI, IDE and PP contain the necessary options for the associated
hardware (PP = parallel port).

Sect. Description Module SCSI IDE PP
------------------------------------------------------------
BLOCK Enhanced IDE/MFM/RLL... Y
BLOCK IDE/ATAPI CDROM ide-cd M
BLOCK SCSI emulation support ide-scsi M
BLOCK Loopback device loop M M M

PARIDE Parallel port IDE device paride Y/M
PARIDE Parallel port ATAPI CD-ROMs M
PARIDE Parallel port generic ATAPI M
PARIDE (select a low-level driver) Y

SCSI SCSI support scsi_mod Y/M Y/M
SCSI SCSI CD-ROM support sr_mod Y/M Y/M
SCSI Enable vendor-specific Y Y
SCSI SCSI generic support sg Y/M Y/M
SCSI (select a low-level driver) Y

FS ISO 9660 CDROM filesystem iso9660 Y/M Y/M Y/M
FS Microsoft Joliet cdrom... joliet Y Y Y

Y stands for yes and means you should put the beast into the kernel.
M stands for module and means you should or must compile this feature
as a module. Y/M gives you the option to decide between either (order
indicates choices with less potential problems). Empty settings don't
need to be modified and not changing them increases the chance that
the resulting kernel will work for you (if it did before...).
Especially in environments where SCSI and ATAPI devices are mixed, you
better build most things as modules.

Compiling loopback device is optional. It allows you to test the
image before writing it to the media. If you want to be able to read
CD-ROMs, you need support for the ISO 9660 filesystem. This driver
automatically includes RockRidge Extensions. The Microsoft Joliet CD-
ROM extensions have to be explicitly added to the ISO 9660 filesystem.
In any case, you need a low-level driver for your hardware. Low-level
refers to the driver, which interacts directly with the hardware. For
SCSI and the parallel port, there are a lot of low-level drivers
available.

Installing the resulting Linux-kernel is beyond the scope of this
HOWTO. Please consult the documentation of your Linux-distribution.
Users of RedHat Linux be aware that you have to compile in the
features "Ramdisk support" and "Initial ramdisk". Furthermore, you
have to generate a new ramdisk with the new modules by issuing a
command like "mkintrd --preload ide-cd initrd-2.2.14.img 2.2.14".

Kostko · 08-31-2002, 10:21 AM

so if i compile ide scsi support as modules, everything will work fine ? where is the reason for that, since it is the same if they are compiled in the kernel, except that this makes kernel bigger and a bit slower ?

Kostko · 08-31-2002, 11:49 AM

i tryed to compile/load scsi support as modules, but it is the same, as i said before...

crashmeister · 08-31-2002, 12:04 PM

Check with the highlight=chaos link from last page and see if you got all the symlinks setup.I got debian3.0 with emulation in the kernel and exactly the same problem beause a symlink was missing.

Kostko · 08-31-2002, 12:26 PM

crashmeister: sorry, but i just don't know to which sym links do you refer ?

crashmeister · 08-31-2002, 12:41 PM

Just check in /dev .I had to put a link in there.cdrom is linked to scd0.On the first page of this thread is a link to the thread where master and neo have about all the possiblities listed - depending wether you cdwriter is slave or master.
Sorry - got to run and buy beer now

Kostko · 08-31-2002, 12:59 PM

did you mean these links:

Quote:

If you have both CDRW and CDROM, and you make CDROM Master, and CDRW Slave and only use CDROM as rom and CDRW as burner, here's the commands and entries:
ln -sf /dev/hdc /dev/cdrom
ln -sf /dev/scd0 /dev/cdburner
ln -sf /dev/scd0 /dev/cdrw

well, they don't help me...

Kostko · 09-01-2002, 10:15 AM

it's workingggg!!!
i have removed /dev/sg0 and did mknod again and now it is working!

thak you for your support!