Date: Wed, 17 Feb 1999 09:47:53 -0500 From: Doug Ledford <dledford@redhat.com> To: System Administrator <admin@intergrafix.net> Cc: aic7xxx Mailing List <AIC7xxx@FreeBSD.ORG> Subject: Re: New 2940U2W with quantum drive Message-ID: <36CAD699.70F725FD@redhat.com> References: <Pine.LNX.4.10.9902170841250.32401-100000@athena.intergrafix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
System Administrator wrote:
>
> Hi,
>
> First of all, my config is
> intel pr440fx motherboard with onboard adaptec 7880. have on the cable 2 9
> Gig Quantum Atlas IIs (one is my boot drive), 1 4.5G Quantum Viking, and 1
> 4.1G(?) Quantum Grand Prix. the controller is on IRQ 9 by the bios, then
> IO-APICs in the linux kernel move it to IRQ 17.
>
> Now, I've added a new 2940U2W controller. On the controller I put a new
> 18.2G Quantum Atlas III (LVD,68pin).
>
> When I bootup the computer it detects the new controller first, then the
> 7880. The problem with this is instead of booting into linux it says
> "Insert bootable media into appropriate drive"
> I'm assuming it's trying to boot from the new 18.2G drive, drive that
> controller was detected first. The only was I could get it to boot was to
> go into Cntrl-A on the NEW controller and turn the SCSI bios off. Then it
> booted fine..the kernel detected the new drive and controller and I can
> use them fine, but when it detected the new drive it says synchronus at
> 40MB/S..which it should be 80.
>
> (scsi1) Wide Channel, SCSI ID=7, 32/255 SCBs
> (scsi1) Downloading sequencer code... 407 instructions downloaded
> scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.10/3.2.4
> <Adaptec AHA-294X Ultra2 SCSI host adapter>
> Detected scsi disk sde at scsi1, channel 0, id 4, lun 0
> (scsi1:0:4:0) Synchronous at 40.0 Mbyte/sec, offset 31.
> SCSI device sde: hdwr sector= 512 bytes. Sectors= 35566499 [17366 MB]
> [17.4 GB]
>
> how can i get this to recognize it as 80 MB/S?
>
> /proc/scsi/aic7xxx/1:
> Adaptec AIC7xxx driver version: 5.1.10/3.2.4
> Compile Options:
> AIC7XXX_RESET_DELAY : 10
> AIC7XXX_TAGGED_QUEUEING: Adapter Support Enabled
> Check below to see which
> devices use tagged queueing
> AIC7XXX_PAGE_ENABLE : Enabled (This is no longer an option)
> AIC7XXX_PROC_STATS : Enabled
>
> Adapter Configuration:
> SCSI Adapter: Adaptec AHA-294X Ultra2 SCSI host adapter
> Ultra2-LVD/SE Wide Controller
> PCI MMAPed I/O Base: 0xffbef000
> Adapter SEEPROM Config: SEEPROM found and used.
> Adaptec SCSI BIOS: Disabled
> IRQ: 17
> SCBs: Active 0, Max Active 1,
> Allocated 15, HW 32, Page 255
> Interrupts: 284781
> BIOS Control Word: 0x18a2
> Adapter Control Word: 0x1c5d
> Extended Translation: Enabled
> Disconnect Enable Flags: 0xffff
> Ultra Enable Flags: 0x0000
> Tag Queue Enable Flags: 0x0000
> Ordered Queue Tag Flags: 0x0000
> Default Tag Queue Depth: 24
> Tagged Queue By Device array for aic7xxx host instance 1:
> {255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255}
> Actual queue depth per device for aic7xxx host instance 1:
> {1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}
>
> Statistics:
>
> (scsi1:0:4:0)
> Device using Wide/Sync transfers at 40.0 MByte/sec, offset 31
> Transinfo settings: current(12/31/1), goal(10/127/1), user(10/127/1)
^^^^^^^ ^^^^^^^^ ^^^^^^^^
These numbers indicate how we are trying to negotiate with the device.
The first number in each triplet is the period as transferred in the
SDTR command, the second is the desired offset value, and the third is 0
for narrow and 1 for wide. The current() numbers are what the disk is
actually set to at the time you read the proc file, the goal() numbers
are what we are going to try and negotiate after having scanned the
devices INQUIRY data, and the user() numbers are how the SEEPROM had the
device configured. In your case, both the SEEPROM and the driver's goal
was to run at 80MByte/s, yet it ended up at 40MByte/s. I would guess
that this means you have an Atlas III LVD drive, but that the Atlas III
LVD drives are still Ultra speed and not Ultra2 speed yet. You would
need to confirm that with Quantum, but the obvious explanation here is
that we said to the drive "Is 80MByte/s OK?" and the drive said back
"No, let's do 40MByte/s instead" and so we did.
> Total transfers 284712 (55061 reads and 229651 writes)
> < 2K 2K+ 4K+ 8K+ 16K+ 32K+ 64K+ 128K+
> Reads: 1 49240 376 472 1897 1311 1271 493
> Writes: 0 176896 16372 2227 2847 4773 8414 18122
>
> Thanx:
>
> -Cygnus
> .-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
> Anthony J. Biacco Network Administrator/Engineer
> admin@intergrafix.net Intergrafix Internet Services
>
> "Dream as if you'll live forever, live as if you'll die today"
> http://cygnus.ncohafmuta.com http://www.intergrafix.net
> .-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe aic7xxx" in the body of the message
--
Doug Ledford <dledford@redhat.com>
Opinions expressed are my own, but
they should be everybody's.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36CAD699.70F725FD>