I have to agree with Derek... it's an ATA-100 controller wrongly recognised
by Win98 as a SCSI controller. I've experienced this with Win98 on an ASUS
board too.
Jin
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of D. Stark - eSN
> Sent: 11 January 2001 22:40
> To: [EMAIL PROTECTED]
> Subject: RE: [expert] SCSI harddrive and LM 7.1
>
>
> Not to be a doubting thomas, but are you *sure* that its
> scsi? Windows will
> report offboard chipsets (that it doesnt know what else to
> call) as scsi. I
> just mention it because looking up that product number with
> google returns
> that it is an ATA100 controller. I don't think that Quantum
> Fireball drives
> are SCSI, either. Thier Atlas line of drives are the high-pro
> scsi line.
>
> I imagine that you tried a normal install and it didnt work?
> I'd look in my
> system BIOS to see if you had ATA/33 options.
>
> Derek Stark
> IT / Linux Admin
> eSupportNow
> xt 8952
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of John J. LeMay Jr.
> Sent: Thursday, January 11, 2001 7:30 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] SCSI harddrive and LM 7.1
>
>
> ** Reply to message from "Zeljko Vukman" <[EMAIL PROTECTED]> on
> Thu, 11 Jan 2001
> 10:47:08 +0100
>
> > Hi Mandrakes,
> > I'm in a little trouble and I hope Mandrake experts could help here.
> > I admit, I never before used SCSI devices, and yesterday
> when I bought
> > a new computer I got a scsi harddrive quantum fireball 20
> Gb. I have no
> > idea how to get it work with my Linux Mandrake 7.1. I tried all scsi
> > options
> > during install but no luck. Mandrake doesn't recognize it at all.
> > I presume that problem is in controler, and windows says that SCSI
> > controller is: Win 95-98 Promise Ultra100(tm) IDE Controler
> (PDC20265).
> > Is there any way to get it work?
> >
> > Best regards,
>
>
> SCSI is a different beast compared to IDE and it's children.
> First, you
> mention
> that Windows sees the controller. Does Windows see the drive?
> If not, does
> the
> SCSI BIOS load (should load right after your machine's BIOS
> and identifies
> the
> card followed by devices on the SCSI "chain".)?
>
> If the SCSI BIOS doesn't see the drive, the problem is either
> that the drive
> is
> not terminated or you are using the same SCSI ID as the
> controller. Try
> changing
> the SCSI ID on the drive in this case.
>
> As for termination, Windows seems to deal better with
> auto-termination than
> Linux does. All SCSI chains must be terminated at both ends
> of the chain.
> Most
> controllers handle one end of the chain. You need to provide
> termination
> after
> the last SCSI device on the chain. Most devices today allow you to set
> termination on the device itself. If this doesn't work, you
> may need to pick
> up
> a terminator and connect it to the SCSI cable.
>
> John LeMay Jr.
> Senior Enterprise Consultant
> NJMC, LLC.
>
>
>
