My original question is at the bottom.
Thanks to Bernt and Dr. Tom for their replies, and to Phil Lawrence
for the DEC Unix Support Team
Bernt replied:
>The entry depends on the slot where you put in...
>
>What i do in such cases is: booting the generic kernel (genvmunix)
>(without an existing /sys/conf/<HOST>; move it to another name)
>this will create a valid entry for each (known) hardware-device.
>Then "merge" your old and the new <HOST>-file, make a new kernel
>and reboot...
Whilst Dr. Tom Blinn replied:
>SCSI adapters are MUCH messier than other options. If you really do
know
>what you're doing, then all you really need to know is that the
driver for
>NCR810 and compatible chips is called "psiop".
>
>I've got a system that happens to have two such adapters in it. In
the
>config file, there are the following lines associated with them:
>
>bus psiop0 at pci0 slot 6 vector psiopintr
>controller scsi0 at psiop0 slot 0
>bus psiop1 at pci0 slot 9 vector psiopintr
>controller scsi1 at psiop1 slot 0
>
>You need both the "bus" and "controller" to get SCSI adapters to work.
>You need to know where the device will appear and on which of your PCI
>busses or you won't get the right "bus psiop" line. This depends on
the
>physical configuration of your system.
>
>I don't remember if we shipped a GENERIC configuration file for the
V3.2
>release (gee, that's so old we don't support it any longer, good luck
on
>getting this new hardware to work, I hope it's compatible with V3.2
and your
>hardware platform). If we did, you can find much of the "generic"
way to
>get this to work in that file.
>
>Frankly, you're MUCH better off waiting until you've got the hardware
in
>the system and working and then using doconfig (or just sizer) to
create
>the config file for you, while running the genvmunix kernel.
>
>If you make any errors in doing it manually, it simply won't work.
There is
>really only one advantage to doing it manually, and that is that you
can put
>the logical "controller scsi" lines attached to the busses you want,
so that
>existing device numbers won't change.
I then posed the question to Dr. Tom:
> Does sizer ignore the current kernel configuration file and list all
> correct hardware components in its output file?
>
> I planned to use sizer -n simon to create /tmp/simon and
/tmp/simon.devs
>
> This would save a lot of time and hassle I can do this in the
evening
> requiring one kernel re-build and reboot.
Dr. Toms' reply was:
>Using sizer -n is probably the way to go if you've got many
Customizations
>in the config file. When you use "sizer -n" it ignores your existing
file;
>the doconfig script (when you run it with no options) basically runs
sizer,
>and then merges information from other sources to the end of the file
that
>sizer created. (You can read the doconfig script but it's not
especially
>easy to follow as scripts go because it's doing a complex task.)
>
>In fact, probably the best method is this.
>
>Before you add the new hardware, run sizer -n and save the output as
what
>you get for the old config. You can do this while you're running
your old
>kernel -- you don't need to reboot with /genvmunix.
>
>Add the new hardware, run sizer -n running genvmunix and get the new
files
>with the new hardware config. You need to do this running /genvmunix
to get
>the new hardware recognized, but you may need to boot only to single
user to
>avoid problems with bus naming conventions, then reboot your old
kernel
>(that doesn't know about the new SCSI controller).
>
>Use your favorite differences tool to compare the two (old and new)
sizer -n
>config files. The differences will be obvious and should be due
primarily
>to the new SCSI controller. Once you see what sizer did with the new
KZPAA,
>it should be obvious what psiop line to add and how to associate a
"scsi"
>line with it (to make it be the next range of SCSI IDs instead of
maybe in
>the midst of your existing addresses). Merge the changes into your
existing
>config file (save a copy, obviously, in a name other than what
doconfig is
>going to use) and then build a new kernel. The new kernel can
preserve all
>of your other Customizations.
The method I have chosen is to install the card then boot genvmunix.
I will then run sizer then modify
the kernel configuration file, rebuild the kernel and reboot.
I will post a second summary with the results.
ORIGINAL POSTING
Dear Alphas
I am looking for the correct kernel entry for a kzpaa-aa scsi host
adapter for an Alpha 2100 running DU 3.2
This card is being installed tomorrow and I would like to build the
kernel before installation.
The card is not yet on-site so I have no sight of any manuals.
Can any body help me, or am I beyond it?
Simon.Millard_at_barclays.co.uk
Address Telephone
CAS - GES/Open Systems Support External: (01202) 601155 ext
2417
Barclays Technology Services Internal: C/W 7-4160-2417
Poole Computer Centre Fax: (01202) 642429
81, Sopers Lane
Poole, Dorset
Live Long and Prosper and may the polarity of your neutron flow never
be reversed!
Internet communications are not secure and therefore the Barclays Group does
not accept legal responsibility for the contents of this message. Any views
or opinions presented are solely those of the author and do not necessarily
represent those of the Barclays Group unless otherwise specifically stated.
Received on Tue Sep 15 1998 - 10:05:20 NZST