https://wiki.raptorcs.com/w/api.php?action=feedcontributions&user=Mx08&feedformat=atomRCS Wiki - User contributions [en]2024-03-29T06:40:48ZUser contributionsMediaWiki 1.33.1https://wiki.raptorcs.com/w/index.php?title=Talk:Operating_System_Compatibility_List&diff=3739Talk:Operating System Compatibility List2022-06-19T12:19:26Z<p>Mx08: Add topic: Include attribute "official upstream support"</p>
<hr />
<div>== Ordering of OS's ==<br />
<br />
I notice that the list of GNU/Linux OS's is no longer ordered alphabetically. I'm restoring the alphabetic order. Hope no one's bothered by that. [[User:JeremyRand|JeremyRand]] ([[User talk:JeremyRand|talk]]) 19:02, 19 May 2019 (CDT)<br />
<br />
Re-ordered versions in descending order, as that seemed to be the most common (and IMO more useful) sort rule. [[User:JeremyRand|JeremyRand]] ([[User talk:JeremyRand|talk]]) 06:46, 16 November 2020 (CST)<br />
<br />
== Include attribute "official upstream support" ==<br />
<br />
It would be useful to have the table indicate whether ppc64(le) is officially supported by the upstream project or not. E.g. Archlinux/Parabola do not officially support ppc64(le) at the moment, and may not be the best choice if one is looking for a stable experience.<br />
<br />
Caveats: Some projects might support only one of ppc64(le), this sould then be indicated via the value of this new attribute.</div>Mx08https://wiki.raptorcs.com/w/index.php?title=POWER9_Hardware_Compatibility_List/PCIe_Devices&diff=3413POWER9 Hardware Compatibility List/PCIe Devices2020-12-27T16:40:42Z<p>Mx08: /* Working */ remove question (the Discussion page is a good place for asking questions, please ask there. thanks!)</p>
<hr />
<div><!-- When adding devices, please list devices in alphabetical order within each category. --><br />
==Compatibility rules==<br />
In general, any PCIe device will work providing that an open source driver is available for your operating system. There are some exceptions:<br />
<br />
* '''Hardware bugs.''' POWER does not permit errant DMA accesses. If a device tries to access areas of host memory which it is not permitted to access, the device is shut down immediately. This is dissimilar to x86 platforms, which simply silently ignore such attempts. Some badly designed I/O devices have bugs causing them to attempt DMA accesses to random areas of host memory; these devices are unlikely to function correctly on POWER systems unless a workaround is available. Note that devices in full bypass mode may legally have access to all host memory, to avoid this and test driver IOMMU setup pass "iommu=nobypass" to the kernel at startup.<br />
* '''I/O space.''' Starting with [[POWER9]], access to the legacy PCI I/O space is no longer supported; devices or drivers which rely on this will not function. The legacy I/O space has been deprecated for as long as PCIe has existed; generally this will only affect very old PCIe devices which use PCIe to PCI bridge chips to attach old PCI devices to the bus. A small subset of these devices may require legacy I/O space support.<br />
* '''Incomplete memory addressing support.''' The PCIe architecture specifies a 64-bit address space. Some I/O devices try to economize on this by only implementing e.g. 40 bits for their addressing, rendering them incapable of addressing host memory which lies above address 2<sup>40</sup>. (Firmware patches to work around this are pending.)<br />
* '''Bifurcation limits.''' Arbitrary PCIe lane bifurcation is not supported. Devices which split a PCIe slot into multiple connectors (for example, PCIe to M.2 adaptors) will not work unless they have a PCIe switch chip, although the first connector will generally work.<br />
<br />
==Troubleshooting==<br />
<br />
If a PCIe device is in a broken state due to being attached/detached from a VM, or due to a transition from Petitboot to the main OS, you may be able to fix it by issuing a hot reset. A script for performing a PCIe hot reset is at [[File:Pcie_hot_reset.sh]]. For background on PCIe resets and how a hot reset differs from the function-level reset performed by <code>echo 1 > /sys/bus/pci/devices/$dev/reset</code>, see [https://unix.stackexchange.com/a/474378 Alex Forencich's explanation on Stack Exchange].<br />
<br />
==NICs==<br />
===Working===<br />
* Broadcom [[BCM5719]]<br />
* Chelsio T520-SO-CR (dual port 10Gb/s, cxgb4 driver)<br />
* Chelsio T6225-SO-CR<br />
* Mellanox ConnectX-6 EN 200Gb/s Adapter Card ''(supports [[CAPI]])''<br />
* Silicom [https://www.silicom-usa.com/pr/server-adapters/networking-adapters/10-gigabit-ethernet-networking-adapters/pe310g4spi9-server-adapter/ PE310G4SPI9]/[https://www.silicom-usa.com/pr/server-adapters/networking-adapters/10-gigabit-ethernet-networking-adapters/pe310g4spi9la-quad-port-10-gigabit-nic-intel-based/ PE310G4SPI9LA] quad port 10 GbE SFP+ adapter (ixgbe driver)<br />
* Unbranded 4-port Gigabit Ethernet adapter (Chipset: Four Realtek RTL8111F controllers behind one ASMedia ASM1184e switch) (r8169 driver, firmware optional)<br />
** The card be identified by the "NET111-V1.0" text on its PCB.<br />
* [https://www.asus.com/Networking-IoT-Servers/Wired-Networking/All-series/XG-C100F/ ASUS XG-C100F] (single port 10GbE SFP+, AQUANTIA AQtion Linux "atlantic" driver)<br />
** The atlantic Linux driver is not compiled by default on PPC64 (Only X86, ARM64 and COMPILE_TEST in Kconfig) but enable it and it works flawlessly. [[File:Atlantic-Linux-driver-on-PPC64.patch|Patch]] to do that by default in the process of being upstreamed.<br />
** There is proprietary firmware written into EEPROM from the factory but it does not seem to be writeable, nor does it have to be loaded by the Linux kernel.<br />
<br />
===Non-working===<br />
* Mellanox ConnectX IB QDR (mlx4 driver)<br />
<br />
==Wireless Cards==<br />
===Working===<br />
* Alfa AWUS036NHA Wireless USB Adaptor<br />
** open source firmware (ath9k_htc) [https://github.com/qca/open-ath9k-htc-firmware]<br />
* [https://ark.intel.com/content/www/us/en/ark/products/75439/intel-dual-band-wireless-ac-7260.html Intel Dual-Band Wireless-AC 7260] (Bluetooth untested)<br />
* [https://ark.intel.com/content/www/us/en/ark/products/86068/intel-dual-band-wireless-ac-8260.html Intel Dual-Band Wireless-AC 8260] (Bluetooth untested)<br />
* [https://ark.intel.com/content/www/us/en/ark/products/99445/intel-wireless-ac-9260.html Intel Dual-Band Wireless-AC 9260] (Bluetooth untested)<br />
* [https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-mini-pcie ThinkPenguin TPE-NMPCIE]<br />
** Chipset: Atheros AR9281<br />
** Linux driver: ath9k<br />
** Tested with StarTech PEX2MPEX; device is detected without trouble by Linux and NetworkManager; didn't try hooking up an antenna, so wasn't able to try connecting to networks.<br />
* TP-Link TL WN823N RTL8192EU [https://github.com/Mange/rtl8192eu-linux-driver]<br />
** remove "ARCH=$(ARCH)" on line 1710 of the makefile and it compiles fine<br />
* TP-LINK TL-WN725N V2 USB dongle<br />
** as of Linux 5.6.x, the rtl8188eu is in staging stage, so it is advised to compile the driver from [[https://github.com/lwfinger/rtl8188eu lwfinger/rtl8188eu]]<br />
<br />
==NVMe Drives==<br />
* Samsung 950 PRO (with M.2 to PCIe adapter)<br />
* Samsung 960 EVO / PRO (with M.2 to PCIe adapter)<br />
* Samsung 970 PRO (with M.2 to PCIe adapter)<br />
* Samsung 970 EVO Plus (with M.2 to PCIe adapter)<br />
* [https://www.samsung.com/semiconductor/ssd/datacenter-ssd/MZ1LB960HAJQ/ Samsung PM983] (with [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php AOC-SHG3-4M2P] M.2 to PCIe adapter)<br />
* [https://ark.intel.com/content/www/us/en/ark/products/series/81000/intel-ssd-dc-p3600-series.html Intel SSD DC P3600 PCIe AIC] (tested 1.6 TB)<br />
* Intel Optane 900P NVMe XPoint PCIe<br />
* Intel Optane 905P NVMe XPoint PCIe AIC<br />
* Intel Optane 905P NVMe Xpoint U.2, with included U.2 to M.2 cable plugged into an [[#PCIe_to_M.2_Adapters|ASUS Hyper M.2 X4 mini]].<br />
* WD Black PCIe (with M.2 to PCIe adapter)<br />
* MyDigitalSSD BPX 480GB (with M.2 to PCIe adapter)<br />
<br />
Known issues:<br />
* [FIXED in stable kernels 4.19 and 5.4] [https://bugzilla.kernel.org/show_bug.cgi?id=202665 IOMMU related errors when performing discard on some NVMe devices] (mainly NVMe SSDs). Current workaround is booting with the kernel parameter ''iommu=soft'', see the [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=530436c45ef2e446c12538a400e465929a0b3ade patch]<br />
<br />
==PCIe to M.2 Adapters==<br />
===Working===<br />
* [https://www.asus.com/us/Motherboard-Accessories/HYPER_M2_X4_MINI_CARD/ ASUS Hyper M.2 X4 mini], PCIe X4 to M.2.<br />
* [http://ableconn.com/products_2.php?gid=62 Ableconn PEXM2-SSD M.2 NGFF PCIe SSD to PCI Express 3.0 x4 Host Adapter Card (M.2 to PCIe adapter)]<br />
* [https://www.addonics.com/products/ad2m2nvmpx8.php Addonics AD2M2NVMPX8] Dual NVMe PCIe adapter 2x M.2 PCIe to PCIe x8<br />
* [https://www.delock.com/produkte/G_89370/merkmale.html Delock PCI Express x4 Card > 1 x internal NVMe M.2 Key M 80 mm - Low Profile Form Factor; Item No. 89370]<br />
* [https://www.newegg.com/Product/Product.aspx?Item=9SIA4RE5AU2769 JEYI SK4 M.2 NVMe(M Key) SSD to PCI-E 3.0 x4 Adapter Converter Card]<br />
* [https://www.newegg.com/Product/Product.aspx?Item=N82E16815124167 SYBA SI-PEX40110 M.2 PCI-e To PCI-e 3.0 x4]<br />
* [https://highpoint-tech.com/USA_new/series-ssd7101a-1-overview.htm HighPoint SSD7101A-1] 4x M.2 PCIe to PCIe 3.0 x16 (based on PLX PEX8747 PCIe switch)<br />
** Works without special drivers as a PCIe switch. NVMEs are detected and work just fine. Petitboot is able to boot attached NVMEs with no problems. Tested in FreeBSD. -- [[User:Bdragon|Bdragon]] ([[User talk:Bdragon|talk]])<br />
* [https://highpoint-tech.com/USA_new/series-ssd7102-overview.htm HighPoint SSD 7102] 4x M.2 PCIe to PCIe 3.0 x16 (with PCIe switch)<br />
* [https://estore-highpoint-tech.com/products/highpoint-ssd7505-pcie-4-0-x16-4-channel-u-2-nvme-raid-controller HighPoint SSD7505] PCIe 4.0 x16 4-Channel M.2 NVMe RAID Controller<br />
* [https://raidsonic.de/en/standards/searchresults.php?we_objectID=5456 Raidsonic Icy Box PCIe extension card for one M.2 NVMe SSD (IB-PCI214M2-HSL)]:<br />
** Tested with a Samsung 970 EVO Plus NVMe M.2 with 2 TB<br />
** Bootable and no special driver installation required<br />
** Has a passive cooling system for the SSD (about 20 degree Celsius cooler than without)<br />
** Supports PCIe 3.0 x4 with up to 32 GBit/s according to the manual<br />
** Seems to support PCIe 4.0 x4 with up to 64 GBit/s according to the current [https://www.raidsonic.de/products/accessories/ac_controller/IB-PCI214M2-HSL/pdf/datasheet_IB-PCI214M2-HSL_e.pdf data sheet] (probably due to the fact that it is only a routing device without any own logic)<br />
* [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P] 4x M.2 PCIe to PCIe 3.0 x8 (using a PEX 8734 PCIe 3.0 (8.0GT/s) Switch). Draws 10 watts in idle. Requires one additional 4-pin 12V connector.<br />
<br />
===Partially working===<br />
* [https://www.amazon.com/gp/product/B074WV4ZN4 Aplicata Quad M.2 NVMe SSD PCIe x16 Adapter] (no PCIe switch; only lowest slot works)<br />
<br />
==PCIe to U.2 Adapters==<br />
===Working===<br />
* [https://highpoint-tech.com/USA_new/series-ssd7120-overview.htm High Point SSD7120] PCIe 3.0 x16 to 4x U.2 NVMe ports (Dedicated PCIe 3.0 x4 per port, with PCIe switch) tested by [[User:Gyakovlev|Gyakovlev]] ([[User talk:Gyakovlev|talk]])<br />
** Tested with [https://www.icydock.com/goods.php?id=255 Icy Dock ToughArmor MB699VP-B] 4xU2 enclosure. Neither above controller nor enclosure ships with cables, 4x SAS HD SFF-8643 cables required to connect drives.<br />
** 4x Optane 905P work fine with this combo.<br />
<br />
==PCIe to MiniPCIe Adapters==<br />
=== Working ===<br />
* [https://www.startech.com/Cards-Adapters/Slot-Extension/PCI-Express-to-Mini-PCI-Express-Card-Adapter~PEX2MPEX StarTech PEX2MPEX] ([https://www.newegg.com/startech-com-model-pex2mpex-pci-express-to-mini-pci-express/p/N82E16815158307?Item=N82E16815158307&Description=mini%20PCIe&cm_re=mini_PCIe-_-15-158-307-_-Product NewEgg])<br />
** Tested with ThinkPenguin TPE-NMPCIE.<br />
** Particularly of interest as a lot of the ASPEED and SiliconMotion GPU's have a MiniPCIe form factor.<br />
<br />
==SAS/SATA Storage Controllers ==<br />
===Working===<br />
* IOCrest SI-PEX40062 (Chipset: Marvell 88SE9235, PCI id 1B4B:9235)<br />
** Marvell 88SE9230 chipset also confirmed to work<br />
* Kouwell PE-115H (Chipset: Marvell 88SE9130, PCI id 1b4b:9130)<br />
* LSI 9300/9200 SAS HBAs<br />
** May require updating to IT firmware on a x86 machine<br />
* [[PM8068]]-based SAS HBAs <br />
* Supermicro AOC-SLG3-4E2P 4-port OCuLink adapter<br />
* Jmicron JMB 363 SATA PCIe card. SATA ports work with Petitboot.<br />
* MegaRAID 9460-8i<br />
<br />
===Non-working===<br />
* AXAGON PCES-SA2 (ASMedia chipset)<br />
* SuperMicro AOC-SASLP-MV8 (mvsas driver)<br />
* MegaRAID 9341-8i - probably a bug in the firmware<br />
<br />
=== Unknown if working (good candidates to test) ===<br />
* [https://highpoint-tech.com/USA_new/series_rr600-overview.htm HighPoint RocketRAID 642L] (Chipset: Marvell 88SE9235)<br />
* [https://highpoint-tech.com/USA_new/series_rr600-overview.htm HighPoint RocketRAID 644L] (Chipset: Marvell 88SE9235)<br />
<br />
== Optical Drives ==<br />
<br />
* [https://www.asus.com/us/Optical-Drives-Storage/BW16D1HT/HelpDesk_Download/ Asus BW-16D1HT Retail] (Blu Ray Writer with SATA interface):<br />
** Partially working (reading BDs works, writing not yet tested). [https://forums.raptorcs.com/index.php/topic,40.0.html Sometimes not recognized during boot phase with ATA timeouts] causing all SATA devices to be disabled<br />
<br />
<br />
== Graphics Cards ==<br />
<br />
No display? Check out the [[Troubleshooting/GPU|GPU Troubleshooting]] page.<br />
<br />
=== AMD ===<br />
<br />
All AMD GPUs currently have DMA issues (limited to 32-bit, which can cause crashes) due to missing Linux kernel support for DMA windows between 33 and 63 bits in length. The root cause is GPU vendors (and occasionally some non-GPU vendors) cutting costs and only including 40-bit capable (Intel-style) DMA controllers. A compatibility mode is expected to be included in Linux 5.4 and above that will resolve this issue.<br />
<br />
* AMD Radeon HD 5570 - Archaic (1GB VRAM, PCI 2.1) but much faster than the AST. This card (ASUS EAH5570 Silent) is passively cooled.<br />
* AMD Radeon HD 5850 - Must disable onboard VGA first. Currently has issues with only using 32-bit DMA.<br />
* AMD Radeon HD 6450 - Works with default settings (kernel: radeon, X: modesetting or radeon), tested in BE mode<br />
* AMD Radeon HD 6850 - Disable AST VGA with jumper. 32 bit.<br />
* AMD Radeon HD 7850 - Disabled onboard VGA. Using amdgpu is highly unstable, radeon driver is usable but has issues with only using 32-bit DMA.<br />
* AMD Radeon HD 7950 - Must disable onboard VGA first. Currently has issues with only using 32-bit DMA.<br />
* AMD Radeon R5 220<br />
* AMD Radeon R5 230 - Works in BE mode (use <code>Option "AccelMethod" "EXA"</code> for Xorg)<br />
* AMD Radeon R7 240<br />
* AMD Radeon R9 290X<br />
* AMD Radeon R9 Nano - Must disable onboard VGA first. Works perfectly under Linux 5.6.x on Fedora 32. There is no video output on kernel 5.7.x and 5.8.x, to workaround this issue the kernel parameter `amdgpu.dc=0` must be added into grub config<br />
* Sapphire GPRO 8200 (Polaris10 core) - Disable AST VGA with jumper, disabling in grub is not enough. Same form factor as WX7100, a single-slot RX 470 with 8GB of RAM and 4 DP outputs.<br />
* AMD Radeon RX 480<br />
* AMD Radeon RX 550 - Works with caveats (below) for particular card tested.<br />
** Card tested was Gigabyte GV-RX550D5-2GD in a Blackbird with Ubuntu 19.10, 5.3.0-24 and amdgpu with onboard VGA disabled by jumper. Suspect with tweaking would work without needing to disable VGA. Alas would lock up every day or two, to the point I replaced with a Sapphire RX580. Based on conversations w/Raptor suspect this was an issue with the model card I had rather than the RX550 itself.<br />
* AMD Radeon RX 560X<br />
* AMD Radeon RX 580 – Works with the amdgpu firmware from Ubuntu 19.04 and disabled onboard VGA<br />
** You may also need a kernel parameter like <code>vga=797</code> if xinit complains about VESA[https://en.wikipedia.org/wiki/VESA_BIOS_Extensions]<br />
** The Sapphire NITRO+ Radeon RX 580 8GB card is a tight fit on the Blackbird planar if you're using the 2nd PCIe slot as it a bit wider than two slots (and is documented as such). Solved by removing the adapter plate for the PCIe-M2 adapter card being used and allowing it to sit in slot untethered.<br />
* AMD Radeon RX Vega 56 - Works with Debian Buster with amdgpu. Requires patches to work, somewhat unstable but usable. Cannot use AST Integrated VGA and AMDGPU at the same time without causing conflict. Not tested at this moment for use in petitboot or firmware. <br />
* AMD Radeon RX Vega 64 - Works with Fedora 32 with Linux kernel 5.5.0's amdgpu. The card does _NOT_ display in bootloader because vega10 firmwares failed to load correctly.<br />
* AMD Radeon Pro WX4100 (Polaris11 core) - May need at least linux 4.16 in order to get Xorg to work.<br />
* AMD Radeon Pro WX5100<br />
* AMD Radeon Pro WX7100 (Polaris10 core) - Available pre-installed on Talos II workstation, server, and desktop configurations.<br />
* AMD Radeon RX 5700 (Navi 10) - Requires [https://lists.freedesktop.org/archives/amd-gfx/2019-December/043682.html kernel patches] to enable display output. <br />
* AMD Radeon RX 5700 XT (Navi 10) - Requires [https://lists.freedesktop.org/archives/amd-gfx/2019-December/043682.html kernel patches] to enable display output.<br />
<br />
The core name is important when storing the firmware into the BOOTKERNFW partition in PNOR for use by skiroot.<br />
<br />
=== NVIDIA ===<br />
* NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1) - Works in petitboot if onboard VGA is disabled. Currently has issues with only using 32-bit DMA. No firmware needed.<br />
* NVIDIA RTX 2070 - usable for compute, but not 3D acceleration; integrated by Raptor as part of the Talos II PowerAI Development System configuration<br />
<br />
=== Other ===<br />
* [[AST2500|ASPEED AST2500]]. Works in both the main OS (LE mode) and Petitboot. BE mode partially works (doesn't crash, but colors are wrong unless you apply a patch that is harmful to performance). <code>ast</code> Linux driver.<br />
* [https://www.climaxdigital.co.uk/CUH195-USB-2-to-DVI-VGA-or-HDMI-Adaptor-1080p-full-hd ClimaxDigital CUH195 USB 2.0 Graphic Adapter] - Based on DisplayLink DL-3500 chipset. Works in the main OS; not tested with Petitboot but is likely to work there too.<br />
* EVGA 100-U2-UV12-A1 UV Plus USB VGA Adapter - DisplayLink Based - Petitboot shows up without loading firmware. Not tested in OS.<br />
<br />
=== Non-working ===<br />
<br />
* [https://www.aspeedtech.com/products.php?fPath=20&rId=244 ASPEED AST1300]. Older revision of the AST2510 (AST1300 is 4th generation; AST2510 is 6th generation). VGA 1920x1200 @ 60Hz 32bpp; framebuffer (no acceleration). <code>ast</code> Linux driver. [https://github.com/open-power/skiboot/issues/257 Open issue with Skiboot for getting it fixed.] Known suppliers of AST1300 devices are:<br />
** [https://iei.rs/IGCME-1300-R10 IEI Integration Corp IGCME-1300-R10] ([https://iei.rs/image/cache/data/IGCME-1300_20131105.pdf Datasheet]) ([https://dls.ieiworld.com/IEIWeb/Reserved/0D332000196276623429/IGCME-1300%20QIG%20V1.01_20120531.pdf Quick Installation Guide])-- Resold by:<br />
*** [http://archivecaslytosk.onion/QZROL eBay example 1]<br />
*** [https://www.ebay.com/p/1383304505 eBay example 2]<br />
*** [https://web.archive.org/web/20171003045507/http://neutronusa.com/prod.cfm/1525210/ NeutronUSA] (Warning: non-TLS link!)<br />
*** [https://forums.servethehome.com/index.php?threads/fs-us-ny-intel-x540-t2-minipcie-vga-slim-120mm-fans.26880/ ServeTheHome]<br />
<br />
=== Unknown if working (good candidates to test) ===<br />
* [https://www.aspeedtech.com/products.php?fPath=20&rId=455 ASPEED AST2510]. It's the GPU component of the [[AST2500]] without the BMC component. VGA 1920x1200 @ 60Hz 32bpp; framebuffer (no acceleration). Might be useful for users who want to add additional VGA displays beyond the single VGA display supported by the built-in AST2500, with similar freedom and performance properties as the AST2500. <code>ast</code> Linux driver. Known suppliers of AST2510 devices are:<br />
** [https://www.win-ent.com/1U-Rackmount-Platforms/pl-81280 WIN Enterprises IP-492B]<br />
** AEWIN Technologies R492B<br />
*** Distributed as add-on for these servers:<br />
**** [https://www.aewin.com/products/scb-1921a/ SCB-1921A]<br />
**** [https://www.aewin.com/zh-hans/products/scb-1925/ SCB-1925] ([https://www.aewin.com/wp-content/uploads/2019/11/SCB-1925.pdf datasheet])<br />
**** [https://www.aewin.com/zh-hant/products/scb-1935a/ SCB-1935A] ([https://www.aewin.com/wp-content/uploads/2020/02/SCB-1935.pdf datasheet])<br />
**** [https://www.aewin.com/products/scb-1935b/ SCB-1935B] ([https://www.aewin.com/wp-content/uploads/2020/02/SCB-1935.pdf datasheet])<br />
* [https://www.aspeedtech.com/products.php?fPath=20&rId=377 ASPEED AST1400]. Older revision of the AST2510 (AST1400 is 5th generation; AST2510 is 6th generation). VGA 1920x1200 @ 60Hz 32bpp; framebuffer (no acceleration). <code>ast</code> Linux driver. Known suppliers of AST1400 devices are:<br />
** [https://iei.rs/IGCME-1300-R11 IEI Integration Corp IGCME-1300-R11] ([https://iei.rs/image/cache/data/IGCME-1300_MPCIE-USB3.pdf Datasheet]) ([https://dls.ieiworld.com/IEIWeb/Reserved/0F233000410888189307/IGCME-1300%20QIG%20V1.10_20150819.pdf Quick Installation Guide]) -- Resold by:<br />
*** [https://eu.mouser.com/ProductDetail/IEI/IGCME-1300-R11?qs=wd5RIQLrsJgucg6W4Ojybw%3D%3D Mouser]<br />
*** [https://www.amazon.com/IEI-Technology-IGCME-1300-R11-Adapter-AST1400/dp/B07WRVK8DR Amazon]<br />
*** [https://www.kacer.com/product/accessories/daughter%20card/Mini%20PCIe/IGCME-1300/IGCME-1300.htm Kacer]<br />
*** [https://www.alibaba.com/product-detail/IEI-IGCME-1300-R11-PCIe-Mini_60839628812.html Alibaba]<br />
*** [https://www.icpamerica.com/igcme-1300-add-on-card/ ICP America]<br />
* SiliconMotion SM750. Chipset is VGA + DVI (dual display) 1920x1440, but some devices may not support the full chipset resolution; appears to have 2D acceleration (not just framebuffer). Appears to be fixed-function silicon (no firmware). PCIe interface. <code>sm750fb</code> Linux driver is in staging. [https://gitlab.com/sudipm/sm750/tree/sm750 <code>sm750</code> Linux driver] is not yet merged to mainline. <code>sm750</code> Linux driver has some weird license text, but [https://github.com/torvalds/linux/commit/81e0da703fdba1ee126868bf8350592c79cdba13 according to Greg Kroah-Hartman] it sounds like the authors intend it to be GPLv2; would be useful to double-check with Greg/Sudip/Teddy whether Silicon Motion's statement to Greg applies to Sudip's <code>sm750</code> or if it only applies to mainline's <code>sm750fb</code>. Known suppliers:<br />
** [https://www.cervoz.com/product.php?id=c39eb02c-014a-1000-a04b-001851f77c0c Cervoz MEC-DIS-M002]. VGA + DVI (dual display) 1280x1024 @ 60Hz. Mini-PCIe form factor. Resold by:<br />
*** [https://www.kacer.com/product/accessories/daughter%20card/Mini%20PCIe/MEC-DIS-M002/MD02.html Kacer]<br />
*** [https://www.texim-europe.com/product/MEC-DIS-M002 Texim Europe]<br />
*** [https://www.bvm.co.uk/products/1053-Mini-PCI-Express-DVI-VGA-Module-MEC-DIS-M002/ BVM]<br />
*** [https://web.archive.org/web/20200704052513/https://nerugged.com/product/mec-dis-m002-mpcie-dvi-vga-controller/ New England Rugged]<br />
** [https://web.archive.org/web/20200707045733/http://www.smartnre.com/en/product/Fastwel_VIM552_3U_CPCI_Graphics_Module.html Fastwel VIM552] (Warning: non-TLS link!)<br />
** [https://www.memorydepot.com/detail/EMPV-1201-C1.html Innodisk EMPV-1201-C1]<br />
** [https://www.memorydepot.com/detail/EMPV-1202-C1.html Innodisk EMPV-1202-C1]<br />
** [https://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760 SUNIX VGA0419]<br />
** [https://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766 SUNIX VGA0429]. Resold by:<br />
*** [https://www.dc3.co.za/computer-store/sc-svga0429/ DC3 Distribution]<br />
** [https://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1817 SUNIX VGA0449M]<br />
** [https://www.vadatech.com/product.php?product=368 VadaTech AMC348]<br />
** [https://www.vadatech.com/product.php?product=151 VadaTech AMC349]<br />
** [https://www.versalogic.com/product/video-expansion-module/ VersaLogic VL-MPEe-V5]<br />
* DisplayLink<br />
** [https://www.climaxdigital.co.uk/epages/BT3449.sf/en_GB/?ObjectPath=/Shops/BT3449/Products/111216 ClimaxDigital CUH350]<br />
*** Based on DisplayLink DL-3500 chipset.<br />
*** ClimaxDigital claims 1920x1200; DisplayLink chipset docs claim 2560x1600.<br />
** [https://www.startech.com/en-us/audio-video-products/usb2dvimm6 StarTech USB2DVIMM6]<br />
*** Based on DisplayLink DL-165 chipset.<br />
*** 1680x1050.<br />
*** Resold by [https://www.newegg.com/startech-com-usb2dvimm6/p/N82E16815158183 NewEgg].<br />
** [https://www.startech.com/en-us/audio-video-products/usb2dvipro2 StarTech USB2DVIPRO2]<br />
*** Based on DisplayLink DL-195 chipset.<br />
*** 1920x1200.<br />
*** Resold by [https://www.newegg.com/startech-com-usb2dvipro2/p/N82E16812400361 NewEgg].<br />
** [https://www.startech.com/en-us/audio-video-products/usb2vgapro2 StarTech USB2VGAPRO2]<br />
*** Based on DisplayLink DL-195 chipset.<br />
*** 1920x1200.<br />
*** Resold by [https://www.newegg.com/startech-com-usb2vgapro2/p/N82E16812400368 NewEgg].<br />
<br />
== Sound Cards ==<br />
<br />
===Working===<br />
* Creative Sound Blaster Audigy FX SB1570 PCIe 5.1 Sound Card<br />
* Creative Sound Blaster X-Fi Xtreme Fidelity PCIe Audio Sound Card (SB0880)<br />
* AMD Radeon HD 5850 and 7950 (HDMI audio)<br />
* [https://www.vantecusa.com/products_detail.php?p_id=156&p_name=+USB+Stereo+Audio+Adapter&pc_id=9&pc_name=Adapters&pt_id=3&pt_name=Audio+%2B++Video#tab-1 VANTEC NBA-120U (USB)]<br />
* Sabrent USB External Stereo Sound Adapter (AU-MMSA)<br />
* [https://mackie.com/products/onyx-blackjack Mackie Onyx Blackjack (USB) Recording Interface]<br />
* RME HDSPe AIO (FreeBSD tested)<br />
* Leveraged Sabrent Bluetooth 4.0 USB adapter (model BT-UB40) to connect to wireless Bluetooth headphones, specifically Bose Quiet Comfort 35.<br />
<br />
===Non-working===<br />
* ASUS Xonar SE - Contains ASMedia USB host controller with errant DMA access flaw<br />
* Creative Sound Blaster Audigy PCIe RX 7.1 - unable to enable emu10k1 driver on little-endian power9 kernel as driver requires ZONE_DMA<br />
<br />
==USB Host Controllers==<br />
===Working===<br />
* Insignia USB 3.0 PCI-e NS-PCCUP53 V1.0 (Chipset: NEC D720202)<br />
* AGAXO PCEU-23R (Chipset: Renesas uPD720202, PCI id 1912:0015)<br />
* Terminus Technology Inc. FE 2.1 7-port Hub<br />
* [https://www.sonnettech.com/product/legacyproducts/allegroprousb3pcie.html Sonnet Allegro Pro USB 3.0 PCIe USB3-PRO-4PM-E] (Chipset: Four [http://www.frescologic.com/product/single/fl1100ex/ Fresco Logic FL1100EX] controllers behind one [https://www.broadcom.com/products/pcie-switches-bridges/pcie-switches/pex8608 PLX PEX 8608] switch)<br />
* [https://www.vantecusa.com/products_detail.php?p_id=125&p_name=+4-Port+SuperSpeed+USB+3.0+PCIe+Host+Card+w%2F+Internal+20-Pin+Connector&pc_id=16&pc_name=USB&pt_id=4&pt_name=Add-on+Cards Vantec UGT-PC345 4 Port USB 3.0 PCIe w/ Internal 20 pin] (Chipset: Renesas uDP720201)<br />
* [https://www.amazon.com/gp/product/B07H4HJNJC] (monster card with 8 ports of USB 3.0) four Renesas uPD720202 chips behind ASMedia 1806, card can be found under different brands but can be identified by the look. [http://sedna-shop.com/index.php?route=product/product&path=59_74&product_id=138 This should be the same card]<br />
* [https://highpoint-tech.com/USA_new/cs-series_RocketU1022A-Series.htm HighPoint RocketU 1022A] (Chipset: ASMedia ASM1042)<br />
** This chip seems somewhat unreliable, since USB reads can fail after only a few tens of gigabytes have been transferred.<br />
* [https://www.sybausa.com/index.php?route=product/product&product_id=818 IOCrest SI-PEX20189] (Chipset: ASMedia ASM1142)<br />
** Requires kernel version 4.14.194, 4.19.139, 5.4.58, 5.7.15, 5.8.1, or later.<br />
*** Petitboot's kernel will need to be updated to one of these versions (or later) in order to boot from any USB devices connected to this controller.<br />
** EEH errors may occur during long reads from multiple devices.<br />
* [http://ableconn.com/products_2.php?gid=121 Ableconn PU31-2C-2] (Chipset: ASMedia ASM2142)<br />
** Requires kernel version 4.14.190, 4.19.135, 5.4.54, 5.7.11, 5.8.0, or later.<br />
*** Petitboot's kernel will need to be updated to one of these versions (or later) in order to boot from any USB devices connected to this controller.<br />
** EEH errors may occur during long reads from multiple devices.<br />
* Semoic USB 3.1 to Type-C 2 Port Expansion Card (Chipset: ASMedia ASM3142, same PCI IDs as ASM2142)<br />
** Card appears to be sold under different brands, but can be identified by the "PCE2TYC-A31", "VER006", "USB 3.1 Type-C 2-Port Card", and "PCE-E 4X" markings on the PCB.<br />
** Requires kernel version 4.14.190, 4.19.135, 5.4.54, 5.7.11, 5.8.0, or later.<br />
*** Petitboot's kernel will need to be updated to one of these versions (or later) in order to boot from any USB devices connected to this controller.<br />
** EEH errors may occur during long reads from multiple devices.<br />
<br />
===Non-working===<br />
In general, USB3 host controllers based on ASMedia chipsets are known to be problematic, due to ASMedia hardware or firmware bugs causing errant DMA accesses to invalid regions of host memory.<br />
<br />
* AXAGON PCEU-43V - chipset Via VL805 - PCI id 1106:3483<br />
* StarTech PEXUSB314A2V - 2x ASM1142 host controllers and a PCIe switch<br />
** This card completely fails to be detected.<br />
* QNINE USB 3.1 Gen2 (Type-A and Type-C) - ASM1142<br />
** This may work now with an updated kernel, but it hasn't been tested yet.<br />
* Rosewill RC-509 - ASM1142<br />
** This may work now with an updated kernel, but it hasn't been tested yet.<br />
<br />
=== Unknown if working (good candidates to test) ===<br />
* [http://sedna-shop.com/index.php?route=product/product&product_id=54 SEDNA - PCIe 7 Port USB 3.0 Adapter Card] (Chipset: NEC)<br />
* [http://sedna-shop.com/index.php?route=product/product&product_id=99 SEDNA - PCIe 4 Port USB 3.0 Adapter Card] (Chipset: NEC uPD720201)<br />
* [https://www.startech.com/Cards-Adapters/USB-3.0/Cards/7-port-pci-express-usb-3-card~PEXUSB3S7 StarTech PCIe 7 Port USB 3.0 Adapter Card] (Chipset: NEC uPD720201)<br />
* [https://highpoint-tech.com/USA_new/series-ru1344a-overview.htm High Point RocketU 1344A 4-Port USB 3.1 PCI-Express 3.0 x 4 HBA] (Chipset: Two ASMedia ASM3142 controllers behind one [https://www.broadcom.com/products/pcie-switches-bridges/pcie-switches/pex8714 PLX PEX 8714] switch)<br />
* [https://highpoint-tech.com/USA_new/series-ru1144d-overview.htm High Point RocketU 1144D 4-Port USB 3.0 PCI-Express 2.0 x 4 HBA] (Chipset: Four ASMedia ASM1042A controllers behind one [https://www.broadcom.com/products/pcie-switches-bridges/pcie-switches/pex8609 PLX PEX 8609] switch)<br />
* [https://www.sonnettech.com/product/allegro-usbc-pcie.html Sonnet Allegro USB-C PCIe Card USB3C-2PM-E] (Chipset: ASMedia ASM1142/ASM3142 (cards shipped before April 2020 use the ASM1142 controller))<br />
* [https://www.sonnettech.com/product/allegro-usbc-4port-pcie.html Sonnet Allegro USB-C 4-Port PCIe Card USB3C-4PM-E] (Chipset: Two ASMedia ASM1142/ASM3142 controllers (cards shipped before January 2020 use ASM1142 controllers) behind one [https://www.diodes.com/part/view/PI7C9X2G308GP Pericom PI7C9X2G308GP] switch)<br />
* [https://www.gigabyte.com/Motherboard/GC-USB-32-GEN2X2 Gigabyte GC-USB 3.2 GEN2X2] (Chipset: ASMedia ASM3242)<br />
<br />
==TV Tuners==<br />
* [https://hauppauge.com/pages/products/data_quadhd.html Hauppauge WinTV-quadHD] (Chipset: Four Silicon Labs Si2157 tuners, four LG LG3306A demodulators, and two Conexant CX23888 PCIe interface chips behind one [https://www.diodes.com/part/view/PI7C9X2G304EL Pericom PI7C9X2G304EL] PCIe switch)<br />
* Hauppauge WinTV HVR-850 (2040:7240) - ATSC - using Kaffeine<br />
<br />
==Firewire Host Controllers==<br />
===Working===<br />
<br />
* [https://www.sybausa.com/index.php?route=product/product&product_id=119 Syba SY-PEX30016] (Chipset: TI XIO2213B)<br />
** Requires [https://marc.info/?l=linux1394-devel&m=157207806405627&q=mbox this patch] to work on kernels with a 64k page size.<br />
<br />
=== Unknown if working (good candidates to test) ===<br />
<br />
* [http://www.dawicontrol.com/index.php?cmd=proddet&id=media Dawicontrol DC-FW800] (Chipset: TI XIO2213B)<br />
* [https://www.delock.de/produkte/G_89210/merkmale.html?setLanguage=en DeLOCK 3x FireWire 800, Item No. 89210] (Chipset: TI XIO2213B)<br />
* [https://www.digitus.info/en/products/computer-components/computer-peripherals/serial-parallel-adapter/ds-30203-2/ DIGITUS Firewire 800 (1394b) PCIe Card] (Chipset: TI XIO2213B)<br />
* [https://www.exsys.de/index.php?page=product&info=127 Exsys EX-16415] (Chipset: TI XIO2213)<br />
* [https://www.exsys.de/index.php?page=product&info=366 Exsys EX-16512E] (Chipset: TI)<br />
* [http://www.ioi.com.tw/products/proddetail.aspx?CatID=106&DeviceID=3021&HostID=2009&ProdID=1060100 IOI Technology FWB-PCIE1X11A] (Chipset: TI XIO2213B)<br />
[[Category:Compatibility List]]<br />
<br />
==Video Capture Cards==<br />
* [https://www.avermedia.com/professional/product/ce310b/overview AVerMedia CE310B] (Chipset: Conexant CX23888)<br />
** Requires kernel version 4.19.106, 5.4.22, 5.5.6, or later.</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Skiboot/NVRAM&diff=3397Skiboot/NVRAM2020-11-27T03:33:59Z<p>Mx08: /* Details */ add note: also known as fast reboot</p>
<hr />
<div>= Known NVRAM settings in Skiboot =<br />
<br />
A loose collection of known NVRAM settings in Skiboot. These should eventually be exposed via the Petiboot TUI.<br />
<br />
To query the state of these settings, execute the following from the petitboot shell, or from a host OS with the nvram utility installed:<br />
<br />
<nowiki>nvram -p ibm,skiboot --print-config</nowiki><br />
<br />
== fast-reset ==<br />
<br />
=== Description ===<br />
Enable quick return to petitboot on reset<br />
<br />
=== Details ===<br />
On Talos II firmware v2.00+ from RCS, and all Blackbird firmwares from RCS, fast reset (also known as fast reboot) is enabled by default. Instead of cycling host power and running the entire IPL process when the system reboots, Skiboot simply re-executes the Skiroot kernel, which runs petitboot to re-launch the host OS. However, certain devices/drivers (most often GPUs with dynamically-loaded firmware) may misbehave when the OS is reloaded without a host power cycle; thus, it may be beneficial to disable this behavior. Set to 1 to enable, or 0 to disable.<br />
<br />
<nowiki>nvram -p ibm,skiboot --update-config fast-reset=0</nowiki><br />
<br />
== pcie-max-link-speed ==<br />
<br />
=== Description ===<br />
PCIe Link Speed Cap<br />
<br />
=== Details ===<br />
To cap the link speed, change the "pcie-max-link-speed" variable to the maximum generation you want to support and re-IPL the machine. For instance, to cap at PCIe Generation 3, in the petitboot command line type:<br />
<br />
<nowiki>nvram -p ibm,skiboot --update-config pcie-max-link-speed=3</nowiki><br />
<br />
== bootargs ==<br />
<br />
=== Description ===<br />
Skiroot kernel command line parameters<br />
<br />
=== Details ===<br />
Controls the arguments passed to the skiroot kernel. For example, to prevent petitboot from appearing on the AST video output and prefer another GPU if available:<br />
<br />
<nowiki>nvram -p ibm,skiboot --update-config bootargs='modprobe.blacklist=ast'</nowiki><br />
<br />
== vas-user-space ==<br />
<br />
=== Description ===<br />
Enable the Virtual Accelerator Switchboard (VAS) userspace support<br />
<br />
=== Details ===<br />
This allows Linux 5.8 and up to interact with the VAS, which is currently used to provide a userspace interface to the nx-gzip accelerator. Note that this option requires skiboot 6.6 or newer, which is not currently shipped by any RCS firmware release.<br />
<br />
<nowiki>nvram -p ibm,skiboot --update-config vas-user-space=enable</nowiki></div>Mx08https://wiki.raptorcs.com/w/index.php?title=POWER9_Hardware_Compatibility_List&diff=3387POWER9 Hardware Compatibility List2020-11-08T05:11:02Z<p>Mx08: add links to TalosII/BB HCL pages</p>
<hr />
<div>General hardware compatibility:<br />
* [[POWER9 Hardware Compatibility List/Memory|Memory Compatibility]]<br />
* [[POWER9 Hardware Compatibility List/PCIe Devices|PCIe Device Compatibility]]<br />
<br />
Board-specific hardware compatibility:<br />
* [[Talos_II/Hardware_Compatibility_List|Talos II Hardware Compatibility List]]<br />
* [[Blackbird/Hardware_Compatibility_List|Blackbird Hardware Compatibility List]]<br />
<br />
Chassis compatibility:<br />
* [[Talos II/Hardware Compatibility List|Talos II Chassis Compatibility]]<br />
* [[Blackbird/Hardware Compatibility List|Blackbird Chassis Compatibility]]<br />
<br />
[[Category:POWER9]]<br />
[[Category:Compatibility List]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&diff=3385Operating System Compatibility List2020-10-21T12:08:29Z<p>Mx08: /* BSDs */ OpenBSD 6.8 now officially supported + remove redundant link</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://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://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://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="5"|[https://cdimage.debian.org/cdimage/ Debian]<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 />
|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 />
|rowspan="6"|[https://alt.fedoraproject.org/alt/ Fedora]<br />
|32<br />
|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 />
|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 />
|rowspan="2"|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 />
|[[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 />
|-<br />
|17.0<br />
|ppc64<br />
|[[User:MarcusC|MarcusC]]<br />
|XFCE4 and virt-manager verified<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 />
|rowspan="3"|[https://www.ubuntu.com/download/server/power Ubuntu Server]<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="3"|[http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ Whonix] ([https://www.whonix.org/ clearnet link])<br />
|15<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 />
|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 />
|14<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 />
|12.0<br />
|ppc64<br />
|[[User:kev009|kev009]]<br />
|Contains initial POWER9 support<br />
|-<br />
|13-CURRENT<br />
|ppc64<br />
|[[User:kev009|kev009]]<br />
|Ongoing development activity, better than releases for the time being<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 />
* NixOS (@crystalgamma:matrix.org on Matrix)<br />
* GuixSD ([[User:Isengaara|Isengaara]])<br />
<br />
== External Links ==<br />
<br />
* [http://bgafc.t-hosting.hu/oses4ppc.php Operating Systems for PowerPC] PPC32be / PPC64be / PPC64le<br />
<br />
[[Category:Compatibility List]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Debricking_the_BMC&diff=3382Debricking the BMC2020-10-10T09:31:39Z<p>Mx08: /* Flash new BMC firmware via serial port (Proprietary Method) */ fix typo</p>
<hr />
<div>==Purpose==<br />
This guide explains how to debrick the BMC when the BMC has been rendered inoperable, for example due to a defective firmware update.<br />
<br />
==Applicability==<br />
All RCS [[OpenPOWER]] systems.<br />
<br />
==Overview==<br />
There are three means of debricking the BMC:<br />
<br />
* Remove the BMC SPI flash chip and reflash it with a flash programmer<br />
** Note: [https://www.flashrom.org/Flashrom flashrom] versions earlier than 1.1 do not support the BMC flash chip<br />
* Flash new BMC firmware via U-Boot TFTP (requires that U-Boot is still intact on the flash)<br />
* Flash new BMC firmware via serial port (requires proprietary BMC chip vendor tool)<br />
<br />
==Reset persistent storage==<br />
This is applicable if somehow the persistent storage (SSH keys, passwords, IPMI error logs, etc.) has been corrupted, but the read only data (U-boot, kernel, initramfs) are all intact. This is also the easiest and least invasive recovery method if you have forgotten the BMC password.<br />
<br />
From the U-boot prompt on the BMC serial console, run the following (must be run quickly, to avoid watchdog timeouts):<br />
<br />
<code>printenv</code><br />
<br />
Look at the bootargs command, set the same environment variable but insert <code>overlay-filesystem-in-ram</code> before the <code>rw</code> keyword.<br />
<br />
Example for Blackbird HW version 1.01:<br />
<br />
<code>setenv bootargs console=ttyS4,115200n8 root=/dev/ram overlay-filesystem-in-ram rw</code><br />
<br />
Then run <code>boot</code> to continue the boot process.<br />
<br />
This will start the BMC with default settings, but the existing persistent data has not yet been cleared. To clear it, log in as root, then run:<br />
<br />
<code>flash_eraseall /dev/mtd/rwfs</code><br />
<br />
<code>reboot</code><br />
<br />
==Flash new BMC firmware via U-Boot TFTP==<br />
'''Note:''' While these instructions have been successfully applied in practice, they are still preliminary. Ask questions in IRC if you are unclear on what to do!<br />
<!-- Hi fellow wiki people! Ask Bdragon in IRC if you have questions about this procedure. <br />
IRC user dragon_pilot was successfully able to recover a nonworking BMC from u-boot, these instructions are the result of that experiment.<br />
Further testing and refinement would be appreciated, preferably by someone who has easy access to an external flasher.<br />
--><br />
<br />
In the event of a failure when updating the BMC, but with a functioning U-boot, you can still recover by using U-Boot to manually bootstrap the BMC by manually loading a boot image over the network or the BMC serial port.<br />
<br />
If your BMC flash is corrupted to the extent that U-Boot does not load properly, these instructions will not work; you will need to remove and reflash the BMC flash chip externally, or flash new firmware [[#Flash new BMC firmware via serial port|via serial port]].<br />
<br />
* Prepare a TFTP server, and place <code>image-bmc</code>, <code>image-rofs</code>, and <code>image-kernel</code> in the root.<br />
<br />
* Connect a serial console to the [[Talos_II/Building_FAQ#BMC_serial_port_J7701|BMC serial port]] (J7701, serial port bracket required). The serial port configuration is <tt>115200,8n1</tt>.<br />
* Disconnect and reconnect power to the machine to force a BMC restart. Press a key to interrupt auto-boot when prompted.<br />
* If you are having trouble with U-Boot resetting while you are trying to run these steps, have a slow network, or you are going to be loading over serial, you can [[Debricking the BMC/Watchdog|disable the FPGA watchdog]].<br />
* Run <code>dhcp x.x.x.x:image-bmc</code>, replacing the IP address of your TFTP server. This will load a copy of the stock boot image into RAM.<br />
* Run <code>bootm 83080000</code>. This will prepare and boot off of the loaded virtual image.<br />
* If your rofs partition is not functional, you will be dropped into the systemd emergency shell at this point. Try both the password you set as well as the default <code>0penBmc</code>, it may be one or the other depending on the state of the rwfs partition. If it boots up properly instead of dropping you into the emergency shell, the problem is probably in your kernel partition and you can retry flashing your <code>image-kernel</code> using the normal procedure. (The rest of these instructions are for the systemd emergency shell.)<br />
* <code>mount -t tmpfs none /tmp</code><br />
* run <code>udhcpc</code> to get an IP address. (TODO: verify that this is the actual command that you run. Do you have to specify the network interface too?)<br />
* <code>cd /tmp</code><br />
* <code>tftp -g -r image-rofs x.x.x.x</code><br />
* <code>tftp -g -r image-kernel x.x.x.x</code><br />
* IMPORTANT: Use <code>md5sum</code>, <code>sha1sum</code>, or <code>sha256sum</code> to verify successful transfer of image-rofs and image-kernel! tftp is a very barebones protocol and relies on transport layer checksumming, which is optional and not always available in UDP!<br />
* Verify that the output of <code>cat /sys/class/mtd/mtd3/name</code> is <code>kernel</code> and the output of <code>cat /sys/class/mtd/mtd4/name</code> is <code>rofs</code>. We will be flashing mtd partitions directly in the next step and this is the last chance to verify that they will be flashed to the correct partition.<br />
* <code>flashcp -v image-kernel /dev/mtd3</code><br />
* <code>flashcp -v image-rofs /dev/mtd4</code><br />
* (TODO: Describe how to reset rwfs in case it was damaged as well?) note: the kernel param for bypassing rwfs is "overlay-filesystem-in-ram". Append it to the existing boot-args before running the bootm command. This can also be used as part of a password reset procedure.<br />
* After the flash is complete, you can run restart the BMC and it should boot successfully.<br />
<br />
* (TODO: Discussion of using Kermit to upload the image without network access) note: I (Bdragon) have successfully done a ram-only boot using cu's built in xmodem support (escape sequence ~X) to do an image transfer into RAM over the BMC serial interface.<br />
* (TODO: Discuss using u-boot's built in cmp tool to perform basic validation of the u-boot image against a second copy loaded into RAM.)<br />
* (TODO: Load recovery images over USB?) note: The onboard USB port is connected to the USB switch after all, so this might be problematic.<br />
* (TODO: Discussion of u-boot memory map) Short version is: flash lives at 0x20000000 and default base address for the memory loading tools is 0x83000000. So add 0x63000000 to any flash address to get the eqivilent address for an image-bmc file loaded into RAM. For example, the bootable image of a loaded image-bmc is at 0x83080000.<br />
<br />
==Flash new BMC firmware via serial port (Open Source Method)==<br />
<br />
Tools required:<br />
<br />
* [[Talos_II/Building_FAQ#BMC_serial_port_J7701|BMC serial port]]<br />
* A secure computer with a serial port (usb to serial works fine) - preferably running linux (Linux on POWER is fine).<br />
<br />
Software:<br />
* flashrom with serial ASpeed flash support from [https://gitlab.raptorengineering.com/raptor-engineering-public/ast2050-flashrom]<br />
<br />
* BMC Firmware bundle: [[Talos_II/Firmware Firmware]] BMC [[:File:Talos_ii_openbmc_v1.07_bundle.tar.bz2| System Package 1.06 2a92dec044239591244b6ed69c3fac162a6b9ea4]]<br />
<br />
Procedure:<br />
<br />
# Build flashrom on your Linux or BSD PC.<br />
# Extract the BMC firmware bundle.<br />
# Set the FPGA RUN/RESET switch to RESET.<br />
#* On a Blackbird, this switch is located roughly between the flash chips and the PCIe slots. If you have a GPU installed in the x16 slot, you may need to remove it.<br />
# Apply standby power to the mainboard<br />
# Run the following command '''./flashrom --verbose --programmer 'ast2400:serial=/dev/ttyUSB0,cpu=halt,spibus=0' -c MX25L25635F/MX25L25645E/MX25L25665E -w image-bmc'''<br />
#* if your serial interface can handle the baudrate 921600 add the parameter:'' ''' high_speed_uart=true'''<br />
#* NOTE: If you are using updated firmware (Talos II/Lite 2.0 beta firmware or later) or are using a Blackbird, U-boot will shut down access to this interface after about 3 seconds of standby power, so you will need to run the command *immediately* after plugging in the power supply to bypass this.<br />
# Be Patient: this will take a *long* time.<br />
# Once the flash has been verified, set the FPGA RUN/RESET switch to RUN.<br />
<br />
==Flash new BMC firmware via serial port (Proprietary Method)==<br />
<br />
''This method was discovered by Centurion Dan as an alternative to pulling and reflashing the BMC SPI chip after a failed update had corrupted/wiped U-Boot.''<br />
<br />
Tools required:<br />
<br />
* [[Talos_II/Building_FAQ#BMC_serial_port_J7701|BMC serial port]]<br />
* An x86 computer with a serial port (usb to serial works fine) - preferably running linux.<br />
<br />
Software:<br />
* Proprietary SOC Flash Utility from [https://www.aspeedtech.com/support.php Aspeed Technology's Support Page]: at least version [http://upload.aspeedtech.com/SOC/v11800.zip 1.18.00]. Since version 1.20.x Aspeed requires being registered as developer to download this util:<br />
<br />
ASPEED SOC Flash Utility --- The utility has been moved to Document Download Page for ASPEED registered developers to access.<br />
<br />
* BMC Firmware bundle: [[Talos_II/Firmware Firmware]] BMC [[:File:Talos_ii_openbmc_v1.07_bundle.tar.bz2| System Package 1.06 2a92dec044239591244b6ed69c3fac162a6b9ea4]]<br />
<br />
Procedure:<br />
<br />
# Unzip the SOC FLASH Utility on your other computer, and unzip the appropriate SOC Flash Utility bundle for that computer.<br />
# Extract the BMC firmware bundle.<br />
# Run the following command '''./socflash -s option=u comport="4" cs=0 if=image-u-boot gpio_b=S71 gpio_a=S70 option=f'''<br />
#* You can drop the'' '''option=f''' ''for a slower but verified write process''<br />
#* if your serial interface can handle the baudrate 921600 add the parameter:'' ''' baudrate=921600'''<br />
#* if you want to see what is going on, you can strace it by prepending:'' '''strace -e trace=open,close,read,write''' to the command above.<br />
#* NOTE: If you are using updated firmware (Talos II/Lite 2.0 beta firmware or later) or are using a Blackbird, U-boot will shut down access to this interface after about 3 seconds of standby power, so you will need to run the command *immediately* after plugging in the power supply to bypass this.<br />
# Be Patient: it took me about 45 minutes to complete the flash process.<br />
<br />
Notes:<br />
* ''gpio_b=S71'' and ''gpio_a=S70'' are used to turn off the fpga watchdog timer before the flash process and then re-enables it after it's completed.<br />
* On a Blackbird, replace ''gpio_b=S71'' with ''gpio_b=G01'' and ''gpio_a=S70'' with ''gpio_a=G00''. Due to the new HDMI interface, the BMC watchdog GPIO was moved to a different pin on the AST2500.<br />
<br />
[[Category:Guides]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=RCS_Platform_Comparison&diff=3310RCS Platform Comparison2020-07-31T18:19:12Z<p>Mx08: remove notes about PCIe extension. reason: OCuLink port on Talos 2 has wrong wiring (custom adapter needed), and PCIe risers don't increase PCIe slot count.</p>
<hr />
<div><br />
Here is a quick comparison to help people get started with the platform.<br />
<br />
Some details have been omitted, this page is intended to give a high-level overview without too much clutter.<br />
<br />
Purchasing overview:<br />
* consider the single CPU board, '''[[Talos II]] Lite''' as your '''default''' option, it offers best performance for a single CPU with all four memory channels loaded<br />
** if you really need '''more''' than 22 CPU cores or more than 2 PCIe slots, consider the full [[Talos II]] but be conscious of extra PSU requirements<br />
** if you really need something '''compact''' and potentially portable, consider the Blackbird due to its MicroATX form factor but be aware that you are constrained to only 8 CPU cores (4 threads/core), only 2 memory channels and you need to be careful to choose a case the meets noise and cooling expectations for this board<br />
<br />
{| class="wikitable"<br />
|-<br />
! Feature !! [[Talos II]] !! [[Talos II]] Lite !! [[Blackbird]] !! [[Condor]]<br />
|-<br />
| Production || Y || Y || Y || postponed<br />
|-<br />
| Reasons to buy || most CPU cores,<br/>max RAM speed,<br/>need >2 PCIe slots || Cheaper but still 22 cores || Cheapest,<br/>integrated peripherals,<br/>smaller size || - <br />
|-<br />
| Price (USD)<ref group="note">please see online shop for latest prices, and be aware that bundles may discount prices if also purchasing CPUs and HSFs. Last updated 2020-07-31.</ref> || 3194.66 || 1502.57 || '''1310.99''' || -<br />
|-<br />
| RYF Certified<ref group="note">Certified by the Free Software Foundation's [https://ryf.fsf.org/vendors/raptor Respects Your Freedom] program</ref> || Y || Y || ? || ?<br />
|-<br />
| Size || EATX || EATX || '''Micro ATX''' || ATX<br />
|-<br />
| CPU count || '''2''' || 1 || 1 || 1<br />
|-<br />
| CPU max cores || '''22''' || '''22''' || 8 || ?<br />
|-<br />
| Memory channels || '''8'''<br/>(4 per CPU) || '''4''' || 2 || '''8'''<br />
|-<br />
| Memory channels×speed<ref group="note">channels multiplied by maximum speed in MHz</ref> || '''21 336'''<br/>(10 668 ''per CPU'') || 10 668 || 5334 || ?<br />
|-<br />
| PCIe 4.0 16x slots<ref group="note">All x16 slots on Talos II (and Lite) and Blackbird are CAPI 2 capable</ref> || '''3'''<ref group="note" name="t2-1cpu-limit">on Talos II, only 2 PCIe slots are available with a single CPU; two CPUs must be installed for all slots to be available</ref> || 1 || 1 || 4?<br />
|-<br />
| PCIe 4.0 8x slots || '''2'''<ref group="note" name="t2-1cpu-limit"/> || 1 || 1 || ?<br />
|-<br />
| μPCIe ports || '''1''' || 0 || 0 || ?<br />
|-<br />
| Video || VGA || VGA || '''HDMI''' || ?<br />
|-<br />
| USB 3.0 ports || 4 || 4 || 4 || ?<br />
|-<br />
| Storage || ''Optional 4x SAS/SATA'' || ''Optional 4x SAS/SATA'' || 4x SATA || ?<br />
|}<br />
<references group="note"/></div>Mx08https://wiki.raptorcs.com/w/index.php?title=POWER9&diff=3230POWER92020-05-07T09:42:01Z<p>Mx08: Undo revision 3189 by Borley (talk) Reason: 1) no source mentioned, 2) no information on the conditions (did other system parameters stay the same? several test runs? which spectre mitigations were enabled during the test?) under which the benchmark was made, 3) IMO this page/section is not appropriate for this kind of benchmark results, given that it otherwise contains very concise, technical information introducing POWER9 and its variants.</p>
<hr />
<div>{{Infobox<br />
|title = Processor Information<br />
|header1 = POWER9<br />
|label2 = [[Power ISA|Power ISA]]<br />
|data2 = 3.0B<br />
|label3 = Process node<br />
|data3 = 14nm<br />
|label4 = Maximum slices<br />
|data4 = 24<br />
|label5 = Maximum cores<br />
|data5 = 12 [[SMT8|SMT8]] / 24 [[SMT4|SMT4]]<br />
|label6 = L2 cache / slice<br />
|data6 = 512kB<br />
|label7 = L3 cache / slice<br />
|data7 = 10MB<br />
|label8 = Production availability<br />
|data8 = January 2018<br />
|label9 = Production stepping(s)<br />
|data9 = (Nimbus) DD2.2, DD2.3<br />
|label10 = [[POWER8E|← POWER8E]]<br />
|data10 = [[POWER10|POWER10 →]]<br />
}}<br />
<br />
POWER9 is IBM's most recent POWER compatible server and workstation CPU ([[Power ISA|POWER ISA]] v3.0B). Built on a 14nm process, each CPU package can contain up to 24 [[SMT4|SMT4]] cores or 12 [[SMT8|SMT8]] cores. Each pair of [[SMT4|SMT4]] cores, or singleton [[SMT8|SMT8]] core, comprises a slice; each slice in turn contains 512kB L2 cache and 10MB L3 cache. Raptor Computing Systems' 4- and 8-core processors provide unpaired cores, such that one [[SMT4|SMT4]] core per slice is fused off. This allows each of the [[SMT4|SMT4]] cores to utilize the full cache of the slice exclusively, increasing performance for these [[Single_Thread|ST]]-focused processors.<br />
<br />
==Process==<br />
POWER9 is fabricated using the GlobalFoundries 14HP (High Performance) process. This is distinct from the GlobalFoundries 14LPP (Low Power) process used by other GF 14nm customers, and is believed to be an IBM-specific process using ex-IBM Microelectronics intellectual property. The process is also used for the CPUs in IBM's z14 mainframes.<ref>Schor, David. [https://fuse.wikichip.org/news/956/globalfoundries-14hp-process-a-marriage-of-two-technologies/ GlobalFoundries 14HP process, a marriage of two technologies]. Wikichip Fuse.</ref><br />
<br />
== Chips ==<br />
<br />
There are three known silicon masks of POWER9:<br />
* Nimbus (POWER9 [[Scale Out]])<br />
* Cumulus (POWER9 [[Scale Up]])<br />
* Axone (POWER9&prime; ("POWER9 Prime"), aka POWER9 with Advanced I/O)<br />
<br />
Nimbus is the &#8220;[[Scale Out|scale out]]&#8221; variant and uses direct-attach DDR4 memory. Cumulus is the &#8220;[[Scale Up|scale up]]&#8221; version and uses [[Centaur]] memory buffers, allowing larger amounts of memory to be attached to a system.<br />
<br />
Chips can be fused as [[SMT4]] or [[SMT8]] during manufacturing. The [[SMT8]] variant essentially fuses each pair of cores into one &#8220;core&#8221;, halving the core count while doubling the number of threads per core. [[SMT4]] variants are intended for [[PowerNV]] platforms running Linux, and [[SMT8]] variants are intended for use with IBM's PowerVM hypervisor which can run Linux, AIX or IBM i.<ref>Stuecheli, Jeff. POWER9. Presentation for [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Power+Systems/page/AIX+Virtual+User+Group+-+USA AIX VUG]. ([https://public.dhe.ibm.com/systems/power/community/aix/Central-VUG-Replays/2017-01-26_IBM_POWER9.wmv video download], [https://www.ibm.com/developerworks/community/wikis/form/anonymous/api/wiki/61ad9cf2-c6a3-4d2c-b779-61ff0266d32a/page/1cb956e8-4160-4bea-a956-e51490c2b920/attachment/56cea2a9-a574-4fbb-8b2c-675432367250/media/POWER9-VUG.pdf slides], [[User:Torpcoms/Timemark/POWER9|timemarks]])</ref><br />
<br />
=== Steppings ===<br />
<br />
Several revisions of the Nimbus mask have been issued:<br />
<br />
* DD2.1 was the final preproduction revision before GA. It has errata preventing the use of hardware virtualization, but DD2.1 Sforza can be used in e.g. the [[Talos II]] if this functionality is not needed.<br />
* DD2.2 is the first GA revision of Nimbus. DD2.2 Sforza is sold by RCS as simply "POWER9", implying version 1.<br />
* DD2.3 is an updated revision of Nimbus, adding [[Power ISA/Privilege States#Ultravisor State|Ultravisor]] functionality, Hardware watchpoint support, and improved Meltdown and Spectre mitigations. DD2.3 parts are sold by RCS as "POWER9 v2".<br />
<br />
== Modules ==<br />
<br />
{| class="wikitable"<br />
|+ POWER9 Modules<br />
! Chip<br />
! Module<br />
! Memory Channels<br />
! XBUS Lanes<br />
! PCIe Lanes<br />
! OpenCAPI Lanes<br />
! Socket<br />
|-<br />
!rowspan="3"|Nimbus<br />
| [[Sforza]]<br />
| 4<br />
| 1<br />
| 48<br />
| 0<br />
| LGA 2601<br />
|-<br />
| [[Monza]]<br />
| 8<br />
| 1<br />
| 34<br />
| 48<br />
| LGA 3899<br />
|-<br />
| [[LaGrange]]<br />
| 8<br />
| 2<br />
| 42<br />
| 16<br />
| LGA 3899<br />
|-<br />
! Cumulus<br />
| (unknown)<br />
| (memory attached via [[Centaur|Centaurs]])<br />
| (unknown)<br />
| (unknown)<br />
| (unknown)<br />
| ?<br />
|-<br />
! Axon<br />
| (unknown)<br />
| (memory attached via OMI)<br />
| Up to 3<br />
| Up to 48<br />
| Up to 48<br />
| ?<br />
|}<br />
<br />
'''''XBUS''' is used for inter-processor communication on dual-socket system''<br />
<br />
=== Nimbus ===<br />
<br />
Nimbus chips are available in three different modules: [[Sforza]], [[Monza]], and [[LaGrange]]. Each module uses the same silicon mask but is packaged differently, exposing different I/O functionality to the host platform, allowing purpose-built systems to be constructed in addition to more general-purpose computers.<br />
<br />
'''[[Sforza|Sforza]]''' is the most flexible of these packages, providing PCIe 4.0 lanes as the main I/O resource, and is what [[Talos_II|Talos™ II]] uses for maximal similarity to existing desktop, workstation, and server systems.<br />
<br />
'''[[Monza|Monza]]''' modules offer the most OpenCAPI/NVLink bandwidth and are used in IBM's AC922 (Witherspoon) systems, such as those used by the Sierra and Summit supercomputers.<br />
<br />
'''[[LaGrange|LaGrange]]''' modules offer increased XBus bandwidth between processor sockets and are used by the Google/Rackspace Zaius motherboard used in the Barreleye G2 system.<ref>Gangidi, Adi [https://blog.rackspace.com/zaius-barreleye-g2-server-development-update-2 Zaius/Barreleye G2 Server Development Update]. 2017-11-13</ref><br />
<br />
Part numbers for different POWER9 Sforza SKUs can be found on page 58 of the [[:File:POWER9 Sforza DS v16 23JUL2018 pub.pdf|datasheet]]. These part numbers are printed on the surface of the CPU module and can be used to determine the type of the CPU.<br />
<br />
=== Cumulus ===<br />
<br />
Little is known about Cumulus chips at this time; as Scale Up chips, they will trade some I/O bandwidth for support for more than two sockets.<ref>Morgan, Timothy Prickett. [https://www.nextplatform.com/2017/12/05/power9-to-the-people/ POWER9 to the People]. 2017-12-05</ref><br />
<br />
=== Axone ===<br />
<br />
Branded POWER9&prime; ("POWER9 Prime"), also known as POWER9 with Advanced I/O. Newly announced in August 2019. Uses serial memory attachment via OMI, an evolution from the [[Centaur]].<br />
<br />
== References ==<br />
<br />
<references/><br />
<br />
== Resources ==<br />
<br />
* '''[[:Category:Documentation|POWER9 CPU and Platform Documentation]]'''<br />
* [[POWER9 Hardware Compatibility List]]<br />
* [[:File:POWER9-Features-and-Specifications.pdf|Basic POWER9 overview presentation]]<br />
* [[:File:PowerISA_public.v3.0B.pdf|Power ISA version 3.0B]] - implemented by POWER9<br />
<br />
== External Links ==<br />
<br />
* [https://en.wikipedia.org/wiki/POWER9 POWER9 English Wikipedia page]<br />
* [https://en.wikichip.org/wiki/ibm/microarchitectures/power9 POWER9 wikichip page]<br />
[[Category:POWER9|*]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Blackbird&diff=3229Blackbird2020-05-07T09:30:34Z<p>Mx08: /* Notes */</p>
<hr />
<div>[[File:Blackbird_board_store_image_bright.png|thumb|C1P9S01 Mainboard]]<br />
<br />
'''Blackbird™''' is an adaptation of [[Raptor Computing Systems|Raptor Computing Systems]]' next-generation [[POWER9|POWER9]] platform to the μATX (microATX) form factor. Focusing on the desktop use case, it is a single socket [[PowerNV]] system.<br />
<br />
== Mainboard ==<br />
<br />
[[File:C1P9S01_block_diagram_from_user_manual.png|thumb|C1P9S01 Block Diagram]]<br />
<br />
=== Specifications ===<br />
<br />
{| class="wikitable sortable"<br />
! style="text-align:left;"| Mainboard Part #<br />
! style="text-align:left;"| Form Factor<br />
! style="text-align:left;"| CPU Type<br />
! style="text-align:left;"| Networking<br />
! style="text-align:left;"| Storage Controller<br />
|-<br />
|C1P9S01<br />
|MicroATX<br />
|POWER9 [[Sforza|Sforza]]<br />
|3x GbE (Broadcom [[BCM5719|BCM5719]])<br />
|4x SATA<br />
|}<br />
<br />
* MicroATX form factor<br />
* One LGA 2601 socket accepting a [[POWER9]] [[Sforza]] CPU with TDP ≤ 160 W<br />
* Two DDR4 1600/1866/2133/2400/2666 ECC registered RAM slots, dual-channel, supporting up to 256GB main memory<br />
* Three Gigabit Ethernet ports provided by a Broadcom [[BCM5719]] chip<br />
* Four SATA ports provided by a firmware-free Marvell [[88SE9235]] SATA chip<br />
* 5.1 audio supporting analog and S/PDIF outputs<br />
* HDMI output via BMC (2D framebuffer), using a firmware-free [[IT66121FN]] PHY chip<br />
* Four USB 3.0 ports (2x rear, 2x on header for front panel) via firmware-free [[TUSB7340]] XHCI chip<br />
* One additional internal USB 2.0 Type-A port<br />
* One x16 PCIe Gen4 slot (CAPI2-capable)<br />
* One x8 PCIe Gen4 slot<br />
* [[AST2500]] BMC with OpenBMC<br />
* One Lattice ICE40HX1K-VQ100 FPGA controller<br />
<br />
=== Notes ===<br />
* 4-core and 8-core CPUs are officially supported.<br />
* Other CPUs (CPUs with a TDP greater than 160W) may operate without WoF due to power regulator limitations.<br />
* Of the three Ethernet ports on the back panel, the one above the USB ports is the one that is shared with the BMC.<br />
<br />
== Energy consumption ==<br />
<br />
NOTE: numbers are approximate and may vary. System power measured at wall with standard instruments. CPU power reported by [[OCC|OCC]].<br />
<br />
{| class="wikitable sortable"<br />
! style="text-align:left;"| Component<br />
! style="text-align:left;"| Design Power<br />
! style="text-align:left;"| Power Use (Idle)<br />
! style="text-align:left;"| Power Use (Full Load)<br />
! style="text-align:left;"| Additional Information<br />
! Source<br />
|-<br />
|4-core CPU (02CY297): DD2.2, 2.15/3.8 GHz<br />
|90W<br />
|54W<br />
|94W<br />
|Measured at the wall. PSU: be quiet! Straight Power 11 450W 80+ Gold<br />
|[[User:MPC7500|MPC7500]]<br />
|-<br />
|8-core CPU (02CY089): DD2.2, 3.45/3.8 GHz<br />
|160W<br />
|28-30W<br />
|114W<br />
|Load generated via <code>stress --cpu 32</code>. CPU frequency scheduler: <code>ondemand</code>. Data reported by <code>lm_sensors</code>.<br />
|[[User:Mx08|Mx08]]<br />
|-<br />
|Blackbird 8-core bundle (BK1B02) with 2x 32GB RAM<br />
|<br />
|54W<br />
|164W<br />
|Load generated via <code>stress --cpu 32</code>. CPU frequency scheduler: <code>ondemand</code>. PSU: Seasonic PRIME 850W 80+ Platinum<br />
|[[User:Mx08|Mx08]]<br />
|-<br />
|BMC (AST 2500)<br />
|<br />
|3.5W<br />
|<br />
|Measured at the wall. PSU: Seasonic PRIME 850W 80+ Platinum<br />
|[[User:Mx08|Mx08]]<br />
|}<br />
<br />
== Support ==<br />
* [[:File:C1P9S01_users_guide_version_1_0.pdf|C1P9S01 User's Guide For Configuration and Setup]] is the primary user manual for Blackbird<br />
* [[Blackbird/Hardware Compatibility List|Blackbird/Hardware Compatibility List]]<br />
<br />
== See also ==<br />
<br />
* [[Talos II|Talos II]] - dual socket, EATX cousin<br />
* [[Talos II/Building FAQ]]<br />
* [[Blackbird/Building FAQ]]<br />
<br />
== External Links ==<br />
<br />
* [https://www.raptorcs.com/BB/ Blackbird homepage] at Raptor Computing Systems' website<br />
<br />
* https://twitter.com/RaptorCompSys/status/1048373354695208960 - a thread on twitter with various Q and A<br />
* https://www.phoronix.com/scan.php?page=news_item&px=Raptor-Blackbird-Announced<br />
* https://www.phoronix.com/scan.php?page=news_item&px=Raptor-Blackbird-Details<br />
<br />
[[Category:Raptor Computing Systems (RCS) Platforms]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Sforza&diff=3228Sforza2020-05-07T09:18:10Z<p>Mx08: /* Configurations */ mark 02CY296 as 'sold by raptor', too</p>
<hr />
<div>{{Infobox<br />
|title = Package Information<br />
|header1 = Sforza<br />
|label2 = Processor<br />
|data2 = [[POWER9|POWER9]]<br />
|label3 = Chip<br />
|data3 = Nimbus<br />
|label4 = Maximum base clock<br />
|data4 = 3.1GHz (4/8 core)<br />
|label5 = Maximum [[WOF|WOF]] clock<br />
|data5 = 3.8GHz (4/8 core)<br />
|label6 = Maximum [[TDP|TDP]]<br />
|data6 = 190W<br />
|label7 = PCIe controllers ([[PEC|PEC]])<br />
|data7 = 3<br />
|label8 = PCIe generation<br />
|data8 = 4<br />
|label9 = Maximum PCIe lanes<br />
|data9 = 48<br />
|label10 = Maximum PCIe endpoints<br />
|data10 = 6<br />
|label11 = [[CAPI 2.0|CAPI 2.0]] interfaces<br />
|data11 = 2<br />
|label12 = [[OpenCAPI|OpenCAPI]] interfaces<br />
|data12 = 0<br />
|label13 = [[NVLink|NVLink]] interfaces<br />
|data13 = 0<br />
}}<br />
<br />
''For more general information about the Nimbus chip this module contains, such as details about particular steppings, please see [[Nimbus|Nimbus]].''<br />
<br />
'''Sforza''' is the codename for a [[POWER9|POWER9]], [[Nimbus|Nimbus]] chip, CPU module/package designed for general purpose computing, with high I/O available over standard PCIe generation 4 interfaces. The Nimbus chip it houses has 24 cores on the die, each capable of SMT4, and as a [[Scale Out]] processor intended for dual socket systems, uses directly attached RAM.<br />
<br />
It is used by the [[Talos_II|Talos™ II]] systems.<br />
<br />
== Configurations ==<br />
As with many CPUs, Nimbus-Sforza modules can be sold with some number of CPU cores disabled, and with different default clock speeds; at this time, no known Nimbus-Sforza parts are available with all 24 cores enabled.<br />
<br />
<!-- using question marks to denote uncertainty for part number is guessed, hopefully we can confirm with Raptor later --><br />
{| class="wikitable sortable"<br />
|+ Parts sold by RCS<br />
! Part<br />
! SKU<br />
! Name<br />
! Cores<br />
! Stepping<br />
! TDP<br />
|-<br />
| 02CY297<br />
| [https://raptorcs.com/content/CP9M01/intro.html CP9M01]<br />
| IBM POWER9 CPU (4-Core)<br />
| 4<br />
| DD2.2<br />
| 90 W<br />
|-<br />
| 02CY089<br />
| [https://raptorcs.com/content/CP9M02/intro.html CP9M02]<br />
| IBM POWER9 CPU (8-Core)<br />
| 8<br />
| DD2.2<br />
| 160 W<br />
|-<br />
| 02CY489<br />
| [https://raptorcs.com/content/CP9M06/intro.html CP9M06]<br />
| IBM POWER9 CPU (18-Core)<br />
| 18<br />
| DD2.2<br />
| 190 W<br />
|-<br />
| 02CY296?<br />
| [https://raptorcs.com/content/CP9M08/intro.html CP9M08]<br />
| IBM POWER9 CPU (22-Core)<br />
| 22<br />
| DD2.2<br />
| 190 W<br />
|-<br />
| 02CY650<br />
| [https://raptorcs.com/content/CP9M31/intro.html CP9M31]<br />
| IBM POWER9 v2 CPU (4-Core)<br />
| 4<br />
| DD2.3<br />
| 90 W<br />
|-<br />
| 02CY649 <!-- confirmed by ClassicHasClass on the forum https://forums.raptorcs.com/index.php/topic,74.msg896.html#msg896 --><br />
| [https://raptorcs.com/content/CP9M32/intro.html CP9M32]<br />
| IBM POWER9 v2 CPU (8-Core)<br />
| 8<br />
| DD2.3<br />
| 160 W<br />
|}<br />
<br />
{| class="wikitable sortable"<br />
|+ All known Sforza parts<br />
! Part<br />
! Cores<br />
! Stepping<br />
! Nest/Boost/Base (GHz)<br />
! Max<br />
|-<br />
|style="background:#8cf"| 02CY296<br />
|rowspan=2| 22<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/2.75<br />
|rowspan=2| 190 W<br />
|-<br />
| 02CY642<br />
| DD2.3<br />
|-<br />
| 02CY227<br />
|rowspan=2| 22<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/2.60<br />
|rowspan=2| 190 W<br />
|-<br />
| 02CY639<br />
| DD2.3<br />
|-<br />
| 02CY228<br />
|rowspan=2| 20<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/2.70<br />
|rowspan=2| 190 W<br />
|-<br />
| 02CY637<br />
| DD2.3<br />
|-<br />
|style="background:#8cf"| 02CY489<br />
|rowspan=2| 18<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/2.80<br />
|rowspan=2| 190 W<br />
|-<br />
| 02CY646<br />
| DD2.3<br />
|-<br />
| 02CY230<br />
|rowspan=2| 16<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/2.90<br />
|rowspan=2| 190 W<br />
|-<br />
| 02CY640<br />
| DD2.3<br />
|-<br />
| 02AA986<br />
| 16<br />
| DD2.1<br />
| 1.600/3.80/2.90<br />
| 190 W<br />
|-<br />
| 02CY977<br />
|rowspan=2| 8<br />
| DD2.2<br />
|rowspan=2| 1.867/4.10/3.80<br />
|rowspan=2| 190 W<br />
|-<br />
| 02WP000<br />
| DD2.3<br />
|-<br />
| 02CY414<br />
|rowspan=2| 22<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/2.25<br />
|rowspan=2| 160 W<br />
|-<br />
| 02CY644<br />
| DD2.3<br />
|-<br />
| 02CY415<br />
|rowspan=2| 20<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/2.40<br />
|rowspan=2| 160 W<br />
|-<br />
| 02CY645<br />
| DD2.3<br />
|-<br />
| 02CY231<br />
|rowspan=2| 16<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/2.50<br />
|rowspan=2| 160 W<br />
|-<br />
| 02CY641<br />
| DD2.3<br />
|-<br />
| 02AA882<br />
| 16<br />
| DD2.1<br />
| 1.600/3.40/2.20<br />
| 160 W<br />
|-<br />
|style="background:#8cf"| 02CY089<br />
|rowspan=2| 8<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/3.50<br />
|rowspan=2| 160 W<br />
|-<br />
|style="background:#8cf"| 02CY649<br />
| DD2.3<br />
|-<br />
| 02CY416<br />
|rowspan=2| 18<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/2.25<br />
|rowspan=2| 130 W<br />
|-<br />
| 02CY647<br />
| DD2.3<br />
|-<br />
| 02CY417<br />
|rowspan=2| 16<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/2.30<br />
|rowspan=2| 130 W<br />
|-<br />
| 02CY648<br />
| DD2.3<br />
|- <!-- WikiChip and https://twitter.com/SamatJain/status/1246199602144927744 --><br />
| 02CY771<br />
|rowspan=2| 12<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/2.20<br />
|rowspan=2| 105 W<br />
|-<br />
| 02CY781<br />
| DD2.3<br />
|-<br />
|style="background:#8cf"| 02CY297<br />
|rowspan=2| 4<br />
| DD2.2<br />
|rowspan=2| 1.867/3.80/3.20<br />
|rowspan=2| 90 W<br />
|-<br />
|style="background:#8cf"| 02CY650<br />
| DD2.3<br />
|}<br />
<br />
Partly sourced from [[:File:POWER9_Sforza_DS_v18_13JUN2019_pub.pdf|Sforza datasheet]] (see Table 6-10 on page 59 in version 1.8)<br />
<br />
== See Also ==<br />
<br />
* [[LaGrange|LaGrange]] POWER9 module<br />
* [[Monza|Monza]] POWER9 module<br />
<br />
== External Links ==<br />
<br />
* [https://www-355.ibm.com/systems/power/openpower/tgcmDocumentRepository.xhtml?aliasId=POWER9_Sforza Sforza Module at IBM OpenPOWER portal]<br />
* [https://en.wikichip.org/wiki/ibm/cores/sforza WikiChip page for Sforza]<br />
<br />
[[Category:Modules]]<br />
[[Category:POWER9]]<br />
[[Category:Mainboard Components]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&diff=3163Operating System Compatibility List2020-04-15T09:59:41Z<p>Mx08: /* GNU/Linux */ fix typo (based on the summary of the previous edit, alpine is meant here)</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://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://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://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="5"|[https://cdimage.debian.org/cdimage/ Debian]<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 />
|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 />
|rowspan="6"|[https://alt.fedoraproject.org/alt/ Fedora]<br />
|32<br />
|ppc64le<br />
|[[User:Tle|Tle]]<br />
|Works perfectly!<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 />
|rowspan="2"|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 />
|[[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 />
|-<br />
|17.0<br />
|ppc64<br />
|[[User:MarcusC|MarcusC]]<br />
|XFCE4 and virt-manager verified<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 />
|rowspan="3"|[https://www.ubuntu.com/download/server/power Ubuntu Server]<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="3"|[http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ Whonix] ([https://www.whonix.org/ clearnet link])<br />
|15<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 />
|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 />
|14<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 />
|12.0<br />
|ppc64<br />
|[[User:kev009|kev009]]<br />
|Contains initial POWER9 support<br />
|-<br />
|13-CURRENT<br />
|ppc64<br />
|[[User:kev009|kev009]]<br />
|Ongoing development activity, better than releases for the time being<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 />
* NixOS (@crystalgamma:matrix.org on Matrix)<br />
* GuixSD ([[User:Isengaara|Isengaara]])<br />
<br />
== External Links ==<br />
<br />
* [http://bgafc.t-hosting.hu/oses4ppc.php Operating Systems for PowerPC] PPC32be / PPC64be / PPC64le<br />
<br />
[[Category:Compatibility List]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=STB&diff=3144STB2020-03-27T00:20:31Z<p>Mx08: add link to experimental guide Secure Boot with your own keys</p>
<hr />
<div>{{Glossary<br />
|name=Secure and Trusted Boot<br />
|abbr=STB<br />
|desc=Term used in OpenPOWER firmware to refer to secure boot and trusted (measured) boot functionality.<br />
}}<br />
<br />
==See also==<br />
<br />
* [[Secure Boot with your own keys]]<br />
<br />
==References==<br />
<br />
* [https://open-power.github.io/skiboot/doc/stb.html Skiboot documentation on Secure and Trusted Boot implementation]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Secure_Boot_with_your_own_keys&diff=3142Secure Boot with your own keys2020-03-27T00:17:03Z<p>Mx08: add disclaimer and reference to creator of the guide</p>
<hr />
<div>''Disclaimer: There may be a cleaner way to do this. This guide was created by [[User:Fizzbuzz|Fizzbuzz]] and successfully tested on a Blackbird system.''<br />
<br />
# Set up a Debian Stretch build environment in accordance with the instructions on the [[Compiling Firmware]] page.<br />
# Set environmental variables (for the purposes of this walkthrough and its helper functions) referring to the OpenPower build directory and the directory where you will be placing your firmware signing keys: <syntaxhighlight lang="bash" line='line'><br />
export OPBUILDDIR=~/blackbird-op-build<br />
export KEYDIR=~/new-keys<br />
</syntaxhighlight><br />
# Generate the keys you will be using to secure your hardware: <syntaxhighlight lang="bash" line='line'><br />
mkdir $KEYDIR<br />
cd $KEYDIR<br />
openssl ecparam -genkey -outform pem -noout -name secp521r1 -out hw_key_a.key<br />
openssl ecparam -genkey -outform pem -noout -name secp521r1 -out hw_key_b.key<br />
openssl ecparam -genkey -outform pem -noout -name secp521r1 -out hw_key_c.key<br />
openssl ecparam -genkey -outform pem -noout -name secp521r1 -out sw_key_a.key<br />
</syntaxhighlight><br />
# Edit <code>$OPBUILDDIR/openpower/configs/hostboot/blackbird.config</code> or <code>$OPBUILDDIR/openpower/configs/hostboot/talos.config</code> (depending on which system you have) and remove or comment out the <code>unset SECUREBOOT</code> line.<br />
# Follow the [[Compiling Firmware]] instructions for building the OpenPower firmware. Run <code>op-build menuconfig</code> before the final <code>op-build</code> if you want to customize your build in some way.<br />
# Replace the keys and key hashes in the pulled code with your own. I've provided some helper functions for this purpose and described the procedure below. <syntaxhighlight lang="bash" line='line'><br />
# Helper functions:<br />
<br />
get_keyhash () {<br />
$OPBUILDDIR/output/host/bin/create-container -v -w0 \<br />
-a $1/hw_key_a.key -b $1/hw_key_b.key -c $1/hw_key_c.key \<br />
--payload /dev/zero --imagefile /dev/null | grep "HW keys hash";<br />
}<br />
<br />
check_keys () {<br />
while read p;<br />
do echo `dirname $p`;<br />
get_keyhash `dirname $p`;<br />
echo '--';<br />
done <<< $(find -name hw_key_a.*)<br />
}<br />
<br />
replace_keys () {<br />
NEWKEYHASH=$(get_keyhash $KEYDIR);<br />
while read p; do<br />
OLDKEYHASH=$(get_keyhash `dirname $p`);<br />
if [ "$OLDKEYHASH" != "$NEWKEYHASH" ]; then<br />
echo "Replacing keys in `dirname $p`"<br />
cp -a $KEYDIR/. $(dirname $p)<br />
fi<br />
done <<< $(find -name hw_key_a.*)<br />
}<br />
<br />
check_imprints () {<br />
while read p; do<br />
echo "$p"<br />
cat $p | xxd -p<br />
done <<< $(find -name imprintHwKeyHash)<br />
}<br />
<br />
replace_imprints () {<br />
NEWIMPRINT=$(get_keyhash $KEYDIR | cut -d' ' -f8);<br />
while read p; do<br />
OLDIMPRINT=$(cat $p | xxd -p);<br />
OLDIMPRINT="${OLDIMPRINT//[$'\t\r\n ']}"<br />
if [ "$OLDIMPRINT" != "$NEWIMPRINT" ]; then<br />
echo "Replacing imprint $p"<br />
echo "$NEWIMPRINT" | xxd -p -r > $p<br />
fi<br />
done <<< $(find -name imprintHwKeyHash)<br />
}<br />
<br />
untar_code () {<br />
untar_pkg () {<br />
cd $OPBUILDDIR/dl/$1/<br />
tar xzf $1-*.tar.gz<br />
}<br />
untar_pkg hostboot<br />
untar_pkg libflash<br />
untar_pkg sb-signing-utils<br />
untar_pkg skiboot<br />
untar_pkg pnv-lpc<br />
cd $OPBUILDDIR<br />
}<br />
<br />
retar_code () {<br />
retar_pkg () {<br />
cd $OPBUILDDIR/dl/$1/<br />
tar czf $1-*.tar.gz $1-*/<br />
rm -fr $1-/<br />
}<br />
retar_pkg hostboot<br />
retar_pkg libflash<br />
retar_pkg sb-signing-utils<br />
retar_pkg skiboot<br />
retar_pkg pnv-lpc<br />
cd $OPBUILDDIR<br />
}<br />
<br />
# Procedure:<br />
<br />
cd $OPBUILDDIR<br />
untar_code<br />
replace_keys<br />
replace_imprints<br />
retar_code<br />
</syntaxhighlight> You can confirm the process worked by running <code>get_keyhash $KEYDIR</code> and comparing the hash returned with the hashes returned by <code>check_keys</code> and <code>check_imprints</code>. They should all match.<br />
# Configure the build system to produce a key transition container in the PNOR image. Run <code>op-build menuconfig</code> and set <code>External options -> OpenPower -> OpenPower Packages -> OpenPower PNOR assembly options -> Secure Boot key transition type</code> to <code>Transition existing keys to development keys</code>. "Development keys" in the context of the build system means "keys existing locally on my hard drive." "Production keys" refer to keys on a signing server somewhere for which the build system will generate signing requests if any "Production key" options are set.<br />
# Clear the old build output and re-build. Our aim in building the first time was only to force the build system to populate the <code>dl</code> directory with all the source code it would be compiling. <syntaxhighlight lang="bash" line='line'><br />
cd $OPBUILDDIR<br />
mv output/.config .<br />
rm -fr output/*<br />
mv .config output/<br />
op-build<br />
</syntaxhighlight><br />
# Save a copy of <code>output/images/</code> to an external drive. Rename the external drive's copy to <code>transition-images</code> or something similar.<br />
# Run <code>op-build menuconfig</code> again and set <code>Secure Boot key transition type</code> back to <code>None</code>.<br />
# Repeat the "clear the old build output and re-build" step.<br />
# Save a copy of <code>output/images/</code> to an external drive.<br />
# Shutdown the computer.<br />
# Follow the instructions on the [[Compiling Firmware]] page to install the <code>transition-images</code> PNOR image on your external drive.<br />
# Make sure the "secure mode disable" jumper on your mainboard is set. (See the user manual for your mainboard if you need help locating this.)<br />
# Boot up the computer and then let it shut itself down. If you did not manually clear and set the ECC bits for your firmware during the installation process, the system may reboot itself first to set those bits. Once it is finished, the hash of your own keys should be "imprinted" on the processor's SEEPROM. To confirm this, you can run <code>cat /proc/device-tree/ibm,secureboot/hw-key-hash | xxd -p</code> in either the host OS or the Petitboot shell to see what value is currently set in the SEEPROM after replacing the key transition PNOR image with a non-transition one.<br />
# Follow the instructions on the [[Compiling Firmware]] page to install the <code>images</code> PNOR image on your external drive.<br />
# Make sure the "secure mode disable" jumper on your mainboard is unset.<br />
# Boot up the computer. It should now be booting in secure mode using your signed firmware!</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Talk:Main_Page&diff=3137Talk:Main Page2020-03-26T23:13:13Z<p>Mx08: /* How to organize external links? */ new section</p>
<hr />
<div>== <s>New grid layout</s> ==<br />
<br />
The new 2x2 grid layout that [[User:HLandau|HLandau]] has created looks like a step in the right direction, although I'm confused <br />
why each grid region has an unused unstyled div. Is this meant to be used for something in the future, or can it be removed?<br />
<br />
Also, there should probably be a discussion on how best to group the four categories; for example, at the moment there are three different links to different parts of the Hardware Compatibility list, which looks to me like a waste of the home page real estate.<br />
<br />
[[User:Olddellian|Olddellian]] ([[User talk:Olddellian|talk]]) 11:13, 10 March 2019 (CDT)<br />
<br />
Removed vestigial divs. --[[User:HLandau|HLandau]] ([[User talk:HLandau|talk]]) 03:18, 11 March 2019 (CDT)<br />
<br />
== Criteria for Software Porting Efforts ==<br />
<br />
What are the criteria for listing Software Porting Efforts on the front page? Looks like 0ad and Wine were excluded, and it's not documented why. --[[User:JeremyRand|JeremyRand]] ([[User talk:JeremyRand|talk]]) 14:22, 16 March 2019 (CDT)<br />
<br />
Why not just make a porting category with a list (A-Z) of applications with ongoing ports?<br />
<br />
This "Porting" category is then placed on the main page. -- [[User:MPC7500|MPC7500]] ([[User talk:MPC7500|talk]]) 8:13, 17 March 2019 (CDT)<br />
<br />
I just saw that this is already the case. But the list contains only "P". I don't think this is optimal, because there will be +100 applications at some point. -- [[User:MPC7500|MPC7500]] ([[User talk:MPC7500|talk]]) 8:30, 17 March 2019 (CDT)<br />
<br />
== How to organize external links? ==<br />
<br />
I have recently added a few links to the "External Links" section on the wiki main page [https://wiki.raptorcs.com/w/index.php?title=Main_Page&action=historysubmit&type=revision&diff=3135&oldid=3133].<br />
<br />
There are a few more which could be useful:<br />
<br />
* [https://github.com/linuxppc/wiki/wiki linuxppc wiki]<br />
* [http://patchwork.ozlabs.org/project/linuxppc-dev/list/ linuxppc-dev Patchwork]<br />
* [https://lists.ozlabs.org/listinfo/linuxppc-dev linuxppc-dev Mailing list]<br />
* [https://ozlabs.org/ OzLabs Homepage] - A group of Australian Open Source hackers (which do PPC-related stuff)<br />
* [https://lists.ozlabs.org/listinfo lists.ozlabs.org Mailing Lists] - Various mailing lists hosted by OzLabs ('''including many PPC-related ones''')<br />
<br />
I'm not sure if the [[Main_Page#External_Links]] is the best place for them... it's getting quite big. But maybe that's not an issue.<br />
<br />
# Should I just add the links above to [[Main_Page#External_Links]]?<br />
# Should we introduce sub-sections in [[Main_Page#External_Links]]? Like "RCS/RE", "Mailing Lists" and "Other"<br />
# Should we create a separate place (section on the main page or a separate page) for mailing lists?<br />
# Should we create a separate place for "developer ressources", with a sub-section for dev-related mailing lists?<br />
<br />
These are just some ideas... what do you all think?<br />
<br />
[[User:Mx08|Mx08]] ([[User talk:Mx08|talk]]) 18:13, 26 March 2020 (CDT)</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Talk:Main_Page&diff=3136Talk:Main Page2020-03-26T22:43:34Z<p>Mx08: closing discussion "New grid layout": it has apparently been resolved</p>
<hr />
<div>== <s>New grid layout</s> ==<br />
<br />
The new 2x2 grid layout that [[User:HLandau|HLandau]] has created looks like a step in the right direction, although I'm confused <br />
why each grid region has an unused unstyled div. Is this meant to be used for something in the future, or can it be removed?<br />
<br />
Also, there should probably be a discussion on how best to group the four categories; for example, at the moment there are three different links to different parts of the Hardware Compatibility list, which looks to me like a waste of the home page real estate.<br />
<br />
[[User:Olddellian|Olddellian]] ([[User talk:Olddellian|talk]]) 11:13, 10 March 2019 (CDT)<br />
<br />
Removed vestigial divs. --[[User:HLandau|HLandau]] ([[User talk:HLandau|talk]]) 03:18, 11 March 2019 (CDT)<br />
<br />
== Criteria for Software Porting Efforts ==<br />
<br />
What are the criteria for listing Software Porting Efforts on the front page? Looks like 0ad and Wine were excluded, and it's not documented why. --[[User:JeremyRand|JeremyRand]] ([[User talk:JeremyRand|talk]]) 14:22, 16 March 2019 (CDT)<br />
<br />
Why not just make a porting category with a list (A-Z) of applications with ongoing ports?<br />
<br />
This "Porting" category is then placed on the main page. -- [[User:MPC7500|MPC7500]] ([[User talk:MPC7500|talk]]) 8:13, 17 March 2019 (CDT)<br />
<br />
I just saw that this is already the case. But the list contains only "P". I don't think this is optimal, because there will be +100 applications at some point. -- [[User:MPC7500|MPC7500]] ([[User talk:MPC7500|talk]]) 8:30, 17 March 2019 (CDT)</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Main_Page&diff=3135Main Page2020-03-26T22:01:16Z<p>Mx08: /* External Links */ add links to RCS twitter account + OpenPOWER-HDL-Cores mailing list</p>
<hr />
<div>'''Welcome to the Raptor Computing Systems Wiki!'''<br />
<br />
This community-driven Wiki provides documentation about:<br />
* [[Raptor Computing Systems|Raptor Computing Systems]] hardware and software like [[Talos II]]™ and [[Blackbird]]™<br />
* application and software concerning [[OpenPOWER|OpenPOWER]] / [[PowerNV|PowerNV]] and [[POWER9|POWER9]].<br />
<br />
See the '''[[Special:AllPages|list of all pages]]''' or use the '''search function''' to search for specific topics (since not every wiki page is directly linked here).<br />
<br />
Use the '''[https://forums.raptorcs.com/ Raptor CS community forum] for discussions'''.<br />
<br />
Please consult the '''[https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents Wiki User's Guide]''' on how to use and contribute to the Wiki.<br />
<br />
<div style="display:table;width:100%;border-spacing:0.5em;"><br />
<div style="display:table-row;"><br />
<div style="display:table-cell;width:50%;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Users</h3><br />
* [[Talos II Beginner's Quick Start Guide]]<br />
* [[:Category:Guides|How-to guides]]<br />
** [[Verifying DVDs]]<br />
** [[Getting System Information]]<br />
* Platforms:<br />
** [[Talos II|Talos II]]<br />
** [[Blackbird]]<br />
** [[Condor]]<br />
* [[Platform Comparison|Platform Comparison to x86]]<br />
* [[IRC|IRC chat]]<br />
* [[:Category:Gallery|Gallery of assembled systems]]<br />
* [[:Category:User Systems|Descriptions of user systems]]<br />
* [[:Category:Glossary|Glossary]]<br />
</div><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">News</h3><br />
<h4>Raptor + OpenPOWER</h4><br />
* August 19-20, ''[https://openpowerfoundation.org/events/openpower-summit-2019-north-america/ OpenPOWER Summit 2019 North America]'' - Raptor Computing Systems presentation and booth<br />
* June 16–20, ''[https://www.isc-hpc.com/ ISC] 2019'' - Blackbird on display according to [https://www.hpcwire.com/solution_content/ibm/cross-industry/powering-the-future-of-hpc-ai-with-openpower/ IBM sponsored Q&A with Hugh Blemings]<br />
* IBM is stating that Power is not vulnerable to [https://en.wikipedia.org/wiki/Microarchitectural_Data_Sampling MDS vulnerabilites] (Fallout, RIDL, ZombieLoad). [https://www.ibm.com/blogs/psirt/ibm-addresses-reported-intel-security-vulnerabilities/ 1], [https://www.ibm.com/blogs/psirt/ibm-addresses-reported-intel-security-vulnerabilities/ 2]<br />
Past events where RCS systems were on display are [[Events|listed at the events page]].<br />
<h4>This Wiki</h4><br />
* A [[Talos II/Building FAQ|Building FAQ]] has been started.<br />
* Initial [[Hardware Compatibility List#Memory|RAM compatibility]] lists are now available.<br />
* [[Power ISA/Privilege States#Ultravisor State|Ultravisor State]] is still not very well understood.<br />
* [[Speculative Execution Vulnerabilities of 2018|Speculative Execution Vulnerabilities of 2018]]<br />
* A [[Desktop Roadmap]] has been started.<br />
<br />
</div><br />
</div><br />
<div style="display:table-row;"><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Compatibility</h3><br />
<h4>Hardware</h4><br />
* [[POWER9 Hardware Compatibility List|POWER9]]<br />
** [[POWER9 Hardware Compatibility List/Memory|Memory compatibility]]<br />
** [[POWER9 Hardware Compatibility List/PCIe Devices|PCIe device compatibility]]<br />
* [[Talos II/Hardware Compatibility List|Talos II specific compatibility]]<br />
* [[Blackbird/Hardware Compatibility List|Blackbird specific compatibility]]<br />
<h4>Software</h4><br />
* [[Operating System Compatibility List|Operating System Compatibility List]]<br />
* [[Fixes in Progress]]<br />
</div><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Developers</h3><br />
* [[:Category:Documentation|POWER9 Documentation]]<br />
* [[OpenPOWER Firmware|OpenPOWER Firmware]]<br />
* [[Talos_II/Compiling_Firmware|Compiling Firmware]]<br />
* [[:Category:Ports|Software Porting Efforts]]<br />
** [[Porting/Firefox|Firefox]]<br />
** [[Porting/Chromium|Chromium]]<br />
** [[Porting/Tor Browser|Tor Browser]]<br />
</div><br />
</div><br />
</div><br />
<br />
== External Links ==<br />
<br />
* [https://raptorcs.com/ Raptor Computing Systems Homepage]<br />
* [https://forums.raptorcs.com/ Raptor Computing Systems Community Forums]<br />
* [https://ticket.raptorcs.com/ Raptor Computing Systems Helpdesk]<br />
* [https://twitter.com/RaptorCompSys Raptor Computing Systems Official Twitter Account]<br />
* [https://git.raptorcs.com/git/ Raptor Computing Systems Git Repositories] - Official distribution channel for software/firmware releases related to RCS products<br />
* [https://gitlab.raptorengineering.com/ Raptor Engineering Gitlab Instance] - Open collaboration platform for software/firmware development related to RCS products<br />
* [https://bugs.raptorengineering.com/ Raptor Engineering Bugtracker]<br />
* [https://openpowerfoundation.org/ OpenPOWER Foundation Homepage]<br />
* [https://www.youtube.com/channel/UCNVcHm09eXVbvUzZkQs0_Sg/ OpenPOWER Foundation YouTube Channel]<br />
* [http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo/openpower-community-dev/ OpenPOWER-Community-Dev] - Mailing list for discussing developer/grass roots OpenPOWER and/or PowerPC matters - hardware and software.<br />
* [http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo/openpower-hdl-cores OpenPOWER-HDL-Cores] - Mailing list for discussing all matters related to HDL/Software implementation of OpenPOWER compliant CPU cores, SoCs, FPGAs etc.<br />
* [https://www.talospace.com/ Talospace] community user blog - news and other posts about POWER9/RCS<br />
* [https://catfox.life/author/awilfox/ The Cat Fox Life] community user blog - news and other posts about OpenPOWER/PowerPC<br />
* [https://www.bountysource.com/teams/ibm/bounties IBM Bounty Program on BountySource]<br />
__NOTOC__</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Main_Page&diff=3134Main Page2020-03-26T21:48:19Z<p>Mx08: /* External Links */ add links to official git repo and gitlab instance</p>
<hr />
<div>'''Welcome to the Raptor Computing Systems Wiki!'''<br />
<br />
This community-driven Wiki provides documentation about:<br />
* [[Raptor Computing Systems|Raptor Computing Systems]] hardware and software like [[Talos II]]™ and [[Blackbird]]™<br />
* application and software concerning [[OpenPOWER|OpenPOWER]] / [[PowerNV|PowerNV]] and [[POWER9|POWER9]].<br />
<br />
See the '''[[Special:AllPages|list of all pages]]''' or use the '''search function''' to search for specific topics (since not every wiki page is directly linked here).<br />
<br />
Use the '''[https://forums.raptorcs.com/ Raptor CS community forum] for discussions'''.<br />
<br />
Please consult the '''[https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents Wiki User's Guide]''' on how to use and contribute to the Wiki.<br />
<br />
<div style="display:table;width:100%;border-spacing:0.5em;"><br />
<div style="display:table-row;"><br />
<div style="display:table-cell;width:50%;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Users</h3><br />
* [[Talos II Beginner's Quick Start Guide]]<br />
* [[:Category:Guides|How-to guides]]<br />
** [[Verifying DVDs]]<br />
** [[Getting System Information]]<br />
* Platforms:<br />
** [[Talos II|Talos II]]<br />
** [[Blackbird]]<br />
** [[Condor]]<br />
* [[Platform Comparison|Platform Comparison to x86]]<br />
* [[IRC|IRC chat]]<br />
* [[:Category:Gallery|Gallery of assembled systems]]<br />
* [[:Category:User Systems|Descriptions of user systems]]<br />
* [[:Category:Glossary|Glossary]]<br />
</div><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">News</h3><br />
<h4>Raptor + OpenPOWER</h4><br />
* August 19-20, ''[https://openpowerfoundation.org/events/openpower-summit-2019-north-america/ OpenPOWER Summit 2019 North America]'' - Raptor Computing Systems presentation and booth<br />
* June 16–20, ''[https://www.isc-hpc.com/ ISC] 2019'' - Blackbird on display according to [https://www.hpcwire.com/solution_content/ibm/cross-industry/powering-the-future-of-hpc-ai-with-openpower/ IBM sponsored Q&A with Hugh Blemings]<br />
* IBM is stating that Power is not vulnerable to [https://en.wikipedia.org/wiki/Microarchitectural_Data_Sampling MDS vulnerabilites] (Fallout, RIDL, ZombieLoad). [https://www.ibm.com/blogs/psirt/ibm-addresses-reported-intel-security-vulnerabilities/ 1], [https://www.ibm.com/blogs/psirt/ibm-addresses-reported-intel-security-vulnerabilities/ 2]<br />
Past events where RCS systems were on display are [[Events|listed at the events page]].<br />
<h4>This Wiki</h4><br />
* A [[Talos II/Building FAQ|Building FAQ]] has been started.<br />
* Initial [[Hardware Compatibility List#Memory|RAM compatibility]] lists are now available.<br />
* [[Power ISA/Privilege States#Ultravisor State|Ultravisor State]] is still not very well understood.<br />
* [[Speculative Execution Vulnerabilities of 2018|Speculative Execution Vulnerabilities of 2018]]<br />
* A [[Desktop Roadmap]] has been started.<br />
<br />
</div><br />
</div><br />
<div style="display:table-row;"><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Compatibility</h3><br />
<h4>Hardware</h4><br />
* [[POWER9 Hardware Compatibility List|POWER9]]<br />
** [[POWER9 Hardware Compatibility List/Memory|Memory compatibility]]<br />
** [[POWER9 Hardware Compatibility List/PCIe Devices|PCIe device compatibility]]<br />
* [[Talos II/Hardware Compatibility List|Talos II specific compatibility]]<br />
* [[Blackbird/Hardware Compatibility List|Blackbird specific compatibility]]<br />
<h4>Software</h4><br />
* [[Operating System Compatibility List|Operating System Compatibility List]]<br />
* [[Fixes in Progress]]<br />
</div><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Developers</h3><br />
* [[:Category:Documentation|POWER9 Documentation]]<br />
* [[OpenPOWER Firmware|OpenPOWER Firmware]]<br />
* [[Talos_II/Compiling_Firmware|Compiling Firmware]]<br />
* [[:Category:Ports|Software Porting Efforts]]<br />
** [[Porting/Firefox|Firefox]]<br />
** [[Porting/Chromium|Chromium]]<br />
** [[Porting/Tor Browser|Tor Browser]]<br />
</div><br />
</div><br />
</div><br />
<br />
== External Links ==<br />
<br />
* [https://raptorcs.com/ Raptor Computing Systems Homepage]<br />
* [https://forums.raptorcs.com/ Raptor Computing Systems Community Forums]<br />
* [https://ticket.raptorcs.com/ Raptor Computing Systems Helpdesk]<br />
* [https://git.raptorcs.com/git/ Raptor Computing Systems Git Repositories] - Official distribution channel for software/firmware releases related to RCS products<br />
* [https://gitlab.raptorengineering.com/ Raptor Engineering Gitlab Instance] - Open collaboration platform for software/firmware development related to RCS products<br />
* [https://bugs.raptorengineering.com/ Raptor Engineering Bugtracker]<br />
* [https://openpowerfoundation.org/ OpenPOWER Foundation Homepage]<br />
* [https://www.youtube.com/channel/UCNVcHm09eXVbvUzZkQs0_Sg/ OpenPOWER Foundation YouTube Channel]<br />
* [http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo/openpower-community-dev/ OpenPOWER-Community-Dev mailing list]<br />
* [https://www.talospace.com/ Talospace] community user blog - news and other posts about POWER9/RCS<br />
* [https://catfox.life/author/awilfox/ The Cat Fox Life] community user blog - news and other posts about OpenPOWER/PowerPC<br />
* [https://www.bountysource.com/teams/ibm/bounties IBM Bounty Program on BountySource]<br />
__NOTOC__</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Main_Page&diff=3133Main Page2020-03-26T21:17:34Z<p>Mx08: /* External Links */ change the formatting of the links to include the full link description, so that it is more intuitive what the destination of a link is</p>
<hr />
<div>'''Welcome to the Raptor Computing Systems Wiki!'''<br />
<br />
This community-driven Wiki provides documentation about:<br />
* [[Raptor Computing Systems|Raptor Computing Systems]] hardware and software like [[Talos II]]™ and [[Blackbird]]™<br />
* application and software concerning [[OpenPOWER|OpenPOWER]] / [[PowerNV|PowerNV]] and [[POWER9|POWER9]].<br />
<br />
See the '''[[Special:AllPages|list of all pages]]''' or use the '''search function''' to search for specific topics (since not every wiki page is directly linked here).<br />
<br />
Use the '''[https://forums.raptorcs.com/ Raptor CS community forum] for discussions'''.<br />
<br />
Please consult the '''[https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents Wiki User's Guide]''' on how to use and contribute to the Wiki.<br />
<br />
<div style="display:table;width:100%;border-spacing:0.5em;"><br />
<div style="display:table-row;"><br />
<div style="display:table-cell;width:50%;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Users</h3><br />
* [[Talos II Beginner's Quick Start Guide]]<br />
* [[:Category:Guides|How-to guides]]<br />
** [[Verifying DVDs]]<br />
** [[Getting System Information]]<br />
* Platforms:<br />
** [[Talos II|Talos II]]<br />
** [[Blackbird]]<br />
** [[Condor]]<br />
* [[Platform Comparison|Platform Comparison to x86]]<br />
* [[IRC|IRC chat]]<br />
* [[:Category:Gallery|Gallery of assembled systems]]<br />
* [[:Category:User Systems|Descriptions of user systems]]<br />
* [[:Category:Glossary|Glossary]]<br />
</div><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">News</h3><br />
<h4>Raptor + OpenPOWER</h4><br />
* August 19-20, ''[https://openpowerfoundation.org/events/openpower-summit-2019-north-america/ OpenPOWER Summit 2019 North America]'' - Raptor Computing Systems presentation and booth<br />
* June 16–20, ''[https://www.isc-hpc.com/ ISC] 2019'' - Blackbird on display according to [https://www.hpcwire.com/solution_content/ibm/cross-industry/powering-the-future-of-hpc-ai-with-openpower/ IBM sponsored Q&A with Hugh Blemings]<br />
* IBM is stating that Power is not vulnerable to [https://en.wikipedia.org/wiki/Microarchitectural_Data_Sampling MDS vulnerabilites] (Fallout, RIDL, ZombieLoad). [https://www.ibm.com/blogs/psirt/ibm-addresses-reported-intel-security-vulnerabilities/ 1], [https://www.ibm.com/blogs/psirt/ibm-addresses-reported-intel-security-vulnerabilities/ 2]<br />
Past events where RCS systems were on display are [[Events|listed at the events page]].<br />
<h4>This Wiki</h4><br />
* A [[Talos II/Building FAQ|Building FAQ]] has been started.<br />
* Initial [[Hardware Compatibility List#Memory|RAM compatibility]] lists are now available.<br />
* [[Power ISA/Privilege States#Ultravisor State|Ultravisor State]] is still not very well understood.<br />
* [[Speculative Execution Vulnerabilities of 2018|Speculative Execution Vulnerabilities of 2018]]<br />
* A [[Desktop Roadmap]] has been started.<br />
<br />
</div><br />
</div><br />
<div style="display:table-row;"><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Compatibility</h3><br />
<h4>Hardware</h4><br />
* [[POWER9 Hardware Compatibility List|POWER9]]<br />
** [[POWER9 Hardware Compatibility List/Memory|Memory compatibility]]<br />
** [[POWER9 Hardware Compatibility List/PCIe Devices|PCIe device compatibility]]<br />
* [[Talos II/Hardware Compatibility List|Talos II specific compatibility]]<br />
* [[Blackbird/Hardware Compatibility List|Blackbird specific compatibility]]<br />
<h4>Software</h4><br />
* [[Operating System Compatibility List|Operating System Compatibility List]]<br />
* [[Fixes in Progress]]<br />
</div><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Developers</h3><br />
* [[:Category:Documentation|POWER9 Documentation]]<br />
* [[OpenPOWER Firmware|OpenPOWER Firmware]]<br />
* [[Talos_II/Compiling_Firmware|Compiling Firmware]]<br />
* [[:Category:Ports|Software Porting Efforts]]<br />
** [[Porting/Firefox|Firefox]]<br />
** [[Porting/Chromium|Chromium]]<br />
** [[Porting/Tor Browser|Tor Browser]]<br />
</div><br />
</div><br />
</div><br />
<br />
== External Links ==<br />
<br />
* [https://raptorcs.com/ Raptor Computing Systems Homepage]<br />
* [https://forums.raptorcs.com/ Raptor Computing Systems Community Forums]<br />
* [https://ticket.raptorcs.com/ Raptor Computing Systems Helpdesk]<br />
* [https://bugs.raptorengineering.com/ Raptor Engineering Bugtracker]<br />
* [https://openpowerfoundation.org/ OpenPOWER Foundation Homepage]<br />
* [https://www.youtube.com/channel/UCNVcHm09eXVbvUzZkQs0_Sg/ OpenPOWER Foundation YouTube Channel]<br />
* [http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo/openpower-community-dev/ OpenPOWER-Community-Dev mailing list]<br />
* [https://www.talospace.com/ Talospace] community user blog - news and other posts about POWER9/RCS<br />
* [https://catfox.life/author/awilfox/ The Cat Fox Life] community user blog - news and other posts about OpenPOWER/PowerPC<br />
* [https://www.bountysource.com/teams/ibm/bounties IBM Bounty Program on BountySource]<br />
__NOTOC__</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Main_Page&diff=3132Main Page2020-03-26T20:51:21Z<p>Mx08: small grammar/spelling/formatting improvements</p>
<hr />
<div>'''Welcome to the Raptor Computing Systems Wiki!'''<br />
<br />
This community-driven Wiki provides documentation about:<br />
* [[Raptor Computing Systems|Raptor Computing Systems]] hardware and software like [[Talos II]]™ and [[Blackbird]]™<br />
* application and software concerning [[OpenPOWER|OpenPOWER]] / [[PowerNV|PowerNV]] and [[POWER9|POWER9]].<br />
<br />
See the '''[[Special:AllPages|list of all pages]]''' or use the '''search function''' to search for specific topics (since not every wiki page is directly linked here).<br />
<br />
Use the '''[https://forums.raptorcs.com/ Raptor CS community forum] for discussions'''.<br />
<br />
Please consult the '''[https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents Wiki User's Guide]''' on how to use and contribute to the Wiki.<br />
<br />
<div style="display:table;width:100%;border-spacing:0.5em;"><br />
<div style="display:table-row;"><br />
<div style="display:table-cell;width:50%;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Users</h3><br />
* [[Talos II Beginner's Quick Start Guide]]<br />
* [[:Category:Guides|How-to guides]]<br />
** [[Verifying DVDs]]<br />
** [[Getting System Information]]<br />
* Platforms:<br />
** [[Talos II|Talos II]]<br />
** [[Blackbird]]<br />
** [[Condor]]<br />
* [[Platform Comparison|Platform Comparison to x86]]<br />
* [[IRC|IRC chat]]<br />
* [[:Category:Gallery|Gallery of assembled systems]]<br />
* [[:Category:User Systems|Descriptions of user systems]]<br />
* [[:Category:Glossary|Glossary]]<br />
</div><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">News</h3><br />
<h4>Raptor + OpenPOWER</h4><br />
* August 19-20, ''[https://openpowerfoundation.org/events/openpower-summit-2019-north-america/ OpenPOWER Summit 2019 North America]'' - Raptor Computing Systems presentation and booth<br />
* June 16–20, ''[https://www.isc-hpc.com/ ISC] 2019'' - Blackbird on display according to [https://www.hpcwire.com/solution_content/ibm/cross-industry/powering-the-future-of-hpc-ai-with-openpower/ IBM sponsored Q&A with Hugh Blemings]<br />
* IBM is stating that Power is not vulnerable to [https://en.wikipedia.org/wiki/Microarchitectural_Data_Sampling MDS vulnerabilites] (Fallout, RIDL, ZombieLoad). [https://www.ibm.com/blogs/psirt/ibm-addresses-reported-intel-security-vulnerabilities/ 1], [https://www.ibm.com/blogs/psirt/ibm-addresses-reported-intel-security-vulnerabilities/ 2]<br />
Past events where RCS systems were on display are [[Events|listed at the events page]].<br />
<h4>This Wiki</h4><br />
* A [[Talos II/Building FAQ|Building FAQ]] has been started.<br />
* Initial [[Hardware Compatibility List#Memory|RAM compatibility]] lists are now available.<br />
* [[Power ISA/Privilege States#Ultravisor State|Ultravisor State]] is still not very well understood.<br />
* [[Speculative Execution Vulnerabilities of 2018|Speculative Execution Vulnerabilities of 2018]]<br />
* A [[Desktop Roadmap]] has been started.<br />
<br />
</div><br />
</div><br />
<div style="display:table-row;"><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Compatibility</h3><br />
<h4>Hardware</h4><br />
* [[POWER9 Hardware Compatibility List|POWER9]]<br />
** [[POWER9 Hardware Compatibility List/Memory|Memory compatibility]]<br />
** [[POWER9 Hardware Compatibility List/PCIe Devices|PCIe device compatibility]]<br />
* [[Talos II/Hardware Compatibility List|Talos II specific compatibility]]<br />
* [[Blackbird/Hardware Compatibility List|Blackbird specific compatibility]]<br />
<h4>Software</h4><br />
* [[Operating System Compatibility List|Operating System Compatibility List]]<br />
* [[Fixes in Progress]]<br />
</div><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Developers</h3><br />
* [[:Category:Documentation|POWER9 Documentation]]<br />
* [[OpenPOWER Firmware|OpenPOWER Firmware]]<br />
* [[Talos_II/Compiling_Firmware|Compiling Firmware]]<br />
* [[:Category:Ports|Software Porting Efforts]]<br />
** [[Porting/Firefox|Firefox]]<br />
** [[Porting/Chromium|Chromium]]<br />
** [[Porting/Tor Browser|Tor Browser]]<br />
</div><br />
</div><br />
</div><br />
<br />
== External Links ==<br />
<br />
* [https://raptorcs.com/ Raptor Computing Systems] homepage<br />
* [https://forums.raptorcs.com/ Raptor Computing Systems] community forums<br />
* [https://ticket.raptorcs.com/ Raptor Computing Systems] helpdesk<br />
* [https://bugs.raptorengineering.com/ Raptor Engineering's Bugtracker]<br />
* [https://openpowerfoundation.org/ OpenPOWER Foundation] homepage<br />
* [https://www.youtube.com/channel/UCNVcHm09eXVbvUzZkQs0_Sg/ OpenPOWER Foundation] YouTube Channel<br />
* [http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo/openpower-community-dev/ OpenPOWER Community Dev] mailing list<br />
* [https://www.talospace.com/ Talospace] community user blogs - news and other posts about POWER9/Talos<br />
* [https://catfox.life/author/awilfox/ The Cat Fox Life] community user blogs - news and other posts about OpenPOWER/PowerPC<br />
* [https://www.bountysource.com/teams/ibm/bounties BountySource] IBM OpenSource Bounties<br />
__NOTOC__</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Main_Page&diff=3131Main Page2020-03-26T19:41:22Z<p>Mx08: adjust formatting</p>
<hr />
<div>'''Welcome to the Raptor Computing Systems Wiki!'''<br />
<br />
This community-driven Wiki provides documentations about<br />
* [[Raptor Computing Systems|Raptor Computing Systems]] hardware and software like Talos™ and Blackbird™<br />
* application and software concerning [[OpenPOWER|OpenPOWER]] / [[PowerNV|PowerNV]] and [[POWER9|POWER9]].<br />
<br />
See the '''[[Special:AllPages|list of all pages]]''' or use the '''search function''' to search for specific topics (since not every wiki page is directly linked here).<br />
<br />
Use the '''[https://forums.raptorcs.com/ Raptor CS community forum] for discussions'''.<br />
<br />
Please consult the '''[https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents Wiki User's Guide]''' on how to use and contribute to the Wiki.<br />
<br />
<div style="display:table;width:100%;border-spacing:0.5em;"><br />
<div style="display:table-row;"><br />
<div style="display:table-cell;width:50%;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Users</h3><br />
* [[Talos II Beginner's Quick Start Guide]]<br />
* [[:Category:Guides|How-to guides]]<br />
** [[Verifying DVDs]]<br />
** [[Getting System Information]]<br />
* Platforms:<br />
** [[Talos II|Talos II]]<br />
** [[Blackbird]]<br />
** [[Condor]]<br />
* [[Platform Comparison|Platform Comparison to x86]]<br />
* [[IRC|IRC chat]]<br />
* [[:Category:Gallery|Gallery of assembled systems]]<br />
* [[:Category:User Systems|Descriptions of user systems]]<br />
* [[:Category:Glossary|Glossary]]<br />
</div><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">News</h3><br />
<h4>Raptor + OpenPOWER</h4><br />
* August 19-20, ''[https://openpowerfoundation.org/events/openpower-summit-2019-north-america/ OpenPOWER Summit 2019 North America]'' - Raptor Computing Systems presentation and booth<br />
* June 16–20, ''[https://www.isc-hpc.com/ ISC] 2019'' - Blackbird on display according to [https://www.hpcwire.com/solution_content/ibm/cross-industry/powering-the-future-of-hpc-ai-with-openpower/ IBM sponsored Q&A with Hugh Blemings]<br />
* IBM is stating that Power is not vulnerable to [https://en.wikipedia.org/wiki/Microarchitectural_Data_Sampling MDS vulnerabilites] (Fallout, RIDL, ZombieLoad). [https://www.ibm.com/blogs/psirt/ibm-addresses-reported-intel-security-vulnerabilities/ 1], [https://www.ibm.com/blogs/psirt/ibm-addresses-reported-intel-security-vulnerabilities/ 2]<br />
Past events where RCS systems were on display are [[Events|listed at the events page]]<br />
<h4>This Wiki</h4><br />
* A [[Talos II/Building FAQ|Building FAQ]] has been started<br />
* Initial [[Hardware Compatibility List#Memory|RAM compatibility]] lists are now available<br />
* [[Power ISA/Privilege States#Ultravisor State|Ultravisor State]] is still not very well understood<br />
* [[Speculative Execution Vulnerabilities of 2018|Speculative Execution Vulnerabilities of 2018]]<br />
* A [[Desktop Roadmap]] has been started.<br />
<br />
</div><br />
</div><br />
<div style="display:table-row;"><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Compatibility</h3><br />
<h4>Hardware</h4><br />
* [[POWER9 Hardware Compatibility List|POWER9]]<br />
** [[POWER9 Hardware Compatibility List/Memory|Memory compatibility]]<br />
** [[POWER9 Hardware Compatibility List/PCIe Devices|PCIe device compatibility]]<br />
* [[Talos II/Hardware Compatibility List|Talos II specific compatibility]]<br />
* [[Blackbird/Hardware Compatibility List|Blackbird specific compatibility]]<br />
<h4>Software</h4><br />
* [[Operating System Compatibility List|Operating System Compatibility List]]<br />
* [[Fixes in Progress]]<br />
</div><br />
<div style="display:table-cell;border: solid 1px #999; padding: 0.5em; margin: 0.2em; background-color: #e5e5f5;"><br />
<h3 style="margin-top:0;padding-top:0;">Developers</h3><br />
* [[:Category:Documentation|POWER9 Documentation]]<br />
* [[OpenPOWER Firmware|OpenPOWER Firmware]]<br />
* [[Talos_II/Compiling_Firmware|Compiling Firmware]]<br />
* [[:Category:Ports|Software Porting Efforts]]<br />
** [[Porting/Firefox|Firefox]]<br />
** [[Porting/Chromium|Chromium]]<br />
** [[Porting/Tor Browser|Tor Browser]]<br />
</div><br />
</div><br />
</div><br />
<br />
== External Links ==<br />
<br />
* [https://raptorcs.com/ Raptor Computing Systems] homepage<br />
* [https://forums.raptorcs.com/ Raptor Computing Systems] community forums<br />
* [https://ticket.raptorcs.com/ Raptor Computing Systems] helpdesk<br />
* [https://bugs.raptorengineering.com/ Raptor Engineering's Bugtracker]<br />
* [https://openpowerfoundation.org/ OpenPOWER Foundation] homepage<br />
* [https://www.youtube.com/channel/UCNVcHm09eXVbvUzZkQs0_Sg/ OpenPOWER Foundation] YouTube Channel<br />
* [http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo/openpower-community-dev/ OpenPOWER Community Dev] mailing list<br />
* [https://www.talospace.com/ Talospace] community user blogs - news and other posts about POWER9/Talos<br />
* [https://catfox.life/author/awilfox/ The Cat Fox Life] community user blogs - news and other posts about OpenPOWER/PowerPC<br />
* [https://www.bountysource.com/teams/ibm/bounties BountySource] IBM OpenSource Bounties<br />
__NOTOC__</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Configuring_Spectre_Protection_Level&diff=3130Configuring Spectre Protection Level2020-03-26T19:17:47Z<p>Mx08: adjust scope of reference: it actually applies to all three sentences, see the reference</p>
<hr />
<div>The Spectre protections on [[POWER9]] can be partly or fully disengaged if desired. Note that disengaging the protections will leave you vulnerable to attack via Spectre variant 2, and could result in data leakage and/or system compromise. The override is controlled by the BMC and requires a reboot of the POWER9 to take effect.<ref>[ftp://170.225.15.34/ecc/sar/CMA/SFA/08h25/1/AC922_8335-GTH-GTX_OpenPowerReadme.op920.21.xhtml IBM POWER9 Systems LC Server Firmware]. Retrieved 2020-03-26.</ref><br />
<br />
To override the protection level:<br />
<br />
<ol><br />
<li>Create/edit the file <code>/var/lib/obmc/cfam_overrides</code> on the BMC.</li><br />
<li>Add the following contents:</li><br />
<pre># Control speculative execution mode<br />
0 0x283a 0x00000001 # bits 28:31 are used for init level -- in this case 1 (Kernel protection only)<br />
0 0x283F 0x20000000 # Indicate override register is valid</pre><br />
<li>Re-[[IPL]] (fully power off and restart the host system) to apply changes.</li><br />
</ol><br />
<br />
Key:<br />
* Init level 0 &mdash; Kernel and User protection (safest, default)<br />
* Init level 1 &mdash; Kernel protection only<br />
* Init level 2 &mdash; No protection<br />
<br />
== See also ==<br />
<br />
* [[Speculative Execution Vulnerabilities of 2018]]<br />
<br />
== References ==<br />
<br />
<references /><br />
<br />
[[Category:Guides]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Configuring_Spectre_Protection_Level&diff=3129Configuring Spectre Protection Level2020-03-26T18:22:19Z<p>Mx08: improve reference</p>
<hr />
<div>The Spectre protections on [[POWER9]] can be partly or fully disengaged if desired. Note that disengaging the protections will leave you vulnerable to attack via Spectre variant 2, and could result in data leakage and/or system compromise. "The override is controlled by the BMC and requires a reboot of the POWER9 to take effect."<ref>[ftp://170.225.15.34/ecc/sar/CMA/SFA/08h25/1/AC922_8335-GTH-GTX_OpenPowerReadme.op920.21.xhtml IBM POWER9 Systems LC Server Firmware]. Retrieved 2020-03-26.</ref><br />
<br />
To override the protection level:<br />
<br />
<ol><br />
<li>Create/edit the file <code>/var/lib/obmc/cfam_overrides</code> on the BMC.</li><br />
<li>Add the following contents:</li><br />
<pre># Control speculative execution mode<br />
0 0x283a 0x00000001 # bits 28:31 are used for init level -- in this case 1 (Kernel protection only)<br />
0 0x283F 0x20000000 # Indicate override register is valid</pre><br />
<li>Re-[[IPL]] (fully power off and restart the host system) to apply changes.</li><br />
</ol><br />
<br />
Key:<br />
* Init level 0 &mdash; Kernel and User protection (safest, default)<br />
* Init level 1 &mdash; Kernel protection only<br />
* Init level 2 &mdash; No protection<br />
<br />
== See also ==<br />
<br />
* [[Speculative Execution Vulnerabilities of 2018]]<br />
<br />
== References ==<br />
<br />
<references /><br />
<br />
[[Category:Guides]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Speculative_Execution_Vulnerabilities_of_2018&diff=3128Speculative Execution Vulnerabilities of 20182020-03-26T17:17:31Z<p>Mx08: add section "See also" and link to Configuring Spectre Protection Level</p>
<hr />
<div>In January of 2018, news of three speculative execution vulnerabilities was made public. Information about these vulnerabilities had been disclosed in private to certain companies and projects in June of 2016. <br />
<br />
{| class="wikitable sortable"<br />
! CVE<br />
! Group<br />
! GPZ name<ref>[https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html Reading privileged memory with a side-channel]. Google Project Zero blog</ref><br />
! Description<br />
|-<br />
| CVE-2017-5715<br />
| Spectre<br />
| Variant 2<br />
| ''indirect'' branch prediction with side-channel analysis<ref>[https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5715 CVE-2017-5715]. Mitre CVE List. "Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis."</ref><br />
|-<br />
| CVE-2017-5753<br />
| Spectre<br />
| Variant 1<br />
| branch prediction with side-channel analysis<ref>[https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5753 CVE-2017-5753]. Mitre CVE List. "Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis."</ref><br />
|-<br />
| CVE-2017-5754<br />
| Meltdown<br />
| Variant 3<br />
| ''indirect'' branch prediction with side-channel analysis ''of data cache''<ref>[https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5754 CVE-2017-5754]. Mitre CVE List. "Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache."</ref><br />
|}<br />
<br />
At this time we know that [[POWER9|POWER9]], [[POWER8|POWER8]], [[POWER8E|POWER8E]], POWER7+, POWER6, and certain PowerPC architectures are affected by at least some of these vulnerabilities. <ref>IBM PSIRT Blog post, [https://www.ibm.com/blogs/psirt/potential-impact-processors-power-family/ Potential Impact on Processors in the POWER family]</ref><ref>TenFourFox Development blog post, [https://tenfourfox.blogspot.co.at/2018/01/actual-field-testing-of-spectre-on.html Actual field testing of Spectre on various Power Macs]</ref><ref>Raptor Engineering GNU Social [https://social.raptorengineering.io/conversation/731 notices about POWER8 and POWER9 vulnerability]</ref><ref>Red Hat security page for [https://access.redhat.com/security/vulnerabilities/speculativeexecution Kernel Side-Channel Attacks]</ref><br />
<br />
== CVE-2017-5715 (Spectre) ==<br />
<br />
According to the official CVE list, this may affect processors using "speculative execution and ''indirect'' branch prediction". Google's Project Zero calls this ''Variant 2: branch target injection''.<br />
<br />
=== POWER9 ===<br />
<br />
Hardware fixes are in place for [[POWER9]] Nimbus DD2.2 / Cumulus DD1.1 and above <ref name="hostboot-commit-fcf7d0e3" />. With these hardware changes, Spectre variant 2 is believed to be mitigated on the production POWER9 devices. Note that firmware applies the protections by throwing chicken switches in the silicon; as a result, the [[POWER/Spectre_Protections|protection level is configurable via firmware flags]].<br />
<br />
== CVE-2017-5753 (Spectre) ==<br />
<br />
According to the official CVE list, this may affect processors using "speculative execution and branch prediction". Google's Project Zero calls this ''Variant 1: bounds check bypass''.<br />
<br />
=== POWER9 ===<br />
<br />
Hardware fixes are in place for [[POWER9]] Nimbus DD2.2 / Cumulus DD1.1 and above <ref name="hostboot-commit-fcf7d0e3" />. With these hardware changes, cross-process attacks via Spectre variant 1 are believed to be fully mitigated on the production POWER9 devices.<br />
<br />
== CVE-2017-5754 (Meltdown) ==<br />
<br />
According to the official CVE list, this may affect processors using "speculative execution and ''indirect'' branch prediction", but specifically uses a data cache side channel. Google's Project Zero calls this '' Variant 3: rogue data cache load''.<br />
<br />
=== Common Mitigations ===<br />
<br />
POWER7, POWER8, and POWER9 are patched from CVE-2017-5754 by purging the L1 cache when context switching to a less privileged process, as the vulnerability on these architectures affects L1 but not L2 cache.<ref>Larabel, Michael. [https://www.phoronix.com/scan.php?page=news_item&px=PowerPC-Mem-Protection-Keys PowerPC Memory Protection Keys In For Linux 4.16, Power Has Meltdown Mitigation In 4.15]. 2018-01-22</ref> Firmware updates are also required to enable workarounds at the hardware level.<ref>[https://delivery04.dhe.ibm.com/sar/CMA/SFA/07dcs/1/8001-12C-22C--8005-12N-22N-OpenPowerReadme.v4.0.xhtml IBM Power8 Systems Server Firmware]</ref> <ref>[http://delivery04.dhe.ibm.com/sar/CMA/SFA/07dhe/0/AC922_8335-GTG_OpenPowerReadme.v1.3.xhtml IBM POWER9 Systems Server Firmware]</ref>.<br />
<br />
=== POWER9 ===<br />
<br />
Hardware fixes are also in place for [[POWER9]] Nimbus DD2.2 / Cumulus DD1.1 and above <ref name="hostboot-commit-fcf7d0e3">[https://git.raptorcs.com/git/talos-hostboot/commit/?id=fcf7d0e3f5fe8013b8f88a70a4f69cb5c0efc38b Hostboot commit message listing security changes for NDD2.2 / CDD1.1]</ref>. In conjunction with the above kernel patch, Meltdown is fully mitigated on the production POWER9 devices.<br />
<br />
== Official statement from Raptor Computing Systems regarding Talos™ II ==<br />
<br />
POWER9 will not ship with vulnerability to Meltdown or any loss in performance compared with the current prototype chips (DD2.1). Further, Spectre is fully mitigated with the exception of the same-process issue that is affecting the entire CPU industry. As far as we are aware there will be no further mitigation from any major CPU vendor now or in the future, as the remaining Spectre issue has been deemed an application level programming issue versus a CPU design issue. Patches for GCC to help fix the affected applications are already rolling out.<br />
<br />
== See also ==<br />
<br />
* [[Configuring Spectre Protection Level]]<br />
<br />
== External Links ==<br />
<br />
* Websites for [https://meltdownattack.com/ Meltdown] and [https://spectreattack.com/ Spectre] are currently the same<br />
<br />
== References ==<br />
<br />
<references/></div>Mx08https://wiki.raptorcs.com/w/index.php?title=Configuring_Spectre_Protection_Level&diff=3127Configuring Spectre Protection Level2020-03-26T01:15:13Z<p>Mx08: Indicate that the override is controlled by the BMC + add reference to IBM bulletin + improve formatting</p>
<hr />
<div>The Spectre protections on [[POWER9]] can be partly or fully disengaged if desired. Note that disengaging the protections will leave you vulnerable to attack via Spectre variant 2, and could result in data leakage and/or system compromise. "The override is controlled by the BMC and requires a reboot of the POWER9 to take effect."<ref>[ftp://170.225.15.34/ecc/sar/CMA/SFA/08h25/1/AC922_8335-GTH-GTX_OpenPowerReadme.op920.21.xhtml IBM POWER9 Systems LC Server Firmware] 2020-03-26</ref><br />
<br />
To override the protection level:<br />
<br />
<ol><br />
<li>Create/edit the file <code>/var/lib/obmc/cfam_overrides</code> on the BMC.</li><br />
<li>Add the following contents:</li><br />
<pre># Control speculative execution mode<br />
0 0x283a 0x00000001 # bits 28:31 are used for init level -- in this case 1 (Kernel protection only)<br />
0 0x283F 0x20000000 # Indicate override register is valid</pre><br />
<li>Re-[[IPL]] (fully power off and restart the host system) to apply changes.</li><br />
</ol><br />
<br />
Key:<br />
* Init level 0 &mdash; Kernel and User protection (safest, default)<br />
* Init level 1 &mdash; Kernel protection only<br />
* Init level 2 &mdash; No protection<br />
<br />
== See also ==<br />
<br />
* [[Speculative Execution Vulnerabilities of 2018]]<br />
<br />
== References ==<br />
<br />
<references /><br />
<br />
[[Category:Guides]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Configuring_Spectre_Protection_Level&diff=3126Configuring Spectre Protection Level2020-03-26T00:06:50Z<p>Mx08: Undo revision 3125 by Carlosedp (talk) Reason: Summary of the spectre vulnerabilities is off-topic here. I will re-add the useful parts (i.e. new information) in a future revision.</p>
<hr />
<div>The Spectre protections on [[POWER9]] can be partly or fully disengaged if desired. Note that disengaging the protections will leave you vulnerable to attack via Spectre variant 2, and could result in data leakage and/or system compromise.<br />
<br />
To override the protection level:<br />
<br />
* Create/edit the <tt>/var/lib/obmc/cfam_overrides</tt> on the BMC.<br />
* Add the following contents:<br />
# Control speculative execution mode<br />
0 0x283a 0x00000001 # bits 28:31 are used for init level -- in this case 1<br />
0 0x283F 0x20000000 # Indicate scratch 3 is valid<br />
* Re-[[IPL]] (fully power off and restart the host system) to apply changes.<br />
<br />
Key:<br />
* Init level 0 &mdash; Kernel and User protection (safest, default)<br />
* Init level 1 &mdash; Kernel protection only<br />
* Init level 2 &mdash; No protection<br />
<br />
[[Category:Guides]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Configuring_Spectre_Protection_Level&diff=3124Configuring Spectre Protection Level2020-03-25T22:58:40Z<p>Mx08: clarify that a full restart is required to apply the changes</p>
<hr />
<div>The Spectre protections on [[POWER9]] can be partly or fully disengaged if desired. Note that disengaging the protections will leave you vulnerable to attack via Spectre variant 2, and could result in data leakage and/or system compromise.<br />
<br />
To override the protection level:<br />
<br />
* Create/edit the <tt>/var/lib/obmc/cfam_overrides</tt> on the BMC.<br />
* Add the following contents:<br />
# Control speculative execution mode<br />
0 0x283a 0x00000001 # bits 28:31 are used for init level -- in this case 1<br />
0 0x283F 0x20000000 # Indicate scratch 3 is valid<br />
* Re-[[IPL]] (fully power off and restart the host system) to apply changes.<br />
<br />
Key:<br />
* Init level 0 &mdash; Kernel and User protection (safest, default)<br />
* Init level 1 &mdash; Kernel protection only<br />
* Init level 2 &mdash; No protection<br />
<br />
[[Category:Guides]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Configuring_Spectre_Protection_Level&diff=3123Configuring Spectre Protection Level2020-03-25T22:23:27Z<p>Mx08: add hint that "IPL" means booting</p>
<hr />
<div>The Spectre protections on [[POWER9]] can be partly or fully disengaged if desired. Note that disengaging the protections will leave you vulnerable to attack via Spectre variant 2, and could result in data leakage and/or system compromise.<br />
<br />
To override the protection level:<br />
<br />
* Create/edit the <tt>/var/lib/obmc/cfam_overrides</tt> on the BMC.<br />
* Add the following contents:<br />
# Control speculative execution mode<br />
0 0x283a 0x00000001 # bits 28:31 are used for init level -- in this case 1<br />
0 0x283F 0x20000000 # Indicate scratch 3 is valid<br />
* Re-[[IPL]] (reboot) to apply changes.<br />
<br />
Key:<br />
* Init level 0 &mdash; Kernel and User protection (safest, default)<br />
* Init level 1 &mdash; Kernel protection only<br />
* Init level 2 &mdash; No protection<br />
<br />
[[Category:Guides]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Blackbird/Hardware_Compatibility_List&diff=3003Blackbird/Hardware Compatibility List2020-02-10T02:52:44Z<p>Mx08: /* Good Cases */</p>
<hr />
<div>== Cases ==<br />
<br />
=== Good Cases ===<br />
<br />
These cases were successfully used by someone.<br />
<br />
* '''AeroCool CS-101'''<br />
** The C1P9S01 Blackbird is compatible out-of-the-box. It's exhaust fan lines up well above the CPU cooler.<br />
** Any bottom mounted fan needs to be narrow (=<1.5cm), otherwise it collides with the bottom of the motherboard.<br />
** Add-in cards need to be inserted at an angle, as the bracer above them is not removable.<br />
* '''Fractal Design Define R6''' and '''Define R6 USB-C'''<br />
** The case provides three 3-pin fans so you have to use the integrated PWM fan hub to enable fan speed control (otherwise the fans will spin at full speed). Connect the first chassis fan (labeled fan 2 on the motherboard) to the ''CPU fan'' connector of the PWM fan hub to let the motherboard control the fan speed<br />
** The USB 3.0 plug for the front panel of the ''Define R6'' case is too broad at one side (collides with the BMC serial console connector) so you have to remove (polish) a little bit of the rubber of the plug so that it fits completely into the internal USB 3.0 connector of the motherboard ([[Media:defineR6_usb3_mod_small_front.jpg|front view]], [[Media:defineR6_usb3_mod_small_side.jpg|side view]]). If you also want to use the adjacent internal header J7701 (for the BMC serial console), then you have to remove a little bit more of the rubber ([[Media:defineR6_usb3_mod_big_front.jpg|front view]], [[Media:defineR6_usb3_mod_big_side.jpg|side view]], [[Media:defineR6_usb3_mod_big_installed.jpg|mounted]]).<br />
** The HDD LED plug for the front panel cannot be plugged into the motherboard's front panel header because it uses a combined plug for + and - but the pins on the header of the motherboard are not neighbors. You need an adapter (a pair of breadboard jumper cables will do), leave it unplugged or use an extension cord to plug it into ''DISK DRIVE ACTIVITY INDICATOR'' two-pin header (the default cable is too short for that).<br />
** ''Define R6 USB-C'' only: The USB 3.1 Gen2 plug for the front panel cannot be used since the motherboard has no connector for that (and USB 3.1 is most probably not supported at all)<br />
<br />
== Power Supplies ==<br />
<br />
* SilverStone SST-SX500-G 500W (The dedicated CPU power cable must be used rather than the integrated 4-pin, otherwise the Blackbird will not boot.)<br />
<br />
== Fans ==<br />
* As of BMC firmware branch "04-16-2019", Noctua Industrial 140mm (NF-A14 iPPC-2000) do not work correctly. However, normal Noctua 140mm (NF-A14 PWM) work as expected even using a splitter for 4 total fans.<br />
<br />
== Memory ==<br />
See [[POWER9 Hardware Compatibility List/Memory]].<br />
<br />
== PCIe Devices ==<br />
See [[POWER9 Hardware Compatibility List/PCIe Devices]].<br />
<br />
'''NOTE:'''<br />
On the Blackbird, pin 1 of the "BMC TTL AUXILIARY SERIAL HEADER" (J10116) conflicts with some PCIe cards (or their metal mounting bracket) in the lower PCIe 4.0 x8 slot. This is the case for e.g. the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P], where the metal bracket touches pin 1 of J10116 such that either the pin gets bent or the card does not fully seat. Since the conflicting distance is less than 1mm, either the metal bracket or the PCB (depending on which one touches the pin) can be filed/ground a tiny bit (with a hand file or dremel), so that the cards fully seats without bending the pin. When doing so, care must be taken to not let any metal dust touch the PCIe card. Ideally the conflict would only be between the metal bracket and the pin, in which case the metal bracket can be unscrewed from the card and modified separately. Afterwards it should be properly cleaned and (if necessary) dried, before being remounted to the card.<br />
<br />
Here are some pictures from [[user:mx08|mx08]]'s modification to the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P]'s metal bracket:<br />
<gallery><br />
File:J10116_BMC-TTL_conflict.jpg|thumb|baseline|center|Conflict (card not fully seated)<br />
File:AOC-SHG3-4M2P_bracket_removed.jpg|thumb|baseline|center|Metal bracket removed<br />
File:AOC-SHG3-4M2P_bracket_modified.jpg|thumb|baseline|center|Metal bracket modified<br />
File:AOC-SHG3-4M2P_bracket_modified_mounted.jpg|thumb|baseline|center|Metal bracket re-mounted<br />
File:J10116_BMC-TTL_conflict_resolved.jpg|thumb|baseline|center|Conflict resolved<br />
</gallery><br />
<br />
An alternative would maybe be to place a 1mm spacer between the top end of the PCIe card's metal bracket and the case, so that the card can be tightened properly while still making firm contact (?) with the PCIe slot.<br />
<br />
== SATA Storage Drives ==<br />
<br />
SATA storage devices can be connected via the on-board [[88SE9235|Marvell 88SE9235]] controller,<br />
or via an optional SATA controller in the 4x PCIe slot.<br />
<br />
NVMe cards are also supported by using an optional PCIe adapter card (see [[POWER9_Hardware_Compatibility_List/PCIe_Devices#NVMe_Drives]]).<br />
<br />
== Serial port adapters to connect with OpenBMC ==<br />
<br />
Working:<br />
* VTOP USB serial RS232 Adapter - USB to RS232 Serial DB9 9 PIN COM Port Converter cable (about 20 USD)<br />
* DeLock Adapter Sub-D 9Pin Bu/Bu null modem (required for direct computer connections eg. with the VTOP USB-serial-adapter)<br />
* Supermicro CBL-0010L<br />
<br />
== See also ==<br />
* [[Talos II/Hardware Compatibility List|Talos II/Hardware Compatibility List]]<br />
<br />
[[Category:Compatibility List]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Blackbird/Hardware_Compatibility_List&diff=3002Blackbird/Hardware Compatibility List2020-02-10T02:49:04Z<p>Mx08: /* Good Cases */ add pictures of USB3 connector mod</p>
<hr />
<div>== Cases ==<br />
<br />
=== Good Cases ===<br />
<br />
These cases were successfully used by someone.<br />
<br />
* '''AeroCool CS-101'''<br />
** The C1P9S01 Blackbird is compatible out-of-the-box. It's exhaust fan lines up well above the CPU cooler.<br />
** Any bottom mounted fan needs to be narrow (=<1.5cm), otherwise it collides with the bottom of the motherboard.<br />
** Add-in cards need to be inserted at an angle, as the bracer above them is not removable.<br />
* '''Fractal Design Define R6''' and '''Define R6 USB-C'''<br />
** The case provides three 3-pin fans so you have to use the integrated PWM fan hub to enable fan speed control (otherwise the fans will spin at full speed). Connect the first chassis fan (labeled fan 2 on the motherboard) to the ''CPU fan'' connector of the PWM fan hub to let the motherboard control the fan speed<br />
** The USB 3.0 plug for the front panel of the ''Define R6'' case is too broad at one side (collides with the BMC serial console connector) so you have to remove (polish) a little bit of the rubber of the plug so that it fits completely into the internal USB 3.0 connector of the motherboard ([[Media:defineR6_usb3_mod_small_front.jpg|front view]], [[Media:defineR6_usb3_mod_small_side.jpg|side view]]). If you also want to use the adjacent internal header J7701 (for the BMC serial console), then you have to remove a little bit more of the rubber ([[Media:defineR6_usb3_mod_big_front.jpg|front view]], [[Media:defineR6_usb3_mod_big_side.jpg|side view]], [[Media:defineR6_usb3_mod_big_installed.jpg|mounted]]).<br />
** The HDD LED plug for the front panel cannot be plugged into the motherboard's front panel header because it uses a combined plug for + and - but the pins on the header of the motherboard are not neighbors. You need an adapter, leave it unplugged or use an extension cord to plug it into ''DISK DRIVE ACTIVITY INDICATOR'' two-pin header (the default cable is too short for that).<br />
** ''Define R6 USB-C'' only: The USB 3.1 Gen2 plug for the front panel cannot be used since the motherboard has no connector for that (and USB 3.1 is most probably not supported at all)<br />
<br />
== Power Supplies ==<br />
<br />
* SilverStone SST-SX500-G 500W (The dedicated CPU power cable must be used rather than the integrated 4-pin, otherwise the Blackbird will not boot.)<br />
<br />
== Fans ==<br />
* As of BMC firmware branch "04-16-2019", Noctua Industrial 140mm (NF-A14 iPPC-2000) do not work correctly. However, normal Noctua 140mm (NF-A14 PWM) work as expected even using a splitter for 4 total fans.<br />
<br />
== Memory ==<br />
See [[POWER9 Hardware Compatibility List/Memory]].<br />
<br />
== PCIe Devices ==<br />
See [[POWER9 Hardware Compatibility List/PCIe Devices]].<br />
<br />
'''NOTE:'''<br />
On the Blackbird, pin 1 of the "BMC TTL AUXILIARY SERIAL HEADER" (J10116) conflicts with some PCIe cards (or their metal mounting bracket) in the lower PCIe 4.0 x8 slot. This is the case for e.g. the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P], where the metal bracket touches pin 1 of J10116 such that either the pin gets bent or the card does not fully seat. Since the conflicting distance is less than 1mm, either the metal bracket or the PCB (depending on which one touches the pin) can be filed/ground a tiny bit (with a hand file or dremel), so that the cards fully seats without bending the pin. When doing so, care must be taken to not let any metal dust touch the PCIe card. Ideally the conflict would only be between the metal bracket and the pin, in which case the metal bracket can be unscrewed from the card and modified separately. Afterwards it should be properly cleaned and (if necessary) dried, before being remounted to the card.<br />
<br />
Here are some pictures from [[user:mx08|mx08]]'s modification to the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P]'s metal bracket:<br />
<gallery><br />
File:J10116_BMC-TTL_conflict.jpg|thumb|baseline|center|Conflict (card not fully seated)<br />
File:AOC-SHG3-4M2P_bracket_removed.jpg|thumb|baseline|center|Metal bracket removed<br />
File:AOC-SHG3-4M2P_bracket_modified.jpg|thumb|baseline|center|Metal bracket modified<br />
File:AOC-SHG3-4M2P_bracket_modified_mounted.jpg|thumb|baseline|center|Metal bracket re-mounted<br />
File:J10116_BMC-TTL_conflict_resolved.jpg|thumb|baseline|center|Conflict resolved<br />
</gallery><br />
<br />
An alternative would maybe be to place a 1mm spacer between the top end of the PCIe card's metal bracket and the case, so that the card can be tightened properly while still making firm contact (?) with the PCIe slot.<br />
<br />
== SATA Storage Drives ==<br />
<br />
SATA storage devices can be connected via the on-board [[88SE9235|Marvell 88SE9235]] controller,<br />
or via an optional SATA controller in the 4x PCIe slot.<br />
<br />
NVMe cards are also supported by using an optional PCIe adapter card (see [[POWER9_Hardware_Compatibility_List/PCIe_Devices#NVMe_Drives]]).<br />
<br />
== Serial port adapters to connect with OpenBMC ==<br />
<br />
Working:<br />
* VTOP USB serial RS232 Adapter - USB to RS232 Serial DB9 9 PIN COM Port Converter cable (about 20 USD)<br />
* DeLock Adapter Sub-D 9Pin Bu/Bu null modem (required for direct computer connections eg. with the VTOP USB-serial-adapter)<br />
* Supermicro CBL-0010L<br />
<br />
== See also ==<br />
* [[Talos II/Hardware Compatibility List|Talos II/Hardware Compatibility List]]<br />
<br />
[[Category:Compatibility List]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=File:DefineR6_usb3_mod_big_installed.jpg&diff=3001File:DefineR6 usb3 mod big installed.jpg2020-02-10T02:40:57Z<p>Mx08: </p>
<hr />
<div></div>Mx08https://wiki.raptorcs.com/w/index.php?title=File:DefineR6_usb3_mod_big_side.jpg&diff=3000File:DefineR6 usb3 mod big side.jpg2020-02-10T02:40:42Z<p>Mx08: </p>
<hr />
<div></div>Mx08https://wiki.raptorcs.com/w/index.php?title=File:DefineR6_usb3_mod_big_front.jpg&diff=2999File:DefineR6 usb3 mod big front.jpg2020-02-10T02:40:27Z<p>Mx08: </p>
<hr />
<div></div>Mx08https://wiki.raptorcs.com/w/index.php?title=File:DefineR6_usb3_mod_small_side.jpg&diff=2998File:DefineR6 usb3 mod small side.jpg2020-02-10T02:40:10Z<p>Mx08: </p>
<hr />
<div></div>Mx08https://wiki.raptorcs.com/w/index.php?title=File:DefineR6_usb3_mod_small_front.jpg&diff=2997File:DefineR6 usb3 mod small front.jpg2020-02-10T02:39:47Z<p>Mx08: </p>
<hr />
<div></div>Mx08https://wiki.raptorcs.com/w/index.php?title=Blackbird/Hardware_Compatibility_List&diff=2996Blackbird/Hardware Compatibility List2020-02-10T02:26:55Z<p>Mx08: /* Good Cases */ small reformat</p>
<hr />
<div>== Cases ==<br />
<br />
=== Good Cases ===<br />
<br />
These cases were successfully used by someone.<br />
<br />
* '''AeroCool CS-101'''<br />
** The C1P9S01 Blackbird is compatible out-of-the-box. It's exhaust fan lines up well above the CPU cooler.<br />
** Any bottom mounted fan needs to be narrow (=<1.5cm), otherwise it collides with the bottom of the motherboard.<br />
** Add-in cards need to be inserted at an angle, as the bracer above them is not removable.<br />
* '''Fractal Design Define R6''' and '''Define R6 USB-C'''<br />
** The case provides three 3-pin fans so you have to use the integrated PWM fan hub to enable fan speed control (otherwise the fans will spin at full speed). Connect the first chassis fan (labeled fan 2 on the motherboard) to the ''CPU fan'' connector of the PWM fan hub to let the motherboard control the fan speed<br />
** The USB 3.0 plug for the front panel of the ''Define R6'' case is too broad at one side (collides with the BMC serial console connector) so you have to remove (polish) a little bit of the rubber of the plug so that it fits completely into the internal USB 3.0 connector of the motherboard (TODO add a picture)<br />
** The HDD LED plug for the front panel cannot be plugged into the motherboard's front panel header because it uses a combined plug for + and - but the pins on the header of the motherboard are not neighbors. You need an adapter, leave it unplugged or use an extension cord to plug it into ''DISK DRIVE ACTIVITY INDICATOR'' two-pin header (the default cable is too short for that).<br />
** ''Define R6 USB-C'' only: The USB 3.1 Gen2 plug for the front panel cannot be used since the motherboard has no connector for that (and USB 3.1 is most probably not supported at all)<br />
<br />
== Power Supplies ==<br />
<br />
* SilverStone SST-SX500-G 500W (The dedicated CPU power cable must be used rather than the integrated 4-pin, otherwise the Blackbird will not boot.)<br />
<br />
== Fans ==<br />
* As of BMC firmware branch "04-16-2019", Noctua Industrial 140mm (NF-A14 iPPC-2000) do not work correctly. However, normal Noctua 140mm (NF-A14 PWM) work as expected even using a splitter for 4 total fans.<br />
<br />
== Memory ==<br />
See [[POWER9 Hardware Compatibility List/Memory]].<br />
<br />
== PCIe Devices ==<br />
See [[POWER9 Hardware Compatibility List/PCIe Devices]].<br />
<br />
'''NOTE:'''<br />
On the Blackbird, pin 1 of the "BMC TTL AUXILIARY SERIAL HEADER" (J10116) conflicts with some PCIe cards (or their metal mounting bracket) in the lower PCIe 4.0 x8 slot. This is the case for e.g. the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P], where the metal bracket touches pin 1 of J10116 such that either the pin gets bent or the card does not fully seat. Since the conflicting distance is less than 1mm, either the metal bracket or the PCB (depending on which one touches the pin) can be filed/ground a tiny bit (with a hand file or dremel), so that the cards fully seats without bending the pin. When doing so, care must be taken to not let any metal dust touch the PCIe card. Ideally the conflict would only be between the metal bracket and the pin, in which case the metal bracket can be unscrewed from the card and modified separately. Afterwards it should be properly cleaned and (if necessary) dried, before being remounted to the card.<br />
<br />
Here are some pictures from [[user:mx08|mx08]]'s modification to the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P]'s metal bracket:<br />
<gallery><br />
File:J10116_BMC-TTL_conflict.jpg|thumb|baseline|center|Conflict (card not fully seated)<br />
File:AOC-SHG3-4M2P_bracket_removed.jpg|thumb|baseline|center|Metal bracket removed<br />
File:AOC-SHG3-4M2P_bracket_modified.jpg|thumb|baseline|center|Metal bracket modified<br />
File:AOC-SHG3-4M2P_bracket_modified_mounted.jpg|thumb|baseline|center|Metal bracket re-mounted<br />
File:J10116_BMC-TTL_conflict_resolved.jpg|thumb|baseline|center|Conflict resolved<br />
</gallery><br />
<br />
An alternative would maybe be to place a 1mm spacer between the top end of the PCIe card's metal bracket and the case, so that the card can be tightened properly while still making firm contact (?) with the PCIe slot.<br />
<br />
== SATA Storage Drives ==<br />
<br />
SATA storage devices can be connected via the on-board [[88SE9235|Marvell 88SE9235]] controller,<br />
or via an optional SATA controller in the 4x PCIe slot.<br />
<br />
NVMe cards are also supported by using an optional PCIe adapter card (see [[POWER9_Hardware_Compatibility_List/PCIe_Devices#NVMe_Drives]]).<br />
<br />
== Serial port adapters to connect with OpenBMC ==<br />
<br />
Working:<br />
* VTOP USB serial RS232 Adapter - USB to RS232 Serial DB9 9 PIN COM Port Converter cable (about 20 USD)<br />
* DeLock Adapter Sub-D 9Pin Bu/Bu null modem (required for direct computer connections eg. with the VTOP USB-serial-adapter)<br />
* Supermicro CBL-0010L<br />
<br />
== See also ==<br />
* [[Talos II/Hardware Compatibility List|Talos II/Hardware Compatibility List]]<br />
<br />
[[Category:Compatibility List]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Errata_and_Improvements&diff=2995Errata and Improvements2020-02-10T02:25:34Z<p>Mx08: /* Blackbird specific */ The position of the HDD LED anode is not an erratum in the manual, all PINs are labeled correctly. Feel free to re-add this point under "misc. improvements" if you like (e.g. proposal to change header / include adapter).</p>
<hr />
<div>==Purpose==<br />
This is a place where mistakes in the user manuals (and other RaptorCS documents) as well as possible improvements (all kinds of things) can be collected, so that they don't get lost.<br />
<br />
User Manual for:<br />
* [[:File:T2P9D01_users_guide_version_1_0.pdf|Talos II]]<br />
* [[:File:C1P9S01_users_guide_version_1_0.pdf|Blackbird]]<br />
<br />
==RCS User Manual==<br />
<br />
===Errata===<br />
<br />
====Talos II specific====<br />
* p.16: Add note that indium pads are not required for 4-/8-core CPUs. Currently, the manual explicitly tells you to install indium pads.<br />
<br />
====Blackbird specific====<br />
* p.14: Explicitly notes to install an indium pad, however no indium pads are provided nor required for the 4-/8-core CPUs which come with the Blackbird<br />
* p.15: There is only one CPU socket available on Blackbird but the user manual says: ''If you have a second CPU, repeat this process for the other socket.''<br />
* p.22: Big Blue Arrow points to wrong header (USB3 instead of TPM)<br />
* p.37: "ON-BOARD VGA DISABLE JUMPER" - but there is no VGA on the Blackbird<br />
<br />
====Talos II & Blackbird====<br />
* Internal USB2.0 Type-A port is not mentioned in the manual<br />
* Internal USB2.0 Type-A port is falsely shown to be connected to the BMC in the block diagrams<br />
<br />
===Possible Improvements===<br />
<br />
====Talos II specific====<br />
* p.17: HSF REMOVAL: Add note that during removal the CPU might stick to the HSF via a potentially installed indium pad. If it then falls down in an angle on the socket, the board is most likely damaged.<br />
<br />
====Blackbird specific====<br />
* p.39: Mark internal audio header as "HDA compatible" more visibly?<br />
<br />
====Talos II & Blackbird====<br />
* Installation description (Talos II: p.13, Blackbird: p.11) should mention especially that there must be '''no more''' mounting studs installed in the case than required.<br />
* Include a front view of the I/O panel naming each port. Esp. indicate which of the RJ-45 ports is connected to the BMC.<br />
* In the HSF INSTALLATION section, explicitly advise against thermal paste, since it's not required and complicates removal of the HSF (CPU may stick, then fall down angled and damage the socket).<br />
<br />
==RCS Schematics==<br />
<br />
===Errata===<br />
<br />
====Talos II specific====<br />
*CPUFAN0 and CPUFAN1 labels are swapped (according to awordnot in #talos-workstation)<br />
<br />
==Miscellaneous Improvements==<br />
* Use a different font on the BMC default password snippets that will make distinguishing the letters 1/l/I and O/0 ''possible at all'' (users regularly have trouble with reading them)<br />
* Explain how to change the BMC password and add a link to printed default password delivered together with the Blackbird. For Talos II there already exists a [[Talos_II_Beginner's_Quick_Start_Guide#Changing_The_Password|how to change the OpenBMC passsword wiki entry]] which should work for Blackbird too.<br />
* Indicate in the BMC hostname whether it's the host or the BMC, e.g. "blackbird-bmc" instead of "blackbird"<br />
* RCS could include 2 plastic mainboard standoffs [https://www.pccables.com/images/STANDOFFS-MOTHERBOARD-STANDARD-MB-PLASTIC-100-PACK.jpg like these] with the mainboard, since missing standoffs are ''very common'', as can be seen here: [[Talos II/Hardware Compatibility List#Problematic Cases]]. They are very cheap in bulk and should not add up much to the cost.<br />
* Provide high-res pictures of the Blackbird board, like for the Talos II: [[:File:Talos ii rev 1.00 top.png|Top]] and [[:File:Talos ii rev 1.00 bottom.png|Bottom]]<br />
* RCS should notify customers if the purchased products are not expected to be getting shipped (start of shipping) in a certain timeframe, e.g. 2 weeks.<br />
* RCS could provide customers with a regular (e.g. monthly) update on their order. (Due to long shipping delays and sometimes unresponsive support, some people were worried if their order will ship at all, and asked about it in the [[IRC| IRC channel]].<br />
* The default PWM duty cycle on the Blackbird is 25/255, which is roughly 10%. For many common consumer fans, this is not enough, many expect the duty cycle to be in the range 20% - 100%. See also [https://noctua.at/media/wysiwyg/Noctua_PWM_specifications_white_paper.pdf this Noctua whitepaper] and [https://www.glkinst.com/cables/cable_pics/4_Wire_PWM_Spec.pdf this 4 wire PWM Spec]. This might (?) also apply to the Talos 2. Tested on Blackbird System Package v1.00.<br />
<br />
=See also=<br />
* [[Desktop Roadmap]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Errata_and_Improvements&diff=2994Errata and Improvements2020-02-10T02:19:34Z<p>Mx08: /* Blackbird specific */ remove hints on how to solve problems since this is only for collecting errata</p>
<hr />
<div>==Purpose==<br />
This is a place where mistakes in the user manuals (and other RaptorCS documents) as well as possible improvements (all kinds of things) can be collected, so that they don't get lost.<br />
<br />
User Manual for:<br />
* [[:File:T2P9D01_users_guide_version_1_0.pdf|Talos II]]<br />
* [[:File:C1P9S01_users_guide_version_1_0.pdf|Blackbird]]<br />
<br />
==RCS User Manual==<br />
<br />
===Errata===<br />
<br />
====Talos II specific====<br />
* p.16: Add note that indium pads are not required for 4-/8-core CPUs. Currently, the manual explicitly tells you to install indium pads.<br />
<br />
====Blackbird specific====<br />
* p.14: Explicitly notes to install an indium pad, however no indium pads are provided nor required for the 4-/8-core CPUs which come with the Blackbird<br />
* p.15: There is only one CPU socket available on Blackbird but the user manual says: ''If you have a second CPU, repeat this process for the other socket.''<br />
* p.19/20: Shows the Front Panel PIN for the *HDD activity LED cathode* but not the PIN for the anode (HDD activity LEDs are often having both PINs in one plug so they should paired on the motherboard).<br />
* p.22: Big Blue Arrow points to wrong header (USB3 instead of TPM)<br />
* p.37: "ON-BOARD VGA DISABLE JUMPER" - but there is no VGA on the Blackbird<br />
<br />
====Talos II & Blackbird====<br />
* Internal USB2.0 Type-A port is not mentioned in the manual<br />
* Internal USB2.0 Type-A port is falsely shown to be connected to the BMC in the block diagrams<br />
<br />
===Possible Improvements===<br />
<br />
====Talos II specific====<br />
* p.17: HSF REMOVAL: Add note that during removal the CPU might stick to the HSF via a potentially installed indium pad. If it then falls down in an angle on the socket, the board is most likely damaged.<br />
<br />
====Blackbird specific====<br />
* p.39: Mark internal audio header as "HDA compatible" more visibly?<br />
<br />
====Talos II & Blackbird====<br />
* Installation description (Talos II: p.13, Blackbird: p.11) should mention especially that there must be '''no more''' mounting studs installed in the case than required.<br />
* Include a front view of the I/O panel naming each port. Esp. indicate which of the RJ-45 ports is connected to the BMC.<br />
* In the HSF INSTALLATION section, explicitly advise against thermal paste, since it's not required and complicates removal of the HSF (CPU may stick, then fall down angled and damage the socket).<br />
<br />
==RCS Schematics==<br />
<br />
===Errata===<br />
<br />
====Talos II specific====<br />
*CPUFAN0 and CPUFAN1 labels are swapped (according to awordnot in #talos-workstation)<br />
<br />
==Miscellaneous Improvements==<br />
* Use a different font on the BMC default password snippets that will make distinguishing the letters 1/l/I and O/0 ''possible at all'' (users regularly have trouble with reading them)<br />
* Explain how to change the BMC password and add a link to printed default password delivered together with the Blackbird. For Talos II there already exists a [[Talos_II_Beginner's_Quick_Start_Guide#Changing_The_Password|how to change the OpenBMC passsword wiki entry]] which should work for Blackbird too.<br />
* Indicate in the BMC hostname whether it's the host or the BMC, e.g. "blackbird-bmc" instead of "blackbird"<br />
* RCS could include 2 plastic mainboard standoffs [https://www.pccables.com/images/STANDOFFS-MOTHERBOARD-STANDARD-MB-PLASTIC-100-PACK.jpg like these] with the mainboard, since missing standoffs are ''very common'', as can be seen here: [[Talos II/Hardware Compatibility List#Problematic Cases]]. They are very cheap in bulk and should not add up much to the cost.<br />
* Provide high-res pictures of the Blackbird board, like for the Talos II: [[:File:Talos ii rev 1.00 top.png|Top]] and [[:File:Talos ii rev 1.00 bottom.png|Bottom]]<br />
* RCS should notify customers if the purchased products are not expected to be getting shipped (start of shipping) in a certain timeframe, e.g. 2 weeks.<br />
* RCS could provide customers with a regular (e.g. monthly) update on their order. (Due to long shipping delays and sometimes unresponsive support, some people were worried if their order will ship at all, and asked about it in the [[IRC| IRC channel]].<br />
* The default PWM duty cycle on the Blackbird is 25/255, which is roughly 10%. For many common consumer fans, this is not enough, many expect the duty cycle to be in the range 20% - 100%. See also [https://noctua.at/media/wysiwyg/Noctua_PWM_specifications_white_paper.pdf this Noctua whitepaper] and [https://www.glkinst.com/cables/cable_pics/4_Wire_PWM_Spec.pdf this 4 wire PWM Spec]. This might (?) also apply to the Talos 2. Tested on Blackbird System Package v1.00.<br />
<br />
=See also=<br />
* [[Desktop Roadmap]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=POWER9&diff=2993POWER92020-02-10T02:15:49Z<p>Mx08: /* Production steppings */ rename headline, since DD2.1 is not "production"</p>
<hr />
<div>{{Infobox<br />
|title = Processor Information<br />
|header1 = POWER9<br />
|label2 = [[Power ISA|Power ISA]]<br />
|data2 = 3.0B<br />
|label3 = Process node<br />
|data3 = 14nm<br />
|label4 = Maximum slices<br />
|data4 = 24<br />
|label5 = Maximum cores<br />
|data5 = 12 [[SMT8|SMT8]] / 24 [[SMT4|SMT4]]<br />
|label6 = L2 cache / slice<br />
|data6 = 512kB<br />
|label7 = L3 cache / slice<br />
|data7 = 10MB<br />
|label8 = Production availability<br />
|data8 = January 2018<br />
|label9 = Production stepping(s)<br />
|data9 = DD2.2, DD2.3<br />
|label10 = [[POWER8E|← POWER8E]]<br />
|data10 = POWER10 → <br />
}}<br />
<br />
POWER9 is IBM's most recent POWER compatible server and workstation CPU ([[Power ISA|POWER ISA]] v3.0B). Built on a 14nm process, each CPU package can contain up to 24 [[SMT4|SMT4]] cores or 12 [[SMT8|SMT8]] cores. Each pair of [[SMT4|SMT4]] cores, or singleton [[SMT8|SMT8]] core, comprises a slice; each slice in turn contains 512kB L2 cache and 10MB L3 cache. Raptor Computing Systems' 4- and 8-core processors provide unpaired cores, such that one [[SMT4|SMT4]] core per slice is fused off. This allows each of the [[SMT4|SMT4]] cores to utilize the full cache of the slice exclusively, increasing performance for these [[Single_Thread|ST]]-focused processors.<br />
<br />
==Process==<br />
POWER9 is fabricated using the GlobalFoundries 14HP (High Performance) process. This is distinct from the GlobalFoundries 14LPP (Low Power) process used by other GF 14nm customers, and is believed to be an IBM-specific process using ex-IBM Microelectronics intellectual property. The process is also used for the CPUs in IBM's z14 mainframes. [https://fuse.wikichip.org/news/956/globalfoundries-14hp-process-a-marriage-of-two-technologies/ A detailed discussion of 14HP and how it differs from 14LPP is available here.]<br />
<br />
== Chips ==<br />
<br />
There are three known silicon masks of POWER9:<br />
* Nimbus (POWER9 [[Scale Out]])<br />
* Cumulus (POWER9 [[Scale Up]])<br />
* Axone (POWER9&prime; ("POWER9 Prime"), aka POWER9 with Advanced I/O)<br />
<br />
Nimbus is the &#8220;[[Scale Out|scale out]]&#8221; variant and uses direct-attach DDR4 memory. Cumulus is the &#8220;[[Scale Up|scale up]]&#8221; version and uses [[Centaur]] memory buffers, allowing larger amounts of memory to be attached to a system.<br />
<br />
Chips can be fused as [[SMT4]] or [[SMT8]] during manufacturing. The [[SMT8]] variant essentially fuses each pair of cores into one &#8220;core&#8221;, halving the core count while doubling the number of threads per core. [[SMT4]] variants are intended for [[PowerNV]] platforms running Linux, and [[SMT8]] variants are intended for use with IBM's PowerVM hypervisor which can run Linux, AIX or IBM i.<ref>Stuecheli, Jeff. POWER9. Presentation for [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Power+Systems/page/AIX+Virtual+User+Group+-+USA AIX VUG]. ([https://public.dhe.ibm.com/systems/power/community/aix/Central-VUG-Replays/2017-01-26_IBM_POWER9.wmv video download], [https://www.ibm.com/developerworks/community/wikis/form/anonymous/api/wiki/61ad9cf2-c6a3-4d2c-b779-61ff0266d32a/page/1cb956e8-4160-4bea-a956-e51490c2b920/attachment/56cea2a9-a574-4fbb-8b2c-675432367250/media/POWER9-VUG.pdf slides], [[User:Torpcoms/Timemark/POWER9|timemarks]])</ref><br />
<br />
== Modules ==<br />
<br />
{| class="wikitable"<br />
|+ POWER9 Modules<br />
! Chip<br />
! Module<br />
! Memory Channels<br />
! XBUS Lanes<br />
! PCIe Lanes<br />
! OpenCAPI Lanes<br />
! Socket<br />
|-<br />
!rowspan="3"|Nimbus<br />
| [[Sforza]]<br />
| 4<br />
| 1<br />
| 48<br />
| 0<br />
| LGA 2601<br />
|-<br />
| [[Monza]]<br />
| 8<br />
| 1<br />
| 34<br />
| 48<br />
| LGA 3899<br />
|-<br />
| [[LaGrange]]<br />
| 8<br />
| 2<br />
| 42<br />
| 16<br />
| LGA 3899<br />
|-<br />
! Cumulus<br />
| (unknown)<br />
| (memory attached via [[Centaur|Centaurs]])<br />
| (unknown)<br />
| (unknown)<br />
| (unknown)<br />
| ?<br />
|-<br />
! Axon<br />
| (unknown)<br />
| (memory attached via OMI)<br />
| Up to 3<br />
| Up to 48<br />
| Up to 48<br />
| ?<br />
|}<br />
<br />
'''''XBUS''' is used for inter-processor communication on dual-socket system''<br />
<br />
=== Nimbus ===<br />
<br />
Nimbus chips are available in three different modules: [[Sforza]], [[Monza]], and [[LaGrange]]. Each module uses the same silicon mask but is packaged differently, exposing different I/O functionality to the host platform, allowing purpose-built systems to be constructed in addition to more general-purpose computers.<br />
<br />
'''[[Sforza|Sforza]]''' is the most flexible of these packages, providing PCIe 4.0 lanes as the main I/O resource, and is what [[Talos_II|Talos™ II]] uses for maximal similarity to existing desktop, workstation, and server systems.<br />
<br />
'''[[Monza|Monza]]''' modules offer the most OpenCAPI/NVLink bandwidth and are used in IBM's AC922 (Witherspoon) systems, such as those used by the Sierra and Summit supercomputers.<br />
<br />
'''[[LaGrange|LaGrange]]''' modules offer increased XBus bandwidth between processor sockets and are used by the Google/Rackspace Zaius motherboard used in the Barreleye G2 system.<ref>Gangidi, Adi [https://blog.rackspace.com/zaius-barreleye-g2-server-development-update-2 Zaius/Barreleye G2 Server Development Update]. 2017-11-13</ref><br />
<br />
Part numbers for different POWER9 Sforza SKUs can be found on page 58 of the [[:File:POWER9 Sforza DS v16 23JUL2018 pub.pdf|datasheet]]. These part numbers are printed on the surface of the CPU module and can be used to determine the type of the CPU.<br />
<br />
===== Steppings =====<br />
<br />
Several revisions of the Nimbus mask have been issued:<br />
<br />
* DD2.1 was the final preproduction revision before GA. It has errata preventing the use of hardware virtualization, but DD2.1 Sforza can be used in e.g. the [[Talos II]] if this functionality is not needed.<br />
* DD2.2 is the first GA revision of Nimbus. DD2.2 Sforza is sold at [https://raptorcs.com/ raptorcs.com].<br />
* DD2.3 is an updated revision of Nimbus. They added Ultravisor functionality and Hardware watchpoint support, also improved Meltdown and Spectre mitigations. DD2.3 parts are sold at [https://raptorcs.com/ raptorcs.com] under the designation POWER9 v2.<br />
<br />
=== Cumulus ===<br />
<br />
Little is known about Cumulus chips at this time; as Scale Up chips, they will trade some I/O bandwidth for support for more than two sockets.<ref>Morgan, Timothy Prickett. [https://www.nextplatform.com/2017/12/05/power9-to-the-people/ POWER9 to the People]. 2017-12-05</ref><br />
<br />
=== Axone ===<br />
<br />
Branded POWER9&prime; ("POWER9 Prime"), also known as POWER9 with Advanced I/O. Newly announced in August 2019. Uses serial memory attachment via OMI, an evolution from the [[Centaur]].<br />
<br />
== References ==<br />
<br />
<references/><br />
<br />
== Resources ==<br />
<br />
* '''[[:Category:Documentation|POWER9 CPU and Platform Documentation]]'''<br />
* [[POWER9 Hardware Compatibility List]]<br />
* [[:File:POWER9-Features-and-Specifications.pdf|Basic POWER9 overview presentation]]<br />
* [[:File:PowerISA_public.v3.0B.pdf|Power ISA version 3.0B]] - implemented by POWER9<br />
<br />
== External Links ==<br />
<br />
* [https://en.wikipedia.org/wiki/POWER9 POWER9 English Wikipedia page]<br />
* [https://en.wikichip.org/wiki/ibm/microarchitectures/power9 POWER9 wikichip page]<br />
[[Category:POWER9|*]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Talk:Errata_and_Improvements&diff=2992Talk:Errata and Improvements2020-02-10T01:43:01Z<p>Mx08: /* What does "disable VGA jumper" do instead? */</p>
<hr />
<div>== What does "disable VGA jumper" do instead? ==<br />
<br />
The errata says<br />
<br />
> p.37: "ON-BOARD VGA DISABLE JUMPER" - but there is no VGA on the Blackbird<br />
<br />
but it is unclear what the jumper does instead (it seems to exist on the board).<br />
<br />
My guess: Is this the "Disable AST VGA with jumper" instead?<br />
<br />
: I think so, but I'm not 100% sure. FWIW Raptor is aware that this page exists and told me that they would look into the issues and apply appropriate changes to the next revision of the manuals. [[User:Mx08|Mx08]] ([[User talk:Mx08|talk]]) 19:42, 9 February 2020 (CST)<br />
<br />
== Existence of USB 2.0 header is unclear ==<br />
<br />
The errata says<br />
<br />
> Internal USB2.0 Type-A port is not mentioned in the manual<br />
<br />
It leaves open: Is there a USB 2.0 header for Talos II and Blackbird on the motherboard? Where is it?<br />
<br />
: There exists an internal USB2.0 Type-A port on both the Talos II and the Blackbird. Note it's not an internal header but a "Type-A port" which are common for e.g. USB sticks etc. Just look at the board, it's easy to find :) [[User:Mx08|Mx08]] ([[User talk:Mx08|talk]]) 19:38, 9 February 2020 (CST)</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Talk:Errata_and_Improvements&diff=2991Talk:Errata and Improvements2020-02-10T01:38:08Z<p>Mx08: answer question</p>
<hr />
<div>== What does "disable VGA jumper" do instead? ==<br />
<br />
The errata says<br />
<br />
> p.37: "ON-BOARD VGA DISABLE JUMPER" - but there is no VGA on the Blackbird<br />
<br />
but it is unclear what the jumper does instead (it seems to exist on the board).<br />
<br />
My guess: Is this the "Disable AST VGA with jumper" instead?<br />
<br />
== Existence of USB 2.0 header is unclear ==<br />
<br />
The errata says<br />
<br />
> Internal USB2.0 Type-A port is not mentioned in the manual<br />
<br />
It leaves open: Is there a USB 2.0 header for Talos II and Blackbird on the motherboard? Where is it?<br />
<br />
: There exists an internal USB2.0 Type-A port on both the Talos II and the Blackbird. Note it's not an internal header but a "Type-A port" which are common for e.g. USB sticks etc. Just look at the board, it's easy to find :) [[User:Mx08|Mx08]] ([[User talk:Mx08|talk]]) 19:38, 9 February 2020 (CST)</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Talk:Errata_and_Improvements&diff=2990Talk:Errata and Improvements2020-02-10T01:34:28Z<p>Mx08: remove conversation about indium pads</p>
<hr />
<div>== What does "disable VGA jumper" do instead? ==<br />
<br />
The errata says<br />
<br />
> p.37: "ON-BOARD VGA DISABLE JUMPER" - but there is no VGA on the Blackbird<br />
<br />
but it is unclear what the jumper does instead (it seems to exist on the board).<br />
<br />
My guess: Is this the "Disable AST VGA with jumper" instead?<br />
<br />
== Existence of USB 2.0 header is unclear ==<br />
<br />
The errata says<br />
<br />
> Internal USB2.0 Type-A port is not mentioned in the manual<br />
<br />
It leaves open: Is there a USB 2.0 header for Talos II and Blackbird on the motherboard? Where is it?</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Blackbird/Hardware_Compatibility_List&diff=2800Blackbird/Hardware Compatibility List2019-11-17T08:37:17Z<p>Mx08: /* Good Cases */ add Fractal Design Define R6</p>
<hr />
<div>== Cases ==<br />
<br />
=== Good Cases ===<br />
<br />
These cases were successfully used by someone.<br />
<br />
* '''AeroCool CS-101'''<br />
** The C1P9S01 Blackbird is compatible out-of-the-box. It's exhaust fan lines up well above the CPU cooler.<br />
** Any bottom mounted fan needs to be narrow (=<1.5cm), otherwise it collides with the bottom of the motherboard.<br />
** Add-in cards need to be inserted at an angle, as the bracer above them is not removable.<br />
* '''Fractal Design Define R6'''<br />
<br />
== Power Supplies ==<br />
<br />
* SilverStone SST-SX500-G 500W (The dedicated CPU power cable must be used rather than the integrated 4-pin, otherwise the Blackbird will not boot.)<br />
<br />
== Fans ==<br />
* As of BMC firmware branch "04-16-2019", Noctua Industrial 140mm (NF-A14 iPPC-2000) do not work correctly. However, normal Noctua 140mm (NF-A14 PWM) work as expected even using a splitter for 4 total fans.<br />
<br />
== Memory ==<br />
See [[POWER9 Hardware Compatibility List/Memory]].<br />
<br />
== PCIe Devices ==<br />
See [[POWER9 Hardware Compatibility List/PCIe Devices]].<br />
<br />
'''NOTE:'''<br />
On the Blackbird, pin 1 of the "BMC TTL AUXILIARY SERIAL HEADER" (J10116) conflicts with some PCIe cards (or their metal mounting bracket) in the lower PCIe 4.0 x8 slot. This is the case for e.g. the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P], where the metal bracket touches pin 1 of J10116 such that either the pin gets bent or the card does not fully seat. Since the conflicting distance is less than 1mm, either the metal bracket or the PCB (depending on which one touches the pin) can be filed/ground a tiny bit (with a hand file or dremel), so that the cards fully seats without bending the pin. When doing so, care must be taken to not let any metal dust touch the PCIe card. Ideally the conflict would only be between the metal bracket and the pin, in which case the metal bracket can be unscrewed from the card and modified separately. Afterwards it should be properly cleaned and (if necessary) dried, before being remounted to the card.<br />
<br />
Here are some pictures from [[user:mx08|mx08]]'s modification to the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P]'s metal bracket:<br />
<gallery><br />
File:J10116_BMC-TTL_conflict.jpg|thumb|baseline|center|Conflict (card not fully seated)<br />
File:AOC-SHG3-4M2P_bracket_removed.jpg|thumb|baseline|center|Metal bracket removed<br />
File:AOC-SHG3-4M2P_bracket_modified.jpg|thumb|baseline|center|Metal bracket modified<br />
File:AOC-SHG3-4M2P_bracket_modified_mounted.jpg|thumb|baseline|center|Metal bracket re-mounted<br />
File:J10116_BMC-TTL_conflict_resolved.jpg|thumb|baseline|center|Conflict resolved<br />
</gallery><br />
<br />
An alternative would maybe be to place a 1mm spacer between the top end of the PCIe card's metal bracket and the case, so that the card can be tightened properly while still making firm contact (?) with the PCIe slot.<br />
<br />
== SATA Storage Drives ==<br />
Connected via optional on-board [[88SE9235|88SE9235]] controller, or via PCIe controller. NVMe cards are also supported. <br />
<br />
== See also ==<br />
* [[Talos II/Hardware Compatibility List|Talos II/Hardware Compatibility List]]<br />
<br />
[[Category:Compatibility List]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Errata_and_Improvements&diff=2778Errata and Improvements2019-10-20T14:46:51Z<p>Mx08: /* Miscellaneous Improvements */ add note about stock PWM duty cycle being too low</p>
<hr />
<div>==Purpose==<br />
This is a place where mistakes in the user manuals (and other RaptorCS documents) as well as possible improvements (all kinds of things) can be collected, so that they don't get lost.<br />
<br />
User Manual for:<br />
* [[:File:T2P9D01_users_guide_version_1_0.pdf|Talos II]]<br />
* [[:File:C1P9S01_users_guide_version_1_0.pdf|Blackbird]]<br />
<br />
==RCS User Manual==<br />
<br />
===Errata===<br />
<br />
====Talos II specific====<br />
* p.16: Add note that indium pads are not required for 4-/8-core CPUs. Currently, the manual explicitly tells you to install indium pads.<br />
<br />
====Blackbird specific====<br />
* p.22: Big Blue Arrow points to wrong header (USB3 instead of TPM)<br />
* p.37: "ON-BOARD VGA DISABLE JUMPER" - but there is no VGA on the Blackbird<br />
* p.14 explicitly notes to install an indium pad, however no indium pads are provided nor required for the 4-/8-core CPUs which come with the Blackbird<br />
<br />
====Talos II & Blackbird====<br />
* Internal USB2.0 Type-A port is not mentioned in the manual<br />
* Internal USB2.0 Type-A port is falsely shown to be connected to the BMC in the block diagrams<br />
<br />
===Possible Improvements===<br />
<br />
====Talos II specific====<br />
* p.17: HSF REMOVAL: Add note that during removal the CPU might stick to the HSF via a potentially installed indium pad. If it then falls down in an angle on the socket, the board is most likely damaged.<br />
<br />
====Blackbird specific====<br />
* p.39: Mark internal audio header as "HDA compatible" more visibly?<br />
<br />
====Talos II & Blackbird====<br />
* Installation description (Talos II: p.13, Blackbird: p.11) should mention especially that there must be '''no more''' mounting studs installed in the case than required.<br />
* Include a front view of the I/O panel naming each port. Esp. indicate which of the RJ-45 ports is connected to the BMC.<br />
* In the HSF INSTALLATION section, explicitly advise against thermal paste, since it's not required and complicates removal of the HSF (CPU may stick, then fall down angled and damage the socket).<br />
<br />
==RCS Schematics==<br />
<br />
===Errata===<br />
<br />
====Talos II specific====<br />
*CPUFAN0 and CPUFAN1 labels are swapped (according to awordnot in #talos-workstation)<br />
<br />
==Miscellaneous Improvements==<br />
* Use a different font on the BMC default password snippets that will make distinguishing the letters 1/l/I and O/0 ''possible at all'' (users regularly have trouble with reading them)<br />
* Indicate in the BMC hostname whether it's the host or the BMC, e.g. "blackbird-bmc" instead of "blackbird"<br />
* RCS could include 2 plastic mainboard standoffs [https://www.pccables.com/images/STANDOFFS-MOTHERBOARD-STANDARD-MB-PLASTIC-100-PACK.jpg like these] with the mainboard, since missing standoffs are ''very common'', as can be seen here: [[Talos II/Hardware Compatibility List#Problematic Cases]]. They are very cheap in bulk and should not add up much to the cost.<br />
* Provide high-res pictures of the Blackbird board, like for the Talos II: [[:File:Talos ii rev 1.00 top.png|Top]] and [[:File:Talos ii rev 1.00 bottom.png|Bottom]]<br />
* RCS should notify customers if the purchased products are not expected to be getting shipped (start of shipping) in a certain timeframe, e.g. 2 weeks.<br />
* RCS could provide customers with a regular (e.g. monthly) update on their order. (Due to long shipping delays and sometimes unresponsive support, some people were worried if their order will ship at all, and asked about it in the [[IRC| IRC channel]].<br />
* The default PWM duty cycle on the Blackbird is 25/255, which is roughly 10%. For many common consumer fans, this is not enough, many expect the duty cycle to be in the range 20% - 100%. See also [https://noctua.at/media/wysiwyg/Noctua_PWM_specifications_white_paper.pdf this Noctua whitepaper] and [https://www.glkinst.com/cables/cable_pics/4_Wire_PWM_Spec.pdf this 4 wire PWM Spec]. This might (?) also apply to the Talos 2. Tested on Blackbird System Package v1.00.<br />
<br />
=See also=<br />
* [[Desktop Roadmap]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Add_GPU_Firmware_To_BOOTKERNFW&diff=2774Add GPU Firmware To BOOTKERNFW2019-10-16T23:52:16Z<p>Mx08: add 'See also' section; add link to "Troubleshooting/GPU"</p>
<hr />
<div><br />
=Purpose=<br />
This guide explains how to add GPU (or other) firmware files to the BOOTKERNFW partition of the boot firmware flash.<br />
This allows Linux kernel drivers which require firmware blobs to function correctly within the Skiroot bootloader environment.<br />
<br />
For example, the <tt>amdgpu</tt> driver requires AMD firmware blobs to bring up AMD GPUs. Copying these files into the firmware partition enables attached displays to be brought up when showing the boot menu.<br />
<br />
=Background=<br />
Many cards require firmware to be loaded at startup time to initialize. On an X86 system, this is usually accomplished by bootstrap code called an "Option ROM", or by extra code in the BIOS.<br />
<br />
On OpenPOWER, this is not a possibility, due to the Option ROM code being platform-specific, as well as the OpenPOWER security stance being that trusting random bootstrap code on cards is a bad idea.<br />
<br />
Therefore, for things like video cards to work, it is necessary for the card's firmware to be loaded in before the card can be used. Linux video drivers in petitboot are capable of doing this loading, however, the actual firmware itself needs to be available so the drivers actually have something to load.<br />
<br />
So, on RCS OpenPOWER systems, there is a special area of flash set aside for user-provided firmware files, called BOOTKERNFW. Due to the limited size of this partition, the user is required to make decisions as to what firmware files to install.<br />
<br />
The exact size of BOOTKERNFW may vary depending on the firmware version you are on, but the standard size currently is 1,966,080 bytes (0x1E0000 hex, approximately 1.8MB.)<br />
<br />
=Applicability=<br />
All RCS OpenPOWER systems.<br />
<br />
=Instructions=<br />
<br />
==Step 1. Generate firmware partition image==<br />
Boot into an OS. A Linux environment is assumed. You will need the '''mksquashfs''' tool available.<br />
<br />
For Debian, you can install '''mksquashfs''' using the following command:<br />
$ apt install squashfs-tools<br />
<br />
Create a directory with the required firmware files available:<br />
$ mkdir /tmp/firmware<br />
$ # ... (copy required files into /tmp/firmware) ...<br />
<br />
The directory structure under <tt>/tmp/firmware</tt> gets mounted at <tt>/lib/firmware</tt>. Here is an example of the required directory structure:<br />
/tmp/firmware/radeon/PITCAIRN_pfp.bin<br />
/tmp/firmware/amdgpu/polaris10_mc.bin<br />
<br />
You can obtain these firmware files from most Linux distros (they tend to be installed in <tt>/lib/firmware</tt>), or from the [https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ linux-firmware repository].<br />
<br />
Having generated the correct directory structure, generate the image:<br />
$ cd /tmp/firmware<br />
$ mksquashfs * /tmp/firmware.bin -all-root -keep-as-directory<br />
<br />
<tt>firmware.bin</tt> is now a SquashFS image which you will copy to a firmware flash partition. You will need to access this image while in the [[Skiroot]] environment, so you may wish to copy it to e.g. <tt>/boot</tt> or another partition which you can easily access from [[Skiroot]].<br />
<br />
==Step 2. Copy firmware partition image to flash==<br />
<br />
=== Method 1: From Petitboot ===<br />
Reboot into the [[Skiroot]] environment, attaching a display using the onboard VGA or HDMI port if necessary. When the [[Petitboot]] bootloader appears, select &#8220;Exit to Shell&#8221;.<br />
<br />
Locate the firmware.bin file you prepared earlier. Petitboot mounts all filesystems it can recognize in folders under /var/petitboot/mnt/dev/, named after disk device partitions. In this example, we will assume that the file was at the path <tt>/var/petitboot/mnt/dev/nvme0n1p2/boot/firmware.bin</tt>.<br />
# ls /var/petitboot/mnt/dev/<br />
# ls /var/petitboot/mnt/dev/nvme0n1p2/boot/<br />
<br />
Use the <tt>pflash</tt> tool to flash the firmware.bin to the BOOTKERNFW partition. If you are on an old PNOR version that does not have pflash available, switch to following one of the other flashing methods.<br />
# pflash -P BOOTKERNFW -e -p /var/petitboot/mnt/dev/nvme0n1p2/boot/firmware.bin<br />
About to erase 0x03e10000..0x03ff0000 !<br />
WARNING ! This will modify your HOST flash chip content !<br />
Enter "yes" to confirm:<br />
<br />
The <tt>pflash</tt> tool will prompt you to confirm that you are about to modify your HOST flash chip content. Answer "yes" and press Enter.<br />
Erasing...<br />
[==================================================] 100% ETA:0s <br />
About to program "bootkern.img" at 0x03e10000..0x03ff0000 !<br />
Programming & Verifying...<br />
[==================================================] 100% ETA:0s <br />
Updating actual size in partition header...<br />
<br />
Reboot the system:<br />
# reboot<br />
<br />
When the system reboots, exit into the shell at the [[Petitboot]] menu again and check to see if the firmware made it as expected:<br />
# ls /lib/firmware/<br />
<br />
=== Method 2: From the BMC ===<br />
On your local machine, scp the firmware.bin to /tmp/ on the BMC.<br />
$ scp /tmp/firmware.bin root@bmc-ip-address:/tmp/firmware.bin<br />
<br />
Power off the host. (optional, but recommended)<br />
<br />
Log into the BMC on port 22.<br />
$ ssh root@bmc-ip-address<br />
<br />
Use the <tt>pflash</tt> tool to flash the firmware.bin to the BOOTKERNFW partition.<br />
# pflash -P BOOTKERNFW -e -p /tmp/firmware.bin<br />
About to erase 0x03e10000..0x03ff0000 !<br />
WARNING ! This will modify your HOST flash chip content !<br />
Enter "yes" to confirm:<br />
<br />
The <tt>pflash</tt> tool will prompt you to confirm that you are about to modify your HOST flash chip content. Answer "yes" and press Enter.<br />
Erasing...<br />
[==================================================] 100% ETA:0s <br />
About to program "bootkern.img" at 0x03e10000..0x03ff0000 !<br />
Programming & Verifying...<br />
[==================================================] 100% ETA:0s <br />
Updating actual size in partition header...<br />
<br />
Power the host back up.<br />
<br />
On the host, exit into the shell at the [[Petitboot]] menu again and check to see if the firmware made it as expected:<br />
# ls /lib/firmware/<br />
<br />
=== Method 3: Old Petitboot method, DANGEROUS ===<br />
WARNING: This method is error-prone and should only be done from the petitboot shell, NEVER on the BMC.<br />
<br />
Reboot into the [[Skiroot]] environment, attaching a display using the onboard VGA or HDMI port if necessary. When the [[Petitboot]] bootloader appears, select &#8220;Exit to Shell&#8221;.<br />
<br />
IMPORTANT: ACCIDENTALLY PERFORMING THESE INSTRUCTIONS ON THE BMC INSTEAD OF THE PETITBOOT CONSOLE MAY DAMAGE YOUR BMC FIRMWARE!<br />
<br />
Make sure you can see the <tt>BOOTKERNFW</tt> partition (should return: <tt>mtd5: 000e0000 00010000 "BOOTKERNFW"</tt>):<br />
# cat /proc/mtd | grep BOOTKERNFW<br />
<br />
Find the flash_erase (mine was in /var/petitboot/mnt/dev/nvme0n1p2/usr/sbin/):<br />
# find / -name flash_erase<br />
<br />
Erase <tt>/dev/mtd5</tt>:<br />
# /var/petitboot/mnt/dev/nvme0n1p2/usr/sbin/flash_erase /dev/mtd5 0 0<br />
<br />
Flash <tt>/dev/mtd5</tt>:<br />
# dd if=/var/petitboot/mnt/dev/nvme0n1p2/boot/firmware.bin of=/dev/mtd5 bs=64k<br />
<br />
Reboot the system:<br />
# reboot<br />
<br />
When the system reboots, exit into the shell at the [[Petitboot]] menu again and check to see if the firmware made it as expected:<br />
# ls /lib/firmware/<br />
<br />
==Notes==<br />
If you are still getting an error message about not being able to find VGA BIOS, it may be because your GPU is being initialized before <tt>/lib/firmware</tt> is mounted. <br />
You can check this by running <tt>dmesg</tt> from the [[Skiroot]] shell. For example, my GPU was trying to initialize at around T+6.5 seconds and the <tt>mtd</tt> device wasn't actually mounted until T+7.25.<br />
I was able to successfully load the firmware after after <tt>/dev/mtd5</tt> was mounted by running <tt>rmmod amdgpu && modprobe amdgpu</tt> from the shell. However, I did experience stability issues in Debian Stretch with <tt>amdgpu</tt>. However, if I let [[Skiroot]] fail to load the firmware and boot anyway, the <tt>radeon</tt> driver works fine.<br />
<br />
e.g.<br />
<pre><br />
$ dmesg<br />
...<br />
[ 6.412518] [drm] radeon kernel modesetting enabled.<br />
[ 6.412848] pci 0033:00:00.0: enabling device (0105 -> 0107)<br />
[ 6.412867] radeon 0033:01:00.0: enabling device (0140 -> 0142)<br />
[ 6.413077] [drm] initializing kernel modesetting (PITCAIRN 0x1002:0x6819 0x1043:0x0431 0x00).<br />
[ 6.413086] radeon: No suitable DMA available<br />
[ 6.413150] [drm:radeon_device_init] *ERROR* Unable to find PCI I/O BAR<br />
[ 6.533321] [drm:radeon_atombios_init] *ERROR* Unable to find PCI I/O BAR; using MMIO for ATOM IIO<br />
[ 6.533415] ATOM BIOS: 6819.15.17.0.0.AS01<br />
[ 6.533434] [drm] GPU not posted. posting now...<br />
[ 6.541203] radeon 0033:01:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)<br />
[ 6.541208] radeon 0033:01:00.0: GTT: 2048M 0x0000000080000000 - 0x00000000FFFFFFFF<br />
[ 6.541211] [drm] Detected VRAM RAM=2048M, BAR=256M<br />
[ 6.541213] [drm] RAM width 256bits DDR<br />
[ 6.541295] [TTM] Zone kernel: Available graphics memory: 50118240 kiB<br />
[ 6.541297] [TTM] Zone dma32: Available graphics memory: 2097152 kiB<br />
[ 6.541299] [TTM] Initializing pool allocator<br />
[ 6.541371] [drm] radeon: 2048M of VRAM memory ready<br />
[ 6.541374] [drm] radeon: 2048M of GTT memory ready.<br />
[ 6.541390] [drm] Loading pitcairn Microcode<br />
[ 6.541429] radeon 0033:01:00.0: Direct firmware load for radeon/pitcairn_pfp.bin failed with error -2<br />
[ 6.541456] radeon 0033:01:00.0: Direct firmware load for radeon/PITCAIRN_pfp.bin failed with error -2<br />
[ 6.541459] si_cp: Failed to load firmware "radeon/PITCAIRN_pfp.bin"<br />
[ 6.541560] [drm:si_init] *ERROR* Failed to load firmware!<br />
[ 6.541653] radeon 0033:01:00.0: Fatal error during GPU init<br />
[ 6.541772] [drm] radeon: finishing device.<br />
...<br />
[ 7.123614] 6 ofpart partitions found on MTD device flash<br />
[ 7.123617] Creating 6 MTD partitions on "flash":<br />
[ 7.123621] 0x000000000000-0x000004000000 : "PNOR"<br />
[ 7.123773] 0x000001b21000-0x000003a21000 : "BOOTKERNEL"<br />
[ 7.123868] 0x000003b44000-0x000003b68000 : "CAPP"<br />
[ 7.123961] 0x000003b88000-0x000003b89000 : "VERSION"<br />
[ 7.124056] 0x000003b89000-0x000003bc9000 : "IMA_CATALOG"<br />
[ 7.124149] 0x000003f10000-0x000003ff0000 : "BOOTKERNFW"<br />
...<br />
$ rmmod amdgpu && modprobe amdgpu<br />
$ dmesg<br />
...<br />
[ 2727.836343] [drm] amdgpu kernel modesetting enabled.<br />
[ 2727.836900] amdgpu 0033:01:00.0: SI support provided by radeon.<br />
[ 2727.836905] amdgpu 0033:01:00.0: Use radeon.si_support=0 amdgpu.si_support=1 to override.<br />
</pre><br />
<br />
==Backing up BOOTKERNFW==<br />
If you are using one of the prebuilt workstations that came with a GPU card preinstalled, you may wish to backup your BOOTKERNFW so you have a known-good version to go back to, as they come with the firmware preloaded into BOOTKERNFW and removing it may cause graphical display to stop working until you reload appropriate firmware into BOOTKERNFW.<br />
<br />
This backup can be taken from either the BMC or the Petitboot shell. The procedure is the same on either.<br />
# cd /tmp<br />
# pflash -P BOOTKERNFW -r BOOTKERNFW.bin<br />
<br />
From another machine, copy the backup to a permanent location.<br />
$ scp root@bmc-ip-address:/tmp/BOOTKERNFW.bin .<br />
<br />
==Erasing BOOTKERNFW==<br />
If you change your mind and decide to stop using BOOTKERNFW, you can erase it from either the BMC or the Petitboot shell. The procedure is the same on either.<br />
# pflash -P BOOTKERNFW -e<br />
About to erase 0x03e10000..0x03ff0000 !<br />
WARNING ! This will modify your HOST flash chip content !<br />
Enter "yes" to confirm:<br />
<br />
The <tt>pflash</tt> tool will prompt you to confirm that you are about to modify your HOST flash chip content. Answer "yes" and press Enter.<br />
Erasing...<br />
[==================================================] 100% ETA:0s <br />
Updating actual size in partition header...<br />
<br />
At this point you are back to an empty BOOTKERNFW partition.<br />
<br />
[[Category:Guides]]<br />
<br />
=See also=<br />
* [[Troubleshooting/GPU]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Troubleshooting/GPU&diff=2773Troubleshooting/GPU2019-10-16T23:50:52Z<p>Mx08: add 'See also' section; add link to "Add GPU Firmware To BOOTKERNFW"</p>
<hr />
<div>[[Category:Troubleshooting]]<br />
<br />
== Background ==<br />
<br />
Because OpenPOWER systems do not have a legacy graphics interface to fall back to, and as a result rely heavily on the running operating system and its drivers to handle display tasks, a few rough edges are exposed. This page attempts to document the current status of these rough edges and suggested workarounds pending actual fixes.<br />
<br />
== Common Issues ==<br />
<br />
=== Bootloader does not show up on monitor(s) attached to a discrete GPU ===<br />
<br />
Most modern discrete GPUs require firmware. As Talos™ II is aimed at a security-conscious audience, we do not currently include GPU firmware in the production firmware images. Instructions are available in the [[:File:T2P9D01 users guide version 1 0.pdf|Users Guide]] to add firmware for your GPU to the PNOR if needed. Note that any added firmware may be able to access and modify data associated with the affected device(s); we strongly recommend you perform a security risk analysis before loading any firmware, and select open firmware where/if it is available.<br />
<br />
If you are using a GPU that does not require firmware, or have already added any needed firmware files to the host PNOR, please ensure that the on-board VGA disable jumper (J10109) is capped. The bootloader output will preferentially show up on the on-board VGA port if it remains enabled.<br />
<br />
Alternatively, you either use a serial console or VGA monitor / adapter to interact with the bootloader.<br />
<br />
=== My AMD GPU works in petitboot but not the subsequent Linux OS ===<br />
<br />
Older versions of the amdgpu driver (Linux 4.15 and below) have a bug where the connected outputs will not re-initialize after a kexec() while the driver is loaded. Kernel 4.16 and above does not appear to have this problem.<br />
<br />
If you need to use kernel 4.15 or below, you can work around this issue by either:<br />
* Enabling and using the VGA video output to access the bootloader (petitboot) -or-<br />
* using a serial connection to control petitboot, and running the following commands prior to selecting an operating system via the petitboot menu:<br />
<nowiki>echo 0 > /sys/class/vtconsole/vtcon1/bind<br />
rmmod amdgpu</nowiki><br />
<br />
=== I want Petitboot via AST but the subsequent Linux OS console on a discrete GPU ===<br />
<br />
If you don't want to put GPU firmware in the PNOR but still want Linux tty on the discrete graphics, you'll find that you'll always get output on the AST first no matter what. Blacklisting the <code>ast</code> module from loading is not sufficient on its own, you will need two kernel boot arguments:<br />
<br />
<nowiki>modprobe.blacklist=ast video=offb:off</nowiki><br />
<br />
For example on Ubuntu, this can be accomplished by changing <code>GRUB_CMDLINE_LINUX</code> in <code>/etc/default/grub</code> accordingly, like<br />
<br />
<nowiki>GRUB_CMDLINE_LINUX="modprobe.blacklist=ast video=offb:off"</nowiki><br />
<br />
and then running <code>update-grub</code>.<br />
<br />
=== Xorg will not start / crashes when a discrete GPU is installed ===<br />
<br />
Installing more than one GPU into an OpenPOWER system (for instance, when adding a discrete GPU) exposes all GPUs directly to the operating system -- there is no concept of a "primary" GPU like there is on x86. Xorg does not handle this gracefully, tending to crash during autoconfiguration. [https://bugs.freedesktop.org/show_bug.cgi?id=94166 At least one bug report has been filed] but fixing the root cause of this issue (incorrect Xorg drivers binding to underlying DRM devices) does not seem to be an Xorg priority. Furthermore, Xorg does not properly handle domains during autoconfiguration per [https://bugs.freedesktop.org/show_bug.cgi?id=98524#c2 another bug report on a similar issue]. Community effort in getting proper fixes into Xorg would be very useful, as the Xorg developers may want to see that more than one or two systems are impacted by these bugs before working on resolving them.<br />
<br />
Two workarounds are available:<br />
<br />
==== Workaround 1: Disable on-board VGA====<br />
Disable the on-board VGA output via the VGA disable jumper, J10109. See the [[:File:T2P9D01 users guide version 1 0.pdf|Users Guide]] for additional information.<br />
<br />
==== Workaround 2: Select desired GPU at runtime ====<br />
<br />
The workaround to keep both devices active, or to retain the ability to switch in the active operating system, is fairly simple, and consists of explicitly assigning Xorg drivers for each installed GPU. For this example we'll show how to fix Xorg on Debian with an AMD WX7100 discrete GPU installed.<br />
<br />
===== Step 1: Locate Bus Numbers =====<br />
<nowiki>root@talos:~# lspci | grep VGA<br />
0000:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100]<br />
0005:02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41)</nowiki><br />
<br />
Note the numbers to the left of the "VGA compatible controller" string. Each of these numbers is the PCI d:B:D.F<ref group="note">PCI Domain:Bus:Device.Function</ref> number of the GPU, and is unique to the slot(s) you have your GPU(s) installed in. As a result of this slot dependence, bus IDs may differ from those shown in this example; always use your bus IDs when following the steps below. This slot dependence means that if you move your GPU to a different slot you will need to update the bus ID associated with that GPU.<br />
<br />
===== Step 2: Create Xorg Configuration Snippet =====<br />
<nowiki>root@talos:~# mkdir /etc/X11/xorg.conf.d</nowiki><br />
<br />
Create and open <code>/etc/X11/xorg.conf.d/21-gpu-driver.conf</code> for editing, then adjust the following template with your GPU information. Pay close attention to the BusID and Driver fields, as they must match your installed GPU(s). Note that Xorg uses decimal numbering, not hexadecimal like <code>lspci</code>, so you will need to convert the numbers within the colons of the lspci output to decimal in order to constrict a valid Xorg BusID. Furthermore, xorg doesn't use leading zeroes like <code>lspci</code> does; these must be stripped off when assembling the Xorg BusID. Finally, Xorg expects to see a BusID assembled as "PCI:B@d:D:F" (note Bus and Domain are swapped), and should not be assembled not using the format shown by <code>lspci</code>.<br />
<br />
<nowiki># AST2500<br />
Section "Device"<br />
Identifier "GPU0"<br />
Driver "modesetting"<br />
BusID "PCI:2@5:0:0"<br />
VendorName "ASpeed Corporation"<br />
EndSection<br />
<br />
# WX7100<br />
Section "Device"<br />
Identifier "GPU1"<br />
Driver "modesetting" # or amdgpu if you have xf86-video-amdgpu installed<br />
BusID "PCI:1@0:0:0"<br />
VendorName "AMD Corporation"<br />
EndSection<br />
<br />
# this is absolutely necessary, it tells xorg which GPU to use for the screen<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "GPU1"<br />
EndSection</nowiki><br />
<br />
Save and exit the configuration snippet file, then restart Xorg. Your GPUs should now function as intended. If Xorg still does not start, make sure that the appropriate kernel driver (such as <code>amdgpu</code> for the example above, keep in mind that the Xorg driver and the kernel driver are separate and distinct) has been loaded:<br />
<br />
<nowiki>root@talos:~# modprobe amdgpu</nowiki><br />
<br />
You can use the generic modesetting Xorg driver for AMD GPUs, or you can use amdgpu from xf86-video-amdgpu. The generic modesetting driver has been reported to work perfectly fine on a Talos with various GPUs, so there is likely no practical reason to use the driver-specific DDX.<br />
<br />
===== Step 3 (optional): Disable Integrated Video =====<br />
<br />
To disable the ASpeed VGA in the booted OS completely, you can use the <code>modprobe.blacklist=ast</code> approach on kernel command line, refer to the "I want Petitboot via AST but the subsequent Linux OS console on a discrete GPU" section above for more information. This method is universal/works on all distributions. The ASpeed VGA will still show up in <code>lspci</code> afterwards, which is normal, as you haven't disabled the hardware, just the driver.<br />
<br />
With this done, it should be possible to remove the device section in the X.Org configuration file for the onboard VGA, but you can also just leave it there if you want, regardless of whether the driver is loaded or not.<br />
<br />
There are alternative ways to blacklist the <code>ast</code> kernel driver. For example on Debian based systems, create a new file <code>/etc/modprobe.d/ast-blacklist.conf</code> and place the following line inside the new file:<br />
<br />
<nowiki>blacklist ast</nowiki><br />
<br />
You may need to reboot if the <code>ast</code> DRM driver has already loaded. Alternatively, you may try to unbind and unload the <code>ast</code> driver as follows (assuming the <code>ast</code> driver is bound to vtcon0):<br />
<br />
<nowiki>root@talos:~# echo 0 > /sys/class/vtconsole/vtcon0/bind<br />
root@talos:~# rmmod ast</nowiki><br />
<br />
=== Monitor not detected in kernel 4.17+ ===<br />
Petitboot shows up fine, but there is no output for the host OS. It has been reported as [https://bugs.freedesktop.org/show_bug.cgi?id=107049 bug 107049], the workaround is to append <code>amdgpu.dc=0</code> to the kernel parameters. This is often associated with a host dmesg trace of<br />
<nowiki>[drm] Cannot find any crtc or sizes</nowiki><br />
<br />
EDIT 2019-05-02: Seems the <code>dc=0</code> workaround is not required any more, tested with 5.1-rc7<br />
<br />
=== Xorg crashes or is laggy with the AST VGA GPU ===<br />
<br />
Xorg seems to enable GLAMOR by default on many operating systems (such as Debian Buster). GLAMOR is a translation layer that converts 2D graphics operations to 3D graphics operations. This makes sense when 3D GPU acceleration is available, but when using a simple unaccelerated 2D GPU like the AST VGA GPU, the result is that 2D operations get converted to 3D operations by GLAMOR and are then converted back to 2D by llvmpipe, which introduces significant overhead.<br />
<br />
In addition, on Debian Buster, GLAMOR has been observed to crash when used in conjunction with llvmpipe.<br />
<br />
You can disable GLAMOR by saving the following text file as <code>/usr/share/X11/xorg.conf.d/00-noglamoregl.conf</code>:<br />
<br />
Section "Device"<br />
Identifier "nogpu"<br />
Driver "modesetting"<br />
Option "Accelmethod" "none"<br />
EndSection<br />
<br />
Section "Module"<br />
Disable "glamoregl"<br />
EndSection<br />
<br />
This bug was probably fixed by [https://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.20-branch&id=1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4 commit 1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4] in upstream Xorg; it is unknown how quickly the fix will make its way to GNU/Linux distributions.<br />
<br />
=== KDE is laggy with the AST VGA GPU ===<br />
<br />
KDE's default compositor uses OpenGL. This makes sense when 3D GPU acceleration is available, but when using a simple unaccelerated 2D GPU like the AST VGA GPU, the result is that 2D operations get converted to 3D operations by KDE's compositor and are then converted back to 2D by llvmpipe, which introduces significant overhead.<br />
<br />
To fix this, go to <code>System Settings</code> → <code>Hardware</code> → <code>Display and Monitor</code> → <code>Compositor</code>, and select <code>XRender</code> as the <code>Rendering backend</code>. You'll probably also want to select <code>Smooth (slower)</code> as the <code>Scale method</code> (it's still much faster than OpenGL, and it looks quite a bit better).<br />
<br />
=== Display stuck at default low resolution with AST HDMI GPU ===<br />
<br />
As of 05/24/2019 upstream Linux kernels do not have driver support for the [[IT66121FN|IT66121FN HDMI transceiver]]. This is being actively worked by Raptor Computing Systems and the larger ppc64el community. Until support is added, you will need to force the correct resolution in Xorg. The general process for discovering bus IDs etc. is detailed above in the AMD GPU section; you will need to extend the result with custom modelines as shown below:<br />
<br />
<nowiki># AST2500<br />
Section "Device"<br />
Identifier "GPU0"<br />
Driver "modesetting"<br />
BusID "PCI:2@5:0:0"<br />
VendorName "ASpeed Corporation"<br />
EndSection<br />
<br />
# configure as appropriate for your monitor -- a standard 1080p screen is assumed below<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
HorizSync 30.0-70.0<br />
VertRefresh 50.0-70.0<br />
Modeline "1920x1080" 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync<br />
EndSection<br />
<br />
# this is absolutely necessary, it tells xorg which GPU to use for the screen<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Monitor "Monitor0"<br />
Device "GPU0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Depth 24<br />
Modes "1920x1080"<br />
EndSubSection<br />
EndSection</nowiki><br />
<br />
=== AMDGPU driver crashes after firmware update ===<br />
The GPU only allows loading one firmware after an ASIC reset, so the firmware used by the skiroot kernel and the host kernel must be the same. See FreeDesktop.org bug [https://bugs.freedesktop.org/show_bug.cgi?id=108585 108585] for more details.<br />
<br />
Note: This is theoretically fixed in kernel 5.1, see [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd/amdgpu/amdgpu.h?h=linux-5.1.y&id=444018893abfde1df86be9d4be3e0c84832397dd this commit]. Needs confirmation.<br />
<br />
== Notes ==<br />
<br />
<references group="note"/><br />
[[Category:Guides]]<br />
<br />
== See also ==<br />
* [[Add GPU Firmware To BOOTKERNFW]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Blackbird/Hardware_Compatibility_List&diff=2772Blackbird/Hardware Compatibility List2019-10-16T15:59:40Z<p>Mx08: /* PCIe Devices */</p>
<hr />
<div>== Cases ==<br />
<br />
== Power Supplies ==<br />
<br />
== Fans ==<br />
* As of BMC firmware branch "04-16-2019", Noctua Industrial 140mm (NF-A14 iPPC-2000) do not work correctly. However, normal Noctua 140mm (NF-A14 PWM) work as expected even using a splitter for 4 total fans.<br />
<br />
== Memory ==<br />
See [[POWER9 Hardware Compatibility List/Memory]].<br />
<br />
== PCIe Devices ==<br />
See [[POWER9 Hardware Compatibility List/PCIe Devices]].<br />
<br />
'''NOTE:'''<br />
On the Blackbird, pin 1 of the "BMC TTL AUXILIARY SERIAL HEADER" (J10116) conflicts with some PCIe cards (or their metal mounting bracket) in the lower PCIe 4.0 x8 slot. This is the case for e.g. the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P], where the metal bracket touches pin 1 of J10116 such that either the pin gets bent or the card does not fully seat. Since the conflicting distance is less than 1mm, either the metal bracket or the PCB (depending on which one touches the pin) can be filed/ground a tiny bit (with a hand file or dremel), so that the cards fully seats without bending the pin. When doing so, care must be taken to not let any metal dust touch the PCIe card. Ideally the conflict would only be between the metal bracket and the pin, in which case the metal bracket can be unscrewed from the card and modified separately. Afterwards it should be properly cleaned and (if necessary) dried, before being remounted to the card.<br />
<br />
Here are some pictures from [[user:mx08|mx08]]'s modification to the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P]'s metal bracket:<br />
<gallery><br />
File:J10116_BMC-TTL_conflict.jpg|thumb|baseline|center|Conflict (card not fully seated)<br />
File:AOC-SHG3-4M2P_bracket_removed.jpg|thumb|baseline|center|Metal bracket removed<br />
File:AOC-SHG3-4M2P_bracket_modified.jpg|thumb|baseline|center|Metal bracket modified<br />
File:AOC-SHG3-4M2P_bracket_modified_mounted.jpg|thumb|baseline|center|Metal bracket re-mounted<br />
File:J10116_BMC-TTL_conflict_resolved.jpg|thumb|baseline|center|Conflict resolved<br />
</gallery><br />
<br />
An alternative would maybe be to place a 1mm spacer between the top end of the PCIe card's metal bracket and the case, so that the card can be tightened properly while still making firm contact (?) with the PCIe slot.<br />
<br />
== SATA Storage Drives ==<br />
Connected via optional on-board [[88SE9235|88SE9235]] controller, or via PCIe controller. NVMe cards are also supported. <br />
<br />
== See also ==<br />
* [[Talos II/Hardware Compatibility List|Talos II/Hardware Compatibility List]]<br />
<br />
[[Category:Compatibility List]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=Blackbird/Hardware_Compatibility_List&diff=2771Blackbird/Hardware Compatibility List2019-10-16T04:23:29Z<p>Mx08: /* PCIe Devices */ add pictures on conflict note (J10116 pin1 and PCIe x8 card)</p>
<hr />
<div>== Cases ==<br />
<br />
== Power Supplies ==<br />
<br />
== Fans ==<br />
* As of BMC firmware branch "04-16-2019", Noctua Industrial 140mm (NF-A14 iPPC-2000) do not work correctly. However, normal Noctua 140mm (NF-A14 PWM) work as expected even using a splitter for 4 total fans.<br />
<br />
== Memory ==<br />
See [[POWER9 Hardware Compatibility List/Memory]].<br />
<br />
== PCIe Devices ==<br />
See [[POWER9 Hardware Compatibility List/PCIe Devices]].<br />
<br />
'''NOTE:'''<br />
On the Blackbird, pin 1 of the "BMC TTL AUXILIARY SERIAL HEADER" (J10116) conflicts with some PCIe cards (or their metal mounting bracket) in the lower PCIe 4.0 x8 slot. This is the case for e.g. the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P], where the metal bracket touches pin 1 of J10116 such that either the pin gets bent or the card does not fully seat. Since the conflicting distance is less than 1mm, either the metal bracket or the PCB (depending on which one touches the pin) can be filed/ground a tiny bit (with a hand file or dremel), so that the cards fully seats without bending the pin. When doing so, care must be taken to not let any metal dust touch the PCIe card. Ideally the conflict would only be between the metal bracket and the pin, in which case the metal bracket can be unscrewed from the card and modified separately. Afterwards it should be properly cleaned and (if necessary) dried, before being remounted to the card.<br />
<br />
Here are some pictures from [[user:mx08|mx08]]'s modification to the [https://www.supermicro.com/en/products/accessories/addon/AOC-SHG3-4M2P.php Supermicro AOC-SHG3-4M2P]'s metal bracket:<br />
<gallery><br />
File:J10116_BMC-TTL_conflict.jpg|thumb|baseline|center|Conflict<br />
File:AOC-SHG3-4M2P_bracket_removed.jpg|thumb|baseline|center|Metal bracket removed<br />
File:AOC-SHG3-4M2P_bracket_modified.jpg|thumb|baseline|center|Metal bracket modified<br />
File:AOC-SHG3-4M2P_bracket_modified_mounted.jpg|thumb|baseline|center|Metal bracket re-mounted<br />
File:J10116_BMC-TTL_conflict_resolved.jpg|thumb|baseline|center|Conflict resolved<br />
</gallery><br />
<br />
An alternative would maybe be to place a 1mm spacer between the top end of the PCIe card's metal bracket and the case, so that the card can be tightened properly while still making firm contact (?) with the PCIe slot.<br />
<br />
== SATA Storage Drives ==<br />
Connected via optional on-board [[88SE9235|88SE9235]] controller, or via PCIe controller. NVMe cards are also supported. <br />
<br />
== See also ==<br />
* [[Talos II/Hardware Compatibility List|Talos II/Hardware Compatibility List]]<br />
<br />
[[Category:Compatibility List]]</div>Mx08https://wiki.raptorcs.com/w/index.php?title=File:J10116_BMC-TTL_conflict_resolved.jpg&diff=2770File:J10116 BMC-TTL conflict resolved.jpg2019-10-16T04:19:13Z<p>Mx08: </p>
<hr />
<div></div>Mx08https://wiki.raptorcs.com/w/index.php?title=File:J10116_BMC-TTL_conflict.jpg&diff=2769File:J10116 BMC-TTL conflict.jpg2019-10-16T04:17:22Z<p>Mx08: </p>
<hr />
<div></div>Mx08https://wiki.raptorcs.com/w/index.php?title=File:AOC-SHG3-4M2P_bracket_removed.jpg&diff=2768File:AOC-SHG3-4M2P bracket removed.jpg2019-10-16T04:16:56Z<p>Mx08: </p>
<hr />
<div></div>Mx08