alex@sapphire.idbsu.edu (Alex Feldman) (01/16/91)
In article <1991Jan15.155520.7406@sat.uucp> root@sat.uucp writes: >I have a HP 9000/400dl discless node that won't boot. All I get is the >message: >Secondary Loader Revision: 64.2 >Booting /hp-ux > >and then a blank screen. There are no entries in rbootd.log except for >the usual start and stop ones. There is a 400t on the lan that does boot. >The most obvious difference is that the 400t has color. > >The server is a 370 running hpux 7.0. > >Any suggestions? Yup. You need 7.03 for monochrome. We went 'round and 'round on this one before someone at HP finally got it straight. The only time HP didn't give us great service. And you need 7.05 for the 68040. -- --alex alex@opal.idbsu.edu Boise State University doesn't have any opinions. Therefore, these are not the opinions of Boise State University.
rodean@hpfcdc.HP.COM (Bruce Rodean) (01/16/91)
In article <1991Jan15.155520.7406@sat.uucp> root@sat.uucp writes: > I have a HP 9000/400dl discless node that won't boot. All I get is the > message: > Secondary Loader Revision: 64.2 > Booting /hp-ux > > and then a blank screen. > > Any suggestions? I would check the device files for that node. From the server execute 'll -H /dev+/<node>' where <node> is the name of the node that won't boot. You should see something like: crw--w--w- 3 myself users 0 0x000000 <node> Jan 15 08:23 console crw-rw-rw- 1 root other 12 0x000000 <node> Dec 13 09:24 crt where once again, <node> should be the name of that node. If it is some other name, then your device files are no good as they "belong" to another node. See the discussion in the mknod.1m manual entry for Device Special Files where it talks about the cnode_name option. It points you to the mkrnod system call. Did you use SAM to add the node? Bruce Rodean rodean@hpfclg.fc.hp.com This does not reflect the official position of Hewlett-Packard Co. No guarantees of any kind are give or implied.