Skip to contentSkip to conversation

cdrecord hangs my computer

DISCUSSION Tero Knuutila 16 participants 33 messages Dec 6, 2003 – Dec 9, 2003 SCSI

lore
Share & tools
lore
#0 lore raw

Hi!

I am running 2.6.0-test11 kernel on Gentoo (i686 AMD Duron). I have HP 7200 cd burner.
My system hangs everytime I try to burn my .wav files to cd with cdrecord. Usually few tracks go succesfully but then everything stops. Even the mouse won't move and powerbutton does not affect.

And if I have understood correctly, Linux should never hang, so hopefully some of You will help me.

I am glad if any responses are CC:t to me ([email protected]). I can't subscribe to this list because traffic is so heavy.

With best regards,
Tero

_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

#1 lore raw
Quoted 4 lines · Tero Knuutila

My system hangs everytime I try to burn my .wav files to cd with cdrecord. Usually few tracks go succesfully but then everything stops. Even the mouse won't move and powerbutton does not affect.

Is this with ide-scsi? If so, does the appended patch help?

If not, we really need a whole lot more information (hw config, messages etc).

Linus

---
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher. # This patch includes the following deltas:
# ChangeSet 1.1499 -> 1.1500
# drivers/scsi/ide-scsi.c 1.33 -> 1.34
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/12/02 [email protected] 1.1500
# Fix ide-scsi.c uninitialized variable
# --------------------------------------------
#

drivers/scsi/ide-scsi.c +1 -0
diff -Nru a/drivers/scsi/ide-scsi.c b/drivers/scsi/ide-scsi.c
@@ -517,6 +517,7 @@
 	pc->current_position=pc->buffer;
 	bcount.all = IDE_MIN(pc->request_transfer, 63 * 1024);		/* Request to transfer the entire buffer at once */
 
