Date: Thu, 04 Feb 1999 22:03:10 -0800 From: ONE-MO <onemo@jps.net> To: "Viren R. Shah" <viren@rstcorp.com> Cc: stable@FreeBSD.ORG Subject: Re: Compaq ida driver patch Message-ID: <36BA899D.C780DF99@jps.net> References: <36B8DA72.F58BB5D1@jps.net> <36B956B7.4299FC0@doc.ic.ac.uk> <199902041438.JAA44908@jabberwock.rstcorp.com> <36B9EECF.DB2F9F08@jps.net> <199902041938.OAA53509@jabberwock.rstcorp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
OK, here's the latest status.
I used your hacked ida.c, noticing a couple changes in addition to the port
address. I rebuilt my kernel with the ida port specified as 0x1000. Upon
booting, I did NOT receive the same process lockup upon accessing the
drive. However, I DID receive many errors about the slices and other
geometry not matching.
So, I decided to check the Array Config Utility and see exactly what
settings I had left it at. The Operating System selected was Unix/Xenix and
the RAID5 array used all available disk space. I decided to delete the
array, change the OS to DOS/Windows, and recreate the array. This time, I
show 264Mb unused space along with the RAID5 logical drive (strange, I
thought). Upon saving this configuration and rebooting, I can now access
the drive without further problems.
Just for fun, I booted my kernel.old (the last kernel built with Mark's
original ida.c) and I again received the lockup upon access.
Thanks for the help, now if only I can determine exactly what it was the
corrected it....
MO!
"Viren R. Shah" wrote:
> >>>>> "MO" == ONE-MO <onemo@jps.net> writes:
>
> MO> I booted a 2.2.7 ida install floppy and checked the device
> MO> settings there. It showed the port at 0x0 so I tried that and it
> MO> detected the actual port of 0x1000. I tried kernel configs with
> MO> both 0x0 and 0x1000, either way I still can't access with
> MO> 3.0-based utils. I am able to access it and setup a filesystem on
> MO> it using the 2.2.7 floppy - but booting back to 3.0, I get the
> MO> same lock trying to mount the fs.
>
> Hmm..I've been running a hacked version of the ida driver on -3.0
> current, and now on -4.0 current (for the past couple of months). So,
> while, the EISA/wd stuff in 3.0 may have changed, it hasn't changed a
> lot. All I've changed in ida.c is hard-coding the port (to 0x6000 in
> my case). I'll send you my version of ida.c seperately.
> also, can you post the dmseg lines from 2.2.7 and 3.0?
>
> Here's how I would recommend you do it:
>
> 1. Install 2.2.x using one of the boot floppies from Mark's site.
> 2. cvsup to 3.0-stable
> 3. Modify the upgrade kernel config file to include the ida
> drivers. Modify the kernel sources according to the instructions on
> Mark's site. Modify ida.c so that it always goes to port 0x1000
> (Look at where I did it in my version of ida.c )
> 4. run the upgrade procedure (I ran make aout-to-elf-build. I don't know
> whether it is still the same)
> 5. DO not install the new boot blocks (just in case the kernel fails)
> 6. try out the new kernel. If it fails, default to the old 2.2.x
> kernel, and make modifications to ida.c. Keep at it till it works.
>
> (don't take this as gospel. Read the upgrade makefiles to see what
> exactly it is doing)
>
> OR
> I can build you a kernel with the port hardcoded to 0x1000. I would
> rather not do this since the only means I have of transferring the
> kernel from my home machine to work is a 28.8 modem.
>
> [I realize that all this is a big hack, and that Mark and a bunch of
> others are cringing, but *shrug* practicality first]
>
> Viren
> --
> Viren R. Shah, {viren @ rstcorp . com} http://www.rstcorp.com/~vshah/
> ====== FreeBSD: It's free, it's fast, it's fun. ======
> "3 syncs represent the trinity - init, the child and the
> eternal zombie process." -- Jordan Hubbard
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36BA899D.C780DF99>