i just happen to have one, new in box! i bought this years ago at Weird Stuff Warehouse when they were still around. i have no idea why, but i'm glad i did.
looks like it is essentially the same protocol as the version of the mouse (type 4?) designed for the SPARCstation. the output is open collector, inverted async serial, 5 byte.
time to build an adapter. the connector is RJ11 (technically 6P4C) but it has these pins sticking out, presumably so you can't plug it into a phone jack.
four months later i made the Video Snake Oil board that can adapt 13W3 (any type!) to VGA. you just wire up the little pads to whatever your machine needs.
i've also installed a ZuluSCSI. this neat little board is a lot cheaper than a SCSI2SD. i'm going to try and install Solaris using a CDROM ISO file. CD6_512.iso is placed on the SD card. it'll be ID 6, 512 bytes per sector.
spoke too soon. another parity error, this time at U677. why there? because that's where i moved the module that was at U676. think i will just pull that bank of RAM for now.
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.
Hiya, I've got my ZuluSCSI installed in a sparcstation 2 and while it's definitely working...something is amiss. I can boot from CD image and Solaris 2.7 sees the hard drive image but I've having s...
[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.
that wasn't the solution lol :blobsweats: there's no more zululog.txt error but the superblock isn't getting written correctly. 6D B6 DB 6D is the test pattern written by the format command. could be somehow corrupting it during the write?
spinning rust refuses to boot when the SCSI ID is set to 0. I can set it to 1 and it will boot partway but the fstab is configured for 0 so it won't work.
ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •it seems to run with 12MB RAM. no more parity errors this time. but now the installer hates my SCSI drive (a ZuluSCSI).
filesystem creation failed for / 🤔
ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •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.
github.com/ZuluSCSI/ZuluSCSI-f…
Has anyone used ZuluSCSI on a SPARCStation? · ZuluSCSI/ZuluSCSI-firmware · Discussion #122
GitHubToOoOoB👻Time
in reply to ToOoOoB👻Time • • •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.
ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •ToOoOoB👻Time
in reply to ToOoOoB👻Time • • •SunOS 4.1.4 says it can't possibly be the year 2023: "WARNING: preposterous time in filesystem -- CHECK AND RESET THE DATE!"
sorry SunOS, there's nothing i can do to fix 2023.
reshared this
xChaos and Ozzelot :anarchy: :linux: reshared this.