I received a large number of very similar replies. Many thanks.
Following these, and the CD documentation that replies helped
me to find, I did the following.
1. Keep a copy of the existing kernal.
# cp /vmunix /vmunix.save
2. Shut the system down.
# shutdown -h now
3. Boot to single user mode using the generic kernel.
>>> boot -fl s -fi "genvmunix"
4. Mount local file systems at the single user prompt.
# /sbin/checkrc
5. Build a new kernel (I did not manually edit the configuration file).
MYSYS is the name of your host.
# doconfig -c MYSYS
6. Once the kernel configuration and build is complete without errors,
move the new kernel.
# mv /sys/MYSYS/vmunix /vmunix
7. Reboot.
# shutdown -r now
At the end of all this the externall attached DLT was recognised
and device files had been created to access it.
# ls -l *mt*
crw-rw-rw- 1 root system 9,54279 Oct 28 12:53 nrmt0a
crw-rw-rw- 1 root system 9,54275 Oct 28 12:53 nrmt0h
crw-rw-rw- 1 root system 9,54273 Oct 28 12:53 nrmt0l
crw-rw-rw- 1 root system 9,54277 Oct 28 12:53 nrmt0m
crw-rw-rw- 1 root system 9,54278 Oct 28 12:53 rmt0a
crw-rw-rw- 1 root system 9,54274 Oct 28 12:53 rmt0h
crw-rw-rw- 1 root system 9,54272 Oct 28 12:53 rmt0l
crw-rw-rw- 1 root system 9,54276 Oct 28 12:53 rmt0m
There is one confusion I have though. I actually did this on two
different systems. The above was how I did it second time. First up
was a few weeks earlier. On the first occasion I edited the
configuration file manually during the doconfig i.e. /sys/conf/MYSYS.
I added the following 2 lines.
bus isp1 at pci0 slot 12 vector ispintr
controller scsi3 at isp1 slot 0
The replies I had received were confusing as to whether I really had to
edit the configuration file or not. Second time up I did not edit it
manually and it has ended up no different after the doconfig. Yet the
devices are still recognised.
Perhaps someone can shed further light on this.
Steve Kinder wrote:
>
> Subject: PCI SCSI problems
> Date: Mon, 4 Oct 1999 22:00:07 +0100
> From: "Kinder, SH (Steve)" <S.H.Kinder_at_dl.ac.uk>
> To: tru64-unix-managers_at_ornl.gov
> CC: "Kinder, SH (Steve)" <s.h.kinder_at_dl.ac.uk>
>
> I have an Alpha XP1000 and have bought an optional PCI external SCSI
> card, KZPBA-CA.
> I have put the card in and have a DLT tape drive attached. At the boot
> prompt >>> sh dev
> seems to recognise the DLT. Unfortunately I can't work out how to get it
> recognised once
> booted. I've tried just doing a MAKEDEV tz5 but when I try an mt on the
> resultant rmt files I
> just get "No such device or address". What tz number would I put if it
> was on say bus 1, tz12?
>
> I'm still learning the ropes on Alphas, how do I find out what
> buses/cards are on the system
> and what SCSI ids are recognised on these? Is there not a simple
> command? Do I have to do
> a kernel reconfig to get the card recognised?
>
> Cheers
>
> Steve
--
========================================================================
=== Steve Kinder, = Tel: +44 (0)1925-603350 ===
=== CCLRC, = Fax: +44 (0)1925-603124 ===
=== Daresbury Laboratory, = ===
=== Warrington, = ===
=== WA4 4AD, UK. = internet: s.h.kinder_at_dl.ac.uk ===
========================================================================
Received on Fri Oct 29 1999 - 16:17:12 NZDT