+	feature.all = 0;
 	if (drive->using_dma && rq->bio) {
 		if (test_bit(PC_WRITING, &pc->flags))
 			feature.b.dma = !HWIF(drive)->ide_dma_write(drive);
#2 lore raw
Quoted 8 lines · Linus Torvalds
Quoted 3 lines · Tero Knuutila

My system hangs everytime I try to burn my .wav files to cd with cdrecord. Usually few tracks go succesfully but then everything stops. Even the mouse won't move and powerbutton does not affect.

Quoted 6 lines

Is this with ide-scsi? If so, does the appended patch help?

If not, we really need a whole lot more information (hw config, messages etc).

Linus

I've noted this at boot several times with 2.6.0-test11

Dec  4 23:59:21 e-d0uble kernel: ide-scsi is deprecated for cd burning! Use ide-cd and give dev=/dev/hdX as device

Removing the ide-cd bootparams: (I didn't try the patch)

Cdrecord 2.00.3 seems to like the sony-dru500a, denoted as --dev=/dev/hdc, I burned several disks this way. crdao and growisofs don't like to parse /dev/hdc as an argumenet, but I'm sure these are easily fixed.

Ethan

#3 lore raw
Quoted 8 lines · Ethan Weinstein
Quoted 7 lines
Quoted 3 lines

My system hangs everytime I try to burn my .wav files to cd with cdrecord. Usually few tracks go succesfully but then everything stops. Even the mouse won't move and powerbutton does not affect.

Is this with ide-scsi? If so, does the appended patch help? If not, we really need a whole lot more information (hw config, messages
etc).

Quoted 4 lines

I've noted this at boot several times with 2.6.0-test11

Dec  4 23:59:21 e-d0uble kernel: ide-scsi is deprecated for cd

burning! Use ide-cd and give dev=/dev/hdX as device

And cdrecord keeps saying "Warning: Open by 'devname' is unintentional and not supported.". Maybe it's about time someone got rid of that message.

Signature · 2 lines
Måns Rullgård
[email protected]
#4 lore raw
In reply to Ethan Weinstein
Quoted 4 lines

I've noted this at boot several times with 2.6.0-test11

Dec  4 23:59:21 e-d0uble kernel: ide-scsi is deprecated for cd burning! 

Use ide-cd and give dev=/dev/hdX as device

At the moment, I don't have a burner on a 2.6.0 machine, however, why is ide-scsi depreciated? On every PC I have that has an ide cd drive, I use ide-scsi. I like the fact that scd0 is the cdrom drive. Instead of guessing if it's hdb hdc or hdd (in the case of this laptop, the dvd was hdb and the modular cdrw was hdc).

On a side note, has anyone had any luck with Acard's SCSIDE AEC-7722 adapter on dvd burners? I was planning on this adapter on an optorite dd0401 dvd burner.

Signature · 1 line
 Lab tests show that use of micro$oft causes cancer in lab animals
#5 lore raw
Quoted 2 lines

At the moment, I don't have a burner on a 2.6.0 machine, however, why is ide-scsi depreciated?

Basically IDE-SCSI is a work-around to allow userspace programs that were designed to talk to SCSI devices to use SCSI-like devices connected to an IDE bus.

This works, but obviously it is better to support things natively. IDE CD recorders are probably the most popular SCSI-like IDE device and were therefore quickly supported. Less common hardware, such as some IDE MO drives, continues to require IDE-SCSI for the time being.

Quoted 4 lines

On every PC I have that has an ide cd drive, I use
ide-scsi. I like the fact that scd0 is the cdrom drive. Instead of guessing if it's hdb hdc or hdd (in the case of this laptop, the dvd was hdb and the modular cdrw was hdc).

It's easy enough to write something in userspace to identify which devices are which and create devices such as /dev/cdrom automatically - no need to use IDE-SCSI for that.

John.

#6 lore raw
In reply to Wakko Warner
Quoted 3 lines · Wakko Warner

At the moment, I don't have a burner on a 2.6.0 machine, however, why is ide-scsi depreciated?

Several reasons.

One is just plain confusion - anybody who uses cdrecord has either been confused by the silly SCSI numbering (while "dev=/dev/hdc" is not confusing at all, and uses the same device you use for mounting the thing etc).

Another is that several things did _not_ work well with ide-scsi. Some people ended up having to boot with ide-scsi enabled to burn CD's, but then if they wanted to watch DVD's (on the same drive), they needed to boot without it.

Quoted 2 lines

On every PC I have that has an ide cd drive, I use
ide-scsi. I like the fact that scd0 is the cdrom drive.

And you liked the fact that you were supposed to write "dev=0,0,0" or something strange like that? What a piece of crap it was.

Linus

#7 lore raw
Quoted 5 lines · Linus Torvalds
Quoted 2 lines

On every PC I have that has an ide cd drive, I use
ide-scsi. I like the fact that scd0 is the cdrom drive.

And you liked the fact that you were supposed to write "dev=0,0,0" or something strange like that? What a piece of crap it was.

Hey, that "piece of crap" has burned one heck of a lot of ISO images of Linux over the years. How about a nod of thanks to the author before you tell him you don't like his interface? And how about acknowledgement that he made that "piece of crap" work on a lot of different Unix platforms?

Signature · 2 lines
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm
#8 lore raw
Quoted 3 lines · Larry McVoy

Hey, that "piece of crap" has burned one heck of a lot of ISO images of Linux over the years.

And so does windows. That doesn't make it good.

Quoted 2 lines

How about a nod of thanks to the author before you tell him you don't like his interface?

I tried to tell him why numbers are bad. Very politely, explaining that a lot of devices cannot be enumerated by a traditional "bus/dev/lun" scheme. He basically cursed at me, and told me that that is how SCSI works. Never mind that IDE isn't SCSI, and even SCSI doesn't work that way any more (iSCSI comes to mind).

I can be polite. But when there is no reason to be polite, I can be blunt too.

Linus

#9 lore raw

#include <hallo.h>

Quoted 4 lines · Linus Torvalds
Quoted 2 lines

Hey, that "piece of crap" has burned one heck of a lot of ISO images of Linux over the years.

And so does windows. That doesn't make it good.

But somehow most Windows programers have easy way to deal with devices, they have clear paths to get hardware access where on Linux there is often something not thought out well which ruins your day. Examples?

If you have worked on a SCSI generic device and wish to get all the block devices associated with this one in upper level, how do you get that information? I tried to find a way a while ago and it simply sucked.

For details: http://bugs.debian.org/93633/ (CDROM TOC cache is not flushed on mount, kernel does not see new sessions on the disk). And don't tell me that I am stupid and I have simply to reject and reinsert the CD as everybody does. It is not mandatory on non-Linux, and why? ;) There must be a more simple way to flush the TOC cache in the block device driver (where it should not be located whatsoever, IMO).

Another example: how to get a list of module names for each module corresponding to drivers that have detected hardware? AFAICS there is no policy, no subsystem to manage this and there are no guidelines for the driver writers. The only thing you can do is looking around in procfs, guessing with some hocus pocus.

How to assign a network interface name when loading the NIC driver?

Quoted 5 lines
Quoted 2 lines

How about a nod of thanks to the author before you tell him you don't like his interface?

I tried to tell him why numbers are bad. Very politely, explaining that a lot of devices cannot be enumerated by a traditional "bus/dev/lun" scheme.

Imagine, there would be an internal mapping between devfs names and "bus/dev/lun" so cdrecord&Co. could query it to get the scsi-generic device name they need. There is almost always a way to a compromise.

Quoted 3 lines

He basically cursed at me, and told me that that is how SCSI works. Never mind that IDE isn't SCSI, and even SCSI doesn't work that way any more (iSCSI comes to mind).

Sorry, but if you drive SCSI protocols over IDE hardware, using the same terminology and the same control methods, why should it not be used as such? Or was it because Windows works that way so we should make it different (worse)?

Telling that someone is a dick is easy if you have the absolute power in your area of control, but listening to him and extracting good arguments may make sence sometimes.

MfG,
Eduard.

#10 lore raw
Quoted 4 lines · Eduard Bloch

But somehow most Windows programers have easy way to deal with devices, they have clear paths to get hardware access where on Linux there is often something not thought out well which ruins your day. Examples?

What? There _is_ a very well thought out way of accessing devices in UNIX. It is way superior to the mess that is windows. It is called a "device node", and a hypothetical program might use a syntax like this:

record dev=/dev/hdc

to access the device "/dev/hdc".

This is nothing new. This is how UNIX has worked for the last thirty years or so. It's not only quite readable, but because everybody uses device nodes the same way, it's consistent which makes it even more pleasant to use. So if you were to want to mount the thing you recorded, you'd use

mount /dev/hdc mntpoint

and notice how we used the same name again?

In contrast, the old cdrecord interfaces are an UNBELIEVABLE PILE OF CRAP! It's an interface that is based on some random hardware layout mechanism that isn't even TRUE any more, and hasn't been true for a long time. It's not helpful to the user, and it doesn't match how devices are accessed by everything else on the system.

It's bad from a technical standpoint (anybody who names a generic device with a flat namespace is just basically clueless), and it's bad from a usability standpoint. It has _zero_ redeeming qualities.

Linus

#11 lore raw
Quoted 9 lines

In contrast, the old cdrecord interfaces are an UNBELIEVABLE PILE OF CRAP! It's an interface that is based on some random hardware layout mechanism that isn't even TRUE any more, and hasn't been true for a long time. It's not helpful to the user, and it doesn't match how devices are accessed by everything else on the system.

It's bad from a technical standpoint (anybody who names a generic device with a flat namespace is just basically clueless), and it's bad from a usability standpoint. It has _zero_ redeeming qualities.

I think the appropriate phrase is "user malevolent" software. Making the user interface fit some arcane technica rather than the user is rather tragic. Reality is quite complicated enough as it is, without deliberately setting out to make it more so.

M.

#12 lore raw

dialectical deprecation Re: cdrecord hangs my computer

Quoted 12 lines · Martin J. Bligh
Quoted 11 lines

In contrast, the old cdrecord interfaces are an UNBELIEVABLE PILE OF CRAP! It's an interface that is based on some random hardware layout mechanism that isn't even TRUE any more, and hasn't been true for a long time. It's not helpful to the user, and it doesn't match how devices are accessed by everything else on the system.

It's bad from a technical standpoint (anybody who names a generic device with a flat namespace is just basically clueless), and it's bad from a usability standpoint. It has _zero_ redeeming qualities.

Quoted 8 lines

I think the appropriate phrase is "user malevolent" software. Making the user interface fit some arcane technica rather than the user is rather tragic. Reality is quite complicated enough as it is, without deliberately setting out to make it more so.

M.

Today I realize that it's not double deprecation, it's dialectical deprecation, for a user who gets caught between the deprecation of ide-scsi and cdrecord targbuslun "flat" naming and then the cdrecord error message when trying to use a full devpath. The user's head is volleyed back and forth as cdrecord maintains its "denial".

cdrecord whines about the full devpath in the first instance, will not work if I use 1,0,0 in both places, but seems to catch a clue about the devpath stub from the first instance in order to use its 1,0,0 nomenclature below that.

#/etc/default/cdrecord CDR_DEVICE=ATAPI:/dev/scsi/host1/bus0/target0/lun0/generic #ATAPI:1,0,0 won't work in CDR_DEVICE, but...
yamaha= ATAPI:1,0,0 -1 -1 ""

I'm scared(under-informed) to drop ide-scsi since I'm using 3ware and don't know if just scsi-generic would be enough for that hd controller(needs ide-scsi? 3ware's site doc is not easy to find).

-Bob

#13 lore raw

Re: dialectical deprecation Re: cdrecord hangs my computer

In article <[email protected]>, Bob <[email protected]> wrote:

| Today I realize that it's not double deprecation, it's dialectical
| deprecation, for a user who gets caught between the deprecation
| of ide-scsi and cdrecord targbuslun "flat" naming and then the
| cdrecord error message when trying to use a full devpath. The
| user's head is volleyed back and forth as cdrecord maintains
| its "denial".
| 
| cdrecord whines about the full devpath in the first instance,
| will not work if I use 1,0,0 in both places, but seems to
| catch a clue about the devpath stub from the first instance
| in order to use its 1,0,0 nomenclature below that.
| 
| #/etc/default/cdrecord
| CDR_DEVICE=ATAPI:/dev/scsi/host1/bus0/target0/lun0/generic
| #ATAPI:1,0,0 won't work in CDR_DEVICE, but...
| yamaha=   ATAPI:1,0,0   -1      -1      ""
| 
| I'm scared(under-informed) to drop ide-scsi since
| I'm using 3ware and don't know if just scsi-generic
| would be enough for that hd controller(needs ide-scsi?
| 3ware's site doc is not easy to find).

First, I would think you want the device with ATAPI, not the generic. I don't use that nomenclature so I may be misreading it. I have used plain /dev/hdc and had it work.

Second, did you use -scanbus to see which three numbers cdrecord wants with ide-scsi and try those? You don't want ATAPI in front of it, just dev=1,0,0 or similar.

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#14 lore raw

Re: dialectical deprecation Re: cdrecord hangs my computer

In reply to Bob

Bob, I don't believe that the 3ware card uses ide-scsi, yes it uses IDE drives and looks like a SCSI controller, but that's done in the 3ware driver, not by useing ide-scsi.

David Lang

Quoted 4 lines · Bob

I'm scared(under-informed) to drop ide-scsi since I'm using 3ware and don't know if just scsi-generic would be enough for that hd controller(needs ide-scsi? 3ware's site doc is not easy to find).

Signature · 3 lines
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
#15 lore raw

Re: dialectical deprecation Re: cdrecord hangs my computer

Quoted 9 lines · David Lang
Quoted 3 lines · Bob

I'm scared(under-informed) to drop ide-scsi since I'm using 3ware and don't know if just scsi-generic would be enough for that hd controller(needs ide-scsi? 3ware's site doc is not easy to find).

