From owner-aic7xxx Tue Dec 29 01:19:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11603 for aic7xxx-outgoing; Tue, 29 Dec 1998 01:19:30 -0800 (PST) (envelope-from owner-aic7xxx@FreeBSD.ORG) Received: from peik.bol.sharif.ac.ir ([194.225.42.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11384 for ; Tue, 29 Dec 1998 01:15:12 -0800 (PST) (envelope-from masu@peik.bol.sharif.ac.ir) Received: from localhost (masu@localhost) by peik.bol.sharif.ac.ir (8.8.6/8.8.6) with SMTP id LAA07265 for ; Tue, 29 Dec 1998 11:47:39 +0330 Date: Tue, 29 Dec 1998 11:47:39 +0330 (IST) From: Massoud Asgharifard To: AIC7XXX driver developement mailing list Subject: Re: aic7xxx and partition maps? In-Reply-To: <199812281749.RAA18828@hewes.icl.ox.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 28 Dec 1998, Mr. Arlington Hewes wrote: > > Folks, > > I'm running linux-2.1.131 on a dual PII (350) GigaByte GA-6BXDS motherboard, > complete with Adaptec UW SCSI. I'm recycling two drives from the previous > incarnation of this machine.... > 2.1.131 was compiled with a patched aic7xxx driver, bringing it up to the > current 5.1.6 release. > > The first problem was that I was unable to ever boot from a bzImage kernel > image - I could never get past the LI of lilo with a bzipped kernel. Making it > more modular and getting it down to a permissible zImage allowed me to boot, > but I'm not sure why this would be. Any number of kernel rebuilds, reconfigs, > and reruns of lilo made no difference, . . . . always hung at LI. Could this > possibly be related to the aic7xxx driver, or is it more low-level than that? > The only reason I ask is that a colleague had exactly the same problem with a > 2.1.131/aic7xxx combination. about your LILO problem, you didn't send your /etc/lilo.conf, anyway, I think 'linear' option is missing from your /etc/lilo.conf. > The second problem is that although my disks are recognized and my system is > running quite happily, the partition tables of my disks are apparently all of > a sudden quite repulsive to fdisk. More problematic, I have had to remove my > windows partition from lilo.conf because of: > > [root@hewes aic7xxx]# /sbin/lilo > Added linux-2.0.36 * > Added linux-2.1.131 > Added redhat-linux > Device 0x0800: Invalid partition table, 3rd entry > 3D address: 1/0/959 (15406335) > Linear address: 1/54/248 (3987522) > [root@hewes aic7xxx]# > > Here's what fdisk now thinks of my disk (remember that it was quite healthy > according to fdisk when running on the NCR driver): > > [root@hewes aic7xxx]# fdisk /dev/sda > > Command (m for help): p > > Disk /dev/sda: 255 heads, 63 sectors, 261 cylinders > Units = cylinders of 16065 * 512 bytes > > Device Boot Start End Blocks Id System > /dev/sda1 1 6 47785+ 82 Linux swap > Partition 1 has different physical/logical endings: > phys=(22, 65, 63) logical=(5, 242, 63) > Partition 1 does not end on cylinder boundary: > phys=(22, 65, 63) should be (22, 254, 63) > /dev/sda2 6 249 1945944 83 Linux native > Partition 2 has different physical/logical beginnings (non-Linux?): > phys=(23, 0, 1) logical=(5, 243, 1) > Partition 2 has different physical/logical endings: > phys=(958, 65, 63) logical=(248, 53, 63) > Partition 2 does not end on cylinder boundary: > phys=(958, 65, 63) should be (958, 254, 63) > /dev/sda3 * 249 261 101871 6 DOS 16-bit >=32M > Partition 3 has different physical/logical beginnings (non-Linux?): > phys=(959, 0, 1) logical=(248, 54, 1) > Partition 3 has different physical/logical endings: > phys=(1007, 65, 63) logical=(260, 227, 63) > Partition 3 does not end on cylinder boundary: > phys=(1007, 65, 63) should be (1007, 254, 63) > > Basically I'm happy to leave things as they are, but I would be much happier > understanding what has happened here, and whether there's something in the > SCSI BIOS which I should be tuning in order for my disks to be recognised > properly. Can anyone enlighten me here? still unsure about my comment, but you may enforce a geometry to driver. > A little bit more info, in case it's relevant: > > >From /proc/pci: > > Bus 0, device 12, function 0: > SCSI storage controller: Adaptec AIC-7895U (rev 4). > Medium devsel. Fast back-to-back capable. IRQ b. Master Capable. > Latency=64. Min Gnt=8.Max Lat=8. > I/O at 0xe800 [0xe801]. > Non-prefetchable 32 bit memory at 0xe6800000 [0xe6800000]. > > And from /proc/scsi/aic7xxx/0: > > Adaptec AIC7xxx driver version: 5.1.6/3.2.4 > Compile Options: > AIC7XXX_RESET_DELAY : 5 > 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 AIC-7895 Ultra SCSI host adapter > Ultra Wide Controller Channel A > PCI MMAPed I/O Base: 0xe6800000 > Adapter SEEPROM Config: SEEPROM found and used. > Adaptec SCSI BIOS: Enabled > IRQ: 11 > SCBs: Active 0, Max Active 1, > Allocated 15, HW 32, Page 255 > Interrupts: 131289 > BIOS Control Word: 0x18a6 > Adapter Control Word: 0x005e > 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: 8 > Tagged Queue By Device array for aic7xxx host instance 0: > {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 0: > {1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1} > > Statistics: > (scsi0:0:3:0) > Device using Narrow/Sync transfers at > 10.0 MByte/sec, offset 15 > Device Negotiation Settings > Period Offset Bus Width > User 012 008 1 > Goal 012 015 0 > Current 025 015 0 > Total transfers 131249 (40107 read;91142 written) > blks(512) rd=315197; blks(512) wr=300530 > < 512 512-1K 1-2K 2-4K 4-8K 8-16K 16-32K 32-64K 64-128K >128K > Reads: 0 33 13090 9859 10388 6183 333 164 57 0 > Writes: 0 0 78395 9787 2330 184 123 88 235 0 > > > Thanks in advance, and thanks for a superbly crafted and seemingly very > powerful driver. Special thanks for keeping it current, with patches for both > 2.1.131 and 2.0.36 on offer!! ;-) > > -Darren > > > -- > Mr. Arlington Hewes (tpcadmin@info.tpc.int) > The TPC.INT Subdomain (http://www.tpc.int/) > > ************************************************** > *** FOR GENERAL INFORMATION *** > *** mailto:tpcfaq@info.tpc.int *** > *** FOR A LIST OF CURRENT COVERAGE *** > *** mailto:tpccover@info.tpc.int *** > *** TO REPORT A PROBLEM (read the FAQ first!) *** > *** mailto:support@info.tpc.int *** > ************************************************** > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe aic7xxx" in the body of the message > -- Massoud "Masu" Asgharifard. masu@bol.sharif.ac.ir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message