An update on this - Intel support advise an update of the OPA software stack.
I don't have a reason why there is a /dev/hfi1 device file on the first cluster, but expect the update will sort this out. On 28 March 2017 at 18:27, John Hearns <hear...@googlemail.com> wrote: > I am a kitten who has lost his mittens. > > Could a couple of kind souls who are using Omnipath please run an ls -l > /dev/hfi* > > On two systems I see: > > crw-rw-rw- 1 root root 246, 0 Mar 24 12:23 /dev/hfi1 > crw-rw-rw- 1 root root 246, 1 Mar 24 12:23 /dev/hfi1_0 > crw------- 1 root root 246, 128 Mar 24 12:23 /dev/hfi1_diagpkt > crw------- 1 root root 246, 200 Mar 24 12:23 /dev/hfi1_diagpkt0 > crw------- 1 root root 246, 192 Mar 24 12:23 /dev/hfi1_ui0 > > > crw-rw-rw- 1 root root 241, 0 Mar 20 15:04 /dev/hfi1_0 > crw------- 1 root root 241, 128 Mar 20 15:04 /dev/hfi1_diagpkt > crw------- 1 root root 241, 200 Mar 20 15:04 /dev/hfi1_diagpkt0 > > > thanks >
_______________________________________________ Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