Bob, I don't believe that the 3ware card uses ide-scsi, yes it uses IDE drives and looks like a SCSI controller, but that's done in the 3ware driver, not by useing ide-scsi.

That is correct.

Signature · 2 lines
Måns Rullgård
[email protected]
#16 lore raw
In reply to Linus Torvalds

In article <[email protected]>, Linus Torvalds <[email protected]> wrote:

| In contrast, the old cdrecord interfaces are an UNBELIEVABLE PILE OF CRAP!
| It's an interface that is based on some random hardware layout mechanism
| that isn't even TRUE any more, and hasn't been true for a long time. It's
| not helpful to the user, and it doesn't match how devices are accessed by
| everything else on the system.
| 
| It's bad from a technical standpoint (anybody who names a generic device
| with a flat namespace is just basically clueless), and it's bad from a
| usability standpoint. It has _zero_ redeeming qualities.

And the redeeming features of naming disks, CDs, and ide-floppy devices hda..hdx in an order depending on the loading order of the device drivers?

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#17 lore raw
Quoted 8 lines · bill davidsen
|
| It's bad from a technical standpoint (anybody who names a generic device
| with a flat namespace is just basically clueless), and it's bad from a
| usability standpoint. It has _zero_ redeeming qualities.

And the redeeming features of naming disks, CDs, and ide-floppy devices hda..hdx in an order depending on the loading order of the device drivers?

