[kaigan]

Hey, everyone,

I've been working on my Fuel recently - replacing a defective CPU and swapping over to an ATX PSU with the adapter. I'm having some issues with the internal SCSI adapter, however. I think it may be the cable and not the controller that has the issue, but I haven't been able to find a suitable replacement cable yet. I do have a compatible PCI SCSI controller and cable, though, so that's what I'm using for the moment.

The issue I'm running into with installing IRIX on the drive is that I need to set a proper root PROM variable. For this controller, I apparently need a valid full hardware graph path for the disk, as the system claims that it can only accept the standard dksX... format for the built-in controller. I've tried a couple of different things. I've tried referencing the disk itself: "/hw/dev/disk/disk65" in this case, if I'm not mistaken. I've also tried referencing the SCSI controller itself. In both cases, it doesn't seem to work.

Has anyone needed to do something similar on another system? If so, would you have any advice on what the full path to a disk should generally look like?

Thanks!

[Raion]

I know it shares the cable with some of the IBM systems. Micrex22 had a suggestion a few years ago.

As for your question, I'm not 100% sure. What model of Fuel did you get?

[kaigan]

It's a 500 MHz model with 4 GB of RAM and a V10. Not the fastest Fuel, but it works.

I did manage to figure out the path through a bit of trial and error, as well as looking over the results of the hinv -g command. The path I needed was as follows: "/hw/module/001c01/Ibrick/xtalk/15/pci/2/scsi_ctlr/0/target/1/lun/0/disk/partition/0/block". So... not the shortest thing ever.

[Raion]

fucking hell, that's long.

[kaigan]

In case any one else runs into a similar issue, I also had to manually run the dvhtool command during the IRIX installation. It would fail during the installation because one of the environment variables it was using couldn't be mapped back to the drive on the PCI SCSI controller. I found a document from Princeton's archives that has some info on the dvhtool command, which helped me to find the right device under /dev/rdsk to use. The document is available here: http://xray0.princeton.edu/~phil/Facilit..._disk.html