![]() The main use for this flag is by MAKEDEV itself. OPTIONS -n Do not actually update the devices, just print the actions that would be performed. Kernel does not have the driver configured or loaded. That the device file is missing, whereas ``ENODEV: No such device'' normally means the Note that programs giving the error ``ENOENT: No such file or directory'' normally means DESCRIPTION MAKEDEV is a script that will create the devices in /dev used to interface with drivers in The EFS partition for my image was number 7.SYNOPSIS cd /dev. ![]() It was a surprise to me that the partitions can (and do!) overlap! Apparently it’s typical for one of the partitions to represent the whole disk, another this header section, and another for the actual partition (the partitioning SunOS uses also has overlaps like this). The Partitions field contains what block offset each partition starts at, how long it is, and its filesystem type. Its apparently usually used for the bootloader and the SGI partitioning program, fx (this is apparently why partitioning happens outside of the OS install process). The VolumeDirectory field is pretty neat - its an array of pointers to files that exist outside of any filesystem, directly in the volume header. It’s a little bit annoying to set up - you can easily set the second, etc, drive to be a CD-ROM but loading the ISO on to it requires dd-ing the ISO to the appropriate offset after your primary disk. Whyyyyyyyyy /Un66ORSCHf- cron mom June 15, 2018Įventually I gave up and went with plan b: the SCSI2SD can emulate multiple drives. I tried swapping terminators, turning on and off termination on the internal drive, setting the “parity” jumper on the CD-ROM, reseating all the cabling, and nothing could keep it stable enough to complete a full install. Use active termination and target drives by LUN- cron mom June 14, 2018Īfter I’d start the install, I kept hitting a bus timeout, and it seemed to never recover. If yr having scsi problems I feel bad for u son With IRIX 5.3 burned to a CD, the hard drive formatted, and (so I thought) all the SCSI problems behind me, I booted in to the installer and watched expectantly. I also took this opportunity to downgrade from IRIX 6.5 to 5.3 - while 6.5 ran OK, my Indy only has 64 MB of RAM and I’ve seen recommendations to use older versions of IRIX for best performance on lower-spec Indys. The previous OS had been loaded via netboot and controlled via a serial console - I had neither a CD-ROM drive nor a suitable keyboard and mouse at the time, so this would be my first graphical install. SCSI gremlins ruin an eveningĪ disk replacement is a natural opportunity to install a fresh OS. When I set it to ID 1, I was able to format it with fx and move on to the install. When the SCSI2SD is set to 0, the Indy believes that all SCSI IDs are pointing to the SCSI2SD, and basically nothing works. Unfortunately, SGI assigns ID 0 to the controller ( most systems assign the controller ID 7). Out of the box, the SCSI2SD acts as a hard drive on SCSI ID 0 - a reasonable configuration for most systems. First, the firmware my v6 had loaded on it seemed to have some odd bugs - the Indy wouldn’t POST with it connected! I tried a lot of variations of settings and what ended up working was…updating the firmware of the drive. Installing the new drive took a few steps.
0 Comments
Leave a Reply. |