.. but you can fix that. Several ways. Make up your own names. Make it have "/dev/the-cd-with-the-blue-faceplate" if you want, and it will all still work quite intuitively.

And when you switch the hardware around, and the CD-ROM breaks and you replace it with another one (still with a blue face-plate, just to not confuse the user unnecessarily, but this time it ends up being on another bus entirely), the "/dev/the-cd...-faceplate" thing still works with minimal effort on the admin part.

And it works in _all_ situations.

Sure, you can have all programs use their own random naming scheme and use .cdrecordrc and edit that instead, but then you have to remember to edit the .k3drc thing too, and the /etc/fstab, and so on and so on.

Isn't it saner to use a naming scheme that everybody can agree on, and that is generic enough that it really _does_ work for everybody, and that allows localised names?

Linus

#18 lore raw
Quoted 6 lines · Linus Torvalds
Quoted 5 lines · bill davidsen
|
| It's bad from a technical standpoint (anybody who names a generic device
| with a flat namespace is just basically clueless), and it's bad from a
| usability standpoint. It has _zero_ redeeming qualities.
Quoted 7 lines
Quoted 3 lines

And the redeeming features of naming disks, CDs, and ide-floppy devices hda..hdx in an order depending on the loading order of the device drivers?

.. but you can fix that. Several ways. Make up your own names. Make it have "/dev/the-cd-with-the-blue-faceplate" if you want, and it will all still work quite intuitively.

