Releases: the-machine-hall/openbsd-sgi
OpenBSD/sgi 7.8
Kernel images
The kernels in this release were again all made with Cavium Octeon based hardware (Ubiquiti/UniFi USG PRO 4, although the root FS used the "usg" hostname instead of "usg4" out of carelessness) this time, using an OpenBSD/octeon kernel with OpenBSD/sgi userland and a modified environment (e.g export MACHINE=sgi before the build is enough for kernel builds, userland builds need a little more work).
So far only kernel images are provided (for details about the supported machines see OpenBSD/sgi and intro(4)):
| Hardware | Family | Kernel | Variant | Hash value | dmesg |
|---|---|---|---|---|---|
| IP24 | IP22 | IP22 | GENERIC-IP22 | 063f240e0639b8c1b77064ce21ddf504d724ae038eb02d53f53d5a0b30d6838e (SHA256) |
R4400 Indy log |
| R4600 Indy log | |||||
| IP26 | IP22 | IP26 | GENERIC-IP26 | 8ef8b07c043643a33984e4f88b41f902f4b950bdddffb57e0db4d7e4a2c59f26 (SHA256) |
untested as I don't have an R8000 Indigo² |
| IP28 | IP22 | IP28 | GENERIC-IP28* | ea22db54a90d0e7655935805c6674c9d559688697d1517e4f17cae1fecda7021 (SHA256) |
R10000 Indigo² log |
| IP29 | IP27 | IP27 | GENERIC-IP27** | 3abea500e1c6121f4ea20fa8c5c8e17ec974abf196aced4b6992634e4b71657f (SHA256) |
dual node R10000 Origin200 log |
| GENERIC-IP27.MP** | eec9ad5443c177fb53d0e5bf28cb17e169af42fb221063a72f9e414936d9ca65 (SHA256) |
R12000 Origin200 log | |||
| dual node R10000 Origin200 log | |||||
| IP30 | IP30 | IP30 | GENERIC-IP30 | 4600dfde9b42172a5671378ce1c6eb9dc6313ea86f6868cbb8b9302402b88f16 (SHA256) |
R12000 Octane2 log |
| GENERIC-IP30.MP | b895ffd5c8890bd9d0d46119e28f6e2a831d2d4f6f43e6a1c1578abd60ce703e (SHA256) |
R12000 Octane log | |||
| IP32 | IP32 | IP32 | GENERIC-IP32 | 39cdf2b35edc16b8ef0d5cb9acfa5f0b5f4cd481056cd7c70bad7f630491be58 (SHA256) |
R5000 O2 log |
*) The kernel image for IP28 includes the fixes/workarounds from #1 (#1 (comment)) and #2 (#2 (comment)).
**) The kernel image for IP27(.MP) is broken on a dual-node R10000 Origin200, see #3 for details. NOTICE: Single-node Origin200s and the SP kernel are not affected by this issue.
Userland
For the userland you can ATM use OpenBSD/octeon based file systems. Create one with nfsrb2 for example. But this won't allow you to build OpenBSD/sgi kernels as gcc 4.2.1 is missing. To build the kernels use for example an OpenBSD/sgi 7.3 based file system with an older than 7.8 kernel, because these won't work with 7.3 file systems (difference is bigger than two versions between 7.8 kernel and 7.3 userland in this direction. IIUC in the other direction it's even only one version of difference allowed).
OpenBSD/sgi 7.7
Kernel images
NEW: The kernels in this release were all made with Cavium Octeon based hardware (Ubiquiti/UniFi USG PRO 4 and USG) this time, using an OpenBSD/octeon kernel with OpenBSD/sgi userland and a modified environment (e.g export MACHINE=sgi before the build is enough for kernel builds, userland builds need a little more work). Especially the USG PRO 4 cuts down build times considerably compared to the Octane with dual R12K at 300 MHz that was used before.
So far only kernel images are provided (for details about the supported machines see OpenBSD/sgi and intro(4)):
| Hardware | Family | Kernel | Variant | Hash value | dmesg |
|---|---|---|---|---|---|
| IP24 | IP22 | IP22 | GENERIC-IP22 | 7d5bfba5a2f0ad887691a71093caae1b7baf930cce83fc3af895a4bd156f2b8f (SHA256) |
R4400 Indy log |
| R4600 Indy log | |||||
| IP26 | IP22 | IP26 | GENERIC-IP26 | 0ab34a1f92e75196b14fdeea911ac7ac880347220c2223a34c838184cd8efabd (SHA256) |
untested as I don't have an R8000 Indigo² |
| IP28 | IP22 | IP28 | GENERIC-IP28* | 94df28245d9a3bc4265b561e3f392dedbdcd91de584832e64b06024a950cf73a (SHA256) |
R10000 Indigo² log |
| IP29 | IP27 | IP27 | GENERIC-IP27** | 625d3f579ce7162ba07534ee77f670312f90e264c4eedcc4fe64db2fbcd0f829 (SHA256) |
R12000 Origin200 log |
| GENERIC-IP27.MP** | d24b5a706a23522520f3af1fd512e9db527ffe082ad6a1c959d1c97adacbf047 (SHA256) |
R12000 Origin200 log | |||
| dual node R10000 Origin200 log | |||||
| IP30 | IP30 | IP30 | GENERIC-IP30 | 876619c2190e809da2eab94cd59520472ed8e8a72a9c533b756ec7068e7bc89b (SHA256) |
R12000 Octane2 log |
| GENERIC-IP30.MP | 88d342360f494a5bccf5d713ea65d24f815de942464b47e9797d98bda14c0eec (SHA256) |
R12000 Octane log | |||
| IP32 | IP32 | IP32 | GENERIC-IP32 | 6f6649b01cac3da0b8db2aaea1774ab2689d3f4f7c49e8ba2868715520ceea7b (SHA256) |
R5000 O2 log |
*) The kernel image for IP28 includes the fixes/workarounds from #1 (#1 (comment)) and #2 (#2 (comment)).
**) The kernel image for IP27(.MP) is broken on a dual-node R10000 Origin200, see #3 for details. NOTICE: Single-node Origin200s and the SP kernel are not affected by this issue.
Userland
For the userland you can ATM use OpenBSD/octeon based file systems. Create one with nfsrb2 for example. But this won't allow you to build OpenBSD/sgi kernels as gcc 4.2.1 is missing. To build the kernels use for example an OpenBSD/sgi 7.3 based file system with an older than 7.7 kernel, because these won't work with 7.3 file systems (difference is bigger than two versions between 7.7 kernel and 7.3 userland in this direction. IIUC in the other direction it's even only one version of difference allowed).
OpenBSD/sgi 7.6
Kernel images
So far only kernel images are provided (for details about the supported machines see OpenBSD/sgi and intro(4)):
| Hardware | Family | Kernel | Variant | Hash value | dmesg |
|---|---|---|---|---|---|
| IP24 | IP22 | IP22 | GENERIC-IP22* | d4cd82917eb70d14dec0d29c2c3d11f639e54b3bb8a672aa11255e7512017556 (SHA256) |
R4400 Indy log |
| R4600 Indy log | |||||
| IP26 | IP22 | IP26 | GENERIC-IP26 | b293120e74dc1d1a92f968c00ff0c34c36b61487c90b7b7c09002833f9e280a4 (SHA256) |
untested as I don't have an R8000 Indigo² |
| IP28 | IP22 | IP28 | GENERIC-IP28** | 1d7c44d61e72c0629e973b2f5b8ce14e358f550be157f14a2a1588dfe0b1f222 (SHA256) |
R10000 Indigo² log |
| IP29 | IP27 | IP27 | GENERIC-IP27*** | 4eb6e4c6b5e9bd9493c23734f4e3778b3a35b6718e3628d35af5468152a1a61c (SHA256) |
R12000 Origin200 log |
| GENERIC-IP27.MP*** | 31c1edd58e21eba827b6fddd5400434fb0c196b54472b43c74f476d980c72e98 (SHA256) |
R12000 Origin200 log | |||
| dual node R10000 Origin200 log | |||||
| IP30 | IP30 | IP30 | GENERIC-IP30 | 82626ba21894fd47effcfb9b206dd0f6760e99f72dac19aa7d25a00efa2c5604 (SHA256) |
R12000 Octane2 log |
| GENERIC-IP30.MP | 9d23d4ca5f023ba10153a1cbce709b4aa8c4e11f47eaa866193e1d52981a8c0b (SHA256) |
R12000 Octane log | |||
| IP32 | IP32 | IP32 | GENERIC-IP32 | 01a6126e89ba31c9170f02b612239d6a5d81b577cee0fc2934927a2db1804a2d (SHA256) |
R5000 O2 log |
*) There seems to have been a hardware issue with either the SCSI controller or the installed SCSI terminator in my R4600 Indy that made the controller listed as unconfigured during testing, when comparing 7.6 and 7.5 logs. I only noticed this when preparing the logs for upload to NYC*BUG's dmesgd and linking here.
**) The kernel image for IP28 includes the fixes/workarounds from #1 (#1 (comment)) and #2 (#2 (comment)).
***) The kernel image for IP27(.MP) is broken on a dual-node R10000 Origin200, see #3 for details. NOTICE: Single-node Origin200s are not affected by this issue.
Userland
For the userland you can ATM use OpenBSD/octeon based file systems. Create one with nfsrb2 for example. But this won't allow you to build OpenBSD/sgi kernels as gcc 4.2.1 is missing. To build the kernels use for example an OpenBSD/sgi 7.3 based file system with an older than 7.6 kernel, because these won't work with 7.3 file systems (difference is bigger than two versions between 7.6 kernel and 7.3 userland in this direction. IIUC in the other direction it's even only one version of difference allowed).
OpenBSD/sgi 7.5
Kernel images
So far only kernel images are provided (for details about the supported machines see OpenBSD/sgi and intro(4)):
| Hardware | Family | Kernel | Variant | Hash value | dmesg |
|---|---|---|---|---|---|
| IP24 | IP22 | IP22 | GENERIC-IP22 | 492c895153aeff7dac8944511741018d365c8378e9ed9dda0f893be0ddea7582 (SHA256) |
R4400 Indy log |
| R4600 Indy log | |||||
| IP26 | IP22 | IP26 | GENERIC-IP26 | 32de1333475189b2883fb2e3a5c29813443bbf52c6490a806a1a641b35dd0781 (SHA256) |
untested as I don't have an R8000 Indigo² |
| IP28 | IP22 | IP28 | GENERIC-IP28* | 63a383fec721ded84aa651f532f3d328c14f1470d63c96bfd7affe948e1ce479 (SHA256) |
R10000 Indigo² log |
| IP29 | IP27 | IP27 | GENERIC-IP27 | 0e6d5ba98a977cd79bc27bd13b69b43d456011f8e7921988caa16bab497f0670 (SHA256) |
R12000 Origin200 log |
| GENERIC-IP27.MP | c464a585fa8c8345642c5402408a391b5a7e44f63d4b530ffa9c3860f917c2b4 (SHA256) |
R12000 Origin200 log | |||
| dual node R10000 Origin200 log | |||||
| IP30 | IP30 | IP30 | GENERIC-IP30 | 04b6fcb3b686039892114d7b1d2e3c5b5a45e189d55d738ced0ea7e4098a2337 (SHA256) |
R12000 Octane2 log |
| GENERIC-IP30.MP | 15f3fc62004c0fd34c92d0ae0c127b40bb1d248a63de60dda8f32823e1d2ef83 (SHA256) |
R12000 Octane log | |||
| IP32 | IP32 | IP32 | GENERIC-IP32 | 5c8417e2da61c983c96ab07df19103954adba5c4c3f07764bf66fcc718d8be03 (SHA256) |
R5000 O2 log |
*) The kernel image for IP28 includes the fixes/workarounds from #1 (#1 (comment)) and #2 (#2 (comment)).
Userland
For the userland you can ATM use OpenBSD/octeon based file systems. Create one with nfsrb2 for example. But this won't allow you to build OpenBSD/sgi kernels as gcc 4.2.1 is missing. To build the kernels use for example an OpenBSD/sgi 7.3 based file system. If 7.5 kernels don't work with 7.3 file systems, you need to use an older kernel version than 7.5 with those.
OpenBSD/sgi 7.4
Kernel images
So far only kernel images are provided (for details about the supported machines see OpenBSD/sgi and intro(4)):
| Hardware | Family | Kernel | Variant | Hash value | dmesg |
|---|---|---|---|---|---|
| IP24 | IP22 | IP22 | GENERIC-IP22 | 08b84351c05d69445b322c8e7b8d9f6306ffc02121c9093e64b6528bc4a99de3 (SHA256) |
R4400 Indy log |
| R4600 Indy log | |||||
| IP26 | IP22 | IP26 | GENERIC-IP26 | d1ec4e238519f08551d83d44e082aa4b4f28acdd083a34148666bf61305d1198 (SHA256) |
untested as I don't have an R8000 Indigo² |
| IP28 | IP22 | IP28 | GENERIC-IP28* | 1d5690621ce3f04b6ea48a8fd3e45b83e091f43abf4b983121522b939487aca7 (SHA256) |
R10000 Indigo² log |
| IP29 | IP27 | IP27 | GENERIC-IP27 | 0442652cea0eae4d29745199d09c66e7772f5c96a41de7d965eb5bfb159671c8 (SHA256) |
R12000 Origin200 log |
| GENERIC-IP27.MP | 662494625d69bf33f9f76795cee06f9d23eb49d7b6219003fc2515aa8c1f687b (SHA256) |
R12000 Origin200 log | |||
| dual node R10000 Origin200 log | |||||
| IP30 | IP30 | IP30 | GENERIC-IP30 | 2243e8ba798207b67928dd6161d1d502f9b91f1390a6a5889432a08fff44f818 (SHA256) |
R12000 Octane2 log |
| GENERIC-IP30.MP | 476ff2d554bebbd62dd961107181d7f09b469f614043c80defa5b901b30bb1b9 (SHA256) |
R12000 Octane log | |||
| IP32 | IP32 | IP32 | GENERIC-IP32 | a778075c2591f90af710d1da4d9b4dc1c0247092b44e4e693a71e8a9f3c7dd1c (SHA256) |
R5000 O2 log |
*) The kernel image for IP28 includes the fixes/workarounds from #1 (#1 (comment)) and #2 (#2 (comment)).
Userland
For the userland you can ATM use OpenBSD/octeon based 7.4 file systems (create one with nfsrb2 for example) - But this won't allow you to build OpenBSD/sgi kernels as gcc 4.2.1 is missing. To build the kernels use for example the new OpenBSD/sgi 7.2 based file system.
OpenBSD/sgi 7.3
UPDATES
2024-07-06
A complete release (w/o Xenocara, w/o LLVM/clang and w/o an install73.iso (which might require Xenocara)) of OpenBSD/sgi 7.3 is available from:
FTP and rsync access are still planned for the future.
This also includes newly built kernels (incl. RAMdisk kernels for e.g. installation purposes). Their codebase doesn't differ from the ones available from GitHub below, so their functionality should be identical, but so far none have been tested.
tbd
NOTICE: This release does not ship with LLVM/clang. This because the amount of time needed to compile LLVM/clang on my build system (Octane w/dual 300 MHz R12K) is more than 110 hours, whereas for a complete release w/o LLVM/clang it "only" needs about 12 hours to compile and another 10 hours to create the release files. To use software from OpenBSD ports with this release you need to copy over LLVM/clang related libraries from an octeon filesystem or base set. This because the software from OpenBSD ports is built with LLVM/clang and requires the related libraries to be present to run. Copying the following files made it work for me:/usr/lib/libLLVM.so.6.0 /usr/lib/libc++.a /usr/lib/libc++.so.8.0 /usr/lib/libc++_p.a /usr/lib/libc++abi.a /usr/lib/libc++abi.so.5.0 /usr/lib/libc++abi_p.a /usr/lib/libcompiler_rt.a..., tested with
nano,htop,git,7zandeopenssl-3.0.
To verify the contents of the release fles I have created a signify(1) keypair and signed the SHA256 file (resulting in SHA256.sig). For downloads via HTTP only I publish the contents of SHA256.sig here, too:
untrusted comment: verify with https://raw.githubusercontent.com/the-machine-hall/openbsd-src/intro/openbsd-sgi-is-alive.pub
RWRmGQ1rewM9vD6VNBdikL8XV7rh4CQDQma+dggTEjR7D1Dk0KSEywjH2SF0SadGzipl3/C96DFONp0wxxKerl/UN2Q4fzjcxgc=
SHA256 (BUILDINFO) = e265318ff8dd89e52c3b5c79e90306e78af164b77c0a095793c10ddd864581c2
SHA256 (INSTALL.sgi) = f99354cae931770a06bc06bda57493d116d794eefc18f1e5099c792953bd4049
SHA256 (base73.tgz) = 47f7852dcf709fd5fd4b91fbc484d41d3d045e35cf58f69fbc10b7191389265e
SHA256 (boot32) = 5d4afbc4db0a441468fd66bf9829d35138e97bd254e9e6526e7f5ddf81010d9a
SHA256 (boot64) = b4f1689c3c8440c7bce2edb03307ad3497cf1983b3089894f8a5b17bc6311846
SHA256 (bootecoff) = c56fca957c3fb4121fe4eae53a7b5bf839dd83ceb88a17ca3ebf356aad7413ed
SHA256 (bsd.IP22) = eb1015e72040fbf2d38def2bbe62629efddeab3466decfed2e8a850683dc7846
SHA256 (bsd.IP26) = 5d1fa3e37c04ace9e63fa80b5cbb205d39f4967259ccd74856bf18e735d1af7d
SHA256 (bsd.IP27) = ec7207c8c6bb799dbe7612c5aa2f07b0735f67b0edd19b85f787b7cfbf23d8c9
SHA256 (bsd.IP28) = 51c6568eecbbe974384020a1ff3220c2c13970a345cba3439bb80438a141ae71
SHA256 (bsd.IP30) = ac52ad8f027c640ecec04b560506038ddd5a7f55a5d7d0a1550622f08c08b93f
SHA256 (bsd.IP32) = 943089e9504c5feed24123d1e464249b1ed20cad56400af5da2f57939fadb981
SHA256 (bsd.mp.IP27) = e85ba1337dac5b94cf5da058ef33aaccc7cefbb3cb38fc3d414c008272b7158e
SHA256 (bsd.mp.IP30) = 0914d9660073687e4e409d20d271d3ea5ec8465e0aa8929c684e2aa37f90d2d7
SHA256 (bsd.rd.IP22) = 85168b61893f5da1b910c0685b31ca564fc18a74e468c09a04ac947e53d06f78
SHA256 (bsd.rd.IP26) = a4feee2377d551cf9583865b21e9567dce9867f57bb4f88ededc1c2cb58f3b5e
SHA256 (bsd.rd.IP27) = 15f2eb1c5d976b70dcc11f65af73e48a9ebe3974bd035d2dee7799a316d9a7c5
SHA256 (bsd.rd.IP28) = b6a6be49dba4fd9f5e5b24b1062e00c4812ab1eeb486487f1bb024e160531167
SHA256 (bsd.rd.IP30) = 1fcbb7f82a182c49b54ff8c137a1867b5a4941e040657693ca8d14082f5439d9
SHA256 (bsd.rd.IP32) = 71aa0bb7271735b71add3235484b10b932d45b670877179da07c9212ece2e80b
SHA256 (cd73.iso) = 922ce56da3c8928d48aff26e60dc7348432ee08d9ee7dfb3938815edc673ebc0
SHA256 (comp73.tgz) = 26488987f8d430169c17d4a39c5946d2ef9c41426b5974ee04d28e425ea8ec32
SHA256 (game73.tgz) = 965fd2ebecc5cf4e5e9ac10e51d6dd1a9a9b0a73ff894bea76c81af2e1e2cdcd
SHA256 (man73.tgz) = ebd34f8120f2767ae10ba0e9a25c2f4c870389b02e3f4809a627c3731cb6b3e9
You can hence verify that what you downloaded comes from me by using signify on OpenBSD (or e.g. signify-openbsd on Debian GNU/Linux) using my signify public key below.
My signify public key is:
RWRmGQ1rewM9vHtQ6vMcAUnRrsJqKO/Z+n07CXxQkTPpAOnsVa26CIUj
...and also available via https://raw.githubusercontent.com/the-machine-hall/openbsd-src/intro/openbsd-sgi-is-alive.pub.
2023-04-26
Added boot logs for R4600 Indy and dual node R10000 Origin200.
2023-04-23
New kernel image for IP28 uploaded. This one includes the fix/workaround from #2 (comment) and fixes/works around the breakage on IP28 described in #2. After finding out that the breakage on IP22 is not new but already present in earlier versions at least since 6.9 I consider the IP22 image OK.
Kernel images
So far only kernel images are provided (for details about the supported machines see OpenBSD/sgi and intro(4)):
| Hardware | Family | Kernel | Variant | Hash value | dmesg |
|---|---|---|---|---|---|
| IP24 | IP22 | IP22 | GENERIC-IP22 | f6ae04fe165a191558badb5d6e0ca21351173eeebd4ae64347ba619a1450b9a6 (SHA256) |
R4400 Indy log |
| R4600 Indy log | |||||
| IP26 | IP22 | IP26 | GENERIC-IP26 | b1af32c53f5ec8f4aad5689cb05fed13ba387118fb4506c6dc267d1972cfa790 (SHA256) |
untested as I don't have an R8000 Indigo² |
| IP28 | IP22 | IP28 | GENERIC-IP28 | a0fbb345ae815c40c2bc14b5f39196e9d801792eef8ae5588d9c929ed3c745d7 (SHA256) |
R10000 Indigo² log |
| IP29 | IP27 | IP27 | GENERIC-IP27 | 2aee605d4d89c9b16417a91a486e9dd0d6c40c1e7b49d58bf0e4adadf683d719 (SHA256) |
R12000 Origin200 log |
| GENERIC-IP27.MP | 2ab2bb2996bcd86a3ef56fcc768948cf8fca0660d3b0df344bca49a29e6bbd44 (SHA256) |
R12000 Origin200 log | |||
| dual node R10000 Origin200 log | |||||
| IP30 | IP30 | IP30 | GENERIC-IP30 | e35496f27ceebbbce35a20d17de853513eab15ada7d99d1e0e254e3202d23ab4 (SHA256) |
R12000 Octane2 log |
| GENERIC-IP30.MP | c8736608fb7a53d70482ed94dadd11fc9bcb6f90175b16aa4eecec802d318d01 (SHA256) |
R12000 Octane log | |||
| IP32 | IP32 | IP32 | GENERIC-IP32 | a23e38c66ee8359970bba83cd32918476baee48adb7ce44587034fdd630a8b7b (SHA256) |
R5000 O2 log |
Userland
For the userland you can use OpenBSD/octeon based 7.3 file systems (create one with nfsrb2 for example). But this won't allow you to build OpenBSD/sgi kernels as gcc 4.2.1 is missing. To build the kernels use for example the new OpenBSD/sgi 7.3 based file system available from this release.
OpenBSD/sgi 7.2
UPDATES
2023-07-22
A complete release (w/o Xenocara, w/o LLVM/clang and w/o an install72.iso (which might require Xenocara)) of OpenBSD/sgi 7.2 is available from:
FTP and rsync access are still planned for the future.
This also includes newly built kernels (incl. RAMdisk kernels for e.g. installation purposes). Their codebase doesn't differ from the ones available from GitHub below, so their functionality should be identical, but so far none have been tested.
tbd
NOTICE: This release does not ship with LLVM/clang. This because the amount of time needed to compile LLVM/clang on my build system (Octane w/dual 300 MHz R12K) is more than 110 hours, whereas for a complete release w/o LLVM/clang it "only" needs about 12 hours to compile and another 10 hours to create the release files. To use software from OpenBSD ports with this release you need to copy over LLVM/clang related libraries from an octeon filesystem or base set. This because the software from OpenBSD ports is built with LLVM/clang and requires the related libraries to be present to run. Copying the following files made it work for me:/usr/lib/libLLVM.so.6.0 /usr/lib/libc++.a /usr/lib/libc++.so.8.0 /usr/lib/libc++_p.a /usr/lib/libc++abi.a /usr/lib/libc++abi.so.5.0 /usr/lib/libc++abi_p.a /usr/lib/libcompiler_rt.a..., tested with
nano,htop,git,7zandeopenssl-3.0.
To verify the contents of the release fles I have created a signify(1) keypair and signed the SHA256 file (resulting in SHA256.sig). For downloads via HTTP only I publish the contents of SHA256.sig here, too:
untrusted comment: verify with https://raw.githubusercontent.com/the-machine-hall/openbsd-src/intro/openbsd-sgi-is-alive.pub
RWRmGQ1rewM9vD3uB3EJ2fOMkh+p5Jb2GGZ3RY2oyJbmbGdUB1ehM6DiAiJmCt1njDLYsHsuorSnYnCNjyBKpaB0LF5EUXxHMgM=
SHA256 (BUILDINFO) = cafa9e3cc864008aeb485c921346cfb7a7fe697838eef1b44ff6e8bab560e4ff
SHA256 (INSTALL.sgi) = 94ae211d9c518597c7231e7834674ba8a19ca1b7087cba52c52e1f764c7016aa
SHA256 (base72.tgz) = 68e6af59256c1a478a9d7ef6251e458028baecc4492db404aff9923d3db9a25e
SHA256 (boot32) = 1a1fe8e258a2219dc4a7a5dc8789260f51529fbee3357186f48641e1b655a5b5
SHA256 (boot64) = 5e1a9acaa0d9c1e0e505a82f49c647bc65ef700ddefdae74bc2fea86307bae7d
SHA256 (bootecoff) = 4c59f1e7c0fc849f2693d627db7f74a3c6b4af65bc73ec8d221c13061eb97ee5
SHA256 (bsd.IP22) = d6cbc57b5339a9320d75231514a247de3a88e230354a634f6971340ff4011483
SHA256 (bsd.IP26) = b4c828716a1835274842b679cfb2b74a0aaf1cbbcdd515e2f9164152300b44e4
SHA256 (bsd.IP27) = 9ee5941d5a0f673dbe180081fa8cc34531aede39154833b17d689a9892464e41
SHA256 (bsd.IP28) = 0260206c4d3f2e5bb39fd9facc5bc06728a98c61a34568e395f3ddc80d5eb03c
SHA256 (bsd.IP30) = cf68699ebc0a4268c9a6bfc58142b0381d33b9d5f54db912e16a4560c61ec363
SHA256 (bsd.IP32) = f37e8fba7c26eb044c4278d2084c1e78dadcb5a4338ae5afece9322d8fc2814e
SHA256 (bsd.mp.IP27) = 93df8c0952b31a95c6813effb9eb04ae0d3d41c0ddc3306dabd1a7f8f0ca0669
SHA256 (bsd.mp.IP30) = 6f39a2b8d27abee19a5a7d93ee6f549e4733bc758a4bb9ec185ce1f24e567a86
SHA256 (bsd.rd.IP22) = ac6d28fb89db6897edeb7d0db08c554e0fdb818c1e746198c60802f8dd16c32e
SHA256 (bsd.rd.IP26) = b88bc7e144a57ca8503ff1a82cf3fea258aa0b8e3581c5cc6ae4208c594279b8
SHA256 (bsd.rd.IP27) = 7b8d8f8cabb09f1491d70a7faafc11231b68877051aad043b58f7fda4a96e8a5
SHA256 (bsd.rd.IP28) = 7f0fd48789a5a12ae8551aaa7579e490aa29ccc7c07ab45d0a60214084971327
SHA256 (bsd.rd.IP30) = 30cee20df779a50b559e7ed00dc8bb11c5f53fccaa5fbe8bb9cfc2d3bf227b06
SHA256 (bsd.rd.IP32) = 9a39e1ded15eec9e98d99495b5bcf19bdc8af1d6f3092b2b262dcbcb3ef77c35
SHA256 (cd72.iso) = db25ef1a76c4df041c0dc4b0c2251a1a764910f04b6c5540254337eb0f5af98a
SHA256 (comp72.tgz) = bfbdf2f815213e43209955ee96bf7d956517c7478a7691c397aee94434520835
SHA256 (game72.tgz) = dcaebe76495f19a6954f29c890dbd4dbf7c95c69f37a1592e252f02d1e994988
SHA256 (man72.tgz) = 1e96b312d279b25bccd3c9d380d204cc30c6b7a9ae63a3df365b18eeaf9452c0
You can hence verify that what you downloaded comes from me by using signify on OpenBSD (or e.g. signify-openbsd on Debian GNU/Linux) using my signify public key below.
My signify public key is:
RWRmGQ1rewM9vHtQ6vMcAUnRrsJqKO/Z+n07CXxQkTPpAOnsVa26CIUj
...and also available via https://raw.githubusercontent.com/the-machine-hall/openbsd-src/intro/openbsd-sgi-is-alive.pub.
2023-04-26
Added boot logs for R4600 Indy and dual node R10000 Origin200.
2023-02-06
New kernel image for IP28 uploaded. This one includes the fix/workaround from #1 (comment) and fixes/works around the breakage on IP28 described in #1.
Kernel images
For details about the supported machines see OpenBSD/sgi and intro(4):
| Hardware | Family | Kernel | Variant | Hash value | dmesg |
|---|---|---|---|---|---|
| IP24 | IP22 | IP22 | GENERIC-IP22 | df272a69c882ca9eb8fb203827832099d7283ae44786d5db72f4ddf5246b1a19 (SHA256) |
R4400 Indy log |
| R4600 Indy log | |||||
| IP26 | IP22 | IP26 | GENERIC-IP26 | 2800ce41d9d0afe4caede304c32b8fb4b0cb2ef0b8ab5dc1c3be1dd922ddf057 (SHA256) |
untested as I don't have an R8000 Indigo² |
| IP28 | IP22 | IP28 | GENERIC-IP28 | fdc084d69783900c65a1ea007a452b22e8227be800dfcb7baae87ad38f6b1f6b (SHA256) |
R10000 Indigo² log |
| IP29 | IP27 | IP27 | GENERIC-IP27 | bb34cc0657434ea80b8fa0ee6d92fbfbce6113204cb2d0ce31c2542fded191db (SHA256) |
R12000 Origin200 log |
| GENERIC-IP27.MP | 3430e528726c08510de5c3b21e6d8f1bf584ec9968548a7b69c2ee3b05799fda (SHA256) |
R12000 Origin200 log | |||
| dual node R10000 Origin200 log | |||||
| IP30 | IP30 | IP30 | GENERIC-IP30 | b497e8634d809ff5199f582e6cca561a20ba6ab9a70992cbbfc213c9f5588676 (SHA256) |
R12000 Octane log |
| GENERIC-IP30.MP | 1e2e149b852a8d57d6fdc702e405468bdeb9bde5744bdc47b51862e0d422e92e (SHA256) |
R12000 Octane log | |||
| IP32 | IP32 | IP32 | GENERIC-IP32 | bafe2f6e1cfc87cddfb0a83b90997907bb594577004698c2387e0c3de6e1e5aa (SHA256) |
R5000 O2 log |
Userland
For the userland you can use OpenBSD/octeon based 7.2 file systems (create one with nfsrb2 for example). But this won't allow you to build OpenBSD/sgi kernels as gcc 4.2.1 is missing. To build the kernels use for example the new OpenBSD/sgi 7.2 based file system available from this release.
OpenBSD/sgi 7.1
UPDATES
2023-05-20
A complete release (w/o Xenocara, w/o LLVM/clang and w/o an install71.iso (which might require Xenocara)) of OpenBSD/sgi 7.1 is available from:
FTP and rsync access are still planned for the future.
This also includes newly built kernels (incl. RAMdisk kernels for e.g. installation purposes). Their codebase doesn't differ from the ones available from GitHub below, so their functionality should be identical, but so far none have been tested.
tbd
NOTICE: This release does not ship with LLVM/clang. This because the amount of time needed to compile LLVM/clang on my build system (Octane w/dual 300 MHz R12K) is more than 110 hours, whereas for a complete release w/o LLVM/clang it "only" needs about 12 hours to compile and another 10 hours to create the release files. To use software from OpenBSD ports with this release you need to copy over LLVM/clang related libraries from an octeon filesystem or base set. This because the software from OpenBSD ports is built with LLVM/clang and requires the related libraries to be present to run. Copying the following files made it work for me:/usr/lib/libLLVM.so.6.0 /usr/lib/libc++.a /usr/lib/libc++.so.8.0 /usr/lib/libc++_p.a /usr/lib/libc++abi.a /usr/lib/libc++abi.so.5.0 /usr/lib/libc++abi_p.a /usr/lib/libcompiler_rt.a..., tested with
nano,htop,git,7zandeopenssl-3.0.
To verify the contents of the release fles I have created a signify(1) keypair and signed the SHA256 file (resulting in SHA256.sig). For downloads via HTTP only I publish the contents of SHA256.sig here, too:
untrusted comment: verify with https://raw.githubusercontent.com/the-machine-hall/openbsd-src/intro/openbsd-sgi-is-alive.pub
RWRmGQ1rewM9vMKbBTe/bUsf7w5i1vPXHqEVam0sGPf4vSatonvsdajbiZTptswYfGXgQS9Uiff8oG5ONfE8zE6xGzEkRd+fAg4=
SHA256 (BUILDINFO) = 711cf622f1266a79e73ef1dc7351fecc6044f3e8c8e02f8380ba3a33f68b80dc
SHA256 (INSTALL.sgi) = ba32a3a1bb2b66acb2e83bdab4652365de2b69e14f35b591a072b8c76843c7f1
SHA256 (base71.tgz) = 7f9fc80f45658a3b50731321950df0b55d3b85c7b7af9c48034468d5c58e9034
SHA256 (boot32) = e437f461220f56862ec89282771440bce55787cdbcb3818d440e7206343078ca
SHA256 (boot64) = 41caa6e1ee6b380a20555b89f1dc01d802bf4b7c8e403147286a109d779f07ed
SHA256 (bootecoff) = cf2935dbba929d05d9ca0647926b553b6ef81b2adc9daa5ea2ecfe1d7444ea3f
SHA256 (bsd.IP22) = 36e16519e62654d9c2e38eb562315fdb114e445d6046f16fe2391c3e01142c3a
SHA256 (bsd.IP26) = 72841af434b403faf716ab1aab177797ffcf6bbacabde969f46be3c7394300fa
SHA256 (bsd.IP27) = 8a2b6e2d1e228edd9b0b9e0c13508c9640f0d5f9ec6e2f5a41e168935b7a7504
SHA256 (bsd.IP28) = 55352405101964b26ec77a822bfbdc50597dfdf7cb093f7e72e9068b9e8490f1
SHA256 (bsd.IP30) = b372abe75f8031736973dcd906a11ee630d8270ae856635b98ecf28d557704fd
SHA256 (bsd.IP32) = 10271be1309299c608e7329af801c4a9f299ea8b48458fdcaedc9b9c14013733
SHA256 (bsd.mp.IP27) = aed70ca605fc5519438f33b56727713d46f6ab22f54a24c7d7379be3e9c0bcbe
SHA256 (bsd.mp.IP30) = 7bc56d9c25a44803d335f1a45d1486c71c53775a5dc505af4baea168e82b7194
SHA256 (bsd.rd.IP22) = 8f0a4900ac6fbd9e3f2a50b0dbdee8500b26983f05d1fc327f6f6904c2ad1793
SHA256 (bsd.rd.IP26) = 73f8ad5511f06be14691bc44075fc9069bd258eafa320a9a8350b140f137669f
SHA256 (bsd.rd.IP27) = 397007e5ebded392c6da2fabf44d558f171d7121a6175c2049c26f688a16ee0a
SHA256 (bsd.rd.IP28) = 32f4c2be905b949d9e4ec84f04df46b4d75f86480a873b34b8d8ee3efcceff85
SHA256 (bsd.rd.IP30) = a1dfc6d2f7dccc7f1fc3dc3546f79cec472ccdc2a64840a4b0d01864dd831be4
SHA256 (bsd.rd.IP32) = eb648a671881e818b4461c6296202edc983f26b4d78e1e34b2b8fc8dd1fb0cb8
SHA256 (cd71.iso) = 1eb802d5e76c8db5aa1c5024d6ba7b76530922388f48599de75c0813088e8410
SHA256 (comp71.tgz) = 7033963ad5019e4606fa7b2f3457f9adf53222700d41b35ddafd7e12f03b9a92
SHA256 (game71.tgz) = e76629f6101a0948076951b682c3bbf0e2a115e928fc607983867a23fd2f0aac
SHA256 (man71.tgz) = 9eeb7e3421c2aa69f983529a49cd70ff4fb9c2a1fe33430a6cd5d32a3444c47d
You can hence verify that what you downloaded comes from me by using signify on OpenBSD (or e.g. signify-openbsd on Debian GNU/Linux) using my signify public key below.
My signify public key is:
RWRmGQ1rewM9vHtQ6vMcAUnRrsJqKO/Z+n07CXxQkTPpAOnsVa26CIUj
...and also available via https://raw.githubusercontent.com/the-machine-hall/openbsd-src/intro/openbsd-sgi-is-alive.pub.
2023-04-26
Added boot logs for R4600 Indy and dual node R10000 Origin200.
Kernel images
For details about the supported machines see OpenBSD/sgi and intro(4):
| Hardware | Family | Kernel | Variant | Hash value | dmesg |
|---|---|---|---|---|---|
| IP24 | IP22 | IP22 | GENERIC-IP22 | afd6b96068c7255ba9463d1eae49dd591a40fd3f9b684c2c109b633f3a48a6cf (SHA256) |
R4400 Indy log |
| R4600 Indy log | |||||
| IP26 | IP22 | IP26 | GENERIC-IP26 | 5aeba3cb1c6e385d959d61de43114cfdbb88b97c2b687af775714e87426efe2c (SHA256) |
untested as I don't have an R8000 Indigo² |
| IP28 | IP22 | IP28 | GENERIC-IP28 | 40a177158c7ed75dc6edd2e42cef4fb2d7eeea50587a7128ba7d346af156f83d (SHA256) |
R10000 Indigo² log |
| IP29 | IP27 | IP27 | GENERIC-IP27 | 3268a25d8c8d6e90aaabd406bf7dda18c9d008c94a9bc152e2e1907196b14587 (SHA256) |
R12000 Origin200 log |
| GENERIC-IP27.MP | aade269f2cef4b4f33402c608fb658ee6c02de2358f5ce8b6c1084d17c7ee829 (SHA256) |
R12000 Origin200 log | |||
| dual node R10000 Origin200 log | |||||
| IP30 | IP30 | IP30 | GENERIC-IP30 | cebfd9691c439a4f606df1760198d19d6b0516bbf3f684fdb6fb32147dceac0d (SHA256) |
R12000 Octane log |
| GENERIC-IP30.MP | 0cbc9fce642bdb892be5fb7f0166342472925db1095127ace31af9678af28624 (SHA256) |
R12000 Octane log | |||
| IP32 | IP32 | IP32 | GENERIC-IP32 | cf9eefef742142c1176e7f2beedb1fe6ba6525e73ac28d57e751e1f294286ea7 (SHA256) |
R5000 O2 log |
For the userland you can use OpenBSD/octeon based file systems (create one with nfsrb2 for example). But this won't allow you to build OpenBSD/sgi kernels as gcc 4.2.1 is missing. To build the kernels use for example the OpenBSD/sgi 7.1 based file system available from this release.
OpenBSD/sgi 7.0
UPDATES
2023-04-26
Added boot logs for R4600 Indy and dual node R10000 Origin200.
2023-02-06
A complete release (w/o Xenocara, w/o LLVM/clang and an install70.iso (which might require Xenocara)) of OpenBSD/sgi 7.0 is available from:
FTP and rsync access are planned for the future.
This also includes newly built kernels (incl. RAMdisk kernels for e.g. installation purposes). Their codebase doesn't differ from the ones available from GitHub below, so their functionality should be identical, but so far only the MP kernel for IP30 was tested.
NOTICE: This release does not ship with LLVM/clang. This because the amount of time needed to compile LLVM/clang on my build system (Octane w/dual 300 MHz R12K) is more than 110 hours, whereas for a complete release w/o LLVM/clang it "only" needs about 12 hours to compile and another 10 hours to create the release files. To use software from OpenBSD ports with this release you need to copy over LLVM/clang related libraries from an octeon filesystem or base set. This because the software from OpenBSD ports is built with LLVM/clang and requires the related libraries to be present to run. Copying the following files made it work for me:
/usr/lib/libLLVM.so.6.0 /usr/lib/libc++.a /usr/lib/libc++.so.8.0 /usr/lib/libc++_p.a /usr/lib/libc++abi.a /usr/lib/libc++abi.so.5.0 /usr/lib/libc++abi_p.a /usr/lib/libcompiler_rt.a..., tested with
nano,htop,git,7zandeopenssl-3.0.
To verify the contents of the release fles I have created a signify(1) keypair and signed the SHA256 file (resulting in SHA256.sig). For downloads via HTTP only I publish the contents of SHA256.sig here, too:
untrusted comment: verify with newkey.pub
RWRmGQ1rewM9vKdQMfJSaAmhwVhqgERjfUjChV1QGDPdjHgg8cq3VCrSo7PFN8BZcsTW86UpT3d2V82AQzklsQEevktE4r6cEwc=
SHA256 (BUILDINFO) = 366c4f4852a6a97c27a612fb297864abe323c2a1d31c22b178f58fcc39accef0
SHA256 (INSTALL.sgi) = b75f2aa88d7e3a63ca9e361c9cfb1d17d31db2dcfc9a8b152fc91744121f475a
SHA256 (base70.tgz) = f113c30195d831e78c45391da4b008be7df794e405d576b00d03790dd87cb5c8
SHA256 (boot32) = 9ecf9eafbd929cdbf4bd34e03b11a0494be239a571f6bc42ec81bb7e507585e8
SHA256 (boot64) = 002f10a5337bb5eace94435f9d71cc23288a789f1390b9b64ccf3c0c3966c871
SHA256 (bootecoff) = 2e61e7ff239def0cabcb63bc09b518b317e19f4c589310e6519148c3d9e95ab5
SHA256 (bsd.IP22) = c77712c374a6c1b39d2f0b05134ebde44f3581973ac38f85b989ff05f997e5bf
SHA256 (bsd.IP26) = 1524fc86a60dcadd81c0f05b68e0bb317e8da057cb29b888cc3fddb210c892eb
SHA256 (bsd.IP27) = 417dbe6887ea4a7539d69808565d69fb6fc6cde2791e1249ab3e8ace56917a31
SHA256 (bsd.IP28) = df47d38ba188eb64713329ab67db7c9ea6374c8f56bb77a79551802190658f4c
SHA256 (bsd.IP30) = 7f67855360567fafc21ec9fc07644a84d2777e0767ccd092f42f444ab74299ab
SHA256 (bsd.IP32) = c2b73de12524b4b80db56674b74b89be37b6b89dbf32139034e9741a1df6dde1
SHA256 (bsd.mp.IP27) = 6e850692e37e94c099ca7c53b02259de1112c0c2ad6ece2d9b4975845e174916
SHA256 (bsd.mp.IP30) = abd526983ebedf9073e2f198690b92119c98ee949365d98a00401e0f7823ad44
SHA256 (bsd.rd.IP22) = 129f5c144b22aac34eb218bb830c99613d9cc2b98203a8fe0d25ea927168e8b0
SHA256 (bsd.rd.IP26) = 6dc91218e978f93b1d25ff0fed66eb67ce472377d0482a83bba9ba04c5493abe
SHA256 (bsd.rd.IP27) = 75de4bfedec967f715ca0a20e266d316ab652d777d19d618a9ff06d90bb23f0f
SHA256 (bsd.rd.IP28) = fd5a4b53b9af8e689619ad6ecd48f31c77376fbfc9399d24b50b5f31d297fccd
SHA256 (bsd.rd.IP30) = 08a9d3ffe0204bd87b3f061424054f83d49817c61bd94d5d6d8eff9f8813c901
SHA256 (bsd.rd.IP32) = dbce0dc19ada83a69acc8aa44d44fe90c8cb0d02953c71636795586d928e24ac
SHA256 (cd70.iso) = 6d24fa51324eddcbf3b528c0e68d24a97ed9fe3505dd00358bfb74dc32f01d9f
SHA256 (comp70.tgz) = b5ade8322c1c4672723cfff9345a1e5f4ab3a44a949e7db2cb05aee5fc657341
SHA256 (game70.tgz) = 650341eb0875f4fa5f66434fc61b6bb0530aa4e114804ddc238f326d0a6f364e
SHA256 (man70.tgz) = 702b50236dc65731069390e8b74f7acf17d174a50fb6355122640e06412a4cfe
You can hence verify that what you downloaded comes from me by using signify on OpenBSD (or e.g. signify-openbsd on Debian GNU/Linux) using my signify public key below.
My signify public key is:
RWRmGQ1rewM9vHtQ6vMcAUnRrsJqKO/Z+n07CXxQkTPpAOnsVa26CIUj
Kernel images
For details about the supported machines see OpenBSD/sgi and intro(4):
| Hardware | Family | Kernel | Variant | Hash value | dmesg |
|---|---|---|---|---|---|
| IP24 | IP22 | IP22 | GENERIC | 32cbce9785133b04c9948f7baa3a08c774b8f8ec19116f85e3a5e7f1b510717d (SHA256) |
R4400 Indy log |
| R4600 Indy log | |||||
| IP26 | IP22 | IP26 | GENERIC | 8ebdbe3441e1df74857d26b5de02f89392ba7dedbb5ec65b6a39083b558831a0 (SHA256) |
untested as I don't have an R8000 Indigo² |
| IP28 | IP22 | IP28 | GENERIC | 0abc4eab176f3f69b75d2d28371f1cd5241ca9e0bf34c8bc29cb733748eb5149 (SHA256) |
R10000 Indigo² log |
| IP29 | IP27 | IP27 | GENERIC | b4ded21ade8cceca1351f684338fc56b210f7f1bddb58c1c617c77d8f80a9937 (SHA256) |
R12000 Origin200 log |
| GENERIC-MP | a045d5e036f6e0fffa0f706707f041e27657763ee7100a9817b513e49e42692c (SHA256) |
R12000 Origin200 log | |||
| dual node R10000 Origin200 log | |||||
| IP30 | IP30 | IP30 | GENERIC | 09d8b34765e832e3d33af9d0ab261a01bb15cf90c438182f01bcc9c88e8aa03d (SHA256) |
R12000 Octane log |
| GENERIC-MP | baf64d46a443957748117ccb8f316389adf03cf013e6a856aec2dbfa1d9990c2 (SHA256) |
R12000 Octane log | |||
| IP32 | IP32 | IP32 | GENERIC | cbc82adff8fee5165cef05ce707f9ea1120a47bd43f0b55632405a7a9752bdba (SHA256) |
R5000 O2 log |
Userland
For the userland you can use OpenBSD/octeon based file systems (create one with nfsrb2 for example). But this won't allow you to build OpenBSD/sgi kernels as gcc 4.2.1 is missing. To build the kernels use for example the OpenBSD/sgi 7.0 based file system available from this release.