Gregory's Serveryeah i am guessing the machine type in the IDPROM is invalid so the installer runs the wrong code.
|
143 comments
  @tubetime you just need to port solaris 10 to it and then as long as the memory error is not in kernel memory the process would be killed and the location blacklisted. i bet it is this issue. basically the ZuluSCSI returns values for disk geometry that somehow confuses the Solaris partition tool. one solution is to use a real SCSI hard drive and then dd it over to the ZuluSCSI once the install is completed. https://github.com/ZuluSCSI/ZuluSCSI-firmware/discussions/122#discussioncomment-4418076  @tubetime damn, I wonder if it’s some kind of Mac-compatibility that’s breaking on SPARC? Many years ago I wrote a little tool called "scsi-ping" which gives you a working disktab entry for a SCSI disk. It's still out there somewhere. zululog.txt has the smoking gun: [996859ms] WARNING: Host used command 0x1A which is affected by drive geometry. Current settings are 63 sectors x 255 heads = 16065 but image size of 2097152 sectors is not divisible. This can cause error messages in diagnostics tools. i think the solution here is to resize the disk image file so it is divisible by 63*255*512. @tubetime This all reminds me of my days with @Migueldeicaza helping him port Linux (him the kernel, me the rest of Red Hat) to the SPARC. The hardware had some idiosyncrasies but we USUALLY found them to all have fairly good reasons. Usually. My favorite thing was getting Linux to install to one from tape. AFAIK I’m the only person to ever do that. @tubetime this FF is suspiciously looking like high-Z.  @tubetime 6D B6 DB is a worst-case test pattern for MFM encoding, so the NAND flash chips in your SD card must not have enough timing margin for the channel code.   @tubetime the one part of the spinning rust drive you didn't want it to emulate @tubetime might not be helpful, as it’s a fairly different machine, but I recently watched this video of someone getting a SPARCclassic up and running off a bluescsi v1, and they seemed to have a good reason to use scsi id 3 https://youtu.be/SMz2y-wdbzs @tubetime I have a vague memory of some early Sun stuff usurping SCSI ID 0, but can't recall the details.  @tubetime the network is the computer, and the computer is a time machine  @tubetime yeah so external drives used to ship with all the little jumpers off (ID=0) and if you plugged that into your Sun4 it wouldn't boot and then you'd call the service department ... so they wanted to make the main disk some other ID but everyone assumes the boot volume is sd0 ... so some evil genius came up with this plan. The *good* external drives had a little pushbutton wheel thingy on the back to change their ID :-)  @tubetime I agree with the sun engineers. Why is something with a 20MHz CPU and 1gb of spinning rust (probs not the original, much more likely to ve 500MB) even powered on in 2023? @tubetime Isn't the boot drive SCSI ID set to 3 on early Sun systems?   @tubetime owo... i hope you saw @ncommander 's #Solaris livestreams... @tubetime Thanks for that! @tubetime Brings back happy memories. Should get my pizza box SparcStation out of the loft and see if it still works. Was running RH Linux last time it was fired up because I didn't have Sloaris installation media. @tubetime I had to do this for my lunchbox machines (an IPX and an LX) But for my Sun Blade 100, I had to do a whole different thing to recover the IDPROM of the three machines, only the IPX got a modern IDPROM replacement. The others have CR2032s with holders hacked in. :o( (though not the Duct Tape Special you had!) |
wrote a little FORTH program to update the contents of the IDPROM, and it looks like it has a valid host id now.