Actually my point was that you were pretty harsh about Joerg's naming scheme, and the default in Linux is also less than perfect. As you note these can be fixed, and in current versions of cdrecord after they are fixed you can use them.

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#19 lore raw
In reply to bill davidsen
Quoted 3 lines · On Mon, 08 Dec 2003 16:21:54 GMT, [email protected] (bill davidsen) said:

And the redeeming features of naming disks, CDs, and ide-floppy devices hda..hdx in an order depending on the loading order of the device drivers?

Amen.

At least when network interfaces do it, I can use 'nameif' to beat them into submission.

#20 lore raw
Quoted 5 lines · On Mon, 8 Dec 2003 [email protected] wrote:

Amen.

At least when network interfaces do it, I can use 'nameif' to beat them into submission.

What's _wrong_ with you people?

The reason you need 'nameif' for network devices is that the kernel actually cares about them. But for normal device nodes, you have thousands of tools to rename them, and you can have a million different names for the same thing if you want to.

Valdis: for /dev/hdxx, you can rename it with such esoteric programs as 'mv', 'ln', 'perl', 'cp', 'mknod', 'emacs', and a few hundred others. What is your beef with it?

In fact, every distribution I know of comes with it already aliased to /dev/cdrom, without you having to lift a pinky to do _anything_ about it.

And quite frankly, anybody who finds

cdrecord dev=/dev/cdrom

less intuitive than

	cdrecord dev=1,0,0

is so drugged and mindwashed by the cdrecord authors that it's not even funny any more.

So stop spreading this incredible crap, guys. How about you just admit that I was right. If that's hard to do, add a comment like

"Just this once Linus happened to pick a winner. Incredible, but it
was probably just a fluke. He's still a drugged-out idiot most of the time."

to make it feel a bit better.

Linus

#21 lore raw
Quoted 3 lines · Linus Torvalds

Valdis: for /dev/hdxx, you can rename it with such esoteric programs as 'mv', 'ln', 'perl', 'cp', 'mknod', 'emacs', and a few hundred others. What is your beef with it?

The difference is that with nameif, I can feed it the MAC address and use that as a "find this interface" key. And given that at the moment, my lap top has *4* ethernet devices (an onboard one, one in the docking station, a wireless card, and one that happens to be be on a Xircom modem card), it's really handy to be able to be able to nail down the names.

Yes, there's 3 zillion ways to rename the device, once I figure out what it's
name *is*. Currently, my machine has a nice symlink set up:

% ls -l /dev/cdroms/
total 0
0 lr-xr-xr-x 1 root root 33 Dec 31 1969 cdrom0 -> ../ide/host0/bus0/target1/lun0/cd

