Jani, Jens, Matt, Eamon & Jakub,
   Thanks for your help so far. I think I'm closer, but for some reason
it's still not working for me. Maybe it's my kernel SCSI options? Maybe
it's a modules.conf setting? Maybe it's something under /etc/hotplug?
I'm not clear yet what is happening, but there is a little life.

   Sorry for this being long. I've opted to put in more info vs. less in
the hopes someone will see the error of my ways.

On Tue, 2004-01-20 at 12:22, Jani-Matti H�tinen wrote:
> On Tuesday 20 January 2004 20:12, Mark Knecht wrote:
> > Hi,
> >    If I use a grub boot option like hdc=ide-scsi, then what /dev device do
> > I mount in fstab to use the device?
> 
> It'll be the first device on the scsi bus. (Assuming that you don't have other 
> scsi devices) It'll be somewhere in /dev/scsi/. Can't remember it anymore, 
> since I've switched to atapi writing.

Immediately after booting in the following manner

title Gentoo Linux 2.4.22r2
root (hd0,5)
kernel (hd0,5)/boot/bzImage-2.4.22r2 ro root=/dev/hda7 hdc=ide-scsi
hdd=ide-scsi

if I look in /dev/scsi

Wizard root # ls /dev/scsi
Wizard root # 

However, if at this point I run cdrecord -scanbus the devices are found:

Wizard root # cdrecord -scanbus
Cdrecord-Clone 2.01a23-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2003
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
<[EMAIL PROTECTED]>.
Note: The author of cdrecord should not be bothered with problems in
this version.
Linux sg driver version: 3.1.25
Using libscg version 'schily-0.7'.
scsibus0:
        0,0,0     0) 'LITE-ON ' 'DVDRW LDW-411S  ' 'FS0B' Removable
CD-ROM
        0,1,0     1) 'LITE-ON ' 'LTR-48246S      ' 'SS0B' Removable
CD-ROM
        0,2,0     2) *
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) *
        0,6,0     6) *
        0,7,0     7) *
Wizard root # 


and stuff is created under /dev/scsi:

Wizard root # ls /dev/scsi
host0
Wizard root # 

as well as two new devices show up in /dev:

Wizard root # ls -al /dev/sg*
/dev/sg0 -> scsi/host0/bus0/target0/lun0/generic
/dev/sg1 -> scsi/host0/bus0/target1/lun0/generic

/dev/sg:
total 0
c0b0t0u0 -> ../scsi/host0/bus0/target0/lun0/generic
c0b0t1u0 -> ../scsi/host0/bus0/target1/lun0/generic
Wizard root # 

People have talked about, and I see it in devfsd.conf that somethign
called sr0 and sr1 should be created, but they are not so far.

Trying to mount /dev/sg1 doesn't work:

Wizard root # mount /dev/sg1 -t iso9660 /mnt/cdrom
mount: /dev/sg1 is not a block device
Wizard root # 


> >    Do I need to make any changes at all in /etc/devfsd.conf to make this
> > work?
> 
> There's a section in the default devfsd.conf which creates the /dev/cdrw 
> symlink for the first device in the scsi bus. Uncomment it and edit it do 
> your needs. (You might, for example switch it to /dev/dvdrw for sake of 
> clarity) You should, of course also edit the relevant line in fstab.
>   If you have two devices in the scsi bus (e.g. a dvd-rw and a cd-rw drive) 
> you can just copy and paste the /dev/cdrw section in devfsd.conf and edit it 
> for the second drive. (The syntax should be fairly straightforward) You might 
> also consider editing the sections which create the /dev/cdrom and /dev/dvd 
> symlinks to point to the right drives in the scsi bus. That way apps like 
> mplayer or ogle will find the devices without any extra options.


Here is what I currently have in devfsd.conf. It looks right to me, but
I'm probably missing something stupid:

# Create /dev/cdrom for the first cdrom drive
LOOKUP          ^cdrom$          CFUNCTION GLOBAL mksymlink
cdroms/cdrom1 cdrom
REGISTER        ^cdroms/cdrom1$   CFUNCTION GLOBAL mksymlink $devname
cdrom
UNREGISTER      ^cdroms/cdrom1$   CFUNCTION GLOBAL unlink cdrom

# Create /dev/dvd for the second cdrom drive
# (change 'cdroms/cdrom1' to suite your setup)
# NOTE: We add the fully qualified path here, else some apps
#       have problems to resolve the true device (drip comes to mind)
LOOKUP          ^dvd$           CFUNCTION GLOBAL mksymlink
${mntpnt}/cdroms/cdrom0 dvd
REGISTER        ^cdroms/cdrom0$  CFUNCTION GLOBAL mksymlink ${devpath}
dvd
UNREGISTER      ^cdroms/cdrom0$  CFUNCTION GLOBAL unlink dvd

# Create /dev/cdrw for the second cdrom on the scsi bus
# (change 'sr0' to suite your setup)
LOOKUP          ^cdrw$          CFUNCTION GLOBAL mksymlink sr1 cdrw
REGISTER        ^sr1$           CFUNCTION GLOBAL mksymlink $devname cdrw
UNREGISTER      ^sr1$           CFUNCTION GLOBAL unlink cdrw

# Create /dev/dvd1 for the first cdrom on the scsi bus
# (change 'sr0' to suite your setup)
LOOKUP          ^dvd1$          CFUNCTION GLOBAL mksymlink sr0 dvd1
REGISTER        ^sr0$           CFUNCTION GLOBAL mksymlink $devname dvd1
UNREGISTER      ^sr0$           CFUNCTION GLOBAL unlink dvd1

Do the srX names really need to sgX names? I just thought of that
possibility.

Kernel is 2.4.22-r2 Loaded modules at this point are:

Wizard root # lsmod
Module                  Size  Used by    Not tainted
ide-scsi                9936   0  (autoclean)
sg                     27580   0  (autoclean)
i2c-proc                6452   0 
i2c-core               15300   0  [i2c-proc]
<SNIP>
sbp2                   17748   0  (unused)
scsi_mod               87296   2  [ide-scsi sg sbp2]
raw1394                19608   0  (unused)
ohci1394               26128   0  (unused)
ieee1394               47940   0  [sbp2 raw1394 ohci1394]
hid                    16036   1 
Wizard root # 


Anyway, thanks for going through this with me. I think it's pretty
close.

With best regards,
Mark


--
[EMAIL PROTECTED] mailing list

Reply via email to