"David C. Hoos, Sr." schrieb:
>
> -----Original Message-----
> From: Marc SCHAEFER <[EMAIL PROTECTED]>
> Newsgroups: alphanet.ml.linux.scsi
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Wednesday, January 27, 1999 3:25 AM
> Subject: Re: WD SCSI controller
>
> >David C. Hoos, Sr. <[EMAIL PROTECTED]> wrote:
> >> I issued the command /sbin/modprobe wd7000, and received the reply
> >> wd7000.o: device or resource busy.
> >
> >Please type ``dmesg | tail'' and tell us what it says, just after
> >this modprobe.
> >
> Here's what was added to the dmesg output:
>
> Failed initialization of WD-7000 SCSI card!
> scsi : 0 hosts.
WD7296/7193/7197 aren't compatible with WD7000. Instead they use some
RISC chip and a special SCSI-I/O ASIC. There is a project page at
http://home.earthlink.net/~webspot/719x.html
The last version of the very preliminary driver I and Aaron Dewell wrote
is at
http://schering.si2.uni-hannover.de/stuff/gaertner/WD719X/
In the moment I have no time to develop further, but something should be
done if I look to Linux 2.2
>
> The output to the screen was:
> /sbin/modprobe wd7000
> /lib/modules/preferred/scsi/wd7000.o: init_module: Device or resource busy
>
> For what it's worth, Windows 95 shows it using the following resources:
>
> Interrupt Request : 11
> Memory Range : EFBDFF00-EFBDFFFF
> Input Output Range : EC00-ECFF
Its a PnPray-device, so this may change.
G�rti
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]