which devfs was nice enough to do. My beef is that if I had 2 cdroms, then there's no guarantee of stability for cdrom0/cdrom1, and unlike the nameif example, there's no really good way to deal with it (especially when you start dealing with hotplug devices).

Or as another poster commented, it's easy to use /dev/cdrom-blue-faceplate once you make it a symlink to the right place. It's getting that symlink into place that's the fun part. I admit I haven't looked at the udev stuff - is it able to look closely enough at devices to do things like "I want the Mitsubishi CDrom to be cdrom0 and the FireWire/USB/whatever to be cdrom1 if it's my Fujitsu, but call it cdrom2 otherwise"? If so, then I don't have a beef with it... ;)

The stuff that supports LABEL= on a partition is a *partial* solution to decouple the name of the device as the system found it from a logical name, but as many have noted, it has its own issues.

#22 lore raw
Quoted 3 lines · [email protected] writes:

The stuff that supports LABEL= on a partition is a *partial* solution to decouple the name of the device as the system found it from a logical name, but as many have noted, it has its own issues.

Yes, labels and UUIDs are great for those of us with lots of SCSI devices, so that adding a controller or changing a cable doesn't require _two_ boots (one to figure out where everything went and edit /etc/fstab, one for real).

I wish I could LABEL swap partitions.

Ian

#23 lore raw
Quoted 6 lines · Ian Soboroff
Quoted 3 lines · [email protected] writes:

The stuff that supports LABEL= on a partition is a *partial* solution to decouple the name of the device as the system found it from a logical name, but as many have noted, it has its own issues.

Quoted 6 lines

Yes, labels and UUIDs are great for those of us with lots of SCSI devices, so that adding a controller or changing a cable doesn't require _two_ boots (one to figure out where everything went and edit /etc/fstab, one for real).

I wish I could LABEL swap partitions.

In March 2001 I posted a patch for util-linux to support that:
http://www.csd.uu.se/~mikpe/linux/swap-label/swap-label-patch-2001-03-15

There was only minor interest in the thing, so I've not pursued it any further.

#24 lore raw
In reply to Larry McVoy
Quoted 12 lines · Larry McVoy
Quoted 8 lines · Linus Torvalds
Quoted 4 lines

On every PC I have that has an ide cd drive, I use
ide-scsi. I like the fact that scd0 is the cdrom drive.

And you liked the fact that you were supposed to write "dev=0,0,0" or something strange like that? What a piece of crap it was.

Quoted 6 lines

Hey, that "piece of crap" has burned one heck of a lot of ISO images of Linux over the years. How about a nod of thanks to the author before you tell him you don't like his interface? And how about acknowledgement that he made that "piece of crap" work on a lot of different Unix platforms?

Naming "1,0,0" won't work everywhere for me.

I started using a 3ware ide card because promise and siig sis were crashing nforce2, so it's a unified concept ;-) to use ide-scsi scsi-sg for hd's on 3ware and for cdr cdrw. I can rip from cdr through pipes to yamaha cdrw, pre-emptive kernel, anticipatory sched, use dma, devfs. The only quirk is naming "1,0,0" won't work everywhere--

#/etc/default/cdrecord CDR_DEVICE=ATAPI:/dev/scsi/host1/bus0/target0/lun0/generic # ATAPI:1,0,0 won't work in CDR_DEVICE but below it does--
yamaha= ATAPI:1,0,0 -1 -1 ""

#/usr/src/linux/.config--
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_IDEDISK is not set
# CONFIG_BLK_DEV_IDECS is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=y

# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs #
CONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_REPORT_LUNS is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
CONFIG_BLK_DEV_3W_XXXX_RAID=y

-Bob D

#25 lore raw
Quoted 7 lines · Bob
Quoted 5 lines · Larry McVoy

Hey, that "piece of crap" has burned one heck of a lot of ISO images of Linux over the years. How about a nod of thanks to the author before you tell him you don't like his interface? And how about acknowledgement that he made that "piece of crap" work on a lot of different Unix platforms?

Naming "1,0,0" won't work everywhere for me.

You're missing my point. I was not claiming that cdrecord's naming scheme was great and I'm still not claiming that. I was objecting to what I saw as a needless slam on someone who has produced a useful tool, maintained it for years, and we've all used it for years.

Personally, I think a

