burdick@iuvax.UUCP (Matt Burdick) (11/16/87)
In the hp9000 model 236 manual "Peripheral Installation Guide", vol 2, we are told the info for mknod for installing the disk drivers. This can also be found in /etc/mkdev. I ran mkdev with the correct lines uncommented, and the files fd.0, fd.1, rfd.0, and rfd.1 were created in the /dev directory. I then tried to run mediainit on one of the drives, but got the error message "no such device". What am I doing wrong? Is there something I'm forgetting to do? -Matt ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ UUCP: {ihnp4,pyramid,akgua}!iuvax!burdick ARPA: burdick@iuvax.cs.indiana.edu Matt Burdick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ UUCP: {ihnp4,pyramid,akgua}!iuvax!burdick ARPA: burdick@iuvax.cs.indiana.edu Matt Burdick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
perry@hpfcdc.UUCP (11/18/87)
I suspect you might be using the CS80/SS80 drivers. The two built-in floppy drives use a special block/character driver. It has been a long time since I had a 9836 (236), and I don't remember the details. It is definitely NOT drivers c4 and b0, which are for CS80 (HPIB) drives. My /etc/mkdev, which has an entry for "Internal flexible discs", leads me to believe this might work: mknod /dev/fd.0 b 1 0 # Right Block mknod /dev/fd.1 b 1 1 # Left Block mknod /dev/rfd.0 c 6 0 # Right Character mknod /dev/rfd.1 c 6 1 # Left Character You might want to look at /etc/conf/conf.c, at the bdevsw[] and cdevsw[] entries for some clues. My 5.3 version, which doesn't support the 236, has "nodev" for driver b1 and c6, so they are plausible. Perry Scott
cjames@hplchm.UUCP (11/18/87)
>I ran mkdev with the correct lines >uncommented, and the files fd.0, fd.1, rfd.0, and rfd.1 were created >in the /dev directory. I then tried to run mediainit on one of the >drives, but got the error message "no such device". This is almost always caused either by having the address set wrong on the device, by having it on the wrong HPIB, or by having two devices at the same address on one bus. Here's an example from of two "raw" disks I use: crw-rw-rw- 1 root other 4 0x0e0100 Sep 11 16:14 1s0 crw-rw-rw- 1 root other 4 0x070100 Jun 2 12:14 701s0 The 1st, named "1s0" is HPIB 14 ("0e"), address 1 ("01"), drive 0 ("00"). The 2nd, named "701s0" is HPIB 7 ("07"), address 1 ("01"), drive 0 ("00"). Other things to watch for: Did you change the device's address when it was on? Most devices only look at their address switches at power-up, so you can only change the address when they are off. If you accidentally put two devices at the same address, usually BOTH will detect the error and go off-line; both may have to be turned off and back on before the system will work again. Hope this helps! Craig James The above opinions are mine and should not be construed as advice from the Hewlett-Packard Company.
rml@hpfcdc.UUCP (11/20/87)
> This is almost always caused either by having the address set wrong on the > device, by having it on the wrong HPIB, or by having two devices at the > same address on one bus. This is true for HP-IB discs, but the question was about the built-in floppies on the 236 (which have no settable addresses). Some possible causes (which may seem obvious - no insult intended if they are) are: a kernel configured without the floppy driver (named "flex" in the dfile), no media in the drive, or drive door not closed. Bob Lenk {ihnp4, hplabs}!hpfcla!rml