Hi Juergen,
The driver shouldn't be the problem. I made the same test with the DC395 AND
(!) with a
Adaptec Driver. When manually selecting the SCSI Driver it's the same as the
DC395.
There is a module not loaded I think. look at the test I have done with the
adaptec driver:
[...]
When choosing expert at the boot: The tty5 shows following:
testing for /modules/cdrom.o
not found /modules/cdrom.o
try with /tmp/cdrom.o
testing for /modules/ide-cd.o
not found /modules/ide-cd.o
try with /tmp/ide-cd.o
testing for /modules/scsi_mod.o
not found /modules/scsi_mod.o
try with /tmp/scsi_mod.o
testing for /modules/aic7xxx.o
not found /modules/aic7xxx.o
try with /tmp/aic7xxx.o
But when choosing "standard" the SCSI Controller is found
automatically and it looks like this:
testing for /modules/ide-cd.o
not found /modules/ide-cd.o
try with /tmp/ide-cd.o
testing for /modules/scsi_mod.o
not found /modules/scsi_mod.o
try with /tmp/scsi_mod.o
testing for /modules/aic7xxx.o
not found /modules/aic7xxx.o
try with /tmp/aic7xxx.o
testing for /modules/cdrom.o
not found /modules/cdrom.o
try with /tmp/cdrom.o
insmod: a module named cdrom already exists
testing for /modules/scsi_mod.o
not found /modules/scsi_mod.o
try with /tmp/scsi_mod.o
insmod: a module named scsi_mod already exists
testing for /modules/sr_mod.o
not found /modules/sr_mod.o
try with /tmp/sr_mod.o
Could it be that this last module is missing when starting it
in the expert mode and you choose the SCSI Controlle manually ?
[...]
As you can see "sr_mod.o" is not loaded when choosing the expert way.
On the standard way the sr_mod.o will be loaded (But only on automatical
found SCSI Drivers, like the adaptec. At the DC395 we have a problem :-( )
Daniel
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Juergen Wakunda
> Sent: Thursday, September 14, 2000 9:45 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Cooker] Bug inside Installation when using SCSI ! PLEASE
> READ !
>
>
>
> Hi,
>
> here is my more detailed bug report (I used 7.2beta1). I was
> not able to use
> the "bug" command on console 2, because this console was not
> active. So i
> wrote the output text down (typos possible).
>
> testing for /modules/ide-mod.o
> not found /modules/ide-mod.o
> try with /tmp/ide-mod.o
>
> testing for /modules/ide-probe.o
> not found /modules/ide-probe.o
> try with /tmp/ide-probe.o
>
> testing for /modules/ide-probe-mod.o
> not found /modules/ide-probe-mod.o
>
> testing for /modules/ide-mod.o
> not found /ide-mod.o
> try with /tmp/ide-mod.o
> insmod: a module named ide-mod already exists
>
> testing for /modules/cdrom.o
> not found /modules/cdrom.o
> try with /tmp/cdrom.o
>
> testing for /modules/ide-cd.o
> not found /modules/ide-cd.o
> try with /tmp/ide-cd.o
>
> (This was the point where the install program asks "do you have a SCSI
> adapter?" - "yes")
>
> testing for /modules/scsi-mod.o
> not found /modules/scsi-mod.o
> try with /tmp/scsi-mod.o
>
> (i chose "dc385x_trm" and pressed autoprobe twice)
>
> testing for /modules/dc395x_trm.o
> not found /modules/dc395x_trm.o
> try with /tmp/dc395x_trm.o
>
> (the driver was successfully loaded, but "i could not mount a
> CD on device
> /dev/scd0")
>
> On console 3:
> (after pressing "autoprobe" for the dc395x_trm driver):
> * running: /bin/insmod /bin/insmod /modules/dc395x_trm.o
> (then i have to press "autoprobe" again):
> * running: /bin/insmod /bin/insmod /modules/dc395x_trm.o
> Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: Quantum Mo
> * scsi devices are available
> * mounting scd0 on /tmp/rhimage as type iso9660
> * creating directory /tmp/rhimage rc = 0
> * calling mount(/tmp/scd0, /tmp/rhimage, iso9660, -1058209791, (nil))
>
>
> After pressing "ok" on console 1 (at the message "i could not ...")
> an endless loop is printing this on console 3:
>
> * PCI bridge probe:
> * not found
>
> * Intel PCIC probe:
> * not found
>
> * Databook PCIC probe:
> * not found
>
> * .....
>
>
> Is it possible that the included version of the driver is not
> the newest?
> I get some (10) messages at the end of the driver initialisation:
>
> <6> DC395x: Sel Timeout IRQ
>
> That was the same on SuSE 6.2 and worked ok. Since SuSE 6.4
> this messages
> disappeared.
> The homepage of the driver is:
>
> ftp://ftp.suse.com/pub/people/garloff/linux/dc395/index.html
>
> Best regards,
>
> Jürgen.
>
>
