> I have a scsi card with a cd-rom and a scanner. And I also have a
> ide cdrecorder.
>
> I have compiled in support for scsi-emulution, and scsi-cdrom and
generic
> scsi support.
>
have you also compiled in SCSI support layer as module?
> When I start up the machine I get:
>
> SCSI subsystem driver Revision: 1.00
> scsi0 : AM53/79C974 PCscsi driver rev. 0.5; host I/O address: 0xc800;
irq:
> 18
>
> Vendor: HP Model: C2500A Rev: 3332
> Type: Processor ANSI SCSI revision: 02
> Vendor: PLEXTOR Model: CD-ROM PX-40TS Rev: 1.05
> Type: CD-ROM ANSI SCSI revision: 02
> scsi1 : SCSI host adapter emulation for IDE ATAPI devices
> Vendor: SAMSUNG Model: CD-R/RW SW-212B Rev: P000
> Type: CD-ROM ANSI SCSI revision: 02
> Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
> Attached scsi CD-ROM sr1 at scsi1, channel 0, id 2, lun 0
> sr0: scsi-1 drive
> Uniform CD-ROM driver Revision: 3.12
> sr1: scsi3-mmc drive: 8x/32x writer cd/rw xa/form2 cdda tray
> Attached scsi generic sg0 at scsi0, channel 0, id 2, lun 0, type 3
^^^^^^^^^^^^^^^^^^^^^^
what cat /proc/scsi/scsi shows? This is funny, sr driver detects
scsi0/target3 and scsi1/target2 but sg driver scsi1/target2 ??? Could
you please give the full dmesg output.
>
> if I run
>
> cdrecord --scanbus
>
> I get:
>
> Cdrecord 1.11a24 (i586-mandrake-linux-gnu) Copyright (C) 1995-2002
J�rg
> Schilling
> Linux sg driver version: 3.1.24
> Using libscg version 'schily-0.6'
> scsibus0:
> 0,0,0 0) *
> 0,1,0 1) *
> 0,2,0 2) *
> 0,3,0 3) 'PLEXTOR ' 'CD-ROM PX-40TS ' '1.05' Removable
CD-ROM
even more funnier. According to above output this does not exist.
> 0,4,0 4) *
> 0,5,0 5) *
> 0,6,0 6) *
> 0,7,0 7) *
>
>
> My scanner and My ide cd-burner disapear after a while.
>
I do not see any scanner in output you quoted.
> If I instead compile all scsi things as modules it works just after I
have
> loaded the modules so I have to load and unload the modules all the
time.
>
> Is this something due to devfs ? How can I solve this?
>
Excellent! May I ask people - PLEASE before accounting every possible
bug to devfs - just boot without devfs and see if bug is still there.
And you do not even mention your kernel version anywhere still start
with assumption devfs is buggy.
-andrej