Slightly OTC: SRM, Tru64

["Amal D'Silva" <amal summnet com>]

Dear all,
I have a problem with Tru64 4.0F and SRM. The config I am using is:
LX4motherbaord with 600 MHz 21164
SRM v5.6
TEKRAM UW controller (using NCR 53C895 chip)
IDE CD ROM
Matrox Millenium 4 MB
With Alphabios loaded, both RedHat 5.2 and NT 4.0 work fine (dual boot)
with the above config. I needed to load Tru64 and hence flashed SRM v5.6.

SRM recognises the controller, but the command :
ls -l dk* 	(where dk* are the hard disks), gives
r--- dk 	0/0		0	dka0.0.0.6.0


The SRM comand "exer_read" works fine, but "exer_write dka0.0.0.6.0" gives:
invalid file name
file open failed for @$#@.. (some junk characters)
dka0.0.0.6.0 is write protected

The SRM command '"test" passes all tests but gives:
Testing dka0.0.0.6.0 (read only)

The "show conf" command, correctly reports the contoller and drive details.

When we try booting Tru64unix 4.0F from the IDE CD ROM, it sets the initial
parameters correctly, jumps tpo bootstrap code, but further gives the message:
PCI device at bus 0, slot 6, function 0, could not be configured
Vendor 0x1000, ......,etc
has no matching entry in the PCI option table

The problem is similar with both the Adaptec (2940UW)(vendor ID 0x9004) and
NCR controllers
( I have read somewhere that SRM v5.6 adds support for adaptec controllers)

The unix boot process shows the IDE CDROM as SCSI 0, LUN 0. ( This is true
with Alphabios also, as the CDROM is recognised as a SCSI device) and shows
the CDRM as device rz0 (which is what Tru64 names the Hard disks)

After this Tru64 loads the Xserver, display the inital setup screen for
partitioning the Disks, etc and suddenly pops up a dialog box with the
message:
"finder -q" failure file "/tmp/finder.abort" exists 
and then exits the installtion and returns to the unix shell prompt.
I did try using "restart nogui" but the result is the same. I even tried
deleting the 0 byte file "/tmp/finder.abort" but it the installation
process seems to create it once again

Thanks in advance,
Amal D'Silva.