https://wiki.raptorcs.com/w/api.php?action=feedcontributions&user=SiteAdmin&feedformat=atom
RCS Wiki - User contributions [en]
2024-03-29T04:52:05Z
User contributions
MediaWiki 1.33.1
https://wiki.raptorcs.com/w/index.php?title=Blackbird/Firmware&diff=4580
Blackbird/Firmware
2024-02-16T17:46:40Z
<p>SiteAdmin: </p>
<hr />
<div>= Blackbird Official Firmware Builds =<br />
<br />
For upgrade instructions, please visit the [[Firmware_Upgrade_Quickstart|Firmware Upgrade Quick Start]] page. Alternatively, for those wishing to build from source, please visit the [[Blackbird/Compiling_Firmware|Compiling Firmware]] page.<br />
<br />
All firmware builds are cryptographically signed with the current Raptor Computing Systems firmware signing key at time of release [https://raptorcs.com/keys/gpg/0xFBBEBF23.pub][https://raptorcs.com/verification/gpg/blackbird/firmware_builds/]. The intermediate firmware signer keys, in turn, are signed by our master umbrella key [https://raptorcs.com/keys/gpg/0x337BF51F.pub].<br />
<br />
== System Package v2.10 ==<br />
Released: 02-15-2024<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.10/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.10-bundle.tar|aef76a11038f2922d542bbdc7e5ccca1094b2f1d]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.02.rom|2b48243d7c404f3841f9ebe45aed9c3bee09ebe2]]<br />
<br />
== System Package v2.00a ==<br />
Released: 10-29-2021<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00a/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00a-bundle.tar|c13110c4cbb6bfa8b4912650a462824e1deb4ae5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.02.rom|2b48243d7c404f3841f9ebe45aed9c3bee09ebe2]]<br />
<br />
== System Package v2.00 ==<br />
Released: 02-19-2020<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00-bundle.tar|7cbe7a8d60a255a94c27138162a03e743df6c9c5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.01.rom|9ddbe70ea5e85466c1e24da927b135e62810c93f]]<br />
<br />
== System Package v1.00 ==<br />
Released: 05-22-2019<br />
* BMC: [[:File:Blackbird_openbmc_v1.00_bundle.tar.bz2|eb50c3fe9fc09aec6f874946362642bbd73a6955]]<br />
* PNOR: [[:File:Blackbird_host_pnor_v1.00.bin.bz2|3fe7beacf0ced330b2fdd5302c5f48f7458e98c3]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.00.rom|32784cea6d7b9fac9871e9d3909d4b7ac199a7f6]]<br />
<br />
Change Log<br />
* Initial release<br />
<br />
Known Issues<br />
* DRAM is capped to 2400MHz. This is not a hardware problem, it is an issue somewhere in hostboot that is being actively worked. 2666MHz DIMMs installed will function at 2400MHz pending a PNOR update to enable 2666MHz support.<br />
* The BMC kernel (incorrectly) detects an SPI master collision on bus 12, yielding a never ending stream of warnings from the i2c core. As this is not a trivial fix given the state of the ASpeed i2c drivers, and the spew is mostly harmless, the decision was made to ship anyway instead of incurring a lengthy delay to rewrite the drivers. If console access to the BMC is desired over serial, "dmesg -n 1" after login will silence the warnings on the console. This issue will be fixed in a future BMC firmware update.<br />
<br />
[[Category:Blackbird_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Talos_II/Firmware&diff=4579
Talos II/Firmware
2024-02-16T17:46:20Z
<p>SiteAdmin: </p>
<hr />
<div>= Talos II Official Firmware Builds =<br />
<br />
For upgrade instructions, please visit the [[Firmware_Upgrade_Quickstart|Firmware Upgrade Quick Start]] page. Alternatively, for those wishing to build from source, please visit the [[Talos_II/Compiling_Firmware|Compiling Firmware]] page.<br />
<br />
All firmware builds are cryptographically signed with the current Raptor Computing Systems firmware signing key at time of release [https://raptorcs.com/keys/gpg/0xFBBEBF23.pub][https://raptorcs.com/verification/gpg/talos_ii/firmware_builds/]. The intermediate firmware signer keys, in turn, are signed by our master umbrella key [https://raptorcs.com/keys/gpg/0x337BF51F.pub].<br />
<br />
== System Package v2.10 ==<br />
Released: 02-15-2024<BR><br />
[https://wiki.raptorcs.com/wiki/Talos_II/Firmware/2.10/Release_Notes Release Notes]<br />
* BMC: [[:File:Talos-ii-openbmc-v2.10-bundle.tar|67efd9872fc3aaa63350bd1722f6bc0346bf8460]]<br />
* PNOR: [[:File:Talos-ii-pnor-v2.10-bundle.tar|aef76a11038f2922d542bbdc7e5ccca1094b2f1d]]<br />
* FPGA: [[:File:Talos-ii-system-fpga-v1.08.rom|99368dab3befa7014155bcd250a4cf9bbb30b71a]]<br />
<br />
== System Package v2.00 ==<br />
Released: 02-19-2020<BR><br />
[https://wiki.raptorcs.com/wiki/Talos_II/Firmware/2.00/Release_Notes Release Notes]<br />
* BMC: [[:File:Talos-ii-openbmc-v2.00-bundle.tar|67efd9872fc3aaa63350bd1722f6bc0346bf8460]]<br />
* PNOR: [[:File:Talos-ii-pnor-v2.00-bundle.tar|f6295c9c7526feee8d6a7efe8d66b79c2883bb52]]<br />
* FPGA: [[:File:Talos-ii-system-fpga-v1.08.rom|99368dab3befa7014155bcd250a4cf9bbb30b71a]]<br />
<br />
== System Package v1.06 ==<br />
Released: 06-19-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.07_bundle.tar.bz2|2a92dec044239591244b6ed69c3fac162a6b9ea4]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.05.bin.bz2|76f78f4d0a31c2b40284125cd763d5b6aa524859]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.07.rom|819d0eb720549fc34a0c9f2a34946fdca04a6a32]]<br />
<br />
Change Log<br />
* Upgrade BMC kernel<br />
* Add Lite support to BMC<br />
* Upgrade PNOR stack to latest upstream versions<br />
* Update FPGA logic to support the Lite hardware configuration<br />
<br />
Known Issues<br />
* When fast reboot is enabled, under certain rare circumstances during IPL the OCC can malfunction and lock the FSI bus. This leads to loss of communication and fan controls, with all fans stuck on high, and can in some situations cause the second CPU to be guarded out. As a result, the fast reboot functionality is disabled by default in the current PNOR.<br />
<br />
== System Package v1.05 ==<br />
Released: 05-28-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.05_bundle.tar.bz2|aa359c9e341494c73d97fad3bd691bae18038482]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.04.bin.bz2|70748d07e8f89d3b54c95cd25e41cf6041ad50d4]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.06.rom|be9634aeac2b5b5e1db6c8b4e0b29cce0d298580]]<br />
<br />
Change Log<br />
* Upgrade BMC kernel to Linux 4.13<br />
* Add FSI bus driver error recovery<br />
* Upgrade PNOR stack to latest upstream versions<br />
* Modify FPGA logic to conform to ATX specifications<br />
<br />
Known Issues<br />
* While significantly lessened in this release, under certain rare circumstances during IPL the OCC can malfunction and lock the FSI bus. This leads to loss of communication and fan controls, with all fans stuck on high, and can in some situations cause the second CPU to be guarded out. This issue is exacerbated by the fast reboot functionality, which is disabled by default in the current PNOR. The underlying fault is being tracked upstream in [https://github.com/openbmc/openbmc/issues/1699 Issue 1699]. Should the second CPU guard out, issue "pflash -P GUARD -c" from the BMC shell to remove the spurious guard entries.<br />
<br />
== System Package v1.04 ==<br />
Released: 05-04-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.04_bundle.tar.bz2|b960fa7dc3f82b382ad81344d84f61186e5d204a]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.03.bin.bz2|d286337d16b9ae9f1e0721782e3913871f44d849]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.05.rom|b21d62815f806da7619273bbe50212bbc0187f2d]]<br />
<br />
Change Log<br />
* Fix regression accidentally introduced in System Package v1.03 where the fan controls do not engage on single CPU systems<br />
* Tweak chassis fan settings to minimize audible hunting<br />
<br />
Known Issues<br />
* Under certain rare circumstances during IPL, the OCC can malfunction and lock the FSI bus. This leads to loss of communication and fan controls, with all fans stuck on high, and can in some situations cause the second CPU to be guarded out. This issue is exacerbated by the fast reboot functionality, which is disabled by default in the current PNOR. The underlying fault is being tracked upstream in [https://github.com/openbmc/openbmc/issues/1699 Issue 1699]. Should the second CPU guard out, issue "pflash -P GUARD -c" from the BMC shell to remove the spurious guard entries.<br />
<br />
== System Package v1.03 ==<br />
Released: 04-30-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.03_bundle.tar.bz2|83fab00f082367c3423e38a1ab866d8058cd8f2b]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.03.bin.bz2|d286337d16b9ae9f1e0721782e3913871f44d849]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.05.rom|b21d62815f806da7619273bbe50212bbc0187f2d]]<br />
<br />
Change Log<br />
* Upgrade PNOR stack to latest upstream versions<br />
* Disable fast reboot by default (work around [https://github.com/openbmc/openbmc/issues/1699 Issue 1699] causing fans stuck on full speed)<br />
* Use PID control loop for fans instead of original (limited functionality) IBM fan control loop<br />
<br />
Known Issues<br />
* Under certain rare circumstances during IPL, the OCC can malfunction and lock the FSI bus. This leads to loss of communication and fan controls, with all fans stuck on high, and can in some situations cause the second CPU to be guarded out. This issue is exacerbated by the fast reboot functionality, which is disabled by default in the current PNOR. The underlying fault is being tracked upstream in [https://github.com/openbmc/openbmc/issues/1699 Issue 1699]. Should the second CPU guard out, issue "pflash -P GUARD -c" from the BMC shell to remove the spurious guard entries.<br />
<br />
== System Package v1.02 ==<br />
Released: 04-20-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.02_bundle.tar.bz2|e4c156f12cecd88e9c05f3b99d40d86ec94c3271]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.02.bin.bz2|91c79554de24932e4ff8cda75806daf1b3ee8b9e]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.04.rom|7a5d72ff8019160492dfb9d71a1f04a4bd1a14fc]]<br />
<br />
Change Log<br />
* Fix certain DIMMs with unusual SPD frequency values<br />
* Raise CPU core temperature setpoints<br />
* Load less aggressive fan curves for CPU temperature control<br />
<br />
Known Issues<br />
* When fast reboot is enabled, the fan controls may stop working after a reboot. A normal reboot (host shutdown, power off, power on, IPL) restores the fan control to normal operation. The FSI bus lockups remain a significant upstream bug in the standard OpenPOWER firmware, and Raptor Computing Systems is waiting for a fix from IBM for the FSI lockup that will also fix the fan controls once and for all.<br />
<br />
== System Package v1.01 ==<br />
Released: 04-15-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.01_bundle.tar.bz2|8528b0f0ee7277d5c1c033c09a9a662759b29d6e]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.01.bin.bz2|e7111679e21991492451a24f456846361e1f86bf]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.04.rom|7a5d72ff8019160492dfb9d71a1f04a4bd1a14fc]]<br />
<br />
Change Log<br />
* Fix spurious guard of second CPU package.<br />
* Fix fan control disengaging during IPL<br />
* Add on-board VGA disable jumper (J10109)<br />
* Revup host PNOR packages to latest upstream versions<br />
* Enable WoF on 18 and 22 core packages<br />
* Enable 2666MHz DDR4 memory DIMMs<br />
* Add on-board VGA disable jumper support<br />
<br />
== System Package v1.00 ==<br />
Released: 03-26-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.00_bundle.tar.bz2|2f6764af548633d305193faa6841dd4639b468e4]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.00.bin.bz2|e25a3f503cdef1d3c69be717aa4f5906bac287a8]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.03.rom|e90ca898402a250e9d2f6e303e25ddaceb0cf8d6]]<br />
<br />
Change Log<br />
* Initial release<br />
<br />
[[Category:Talos_II_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Blackbird/Firmware/2.10/Release_Notes&diff=4578
Blackbird/Firmware/2.10/Release Notes
2024-02-16T00:24:54Z
<p>SiteAdmin: Created page with "== System Package 2.10 Release Notes == === BMC === * No change === PNOR === * Update hostboot to latest upstream version * Update skiboot to latest upstream version * Upd..."</p>
<hr />
<div>== System Package 2.10 Release Notes ==<br />
<br />
=== BMC ===<br />
<br />
* No change<br />
<br />
=== PNOR ===<br />
<br />
* Update hostboot to latest upstream version<br />
* Update skiboot to latest upstream version<br />
* Update petitboot to latest upstream version<br />
* Update hcode to latest upstream version<br />
* Update skiroot to Linux 6.6.y stable branch<br />
* Enable Infiniband drivers in skiroot<br />
* Fix sporadic crash on paired-core machines (higher than 8 core) under specific workloads<br />
* Compress hostboot runtime to free up additional space in the BOOTKERNFW partition<br />
* Enable firmware component signature checks during IPL by default. Note that this uses the well-known (insecure) public transitional key in the official firmware builds, but makes the transition to a machine owner's key easier should the user wish to enable a secure boot chain using their own signing keys.<br />
<br />
=== FPGA ===<br />
<br />
* No change<br />
<br />
=== Known Issues ===<br />
* New BMC cannot IPL old PNOR and vice versa (CANTFIX)<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
* Certain DIMMs may not function in Slot 0. This is '''not''' a defect in the Blackbird planar, it is a memory VPD issue that is being worked by Raptor and the IBM memory team. Future firmware updates are expected to address this problem.<br />
* Upgrading from a BMC that has been manually edited to add or remove users can result in loss of SSH access after the upgrade has completed. The root cause is that <CODE>/etc/passwd</CODE> is retained verbatim across updates if modified, and as a result the new <CODE>sshd</CODE> user is not present in the upgraded firmware environment.<br />
** Prior to upgrading such a BMC, the following line should be added to <CODE>/etc/passwd</CODE> on the BMC:<BR><CODE>sshd:x:996:995::/var/run/sshd:/bin/false</CODE><br />
** Alternatively, the files <CODE>/etc/passwd</CODE> and <CODE>/etc/group</CODE> can be removed immediately before reboot to apply the update. Caution should be used with this method, as failure to apply the update could then result in a requirement to use a BMC serial cable or external SPI flasher to recover.</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Blackbird/Firmware&diff=4577
Blackbird/Firmware
2024-02-16T00:24:45Z
<p>SiteAdmin: </p>
<hr />
<div>= Blackbird Official Firmware Builds =<br />
<br />
For upgrade instructions, please visit the [[Firmware_Upgrade_Quickstart|Firmware Upgrade Quick Start]] page. Alternatively, for those wishing to build from source, please visit the [[Blackbird/Compiling_Firmware|Compiling Firmware]] page.<br />
<br />
All firmware builds are cryptographically signed with the current Raptor Computing Systems firmware signing key at time of release [https://raptorcs.com/verification/gpg/blackbird/firmware_builds/]. The intermediate firmware signer keys, in turn, are signed by our master umbrella key [https://raptorcs.com/keys/gpg/0x337BF51F.pub].<br />
<br />
== System Package v2.10 ==<br />
Released: 02-15-2024<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.10/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.10-bundle.tar|aef76a11038f2922d542bbdc7e5ccca1094b2f1d]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.02.rom|2b48243d7c404f3841f9ebe45aed9c3bee09ebe2]]<br />
<br />
== System Package v2.00a ==<br />
Released: 10-29-2021<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00a/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00a-bundle.tar|c13110c4cbb6bfa8b4912650a462824e1deb4ae5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.02.rom|2b48243d7c404f3841f9ebe45aed9c3bee09ebe2]]<br />
<br />
== System Package v2.00 ==<br />
Released: 02-19-2020<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00-bundle.tar|7cbe7a8d60a255a94c27138162a03e743df6c9c5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.01.rom|9ddbe70ea5e85466c1e24da927b135e62810c93f]]<br />
<br />
== System Package v1.00 ==<br />
Released: 05-22-2019<br />
* BMC: [[:File:Blackbird_openbmc_v1.00_bundle.tar.bz2|eb50c3fe9fc09aec6f874946362642bbd73a6955]]<br />
* PNOR: [[:File:Blackbird_host_pnor_v1.00.bin.bz2|3fe7beacf0ced330b2fdd5302c5f48f7458e98c3]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.00.rom|32784cea6d7b9fac9871e9d3909d4b7ac199a7f6]]<br />
<br />
Change Log<br />
* Initial release<br />
<br />
Known Issues<br />
* DRAM is capped to 2400MHz. This is not a hardware problem, it is an issue somewhere in hostboot that is being actively worked. 2666MHz DIMMs installed will function at 2400MHz pending a PNOR update to enable 2666MHz support.<br />
* The BMC kernel (incorrectly) detects an SPI master collision on bus 12, yielding a never ending stream of warnings from the i2c core. As this is not a trivial fix given the state of the ASpeed i2c drivers, and the spew is mostly harmless, the decision was made to ship anyway instead of incurring a lengthy delay to rewrite the drivers. If console access to the BMC is desired over serial, "dmesg -n 1" after login will silence the warnings on the console. This issue will be fixed in a future BMC firmware update.<br />
<br />
[[Category:Blackbird_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Blackbird/Firmware&diff=4576
Blackbird/Firmware
2024-02-16T00:24:27Z
<p>SiteAdmin: </p>
<hr />
<div>= Blackbird Official Firmware Builds =<br />
<br />
For upgrade instructions, please visit the [[Firmware_Upgrade_Quickstart|Firmware Upgrade Quick Start]] page. Alternatively, for those wishing to build from source, please visit the [[Blackbird/Compiling_Firmware|Compiling Firmware]] page.<br />
<br />
All firmware builds are cryptographically signed with the current Raptor Computing Systems firmware signing key at time of release [https://raptorcs.com/verification/gpg/blackbird/firmware_builds/]. The intermediate firmware signer keys, in turn, are signed by our master umbrella key [https://raptorcs.com/keys/gpg/0x337BF51F.pub].<br />
<br />
== System Package v2.10 ==<br />
Released: 02-15-2024<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00a/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.10-bundle.tar|aef76a11038f2922d542bbdc7e5ccca1094b2f1d]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.02.rom|2b48243d7c404f3841f9ebe45aed9c3bee09ebe2]]<br />
<br />
== System Package v2.00a ==<br />
Released: 10-29-2021<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00a/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00a-bundle.tar|c13110c4cbb6bfa8b4912650a462824e1deb4ae5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.02.rom|2b48243d7c404f3841f9ebe45aed9c3bee09ebe2]]<br />
<br />
== System Package v2.00 ==<br />
Released: 02-19-2020<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00-bundle.tar|7cbe7a8d60a255a94c27138162a03e743df6c9c5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.01.rom|9ddbe70ea5e85466c1e24da927b135e62810c93f]]<br />
<br />
== System Package v1.00 ==<br />
Released: 05-22-2019<br />
* BMC: [[:File:Blackbird_openbmc_v1.00_bundle.tar.bz2|eb50c3fe9fc09aec6f874946362642bbd73a6955]]<br />
* PNOR: [[:File:Blackbird_host_pnor_v1.00.bin.bz2|3fe7beacf0ced330b2fdd5302c5f48f7458e98c3]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.00.rom|32784cea6d7b9fac9871e9d3909d4b7ac199a7f6]]<br />
<br />
Change Log<br />
* Initial release<br />
<br />
Known Issues<br />
* DRAM is capped to 2400MHz. This is not a hardware problem, it is an issue somewhere in hostboot that is being actively worked. 2666MHz DIMMs installed will function at 2400MHz pending a PNOR update to enable 2666MHz support.<br />
* The BMC kernel (incorrectly) detects an SPI master collision on bus 12, yielding a never ending stream of warnings from the i2c core. As this is not a trivial fix given the state of the ASpeed i2c drivers, and the spew is mostly harmless, the decision was made to ship anyway instead of incurring a lengthy delay to rewrite the drivers. If console access to the BMC is desired over serial, "dmesg -n 1" after login will silence the warnings on the console. This issue will be fixed in a future BMC firmware update.<br />
<br />
[[Category:Blackbird_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Blackbird/Firmware&diff=4575
Blackbird/Firmware
2024-02-16T00:24:15Z
<p>SiteAdmin: </p>
<hr />
<div>= Blackbird Official Firmware Builds =<br />
<br />
For upgrade instructions, please visit the [[Firmware_Upgrade_Quickstart|Firmware Upgrade Quick Start]] page. Alternatively, for those wishing to build from source, please visit the [[Blackbird/Compiling_Firmware|Compiling Firmware]] page.<br />
<br />
All firmware builds are cryptographically signed with the current Raptor Computing Systems firmware signing key at time of release [https://raptorcs.com/verification/gpg/blackbird/firmware_builds/]. The intermediate firmware signer keys, in turn, are signed by our master umbrella key [https://raptorcs.com/keys/gpg/0x337BF51F.pub].<br />
<br />
== System Package v2.10 ==<br />
Released: 02-15-2024<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00a/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.10a-bundle.tar|aef76a11038f2922d542bbdc7e5ccca1094b2f1d]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.02.rom|2b48243d7c404f3841f9ebe45aed9c3bee09ebe2]]<br />
<br />
== System Package v2.00a ==<br />
Released: 10-29-2021<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00a/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00a-bundle.tar|c13110c4cbb6bfa8b4912650a462824e1deb4ae5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.02.rom|2b48243d7c404f3841f9ebe45aed9c3bee09ebe2]]<br />
<br />
== System Package v2.00 ==<br />
Released: 02-19-2020<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00-bundle.tar|7cbe7a8d60a255a94c27138162a03e743df6c9c5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.01.rom|9ddbe70ea5e85466c1e24da927b135e62810c93f]]<br />
<br />
== System Package v1.00 ==<br />
Released: 05-22-2019<br />
* BMC: [[:File:Blackbird_openbmc_v1.00_bundle.tar.bz2|eb50c3fe9fc09aec6f874946362642bbd73a6955]]<br />
* PNOR: [[:File:Blackbird_host_pnor_v1.00.bin.bz2|3fe7beacf0ced330b2fdd5302c5f48f7458e98c3]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.00.rom|32784cea6d7b9fac9871e9d3909d4b7ac199a7f6]]<br />
<br />
Change Log<br />
* Initial release<br />
<br />
Known Issues<br />
* DRAM is capped to 2400MHz. This is not a hardware problem, it is an issue somewhere in hostboot that is being actively worked. 2666MHz DIMMs installed will function at 2400MHz pending a PNOR update to enable 2666MHz support.<br />
* The BMC kernel (incorrectly) detects an SPI master collision on bus 12, yielding a never ending stream of warnings from the i2c core. As this is not a trivial fix given the state of the ASpeed i2c drivers, and the spew is mostly harmless, the decision was made to ship anyway instead of incurring a lengthy delay to rewrite the drivers. If console access to the BMC is desired over serial, "dmesg -n 1" after login will silence the warnings on the console. This issue will be fixed in a future BMC firmware update.<br />
<br />
[[Category:Blackbird_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Talos_II/Firmware/2.10/Release_Notes&diff=4574
Talos II/Firmware/2.10/Release Notes
2024-02-16T00:23:03Z
<p>SiteAdmin: Created page with "== System Package 2.10 Release Notes == === BMC === * No change === PNOR === * Update hostboot to latest upstream version * Update skiboot to latest upstream version * Upd..."</p>
<hr />
<div>== System Package 2.10 Release Notes ==<br />
<br />
=== BMC ===<br />
<br />
* No change<br />
<br />
=== PNOR ===<br />
<br />
* Update hostboot to latest upstream version<br />
* Update skiboot to latest upstream version<br />
* Update petitboot to latest upstream version<br />
* Update hcode to latest upstream version<br />
* Update skiroot to Linux 6.6.y stable branch<br />
* Enable Infiniband drivers in skiroot<br />
* Fix sporadic crash on paired-core machines (higher than 8 core) under specific workloads<br />
* Compress hostboot runtime to free up additional space in the BOOTKERNFW partition<br />
* Enable firmware component signature checks during IPL by default. Note that this uses the well-known (insecure) public transitional key in the official firmware builds, but makes the transition to a machine owner's key easier should the user wish to enable a secure boot chain using their own signing keys.<br />
<br />
=== FPGA ===<br />
<br />
* No change<br />
<br />
=== Known Issues ===<br />
* New BMC cannot IPL old PNOR and vice versa (CANTFIX)<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
* Certain DIMMs may not function in Slot 0. This is '''not''' a defect in the Blackbird planar, it is a memory VPD issue that is being worked by Raptor and the IBM memory team. Future firmware updates are expected to address this problem.<br />
* Upgrading from a BMC that has been manually edited to add or remove users can result in loss of SSH access after the upgrade has completed. The root cause is that <CODE>/etc/passwd</CODE> is retained verbatim across updates if modified, and as a result the new <CODE>sshd</CODE> user is not present in the upgraded firmware environment.<br />
** Prior to upgrading such a BMC, the following line should be added to <CODE>/etc/passwd</CODE> on the BMC:<BR><CODE>sshd:x:996:995::/var/run/sshd:/bin/false</CODE><br />
** Alternatively, the files <CODE>/etc/passwd</CODE> and <CODE>/etc/group</CODE> can be removed immediately before reboot to apply the update. Caution should be used with this method, as failure to apply the update could then result in a requirement to use a BMC serial cable or external SPI flasher to recover.</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Talos_II/Firmware&diff=4573
Talos II/Firmware
2024-02-16T00:18:24Z
<p>SiteAdmin: </p>
<hr />
<div>= Talos II Official Firmware Builds =<br />
<br />
For upgrade instructions, please visit the [[Firmware_Upgrade_Quickstart|Firmware Upgrade Quick Start]] page. Alternatively, for those wishing to build from source, please visit the [[Talos_II/Compiling_Firmware|Compiling Firmware]] page.<br />
<br />
All firmware builds are cryptographically signed with the current Raptor Computing Systems firmware signing key at time of release [https://raptorcs.com/verification/gpg/talos_ii/firmware_builds/]. The intermediate firmware signer keys, in turn, are signed by our master umbrella key [https://raptorcs.com/keys/gpg/0x337BF51F.pub].<br />
<br />
== System Package v2.10 ==<br />
Released: 02-15-2024<BR><br />
[https://wiki.raptorcs.com/wiki/Talos_II/Firmware/2.10/Release_Notes Release Notes]<br />
* BMC: [[:File:Talos-ii-openbmc-v2.10-bundle.tar|67efd9872fc3aaa63350bd1722f6bc0346bf8460]]<br />
* PNOR: [[:File:Talos-ii-pnor-v2.10-bundle.tar|aef76a11038f2922d542bbdc7e5ccca1094b2f1d]]<br />
* FPGA: [[:File:Talos-ii-system-fpga-v1.08.rom|99368dab3befa7014155bcd250a4cf9bbb30b71a]]<br />
<br />
== System Package v2.00 ==<br />
Released: 02-19-2020<BR><br />
[https://wiki.raptorcs.com/wiki/Talos_II/Firmware/2.00/Release_Notes Release Notes]<br />
* BMC: [[:File:Talos-ii-openbmc-v2.00-bundle.tar|67efd9872fc3aaa63350bd1722f6bc0346bf8460]]<br />
* PNOR: [[:File:Talos-ii-pnor-v2.00-bundle.tar|f6295c9c7526feee8d6a7efe8d66b79c2883bb52]]<br />
* FPGA: [[:File:Talos-ii-system-fpga-v1.08.rom|99368dab3befa7014155bcd250a4cf9bbb30b71a]]<br />
<br />
== System Package v1.06 ==<br />
Released: 06-19-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.07_bundle.tar.bz2|2a92dec044239591244b6ed69c3fac162a6b9ea4]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.05.bin.bz2|76f78f4d0a31c2b40284125cd763d5b6aa524859]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.07.rom|819d0eb720549fc34a0c9f2a34946fdca04a6a32]]<br />
<br />
Change Log<br />
* Upgrade BMC kernel<br />
* Add Lite support to BMC<br />
* Upgrade PNOR stack to latest upstream versions<br />
* Update FPGA logic to support the Lite hardware configuration<br />
<br />
Known Issues<br />
* When fast reboot is enabled, under certain rare circumstances during IPL the OCC can malfunction and lock the FSI bus. This leads to loss of communication and fan controls, with all fans stuck on high, and can in some situations cause the second CPU to be guarded out. As a result, the fast reboot functionality is disabled by default in the current PNOR.<br />
<br />
== System Package v1.05 ==<br />
Released: 05-28-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.05_bundle.tar.bz2|aa359c9e341494c73d97fad3bd691bae18038482]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.04.bin.bz2|70748d07e8f89d3b54c95cd25e41cf6041ad50d4]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.06.rom|be9634aeac2b5b5e1db6c8b4e0b29cce0d298580]]<br />
<br />
Change Log<br />
* Upgrade BMC kernel to Linux 4.13<br />
* Add FSI bus driver error recovery<br />
* Upgrade PNOR stack to latest upstream versions<br />
* Modify FPGA logic to conform to ATX specifications<br />
<br />
Known Issues<br />
* While significantly lessened in this release, under certain rare circumstances during IPL the OCC can malfunction and lock the FSI bus. This leads to loss of communication and fan controls, with all fans stuck on high, and can in some situations cause the second CPU to be guarded out. This issue is exacerbated by the fast reboot functionality, which is disabled by default in the current PNOR. The underlying fault is being tracked upstream in [https://github.com/openbmc/openbmc/issues/1699 Issue 1699]. Should the second CPU guard out, issue "pflash -P GUARD -c" from the BMC shell to remove the spurious guard entries.<br />
<br />
== System Package v1.04 ==<br />
Released: 05-04-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.04_bundle.tar.bz2|b960fa7dc3f82b382ad81344d84f61186e5d204a]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.03.bin.bz2|d286337d16b9ae9f1e0721782e3913871f44d849]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.05.rom|b21d62815f806da7619273bbe50212bbc0187f2d]]<br />
<br />
Change Log<br />
* Fix regression accidentally introduced in System Package v1.03 where the fan controls do not engage on single CPU systems<br />
* Tweak chassis fan settings to minimize audible hunting<br />
<br />
Known Issues<br />
* Under certain rare circumstances during IPL, the OCC can malfunction and lock the FSI bus. This leads to loss of communication and fan controls, with all fans stuck on high, and can in some situations cause the second CPU to be guarded out. This issue is exacerbated by the fast reboot functionality, which is disabled by default in the current PNOR. The underlying fault is being tracked upstream in [https://github.com/openbmc/openbmc/issues/1699 Issue 1699]. Should the second CPU guard out, issue "pflash -P GUARD -c" from the BMC shell to remove the spurious guard entries.<br />
<br />
== System Package v1.03 ==<br />
Released: 04-30-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.03_bundle.tar.bz2|83fab00f082367c3423e38a1ab866d8058cd8f2b]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.03.bin.bz2|d286337d16b9ae9f1e0721782e3913871f44d849]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.05.rom|b21d62815f806da7619273bbe50212bbc0187f2d]]<br />
<br />
Change Log<br />
* Upgrade PNOR stack to latest upstream versions<br />
* Disable fast reboot by default (work around [https://github.com/openbmc/openbmc/issues/1699 Issue 1699] causing fans stuck on full speed)<br />
* Use PID control loop for fans instead of original (limited functionality) IBM fan control loop<br />
<br />
Known Issues<br />
* Under certain rare circumstances during IPL, the OCC can malfunction and lock the FSI bus. This leads to loss of communication and fan controls, with all fans stuck on high, and can in some situations cause the second CPU to be guarded out. This issue is exacerbated by the fast reboot functionality, which is disabled by default in the current PNOR. The underlying fault is being tracked upstream in [https://github.com/openbmc/openbmc/issues/1699 Issue 1699]. Should the second CPU guard out, issue "pflash -P GUARD -c" from the BMC shell to remove the spurious guard entries.<br />
<br />
== System Package v1.02 ==<br />
Released: 04-20-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.02_bundle.tar.bz2|e4c156f12cecd88e9c05f3b99d40d86ec94c3271]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.02.bin.bz2|91c79554de24932e4ff8cda75806daf1b3ee8b9e]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.04.rom|7a5d72ff8019160492dfb9d71a1f04a4bd1a14fc]]<br />
<br />
Change Log<br />
* Fix certain DIMMs with unusual SPD frequency values<br />
* Raise CPU core temperature setpoints<br />
* Load less aggressive fan curves for CPU temperature control<br />
<br />
Known Issues<br />
* When fast reboot is enabled, the fan controls may stop working after a reboot. A normal reboot (host shutdown, power off, power on, IPL) restores the fan control to normal operation. The FSI bus lockups remain a significant upstream bug in the standard OpenPOWER firmware, and Raptor Computing Systems is waiting for a fix from IBM for the FSI lockup that will also fix the fan controls once and for all.<br />
<br />
== System Package v1.01 ==<br />
Released: 04-15-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.01_bundle.tar.bz2|8528b0f0ee7277d5c1c033c09a9a662759b29d6e]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.01.bin.bz2|e7111679e21991492451a24f456846361e1f86bf]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.04.rom|7a5d72ff8019160492dfb9d71a1f04a4bd1a14fc]]<br />
<br />
Change Log<br />
* Fix spurious guard of second CPU package.<br />
* Fix fan control disengaging during IPL<br />
* Add on-board VGA disable jumper (J10109)<br />
* Revup host PNOR packages to latest upstream versions<br />
* Enable WoF on 18 and 22 core packages<br />
* Enable 2666MHz DDR4 memory DIMMs<br />
* Add on-board VGA disable jumper support<br />
<br />
== System Package v1.00 ==<br />
Released: 03-26-2018<br />
* BMC: [[:File:Talos_ii_openbmc_v1.00_bundle.tar.bz2|2f6764af548633d305193faa6841dd4639b468e4]]<br />
* PNOR: [[:File:Talos_ii_host_pnor_v1.00.bin.bz2|e25a3f503cdef1d3c69be717aa4f5906bac287a8]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.03.rom|e90ca898402a250e9d2f6e303e25ddaceb0cf8d6]]<br />
<br />
Change Log<br />
* Initial release<br />
<br />
[[Category:Talos_II_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Talos-ii-pnor-v2.10-bundle.tar&diff=4572
File:Talos-ii-pnor-v2.10-bundle.tar
2024-02-16T00:17:14Z
<p>SiteAdmin: == Summary ==
Built from https://gitlab.raptorengineering.com/openpower-firmware/machine-talos-ii/op-build/-/tree/raptor-v2.10<br>
Corresponding GIT hash, as shown on test reports: '''aef76a11038f2922d542bbdc7e5ccca1094b2f1d'''
Category:Talos_II_Firmware</p>
<hr />
<div>== Summary ==<br />
Built from https://gitlab.raptorengineering.com/openpower-firmware/machine-talos-ii/op-build/-/tree/raptor-v2.10<br><br />
Corresponding GIT hash, as shown on test reports: '''aef76a11038f2922d542bbdc7e5ccca1094b2f1d'''<br />
<br />
[[Category:Talos_II_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Blackbird-pnor-v2.10-bundle.tar&diff=4571
File:Blackbird-pnor-v2.10-bundle.tar
2024-02-16T00:16:42Z
<p>SiteAdmin: == Summary ==
Built from https://gitlab.raptorengineering.com/openpower-firmware/machine-blackbird/op-build/-/tree/raptor-v2.10<br>
Corresponding GIT hash, as shown on test reports: '''aef76a11038f2922d542bbdc7e5ccca1094b2f1d'''
Category:Blackbird_Firmware</p>
<hr />
<div>== Summary ==<br />
Built from https://gitlab.raptorengineering.com/openpower-firmware/machine-blackbird/op-build/-/tree/raptor-v2.10<br><br />
Corresponding GIT hash, as shown on test reports: '''aef76a11038f2922d542bbdc7e5ccca1094b2f1d'''<br />
<br />
[[Category:Blackbird_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Talos-ii-openbmc-v2.10-bundle.tar&diff=4570
File:Talos-ii-openbmc-v2.10-bundle.tar
2024-02-16T00:15:24Z
<p>SiteAdmin: == Summary ==
Built from https://git.raptorcs.com/git/talos-openbmc/tag/?h=raptor-v2.00<br>
Corresponding GIT hash, as shown on test reports: '''67efd9872fc3aaa63350bd1722f6bc0346bf8460'''
'''A one time process is required to upgrade from firmware versions below 2.00.'''
Please read the following instructions carefully before proceeding.
===== Upgrade Instructions =====
* Ensure that the BMC and PNOR was previously updated to System Package v1.06, and that that your system successfully boo...</p>
<hr />
<div>== Summary ==<br />
Built from https://git.raptorcs.com/git/talos-openbmc/tag/?h=raptor-v2.00<br><br />
Corresponding GIT hash, as shown on test reports: '''67efd9872fc3aaa63350bd1722f6bc0346bf8460'''<br />
<br />
'''A one time process is required to upgrade from firmware versions below 2.00.''' <br />
Please read the following instructions carefully before proceeding.<br />
<br />
===== Upgrade Instructions =====<br />
* Ensure that the BMC and PNOR was previously updated to System Package v1.06, and that that your system successfully boots after that update<br />
* Extract the <CODE>shell_upgrade/talos-ii-v2.00-image-bmc.bz2</CODE> file from <CODE>shell_upgrade/talos-ii-v2.00-image-bmc.bz2</CODE><br />
* Decompress <CODE>talos-ii-v2.00-image-bmc.bz2</CODE> and rename to <CODE>image-bmc</CODE><br />
* Power down your system<br />
* Issue <CODE>reboot</CODE> on the BMC<br />
* Transfer the decompressed BMC image file to <CODE>/run/initramfs/image-bmc</CODE> on the BMC<br />
* Run <CODE>fw_printenv | grep eth1addr</CODE> and write down the MAC address. '''You will need this information later'''<br />
* Issue <CODE>reboot</CODE> on the BMC<br />
* After BMC restart (this may take 5-10 minutes):<br />
** <CODE>fw_setenv ethaddr <IPMI MAC address written down earlier></CODE><br />
** <CODE>fw_setenv eth1addr <IPMI MAC address written down earlier></CODE><br />
<br />
Note that image-bmc is provided for external recovery and reflashing purposes. Attempting to flash image-bmc to installed system package versions lower than v2.00 will destroy your U-Boot environment variables, requiring that you reconfigure the MAC address of the BMC from the IPMI MAC sticker on the mainboard. Version 2.00 and higher do not have this limitation and it is safe to use the image-bmc upgrade process.<br />
<br />
[[Category:Talos_II_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Blackbird-openbmc-v2.10-bundle.tar&diff=4569
File:Blackbird-openbmc-v2.10-bundle.tar
2024-02-16T00:14:57Z
<p>SiteAdmin: == Summary ==
Built from https://git.raptorcs.com/git/blackbird-openbmc/tag/?h=raptor-v2.00<br>
Corresponding GIT hash, as shown on test reports: '''18878e4f6250fdad538c7af3dabf90fd526e9264'''
'''A one time process is required to upgrade from firmware versions below 2.00.'''
Please read the following instructions carefully before proceeding.
===== Upgrade Instructions =====
* Extract the <CODE>shell_upgrade/blackbird-v2.00-image-bmc.bz2</CODE> file from <CODE>shell_upgrade/blackbird-v2.00-...</p>
<hr />
<div>== Summary ==<br />
Built from https://git.raptorcs.com/git/blackbird-openbmc/tag/?h=raptor-v2.00<br><br />
Corresponding GIT hash, as shown on test reports: '''18878e4f6250fdad538c7af3dabf90fd526e9264'''<br />
<br />
'''A one time process is required to upgrade from firmware versions below 2.00.''' <br />
Please read the following instructions carefully before proceeding.<br />
<br />
===== Upgrade Instructions =====<br />
* Extract the <CODE>shell_upgrade/blackbird-v2.00-image-bmc.bz2</CODE> file from <CODE>shell_upgrade/blackbird-v2.00-image-bmc.bz2</CODE><br />
* Decompress <CODE>blackbird-v2.00-image-bmc.bz2</CODE> and rename to <CODE>image-bmc</CODE><br />
* Power down your system<br />
* Issue <CODE>reboot</CODE> on the BMC<br />
* Transfer the decompressed BMC image file to <CODE>/run/initramfs/image-bmc</CODE> on the BMC<br />
* Run <CODE>fw_printenv | grep eth1addr</CODE> and write down the MAC address. '''You will need this information later'''<br />
* Issue <CODE>reboot</CODE> on the BMC<br />
* After BMC restart (this may take 5-10 minutes):<br />
** <CODE>fw_setenv ethaddr <IPMI MAC address written down earlier></CODE><br />
** <CODE>fw_setenv eth1addr <IPMI MAC address written down earlier></CODE><br />
<br />
Note that image-bmc is provided for external recovery and reflashing purposes. Attempting to flash image-bmc to installed system package versions lower than v2.00 will destroy your U-Boot environment variables, requiring that you reconfigure the MAC address of the BMC from the IPMI MAC sticker on the mainboard. Version 2.00 and higher do not have this limitation and it is safe to use the image-bmc upgrade process.<br />
<br />
[[Category:Blackbird_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Category:Documentation&diff=4427
Category:Documentation
2023-08-29T16:58:47Z
<p>SiteAdmin: </p>
<hr />
<div>The following documentation is available:<br />
<br />
* [[Talos II]] specific documentation:<br />
** [[:File:T2P9D01_users_guide_version_1_0.pdf|Talos II User's Guide]]<br />
** [[:File:Talos ii.dts|Example Talos II device tree]]<br />
* [[Blackbird]] specific documentation:<br />
** [[:File:C1P9S01_users_guide_version_1_0.pdf|Blackbird User's Guide]]<br />
* [[POWER9]] specific documentation:<br />
** RCS platform level documentation<br />
*** [[:File:P9PS_datasheet.pdf|P9PS platform control soft SoC documentation]]<br />
** User-level documentation<br />
*** [[:File:POWER9-Features-and-Specifications.pdf|Introduction to POWER9 Features and Specifications]]<br />
*** [[:File:POWER9 um OpenPOWER v21 10OCT2019 pub.pdf|POWER9 User Manual v21]] (old versions: [[:File:POWER9_um_OpenPOWER_v20GA_09APR2018_pub.pdf|v20GA]])<br />
*** [[:File:POWER9_PMU_UG_v12_28NOV2018_pub.pdf|POWER9 Performance Monitoring Unit User Guide v12]]<br />
** Operating System-level documentation<br />
*** [[:File:IPL-Flow-POWER9.pdf|POWER9 IPL/Bootstrap Process Documentation]]<br />
** Low-level documentation<br />
*** [[:File:POWER9_Sforza_DS_v19_16APR2020_pub.pdf|POWER9 Sforza Datasheet v19]] (old versions: [[:File:POWER9_Sforza_DS_v18_13JUN2019_pub.pdf|v18]], [[:File:POWER9_Sforza_DS_v16_23JUL2018_pub.pdf|v16]])<br />
*** [[:File:POWER9_LaGrange_ds_v17_28MAR2019_pub.pdf|POWER9 LaGrange Datasheet v17]]<br />
*** [[:File:POWER9 errata dd2.2 v1.2 19APR2019 pub.pdf|POWER9 DD2.2 Errata]]<br />
*** [[:File:POWER9 Processor Programming Model Bulletin 090919.pdf|POWER9 DD2.1 Use Restrictions]]<br />
*** [[:File:POWER9_Registers_vol1_version1.2_pub.pdf|POWER9 Registers Vol. 1 v1.2]]<br />
*** [[:File:POWER9_Registers_vol2_version1.2_pub.pdf|POWER9 Registers Vol. 2 v1.2]]<br />
*** [[:File:POWER9_Registers_vol3_version1.2_pub.pdf|POWER9 Registers Vol. 3 v1.3]]<br />
*** [[:File:405 um.pdf|PPC405 User Manual]] (used for the [[OCC]])<br />
*** [[:File:PPE 42X Core Users Manual.pdf|PPE 42 Embedded Processor Core User's Manual v4.0]] (used for the [[SBE]])<br />
*** PCIe controller documentation:<br />
**** [[:File:POWER9_PCIe_controller_v11_27JUL2018_pub.pdf|PCIe controller v11 Documentation]]<br />
**** [[:File:P9_PHB_version1.0_27July2018_pub.pdf|PHB v1.0.27 Documentation]]<br />
* General POWER documentation:<br />
** ISA Documentation:<br />
*** [[:File:PowerISA_public.v3.0B.pdf|ISA Specification v3.0B]] (implemented by [[POWER9]])<br />
*** [[:File:PowerISA_V2.07B.pdf|ISA Specification v2.07B]] (implemented by [[POWER8]])<br />
*** [[:File:POWER9 Processor Programming Model Bulletin 090919.pdf|Ultravisor ISA Extensions for POWER9]]<br />
*** [[Power ISA|Other versions]]<br />
** ABI Documentation:<br />
*** [[:File:Leabi-20170510.pdf|&#8220;ELFv2&#8221; 64-bit ABI]]<br />
*** [[:File:Power-Arch-32-bit-ABI-supp-1.0-Unified.pdf|32-bit ABI v1.0]]<br />
** Platform Documentation:<br />
*** [[:File:LoPAPR_DRAFT_v11_24March2016_cmt1.pdf|LoPAPR v1.1]] (VM-level platform documentation)<br />
*** [[:File:Power_ePAPR_APPROVED_v1.1.pdf|ePAPR v1.1 Specification]] (embedded platform specification)<br />
*** [[:File:IODA2WGSpec-1.0.0-20160217.pdf|I/O Design Architecture v2 v1.0.0]] (IOMMU specification)<br />
*** [[:File:OpenFSI-spec-20161212.pdf|OpenFSI Specification]] ([[FSI]] bus protocol)<br />
<br />
* See also:<br />
** [https://openpowerfoundation.org/technical/resource-catalog/ OpenPOWER Resource Catalog]<br />
** [https://www-355.ibm.com/systems/power/openpower/ IBM Portal for OpenPOWER]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:P9PS_datasheet.pdf&diff=4426
File:P9PS datasheet.pdf
2023-08-29T16:55:48Z
<p>SiteAdmin: Datasheet for embedded platform control functions as implemented on iCE40 FPGA on RCS POWER9 platforms</p>
<hr />
<div>== Summary ==<br />
Datasheet for embedded platform control functions as implemented on iCE40 FPGA on RCS POWER9 platforms</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Arctic_Tern_BMC_Integration_Guide_Version_0.90.pdf&diff=3844
File:Arctic Tern BMC Integration Guide Version 0.90.pdf
2022-08-20T18:15:27Z
<p>SiteAdmin: SiteAdmin uploaded a new version of File:Arctic Tern BMC Integration Guide Version 0.90.pdf</p>
<hr />
<div></div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Arctic_Tern_BMC_Integration_Guide_Version_0.90.pdf&diff=3843
File:Arctic Tern BMC Integration Guide Version 0.90.pdf
2022-08-20T17:40:49Z
<p>SiteAdmin: SiteAdmin uploaded a new version of File:Arctic Tern BMC Integration Guide Version 0.90.pdf</p>
<hr />
<div></div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Arctic_Tern_BMC_Integration_Guide_Version_0.90.pdf&diff=3841
File:Arctic Tern BMC Integration Guide Version 0.90.pdf
2022-08-17T08:25:21Z
<p>SiteAdmin: </p>
<hr />
<div></div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Arctic_Tern_Module_Schematic_v1.01.pdf&diff=3822
File:Arctic Tern Module Schematic v1.01.pdf
2022-07-28T20:52:33Z
<p>SiteAdmin: </p>
<hr />
<div></div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Arctic_Tern_PCIe_Carrier_Schematic_v1.00.pdf&diff=3821
File:Arctic Tern PCIe Carrier Schematic v1.00.pdf
2022-07-28T17:53:37Z
<p>SiteAdmin: </p>
<hr />
<div></div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Arctic_Tern_Users_Guide_Version_1.00.pdf&diff=3818
File:Arctic Tern Users Guide Version 1.00.pdf
2022-07-27T23:55:17Z
<p>SiteAdmin: SiteAdmin uploaded a new version of File:Arctic Tern Users Guide Version 1.00.pdf</p>
<hr />
<div></div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Arctic_Tern_Users_Guide_Version_1.00.pdf&diff=3817
File:Arctic Tern Users Guide Version 1.00.pdf
2022-07-27T22:11:46Z
<p>SiteAdmin: </p>
<hr />
<div></div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Talos_II/Firmware/2.00/Release_Notes&diff=3713
Talos II/Firmware/2.00/Release Notes
2022-05-03T17:18:23Z
<p>SiteAdmin: </p>
<hr />
<div>== System Package 2.00 Release Notes ==<br />
<br />
=== BMC ===<br />
<br />
* Our standard ATX products (this includes Talos II and Blackbird) now ship with an easy to use Web GUI installed on the BMC.<br />
** Full support for serial console interaction, iKVM, and remote media is added with this firmware version<br />
** A recent Web browser, such as Ungoogled Chromium for POWER (https://github.com/leo-lb/ungoogled-chromium) is required due to the use of modern Web features. No closed source or proprietary plugins are required to use any of the BMC Web GUI features.<br />
** Earlier methods of interacting with the BMC, including firmware updates over SSH, will continue to be supported across all product lines as they are efficient at scale in larger deployments. The Web GUI is just another way of interacting with the BMC, targeted at individual users and SME.<br />
** The login credentials for SSH and the Web GUI are shared -- changing one will change the other. This makes it easy to change your BMC root password from a Web browser on a second computer if required.<br />
** The Web server will '''not''' respond to <CODE>http://</CODE> requests. You must access it via <CODE>https://</CODE> only.<br />
<br />
* After upgrading from any system firmware package version before 2.00, spurious entries left over from previous firmware versions may show up in the system inventory. You can clear these from the BMC command line, with chassis power '''off''' as follows:<BR><CODE>rm -rf /var/lib/phosphor-inventory-manager/xyz/openbmc_project/inventory/system/chassis</CODE><BR><CODE>reboot</CODE><BR>When the BMC starts back up and the system is powered back on, the inventory will re-populate with correct data.<br />
<br />
=== PNOR ===<br />
<br />
* Supports DD2.3 ("v2") CPUs<br />
* Supports Ultravisor<br />
* Memory VPD updated to improve compatibility with third party RAM DIMMs<br />
* AMD Navi GPU support (with proprietary AMD GPU firmware added to BOOTKERNFW partition)<br />
<br />
=== Known Issues ===<br />
* New BMC cannot IPL old PNOR and vice versa (CANTFIX)<br />
* PCB hardware revision 1.00 and older do not support FPGA version v1.08 and above. There is no loss of functionality by remaining on the v1.07 FPGA version for these older boards, the newer FPGA revisions enable features on the newer boards that are not present on the older boards at a hardware level.<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
* Upgrading from a BMC that has been manually edited to add or remove users can result in loss of SSH access after the upgrade has completed. The root cause is that <CODE>/etc/passwd</CODE> is retained verbatim across updates if modified, and as a result the new <CODE>sshd</CODE> user is not present in the upgraded firmware environment.<br />
** Prior to upgrading such a BMC, the following line should be added to <CODE>/etc/passwd</CODE> on the BMC:<BR><CODE>sshd:x:996:995::/var/run/sshd:/bin/false</CODE><br />
** Alternatively, the files <CODE>/etc/passwd</CODE> and <CODE>/etc/group</CODE> can be removed immediately before reboot to apply the update. Caution should be used with this method, as failure to apply the update could then result in a requirement to use a BMC serial cable or external SPI flasher to recover.<br />
* Systems with LSI SAS controllers (mpt3sas kernel module) crash in petitboot and are unable to boot the target OS<br />
** WORKAROUND: Use [[:File:Talos-ii-2.01-beta-pnor.tar|our current 2.01 Beta PNOR]] instead of the 2.00 release PNOR</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Operating_System_Specific_Workarounds/Debian&diff=3612
Operating System Specific Workarounds/Debian
2022-01-26T05:40:46Z
<p>SiteAdmin: </p>
<hr />
<div>= Debian-Specific Issues and Workarounds =<br />
<br />
__TOC__<br />
<br />
== Bullseye ==<br />
<br />
=== Blank VGA ===<br />
'''Cause'''<br />
<br />
The required open-source (libre) video driver module ("ast") is not included in the installer package<br />
<br />
'''Upstream Bug Report'''<br />
<br />
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990016<br />
<br />
'''Status'''<br />
<br />
Root cause found, solution provided, '''upstream not responding'''<br />
<br />
'''Workaround'''<br />
<br />
Debian can be installed via the serial console, then switched to VGA mode after installation (i.e. after the ASpeed driver module is available to the kernel). The following instructions assume you have SSH shell access to the BMC:<br />
<br />
* Install<br />
<br />
# With system power off, SSH to the BMC<br />
# Run 'obmc-console-client' on the BMC to attach the current SSH shell to the serial console<br />
# Attach the Debian install media<br />
# Power on the system<br />
# When the Petitboot screen appears, select the Debian install option you want and press 'e' to edit<br />
# Highlight the "Boot arguments" field and append "console=hvc0" after "quiet". Ensure there is at least one space between "quiet" and "console=hvc0".<br />
# Highlight OK and press Enter<br />
# Ensure the previously-selected Debian install option is still selected, then press Enter<br />
# Install Debian normally<br />
<br />
* Switch from serial to VGA text console<br />
<br />
# Edit /etc/initramfs-tools/modules and append "ast" to it<br />
# As root, run update-initramfs -u -k all<br />
# Edit /etc/default/grub and change the "console=hvc0" string to "console=tty0"<br />
# As root, run update-grub<br />
# Reboot<br />
<br />
=== Blank output on GPU after blacklisting AST ===<br />
'''Cause'''<br />
<br />
There appears to be an oversight in Debian wherein when the ''firmware-amd-graphics'' package is installed initramfs is not updated automatically to include the amdgpu module and the GPU firmware.<br />
<br />
'''Workaround'''<br />
<br />
* Manually load amdgpu into initramfs<br />
<br />
#Append ''amdgpu'' to /etc/initramfs-tools/modules<br />
#As root, run update-initramfs -u<br />
#Edit /etc/default/grub and change GRUB_CMDLINE_LINUX= to GRUB_CMDLINE_LINUX="modprobe.blacklist=ast video=offb:off console=tty0"<br />
#Run update-grub as root<br />
#Shutdown<br />
#With BMC power disconnected, ascertain that the J10109 jumper is set as disabled before booting again<br />
<br />
=== AMD GPUs: OpenGL failure / rectangular boxes instead of fonts in GDM3 ===<br />
'''Cause'''<br />
<br />
Debian ships a patched Linux kernel that introduces Debian-specific bugs in the AMD GPU driver. One of these bugs impacts all 64k page size systems, including the default kernels for ppc64le, and leads to generic failure of most OpenGL applications, including failure of font rendering in Gnome applications and, most notably, GDM3.<br />
<br />
'''Upstream Bug Report'''<br />
<br />
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990279<br />
<br />
'''Status'''<br />
<br />
Root cause found, solution provided, discussion stalled, '''upstream no longer responding'''<br />
<br />
'''Workaround'''<br />
<br />
Apply the patch in the listed bug report (and reproduced below) to the current Debian kernel, then recompile and install:<br />
<br />
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; overflow:auto;"><br />
<pre><br />
From 02c987eb2ab0cdfd536d08bf812f4e37d3cc150a Mon Sep 17 00:00:00 2001<br />
From: Huacai Chen <chenhc@lemote.com><br />
Date: Tue, 30 Mar 2021 23:33:33 +0800<br />
Subject: [PATCH] drm/amdgpu: Set a suitable dev_info.gart_page_size<br />
MIME-Version: 1.0<br />
Content-Type: text/plain; charset=UTF-8<br />
Content-Transfer-Encoding: 8bit<br />
<br />
commit f4d3da72a76a9ce5f57bba64788931686a9dc333 upstream.<br />
<br />
In Mesa, dev_info.gart_page_size is used for alignment and it was<br />
set to AMDGPU_GPU_PAGE_SIZE(4KB). However, the page table of AMDGPU<br />
driver requires an alignment on CPU pages. So, for non-4KB page system,<br />
gart_page_size should be max_t(u32, PAGE_SIZE, AMDGPU_GPU_PAGE_SIZE).<br />
<br />
Signed-off-by: Rui Wang <wangr@lemote.com><br />
Signed-off-by: Huacai Chen <chenhc@lemote.com><br />
Link: https://github.com/loongson-community/linux-stable/commit/caa9c0a1<br />
[Xi: rebased for drm-next, use max_t for checkpatch,<br />
and reworded commit message.]<br />
Signed-off-by: Xi Ruoyao <xry111@mengyan1223.wang><br />
BugLink: https://gitlab.freedesktop.org/drm/amd/-/issues/1549<br />
Tested-by: Dan Horák <dan@danny.cz><br />
Reviewed-by: Christian König <christian.koenig@amd.com><br />
Signed-off-by: Alex Deucher <alexander.deucher@amd.com><br />
[Salvatore Bonaccorso: Backport to 5.10.y which does not contain<br />
a5a52a43eac0 ("drm/amd/amdgpu/amdgpu_kms: Remove 'struct<br />
drm_amdgpu_info_device dev_info' from the stack") which removes dev_info<br />
from the stack and places it on the heap.]<br />
Signed-off-by: Salvatore Bonaccorso <carnil@debian.org><br />
---<br />
drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c | 4 ++--<br />
1 file changed, 2 insertions(+), 2 deletions(-)<br />
<br />
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c<br />
index efda38349a03..917b94002f4b 100644<br />
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c<br />
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c<br />
@@ -766,9 +766,9 @@ static int amdgpu_info_ioctl(struct drm_device *dev, void *data, struct drm_file<br />
dev_info.high_va_offset = AMDGPU_GMC_HOLE_END;<br />
dev_info.high_va_max = AMDGPU_GMC_HOLE_END | vm_size;<br />
}<br />
- dev_info.virtual_address_alignment = max((int)PAGE_SIZE, AMDGPU_GPU_PAGE_SIZE);<br />
+ dev_info.virtual_address_alignment = max_t(u32, PAGE_SIZE, AMDGPU_GPU_PAGE_SIZE);<br />
dev_info.pte_fragment_size = (1 << adev->vm_manager.fragment_size) * AMDGPU_GPU_PAGE_SIZE;<br />
- dev_info.gart_page_size = AMDGPU_GPU_PAGE_SIZE;<br />
+ dev_info.gart_page_size = max_t(u32, PAGE_SIZE, AMDGPU_GPU_PAGE_SIZE);<br />
dev_info.cu_active_number = adev->gfx.cu_info.number;<br />
dev_info.cu_ao_mask = adev->gfx.cu_info.ao_cu_mask;<br />
dev_info.ce_ram_size = adev->gfx.ce_ram_size;<br />
-- <br />
2.33.0<br />
</pre><br />
</div><br />
<br />
Note that compiling a new Debian kernel as shown requires 24GB or more free disk space, and that you will need to repeat this process every time a Debian kernel security update is released. To reduce load on all impacted users, if you are impacted we strongly recommend you help put pressure on the Debian maintainers to merge the tested and working patch that is languishing in the bug report above.<br />
<br />
On a default Bullseye system:<br />
# apt-get source linux-image-5.10.0-10-powerpc64le<br />
# cd linux-5.10.*<br />
# Patch drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c<br />
# make bindeb-pkg -j32 (adjust -j for number of CPUs to use for build)<br />
# cd ..<br />
# dpkg -i linux-image-5.10.*_5.10.*-1_ppc64el.deb</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Operating_System_Specific_Workarounds/Debian&diff=3611
Operating System Specific Workarounds/Debian
2022-01-26T05:39:39Z
<p>SiteAdmin: </p>
<hr />
<div>= Debian-Specific Issues and Workarounds =<br />
<br />
__TOC__<br />
<br />
== Bullseye ==<br />
<br />
=== Blank VGA ===<br />
'''Cause'''<br />
<br />
The required open-source (libre) video driver module ("ast") is not included in the installer package<br />
<br />
'''Upstream Bug Report'''<br />
<br />
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990016<br />
<br />
'''Status'''<br />
<br />
Root cause found, solution provided, '''upstream not responding'''<br />
<br />
'''Workaround'''<br />
<br />
Debian can be installed via the serial console, then switched to VGA mode after installation (i.e. after the ASpeed driver module is available to the kernel). The following instructions assume you have SSH shell access to the BMC:<br />
<br />
* Install<br />
<br />
# With system power off, SSH to the BMC<br />
# Run 'obmc-console-client' on the BMC to attach the current SSH shell to the serial console<br />
# Attach the Debian install media<br />
# Power on the system<br />
# When the Petitboot screen appears, select the Debian install option you want and press 'e' to edit<br />
# Highlight the "Boot arguments" field and append "console=hvc0" after "quiet". Ensure there is at least one space between "quiet" and "console=hvc0".<br />
# Highlight OK and press Enter<br />
# Ensure the previously-selected Debian install option is still selected, then press Enter<br />
# Install Debian normally<br />
<br />
* Switch from serial to VGA text console<br />
<br />
# Edit /etc/initramfs-tools/modules and append "ast" to it<br />
# As root, run update-initramfs -u -k all<br />
# Edit /etc/default/grub and change the "console=hvc0" string to "console=tty0"<br />
# As root, run update-grub<br />
# Reboot<br />
<br />
=== Blank output on GPU after blacklisting AST ===<br />
'''Cause'''<br />
<br />
There appears to be an oversight in Debian wherein when the ''firmware-amd-graphics'' package is installed initramfs is not updated automatically to include the amdgpu module and the GPU firmware.<br />
<br />
'''Workaround'''<br />
<br />
* Manually load amdgpu into initramfs<br />
<br />
#Append ''amdgpu'' to /etc/initramfs-tools/modules<br />
#As root, run update-initramfs -u<br />
#Edit /etc/default/grub and change GRUB_CMDLINE_LINUX= to GRUB_CMDLINE_LINUX="modprobe.blacklist=ast video=offb:off console=tty0"<br />
#Run update-grub as root<br />
#Shutdown<br />
#With BMC power disconnected, ascertain that the J10109 jumper is set as disabled before booting again<br />
<br />
=== AMD GPUs: OpenGL failure / rectangular boxes instead of fonts in GDM3 ===<br />
'''Cause'''<br />
<br />
Debian ships a Linux kernel that introduces Debian-specific bugs in the AMD GPU driver that impact all 64k page size systems, including the default kernels for ppc64le.<br />
<br />
'''Upstream Bug Report'''<br />
<br />
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990279<br />
<br />
'''Status'''<br />
<br />
Root cause found, solution provided, discussion stalled, '''upstream no longer responding'''<br />
<br />
'''Workaround'''<br />
<br />
Apply the patch in the listed bug report (and reproduced below) to the current Debian kernel, then recompile and install:<br />
<br />
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px; overflow:auto;"><br />
<pre><br />
From 02c987eb2ab0cdfd536d08bf812f4e37d3cc150a Mon Sep 17 00:00:00 2001<br />
From: Huacai Chen <chenhc@lemote.com><br />
Date: Tue, 30 Mar 2021 23:33:33 +0800<br />
Subject: [PATCH] drm/amdgpu: Set a suitable dev_info.gart_page_size<br />
MIME-Version: 1.0<br />
Content-Type: text/plain; charset=UTF-8<br />
Content-Transfer-Encoding: 8bit<br />
<br />
commit f4d3da72a76a9ce5f57bba64788931686a9dc333 upstream.<br />
<br />
In Mesa, dev_info.gart_page_size is used for alignment and it was<br />
set to AMDGPU_GPU_PAGE_SIZE(4KB). However, the page table of AMDGPU<br />
driver requires an alignment on CPU pages. So, for non-4KB page system,<br />
gart_page_size should be max_t(u32, PAGE_SIZE, AMDGPU_GPU_PAGE_SIZE).<br />
<br />
Signed-off-by: Rui Wang <wangr@lemote.com><br />
Signed-off-by: Huacai Chen <chenhc@lemote.com><br />
Link: https://github.com/loongson-community/linux-stable/commit/caa9c0a1<br />
[Xi: rebased for drm-next, use max_t for checkpatch,<br />
and reworded commit message.]<br />
Signed-off-by: Xi Ruoyao <xry111@mengyan1223.wang><br />
BugLink: https://gitlab.freedesktop.org/drm/amd/-/issues/1549<br />
Tested-by: Dan Horák <dan@danny.cz><br />
Reviewed-by: Christian König <christian.koenig@amd.com><br />
Signed-off-by: Alex Deucher <alexander.deucher@amd.com><br />
[Salvatore Bonaccorso: Backport to 5.10.y which does not contain<br />
a5a52a43eac0 ("drm/amd/amdgpu/amdgpu_kms: Remove 'struct<br />
drm_amdgpu_info_device dev_info' from the stack") which removes dev_info<br />
from the stack and places it on the heap.]<br />
Signed-off-by: Salvatore Bonaccorso <carnil@debian.org><br />
---<br />
drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c | 4 ++--<br />
1 file changed, 2 insertions(+), 2 deletions(-)<br />
<br />
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c<br />
index efda38349a03..917b94002f4b 100644<br />
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c<br />
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c<br />
@@ -766,9 +766,9 @@ static int amdgpu_info_ioctl(struct drm_device *dev, void *data, struct drm_file<br />
dev_info.high_va_offset = AMDGPU_GMC_HOLE_END;<br />
dev_info.high_va_max = AMDGPU_GMC_HOLE_END | vm_size;<br />
}<br />
- dev_info.virtual_address_alignment = max((int)PAGE_SIZE, AMDGPU_GPU_PAGE_SIZE);<br />
+ dev_info.virtual_address_alignment = max_t(u32, PAGE_SIZE, AMDGPU_GPU_PAGE_SIZE);<br />
dev_info.pte_fragment_size = (1 << adev->vm_manager.fragment_size) * AMDGPU_GPU_PAGE_SIZE;<br />
- dev_info.gart_page_size = AMDGPU_GPU_PAGE_SIZE;<br />
+ dev_info.gart_page_size = max_t(u32, PAGE_SIZE, AMDGPU_GPU_PAGE_SIZE);<br />
dev_info.cu_active_number = adev->gfx.cu_info.number;<br />
dev_info.cu_ao_mask = adev->gfx.cu_info.ao_cu_mask;<br />
dev_info.ce_ram_size = adev->gfx.ce_ram_size;<br />
-- <br />
2.33.0<br />
</pre><br />
</div><br />
<br />
Note that compiling a new Debian kernel as shown requires 24GB or more free disk space, and that you will need to repeat this process every time a Debian kernel security update is released. To reduce load on all impacted users, if you are impacted we strongly recommend you help put pressure on the Debian maintainers to merge the tested and working patch that is languishing in the bug report above.<br />
<br />
On a default Bullseye system:<br />
# apt-get source linux-image-5.10.0-10-powerpc64le<br />
# cd linux-5.10.*<br />
# Patch drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c<br />
# make bindeb-pkg -j32 (adjust -j for number of CPUs to use for build)<br />
# cd ..<br />
# dpkg -i linux-image-5.10.*_5.10.*-1_ppc64el.deb</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&diff=3607
Operating System Compatibility List
2022-01-10T20:11:28Z
<p>SiteAdmin: Add link to Debian Bullseye VGA workaround</p>
<hr />
<div>Not everything is bug-free, so you might want to the check also [[Fixes in Progress]] about the state of their upstreaming.<br />
== GNU/Linux ==<br />
{| class="wikitable"<br />
|Distribution<br />
|Version<br />
|Architecture<br />
|Reported by<br />
|Notes<br />
|-<br />
|[https://www.adelielinux.org/ Adélie]<br />
|1.0-beta1<br />
|ppc64<br />
|[[User:Awilfox|awilfox]]<br />
|Needs the easy-kernel-power8 package instead of easy-kernel. KDE 5 is stable.<br />
|-<br />
|[https://alpinelinux.org/ Alpine]<br />
|3.11.5<br />
|ppc64le<br />
|[[User:Tle|Tle]]<br />
|Needs internet connection for the setup-alpine to fetch grub-ieee1275 and sfdisk. Let's hope the next version would include these two packages in the ISO. I have lodged a [https://gitlab.alpinelinux.org/alpine/aports/issues/11384 request]<br />
|-<br />
|[https://en.altlinux.org/ ALT]<br />
|10.0<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Unable to install. The image is not displayed in Petitboot.<br />
|-<br />
|[https://aosc.io/ AOSC OS]<br />
|RR<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Not tested yet.<br />
|-<br />
|[https://archlinuxpower.org/ Arch]<br />
|RR<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Not tested yet.<br />
|-<br />
|[https://ataraxialinux.org/ Ataraxia]<br />
|201101<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Not tested yet.<br />
|-<br />
|[https://bedrocklinux.org/ Bedrock]<br />
|0.7.24<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Not tested yet.<br />
|-<br />
|[https://www.centos.org/ CentOS]<br />
|7.7<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Works OOTB. I only needed the [[Troubleshooting/GPU#Xorg_crashes_or_is_laggy_with_the_AST_VGA_GPU| snippets for the AST GPU]]<br />
|-<br />
|rowspan="9"|[https://cdimage.debian.org/cdimage/ Debian]<br />
|11.1.0 (netinst)<br />
|ppc64le<br />
|[[User:Jas|Jas]]<br />
|Installs and works out of box with no changes. Installer is on serial port, VGA is blank <br />
([[Operating_System_Specific_Workarounds/Debian#Bullseye|workaround]]). Works fine as a KVM host via virt-manager and a Debian 11 guest VM.<br />
|-<br />
|11 (2021-03-29 weekly DVD ISO)<br />
|ppc64le (inside KVM; machine type = pseries)<br />
|[[User:JeremyRand|JeremyRand]]<br />
|Seems to work fine with XFCE.<br />
|-<br />
|11/Sid (2021-02-02 [https://cdimage.debian.org/cdimage/ports/snapshots/ snapshot])<br />
|ppc64 (BE) (inside KVM; machine type = pseries)<br />
|[[User:JeremyRand|JeremyRand]]<br />
|Seems to work fine with XFCE. Note that even though this ISO is labeled "10.0.0" in the filename, it is actually Sid, not Buster.<br />
|-<br />
|10 (2018-05-28 weekly DVD ISO)<br />
|ppc64le<br />
|[[User:JeremyRand|JeremyRand]]<br />
|Seems to work fine. KDE crashes occasionally, but that might be unrelated to running it on POWER9. Works fine as a KVM host via virt-manager (tested with Debian 10 as the guest). Be warned that the installer will enable the contrib repos (without your knowledge or consent), which is bad from a software freedom standpoint.<br />
|-<br />
|[https://cdimage.debian.org/cdimage/ports/10.0/ 10.0] (ISO is dated 2018-05-18)<br />
|ppc64 (BE) (inside KVM; machine type = pseries)<br />
|[[User:JeremyRand|JeremyRand]]<br />
|ISO fails to boot in virt-manager.<br />
|-<br />
|10<br />
|ppc64<br />
|[[User:Awilfox|awilfox]]<br />
|Only tested in KVM-PV. Using Adélie easy-kernel as kernel, Debian Buster userland.<br />
|-<br />
|9.9.0<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Works OOTB. I only needed the [[Troubleshooting/GPU#Xorg_crashes_or_is_laggy_with_the_AST_VGA_GPU| snippets for the AST GPU]]<br />
|-<br />
|9.5.0<br />
|ppc64le (inside KVM; machine type = pseries)<br />
|[[User:JeremyRand|JeremyRand]]<br />
|Seems to work fine with KDE. Default version of Linux works fine. Be warned that the installer will enable the contrib repos (without your knowledge or consent), which is bad from a software freedom standpoint. However, running <code>dpkg-query -W -f='${Section}\t${Package}\n' &#124; grep ^contrib</code> (see [https://unix.stackexchange.com/a/111102 this Stack Exchange answer]) suggests that no actual packages from the contrib repos are installed by default, so you should be able to disable the contrib repos after installation without ever being exposed to contrib-packaged software.<br />
|-<br />
|9<br />
|ppc64le<br />
|[[User:nashimus|nashimus]]<br />
|Requires 4.16 or newer kernel. Installed Debian testing net install, set apt sources to Debian stable and downgraded, keeping 4.16 kernel. Most VMs failed to boot before updating qemu to 2.12.0.<br />
|-<br />
|[https://www.devuan.org/ Devuan]<br />
|4.0<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Works<br />
|-<br />
|rowspan="11"|[https://alt.fedoraproject.org/alt/ Fedora]<br />
|35<br />
|ppc64le<br />
|ClassicHasClass<br />
|[https://www.talospace.com/2021/11/fedora-35-mini-review-on-blackbird-and.html Review at Talospace.]<br />
|-<br />
|34<br />
|ppc64le<br />
|ClassicHasClass<br />
|[https://www.talospace.com/2021/05/fedora-34-mini-review-on-blackbird-and.html Review at Talospace.]<br />
|-<br />
|rowspan="2"|33<br />
|rowspan="2"|ppc64le<br />
|[[User:Tle|Tle]]<br />
|Server and Workstation variant works perfectly!<br />
|-<br />
|ClassicHasClass<br />
|[https://www.talospace.com/2020/11/fedora-33-mini-review-on-blackbird-and.html Review at Talospace.]<br />
|-<br />
|rowspan="2"|32<br />
|rowspan="2"|ppc64le<br />
|[[User:Tle|Tle]]<br />
|Server variant works perfectly!<br />
The Workstation Live variant failed to load kernel image at Petitboot prompt, the workaround is to change kernel/initrd paths before booting to<br />
be /ppc/ppc64/{vmlinuz,initrd.img} instead of /ppc/ppc<br />
|-<br />
|ClassicHasClass<br />
|[https://www.talospace.com/2020/05/fedora-32-mini-review-on-blackbird-and.html Review at Talospace.]<br />
|-<br />
|31<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Works. I only needed the [[Troubleshooting/GPU#Xorg_crashes_or_is_laggy_with_the_AST_VGA_GPU| snippets for the AST GPU]]. When installing GNOME (workstation-product-environment) you have to do [[Troubleshooting/GPU#Wayland_.28GNOME.29_freeze_after_boot_with_the_AST_VGA_GPU|this modification]]<br />
|-<br />
|30<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Works OOTB. I only needed the [[Troubleshooting/GPU#Xorg_crashes_or_is_laggy_with_the_AST_VGA_GPU| snippets for the AST GPU]]<br />
|-<br />
|rowspan="3"|28<br />
|ppc64le<br />
|[[User:Sharkcz|Sharkcz]]<br />
|only bare metal verified for now, you might want to enable [[User:Sharkcz|SharkCZ]]'s COPR [https://copr.fedorainfracloud.org/coprs/sharkcz/talos/ repo] for not-yet-upstreamed updates<br />
|-<br />
|ppc64le<br />
|[[User:nashimus|nashimus]]<br />
|May need to manually specify inst.stage2, during install. [https://www.ibm.com/developerworks/community/blogs/cb4b63c0-e358-474c-8b04-391c3a279d5a/entry/Baremetal_RHEL_Redhat_Installation_with_OPAL?lang=en Workaround] [https://bugzilla.redhat.com/show_bug.cgi?id=1577587 Bug]<br />
|-<br />
|ppc64<br />
|[[User:Sharkcz|Sharkcz]]<br />
|discontinued in Fedora 29<br />
|-<br />
|rowspan="2|[https://wiki.gentoo.org/wiki/Handbook:PPC64 Gentoo]<br />
| n/a<br />
|ppc64le<br />
|[[User:Luke-jr|luke-jr]]<br />
|Once installed, works fine.<br />
Gnome, Plasma and other desktops are supported.<br />
Ships working firefox, chromium, qtwebengine. <br />
[https://distfiles.gentoo.org/releases/ppc/autobuilds/current-install-ppc64le-minimal/ latest install iso supporting both 4k and 64k pagesize kernels]<br />
|-<br />
|17.0<br />
|ppc64<br />
|[[User:MarcusC|MarcusC]]<br />
|XFCE4 and virt-manager verified<br />
|-<br />
|[https://www.glasnost.org/ Glasnost]<br />
|2021.10-01<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Not tested yet.<br />
|-<br />
|[http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/Kicksecure Kicksecure] ([https://www.whonix.org/wiki/Kicksecure clearnet link])<br />
|16<br />
|ppc64le<br />
|[[User:JeremyRand|JeremyRand]]<br />
|Appears to work fine with XFCE in a VM when the [[Kicksecure]] instructions are followed. Haven't tried CLI or host.<br />
|-<br />
|rowspan="2"|[https://www.opensuse.org/ openSUSE]<br />
|Leap 15.1<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Works OOTB. I only needed the [[Troubleshooting/GPU#Xorg_crashes_or_is_laggy_with_the_AST_VGA_GPU| snippets for the AST GPU]]<br />
|-<br />
|Tumbleweed 20190805<br />
|ppc64le<br />
|[[User:Jonsger|Jonsger]]<br />
|Install via serial console (over ssh) and connect HDMI to dedicated GPU. Use Xorg config from [[Troubleshooting/GPU#Step_2:_Create_Xorg_Configuration_Snippet]]. radeonsi is missing, as Mesa-dri is not build for ppc64le. Workaround: install from [https://build.opensuse.org/project/show/home:jbrielmaier:ppc64le home:jbrielmaier:ppc64le] repo.<br />
|-<br />
|[https://www.powerel.org/ PowerEL]<br />
|7<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Unable to install. The image is not displayed in Petitboot.<br />
|-<br />
|[https://www.riscyslack.org/ Riscy Slack (Slackware)]<br />
|2020-11-17<br />
|ppc64le<br />
|[[User: MPC7500|MPC7500]]<br />
|Works OOTB. I only needed the [[Troubleshooting/GPU#Xorg_crashes_or_is_laggy_with_the_AST_VGA_GPU| snippets for the AST GPU]]<br />
|-<br />
|[http://t2sde.org/ T2 SDE]<br />
|21.5<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Not tested yet.<br />
|-<br />
|rowspan="4"|[https://www.ubuntu.com/download/server/power Ubuntu Server]<br />
|20.04 LTS<br />
|ppc64le<br />
|[[User:Jas|Jas]]<br />
|Installs and works out of box with no changes.<br />
|-<br />
|19.10 (kernel 5.3.x)<br />
|ppc64le<br />
|[[User:FlyingBlackbird|FlyingBlackbird]]<br />
|Works OOTB with Gnome (installed via <code>sudo tasksel</code> choosing ''Ubuntu Desktop'') and a single SATA HDD. I only needed to configure Xorg for a FullHD resolution of the AST GPU as described in [[Troubleshooting/GPU#Display_stuck_at_default_low_resolution_with_AST_HDMI_GPU]]. Note that NVMe SSDs may crash when a manual or scheduled <code>discard</code> ("trim") is started (due to a kernel bug fixed in 5.4 but there is a work-around, see [[POWER9 Hardware Compatibility List/PCIe Devices#NVMe_Drives]]. So far a combination of a NVMe SSD and SATA HDD makes troubles if both drives are used for OS installation targets with booting from HDD causes ATA error messages (I am investigating this, see the [[User:FlyingBlackbird|up-to-date status of my system configuration]]).<br />
|-<br />
|19.04<br />
|ppc64le<br />
|[[User:MPC7500|MPC7500]]<br />
|Works OOTB. I only needed the [[Troubleshooting/GPU#Xorg_crashes_or_is_laggy_with_the_AST_VGA_GPU| snippets for the AST GPU]]<br />
|-<br />
|18.10<br />
|ppc64le<br />
|[[User:q66|q66]]<br />
|Installs and works out of box with no changes, Xfce4.<br />
|-<br />
|[https://voidlinux-ppc.org Void Linux for Power Architecture]<br />
|n/a<br />
|ppc64le/ppc64/ppc<br />
|[[User:q66|q66]]<br />
|Staging fork of Void Linux (custom binary repository and infrastructure, merging changes back upstream), fully functional, both endians, glibc or musl, 64-bit or 32-bit (32-bit works on Talos with 64-bit kernel or in a VM)<br />
|-<br />
|rowspan="5"|[http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ Whonix] ([https://www.whonix.org/ clearnet link])<br />
|16<br />
|ppc64le<br />
|[[User:JeremyRand|JeremyRand]]<br />
|Appears to work fine with XFCE (both Gateway and Workstation) when the [[Whonix]] instructions are followed. Haven't tried CLI.<br />
|-<br />
|15 (Morphed from Sid)<br />
|ppc64 (BE)<br />
|[[User:JeremyRand|JeremyRand]]<br />
|Dependency conflicts prevent distro-morphing from Debian Sid to Whonix. I'm working on getting these fixed.<br />
|-<br />
|15 (Morphed from Buster)<br />
|ppc64le<br />
|[[User:JeremyRand|JeremyRand]]<br />
|Appears to work fine with KDE (both Gateway and Workstation) when the [[Whonix]] instructions are followed; host OS used for testing was Debian 10. Haven't tried XFCE and CLI.<br />
|-<br />
|rowspan="2"|14<br />
|ppc64le<br />
|[[User:JeremyRand|JeremyRand]]<br />
|Appears to work fine when the [[Whonix]] instructions are followed; host OS used for testing was Debian 10. (UPDATE: Whonix 14 is no longer recommended by upstream for KVM; use Whonix 15 instead.)<br />
|-<br />
|amd64<br />
|[[User:JeremyRand|JeremyRand]]<br />
|Appears to boot without errors when the [[Whonix/x86]] instructions are followed; host OS used for testing was Debian 10. Didn't test anything beyond showing the XFCE GUI.<br />
|}<br />
<br />
== BSDs ==<br />
{| class="wikitable"<br />
|Distribution<br />
|Version<br />
|Architecture<br />
|Reported by<br />
|Notes<br />
|-<br />
|rowspan="2"|[https://www.freebsd.org/ FreeBSD]<br />
|13-CURRENT<br />
|ppc64<br />
|[[User:kev009|kev009]]<br />
|Ongoing development activity, better than releases for the time being<br />
|-<br />
|12.0<br />
|ppc64<br />
|[[User:kev009|kev009]]<br />
|Contains initial POWER9 support<br />
|-<br />
|[http://www.openbsd.org/powerpc64.html OpenBSD]<br />
|6.8<br />
|powerpc64<br />
|[[User:DanielPocock|DanielPocock]]<br />
|Official support since OpenBSD 6.8<br />
|-<br />
|[https://github.com/POWER9BSD/ POWER9BSD]<br />
|13-CURRENT<br />
|ppc64<br />
|[[User:kev009|kev009]]<br />
|Advance POWER9 features for FreeBSD like Radix MMU, amdgpu etc<br />
|-<br />
|}<br />
<br />
==Ports in progress==<br />
Rapid progress is being made on these ports by members of the community.<br />
<br />
* GNU Guix System ([[User:Isengaara|Isengaara]] and lle-bout (email: lle-bout at zaclys dot net))<br />
* NixOS (@crystalgamma:matrix.org on Matrix)<br />
<br />
== External Links ==<br />
<br />
* [http://bgafc.t-hosting.hu/oses4ppc.php Operating Systems for PowerPC] PPC32 / PPC64 / PPC64le<br />
<br />
[[Category:Compatibility List]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Operating_System_Specific_Workarounds/Debian&diff=3606
Operating System Specific Workarounds/Debian
2022-01-10T20:08:24Z
<p>SiteAdmin: Created page with "= Debian-Specific Issues and Workarounds = __TOC__ == Bullseye == === Blank VGA === '''Cause''' The required open-source (libre) video driver module ("ast") is not include..."</p>
<hr />
<div>= Debian-Specific Issues and Workarounds =<br />
<br />
__TOC__<br />
<br />
== Bullseye ==<br />
<br />
=== Blank VGA ===<br />
'''Cause'''<br />
<br />
The required open-source (libre) video driver module ("ast") is not included in the installer package<br />
<br />
'''Upstream Bug Report'''<br />
<br />
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99001<br />
<br />
'''Status'''<br />
<br />
Root cause found, solution provided, '''upstream not responding'''<br />
<br />
'''Workaround'''<br />
<br />
Debian can be installed via the serial console, then switched to VGA mode after installation (i.e. after the ASpeed driver module is available to the kernel). The following instructions assume you have SSH shell access to the BMC:<br />
<br />
* Install<br />
<br />
# With system power off, SSH to the BMC<br />
# Run 'obmc-console-client' on the BMC to attach the current SSH shell to the serial console<br />
# Attach the Debian install media<br />
# Power on the system<br />
# When the Petitboot screen appears, select the Debian install option you want and press 'e' to edit<br />
# Highlight the "Boot arguments" field and append "console=hvc0" after "quiet". Ensure there is at least one space between "quiet" and "console=hvc0".<br />
# Highlight OK and press Enter<br />
# Ensure the previously-selected Debian install option is still selected, then press Enter<br />
# Install Debian normally<br />
<br />
* Switch from serial to VGA text console<br />
<br />
# Edit /etc/modules and append "ast" to it<br />
# As root, run update-initramfs -u -k all<br />
# Edit /etc/default/grub and change the "console=hvc0" string to "console=tty0"<br />
# As root, run update-grub<br />
# Reboot</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Blackbird/Firmware&diff=3574
Blackbird/Firmware
2021-10-29T19:06:10Z
<p>SiteAdmin: </p>
<hr />
<div>= Blackbird Official Firmware Builds =<br />
<br />
For upgrade instructions, please visit the [[Firmware_Upgrade_Quickstart|Firmware Upgrade Quick Start]] page. Alternatively, for those wishing to build from source, please visit the [[Blackbird/Compiling_Firmware|Compiling Firmware]] page.<br />
<br />
All firmware builds are cryptographically signed with the current Raptor Computing Systems firmware signing key at time of release [https://raptorcs.com/verification/gpg/blackbird/firmware_builds/]. The intermediate firmware signer keys, in turn, are signed by our master umbrella key [https://raptorcs.com/keys/gpg/0x337BF51F.pub].<br />
<br />
== System Package v2.00a ==<br />
Released: 10-29-2021<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00a/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00a-bundle.tar|c13110c4cbb6bfa8b4912650a462824e1deb4ae5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.02.rom|2b48243d7c404f3841f9ebe45aed9c3bee09ebe2]]<br />
<br />
== System Package v2.00 ==<br />
Released: 02-19-2020<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00-bundle.tar|7cbe7a8d60a255a94c27138162a03e743df6c9c5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.01.rom|9ddbe70ea5e85466c1e24da927b135e62810c93f]]<br />
<br />
== System Package v1.00 ==<br />
Released: 05-22-2019<br />
* BMC: [[:File:Blackbird_openbmc_v1.00_bundle.tar.bz2|eb50c3fe9fc09aec6f874946362642bbd73a6955]]<br />
* PNOR: [[:File:Blackbird_host_pnor_v1.00.bin.bz2|3fe7beacf0ced330b2fdd5302c5f48f7458e98c3]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.00.rom|32784cea6d7b9fac9871e9d3909d4b7ac199a7f6]]<br />
<br />
Change Log<br />
* Initial release<br />
<br />
Known Issues<br />
* DRAM is capped to 2400MHz. This is not a hardware problem, it is an issue somewhere in hostboot that is being actively worked. 2666MHz DIMMs installed will function at 2400MHz pending a PNOR update to enable 2666MHz support.<br />
* The BMC kernel (incorrectly) detects an SPI master collision on bus 12, yielding a never ending stream of warnings from the i2c core. As this is not a trivial fix given the state of the ASpeed i2c drivers, and the spew is mostly harmless, the decision was made to ship anyway instead of incurring a lengthy delay to rewrite the drivers. If console access to the BMC is desired over serial, "dmesg -n 1" after login will silence the warnings on the console. This issue will be fixed in a future BMC firmware update.<br />
<br />
[[Category:Blackbird_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Blackbird-pnor-v2.00a-bundle.tar&diff=3573
File:Blackbird-pnor-v2.00a-bundle.tar
2021-10-29T19:05:44Z
<p>SiteAdmin: == Summary ==
Built from https://git.raptorcs.com/git/blackbird-op-build/tag/?h=raptor-v2.00a<br>
Corresponding GIT hash, as shown on test reports: '''c13110c4cbb6bfa8b4912650a462824e1deb4ae5'''
Category:Blackbird_Firmware</p>
<hr />
<div>== Summary ==<br />
Built from https://git.raptorcs.com/git/blackbird-op-build/tag/?h=raptor-v2.00a<br><br />
Corresponding GIT hash, as shown on test reports: '''c13110c4cbb6bfa8b4912650a462824e1deb4ae5'''<br />
<br />
[[Category:Blackbird_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Blackbird/Firmware/2.00a/Release_Notes&diff=3572
Blackbird/Firmware/2.00a/Release Notes
2021-10-29T19:01:55Z
<p>SiteAdmin: </p>
<hr />
<div>== System Package 2.00 Release Notes ==<br />
<br />
=== BMC ===<br />
<br />
* No change<br />
<br />
=== PNOR ===<br />
<br />
* Fix LSI SAS (mpt3sas kernel module) crash in petitboot.<br />
<br />
=== FPGA ===<br />
<br />
* Add standby VDDRAB 1.2V power plane controls for corresponding hardware in Blackbird planar revisions 1.02 and above.<br />
<br />
=== Known Issues ===<br />
* New BMC cannot IPL old PNOR and vice versa (CANTFIX)<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
* Certain DIMMs may not function in Slot 0. This is '''not''' a defect in the Blackbird planar, it is a memory VPD issue that is being worked by Raptor and the IBM memory team. Future firmware updates are expected to address this problem.<br />
* Upgrading from a BMC that has been manually edited to add or remove users can result in loss of SSH access after the upgrade has completed. The root cause is that <CODE>/etc/passwd</CODE> is retained verbatim across updates if modified, and as a result the new <CODE>sshd</CODE> user is not present in the upgraded firmware environment.<br />
** Prior to upgrading such a BMC, the following line should be added to <CODE>/etc/passwd</CODE> on the BMC:<BR><CODE>sshd:x:996:995::/var/run/sshd:/bin/false</CODE><br />
** Alternatively, the files <CODE>/etc/passwd</CODE> and <CODE>/etc/group</CODE> can be removed immediately before reboot to apply the update. Caution should be used with this method, as failure to apply the update could then result in a requirement to use a BMC serial cable or external SPI flasher to recover.</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Blackbird/Firmware/2.00a/Release_Notes&diff=3571
Blackbird/Firmware/2.00a/Release Notes
2021-10-29T18:48:46Z
<p>SiteAdmin: Created page with "== System Package 2.00 Release Notes == === BMC === * No change === PNOR === * No change === FPGA === * Add standby VDDRAB 1.2V power plane controls for corresponding ha..."</p>
<hr />
<div>== System Package 2.00 Release Notes ==<br />
<br />
=== BMC ===<br />
<br />
* No change<br />
<br />
=== PNOR ===<br />
<br />
* No change<br />
<br />
=== FPGA ===<br />
<br />
* Add standby VDDRAB 1.2V power plane controls for corresponding hardware in Blackbird planar revisions 1.02 and above.<br />
<br />
=== Known Issues ===<br />
* New BMC cannot IPL old PNOR and vice versa (CANTFIX)<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
* Certain DIMMs may not function in Slot 0. This is '''not''' a defect in the Blackbird planar, it is a memory VPD issue that is being worked by Raptor and the IBM memory team. Future firmware updates are expected to address this problem.<br />
* Upgrading from a BMC that has been manually edited to add or remove users can result in loss of SSH access after the upgrade has completed. The root cause is that <CODE>/etc/passwd</CODE> is retained verbatim across updates if modified, and as a result the new <CODE>sshd</CODE> user is not present in the upgraded firmware environment.<br />
** Prior to upgrading such a BMC, the following line should be added to <CODE>/etc/passwd</CODE> on the BMC:<BR><CODE>sshd:x:996:995::/var/run/sshd:/bin/false</CODE><br />
** Alternatively, the files <CODE>/etc/passwd</CODE> and <CODE>/etc/group</CODE> can be removed immediately before reboot to apply the update. Caution should be used with this method, as failure to apply the update could then result in a requirement to use a BMC serial cable or external SPI flasher to recover.<br />
* Systems with LSI SAS controllers (mpt3sas kernel module) crash in petitboot and are unable to boot the target OS<br />
** WORKAROUND: Use [[:File:Blackbird-2.01-beta-pnor.tar|our current 2.01 Beta PNOR]] instead of the 2.00 release PNOR</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Blackbird/Firmware&diff=3570
Blackbird/Firmware
2021-10-29T18:46:32Z
<p>SiteAdmin: </p>
<hr />
<div>= Blackbird Official Firmware Builds =<br />
<br />
For upgrade instructions, please visit the [[Firmware_Upgrade_Quickstart|Firmware Upgrade Quick Start]] page. Alternatively, for those wishing to build from source, please visit the [[Blackbird/Compiling_Firmware|Compiling Firmware]] page.<br />
<br />
All firmware builds are cryptographically signed with the current Raptor Computing Systems firmware signing key at time of release [https://raptorcs.com/verification/gpg/blackbird/firmware_builds/]. The intermediate firmware signer keys, in turn, are signed by our master umbrella key [https://raptorcs.com/keys/gpg/0x337BF51F.pub].<br />
<br />
== System Package v2.00a ==<br />
Released: 10-29-2021<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00a/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00-bundle.tar|7cbe7a8d60a255a94c27138162a03e743df6c9c5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.02.rom|2b48243d7c404f3841f9ebe45aed9c3bee09ebe2]]<br />
<br />
== System Package v2.00 ==<br />
Released: 02-19-2020<BR><br />
[https://wiki.raptorcs.com/wiki/Blackbird/Firmware/2.00/Release_Notes Release Notes]<br />
* BMC: [[:File:Blackbird-openbmc-v2.00-bundle.tar|18878e4f6250fdad538c7af3dabf90fd526e9264]]<br />
* PNOR: [[:File:Blackbird-pnor-v2.00-bundle.tar|7cbe7a8d60a255a94c27138162a03e743df6c9c5]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.01.rom|9ddbe70ea5e85466c1e24da927b135e62810c93f]]<br />
<br />
== System Package v1.00 ==<br />
Released: 05-22-2019<br />
* BMC: [[:File:Blackbird_openbmc_v1.00_bundle.tar.bz2|eb50c3fe9fc09aec6f874946362642bbd73a6955]]<br />
* PNOR: [[:File:Blackbird_host_pnor_v1.00.bin.bz2|3fe7beacf0ced330b2fdd5302c5f48f7458e98c3]]<br />
* FPGA: [[:File:Blackbird-system-fpga-v1.00.rom|32784cea6d7b9fac9871e9d3909d4b7ac199a7f6]]<br />
<br />
Change Log<br />
* Initial release<br />
<br />
Known Issues<br />
* DRAM is capped to 2400MHz. This is not a hardware problem, it is an issue somewhere in hostboot that is being actively worked. 2666MHz DIMMs installed will function at 2400MHz pending a PNOR update to enable 2666MHz support.<br />
* The BMC kernel (incorrectly) detects an SPI master collision on bus 12, yielding a never ending stream of warnings from the i2c core. As this is not a trivial fix given the state of the ASpeed i2c drivers, and the spew is mostly harmless, the decision was made to ship anyway instead of incurring a lengthy delay to rewrite the drivers. If console access to the BMC is desired over serial, "dmesg -n 1" after login will silence the warnings on the console. This issue will be fixed in a future BMC firmware update.<br />
<br />
[[Category:Blackbird_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Blackbird-system-fpga-v1.02.rom&diff=3569
File:Blackbird-system-fpga-v1.02.rom
2021-10-29T18:45:32Z
<p>SiteAdmin: </p>
<hr />
<div>== Summary ==<br />
Built from https://git.raptorcs.com/git/blackbird-system-fpga/tag/?h=v1.02<br />
<br />
[[Category:Blackbird_Firmware]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Blackbird-system-fpga-v1.02.rom&diff=3568
File:Blackbird-system-fpga-v1.02.rom
2021-10-29T18:44:03Z
<p>SiteAdmin: Built from https://git.raptorcs.com/git/blackbird-system-fpga/tag/?h=v1.02</p>
<hr />
<div>== Summary ==<br />
Built from https://git.raptorcs.com/git/blackbird-system-fpga/tag/?h=v1.02</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Kestrel_Demo_OCP_Virtual_2021.webm&diff=3567
File:Kestrel Demo OCP Virtual 2021.webm
2021-10-26T01:15:19Z
<p>SiteAdmin: </p>
<hr />
<div></div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=BCM5719&diff=3472
BCM5719
2021-05-16T00:17:14Z
<p>SiteAdmin: </p>
<hr />
<div>==Overview==<br />
<br />
The BCM5719 is the [[NIC|NIC]] integrated into the [[Talos_II|Talos™ II]] and [[Blackbird|Blackbird™]] systems. It is based on the wildly popular NetXtreme architecture, and there have been efforts to document the internal operation of devices based on that architecture.<br />
<br />
All Raptor systems shipped after May 10, 2021 use the open-source Ortega firmware for the BCM5719 device.<br />
<br />
The BCM5719 also connects to the BMC via RGMII NC-SI, providing network connectivity to the BMC.<br />
<br />
==Details==<br />
On board EEPROM layout (note: may change as understanding of EEPROM file system evolves)<br />
{| class="wikitable sortable"<br />
! style="text-align:left;"| Offset<br />
! style="text-align:left;"| Length<br />
! style="text-align:left;"| Data<br />
! style="text-align:left;"| CRC Protected<br />
|-<br />
|0x7e<br />
|6<br />
|MAC Address (port 0)<br />
|NO<br />
|-<br />
|0xce<br />
|6<br />
|MAC Address (port 1)<br />
|NO<br />
|-<br />
|0x20a<br />
|6<br />
|MAC Address (port 2)<br />
|NO<br />
|-<br />
|0x25a<br />
|6<br />
|MAC Address (port 3)<br />
|NO<br />
|}<br />
<br />
==Resources==<br />
* [https://git.raptorcs.com/git/bcm5719-ortega/ Official Ortega firmware shipped on Raptor systems]<br />
* [https://docs.broadcom.com/docs-and-downloads/collateral/pg/5718-PG107-R.pdf Register manual]<br />
* [[:File:Bcm5719_talos.bin|Proprietary Broadcom firmware image]] for recovery of bricked [[Talos_II|Talos™ II]] on-board NICs. This image is considered deprecated by Raptor, and Raptor strongly recommends the use of the open-source Ortega firmware instead of the proprietary Broadcom firmware. Note that the two MAC addresses inside this image '''must''' be changed to match the MAC addresses on your particular [[Talos_II|Talos™ II]] system; failure to do so could potentially cause serious network issues, including harm to other computers and/or users on any network(s) attached to the Broadcom network ports.<br />
* Reverse engineering work by Guillaume Delugré<br />
** [https://static.raptorcs.com/TALOSII/contest_files/10-hack.lu-nicreverse_slides.pdf Slides] from initial presentation by Guillaume Delugré at HACK.LU 2010<br />
** [https://infocon.org/cons/Hack%20In%20The%20Box/HITB%202011%20-%20Malaysia/D2T3%20-%20Guillaume%20Delugre%20-%20Reverse%20Engineering%20Broadcom%20NetExtreme%20Firmware.pdf Slides] from second presentation of Guillaume Delugré's talk at HITB Malaysia 2011<br />
** [http://esec-lab.sogeti.com/static/publications/11-recon-nicreverse_slides.pdf Slides] and [https://infocon.org/cons/REcon/REcon%202011/14_Guillaume_Delugre.mp4 Audio] from [https://recon.cx/2011/schedule/events/120.en.html followup presentation] by Guillaume Delugré for Recon 2011 (Video in file is broken)]<br />
* '''[[Project Ortega]]''' &mdash; firmware reverse engineering project<br />
* [https://github.com/meklort/bcm5719-fw/ meklort/bcm5719-fw] - firmware reimplementation (BSD licensed)<br />
<br />
==References==<br />
<br />
[[Category:Mainboard Components]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=BCM5719&diff=3470
BCM5719
2021-05-16T00:15:46Z
<p>SiteAdmin: </p>
<hr />
<div>==Overview==<br />
<br />
The BCM5719 is the [[NIC|NIC]] integrated into the [[Talos_II|Talos™ II]] and [[Blackbird|Blackbird™]] systems. It is based on the wildly popular NetXtreme architecture, and there have been efforts to document the internal operation of devices based on that architecture.<br />
<br />
As the BCM5719 is the only on-board device on the non-SAS [[Talos_II|Talos™ II]] variants to use proprietary firmware, Raptor Computing Systems has started a contest to see who can create a truly libre replacement firmware<ref>https://www.raptorcs.com/TALOSII/nic_fw_contest.php</ref>. Anyone with the appropriate skill set is encouraged to take up the challenge, and contributions to this page as the device is analyzed in detail are welcomed.<br />
<br />
While the BCM5719 does, at least for now, execute proprietary firmware it is prevented from corrupting the operating system and/or other protected memory regions via the system IOMMU<ref>https://mail.coreboot.org/pipermail/coreboot/2017-September/085048.html</ref>.<br />
<br />
The BCM5719 also connects to the BMC via RGMII NC-SI, providing network connectivity to the BMC.<br />
<br />
==Details==<br />
On board EEPROM layout (note: may change as understanding of EEPROM file system evolves)<br />
{| class="wikitable sortable"<br />
! style="text-align:left;"| Offset<br />
! style="text-align:left;"| Length<br />
! style="text-align:left;"| Data<br />
! style="text-align:left;"| CRC Protected<br />
|-<br />
|0x7e<br />
|6<br />
|MAC Address (port 0)<br />
|NO<br />
|-<br />
|0xce<br />
|6<br />
|MAC Address (port 1)<br />
|NO<br />
|-<br />
|0x20a<br />
|6<br />
|MAC Address (port 2)<br />
|NO<br />
|-<br />
|0x25a<br />
|6<br />
|MAC Address (port 3)<br />
|NO<br />
|}<br />
<br />
==Resources==<br />
* [https://git.raptorcs.com/git/bcm5719-ortega/ Official Ortega firmware shipped on Raptor systems]<br />
* [https://docs.broadcom.com/docs-and-downloads/collateral/pg/5718-PG107-R.pdf Register manual]<br />
* [[:File:Bcm5719_talos.bin|Proprietary Broadcom firmware image]] for recovery of bricked [[Talos_II|Talos™ II]] on-board NICs. This image is considered deprecated by Raptor, and Raptor strongly recommends the use of the open-source Ortega firmware instead of the proprietary Broadcom firmware. Note that the two MAC addresses inside this image '''must''' be changed to match the MAC addresses on your particular [[Talos_II|Talos™ II]] system; failure to do so could potentially cause serious network issues, including harm to other computers and/or users on any network(s) attached to the Broadcom network ports.<br />
* Reverse engineering work by Guillaume Delugré<br />
** [https://static.raptorcs.com/TALOSII/contest_files/10-hack.lu-nicreverse_slides.pdf Slides] from initial presentation by Guillaume Delugré at HACK.LU 2010<br />
** [https://infocon.org/cons/Hack%20In%20The%20Box/HITB%202011%20-%20Malaysia/D2T3%20-%20Guillaume%20Delugre%20-%20Reverse%20Engineering%20Broadcom%20NetExtreme%20Firmware.pdf Slides] from second presentation of Guillaume Delugré's talk at HITB Malaysia 2011<br />
** [http://esec-lab.sogeti.com/static/publications/11-recon-nicreverse_slides.pdf Slides] and [https://infocon.org/cons/REcon/REcon%202011/14_Guillaume_Delugre.mp4 Audio] from [https://recon.cx/2011/schedule/events/120.en.html followup presentation] by Guillaume Delugré for Recon 2011 (Video in file is broken)]<br />
* '''[[Project Ortega]]''' &mdash; firmware reverse engineering project<br />
* [https://github.com/meklort/bcm5719-fw/ meklort/bcm5719-fw] - firmware reimplementation (BSD licensed)<br />
<br />
==References==<br />
<br />
[[Category:Mainboard Components]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Category:Documentation&diff=3460
Category:Documentation
2021-04-14T21:54:56Z
<p>SiteAdmin: </p>
<hr />
<div>The following documentation is available:<br />
<br />
* [[Talos II]] specific documentation:<br />
** [[:File:T2P9D01_users_guide_version_1_0.pdf|Talos II User's Guide]]<br />
** [[:File:Talos ii.dts|Example Talos II device tree]]<br />
* [[Blackbird]] specific documentation:<br />
** [[:File:C1P9S01_users_guide_version_1_0.pdf|Blackbird User's Guide]]<br />
* [[POWER9]] specific documentation:<br />
** User-level documentation<br />
*** [[:File:POWER9-Features-and-Specifications.pdf|Introduction to POWER9 Features and Specifications]]<br />
*** [[:File:POWER9 um OpenPOWER v21 10OCT2019 pub.pdf|POWER9 User Manual v21]] (old versions: [[:File:POWER9_um_OpenPOWER_v20GA_09APR2018_pub.pdf|v20GA]])<br />
*** [[:File:POWER9_PMU_UG_v12_28NOV2018_pub.pdf|POWER9 Performance Monitoring Unit User Guide v12]]<br />
** Operating System-level documentation<br />
*** [[:File:IPL-Flow-POWER9.pdf|POWER9 IPL/Bootstrap Process Documentation]]<br />
** Low-level documentation<br />
*** [[:File:POWER9_Sforza_DS_v18_13JUN2019_pub.pdf|POWER9 Sforza Datasheet v18]] (old versions: [[:File:POWER9_Sforza_DS_v16_23JUL2018_pub.pdf|v16]])<br />
*** [[:File:POWER9_LaGrange_ds_v17_28MAR2019_pub.pdf|POWER9 LaGrange Datasheet v17]]<br />
*** [[:File:POWER9 errata dd2.2 v1.2 19APR2019 pub.pdf|POWER9 DD2.2 Errata]]<br />
*** [[:File:POWER9 Processor Programming Model Bulletin 090919.pdf|POWER9 DD2.1 Use Restrictions]]<br />
*** [[:File:POWER9_Registers_vol1_version1.2_pub.pdf|POWER9 Registers Vol. 1 v1.2]]<br />
*** [[:File:POWER9_Registers_vol2_version1.2_pub.pdf|POWER9 Registers Vol. 2 v1.2]]<br />
*** [[:File:POWER9_Registers_vol3_version1.2_pub.pdf|POWER9 Registers Vol. 3 v1.3]]<br />
*** [[:File:405 um.pdf|PPC405 User Manual]] (used for the [[OCC]])<br />
*** PCIe controller documentation:<br />
**** [[:File:POWER9_PCIe_controller_v11_27JUL2018_pub.pdf|PCIe controller v11 Documentation]]<br />
**** [[:File:P9_PHB_version1.0_27July2018_pub.pdf|PHB v1.0.27 Documentation]]<br />
* General POWER documentation:<br />
** ISA Documentation:<br />
*** [[:File:PowerISA_public.v3.0B.pdf|ISA Specification v3.0B]] (implemented by [[POWER9]])<br />
*** [[:File:PowerISA_V2.07B.pdf|ISA Specification v2.07B]] (implemented by [[POWER8]])<br />
*** [[:File:POWER9 Processor Programming Model Bulletin 090919.pdf|Ultravisor ISA Extensions for POWER9]]<br />
*** [[Power ISA|Other versions]]<br />
** ABI Documentation:<br />
*** [[:File:Leabi-20170510.pdf|&#8220;ELFv2&#8221; 64-bit ABI]]<br />
*** [[:File:Power-Arch-32-bit-ABI-supp-1.0-Unified.pdf|32-bit ABI v1.0]]<br />
** Platform Documentation:<br />
*** [[:File:LoPAPR_DRAFT_v11_24March2016_cmt1.pdf|LoPAPR v1.1]] (VM-level platform documentation)<br />
*** [[:File:Power_ePAPR_APPROVED_v1.1.pdf|ePAPR v1.1 Specification]] (embedded platform specification)<br />
*** [[:File:IODA2WGSpec-1.0.0-20160217.pdf|I/O Design Architecture v2 v1.0.0]] (IOMMU specification)<br />
*** [[:File:OpenFSI-spec-20161212.pdf|OpenFSI Specification]] ([[FSI]] bus protocol)<br />
<br />
* See also:<br />
** [https://openpowerfoundation.org/technical/resource-catalog/ OpenPOWER Resource Catalog]<br />
** [https://www-355.ibm.com/systems/power/openpower/ IBM Portal for OpenPOWER]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:POWER9_Registers_vol1_version1.2_pub.pdf&diff=3459
File:POWER9 Registers vol1 version1.2 pub.pdf
2021-04-14T21:45:19Z
<p>SiteAdmin: POWER9 Processor Register Guide Volume 1
https://ibm.ent.box.com/s/kvh7vfckzgowzkecyhrtm7fyuz2la4ua
Licensing:
Copyright © 2021 IBM, All Rights Reserved<BR>
No restrictions placed on unmodified redistribution or publication
Category:Documentation</p>
<hr />
<div>== Summary ==<br />
POWER9 Processor Register Guide Volume 1<br />
<br />
https://ibm.ent.box.com/s/kvh7vfckzgowzkecyhrtm7fyuz2la4ua<br />
<br />
Licensing:<br />
Copyright © 2021 IBM, All Rights Reserved<BR><br />
No restrictions placed on unmodified redistribution or publication<br />
<br />
[[Category:Documentation]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Promo_sheet_3.pdf&diff=3239
File:Promo sheet 3.pdf
2020-05-14T19:38:48Z
<p>SiteAdmin: </p>
<hr />
<div></div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Verifying_DVDs&diff=3151
Verifying DVDs
2020-03-30T19:10:47Z
<p>SiteAdmin: Fix order of arguments in GPG verify command</p>
<hr />
<div><br />
= Verification of Recovery and Software DVDs =<br />
<br />
Raptor Computing Systems signs their source DVD images with a publicly available Firmware Signing GPG key. Verification of DVD contents is strongly recommended to ensure you have received an authentic copy of the software and information contained thereon. Shipments of the Talos II systems include both the source DVD and a letter with a QR Code containing the 40-character PGP Key Fingerprint of the firmware signing key, and a link to where the detached digital signature can be found. <br />
<br />
Digital signatures offer sender authentication (a guarantee of who sent the message) as well as provide message integrity (a guarantee that the message has not been altered since the sender authorized it), on one crucial, pivotal condition: that the key itself can be verified to actually belong to who it purports to belong to. If this condition is not met, an adversary could simply change the keys and replace the signatures on a counterfeit disk with one of their own, then impersonate the sender to recipient or vice-versa.<br />
<br />
PGP was originally designed with the implicit assumption that the sender and recipient would either be able to meet each other in person to determine the validity of their keys, or would know "trusted introducers" that they believed to be trustworthy that could do so on their behalf through the use of the PGP "Web Of Trust". This "Web Of Trust" model is impractical when the sender and recipient do not know each other and are not in a position where they could meet in person or have any trusted friends in common. <br />
<br />
As an alternative to this, Raptor has included a letter marked "Important Information" that is included with all Talos IIs. This letter contains a QR code which encodes the PGP key fingerprint of the key used to sign the firmware. The QR code is marked with Raptor Computing System's logo and should be on the opposite side of the letter. When scanned with any QR Code reading application, it will contain the 40-character plain text hexadecimal SHA-1 fingerprint used to uniquely prove the key's uniqueness. Please note that this format is not compatible with Android OpenKeyChain's "Scan From QR Code" function, and simply gives the raw 40-character fingerprint without spaces or comma separation. <br />
<br />
This forms something of a chain of trust that looks like the following:<br />
<br />
* You and the message you wish to verify, in this case Raptor's DVD;<br />
* Genuineness of the message attested by the Digital Signature;<br />
* Production of the Digital Signature using the Firmware Signing Key or by a Sales Key;<br />
* Validation of the Firmware Signing Key by the Umbrella Signing Key;<br />
* Security of where the Secret Key for Raptor's Umbrella Signing Key and cryptographic materials are stored. <br />
* Verification of the Hash of the Signing Key via the QR Code included in Raptor's "Important Information" Letter. <br />
<br />
The theory behind this chain of trust is simple: Raptor is a large company and may require many different keys to be used for different reasons and different jobs. Rather than needing to verify many different keys out of band for everything manually, instead Raptor can generate one key that represents them, and digitally certifies all the keys that they use, then keep that one special umbrella signing key in an ultra-secure place. Users that wish to verify that a key really does belong to Raptor then only need to verify that one key at the end of the chain of trust, and if they trust it, all the keys that it validates may be assumed to actually belong to Raptor. This approach provides separation of duties by keeping different keys for different jobs, some amount of convenience by ensuring users only need to verify one key, and ensures that the Umbrella Key does not need to be entrusted to many different people. In turn, keeping the number of people who need to be trusted with the key reduces the likelihood that someone may mishandle it and allow it to leak. As a side-benefit, in the event that one of the keys it certified is stolen, Raptor can simply use the Umbrella key to revoke its certification to inform other people that the key has been compromised and is no longer valid, without having to start over from scratch with entirely new credentials and force everyone to go through the entire exercise of verifying all of the keys all again. <br />
<br />
The detached digital signature files produced by the signing keys are available on Raptor's Website. Copies of the public keys may then be obtained from an untrusted source, such as via the outside, untrusted internet, as long as the Key Fingerprint matches and the package has not been disturbed or surreptitiously modified while in transit. <br />
<br />
==The Process Explained==<br />
<br />
What we will do:<br />
* We will first copy the CD image to someplace on your drive on your secure, trustworthy computer. Because signing and verification only works if the copying is exact, we will use the Unix utility "data definition" to do it after finding out the information on the image. <br />
* Once the drive is copied, we will scan the letter for its QR codes to obtain the PGP Key Fingerprints for the respective keys and copy them down.<br />
* With the PGP key fingerprints scanned, we will then retrieve the keys from Raptor's website or from a PGP Public Key server of our choice via the Internet.<br />
* We will then validate the Chain of Trust (see: Chain Of Trust, Section 2) to ensure that the key is genuine and valid, and opt to trust the key. <br />
* Once the chain of trust is valid, we will verify the digital signature on the CD image. If GnuPG verifies that the signature is valid and from a trusted key, we can be reasonably confident that Raptor authorized the sending of the CD image, and it has not been modified since.<br />
<br />
In order to do it, you will need the following tools: <br />
* The ''isoinfo'' software package. This is a handy little utility which will print the image about a CD you will need to properly copy the disk in a condition where it will be in the exact condition that it was burned. isoinfo is included in the package manager of most Linux distributions. <br />
* The ''curl'' software application is highly recommended, but not essential. This utility is used to retrieve files from the Internet, <br />
* GnuPG, which is usually invoked from the commandline with the command <code>gpg</code>. By default, almost every Linux distribution should have GnuPG which provides the necessary functions for maintaining the PGP Public Key Infrastructure. <br />
* The letter marked "Important Information" that came in the box with your Talos II. This should have three QR codes on it, one at the front, and two at the back. <br />
* A computer system that you can trust to verify the integrity of the Talos. This could range from a simple computer that you believe to be reasonably trustworthy, an X60 Thinkpad Laptop from 2005 running coreboot or an X200 Laptop running Libreboot, another Talos II, or an elabourate setup consisting of multiple trustworthy computers that are physically separate from each other, including one which may have been purchased from a randomly selected brick-and-mortar store anonymously, paid in cash, running its operating system from a LiveCD verified on multiple different computers and never connected to any network to perform the verification nor used prior to this point.<br />
* An Internet connection. <br />
* A device that is capable of scanning QR codes that you trust. This could be an old Samsung Galaxy S2 running Replicant that has had cellular and wifi antennas physically removed from the phone to prevent compromise of the phone's baseband.<br />
<br />
More information on GnuPG is available at the GnuPG Project Manual[https://www.gnupg.org/gph/en/manual.html].<br />
<br />
==The Steps Detailed==<br />
<br />
===Deterministic Copying Of The Disk===<br />
When the cd image was signed by Raptor, it was signed in a specific condition. You will need to reproduce this condition exactly right down to the last bit, or the verification will fail and produce a "Bad Signature" error. To do so, we will first need to obtain the information about the drive to supply the right parameters to copy the drive. <br />
<br />
<br />
'''Heads-up!''' If you get an error that says <code>isoinfo: command not found</code> then the correct package has not been installed on your system. If you do not have it, on Debian-based systems such as Ubuntu or Linux Mint, you may obtain them with the command <code>sudo apt install genisoimage</code> which should automatically download and install isoinfo and its dependencies on your system.<br />
<br />
<br />
This tutorial assumes that your cd rom device entry is listed as <code>/dev/cdrom</code>. However, some systems may not have the symbolic link of /dev/cdrom to /dev/sr0. You may check to see which device entry your DVD or BD ROM is by inserting the disk, and typing without any other arguments <code>mount | grep udf</code> which will display all the device entries associated with handling the currently inserted disks. The device entry will be the first entry listed, for example: <br />
<br />
<pre>user@computer:~$ mount | grep udf<br />
/dev/sr0 on /media/cdrom0 type udf </pre><br />
<br />
In this tutorial, we will use /dev/sr0.<br />
<br />
We will be looking for two specific items here: Logical Block Size, and Volume Size, which will become parameters will then pass on to Data Definition. To make this easier for the end user, we can use grep to search through the entire output text and only print the information we want with the following command <br />
This should return two lines, one number representing logical block size, and the other number representing the volume block size.<br />
<br />
<pre>user@computer:~$ isoinfo -d -i /dev/sr0 | grep -E 'Logical block size|Volume size'<br />
Logical block size is: 2048<br />
Volume size is: 4135453</pre><br />
<br />
Alternatively, you can use the command <code>isosize</code>:<br />
<br />
<pre>user@computer:~$ isosize -x /dev/sr0<br />
sector count: 4135453, sector size: 2048<br />
</pre><br />
<br />
'''STOP!''' Do not simply enter the values obtained on the Wiki blindly. The values for Logical Block Size and Volume size shown here are listed as being for example only, and may change depending on which version of the disk you were supplied with. Always double check your command syntax prior to entering it. Each person's system will be slightly different, so ensure you do what is right for your system, not just what is listed on the wiki page. <br />
<br />
With this information now known, we will now begin deterministing copying of the CD via the data definition (or define data) tool, <code>dd</code>. dd is a utility that has been a part of all Unix-like operating systems since approximately 1985. dd mainly utilizes two parameters, the input file, which is specified by "if", and the output file specified by "of", and will bitwise copy from the input file to the output file, along with any parameters we want to set, such as the block size, and the volume size. We will then set the parameters as such:<br />
*Input file, or <code>if=</code> The input file should be the device entry for your CD ROM, which we obtained earlier by searching for the mounted media of the type "udf". In our example, we are using /dev/sr0<br />
*Output file, or <code>of=</code> The output file is the clone we will copy to the disk to verify. Here, we will put it in your home directory, with the filename "raptordisk.iso" or the absolute filename "~/raptordisk.iso"<br />
*Block Size or <code>bs=</code> The block size will be the number indicated by "Logical block size" as given by isoinfo.<br />
*Volume Size, or <code>count=</code>The volume size is the exact size of the entire volume, in the number of blocks. <br />
For our example, our command syntax will be the following. To include a progress meter, simply include "status=progress" to let the computer know you wish to view the progress of the copy being made in real time. This will produce an exact clone of the disk to your home directory under the name "raptordisk.iso".<br />
<br />
<br />
<pre>dd if="/dev/sr0" of="~/raptordisk.iso" count=4135453 bs=2048 status=progress</pre><br />
<br />
<br />
'''STOP!''' dd is a powerful tool intended for low-level, bitwise copying of the actual ones and zeroes on the disk or media. The dd command is intended to restore backups and make exact clones of data, but can also be repurposed for secure erasure of hard drives. With great power comes great responsibility: ensure that the input file and output file denoted by <code>if=</code> and <code>of=</code> respectively are the files you really want to write. Never specify an output file to one you do not intend to overwrite! <br />
<br />
If all has been done correctly, this will procedure should create a bit-wise (exact) clone of the disk image in your home directory, which will be called "raptordisk.iso." We will verify this clone shortly.<br />
<br />
===Obtaining and Trusting the Umbrella Signer Public Key===<br />
<br />
To obtain the Umbrella Signing Public Key, you may use the url included on the letter, which is also given as a QR-code that may be scanned by any QR-code reading software or by visiting the url below it. Although the download is made over Transport Layer Security (or SSL), the key should first be verified locally on your computer against the 40-character fingerprint obtained by scanning the QR code in the letter. To do this, we will check the key fingerprint of the key we receive <br />
<br />
The public key will be available in ascii-armoured format and will be marked to note where the public key begins and ends. If your browser does not automatically download it, you may copy the page to your hard drive using wget or curl, and pass it to GnuPG with the following terminal command sequence. Note that if the url you receive on your letter is different from the one you see here, '''take the one on the letter to be correct.''' <br />
<br />
If you do not have curl, you may install it using the command <code>sudo apt install -y curl </code>.<br />
<br />
<pre> user@computer:~$ curl https://www.raptorcs.com/keys/gpg/0x337BF51F.pub | gpg --import </pre><br />
<br />
You may see a screen that resembles something like this. (Please note that in this manual entry, the key fingerprint itself has been obscured to prevent confusion)<br />
<br />
<pre><br />
pub rsa4096/████████████ created: 2018-04-16 expires: never<br />
Key fingerprint = ████ ████ ████ ████ ████ ████ ████ ████ ████ ████<br />
<br />
Raptor Computing Systems Primary Signer (Umbrella Signer) <authentication@raptorcs.com><br />
<br />
Do you want to import this key? (y/N)</pre><br />
<br />
Compare this result displayed on your computer to the 40-character key fingerprint you obtained from scanning the QR-Code reader. It must match '''exactly''' to avoid obtaining a counterfeit key. If the 40-character key fingerprint matches exactly, you can sign it locally with one of your own keys, or you can take ownership of the key by setting its trust to ultimate. <br />
<br />
If you miss this information the first time around, you may view it again with the command:<br />
<br />
<pre> user@computer:~$ gpg -k authentication@raptorcs.com --with-fingerprint</pre><br />
<br />
First, we will edit the key with: <br />
<br />
'''Heads Up!''' This tutorial assumes you have no ultimately trusted keys in your GnuPG trust database. The "Ultimate" trust level in GnuPG is intended for keys you own, and is required to validate other keys. Setting ultimate trust for a key you do not own is normally a very harmful use case, as an ultimately trusted key that you do not own can be used to issue counterfeit keys for your contacts and impersonate your contacts to you unless you decide to stop trusting it. After the key is no longer needed to be trusted, you should un-set its trust from Ultimate. You can avoid using these issues by locally signing Raptor's Umbrella key with an ultimately trusted key that ''you'' own using <code> gpg --lsign-key</code>.<br />
<br />
<pre> user@computer:~$ gpg --edit-key 0x337BF51F</pre><br />
<br />
This will bring us to the gpg> key editing dialogue.<br />
<pre> <br />
pub rsa4096/9B2BF5BD337BF51F<br />
created: 2018-04-16 expires: never usage: SC <br />
trust: unknown validity: unknown<br />
sub rsa4096/366FA0E6B8EE80D8<br />
created: 2018-04-16 expires: never usage: E <br />
[ unknown] (1). Raptor Computing Systems Primary Signer (Umbrella Signer) <authentication@raptorcs.com><br />
<br />
gpg> </pre><br />
<br />
At the prompt, type <code>trust</code> and press return to bring up the trust dialogue, allowing you to tell the computer how much you trust the user of this key to cryptographically attest to the validity of other keys. <br />
<br />
<pre>gpg> trust</pre><br />
<br />
This will return the trust dialogue. If we do not have a key of our own to validate to its ownership, we will need to take ownership of it ourselves and pretend it is ours for the moment by setting it to ultimate trust. <br />
<br />
<pre>Please decide how far you trust this user to correctly verify other users' keys<br />
(by looking at passports, checking fingerprints from different sources, etc.)<br />
<br />
1 = I don't know or won't say<br />
2 = I do NOT trust<br />
3 = I trust marginally<br />
4 = I trust fully<br />
5 = I trust ultimately<br />
m = back to the main menu<br />
<br />
Your decision? </pre><br />
<br />
Enter <code>5</code> for ultimate and press return.<br />
<br />
<pre>Please note that the shown key validity is not necessarily correct<br />
unless you restart the program.<br />
<br />
gpg> </pre><br />
<br />
Type <code>quit</code> and press return, which should send you back to your terminal shell. We can verify that the command worked using <code> gpg -k --with-fingerprint authentication@raptorcs.com</code> to check. <br />
<br />
<pre>pub rsa4096/9B2BF5BD337BF51F 2018-04-16 [SC]<br />
Key fingerprint = 9C2A 6E8F AEA7 EE92 1EFD 4891 9B2B F5BD 337B F51F<br />
uid [ultimate] Raptor Computing Systems Primary Signer (Umbrella Signer) <authentication@raptorcs.com><br />
sub rsa4096/366FA0E6B8EE80D8 2018-04-16 [E]<br />
Key fingerprint = 83DA 26B4 FAC2 2215 832B 8894 366F A0E6 B8EE 80D8</pre><br />
Notice next to UID, the <code>[ unknown]</code> marker has been replaced to <code>[ultimate]</code>. The computer now trusts this key and its owner to be valid to the point where it will consider ''any'' keys that this key has certified to be fully valid as being verified to belong to who they really say they belong to, as long as this key itself is. <br />
<br />
<br />
===Retrieving the Detached Digital Signature===<br />
Retrieving the detached digital signature is simple, by either visiting the url shown below the QR code on the ''front'' of the Important Information letter, or by simply using <code>curl</code> to retrieve the detached digital signature file in the same manner the public key was retrieved. The command to do so should be similar to the following. Note that the version number of the command has been obscured. '''To determine the version of your recovery disk, look at the url on the letter.''' <br />
<br />
<pre> user@computer:~$ curl https://www.raptorcs.com/verification/gpg/talos_ii/recovery_disks/talos_recovery_disk_v████.iso.asc</pre><br />
<br />
This should download the detached signature file to your computer. <br />
<br />
===Retrieving The Firmware Signing Key===<br />
The digital signature file and the Root Umbrella key however are not everything we need to verify the integrity of the disk. Attempting to verify the disk (more on that later) will yield the following error:<br />
<br />
<pre>gpg: Signature made Tue 19 Jun 2018 06:05:04 PM EDT<br />
gpg: using RSA key 101A7EF8EF283DDC<br />
gpg: key 101A7EF8EF283DDC: 1 signature not checked due to a missing key<br />
</pre><br />
<br />
This error message is simple: the signature was generated by an RSA key with the particular long key ID shown, but you do not have that public key in your keyring to verify the signature with. Two options present themselves:<br />
* If you have GnuPG configured to connect to the internet, you may get GnuPG to automatically connect to the Internet and fetch the missing key with the command below. '''If done without the aid of anonymizing proxy such as Tor, this approach may leak your IP address and your key request to the key server and possibly the rest of the Internet.'''<br />
<pre>user@computer:~$ gpg --recv-keys 101A7EF8EF283DDC</pre><br />
* If you do not have GnuPG configured for automatic key retrieval, you can go onto the PGP Key Server pool, such as to https://pgp.mit.edu and seach via the web user interface by searching for the Long Key ID, copy the text of the key beginning with <code>-----BEGIN PGP PUBLIC KEY BLOCK-----</code> and ending with <code>-----END PGP PUBLIC KEY BLOCK-----</code> into a text file, and import it into your GPG keyring with <code>gpg --import [path to file]</code>.<br />
* If you use a graphical frontend such as Gnu Privacy Assistant or Enigmail on your computer to manage keys, you may copy the keys from the clipboard. <br />
<br />
After the key is imported, you may see a screen similar to this:<br />
<br />
<pre><br />
gpg: key 101A7EF8EF283DDC: public key "Raptor Computing Systems Firmware Signer (2018) (2018 Firmware Signer) <support@raptorcs.com>" imported<br />
gpg: Total number processed: 1<br />
gpg: imported: 1<br />
gpg: marginals needed: 3 completes needed: 1 trust model: pgp<br />
gpg: depth: 0 valid: 9 signed: 5 trust: 0-, 0q, 0n, 0m, 0f, 9u<br />
gpg: depth: 1 valid: 5 signed: 0 trust: 5-, 0q, 0n, 0m, 0f, 0u<br />
gpg: next trustdb check due at 2018-09-09<br />
</pre><br />
<br />
We may then check its validity. If all has gone right, since we chose to trust Raptor's Umbrella signing key "ultimately," should this be the real key, this key will immediately become fully valid thanks to Raptor's digital signature on it. We then check may the command with <code>gpg -k EF283DDC --with-fingerprint</code> and look for the trust level which should be indicated next to the symbol "uid". <br />
<br />
<pre><br />
user@computer:~$ gpg -k EF283DDC --with-fingerprint<br />
pub rsa4096/101A7EF8EF283DDC 2018-04-25 [SC] [expires: 2019-01-20]<br />
Key fingerprint = D7E9 CE35 33F1 938C 6F8E F5FD 101A 7EF8 EF28 3DDC<br />
uid [ full ] Raptor Computing Systems Firmware Signer (2018) (2018 Firmware Signer) <support@raptorcs.com><br />
sub rsa4096/CE591B3C94F3C9EE 2018-04-25 [E] [expires: 2019-01-20]</pre><br />
<br />
Note that it says <code>[ full ]</code> next to the User ID. This indicates that the computer has found the keys as being authentic, as it has verified the chain of trust back to an ultimately trusted key that in the previous steps, we verified to be provably unique and identitical to the one listed on Raptor's letter. Because of this, the computer now considers the firmware signing key to be fully valid. We may now attempt to verify the DVD image with GnuPG. <br />
<br />
'''WARNING!''' If the text in the brackets lists anything aside from <code>[ full ]</code>, '''STOP IMMEDIATELY''' as the key has not validated. A failure for the key to validate may signify something benign, such as either obtaining the wrong key, or worse, a counterfeit. Note that Raptor maintains several keys: some are used for different projects, some are used for customer correspondence, and some are used for signing their [[Warrant Canary]], all of which should be signed by the Umbrella Signer. Ensure you have gotten the one that is used for signing the firmware. <br />
<br />
===Verifying The Disk===<br />
With the chain of trust intact and the detached digital signature and a bitwise copy of the disk image, you may now verify the digital signature on the recovery and firmware disk. This tutorial assumes that you have saved both the recovery disk and detached digital signature file into your home directory, and named the image of the disk "raptordisk.iso" and the detached signature file "talos_recovery_disk_v████.iso.asc"<br />
<br />
The command syntax to verify a detached signature file is: <code> gpg --verify [path-to-signature-file] [path-to-file-being-verified]</code>. For the purpose of this tutorial, the command is shown below with the version numbers hidden. Since the disk image itself will be as large as the recovery disk is (approximately 8.5GB) this command may take several minutes to complete, and will not display a progress indicator during this time. <br />
<br />
<pre><br />
user@computer:~$ gpg --verify talos_recovery_disk_v████.iso.asc raptordisk.iso<br />
gpg: Signature made Tue 19 Jun 2018 06:05:04 PM EDT<br />
gpg: using RSA key 101A7EF8EF283DDC<br />
gpg: Good signature from "Raptor Computing Systems Firmware Signer (2018) (2018 Firmware Signer) <support@raptorcs.com>" [full]<br />
Primary key fingerprint: D7E9 CE35 33F1 938C 6F8E F5FD 101A 7EF8 EF28 3DDC<br />
</pre><br />
<br />
If you see <code>Good Signature</code>, congratulations. The chain of trust has been verified to an ultimately trusted key, which has been compared to a tracked and insured letter directly from Raptor. You may wish to further check the validity of the key in other ways, including asking other people you know and trust over an end-to-end authenticated and secure channel to attest to the key fingerprint of the Umbrella Signing Key. Your disk is verified to have come from Raptor, and not been modified since. <br />
<br />
==Troubleshooting==<br />
If you get a <code>Bad Signature</code> warning, this may signify that the disk is no longer in the original condition that Raptor sent it in (and could represent the work of tampering or damage) or may be resultant of much more benign causes, such as selecting the wrong file for validation, or that the disk was not copied properly (a single flipped or extra bit will cause the validation to fail). If you get a Bad Signature error, ensure you have checked the commands properly and copied the disk properly using dd with the exact bit size and count according to the disk properties. This is the most common cause of false positives.<br />
<br />
Prior to sounding an alarm, ensure the following conditions are met:<br />
* You have obtained the correct bit size for the disk and that the disk was copied with the correct bit size and count. <br />
* You have obtained the Firmware signing key, instead of a correspondence key or Canary signing key. <br />
* That the digital signature file is correct to the version of the disk you were supplied with. (Check the letter to be sure)<br />
* That the full 40-character fingerprint matches the one obtained.<br />
* The chain of trust is valid. Only the Umbrella signing key needs to be verified via the QR Code. All keys underneath it should validate automatically from being certified by the Umbrella key. <br />
<br />
If you continue to experience issues, contact the IRC channel on Freenode. The name of the IRC channel on the Freenode IRC network is listed on the bottom of the letter. As Freenode has been under attack by spam lately, you may be required to register a your nickname on Freenode as a part of an antispam measure utilizing an E-mail address.<br />
<br />
=Quick Verification Guide for Advanced Users=<br />
This section contains a quick reference guide for the commands, and omits the rationale and theory. <br />
<br />
'''Please note that this section is in progress and is incomplete.'''<br />
<br />
<br />
Once created, you may verify the ISO with GPG:<br />
<br />
<code>gpg --verify <GPG signature file> source.iso</code><br />
<br />
<br />
'''Verify Without Saving ISO:'''<br />
<br />
<code>gpg --verify talos_recovery_disk_v1.0x.iso.asc <(dd if=/dev/cdrom bs=<block size> count=<volume size>)</code><br />
<br />
<br />
E.g.<br />
<br />
<code>gpg --verify talos_recovery_disk_v1.02.iso.asc <(dd if=/dev/cdrom bs=2048 count=3861982)</code><br />
<br />
<br />
<br />
'''Umbrella Key Fingerprint'''<br />
:Raptor Computing Systems Primary Signer (Umbrella Signer) <authentication@raptorcs.com><br />
:Fingerprint (9C2A 6E8F AEA7 EE92 1EFD 4891 9B2B F5BD 337B F51F) <br />
:(Verify this fingerprint matches multiple independent sources.)<br />
<br /><br />
Additional information on validating public keys:<br />
<br /><br />
[https://www.gnupg.org/gph/en/manual/x334.html The GNU Privacy Handbook: Validating other keys on your public keyring]<br />
<br />
===How To===<br />
====Get Block and Logical Volume Sizes (Needed Later)====<br />
<code>isoinfo -d -i /dev/sr0 | grep -E 'Logical block size|Volume size'</code><br />
<pre><br />
Logical block size is: 2048<br />
Volume size is: 3871504<br />
</pre><br />
<br />
====Save ISO File (Optional)====<br />
:<code>dd if="/dev/sr0" of="source.iso" count='''<volume size>''' bs='''<block size>'''</code><br />
:<code>dd if="/dev/sr0" of="source.iso" count=3871504 bs=2048</code><br />
<br />
====Download Signature File:====<br />
:In this example we will be verifying a v1.03 disc.<br />
:Details may vary for other versions/keys, but they all should lead back to the Raptor Umbrella Signer.<br />
:<code>wget https://www.raptorcs.com/verification/gpg/talos_ii/recovery_disks/talos_recovery_disk_v1.03.iso.asc</code><br />
<br />
====Verifying ISO Signature:====<br />
Verifying ISO file:<br />
:<code>gpg --verify talos_recover_disk_v.103.iso.asc source.iso</code><br />
<br />
Verify without saving ISO (Optional):<br />
:<code>gpg --verify talos_recovery_disk_v1.03.iso.asc <(dd if=/dev/cdrom bs='''<block size>''' count='''<volume size>''')</code><br />
:<code>gpg --verify talos_recovery_disk_v1.03.iso.asc <(dd if=/dev/cdrom bs=<2048> count=<3871504>)</code><br />
<br />
===== If you see this, import the public key and verify again: =====<br />
<pre><br />
gpg: Signature made Mon 30 Apr 2018 04:44:08 PM MDT<br />
gpg: using RSA key 101A7EF8EF283DDC<br />
gpg: Can't check signature: No public key<br />
</pre><br />
<br />
=====Importing a Key (If Applicable)=====<br />
:<code>gpg --recv-keys 101A7EF8EF283DDC</code><br />
<br />
<pre><br />
gpg: key 101A7EF8EF283DDC: public key "Raptor Computing Systems Firmware Signer (2018) (2018 Firmware Signer) <support@raptorcs.com>" imported<br />
gpg: no ultimately trusted keys found<br />
gpg: Total number processed: 1<br />
gpg: imported: 1<br />
</pre><br />
<br />
=====Successful Verification of Signed ISO=====<br />
<pre><br />
gpg: Signature made Mon 30 Apr 2018 04:44:08 PM MDT<br />
gpg: using RSA key 101A7EF8EF283DDC<br />
gpg: Good signature from "Raptor Computing Systems Firmware Signer (2018) (2018 Firmware Signer) <support@raptorcs.com>" [marginal]<br />
gpg: support@raptorcs.com: Verified 1 signature in the past 10 days. Encrypted 0 messages.<br />
...<br />
gpg: It is not certain that the signature belongs to the owner.<br />
Primary key fingerprint: D7E9 CE35 33F1 938C 6F8E F5FD 101A 7EF8 EF28 3DDC<br />
</pre><br />
<br />
=====Verifing Keys=====<br />
We've verified that source.iso was signed by 101A7EF8EF283DDC (2018 Firmware Signer) <support@raptorcs.com>.<br />
<br /><br />
How do we verify that key really belongs to Raptor? <br />
<br /><br />
<code>gpg --list-signatures 101A7EF8EF283DDC</code><br />
<pre><br />
pub rsa4096 2018-04-25 [SC] [expires: 2019-01-20]<br />
D7E9CE3533F1938C6F8EF5FD101A7EF8EF283DDC<br />
uid [marginal] Raptor Computing Systems Firmware Signer (2018) (2018 Firmware Signer) <support@raptorcs.com><br />
sig 3 101A7EF8EF283DDC 2018-04-25 Raptor Computing Systems Firmware Signer (2018) (2018 Firmware Signer) <support@raptorcs.com><br />
sig 9B2BF5BD337BF51F 2018-04-25 Raptor Computing Systems Primary Signer (Umbrella Signer) <authentication@raptorcs.com><br />
sub rsa4096 2018-04-25 [E] [expires: 2019-01-20]<br />
sig 101A7EF8EF283DDC 2018-04-25 Raptor Computing Systems Firmware Signer (2018) (2018 Firmware Signer) <support@raptorcs.com><br />
</pre><br />
101A7EF8EF283DDC was signed by 9B2BF5BD337BF51F<br />
<br /><br />
<code>gpg --fingerprint 9B2BF5BD337BF51F</code><br />
<pre><br />
pub rsa4096 2018-04-16 [SC]<br />
9C2A 6E8F AEA7 EE92 1EFD 4891 9B2B F5BD 337B F51F<br />
uid [marginal] Raptor Computing Systems Primary Signer (Umbrella Signer) <authentication@raptorcs.com><br />
sub rsa4096 2018-04-16 [E]<br />
</pre><br />
<br />
[[Category:Guides]]</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Blackbird-2.01-beta-pnor.tar&diff=3069
File:Blackbird-2.01-beta-pnor.tar
2020-02-23T06:18:19Z
<p>SiteAdmin: Protected "File:Blackbird-2.01-beta-pnor.tar": Beta firmware ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [Upload=Allow only administrators] (indefinite))</p>
<hr />
<div>== Summary ==<br />
BETA 2.01-next PNOR Flash image for Blackbird<br />
<br />
See warnings at https://wiki.raptorcs.com/wiki/Blackbird/Firmware/Public_Beta</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Blackbird/Firmware/2.00/Release_Notes&diff=3068
Blackbird/Firmware/2.00/Release Notes
2020-02-23T06:18:08Z
<p>SiteAdmin: </p>
<hr />
<div>== System Package 2.00 Release Notes ==<br />
<br />
=== BMC ===<br />
<br />
* Our standard ATX products (this includes Talos II and Blackbird) now ship with an easy to use Web GUI installed on the BMC.<br />
** Full support for serial console interaction, iKVM, and remote media is added with this firmware version<br />
** A recent Web browser, such as Ungoogled Chromium for POWER (https://github.com/leo-lb/ungoogled-chromium) is required due to the use of modern Web features. No closed source or proprietary plugins are required to use any of the BMC Web GUI features.<br />
** Earlier methods of interacting with the BMC, including firmware updates over SSH, will continue to be supported across all product lines as they are efficient at scale in larger deployments. The Web GUI is just another way of interacting with the BMC, targeted at individual users and SME.<br />
** The login credentials for SSH and the Web GUI are shared -- changing one will change the other. This makes it easy to change your BMC root password from a Web browser on a second computer if required.<br />
** The Web server will '''not''' respond to <CODE>http://</CODE> requests. You must access it via <CODE>https://</CODE> only.<br />
<br />
* After upgrading from any system firmware package version before 2.00, spurious entries left over from previous firmware versions may show up in the system inventory. You can clear these from the BMC command line, with chassis power '''off''' as follows:<BR><CODE>rm -rf /var/lib/phosphor-inventory-manager/xyz/openbmc_project/inventory/system/chassis</CODE><BR><CODE>reboot</CODE><BR>When the BMC starts back up and the system is powered back on, the inventory will re-populate with correct data.<br />
<br />
=== PNOR ===<br />
<br />
* Supports DD2.3 ("v2") CPUs<br />
* Supports Ultravisor<br />
* Memory VPD updated to improve compatibility with third party RAM DIMMs<br />
* AMD Navi GPU support (with proprietary AMD GPU firmware added to BOOTKERNFW partition)<br />
<br />
=== Known Issues ===<br />
* New BMC cannot IPL old PNOR and vice versa (CANTFIX)<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
* Certain DIMMs may not function in Slot 0. This is '''not''' a defect in the Blackbird planar, it is a memory VPD issue that is being worked by Raptor and the IBM memory team. Future firmware updates are expected to address this problem.<br />
* Upgrading from a BMC that has been manually edited to add or remove users can result in loss of SSH access after the upgrade has completed. The root cause is that <CODE>/etc/passwd</CODE> is retained verbatim across updates if modified, and as a result the new <CODE>sshd</CODE> user is not present in the upgraded firmware environment.<br />
** Prior to upgrading such a BMC, the following line should be added to <CODE>/etc/passwd</CODE> on the BMC:<BR><CODE>sshd:x:996:995::/var/run/sshd:/bin/false</CODE><br />
** Alternatively, the files <CODE>/etc/passwd</CODE> and <CODE>/etc/group</CODE> can be removed immediately before reboot to apply the update. Caution should be used with this method, as failure to apply the update could then result in a requirement to use a BMC serial cable or external SPI flasher to recover.<br />
* Systems with LSI SAS controllers (mpt3sas kernel module) crash in petitboot and are unable to boot the target OS<br />
** WORKAROUND: Use [[:File:Blackbird-2.01-beta-pnor.tar|our current 2.01 Beta PNOR]] instead of the 2.00 release PNOR</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Blackbird/Firmware/Public_Beta&diff=3067
Blackbird/Firmware/Public Beta
2020-02-23T06:17:22Z
<p>SiteAdmin: Created page with "== Public Beta Firmware == === Introduction === From time to time Raptor may make public beta firmware images available. These are normally firmware images that are on a fa..."</p>
<hr />
<div>== Public Beta Firmware ==<br />
<br />
=== Introduction ===<br />
<br />
From time to time Raptor may make public beta firmware images available. These are normally firmware images that are on a fast track to wide GA release, but for which Raptor is seeking public feedback about any issues encountered during upgrades or features missing for daily use.<br />
<br />
'''WARNING''' Beta images have not undergone full release qualification. It is possible that upgrades may fail, leaving your system in a state requiring advanced recovery (e.g. loading a replacement BMC firmware image over TFTP and flashing it via the serial console, or externally writing the BMC Flash device with an SPI programmer). Please do not try the beta firmware images unless you have sufficient recovery tools available.<br />
<br />
=== Current Beta Images ===<br />
==== 2.01-next (04-16-2019 branch) ====<br />
* PNOR: [[:File:Blackbird-2.01-beta-pnor.tar|92ee2568c8e28b6f6449b02380653aa5aeb82284]]<br />
<br />
===== Known Issues =====<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
<br />
===== Regressions =====<br />
* ?<br />
<br />
===== Changelog =====<br />
====== Beta 1 (02-22-2020) ======<br />
* PNOR: Fix crash in petitboot with LSI SAS controllers (mpt3sas module)</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Blackbird-2.01-beta-pnor.tar&diff=3066
File:Blackbird-2.01-beta-pnor.tar
2020-02-23T06:15:51Z
<p>SiteAdmin: == Summary ==
BETA 2.01-next PNOR Flash image for Blackbird
See warnings at https://wiki.raptorcs.com/wiki/Blackbird/Firmware/Public_Beta</p>
<hr />
<div>== Summary ==<br />
BETA 2.01-next PNOR Flash image for Blackbird<br />
<br />
See warnings at https://wiki.raptorcs.com/wiki/Blackbird/Firmware/Public_Beta</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Talos_II/Firmware/2.00/Release_Notes&diff=3064
Talos II/Firmware/2.00/Release Notes
2020-02-23T00:41:38Z
<p>SiteAdmin: </p>
<hr />
<div>== System Package 2.00 Release Notes ==<br />
<br />
=== BMC ===<br />
<br />
* Our standard ATX products (this includes Talos II and Blackbird) now ship with an easy to use Web GUI installed on the BMC.<br />
** Full support for serial console interaction, iKVM, and remote media is added with this firmware version<br />
** A recent Web browser, such as Ungoogled Chromium for POWER (https://github.com/leo-lb/ungoogled-chromium) is required due to the use of modern Web features. No closed source or proprietary plugins are required to use any of the BMC Web GUI features.<br />
** Earlier methods of interacting with the BMC, including firmware updates over SSH, will continue to be supported across all product lines as they are efficient at scale in larger deployments. The Web GUI is just another way of interacting with the BMC, targeted at individual users and SME.<br />
** The login credentials for SSH and the Web GUI are shared -- changing one will change the other. This makes it easy to change your BMC root password from a Web browser on a second computer if required.<br />
** The Web server will '''not''' respond to <CODE>http://</CODE> requests. You must access it via <CODE>https://</CODE> only.<br />
<br />
* After upgrading from any system firmware package version before 2.00, spurious entries left over from previous firmware versions may show up in the system inventory. You can clear these from the BMC command line, with chassis power '''off''' as follows:<BR><CODE>rm -rf /var/lib/phosphor-inventory-manager/xyz/openbmc_project/inventory/system/chassis</CODE><BR><CODE>reboot</CODE><BR>When the BMC starts back up and the system is powered back on, the inventory will re-populate with correct data.<br />
<br />
=== PNOR ===<br />
<br />
* Supports DD2.3 ("v2") CPUs<br />
* Supports Ultravisor<br />
* Memory VPD updated to improve compatibility with third party RAM DIMMs<br />
* AMD Navi GPU support (with proprietary AMD GPU firmware added to BOOTKERNFW partition)<br />
<br />
=== Known Issues ===<br />
* New BMC cannot IPL old PNOR and vice versa (CANTFIX)<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
* Upgrading from a BMC that has been manually edited to add or remove users can result in loss of SSH access after the upgrade has completed. The root cause is that <CODE>/etc/passwd</CODE> is retained verbatim across updates if modified, and as a result the new <CODE>sshd</CODE> user is not present in the upgraded firmware environment.<br />
** Prior to upgrading such a BMC, the following line should be added to <CODE>/etc/passwd</CODE> on the BMC:<BR><CODE>sshd:x:996:995::/var/run/sshd:/bin/false</CODE><br />
** Alternatively, the files <CODE>/etc/passwd</CODE> and <CODE>/etc/group</CODE> can be removed immediately before reboot to apply the update. Caution should be used with this method, as failure to apply the update could then result in a requirement to use a BMC serial cable or external SPI flasher to recover.<br />
* Systems with LSI SAS controllers (mpt3sas kernel module) crash in petitboot and are unable to boot the target OS<br />
** WORKAROUND: Use [[:File:Talos-ii-2.01-beta-pnor.tar|our current 2.01 Beta PNOR]] instead of the 2.00 release PNOR</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Talos_II/Firmware/2.00/Release_Notes&diff=3063
Talos II/Firmware/2.00/Release Notes
2020-02-23T00:41:17Z
<p>SiteAdmin: </p>
<hr />
<div>== System Package 2.00 Release Notes ==<br />
<br />
=== BMC ===<br />
<br />
* Our standard ATX products (this includes Talos II and Blackbird) now ship with an easy to use Web GUI installed on the BMC.<br />
** Full support for serial console interaction, iKVM, and remote media is added with this firmware version<br />
** A recent Web browser, such as Ungoogled Chromium for POWER (https://github.com/leo-lb/ungoogled-chromium) is required due to the use of modern Web features. No closed source or proprietary plugins are required to use any of the BMC Web GUI features.<br />
** Earlier methods of interacting with the BMC, including firmware updates over SSH, will continue to be supported across all product lines as they are efficient at scale in larger deployments. The Web GUI is just another way of interacting with the BMC, targeted at individual users and SME.<br />
** The login credentials for SSH and the Web GUI are shared -- changing one will change the other. This makes it easy to change your BMC root password from a Web browser on a second computer if required.<br />
** The Web server will '''not''' respond to <CODE>http://</CODE> requests. You must access it via <CODE>https://</CODE> only.<br />
<br />
* After upgrading from any system firmware package version before 2.00, spurious entries left over from previous firmware versions may show up in the system inventory. You can clear these from the BMC command line, with chassis power '''off''' as follows:<BR><CODE>rm -rf /var/lib/phosphor-inventory-manager/xyz/openbmc_project/inventory/system/chassis</CODE><BR><CODE>reboot</CODE><BR>When the BMC starts back up and the system is powered back on, the inventory will re-populate with correct data.<br />
<br />
=== PNOR ===<br />
<br />
* Supports DD2.3 ("v2") CPUs<br />
* Supports Ultravisor<br />
* Memory VPD updated to improve compatibility with third party RAM DIMMs<br />
* AMD Navi GPU support (with proprietary AMD GPU firmware added to BOOTKERNFW partition)<br />
<br />
=== Known Issues ===<br />
* New BMC cannot IPL old PNOR and vice versa (CANTFIX)<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
* Upgrading from a BMC that has been manually edited to add or remove users can result in loss of SSH access after the upgrade has completed. The root cause is that <CODE>/etc/passwd</CODE> is retained verbatim across updates if modified, and as a result the new <CODE>sshd</CODE> user is not present in the upgraded firmware environment.<br />
** Prior to upgrading such a BMC, the following line should be added to <CODE>/etc/passwd</CODE> on the BMC:<BR><CODE>sshd:x:996:995::/var/run/sshd:/bin/false</CODE><br />
** Alternatively, the files <CODE>/etc/passwd</CODE> and <CODE>/etc/group</CODE> can be removed immediately before reboot to apply the update. Caution should be used with this method, as failure to apply the update could then result in a requirement to use a BMC serial cable or external SPI flasher to recover.<br />
* Systems with LSI SAS controllers (mpt3sas kernel module) crash in petitboot and are unable to boot the target OS<br />
** WORKAROUND: Use the PNOR at [[:File:Talos-ii-2.01-beta-pnor.tar|our current 2.01 Beta image]] instead of the 2.00 release PNOR</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Talos_II/Firmware/Public_Beta&diff=3062
Talos II/Firmware/Public Beta
2020-02-23T00:39:02Z
<p>SiteAdmin: </p>
<hr />
<div>== Public Beta Firmware ==<br />
<br />
=== Introduction ===<br />
<br />
From time to time Raptor may make public beta firmware images available. These are normally firmware images that are on a fast track to wide GA release, but for which Raptor is seeking public feedback about any issues encountered during upgrades or features missing for daily use.<br />
<br />
'''WARNING''' Beta images have not undergone full release qualification. It is possible that upgrades may fail, leaving your system in a state requiring advanced recovery (e.g. loading a replacement BMC firmware image over TFTP and flashing it via the serial console, or externally writing the BMC Flash device with an SPI programmer). Please do not try the beta firmware images unless you have sufficient recovery tools available.<br />
<br />
=== Current Beta Images ===<br />
==== 2.01-next (04-16-2019 branch) ====<br />
* PNOR: [[:File:Talos-ii-2.01-beta-pnor.tar|5d7b717fceeaa1e7cf45de2938e190cb6e0ed1ee]]<br />
<br />
===== Known Issues =====<br />
* System Package 1.x BMC firmware cannot IPL 2.x or higher PNOR (CANTFIX)<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
<br />
===== Regressions =====<br />
* ?<br />
<br />
===== Changelog =====<br />
====== Beta 1 (02-22-2020) ======<br />
* PNOR: Fix crash in petitboot with LSI SAS controllers (mpt3sas module)<br />
<br />
=== Old Beta Images ===<br />
==== 2.00-next (04-16-2019 branch) ====<br />
* BMC: [[:File:Talos-ii-1.07-beta-bmc.img.bz2|486cbe9701c5c9a811f3342494bcbc392da816e1]]<br />
* PNOR: [[:File:Talos-ii-1.07-beta-pnor.img.bz2|89b3a940b6fef143134b296b0bf15cecf258628c]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.08-beta.rom|f3a97a9a50fb2b53aa39d7687bf36bd21bd21e9d]]<br />
<br />
===== Instructions =====<br />
* Ensure that the BMC and PNOR was previously updated to System Package v1.06, and that that your system successfully boots after that update<br />
* Power down your system<br />
* Issue "reboot" on the BMC<br />
* Transfer the decompressed BMC image file to /run/initramfs/image-bmc on the BMC<br />
* Run "fw_printenv | grep eth1addr" and write down the MAC address. '''You will need this information later'''<br />
* Issue "reboot" on the BMC<br />
* After BMC restart (this may take 5-10 minutes):<br />
** fw_setenv ethaddr <IPMI MAC address written down earlier><br />
** fw_setenv eth1addr <IPMI MAC address written down earlier><br />
* Transfer decompressed PNOR image file to the BMC /tmp directory<br />
** pflash -E -p /tmp/talos.pnor<br />
** pflash -P CVPD -c<br />
<br />
===== Known Issues =====<br />
* New BMC cannot IPL old PNOR and vice versa (CANTFIX)<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
<br />
===== Regressions =====<br />
* ?<br />
<br />
===== Changelog =====<br />
====== Release Candidate 1 (09-20-2019) ======<br />
* FPGA: Fix power off failure on Talos II Lite systems<br />
* PNOR: Fix incorrect voltage slew rate causing random OCC hang in power saving stop states (https://github.com/open-power/occ/issues/26)<br />
* PNOR: Add LUKS encryption userspace utilities to support FDE direct boot<br />
* PNOR: Add basic diagnostic utilities for system check to Petitboot environment<br />
====== Beta 3 (04-28-2019) ======<br />
* PNOR: Add workaround for skiboot hang during Flash access (https://github.com/open-power/skiboot/issues/240)<br />
* BMC: Initial work to stop BMC from binding to Ethernet port #1 (lock to port #0)<br />
====== Beta 2 (04-28-2019) ======<br />
* PNOR: Downgrade kernel to version 4.19. This works around radeon driver crashes in petitboot</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Talos-ii-2.01-beta-pnor.tar&diff=3061
File:Talos-ii-2.01-beta-pnor.tar
2020-02-23T00:38:32Z
<p>SiteAdmin: Protected "File:Talos-ii-2.01-beta-pnor.tar": Beta firmware ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [Upload=Allow only administrators] (indefinite))</p>
<hr />
<div>== Summary ==<br />
BETA 2.01-next PNOR Flash image for Talos II<br />
<br />
See warnings at https://wiki.raptorcs.com/wiki/Talos_II/Firmware/Public_Beta</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=Talos_II/Firmware/Public_Beta&diff=3060
Talos II/Firmware/Public Beta
2020-02-23T00:38:20Z
<p>SiteAdmin: </p>
<hr />
<div>== Public Beta Firmware ==<br />
<br />
=== Introduction ===<br />
<br />
From time to time Raptor may make public beta firmware images available. These are normally firmware images that are on a fast track to wide GA release, but for which Raptor is seeking public feedback about any issues encountered during upgrades or features missing for daily use.<br />
<br />
'''WARNING''' Beta images have not undergone full release qualification. It is possible that upgrades may fail, leaving your system in a state requiring advanced recovery (e.g. loading a replacement BMC firmware image over TFTP and flashing it via the serial console, or externally writing the BMC Flash device with an SPI programmer). Please do not try the beta firmware images unless you have sufficient recovery tools available.<br />
<br />
=== Current Beta Images ===<br />
==== 2.01-next (04-16-2019 branch) ====<br />
* PNOR: [[:File:Talos-ii-1.07-beta-pnor.img.bz2|89b3a940b6fef143134b296b0bf15cecf258628c]]<br />
<br />
===== Known Issues =====<br />
* System Package 1.x BMC firmware cannot IPL 2.x or higher PNOR (CANTFIX)<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
<br />
===== Regressions =====<br />
* ?<br />
<br />
===== Changelog =====<br />
====== Beta 1 (02-22-2020) ======<br />
* PNOR: Fix crash in petitboot with LSI SAS controllers (mpt3sas module)<br />
<br />
=== Old Beta Images ===<br />
==== 2.00-next (04-16-2019 branch) ====<br />
* BMC: [[:File:Talos-ii-1.07-beta-bmc.img.bz2|486cbe9701c5c9a811f3342494bcbc392da816e1]]<br />
* PNOR: [[:File:Talos-ii-1.07-beta-pnor.img.bz2|89b3a940b6fef143134b296b0bf15cecf258628c]]<br />
* FPGA: [[:File:Talos-system-fpga-v1.08-beta.rom|f3a97a9a50fb2b53aa39d7687bf36bd21bd21e9d]]<br />
<br />
===== Instructions =====<br />
* Ensure that the BMC and PNOR was previously updated to System Package v1.06, and that that your system successfully boots after that update<br />
* Power down your system<br />
* Issue "reboot" on the BMC<br />
* Transfer the decompressed BMC image file to /run/initramfs/image-bmc on the BMC<br />
* Run "fw_printenv | grep eth1addr" and write down the MAC address. '''You will need this information later'''<br />
* Issue "reboot" on the BMC<br />
* After BMC restart (this may take 5-10 minutes):<br />
** fw_setenv ethaddr <IPMI MAC address written down earlier><br />
** fw_setenv eth1addr <IPMI MAC address written down earlier><br />
* Transfer decompressed PNOR image file to the BMC /tmp directory<br />
** pflash -E -p /tmp/talos.pnor<br />
** pflash -P CVPD -c<br />
<br />
===== Known Issues =====<br />
* New BMC cannot IPL old PNOR and vice versa (CANTFIX)<br />
* Lockdown of P2A bridge for security breaks AST2500 VGA passthrough -- ast driver in guest cannot read configuration due to lockdown, and qemu does not pass host device tree information with VGA configuration data to guest kernel.<br />
<br />
===== Regressions =====<br />
* ?<br />
<br />
===== Changelog =====<br />
====== Release Candidate 1 (09-20-2019) ======<br />
* FPGA: Fix power off failure on Talos II Lite systems<br />
* PNOR: Fix incorrect voltage slew rate causing random OCC hang in power saving stop states (https://github.com/open-power/occ/issues/26)<br />
* PNOR: Add LUKS encryption userspace utilities to support FDE direct boot<br />
* PNOR: Add basic diagnostic utilities for system check to Petitboot environment<br />
====== Beta 3 (04-28-2019) ======<br />
* PNOR: Add workaround for skiboot hang during Flash access (https://github.com/open-power/skiboot/issues/240)<br />
* BMC: Initial work to stop BMC from binding to Ethernet port #1 (lock to port #0)<br />
====== Beta 2 (04-28-2019) ======<br />
* PNOR: Downgrade kernel to version 4.19. This works around radeon driver crashes in petitboot</div>
SiteAdmin
https://wiki.raptorcs.com/w/index.php?title=File:Talos-ii-2.01-beta-pnor.tar&diff=3059
File:Talos-ii-2.01-beta-pnor.tar
2020-02-23T00:36:02Z
<p>SiteAdmin: BETA 2.01-next PNOR Flash image for Talos II
See warnings at https://wiki.raptorcs.com/wiki/Talos_II/Firmware/Public_Beta</p>
<hr />
<div>== Summary ==<br />
BETA 2.01-next PNOR Flash image for Talos II<br />
<br />
See warnings at https://wiki.raptorcs.com/wiki/Talos_II/Firmware/Public_Beta</div>
SiteAdmin