[SOLVED] 8 icons for 1 DVD-ROM

[rmb]

I installed Wolvix 1.1 on a Gateway 200-STM.  The desktop displays 8 CD-ROM icons, but I only have one DVD-ROM.  This is the output from dmesg:

scsi 2:0:1:0: CD-ROM            TOSHIBA  DVD-ROM SD-R2312 1707 PQ: 0 ANSI: 0
sr1: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
sr 2:0:1:0: Attached scsi CD-ROM sr1
sr 2:0:1:0: Attached scsi generic sg1 type 5
scsi 2:0:2:0: CD-ROM            TOSHIBA  DVD-ROM SD-R2312 1707 PQ: 0 ANSI: 0
sr2: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
sr 2:0:2:0: Attached scsi CD-ROM sr2
sr 2:0:2:0: Attached scsi generic sg2 type 5
scsi 2:0:3:0: CD-ROM            TOSHIBA  DVD-ROM SD-R2312 1707 PQ: 0 ANSI: 0
sr3: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
sr 2:0:3:0: Attached scsi CD-ROM sr3
sr 2:0:3:0: Attached scsi generic sg3 type 5
scsi 2:0:4:0: CD-ROM            TOSHIBA  DVD-ROM SD-R2312 1707 PQ: 0 ANSI: 0
sr4: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
sr 2:0:4:0: Attached scsi CD-ROM sr4
sr 2:0:4:0: Attached scsi generic sg4 type 5
scsi 2:0:5:0: CD-ROM            TOSHIBA  DVD-ROM SD-R2312 1707 PQ: 0 ANSI: 0
sr5: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
sr 2:0:5:0: Attached scsi CD-ROM sr5
sr 2:0:5:0: Attached scsi generic sg5 type 5
scsi 2:0:6:0: CD-ROM            TOSHIBA  DVD-ROM SD-R2312 1707 PQ: 0 ANSI: 0
sr6: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
sr 2:0:6:0: Attached scsi CD-ROM sr6
sr 2:0:6:0: Attached scsi generic sg6 type 5
scsi 2:0:7:0: CD-ROM            TOSHIBA  DVD-ROM SD-R2312 1707 PQ: 0 ANSI: 0
sr7: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
sr 2:0:7:0: Attached scsi CD-ROM sr7
sr 2:0:7:0: Attached scsi generic sg7 type 5

Will the real icon please stand up?

How can I get rid of 7 imposters?  I didn't find any similar problem in the forums.  I don't know how to research the problem, because I don't know what the problem is.  Any help would be very much appreciated.

rmb

[rmb]

Well, I'm not the brightest star in the sky, but I found two solutions for this annoyance.

After searching Google for some time, I stumbled across a reference to a file named rc.scanluns, which Wolvix places in the  /etc/rc.d directory.

First solution:  I moved the rc.scanluns script to a pen drive, and rebooted.  The result:

Code:

rmb wolvix ~ $ cat /proc/scsi/scsi
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: TOSHIBA  Model: DVD-ROM SD-R2312 Rev: 1707
  Type:   CD-ROM                           ANSI  SCSI revision: 00

After reading the script I found the second solution.  One of the comments in the script said:

Code:

#Run this only if "noscanluns" was NOT given as a kernel option.

So I added "noscanluns" as a kernel option and rebooted with same result.

I don't know how important the rc.scanluns script is (SLAX doesn't use it), but I decided to be safe and keep the script and use the "noscanluns" option.

[Wolven]

Good work figuring this out. I'm not sure where the rc.scanluns, script comes from, but it has to be from Slackware, or from one of the package I've built. Looking at my current /etc/rc.d/ directory I see that I don't have a rc.scanluns file. I'll keep an eye out for this in future releases.

[martinultima]

rc.scanluns is from the Slackware sysvinit-scripts package; it's used to detect SCSI devices (including "real" SCSI, SATA, and SCSI-emulation such as USB drives) that may not have been correctly configured during startup.  Most systems don't need it to function, and in cases like yours, it can be a genuine hindrance.

If noscanluns works, great   You can also disable it by changing the file permissions: sudo chmod a-x /etc/rc.d/rc.scanluns
That same trick works with any other Slackware init scripts; anything marked executable (chmod a+x) will be started, otherwise it's silently ignored.

@ Wolven -- the rc.scanluns script should be safe to leave in.  I usually disable it on my own systems, because I personally have no use for it, but it may not be a bad idea since some configurations actually may need it (offhand I don't know).

[rmb]

Thanks, martinultima, for the suggestion to change file permission. I had not thought of that.

[martinultima]

Thanks, martinultima, for the suggestion to change file permission. I had not thought of that.

No problem.  A king developer has to know these things