The cdrecord naming scheme is broken, we aren't going to support it.

would have been enough. Maybe Linus has some issues with the author but that's no excuse to be that rude. I'm a little tired of this mailing list hammering on people more than is needed.

Signature · 2 lines
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm
#26 lore raw
In reply to Linus Torvalds
Quoted 9 lines
Quoted 2 lines

At the moment, I don't have a burner on a 2.6.0 machine, however, why is ide-scsi depreciated?

Several reasons.

One is just plain confusion - anybody who uses cdrecord has either been confused by the silly SCSI numbering (while "dev=/dev/hdc" is not confusing at all, and uses the same device you use for mounting the thing etc).

Actually, itwould be nice if I could use dev=/dev/scd0. I do have a scsi burner (and an ide one too)

Quoted 4 lines

Another is that several things did _not_ work well with ide-scsi. Some people ended up having to boot with ide-scsi enabled to burn CD's, but then if they wanted to watch DVD's (on the same drive), they needed to boot without it.

The joys of modules =)

Quoted 5 lines
Quoted 2 lines

On every PC I have that has an ide cd drive, I use
ide-scsi. I like the fact that scd0 is the cdrom drive.

And you liked the fact that you were supposed to write "dev=0,0,0" or something strange like that? What a piece of crap it was.

I have it named using cdrecord's defaults. People who have real scsi burners still have to use that format.

Signature · 1 line
 Lab tests show that use of micro$oft causes cancer in lab animals
#27 lore raw
Quoted 2 lines · Linus
Quoted 2 lines

And you liked the fact that you were supposed to write "dev=0,0,0" or something strange like that? What a piece of crap it was.

Quoted 2 lines · Wakko Warner

I have it named using cdrecord's defaults. People who have real scsi burners still have to use that format.

Since I appear to be one of the very few who have a SCSI burner around, I might as well chime in. ISTR being able to use dev=/dev/scd0 at some point, though axboe might know more (I'm pretty much at an end-user level on these kinds issues for the moment).

-- wli

#28 lore raw
In reply to Wakko Warner
Quoted 8 lines · Wakko Warner
Quoted 5 lines

One is just plain confusion - anybody who uses cdrecord has either been confused by the silly SCSI numbering (while "dev=/dev/hdc" is not confusing at all, and uses the same device you use for mounting the thing etc).

Actually, it would be nice if I could use dev=/dev/scd0. I do have a scsi burner (and an ide one too)

It _should_ just work these days. Anything that uses "cdrom_ioctl()" should automatically get the SCSI command translation code (which isn't part of the scsi driver).

But hey, the scsi layer confuses me. Less than it used to, but still.

Linus

#29 lore raw
In reply to Linus Torvalds

In article <[email protected]>, Linus Torvalds <[email protected]> wrote:

| >		 On every PC I have that has an ide cd drive, I use
| > ide-scsi.  I like the fact that scd0 is the cdrom drive.
| 
| And you liked the fact that you were supposed to write "dev=0,0,0" or
| something strange like that? What a piece of crap it was.

Actually, dev=0,0,0 or dev=/dev/hdc are neither particularly portable;
each can be something else on another machine. At least /dev/sr0 (or scd0 if you go to that church) are a bit less likely to change.

Joerg made the point at one time that the 0,0,0 notation will allow
use of devices with no inode. That's not been useful to me, but it's probably true ;-)

If I were going to do that at all, I would have used controller, bus,
device, LUN notation, (0,0,0,0) and been done with it. Joerg marches to the beat of another drummer, however, maybe even a whole other brass band. He wrote it, he invites people to not use it if they don't like it, which I've heard in other contexts. ;-)

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#30 lore raw
Quoted 9 lines · bill davidsen

In article <[email protected]>, Linus Torvalds <[email protected]> wrote:

|
| And you liked the fact that you were supposed to write "dev=0,0,0" or
| something strange like that? What a piece of crap it was.

Actually, dev=0,0,0 or dev=/dev/hdc are neither particularly portable;
each can be something else on another machine. At least /dev/sr0 (or scd0 if you go to that church) are a bit less likely to change.

Actually, the sane thing to do is to use "/dev/cdrom", which is likely to be right, and if it isn't, you can always fix it (and you can fix it _dynamically_ with something like "udev" - so it will do the right thing even if your cdrom happens to be hot-pluggable).

