Kliman01
January 15th, 2006, 14:28
I picked up a SPARCstation 20 with 3 NICs in it for nothing...seemed like a perfect pf box. I've downloaded the bootable CD for 3.8/sparc and am able to boot from the CD without any problems. All the hardware is found, and the installation goes as you would expect it to.
The first thing that raises my eyebrows is the "Making all device nodes" (I think that's what it says) takes about 5 minutes, then a bunch of scsi-related stuff goes by on the screen before the system restarts. I figured this might be a bad drive, so I swapped it for a known-good drive and had the same results.
When the system tries to boot from the disk, I get the following error:
Boot device: /iommu/sbus/sdpdma@f,400000/esp@f,800000/sd@3,0:a File and args: bsd
The file just loaded does not appear to be executable.
I followed the sparc installation instructions, and so far I have tried the following:
setenv boot-file bsd
setenv boot-device disk0:a
setenv boot-device disk3:a
sometimes I would get a "Can't open boot device" error, which leads me to believe that the boot-device disk3:a is actually correct...seems like there's something wrong with the boot block.
If anybody has seen anything like this and can point me in the right direction, that would be much appreciated.
Thanks in advance.
The first thing that raises my eyebrows is the "Making all device nodes" (I think that's what it says) takes about 5 minutes, then a bunch of scsi-related stuff goes by on the screen before the system restarts. I figured this might be a bad drive, so I swapped it for a known-good drive and had the same results.
When the system tries to boot from the disk, I get the following error:
Boot device: /iommu/sbus/sdpdma@f,400000/esp@f,800000/sd@3,0:a File and args: bsd
The file just loaded does not appear to be executable.
I followed the sparc installation instructions, and so far I have tried the following:
setenv boot-file bsd
setenv boot-device disk0:a
setenv boot-device disk3:a
sometimes I would get a "Can't open boot device" error, which leads me to believe that the boot-device disk3:a is actually correct...seems like there's something wrong with the boot block.
If anybody has seen anything like this and can point me in the right direction, that would be much appreciated.
Thanks in advance.