Hello,
I have an Intel server se7501WV2 with on SCSI Controller on board and a second
one as an extra card.
Build in is an Adaptec AIC7902 Ultra320 (two channel), extra is an Adaptec
29320LP-R PCI Single U320 (Chip AIC-7901X). Both use the
same driver (aic79xx).
If both are installed I get S
Hi!I hava a Western Digital
WD7193 SCSI Controller and it is not compatible to the WD7000 Driver.If
I don't get a driver for WD7193,WD7197,WD7296 or compatible SCSI Controllers I
willnever be able to use Linux because my harddrives and CDRom drives are
conntected to it.And there i
Hello Allan,
I currently have a buslogic BT946 controller with one 1 gig conner scsi drive
and then a 420 meg ide drive and an 850 ide drive. It all works fine. The
scsi drive only has linux stuff on it and then one ide drive has a linux
partition (/) for booting and that sort of stuff. Works f
On Fri, Jun 05, 1998 at 02:35:32PM -0700, Allan Bart wrote:
>
> Hello,
>
> I was wondering if any of the users on this group have concurrently
> run both types of disk drives. i am planning to use an advansys 5140
> and an internal ide controller on my old ast 486dx system.
I used an ASUS SP3G
On 06/05/98 at 02:35 PM, Allan Bart <[EMAIL PROTECTED]> said:
>Hello,
>I was wondering if any of the users on this group have concurrently run
>both types of disk drives. i am planning to use an advansys 5140 and an
>internal ide controller on my old ast 486dx system.
>looking ro hear from you,
My system runs an Adaptec 7xxx SCSI controller (and drive), three IDE drives
and an IDE CD-Rom... Works... boots off of /dev/hda1 so I had to use LILO to
boot anything off of /dev/sda1
On 05-Jun-98 Allan Bart wrote:
> I was wondering if any of the users on this group have concurrently
> run both
Hello,
I was wondering if any of the users on this group have concurrently
run both types of disk drives. i am planning to use an advansys 5140
and an internal ide controller on my old ast 486dx system.
looking ro hear from you,
allan bart
==
Allan W. Bart, Jr.
Strategic Analyst
__
Rob Browning <[EMAIL PROTECTED]> writes:
> Dale Scheetz <[EMAIL PROTECTED]> writes:
> > I would highly recommend Buss Logic to anyone needing a SCSI interface.
> That's my impression as well. I've also heard that for the truly
> performance crazed, DPT cards are the answer, but are also more
> exp
On Wed, 25 Jun 1997, Rick Hawkins wrote:
> a-hah! I've gotten somewhere--but it's not good.
>
> Once I connected the three scsi devices, I found that it finds all 3.
> But . . . The last device in the list does not get a /dev/srX entry.
> Thus with jus a cd and a zip in the chain, the cd gets on
Rick Hawkins wrote:
>
> a-hah! I've gotten somewhere--but it's not good.
>
> Once I connected the three scsi devices, I found that it finds all 3.
> But . . . The last device in the list does not get a /dev/srX entry.
> Thus with jus a cd and a zip in the chain, the cd gets one, but not the
> zi
a-hah! I've gotten somewhere--but it's not good.
Once I connected the three scsi devices, I found that it finds all 3.
But . . . The last device in the list does not get a /dev/srX entry.
Thus with jus a cd and a zip in the chain, the cd gets one, but not the
zip. With both cd's & the zip, both
On Wed, 25 Jun 1997, Rick Hawkins wrote:
> grr. Still going :( I am about to connect more pieces here in the
> chain.
>
> Device 0 (i can't figure out how to change the id; the switches seem to
> do nothing) will be this troublesome NEC intersect drive. Device 3 is
> an ancient apple cdrom dri
grr. Still going :( I am about to connect more pieces here in the
chain.
Device 0 (i can't figure out how to change the id; the switches seem to
do nothing) will be this troublesome NEC intersect drive. Device 3 is
an ancient apple cdrom drive--it should be able to read the directory &
first f
On Tue, 24 Jun 1997, Rick Hawkins wrote:
> > Try making a 1.3 rescue disk and booting it with the fdomain parameters.
> > If you watch the screen (fast) during boot, you should see whether it got
> > the scsi controller OK or not. If that works, then it's just a matter of
> > configuring the kerne
> -- using template mhl.format --
> Date:Tue, 24 Jun 97 20:54:15 EDT
> To: Rick Hawkins <[EMAIL PROTECTED]>
> cc: debian-user@lists.debian.org
>
> From:Paul Wade <[EMAIL PROTECTED]>
> Subject: Re: more on scsi controllers
>
> X-Sender: [
Try making a 1.3 rescue disk and booting it with the fdomain parameters.
If you watch the screen (fast) during boot, you should see whether it got
the scsi controller OK or not. If that works, then it's just a matter of
configuring the kernel and LILO on your system.
On Tue, 24 Jun 1997, Rick Haw
Rick Hawkins <[EMAIL PROTECTED]> wrote:
>After the hints so far, it's clear that eata 's error messages have to
>do with using the same adresses as the second ide card (which is
>installed).
I'm new to Linux, but I've been working on computers for years, so let
me ask a question that's naive, ye
>
> At the boot: prompt type
>
> linux fdomain=0x230,11
>
> If I'm wrong about the 'linux' correct me. I can't reboot right now to
> verify that.
OK, i sort of seem to be there. I compiled the fdomain module (among
others). The autoprobe doesn't work:
modprobe fdomain=0x140,11
yields no r
Isn't there a "reserve=io_address, length" option you can feed the
kernel to protect against autoprobing? I've had experiences where
another, unrelated driver got to a card first with an autoprobe and
bolloxed everything up. Seems I used a boot line like "linux
reserve=blah,blah aic7xxx=blah,blah
>
> Use a standard kernel, like the rescue disk.
>
> At the boot: prompt type
>
> linux fdomain=0x230,11
>
> If I'm wrong about the 'linux' correct me. I can't reboot right now to
> verify that.
close. capital L. But it still didn't work :( I wonder if the eata
is somehow interfering. I h
Use a standard kernel, like the rescue disk.
At the boot: prompt type
linux fdomain=0x230,11
If I'm wrong about the 'linux' correct me. I can't reboot right now to
verify that.
On Tue, 24 Jun 1997, Rick Hawkins wrote:
> > dir /proc/scsi
>
>
> > cat /proc/scsi/aha152x (in my case) give iopor
> dir /proc/scsi
> cat /proc/scsi/aha152x (in my case) give ioport, irq, and a whole bunch of
> cool techie words.
bash-2.00# dir /proc/scsi/
scsi
bash-2.00# cat /proc/scsi/scsi
Attached devices: none
bash-2.00# dir /proc/scsi/
scsi
bash-2.00# cat /proc/scsi/scsi
Attached devices: none
bash-
The first step is to see a host adaptor.
dir /proc/scsi
cat /proc/scsi/aha152x (in my case) give ioport, irq, and a whole bunch of
cool techie words.
If nothing is there, then we need to help it along a bit.
The LILO argument is:
fdomain=,[,]
Does the card have jumpers? Somebody on this list
> Looking at the kernel source, I would say try for the future domain first.
> It should be supported by a standard Debian kernel as a built-in (not
> modular) driver. Maybe if you're lucky it will autoprobe.
no such luck :(
bash-2.00# mount /dev/scd0 /cdrom/ -t iso9660
mount: the kernel does
Looking at the kernel source, I would say try for the future domain first.
It should be supported by a standard Debian kernel as a built-in (not
modular) driver. Maybe if you're lucky it will autoprobe.
On Tue, 24 Jun 1997, Nathan E Norman wrote:
> On Tue, 24 Jun 1997, Rick Hawkins wrote:
>
> :
On Tue, 24 Jun 1997, Rick Hawkins wrote:
:
:After the hints so far, it's clear that eata 's error messages have to
:do with using the same adresses as the second ide card (which is
:installed). However, those aren't the correct adressess.
:
:I actually have three scsi cards sitting here to cho
After the hints so far, it's clear that eata 's error messages have to
do with using the same adresses as the second ide card (which is
installed). However, those aren't the correct adressess.
I actually have three scsi cards sitting here to choose from:
1) the nec card, which, on closer look
27 matches
Mail list logo