The only time that ends up being confusing is if you have multiple CD-roms (which used to be common - DVD reader and CD writer - but is going away again on "normal" machines due to combo drives). And then you really actually care about position, so then you are likely happy to go back to "/dev/hdc" or "/dev/usb-cdrom" or something like that to specify _which_ CD-RW you're talking about.

Quoted 2 lines

If I were going to do that at all, I would have used controller, bus,
device, LUN notation, (0,0,0,0) and been done with it.

Well, even that isn't enough.

What's the format for iSCSI? What's the format for buses that are hierarchical? The thing is, naming is _hard_, and the only way to name things in a generic manner is:
- allow multiple levels (ie not a fixed "always 3/4 levels" format)
- don't use numbers (part of the name might be a hostname or whatever).

Which means that you have to have names that are (a) hierarchical and (b) strings as the individual path components.

In addition, you clearly _do_ want to have the "simplified" form (aka the "just point me to the 'cdrom', dammit!" format). Because quite frankly, the regular user that doesn't care, doesn't really want to know how his (single) CD-ROM is connected, and if he has to look it up he'll have all the right in the world to say "This computer is _stupid_".

And guess what you end up with if you have these requirements? A filesystem. No, "/dev/cdrom" and "/dev/iscsi/cdrom.work.com/cd5" aren't the _only_ ways of naming things, but they are clear, and they are sufficient.

And "0,0,0,0" fails _both_ of these obvious requirements. It's neither clear _nor_ sufficient.

Linus

#31 lore raw

bluefaceplate demographics Re: cdrecord hangs my computer

#/etc/default/cdrecord
#works--
CDR_DEVICE=ATAPI:/dev/bluefaceplate #ATAPI:1,0,0 not working due to devfs stub diff

but then Joerg's revenge is to gain political leverage by recruiting neophytes who can't configure options on the command line(!aliased, !scripted) so they love Joerg if his default works--and for second-degree neophytes who can edit config files, default opts config won't take bluefaceplate(explicit devpath) nomenclature! --targbuslun only(can ide-cd do this ATAPI:1,0,0?)!--

# drive name    device  speed   fifosize driveropts
#
teac=           1,3,0   -1      -1      ""
panasonic=      1,4,0   -1      -1      ""
plextor=        1,4,0   -1      -1      ""
sanyo=          1,4,0   -1      -1      burnfree
# will ide-cd work here?---
yamaha=   ATAPI:1,0,0   -1      -1      ""
cdrom=          0,6,0    2      1m      ""

-Bob D

Quoted 28 lines · Linus Torvalds
Quoted 11 lines · bill davidsen

In article <[email protected]>, Linus Torvalds <[email protected]> wrote:

|
| And you liked the fact that you were supposed to write "dev=0,0,0" or
| something strange like that? What a piece of crap it was.

Actually, dev=0,0,0 or dev=/dev/hdc are neither particularly portable;
each can be something else on another machine. At least /dev/sr0 (or scd0 if you go to that church) are a bit less likely to change.

Actually, the sane thing to do is to use "/dev/cdrom", which is likely to be right, and if it isn't, you can always fix it (and you can fix it _dynamically_ with something like "udev" - so it will do the right thing even if your cdrom happens to be hot-pluggable).

The only time that ends up being confusing is if you have multiple CD-roms (which used to be common - DVD reader and CD writer - but is going away again on "normal" machines due to combo drives). And then you really actually care about position, so then you are likely happy to go back to "/dev/hdc" or "/dev/usb-cdrom" or something like that to specify _which_ CD-RW you're talking about.

#32 lore raw
In reply to Ethan Weinstein
Quoted 5 lines · Ethan Weinstein

I've noted this at boot several times with 2.6.0-test11

Dec  4 23:59:21 e-d0uble kernel: ide-scsi is deprecated for cd burning!

Use ide-cd and give dev=/dev/hdX as device

Yup.

Quoted 4 lines

Removing the ide-cd bootparams: (I didn't try the patch)

Cdrecord 2.00.3 seems to like the sony-dru500a, denoted as --dev=/dev/hdc, I burned several disks this way.

Good. However, I'd still like to hear if ide-scsi.c works with the patch:
it's deprecated and I don't actually encourage people to use it, but it would be interesting to hear whether it works for people..

Linus