Firewire CD-RW...

[bruce woller]

On Monday, June 2, 2003, at 05:19  PM, Dylan wrote:
> scsi singledevice 1 0 7 0
>
> Do you know what the 'scsi singledevice xxxx' is?  It didn't show up 
> before.
>
> Dylan

the rescan-scsi-bus.sh script calls 'scsi single device program to 
detect each scsi address individually.  e.g.

> scsi singledevice 1 0 7 0
                                     |  |  |  |
                                     |  |  |  |
                                     |  |  |  > LUN 0
                                     |  |  >TARGET 7
                                     |  >BUS TENANT 0
                                     >BUS 1
for example I have two Adaptec SCSI cards in my system on BUS 2 and 3 :

scsi2 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
         <Adaptec 2902/04/10/15/20/30C SCSI adapter>
         aic7850: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs

scsi3 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
         <Adaptec 2940B Ultra2 SCSI adapter>
         aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs

The SCSI emulation of the ide controller shows up on BUS 0.  Apple 
hardware has always had a SCSI Bus (I think OS 9 really needs to see a 
SCSI bus) so a dummy bus is built into motherboards since the G3 B&W 
(when SCSI disappeared as a standard bus from Apple hardware).  It is 
called MESH.  Don't ask me why.
> SCSI subsystem driver Revision: 1.00
> scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> mesh: configured for synchronous 5 MB/s
> mesh: performing initial bus reset...
> scsi1 : MESH


Here is output from dmesg on my machine:
<snip>
> input2: USB HID v10.01 Mouse [Logitech USB Receiver] on usb1:3.0
>   Vendor: UMAX      Model: Astra 2200        Rev: V2.3
>   Type:   Scanner                            ANSI SCSI revision: 02
> blk: queue c0f49874, I/O limit 4095Mb (mask 0xffffffff)
>   Vendor: QUANTUM   Model: ATLAS10K3_18_WLS  Rev: 020W
>   Type:   Direct-Access                      ANSI SCSI revision: 03
> blk: queue c0f49a74, I/O limit 4095Mb (mask 0xffffffff)
>   Vendor: QUANTUM   Model: ATLAS10K3_18_WLS  Rev: 020W
>   Type:   Direct-Access                      ANSI SCSI revision: 03
> blk: queue c0f49b74, I/O limit 4095Mb (mask 0xffffffff)
> scsi3:A:0:0: Tagged Queuing enabled.  Depth 253
> scsi3:A:1:0: Tagged Queuing enabled.  Depth 253
> Attached scsi generic sg0 at scsi2, channel 0, id 5, lun 0,  type 6
> Attached scsi disk sda at scsi3, channel 0, id 0, lun 0
> Attached scsi disk sdb at scsi3, channel 0, id 1, lun 0
> (scsi3:A:0): 80.000MB/s transfers (40.000MHz, offset 127, 16bit)
> SCSI device sda: 35916548 512-byte hdwr sectors (18389 MB)
>  sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 
> sda12
> (scsi3:A:1): 80.000MB/s transfers (40.000MHz, offset 127, 16bit)
> SCSI device sdb: 35916548 512-byte hdwr sectors (18389 MB)
>  sdb: [mac] sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9 sdb10
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> Freeing unused kernel memory: 172k init 8k chrp 8k prep
> EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,10), internal journal
> Adding Swap: 786424k swap-space (priority -1)
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,9), internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> i2c-core.o: i2c core module
> i2c-algo-bit.o: i2c bit algorithm module
> PCI: Enabling device 01:00.0 (0014 -> 0016)
> pcilynx0: allocated PCL memory 4096 Bytes @ 0xef195000
> pcilynx0: allocated interrupt 21
> pcilynx0: remapped memory spaces reg 0xf2251000, rom 0xf2275000, ram 
> 0xf2253000, aux 0xf2264000
> pcilynx0: found 1394a conform PHY (using extended register set)
> pcilynx0: PHY vendor id 0x080028
> pcilynx0: PHY product id 0x000000
> i2c-core.o: adapter PCILynx I2C adapter registered as adapter 0.
> pcilynx0: got bus info block from serial eeprom
> pcilynx0: read a valid bus info block from
> i2c-core.o: adapter unregistered: PCILynx I2C adapter
> pcilynx0: resetting bus on request
> pcilynx0: bus reset interrupt
> pcilynx0: SelfID process finished (phyid 2, root)
> pcilynx0: SelfID packet 0x807f8094 rcvd
> pcilynx0: SelfID packet 0x813f846c rcvd
> pcilynx0: SelfID packet 0x82478c76 rcvd
> ieee1394: Device added: Node[00:1023]  GUID[000000000000b486]  
> [Unknown]
> ieee1394: Host added: Node[02:1023]  GUID[0000000000000000]  [TEXAS 
> INSTRUMENTS]
> ieee1394: sbp2: Error logging into SBP-2 device - login timed-out
> ieee1394: sbp2: sbp2_login_device failed
> scsi4 : IEEE-1394 SBP-2 protocol driver (host: pcilynx)
> $Rev: 584 $ James Goodwin <jamesg@filanet.com>
> SBP-2 module load options:
> - Max speed supported: S400
> - Max sectors per I/O supported: 255
> - Max outstanding commands supported: 8
> - Max outstanding commands per lun supported: 1
> - Serialized I/O (debug): no
> - Exclusive login: yes
> ip_tables: (C) 2000-2002 Netfilter core team
> irda_setup timed out on 1st byte
> usb.c: registered new driver usblp
> printer.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 
> vid 0x04B8 pid 0x0005
> printer.c: v0.11: USB Printer Device Class driver

When I run rescanscsibus the sbp2 driver scsi emulation shows up as 
scsi4.  Alas, like you I cannot mount my CD-RW drive.  Seeing your 
later posts it seems that you are now very close to success.  I have 
tried downloading the subversion tarball of the latest 
/drivers/ieee1394 directory (trunk) and recompiling all modules but I 
get missing include files.  The notes on the ieee1394  web site say 
that the subversion tree is only for 2.5 kernels.  Didn't I see a post 
that said someone was using this with 2.4.20?

Regards,
Bruce