<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.raptorcs.com/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Q66</id>
	<title>RCS Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.raptorcs.com/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Q66"/>
	<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/wiki/Special:Contributions/Q66"/>
	<updated>2026-04-26T07:32:52Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.33.1</generator>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=2734</id>
		<title>Operating System Compatibility List</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=2734"/>
		<updated>2019-09-19T23:29:34Z</updated>

		<summary type="html">&lt;p&gt;Q66: void url update&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Not everything is bug-free, so you might want to the check also [[Fixes in Progress]] about the state of their upstreaming.&lt;br /&gt;
== GNU/Linux ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.adelielinux.org/ Adélie]&lt;br /&gt;
|1.0-beta1&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Needs the easy-kernel-power8 package instead of easy-kernel.  KDE 5 is stable.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;4&amp;quot;|[https://cdimage.debian.org/cdimage/ Debian]&lt;br /&gt;
|10 (2018-05-28 weekly DVD ISO)&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Only tested in KVM-PV.  Using Adélie easy-kernel as kernel, Debian Buster userland.&lt;br /&gt;
|-&lt;br /&gt;
|9.5.0&lt;br /&gt;
|ppc64le (inside KVM; machine type = pseries)&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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 &amp;lt;code&amp;gt;dpkg-query -W -f='${Section}\t${Package}\n' &amp;amp;#124; grep ^contrib&amp;lt;/code&amp;gt; (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.&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|[https://alt.fedoraproject.org/alt/ Fedora]&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|28&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|ppc64le&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|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&lt;br /&gt;
|-&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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]&lt;br /&gt;
|-&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|discontinued in Fedora 29&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://wiki.gentoo.org/wiki/Handbook:PPC64 Gentoo]&lt;br /&gt;
| n/a&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:Luke-jr|luke-jr]]&lt;br /&gt;
|Once installed, works fine.&lt;br /&gt;
|-&lt;br /&gt;
|17.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:MarcusC|MarcusC]]&lt;br /&gt;
|XFCE4 and virt-manager verified&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.opensuse.org/ openSUSE]&lt;br /&gt;
|Tumbleweed 20190805&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:Jonsger|Jonsger]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.ubuntu.com/download/server/power Ubuntu]&lt;br /&gt;
|18.10&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:q66|q66]]&lt;br /&gt;
|Installs and works out of box with no changes, Xfce4.&lt;br /&gt;
|-&lt;br /&gt;
|[https://voidlinux-ppc.org Void Linux for Power Architecture]&lt;br /&gt;
|n/a&lt;br /&gt;
|ppc64le/ppc64/ppc&lt;br /&gt;
|[[User:q66|q66]]&lt;br /&gt;
|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)&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|[http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ Whonix] ([https://www.whonix.org/ clearnet link])&lt;br /&gt;
|15&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|14&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.)&lt;br /&gt;
|-&lt;br /&gt;
|14&lt;br /&gt;
|amd64&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== BSDs ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://www.freebsd.org/ FreeBSD]&lt;br /&gt;
|12.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Contains initial POWER9 support&lt;br /&gt;
|-&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Ongoing development activity, better than releases for the time being&lt;br /&gt;
|-&lt;br /&gt;
|[https://github.com/POWER9BSD/ POWER9BSD]&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Advance POWER9 features for FreeBSD like Radix MMU, amdgpu etc&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Ports in progress===&lt;br /&gt;
Rapid progress is being made on these ports by members of the community.&lt;br /&gt;
&lt;br /&gt;
* NixOS&lt;br /&gt;
* GuixSD ([[User:Isengaara|Isengaara]])&lt;br /&gt;
&lt;br /&gt;
== External Links ==&lt;br /&gt;
&lt;br /&gt;
* [http://bgafc.t-hosting.hu/oses4ppc.php Operating Systems for PowerPC] PPC32be / PPC64be / PPC64le&lt;br /&gt;
&lt;br /&gt;
[[Category:Compatibility List]]&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=2467</id>
		<title>Operating System Compatibility List</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=2467"/>
		<updated>2019-05-19T16:23:23Z</updated>

		<summary type="html">&lt;p&gt;Q66: update void info&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Not everything is bug-free, so you might want to the check also [[Fixes in Progress]] about the state of their upstreaming.&lt;br /&gt;
== GNU/Linux ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.adelielinux.org/ Adélie]&lt;br /&gt;
|1.0-beta1&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Needs the easy-kernel-power8 package instead of easy-kernel.  KDE 5 is stable.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;4&amp;quot;|[https://cdimage.debian.org/cdimage/ Debian]&lt;br /&gt;
|10 (2018-05-28 weekly DVD ISO)&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Only tested in KVM-PV.  Using Adélie easy-kernel as kernel, Debian Buster userland.&lt;br /&gt;
|-&lt;br /&gt;
|9.5.0&lt;br /&gt;
|ppc64le (inside KVM; machine type = pseries)&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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 &amp;lt;code&amp;gt;dpkg-query -W -f='${Section}\t${Package}\n' &amp;amp;#124; grep ^contrib&amp;lt;/code&amp;gt; (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.&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|[https://alt.fedoraproject.org/alt/ Fedora]&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|28&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|ppc64le&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|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&lt;br /&gt;
|-&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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]&lt;br /&gt;
|-&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|discontinued in Fedora 29&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://wiki.gentoo.org/wiki/Handbook:PPC64 Gentoo]&lt;br /&gt;
| n/a&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:Luke-jr|luke-jr]]&lt;br /&gt;
|Once installed, works fine.&lt;br /&gt;
|-&lt;br /&gt;
|17.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:MarcusC|MarcusC]]&lt;br /&gt;
|XFCE4 and virt-manager verified&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|[http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ Whonix] ([https://www.whonix.org/ clearnet link])&lt;br /&gt;
|15&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|14&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.)&lt;br /&gt;
|-&lt;br /&gt;
|14&lt;br /&gt;
|amd64&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.ubuntu.com/download/server/power Ubuntu]&lt;br /&gt;
|18.10&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:q66|q66]]&lt;br /&gt;
|Installs and works out of box with no changes, Xfce4.&lt;br /&gt;
|-&lt;br /&gt;
|[https://void-power.octaforge.org Void Linux for Power Architecture]&lt;br /&gt;
|n/a&lt;br /&gt;
|ppc64le/ppc64/ppc&lt;br /&gt;
|[[User:q66|q66]]&lt;br /&gt;
|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)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== BSDs ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://www.freebsd.org/ FreeBSD]&lt;br /&gt;
|12.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Contains initial POWER9 support&lt;br /&gt;
|-&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Ongoing development activity, better than releases for the time being&lt;br /&gt;
|-&lt;br /&gt;
|[https://github.com/POWER9BSD/ POWER9BSD]&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Advance POWER9 features for FreeBSD like Radix MMU, amdgpu etc&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Ports in progress===&lt;br /&gt;
Rapid progress is being made on these ports by members of the community.&lt;br /&gt;
&lt;br /&gt;
* NixOS&lt;br /&gt;
* GuixSD ([[User:Isengaara|Isengaara]])&lt;br /&gt;
&lt;br /&gt;
[[Category:Compatibility List]]&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=User:Q66/Build&amp;diff=2404</id>
		<title>User:Q66/Build</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=User:Q66/Build&amp;diff=2404"/>
		<updated>2019-04-30T01:47:10Z</updated>

		<summary type="html">&lt;p&gt;Q66: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Main desktop system:'''&lt;br /&gt;
&lt;br /&gt;
* Tyan TN71-BP012 POWER8 Turismo 10-core&lt;br /&gt;
* 128GB (16x8GB) Hynix DDR3L-1333 reg ECC RAM&lt;br /&gt;
* AMD Radeon Pro WX 5100&lt;br /&gt;
* Samsung 860 EVO SATAIII 250GB / + Samsung 970 Pro NVMe 512GB /home&lt;br /&gt;
* Custom AIO watercooling + IKEA LackRack mount&lt;br /&gt;
&lt;br /&gt;
'''Peripherals:'''&lt;br /&gt;
&lt;br /&gt;
* 3x LG 27UD69P-W 27&amp;quot; 4K UHD displays&lt;br /&gt;
* JDS Labs ODAC revB USB audio&lt;br /&gt;
* NAD D3020 amplifier&lt;br /&gt;
* Audio-Technica ATH-R70x headphones&lt;br /&gt;
* Model M keyboard&lt;br /&gt;
* 3DConnexion CadMouse&lt;br /&gt;
&lt;br /&gt;
'''Server system:'''&lt;br /&gt;
&lt;br /&gt;
* Talos 2 Lite&lt;br /&gt;
* 1x 18-core IBM POWER9&lt;br /&gt;
* 128GB (4x32GB) Samsung DDR4-2666 reg ECC RAM&lt;br /&gt;
* 1x 250GB WD Blue SSD + 2x 1TB WD Blue SSD&lt;br /&gt;
* LSI SAS2308-IT storage HBA&lt;br /&gt;
* Mellanox ConnectX EN 10GbE SFP+ NIC&lt;br /&gt;
* EVGA Supernova G2 750W 80+Gold PSU&lt;br /&gt;
* Nanoxia Deep Silence 2 case&lt;br /&gt;
* [[Dual_92mm_fan_CPU|Dual 92mm fan HSF mod]]&lt;br /&gt;
&lt;br /&gt;
'''Software:'''&lt;br /&gt;
&lt;br /&gt;
Void Linux (void-ppc64) ppc64le on both systems. Testing VMs/chroots for Void Linux ppc64, ppc64-musl, ppc64le-musl.&lt;br /&gt;
&lt;br /&gt;
[[Category:User Systems]]&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=User:Q66/Build&amp;diff=2403</id>
		<title>User:Q66/Build</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=User:Q66/Build&amp;diff=2403"/>
		<updated>2019-04-30T01:46:05Z</updated>

		<summary type="html">&lt;p&gt;Q66: Created page with &amp;quot;'''Main desktop system:'''  * Tyan TN71-BP012 POWER8 Turismo 10-core * 128GB (16x8GB) Hynix DDR3L-1333 reg ECC RAM * AMD Radeon Pro WX 5100 * Samsung 860 EVO SATAIII 250GB / +...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Main desktop system:'''&lt;br /&gt;
&lt;br /&gt;
* Tyan TN71-BP012 POWER8 Turismo 10-core&lt;br /&gt;
* 128GB (16x8GB) Hynix DDR3L-1333 reg ECC RAM&lt;br /&gt;
* AMD Radeon Pro WX 5100&lt;br /&gt;
* Samsung 860 EVO SATAIII 250GB / + Samsung 970 Pro NVMe 512GB /home&lt;br /&gt;
* Custom AIO watercooling + IKEA LackRack mount&lt;br /&gt;
&lt;br /&gt;
'''Peripherals:'''&lt;br /&gt;
&lt;br /&gt;
* 3x LG 27UD69P-W 27&amp;quot; 4K UHD displays&lt;br /&gt;
* JDS Labs ODAC revB USB audio&lt;br /&gt;
* NAD D3020 amplifier&lt;br /&gt;
* Audio-Technica ATH-R70x headphones&lt;br /&gt;
* Model M keyboard&lt;br /&gt;
* 3DConnexion CadMouse&lt;br /&gt;
&lt;br /&gt;
'''Server system:'''&lt;br /&gt;
&lt;br /&gt;
* Talos 2 Lite&lt;br /&gt;
* 1x 18-core IBM POWER9&lt;br /&gt;
* 128GB (4x32GB) Samsung DDR4-2666 reg ECC RAM&lt;br /&gt;
* 1x 250GB WD Blue SSD + 2x 1TB WD Blue SSD&lt;br /&gt;
* LSI SAS2308-IT storage HBA&lt;br /&gt;
* Mellanox ConnectX EN 10GbE SFP+ NIC&lt;br /&gt;
* EVGA Supernova G2 750W 80+Gold PSU&lt;br /&gt;
* Nanoxia Deep Silence 2 case&lt;br /&gt;
* [[Dual_92mm_fan_CPU|Dual 92mm fan HSF mod]]&lt;br /&gt;
&lt;br /&gt;
'''Software:'''&lt;br /&gt;
&lt;br /&gt;
Void Linux (void-ppc64) ppc64le on both systems. Testing VMs/chroots for Void Linux ppc64, ppc64-musl, ppc64le-musl.&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=2400</id>
		<title>Operating System Compatibility List</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=2400"/>
		<updated>2019-04-28T23:25:22Z</updated>

		<summary type="html">&lt;p&gt;Q66: update targets&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Not everything is bug-free, so you might want to the check also [[Fixes in Progress]] about the state of their upstreaming.&lt;br /&gt;
== GNU/Linux ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.adelielinux.org/ Adélie]&lt;br /&gt;
|1.0-beta1&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Needs the easy-kernel-power8 package instead of easy-kernel.  KDE 5 is stable.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;4&amp;quot;|[https://cdimage.debian.org/cdimage/ Debian]&lt;br /&gt;
|10 (2018-05-28 weekly DVD ISO)&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Only tested in KVM-PV.  Using Adélie easy-kernel as kernel, Debian Buster userland.&lt;br /&gt;
|-&lt;br /&gt;
|9.5.0&lt;br /&gt;
|ppc64le (inside KVM; machine type = pseries)&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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 &amp;lt;code&amp;gt;dpkg-query -W -f='${Section}\t${Package}\n' &amp;amp;#124; grep ^contrib&amp;lt;/code&amp;gt; (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.&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|[https://alt.fedoraproject.org/alt/ Fedora]&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|28&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|ppc64le&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|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&lt;br /&gt;
|-&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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]&lt;br /&gt;
|-&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|discontinued in Fedora 29&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://wiki.gentoo.org/wiki/Handbook:PPC64 Gentoo]&lt;br /&gt;
| n/a&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:Luke-jr|luke-jr]]&lt;br /&gt;
|Once installed, works fine.&lt;br /&gt;
|-&lt;br /&gt;
|17.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:MarcusC|MarcusC]]&lt;br /&gt;
|XFCE4 and virt-manager verified&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ Whonix] ([https://www.whonix.org/ clearnet link])&lt;br /&gt;
|14&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|Appears to work fine when the [[Whonix]] instructions are followed; host OS used for testing was Debian 10.&lt;br /&gt;
|-&lt;br /&gt;
|14&lt;br /&gt;
|amd64&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.ubuntu.com/download/server/power Ubuntu]&lt;br /&gt;
|18.10&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:q66|q66]]&lt;br /&gt;
|Installs and works out of box with no changes, Xfce4.&lt;br /&gt;
|-&lt;br /&gt;
|[https://void-ppc64.octaforge.org Void-ppc64]&lt;br /&gt;
|n/a&lt;br /&gt;
|ppc64le/ppc64&lt;br /&gt;
|[[User:q66|q66]]&lt;br /&gt;
|Staging fork of Void Linux (custom binary repository and infrastructure, merging changes back upstream), fully functional, both endians, glibc or musl&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== BSDs ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://www.freebsd.org/ FreeBSD]&lt;br /&gt;
|12.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Contains initial POWER9 support&lt;br /&gt;
|-&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Ongoing development activity, better than releases for the time being&lt;br /&gt;
|-&lt;br /&gt;
|[https://github.com/POWER9BSD/ POWER9BSD]&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Advance POWER9 features for FreeBSD like Radix MMU, amdgpu etc&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Ports in progress===&lt;br /&gt;
Rapid progress is being made on these ports by members of the community.&lt;br /&gt;
&lt;br /&gt;
* NixOS&lt;br /&gt;
* GuixSD ([[User:Isengaara|Isengaara]])&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Troubleshooting/GPU&amp;diff=2350</id>
		<title>Troubleshooting/GPU</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Troubleshooting/GPU&amp;diff=2350"/>
		<updated>2019-04-16T02:43:25Z</updated>

		<summary type="html">&lt;p&gt;Q66: unified aspeed blacklisting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Troubleshooting]]&lt;br /&gt;
&lt;br /&gt;
== Background ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Common Issues ==&lt;br /&gt;
&lt;br /&gt;
=== Bootloader does not show up on monitor(s) attached to a discrete GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Alternatively, you either use a serial console or VGA monitor / adapter to interact with the bootloader.&lt;br /&gt;
&lt;br /&gt;
=== My AMD GPU works in petitboot but not the subsequent Linux OS ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If you need to use kernel 4.15 or below, you can work around this issue by either:&lt;br /&gt;
* Enabling and using the VGA video output to access the bootloader (petitboot) -or-&lt;br /&gt;
* using a serial connection to control petitboot, and running the following commands prior to selecting an operating system via the petitboot menu:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;echo 0 &amp;gt; /sys/class/vtconsole/vtcon1/bind&lt;br /&gt;
rmmod amdgpu&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== I want Petitboot via AST but the subsequent Linux OS console on a discrete GPU ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; module from loading is not sufficient on its own, you will need two kernel boot arguments:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;modprobe.blacklist=ast video=offb:off&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example on Ubuntu, this can be accomplished by changing &amp;lt;code&amp;gt;GRUB_CMDLINE_LINUX&amp;lt;/code&amp;gt; in &amp;lt;code&amp;gt;/etc/default/grub&amp;lt;/code&amp;gt; accordingly, like&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;GRUB_CMDLINE_LINUX=&amp;quot;modprobe.blacklist=ast video=offb:off&amp;quot;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and then running &amp;lt;code&amp;gt;update-grub&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Xorg will not start / crashes when a discrete GPU is installed ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;primary&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are available:&lt;br /&gt;
&lt;br /&gt;
==== Workaround 1: Disable on-board VGA====&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==== Workaround 2: Select desired GPU at runtime ====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===== Step 1: Locate Bus Numbers =====&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# lspci | grep VGA&lt;br /&gt;
0000:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100]&lt;br /&gt;
0005:02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note the numbers to the left of the &amp;quot;VGA compatible controller&amp;quot; string.  Each of these numbers is the PCI d:B:D.F&amp;lt;ref group=&amp;quot;note&amp;quot;&amp;gt;PCI Domain:Bus:Device.Function&amp;lt;/ref&amp;gt; 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.&lt;br /&gt;
&lt;br /&gt;
===== Step 2: Create Xorg Configuration Snippet =====&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# mkdir /etc/X11/xorg.conf.d&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Create and open &amp;lt;code&amp;gt;/etc/X11/xorg.conf.d/21-gpu-driver.conf&amp;lt;/code&amp;gt; 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 &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt;, 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 &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt; does; these must be stripped off when assembling the Xorg BusID.  Finally, Xorg expects to see a BusID assembled as &amp;quot;PCI:B@d:D:F&amp;quot; (note Bus and Domain are swapped), and should not be assembled not using the format shown by &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;# AST2500&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;GPU0&amp;quot;&lt;br /&gt;
    Driver         &amp;quot;modesetting&amp;quot;&lt;br /&gt;
    BusID          &amp;quot;PCI:2@5:0:0&amp;quot;&lt;br /&gt;
    VendorName     &amp;quot;ASpeed Corporation&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
# WX7100&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;GPU1&amp;quot;&lt;br /&gt;
    Driver         &amp;quot;modesetting&amp;quot; # or amdgpu if you have xf86-video-amdgpu installed&lt;br /&gt;
    BusID          &amp;quot;PCI:1@0:0:0&amp;quot;&lt;br /&gt;
    VendorName     &amp;quot;AMD Corporation&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
# this is absolutely necessary, it tells xorg which GPU to use for the screen&lt;br /&gt;
Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;Screen0&amp;quot;&lt;br /&gt;
    Device         &amp;quot;GPU1&amp;quot;&lt;br /&gt;
EndSection&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;code&amp;gt;amdgpu&amp;lt;/code&amp;gt; for the example above, keep in mind that the Xorg driver and the kernel driver are separate and distinct) has been loaded:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# modprobe amdgpu&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===== Step 3 (optional): Disable Integrated Video =====&lt;br /&gt;
&lt;br /&gt;
To disable the ASpeed VGA in the booted OS completely, you can use the &amp;lt;code&amp;gt;modprobe.blacklist=ast&amp;lt;/code&amp;gt; approach on kernel command line, refer to the &amp;quot;I want Petitboot via AST but the subsequent Linux OS console on a discrete GPU&amp;quot; section above for more information. This method is universal/works on all distributions. The ASpeed VGA will still show up in &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt; afterwards, which is normal, as you haven't disabled the hardware, just the driver.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
There are alternative ways to blacklist the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; kernel driver. For example on Debian based systems, create a new file &amp;lt;code&amp;gt;/etc/modprobe.d/ast-blacklist.conf&amp;lt;/code&amp;gt; and place the following line inside the new file:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;blacklist ast&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You may need to reboot if the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; DRM driver has already loaded.  Alternatively, you may try to unbind and unload the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver as follows (assuming the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver is bound to vtcon0):&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# echo 0 &amp;gt; /sys/class/vtconsole/vtcon0/bind&lt;br /&gt;
root@talos:~# rmmod ast&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Monitor not detected in kernel 4.17+ ===&lt;br /&gt;
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 &amp;lt;code&amp;gt;amdgpu.dc=0&amp;lt;/code&amp;gt; to the kernel parameters.  This is often associated with a host dmesg trace of&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;[drm] Cannot find any crtc or sizes&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Xorg crashes or is laggy with the AST VGA GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
In addition, on Debian Buster, GLAMOR has been observed to crash when used in conjunction with llvmpipe.&lt;br /&gt;
&lt;br /&gt;
You can disable GLAMOR by saving the following text file as &amp;lt;code&amp;gt;/usr/share/X11/xorg.conf.d/00-noglamoregl.conf&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Device&amp;quot;&lt;br /&gt;
 	Identifier &amp;quot;nogpu&amp;quot;&lt;br /&gt;
 	Driver &amp;quot;modesetting&amp;quot;&lt;br /&gt;
 	Option &amp;quot;Accelmethod&amp;quot; &amp;quot;none&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
 &lt;br /&gt;
 Section &amp;quot;Module&amp;quot;&lt;br /&gt;
 	Disable &amp;quot;glamoregl&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
This bug was probably fixed by [https://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.20-branch&amp;amp;id=1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4 commit 1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4] in upstream Xorg; it is unknown how quickly the fix will make its way to GNU/Linux distributions.&lt;br /&gt;
&lt;br /&gt;
=== KDE is laggy with the AST VGA GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To fix this, go to &amp;lt;code&amp;gt;System Settings&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Hardware&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Display and Monitor&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Compositor&amp;lt;/code&amp;gt;, and select &amp;lt;code&amp;gt;XRender&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;Rendering backend&amp;lt;/code&amp;gt;.  You'll probably also want to select &amp;lt;code&amp;gt;Smooth (slower)&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;Scale method&amp;lt;/code&amp;gt; (it's still much faster than OpenGL, and it looks quite a bit better).&lt;br /&gt;
&lt;br /&gt;
=== AMDGPU driver crashes after firmware update ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references group=&amp;quot;note&amp;quot;/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Troubleshooting/GPU&amp;diff=2342</id>
		<title>Troubleshooting/GPU</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Troubleshooting/GPU&amp;diff=2342"/>
		<updated>2019-04-07T16:28:58Z</updated>

		<summary type="html">&lt;p&gt;Q66: driver note&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Troubleshooting]]&lt;br /&gt;
&lt;br /&gt;
== Background ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Common Issues ==&lt;br /&gt;
&lt;br /&gt;
=== Bootloader does not show up on monitor(s) attached to a discrete GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Alternatively, you either use a serial console or VGA monitor / adapter to interact with the bootloader.&lt;br /&gt;
&lt;br /&gt;
=== My AMD GPU works in petitboot but not the subsequent Linux OS ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If you need to use kernel 4.15 or below, you can work around this issue by either:&lt;br /&gt;
* Enabling and using the VGA video output to access the bootloader (petitboot) -or-&lt;br /&gt;
* using a serial connection to control petitboot, and running the following commands prior to selecting an operating system via the petitboot menu:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;echo 0 &amp;gt; /sys/class/vtconsole/vtcon1/bind&lt;br /&gt;
rmmod amdgpu&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== I want Petitboot via AST but the subsequent Linux OS console on a discrete GPU ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; module from loading is not sufficient on its own, you will need two kernel boot arguments:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;modprobe.blacklist=ast video=offb:off&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example on Ubuntu, this can be accomplished by changing &amp;lt;code&amp;gt;GRUB_CMDLINE_LINUX&amp;lt;/code&amp;gt; in &amp;lt;code&amp;gt;/etc/default/grub&amp;lt;/code&amp;gt; accordingly, like&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;GRUB_CMDLINE_LINUX=&amp;quot;modprobe.blacklist=ast video=offb:off&amp;quot;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and then running &amp;lt;code&amp;gt;update-grub&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Xorg will not start / crashes when a discrete GPU is installed ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;primary&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are available:&lt;br /&gt;
&lt;br /&gt;
==== Workaround 1: Disable on-board VGA====&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==== Workaround 2: Select desired GPU at runtime ====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===== Step 1: Locate Bus Numbers =====&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# lspci | grep VGA&lt;br /&gt;
0000:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100]&lt;br /&gt;
0005:02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note the numbers to the left of the &amp;quot;VGA compatible controller&amp;quot; string.  Each of these numbers is the PCI d:B:D.F&amp;lt;ref group=&amp;quot;note&amp;quot;&amp;gt;PCI Domain:Bus:Device.Function&amp;lt;/ref&amp;gt; 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.&lt;br /&gt;
&lt;br /&gt;
===== Step 2: Create Xorg Configuration Snippet =====&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# mkdir /etc/X11/xorg.conf.d&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Create and open &amp;lt;code&amp;gt;/etc/X11/xorg.conf.d/21-gpu-driver.conf&amp;lt;/code&amp;gt; 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 &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt;, 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 &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt; does; these must be stripped off when assembling the Xorg BusID.  Finally, Xorg expects to see a BusID assembled as &amp;quot;PCI:B@d:D:F&amp;quot; (note Bus and Domain are swapped), and should not be assembled not using the format shown by &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;# AST2500&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;GPU0&amp;quot;&lt;br /&gt;
    Driver         &amp;quot;modesetting&amp;quot;&lt;br /&gt;
    BusID          &amp;quot;PCI:2@5:0:0&amp;quot;&lt;br /&gt;
    VendorName     &amp;quot;ASpeed Corporation&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
# WX7100&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;GPU1&amp;quot;&lt;br /&gt;
    Driver         &amp;quot;modesetting&amp;quot; # or amdgpu if you have xf86-video-amdgpu installed&lt;br /&gt;
    BusID          &amp;quot;PCI:1@0:0:0&amp;quot;&lt;br /&gt;
    VendorName     &amp;quot;AMD Corporation&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
# this is absolutely necessary, it tells xorg which GPU to use for the screen&lt;br /&gt;
Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;Screen0&amp;quot;&lt;br /&gt;
    Device         &amp;quot;GPU1&amp;quot;&lt;br /&gt;
EndSection&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;code&amp;gt;amdgpu&amp;lt;/code&amp;gt; for the example above, keep in mind that the Xorg driver and the kernel driver are separate and distinct) has been loaded:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# modprobe amdgpu&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===== Step 3 (optional): Disable Integrated Video =====&lt;br /&gt;
&lt;br /&gt;
If you want all Xorg output to be directed to your discrete GPU(s), you may want to disable the integrated VGA video output as much as possible.  To do this, delete the ASpeed block from your Xorg configuration snippet, and blacklist the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver.  To blacklist the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver on Debian based systems, create a new file &amp;lt;code&amp;gt;/etc/modprobe.d/ast-blacklist.conf&amp;lt;/code&amp;gt; and place the following line inside the new file:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;blacklist ast&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You may need to reboot if the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; DRM driver has already loaded.  Alternatively, you may try to unbind and unload the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver as follows (assuming the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver is bound to vtcon0):&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# echo 0 &amp;gt; /sys/class/vtconsole/vtcon0/bind&lt;br /&gt;
root@talos:~# rmmod ast&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Monitor not detected in kernel 4.17+ ===&lt;br /&gt;
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 &amp;lt;code&amp;gt;amdgpu.dc=0&amp;lt;/code&amp;gt; to the kernel parameters.  This is often associated with a host dmesg trace of&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;[drm] Cannot find any crtc or sizes&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Xorg crashes or is laggy with the AST VGA GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
In addition, on Debian Buster, GLAMOR has been observed to crash when used in conjunction with llvmpipe.&lt;br /&gt;
&lt;br /&gt;
You can disable GLAMOR by saving the following text file as &amp;lt;code&amp;gt;/usr/share/X11/xorg.conf.d/00-noglamoregl.conf&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Device&amp;quot;&lt;br /&gt;
 	Identifier &amp;quot;nogpu&amp;quot;&lt;br /&gt;
 	Driver &amp;quot;modesetting&amp;quot;&lt;br /&gt;
 	Option &amp;quot;Accelmethod&amp;quot; &amp;quot;none&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
 &lt;br /&gt;
 Section &amp;quot;Module&amp;quot;&lt;br /&gt;
 	Disable &amp;quot;glamoregl&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
This bug was probably fixed by [https://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.20-branch&amp;amp;id=1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4 commit 1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4] in upstream Xorg; it is unknown how quickly the fix will make its way to GNU/Linux distributions.&lt;br /&gt;
&lt;br /&gt;
=== KDE is laggy with the AST VGA GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To fix this, go to &amp;lt;code&amp;gt;System Settings&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Hardware&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Display and Monitor&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Compositor&amp;lt;/code&amp;gt;, and select &amp;lt;code&amp;gt;XRender&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;Rendering backend&amp;lt;/code&amp;gt;.  You'll probably also want to select &amp;lt;code&amp;gt;Smooth (slower)&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;Scale method&amp;lt;/code&amp;gt; (it's still much faster than OpenGL, and it looks quite a bit better).&lt;br /&gt;
&lt;br /&gt;
=== AMDGPU driver crashes after firmware update ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references group=&amp;quot;note&amp;quot;/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Troubleshooting/GPU&amp;diff=2341</id>
		<title>Troubleshooting/GPU</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Troubleshooting/GPU&amp;diff=2341"/>
		<updated>2019-04-07T16:26:50Z</updated>

		<summary type="html">&lt;p&gt;Q66: formatting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Troubleshooting]]&lt;br /&gt;
&lt;br /&gt;
== Background ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Common Issues ==&lt;br /&gt;
&lt;br /&gt;
=== Bootloader does not show up on monitor(s) attached to a discrete GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Alternatively, you either use a serial console or VGA monitor / adapter to interact with the bootloader.&lt;br /&gt;
&lt;br /&gt;
=== My AMD GPU works in petitboot but not the subsequent Linux OS ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If you need to use kernel 4.15 or below, you can work around this issue by either:&lt;br /&gt;
* Enabling and using the VGA video output to access the bootloader (petitboot) -or-&lt;br /&gt;
* using a serial connection to control petitboot, and running the following commands prior to selecting an operating system via the petitboot menu:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;echo 0 &amp;gt; /sys/class/vtconsole/vtcon1/bind&lt;br /&gt;
rmmod amdgpu&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== I want Petitboot via AST but the subsequent Linux OS console on a discrete GPU ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; module from loading is not sufficient on its own, you will need two kernel boot arguments:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;modprobe.blacklist=ast video=offb:off&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example on Ubuntu, this can be accomplished by changing &amp;lt;code&amp;gt;GRUB_CMDLINE_LINUX&amp;lt;/code&amp;gt; in &amp;lt;code&amp;gt;/etc/default/grub&amp;lt;/code&amp;gt; accordingly, like&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;GRUB_CMDLINE_LINUX=&amp;quot;modprobe.blacklist=ast video=offb:off&amp;quot;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and then running &amp;lt;code&amp;gt;update-grub&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Xorg will not start / crashes when a discrete GPU is installed ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;primary&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are available:&lt;br /&gt;
&lt;br /&gt;
==== Workaround 1: Disable on-board VGA====&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==== Workaround 2: Select desired GPU at runtime ====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===== Step 1: Locate Bus Numbers =====&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# lspci | grep VGA&lt;br /&gt;
0000:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100]&lt;br /&gt;
0005:02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note the numbers to the left of the &amp;quot;VGA compatible controller&amp;quot; string.  Each of these numbers is the PCI d:B:D.F&amp;lt;ref group=&amp;quot;note&amp;quot;&amp;gt;PCI Domain:Bus:Device.Function&amp;lt;/ref&amp;gt; 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.&lt;br /&gt;
&lt;br /&gt;
===== Step 2: Create Xorg Configuration Snippet =====&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# mkdir /etc/X11/xorg.conf.d&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Create and open &amp;lt;code&amp;gt;/etc/X11/xorg.conf.d/21-gpu-driver.conf&amp;lt;/code&amp;gt; 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 &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt;, 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 &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt; does; these must be stripped off when assembling the Xorg BusID.  Finally, Xorg expects to see a BusID assembled as &amp;quot;PCI:B@d:D:F&amp;quot; (note Bus and Domain are swapped), and should not be assembled not using the format shown by &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;# AST2500&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;GPU0&amp;quot;&lt;br /&gt;
    Driver         &amp;quot;modesetting&amp;quot;&lt;br /&gt;
    BusID          &amp;quot;PCI:2@5:0:0&amp;quot;&lt;br /&gt;
    VendorName     &amp;quot;ASpeed Corporation&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
# WX7100&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;GPU1&amp;quot;&lt;br /&gt;
    Driver         &amp;quot;modesetting&amp;quot; # or amdgpu if you have xf86-video-amdgpu installed&lt;br /&gt;
    BusID          &amp;quot;PCI:1@0:0:0&amp;quot;&lt;br /&gt;
    VendorName     &amp;quot;AMD Corporation&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
# this is absolutely necessary, it tells xorg which GPU to use for the screen&lt;br /&gt;
Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;Screen0&amp;quot;&lt;br /&gt;
    Device         &amp;quot;GPU1&amp;quot;&lt;br /&gt;
EndSection&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;code&amp;gt;amdgpu&amp;lt;/code&amp;gt; in the example above) has been loaded:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# modprobe amdgpu&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use the generic modesetting 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.&lt;br /&gt;
&lt;br /&gt;
===== Step 3 (optional): Disable Integrated Video =====&lt;br /&gt;
&lt;br /&gt;
If you want all Xorg output to be directed to your discrete GPU(s), you may want to disable the integrated VGA video output as much as possible.  To do this, delete the ASpeed block from your Xorg configuration snippet, and blacklist the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver.  To blacklist the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver on Debian based systems, create a new file &amp;lt;code&amp;gt;/etc/modprobe.d/ast-blacklist.conf&amp;lt;/code&amp;gt; and place the following line inside the new file:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;blacklist ast&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You may need to reboot if the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; DRM driver has already loaded.  Alternatively, you may try to unbind and unload the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver as follows (assuming the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver is bound to vtcon0):&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# echo 0 &amp;gt; /sys/class/vtconsole/vtcon0/bind&lt;br /&gt;
root@talos:~# rmmod ast&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Monitor not detected in kernel 4.17+ ===&lt;br /&gt;
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 &amp;lt;code&amp;gt;amdgpu.dc=0&amp;lt;/code&amp;gt; to the kernel parameters.  This is often associated with a host dmesg trace of&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;[drm] Cannot find any crtc or sizes&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Xorg crashes or is laggy with the AST VGA GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
In addition, on Debian Buster, GLAMOR has been observed to crash when used in conjunction with llvmpipe.&lt;br /&gt;
&lt;br /&gt;
You can disable GLAMOR by saving the following text file as &amp;lt;code&amp;gt;/usr/share/X11/xorg.conf.d/00-noglamoregl.conf&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Device&amp;quot;&lt;br /&gt;
 	Identifier &amp;quot;nogpu&amp;quot;&lt;br /&gt;
 	Driver &amp;quot;modesetting&amp;quot;&lt;br /&gt;
 	Option &amp;quot;Accelmethod&amp;quot; &amp;quot;none&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
 &lt;br /&gt;
 Section &amp;quot;Module&amp;quot;&lt;br /&gt;
 	Disable &amp;quot;glamoregl&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
This bug was probably fixed by [https://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.20-branch&amp;amp;id=1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4 commit 1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4] in upstream Xorg; it is unknown how quickly the fix will make its way to GNU/Linux distributions.&lt;br /&gt;
&lt;br /&gt;
=== KDE is laggy with the AST VGA GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To fix this, go to &amp;lt;code&amp;gt;System Settings&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Hardware&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Display and Monitor&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Compositor&amp;lt;/code&amp;gt;, and select &amp;lt;code&amp;gt;XRender&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;Rendering backend&amp;lt;/code&amp;gt;.  You'll probably also want to select &amp;lt;code&amp;gt;Smooth (slower)&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;Scale method&amp;lt;/code&amp;gt; (it's still much faster than OpenGL, and it looks quite a bit better).&lt;br /&gt;
&lt;br /&gt;
=== AMDGPU driver crashes after firmware update ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references group=&amp;quot;note&amp;quot;/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Troubleshooting/GPU&amp;diff=2340</id>
		<title>Troubleshooting/GPU</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Troubleshooting/GPU&amp;diff=2340"/>
		<updated>2019-04-07T16:24:24Z</updated>

		<summary type="html">&lt;p&gt;Q66: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Troubleshooting]]&lt;br /&gt;
&lt;br /&gt;
== Background ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Common Issues ==&lt;br /&gt;
&lt;br /&gt;
=== Bootloader does not show up on monitor(s) attached to a discrete GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Alternatively, you either use a serial console or VGA monitor / adapter to interact with the bootloader.&lt;br /&gt;
&lt;br /&gt;
=== My AMD GPU works in petitboot but not the subsequent Linux OS ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If you need to use kernel 4.15 or below, you can work around this issue by either:&lt;br /&gt;
* Enabling and using the VGA video output to access the bootloader (petitboot) -or-&lt;br /&gt;
* using a serial connection to control petitboot, and running the following commands prior to selecting an operating system via the petitboot menu:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;echo 0 &amp;gt; /sys/class/vtconsole/vtcon1/bind&lt;br /&gt;
rmmod amdgpu&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== I want Petitboot via AST but the subsequent Linux OS console on a discrete GPU ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; module from loading is not sufficient on its own, you will need two kernel boot arguments:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;modprobe.blacklist=ast video=offb:off&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example on Ubuntu, this can be accomplished by changing &amp;lt;code&amp;gt;GRUB_CMDLINE_LINUX&amp;lt;/code&amp;gt; in &amp;lt;code&amp;gt;/etc/default/grub&amp;lt;/code&amp;gt; accordingly, like&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;GRUB_CMDLINE_LINUX=&amp;quot;modprobe.blacklist=ast video=offb:off&amp;quot;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and then running &amp;lt;code&amp;gt;update-grub&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Xorg will not start / crashes when a discrete GPU is installed ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;primary&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are available:&lt;br /&gt;
&lt;br /&gt;
==== Workaround 1: Disable on-board VGA====&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==== Workaround 2: Select desired GPU at runtime ====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===== Step 1: Locate Bus Numbers =====&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# lspci | grep VGA&lt;br /&gt;
0000:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100]&lt;br /&gt;
0005:02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note the numbers to the left of the &amp;quot;VGA compatible controller&amp;quot; string.  Each of these numbers is the PCI d:B:D.F&amp;lt;ref group=&amp;quot;note&amp;quot;&amp;gt;PCI Domain:Bus:Device.Function&amp;lt;/ref&amp;gt; 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.&lt;br /&gt;
&lt;br /&gt;
===== Step 2: Create Xorg Configuration Snippet =====&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# mkdir /etc/X11/xorg.conf.d&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Create and open &amp;lt;code&amp;gt;/etc/X11/xorg.conf.d/21-gpu-driver.conf&amp;lt;/code&amp;gt; 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 &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt;, 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 &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt; does; these must be stripped off when assembling the Xorg BusID.  Finally, Xorg expects to see a BusID assembled as &amp;quot;PCI:B@d:D:F&amp;quot; (note Bus and Domain are swapped), and should not be assembled not using the format shown by &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;# AST2500&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;GPU0&amp;quot;&lt;br /&gt;
    Driver         &amp;quot;modesetting&amp;quot;&lt;br /&gt;
    BusID          &amp;quot;PCI:2@5:0:0&amp;quot;&lt;br /&gt;
    VendorName     &amp;quot;ASpeed Corporation&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
# WX7100&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;GPU1&amp;quot;&lt;br /&gt;
    Driver         &amp;quot;modesetting&amp;quot; # or amdgpu if you have xf86-video-amdgpu installed&lt;br /&gt;
    BusID          &amp;quot;PCI:1@0:0:0&amp;quot;&lt;br /&gt;
    VendorName     &amp;quot;AMD Corporation&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
# this is absolutely necessary, it tells xorg which GPU to use for the screen&lt;br /&gt;
Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
    Identifier &amp;quot;Screen0&amp;quot;&lt;br /&gt;
    Device &amp;quot;GPU1&amp;quot;&lt;br /&gt;
EndSection&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;code&amp;gt;amdgpu&amp;lt;/code&amp;gt; in the example above) has been loaded:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# modprobe amdgpu&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use the generic modesetting 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.&lt;br /&gt;
&lt;br /&gt;
===== Step 3 (optional): Disable Integrated Video =====&lt;br /&gt;
&lt;br /&gt;
If you want all Xorg output to be directed to your discrete GPU(s), you may want to disable the integrated VGA video output as much as possible.  To do this, delete the ASpeed block from your Xorg configuration snippet, and blacklist the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver.  To blacklist the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver on Debian based systems, create a new file &amp;lt;code&amp;gt;/etc/modprobe.d/ast-blacklist.conf&amp;lt;/code&amp;gt; and place the following line inside the new file:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;blacklist ast&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You may need to reboot if the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; DRM driver has already loaded.  Alternatively, you may try to unbind and unload the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver as follows (assuming the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver is bound to vtcon0):&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# echo 0 &amp;gt; /sys/class/vtconsole/vtcon0/bind&lt;br /&gt;
root@talos:~# rmmod ast&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Monitor not detected in kernel 4.17+ ===&lt;br /&gt;
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 &amp;lt;code&amp;gt;amdgpu.dc=0&amp;lt;/code&amp;gt; to the kernel parameters.  This is often associated with a host dmesg trace of&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;[drm] Cannot find any crtc or sizes&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Xorg crashes or is laggy with the AST VGA GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
In addition, on Debian Buster, GLAMOR has been observed to crash when used in conjunction with llvmpipe.&lt;br /&gt;
&lt;br /&gt;
You can disable GLAMOR by saving the following text file as &amp;lt;code&amp;gt;/usr/share/X11/xorg.conf.d/00-noglamoregl.conf&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Device&amp;quot;&lt;br /&gt;
 	Identifier &amp;quot;nogpu&amp;quot;&lt;br /&gt;
 	Driver &amp;quot;modesetting&amp;quot;&lt;br /&gt;
 	Option &amp;quot;Accelmethod&amp;quot; &amp;quot;none&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
 &lt;br /&gt;
 Section &amp;quot;Module&amp;quot;&lt;br /&gt;
 	Disable &amp;quot;glamoregl&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
This bug was probably fixed by [https://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.20-branch&amp;amp;id=1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4 commit 1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4] in upstream Xorg; it is unknown how quickly the fix will make its way to GNU/Linux distributions.&lt;br /&gt;
&lt;br /&gt;
=== KDE is laggy with the AST VGA GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To fix this, go to &amp;lt;code&amp;gt;System Settings&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Hardware&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Display and Monitor&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Compositor&amp;lt;/code&amp;gt;, and select &amp;lt;code&amp;gt;XRender&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;Rendering backend&amp;lt;/code&amp;gt;.  You'll probably also want to select &amp;lt;code&amp;gt;Smooth (slower)&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;Scale method&amp;lt;/code&amp;gt; (it's still much faster than OpenGL, and it looks quite a bit better).&lt;br /&gt;
&lt;br /&gt;
=== AMDGPU driver crashes after firmware update ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references group=&amp;quot;note&amp;quot;/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Dual_92mm_fan_CPU&amp;diff=2317</id>
		<title>Dual 92mm fan CPU</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Dual_92mm_fan_CPU&amp;diff=2317"/>
		<updated>2019-03-31T15:03:27Z</updated>

		<summary type="html">&lt;p&gt;Q66: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Dual 92mm Fan CPU Cooling =&lt;br /&gt;
It is recommended to choose a high quality fan for this modification, with specs at least close to equivalent to the tested fans. Also, ensure adequate airflow through the chassis, which is true always, even with the default cooling. It is also important to attach the fans in a push-pull configuration, where one of the fans pushes air through the heatsink fins and the other fan takes in hot air and blows it out towards the back of the case. This is achieved by orienting both fans in the same direction. The &amp;quot;base&amp;quot; (grille) side of the fan is the exhaust, while the &amp;quot;blade&amp;quot; side of the fan is the intake. See pictures for proper configuration.&lt;br /&gt;
&lt;br /&gt;
The fans should both be connected to the CPU fan connector using a 4-pin Y cable. The tested Noctua NF-A9 PWM bundles this cable, for other fans you might have to purchase it separately.&lt;br /&gt;
&lt;br /&gt;
== Fans Used ==&lt;br /&gt;
* Noctua NF-B9 PWM&lt;br /&gt;
** Tested by [[User:q66|q66]] on single CPU 18-core system. Reports lower max temp and lower noise levels vs stock, under stress testing. Achieves max turbo boost. Performs similarly to NF-A9 PWM with the bundled low noise adapter (LNA), as the NF-B9 PWM is 1600 RPM, while the NF-A9 PWM is 2000 RPM and 1550 RPM with LNA. Unlike NF-A9 PWM, it does not have builtin rubber anti-vibration pads, which does not seem to make much actual difference. You are unlikely to find this fan (as NF-A9 PWM is the successor) unless you already have them at home.&lt;br /&gt;
* Noctua NF-A9 PWM&lt;br /&gt;
** Tested by [[User:q66|q66]] on a single CPU 18-core system. Stress testing reveals 54°C on hottest core with default speed and 30°C in idle; with LNA, 32°C in idle and 65°C hottest core under prolonged stress testing (sensors reporting maximum CPU power draw/overclock). Therefore, it is safe to use the LNA, as 65°C is well within headroom for maximum turbo boost.&lt;br /&gt;
** Pending testing by [[User:nashimus|nashimus]] on dual 18 core system, SC747TG-R1400B-SQ chassis. More photos/info to come when board is back from RMA.&lt;br /&gt;
&lt;br /&gt;
== Attaching The Fans ==&lt;br /&gt;
&lt;br /&gt;
(Noctua NF-A9 Pictured, for both setups; NF-B9 looks nearly identical)&lt;br /&gt;
[[File:3U CPU NF-A9 01.JPG|left|thumb|800px|[[User:nashimus|nashimus]]: Attached using a thin, but stiff, solid stainless steel wire to connect to partially inserted fan screws. An &amp;quot;H&amp;quot; pattern is used to keep the fans aligned with the heat sink.]]&lt;br /&gt;
[[File:3U CPU NF-A9 02.JPG|left|thumb|800px|[[User:nashimus|nashimus]]: The fan is a little crooked in this photo from being handled. An additional strand could prevent the fan from moving, but it doesn't seem necessary at this point. The fans are already pretty snug.]]&lt;br /&gt;
[[File:3U CPU NF-A9 03.JPG|left|thumb|800px|[[User:nashimus|nashimus]]: Due to the placement of the heat sink retention mechanism, the fans stand about a centimeter above the top of the heat sink.]]&lt;br /&gt;
[[File:3U CPU NF-A9 04.JPG|left|thumb|800px|[[User:nashimus|nashimus]]: ...]]&lt;br /&gt;
&lt;br /&gt;
[[File:3U-NF-A9-PWM-q66-1.jpg|left|thumb|800px|[[User:q66|q66]]: Attached using several nylon zip ties joined together. The simpler of the methods, but holds the fans perfectly, with no vibrations or obstructions.]]&lt;br /&gt;
[[File:3U-NF-A9-PWM-q66-2.jpg|left|thumb|800px|[[User:q66|q66]]: Closeup of the attachment. The overhang is present, just like with method 1, with no way to avoid it, but it doesn't do any harm as long as you have the height in your case available (pretty much any tower or 4U case will have plenty of space)]]&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Dual_92mm_fan_CPU&amp;diff=2315</id>
		<title>Dual 92mm fan CPU</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Dual_92mm_fan_CPU&amp;diff=2315"/>
		<updated>2019-03-31T14:57:03Z</updated>

		<summary type="html">&lt;p&gt;Q66: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Dual 92mm Fan CPU Cooling =&lt;br /&gt;
It is recommended to choose a high quality fan for this modification. Also, ensure adequate airflow through the chassis. It is also important to attach the fans in a push-pull configuration, where one of the fans pushes air through the heatsink fins and the other fan takes in hot air and blows it out towards the back of the case. This is achieved by orienting both fans in the same direction. The &amp;quot;base&amp;quot; (grille) side of the fan is the exhaust, while the &amp;quot;blade&amp;quot; side of the fan is the intake. See pictures for proper configuration.&lt;br /&gt;
== Fans Used ==&lt;br /&gt;
* Noctua NF-B9 PWM&lt;br /&gt;
** Tested by [[User:q66|q66]] on single CPU 18-core system. Reports lower max temp and lower noise levels vs stock, under stress testing. Achieves max turbo boost. Performs similarly to NF-A9 PWM with the bundled low noise adapter (LNA), as the NF-B9 PWM is 1600 RPM, while the NF-A9 PWM is 2000 RPM and 1550 RPM with LNA. Unlike NF-A9 PWM, it does not have builtin rubber anti-vibration pads, which does not seem to make much actual difference. You are unlikely to find this fan (as NF-A9 PWM is the successor) unless you already have them at home.&lt;br /&gt;
* Noctua NF-A9 PWM&lt;br /&gt;
** Tested by [[User:q66|q66]] on a single CPU 18-core system. Stress testing reveals 54°C on hottest core with default speed and 30°C in idle; with LNA, 32°C in idle and 65°C hottest core under prolonged stress testing (sensors reporting maximum CPU power draw/overclock). Therefore, it is safe to use the LNA, as 65°C is well within headroom for maximum turbo boost.&lt;br /&gt;
** Pending testing by [[User:nashimus|nashimus]] on dual 18 core system, SC747TG-R1400B-SQ chassis. More photos/info to come when board is back from RMA.&lt;br /&gt;
&lt;br /&gt;
== Attaching The Fans ==&lt;br /&gt;
&lt;br /&gt;
(Noctua NF-A9 Pictured, for both setups; NF-B9 looks nearly identical)&lt;br /&gt;
[[File:3U CPU NF-A9 01.JPG|left|thumb|800px|[[User:nashimus|nashimus]]: Attached using a thin, but stiff, solid stainless steel wire to connect to partially inserted fan screws. An &amp;quot;H&amp;quot; pattern is used to keep the fans aligned with the heat sink.]]&lt;br /&gt;
[[File:3U CPU NF-A9 02.JPG|left|thumb|800px|[[User:nashimus|nashimus]]: The fan is a little crooked in this photo from being handled. An additional strand could prevent the fan from moving, but it doesn't seem necessary at this point. The fans are already pretty snug.]]&lt;br /&gt;
[[File:3U CPU NF-A9 03.JPG|left|thumb|800px|[[User:nashimus|nashimus]]: Due to the placement of the heat sink retention mechanism, the fans stand about a centimeter above the top of the heat sink.]]&lt;br /&gt;
[[File:3U CPU NF-A9 04.JPG|left|thumb|800px|[[User:nashimus|nashimus]]: ...]]&lt;br /&gt;
&lt;br /&gt;
[[File:3U-NF-A9-PWM-q66-1.jpg|left|thumb|800px|[[User:q66|q66]]: Attached using several nylon zip ties joined together. The simpler of the methods, but holds the fans perfectly, with no vibrations or obstructions.]]&lt;br /&gt;
[[File:3U-NF-A9-PWM-q66-2.jpg|left|thumb|800px|[[User:q66|q66]]: Closeup of the attachment. The overhang is present, just like with method 1, with no way to avoid it, but it doesn't do any harm as long as you have the height in your case available (pretty much any tower or 4U case will have plenty of space)]]&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=File:3U-NF-A9-PWM-q66-2.jpg&amp;diff=2313</id>
		<title>File:3U-NF-A9-PWM-q66-2.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=File:3U-NF-A9-PWM-q66-2.jpg&amp;diff=2313"/>
		<updated>2019-03-31T14:50:14Z</updated>

		<summary type="html">&lt;p&gt;Q66: Dual NF-A9 PWM attached using nylon zip ties&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Dual NF-A9 PWM attached using nylon zip ties&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=File:3U-NF-A9-PWM-q66-1.jpg&amp;diff=2312</id>
		<title>File:3U-NF-A9-PWM-q66-1.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=File:3U-NF-A9-PWM-q66-1.jpg&amp;diff=2312"/>
		<updated>2019-03-31T14:49:45Z</updated>

		<summary type="html">&lt;p&gt;Q66: Dual NF-A9 PWM attached using nylon zip ties&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Dual NF-A9 PWM attached using nylon zip ties&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Dual_92mm_fan_CPU&amp;diff=2311</id>
		<title>Dual 92mm fan CPU</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Dual_92mm_fan_CPU&amp;diff=2311"/>
		<updated>2019-03-31T14:46:06Z</updated>

		<summary type="html">&lt;p&gt;Q66: q66 test&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Dual 92mm Fan CPU Cooling =&lt;br /&gt;
It is recommended to choose a high quality fan for this modification. Also, ensure adequate airflow through the chassis. It is also important to attach the fans in a push-pull configuration, where one of the fans pushes air through the heatsink fins and the other fan takes in hot air and blows it out towards the back of the case. This is achieved by orienting both fans in the same direction. The &amp;quot;base&amp;quot; (grille) side of the fan is the exhaust, while the &amp;quot;blade&amp;quot; side of the fan is the intake. See pictures for proper configuration.&lt;br /&gt;
== Fans Used ==&lt;br /&gt;
* Noctua NF-B9 PWM&lt;br /&gt;
** Tested by [[User:q66|q66]] on single CPU 18-core system. Reports lower max temp and lower noise levels vs stock, under stress testing. Achieves max turbo boost. Performs similarly to NF-A9 PWM with the bundled low noise adapter (LNA), as the NF-B9 PWM is 1600 RPM, while the NF-A9 PWM is 2000 RPM and 1550 RPM with LNA.&lt;br /&gt;
* Noctua NF-A9 PWM&lt;br /&gt;
** Tested by [[User:q66|q66]] on a single CPU 18-core system. Stress testing reveals 54°C on hottest core with default speed and 30°C in idle; with LNA, 32°C in idle and 65°C hottest core under prolonged stress testing (sensors reporting maximum CPU power draw/overclock). Therefore, it is safe to use the LNA, as 65°C is well within headroom for maximum turbo boost.&lt;br /&gt;
** Pending testing by [[User:nashimus|nashimus]] on dual 18 core system, SC747TG-R1400B-SQ chassis. More photos/info to come when board is back from RMA.&lt;br /&gt;
&lt;br /&gt;
== Attaching The Fans ==&lt;br /&gt;
&lt;br /&gt;
(Noctua NF-A9 Pictured)&lt;br /&gt;
[[File:3U CPU NF-A9 01.JPG|left|thumb|800px|Attached using a thin, but stiff, solid stainless steel wire to connect to partially inserted fan screws. An &amp;quot;H&amp;quot; pattern is used to keep the fans aligned with the heat sink.]]&lt;br /&gt;
[[File:3U CPU NF-A9 02.JPG|left|thumb|800px|The fan is a little crooked in this photo from being handled. An additional strand could prevent the fan from moving, but it doesn't seem necessary at this point. The fans are already pretty snug.]]&lt;br /&gt;
[[File:3U CPU NF-A9 03.JPG|left|thumb|800px|Due to the placement of the heat sink retention mechanism, the fans stand about a centimeter above the top of the heat sink.]]&lt;br /&gt;
[[File:3U CPU NF-A9 04.JPG|left|thumb|800px]]&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=1875</id>
		<title>Operating System Compatibility List</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=1875"/>
		<updated>2019-01-06T15:18:17Z</updated>

		<summary type="html">&lt;p&gt;Q66: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Not everything is bug-free, so you might want to the check also [[Fixes in Progress]] about the state of their upstreaming.&lt;br /&gt;
== GNU/Linux ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.adelielinux.org/ Adélie]&lt;br /&gt;
|1.0-beta1&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Needs the easy-kernel-power8 package instead of easy-kernel.  KDE 5 is stable.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;4&amp;quot;|[https://cdimage.debian.org/cdimage/ Debian]&lt;br /&gt;
|10 (2018-05-28 weekly DVD ISO)&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Only tested in KVM-PV.  Using Adélie easy-kernel as kernel, Debian Buster userland.&lt;br /&gt;
|-&lt;br /&gt;
|9.5.0&lt;br /&gt;
|ppc64le (inside KVM; machine type = pseries)&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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 &amp;lt;code&amp;gt;dpkg-query -W -f='${Section}\t${Package}\n' &amp;amp;#124; grep ^contrib&amp;lt;/code&amp;gt; (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.&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|[https://alt.fedoraproject.org/alt/ Fedora]&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|28&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|ppc64le&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|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&lt;br /&gt;
|-&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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]&lt;br /&gt;
|-&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|discontinued in Fedora 29&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://wiki.gentoo.org/wiki/Handbook:PPC64 Gentoo]&lt;br /&gt;
| n/a&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:Luke-jr|luke-jr]]&lt;br /&gt;
|Once installed, works fine.&lt;br /&gt;
|-&lt;br /&gt;
|17.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:MarcusC|MarcusC]]&lt;br /&gt;
|XFCE4 and virt-manager verified&lt;br /&gt;
|-&lt;br /&gt;
|[http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ Whonix] ([https://www.whonix.org/ clearnet link])&lt;br /&gt;
|14&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|Appears to work fine when the [[Whonix]] instructions are followed; host OS used for testing was Debian 10.&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.ubuntu.com/download/server/power Ubuntu]&lt;br /&gt;
|18.10&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:q66|q66]]&lt;br /&gt;
|Installs and works out of box with no changes, Xfce4.&lt;br /&gt;
|-&lt;br /&gt;
|[https://void-ppc64.octaforge.org Void-ppc64]&lt;br /&gt;
|n/a&lt;br /&gt;
|ppc64le, ppc64le-musl, ppc64-musl&lt;br /&gt;
|[[User:q66|q66]]&lt;br /&gt;
|Staging fork of Void Linux (custom binary repository and infrastructure, merging changes back upstream), fully functional&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== BSDs ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://www.freebsd.org/ FreeBSD]&lt;br /&gt;
|12.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Contains initial POWER9 support&lt;br /&gt;
|-&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Ongoing development activity, better than releases for the time being&lt;br /&gt;
|-&lt;br /&gt;
|[https://github.com/POWER9BSD/ POWER9BSD]&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Advance POWER9 features for FreeBSD like Radix MMU, amdgpu etc&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Ports in progress===&lt;br /&gt;
Rapid progress is being made on these ports by members of the community.&lt;br /&gt;
&lt;br /&gt;
* NixOS&lt;br /&gt;
* GuixSD ([[User:Isengaara|Isengaara]])&lt;br /&gt;
* Parabola GNU/Linux-libre ([[User:Ebrasca|Ebrasca]])&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=1874</id>
		<title>Operating System Compatibility List</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=1874"/>
		<updated>2019-01-04T19:11:31Z</updated>

		<summary type="html">&lt;p&gt;Q66: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Not everything is bug-free, so you might want to the check also [[Fixes in Progress]] about the state of their upstreaming.&lt;br /&gt;
== GNU/Linux ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.adelielinux.org/ Adélie]&lt;br /&gt;
|1.0-beta1&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Needs the easy-kernel-power8 package instead of easy-kernel.  KDE 5 is stable.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;4&amp;quot;|[https://cdimage.debian.org/cdimage/ Debian]&lt;br /&gt;
|10 (2018-05-28 weekly DVD ISO)&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Only tested in KVM-PV.  Using Adélie easy-kernel as kernel, Debian Buster userland.&lt;br /&gt;
|-&lt;br /&gt;
|9.5.0&lt;br /&gt;
|ppc64le (inside KVM; machine type = pseries)&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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 &amp;lt;code&amp;gt;dpkg-query -W -f='${Section}\t${Package}\n' &amp;amp;#124; grep ^contrib&amp;lt;/code&amp;gt; (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.&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|[https://alt.fedoraproject.org/alt/ Fedora]&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|28&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|ppc64le&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|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&lt;br /&gt;
|-&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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]&lt;br /&gt;
|-&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|discontinued in Fedora 29&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://wiki.gentoo.org/wiki/Handbook:PPC64 Gentoo]&lt;br /&gt;
| n/a&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:Luke-jr|luke-jr]]&lt;br /&gt;
|Once installed, works fine.&lt;br /&gt;
|-&lt;br /&gt;
|17.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:MarcusC|MarcusC]]&lt;br /&gt;
|XFCE4 and virt-manager verified&lt;br /&gt;
|-&lt;br /&gt;
|[http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ Whonix] ([https://www.whonix.org/ clearnet link])&lt;br /&gt;
|14&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|Appears to work fine when the [[Whonix]] instructions are followed; host OS used for testing was Debian 10.&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.ubuntu.com/download/server/power Ubuntu]&lt;br /&gt;
|18.10&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:q66|q66]]&lt;br /&gt;
|Installs and works out of box with no changes, Xfce4.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== BSDs ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://www.freebsd.org/ FreeBSD]&lt;br /&gt;
|12.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Contains initial POWER9 support&lt;br /&gt;
|-&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Ongoing development activity, better than releases for the time being&lt;br /&gt;
|-&lt;br /&gt;
|[https://github.com/POWER9BSD/ POWER9BSD]&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Advance POWER9 features for FreeBSD like Radix MMU, amdgpu etc&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Ports in progress===&lt;br /&gt;
Rapid progress is being made on these ports by members of the community.&lt;br /&gt;
&lt;br /&gt;
* NixOS&lt;br /&gt;
* GuixSD ([[User:Isengaara|Isengaara]])&lt;br /&gt;
* Parabola GNU/Linux-libre ([[User:Ebrasca|Ebrasca]])&lt;br /&gt;
* Void Linux ([[User:q66|q66]]; in process of upstreaming, already fully working fork/staging distro [https://void-ppc64.octaforge.org/ here])&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=1871</id>
		<title>Operating System Compatibility List</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=1871"/>
		<updated>2018-12-19T00:59:35Z</updated>

		<summary type="html">&lt;p&gt;Q66: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Not everything is bug-free, so you might want to the check also [[Fixes in Progress]] about the state of their upstreaming.&lt;br /&gt;
== GNU/Linux ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.adelielinux.org/ Adélie]&lt;br /&gt;
|1.0-beta1&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Needs the easy-kernel-power8 package instead of easy-kernel.  KDE 5 is stable.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;4&amp;quot;|[https://cdimage.debian.org/cdimage/ Debian]&lt;br /&gt;
|10 (2018-05-28 weekly DVD ISO)&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Only tested in KVM-PV.  Using Adélie easy-kernel as kernel, Debian Buster userland.&lt;br /&gt;
|-&lt;br /&gt;
|9.5.0&lt;br /&gt;
|ppc64le (inside KVM; machine type = pseries)&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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 &amp;lt;code&amp;gt;dpkg-query -W -f='${Section}\t${Package}\n' &amp;amp;#124; grep ^contrib&amp;lt;/code&amp;gt; (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.&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|[https://alt.fedoraproject.org/alt/ Fedora]&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|28&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|ppc64le&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|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&lt;br /&gt;
|-&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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]&lt;br /&gt;
|-&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|discontinued in Fedora 29&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://wiki.gentoo.org/wiki/Handbook:PPC64 Gentoo]&lt;br /&gt;
| n/a&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:Luke-jr|luke-jr]]&lt;br /&gt;
|Once installed, works fine.&lt;br /&gt;
|-&lt;br /&gt;
|17.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:MarcusC|MarcusC]]&lt;br /&gt;
|XFCE4 and virt-manager verified&lt;br /&gt;
|-&lt;br /&gt;
|[http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ Whonix] ([https://www.whonix.org/ clearnet link])&lt;br /&gt;
|14&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|Appears to work fine when the [[Whonix]] instructions are followed; host OS used for testing was Debian 10.&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.ubuntu.com/download/server/power Ubuntu]&lt;br /&gt;
|18.10&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:q66|q66]]&lt;br /&gt;
|Installs and works out of box with no changes, Xfce4.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== BSDs ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://www.freebsd.org/ FreeBSD]&lt;br /&gt;
|12.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Contains initial POWER9 support&lt;br /&gt;
|-&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Ongoing development activity, better than releases for the time being&lt;br /&gt;
|-&lt;br /&gt;
|[https://github.com/POWER9BSD/ POWER9BSD]&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Advance POWER9 features for FreeBSD like Radix MMU, amdgpu etc&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Ports in progress===&lt;br /&gt;
Rapid progress is being made on these ports by members of the community.&lt;br /&gt;
&lt;br /&gt;
* NixOS&lt;br /&gt;
* GuixSD ([[User:Isengaara|Isengaara]])&lt;br /&gt;
* Parabola GNU/Linux-libre ([[User:Ebrasca|Ebrasca]])&lt;br /&gt;
* Void Linux ([[User:q66|q66]]; ppc64 changes currently being upstreamed, provisional unofficial binary repository up)&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Troubleshooting/GPU&amp;diff=1855</id>
		<title>Troubleshooting/GPU</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Troubleshooting/GPU&amp;diff=1855"/>
		<updated>2018-12-11T01:06:51Z</updated>

		<summary type="html">&lt;p&gt;Q66: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Troubleshooting]]&lt;br /&gt;
&lt;br /&gt;
== Background ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Common Issues ==&lt;br /&gt;
&lt;br /&gt;
=== Bootloader does not show up on monitor(s) attached to a discrete GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Alternatively, you either use a serial console or VGA monitor / adapter to interact with the bootloader.&lt;br /&gt;
&lt;br /&gt;
=== My AMD GPU works in petitboot but not the subsequent Linux OS ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If you need to use kernel 4.15 or below, you can work around this issue by either:&lt;br /&gt;
* Enabling and using the VGA video output to access the bootloader (petitboot) -or-&lt;br /&gt;
* using a serial connection to control petitboot, and running the following commands prior to selecting an operating system via the petitboot menu:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;echo 0 &amp;gt; /sys/class/vtconsole/vtcon1/bind&lt;br /&gt;
rmmod amdgpu&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== I want Petitboot via AST but the subsequent Linux OS console on a discrete GPU ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; module from loading is not sufficient on its own, you will need two kernel boot arguments:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;modprobe.blacklist=ast video=offb:off&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example on Ubuntu, this can be accomplished by changing &amp;lt;code&amp;gt;GRUB_CMDLINE_LINUX&amp;lt;/code&amp;gt; in &amp;lt;code&amp;gt;/etc/default/grub&amp;lt;/code&amp;gt; accordingly, like&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;GRUB_CMDLINE_LINUX=&amp;quot;modprobe.blacklist=ast video=offb:off&amp;quot;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and then running &amp;lt;code&amp;gt;update-grub&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Xorg will not start / crashes when a discrete GPU is installed ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;primary&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are available:&lt;br /&gt;
&lt;br /&gt;
==== Workaround 1: Disable on-board VGA====&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==== Workaround 2: Select desired GPU at runtime ====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===== Step 1: Locate Bus Numbers =====&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# lspci | grep VGA&lt;br /&gt;
0000:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100]&lt;br /&gt;
0005:02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note the numbers to the left of the &amp;quot;VGA compatible controller&amp;quot; string.  Each of these numbers is the PCI d:B:D.F&amp;lt;ref group=&amp;quot;note&amp;quot;&amp;gt;PCI Domain:Bus:Device.Function&amp;lt;/ref&amp;gt; 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.&lt;br /&gt;
&lt;br /&gt;
===== Step 2: Create Xorg Configuration Snippet =====&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# mkdir /etc/X11/xorg.conf.d&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Create and open &amp;lt;code&amp;gt;/etc/X11/xorg.conf.d/21-gpu-driver.conf&amp;lt;/code&amp;gt; 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 &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt;, 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 &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt; does; these must be stripped off when assembling the Xorg BusID.  Finally, Xorg expects to see a BusID assembled as &amp;quot;PCI:B@d:D:F&amp;quot; (note Bus and Domain are swapped), and should not be assembled not using the format shown by &amp;lt;code&amp;gt;lspci&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;# AST2500&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;GPU0&amp;quot;&lt;br /&gt;
    Driver         &amp;quot;modesetting&amp;quot;&lt;br /&gt;
    BusID          &amp;quot;PCI:2@5:0:0&amp;quot;&lt;br /&gt;
    VendorName     &amp;quot;ASpeed Corporation&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
# WX7100&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    Identifier     &amp;quot;GPU1&amp;quot;&lt;br /&gt;
    Driver         &amp;quot;amdgpu&amp;quot;&lt;br /&gt;
    BusID          &amp;quot;PCI:1@0:0:0&amp;quot;&lt;br /&gt;
    VendorName     &amp;quot;AMD Corporation&amp;quot;&lt;br /&gt;
EndSection&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;code&amp;gt;amdgpu&amp;lt;/code&amp;gt; in the example above) has been loaded:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# modprobe amdgpu&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Step 3 (optional): Disable Integrated Video =====&lt;br /&gt;
&lt;br /&gt;
If you want all Xorg output to be directed to your discrete GPU(s), you may want to disable the integrated VGA video output as much as possible.  To do this, delete the ASpeed block from your Xorg configuration snippet, and blacklist the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver.  To blacklist the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver on Debian based systems, create a new file &amp;lt;code&amp;gt;/etc/modprobe.d/ast-blacklist.conf&amp;lt;/code&amp;gt; and place the following line inside the new file:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;blacklist ast&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You may need to reboot if the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; DRM driver has already loaded.  Alternatively, you may try to unbind and unload the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver as follows (assuming the &amp;lt;code&amp;gt;ast&amp;lt;/code&amp;gt; driver is bound to vtcon0):&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;root@talos:~# echo 0 &amp;gt; /sys/class/vtconsole/vtcon0/bind&lt;br /&gt;
root@talos:~# rmmod ast&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Monitor not detected in kernel 4.17+ ===&lt;br /&gt;
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 &amp;lt;code&amp;gt;amdgpu.dc=0&amp;lt;/code&amp;gt; to the kernel parameters.  This is often associated with a host dmesg trace of&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;[drm] Cannot find any crtc or sizes&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Xorg crashes or is laggy with the AST VGA GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
In addition, on Debian Buster, GLAMOR has been observed to crash when used in conjunction with llvmpipe.&lt;br /&gt;
&lt;br /&gt;
You can disable GLAMOR by saving the following text file as &amp;lt;code&amp;gt;/usr/share/X11/xorg.conf.d/00-noglamoregl.conf&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Device&amp;quot;&lt;br /&gt;
 	Identifier &amp;quot;nogpu&amp;quot;&lt;br /&gt;
 	Driver &amp;quot;modesetting&amp;quot;&lt;br /&gt;
 	Option &amp;quot;Accelmethod&amp;quot; &amp;quot;none&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
 &lt;br /&gt;
 Section &amp;quot;Module&amp;quot;&lt;br /&gt;
 	Disable &amp;quot;glamoregl&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
This bug was probably fixed by [https://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.20-branch&amp;amp;id=1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4 commit 1e3c5d614ee33d9eac1d2cf6366feeb8341fc0f4] in upstream Xorg; it is unknown how quickly the fix will make its way to GNU/Linux distributions.&lt;br /&gt;
&lt;br /&gt;
=== KDE is laggy with the AST VGA GPU ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To fix this, go to &amp;lt;code&amp;gt;System Settings&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Hardware&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Display and Monitor&amp;lt;/code&amp;gt; → &amp;lt;code&amp;gt;Compositor&amp;lt;/code&amp;gt;, and select &amp;lt;code&amp;gt;XRender&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;Rendering backend&amp;lt;/code&amp;gt;.  You'll probably also want to select &amp;lt;code&amp;gt;Smooth (slower)&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;Scale method&amp;lt;/code&amp;gt; (it's still much faster than OpenGL, and it looks quite a bit better).&lt;br /&gt;
&lt;br /&gt;
=== AMDGPU driver crashes after firmware update ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references group=&amp;quot;note&amp;quot;/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=1854</id>
		<title>Operating System Compatibility List</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=1854"/>
		<updated>2018-12-11T00:54:32Z</updated>

		<summary type="html">&lt;p&gt;Q66: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Not everything is bug-free, so you might want to the check also [[Fixes in Progress]] about the state of their upstreaming.&lt;br /&gt;
== GNU/Linux ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.adelielinux.org/ Adélie]&lt;br /&gt;
|1.0-beta1&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Needs the easy-kernel-power8 package instead of easy-kernel.  KDE 5 is stable.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;4&amp;quot;|[https://cdimage.debian.org/cdimage/ Debian]&lt;br /&gt;
|10 (2018-05-28 weekly DVD ISO)&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Only tested in KVM-PV.  Using Adélie easy-kernel as kernel, Debian Buster userland.&lt;br /&gt;
|-&lt;br /&gt;
|9.5.0&lt;br /&gt;
|ppc64le (inside KVM; machine type = pseries)&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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 &amp;lt;code&amp;gt;dpkg-query -W -f='${Section}\t${Package}\n' &amp;amp;#124; grep ^contrib&amp;lt;/code&amp;gt; (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.&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|[https://alt.fedoraproject.org/alt/ Fedora]&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|28&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|ppc64le&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|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&lt;br /&gt;
|-&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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]&lt;br /&gt;
|-&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|discontinued in Fedora 29&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://wiki.gentoo.org/wiki/Handbook:PPC64 Gentoo]&lt;br /&gt;
| n/a&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:Luke-jr|luke-jr]]&lt;br /&gt;
|Once installed, works fine.&lt;br /&gt;
|-&lt;br /&gt;
|17.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:MarcusC|MarcusC]]&lt;br /&gt;
|XFCE4 and virt-manager verified&lt;br /&gt;
|-&lt;br /&gt;
|[http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ Whonix] ([https://www.whonix.org/ clearnet link])&lt;br /&gt;
|14&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|Appears to work fine when the [[Whonix]] instructions are followed; host OS used for testing was Debian 10.&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.ubuntu.com/download/server/power Ubuntu]&lt;br /&gt;
|18.10&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:q66|q66]]&lt;br /&gt;
|Installs and works out of box with no changes, Xfce4.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== BSDs ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://www.freebsd.org/ FreeBSD]&lt;br /&gt;
|12.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Contains initial POWER9 support&lt;br /&gt;
|-&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Ongoing development activity, better than releases for the time being&lt;br /&gt;
|-&lt;br /&gt;
|[https://github.com/POWER9BSD/ POWER9BSD]&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Advance POWER9 features for FreeBSD like Radix MMU, amdgpu etc&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Ports in progress===&lt;br /&gt;
Rapid progress is being made on these ports by members of the community.&lt;br /&gt;
&lt;br /&gt;
* NixOS&lt;br /&gt;
* GuixSD ([[User:Isengaara|Isengaara]])&lt;br /&gt;
* Parabola GNU/Linux-libre ([[User:Ebrasca|Ebrasca]])&lt;br /&gt;
* Void Linux ([[User:q66|q66]])&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=1853</id>
		<title>Operating System Compatibility List</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Operating_System_Compatibility_List&amp;diff=1853"/>
		<updated>2018-12-10T21:30:06Z</updated>

		<summary type="html">&lt;p&gt;Q66: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Not everything is bug-free, so you might want to the check also [[Fixes in Progress]] about the state of their upstreaming.&lt;br /&gt;
== GNU/Linux ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|[https://www.adelielinux.org/ Adélie]&lt;br /&gt;
|1.0-beta1&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Needs the easy-kernel-power8 package instead of easy-kernel.  KDE 5 is stable.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;4&amp;quot;|[https://cdimage.debian.org/cdimage/ Debian]&lt;br /&gt;
|10 (2018-05-28 weekly DVD ISO)&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Awilfox|awilfox]]&lt;br /&gt;
|Only tested in KVM-PV.  Using Adélie easy-kernel as kernel, Debian Buster userland.&lt;br /&gt;
|-&lt;br /&gt;
|9.5.0&lt;br /&gt;
|ppc64le (inside KVM; machine type = pseries)&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|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 &amp;lt;code&amp;gt;dpkg-query -W -f='${Section}\t${Package}\n' &amp;amp;#124; grep ^contrib&amp;lt;/code&amp;gt; (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.&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|[https://alt.fedoraproject.org/alt/ Fedora]&lt;br /&gt;
|rowspan=&amp;quot;3&amp;quot;|28&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|ppc64le&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|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&lt;br /&gt;
|-&lt;br /&gt;
|[[User:nashimus|nashimus]]&lt;br /&gt;
|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]&lt;br /&gt;
|-&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:Sharkcz|Sharkcz]]&lt;br /&gt;
|discontinued in Fedora 29&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://wiki.gentoo.org/wiki/Handbook:PPC64 Gentoo]&lt;br /&gt;
| n/a&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:Luke-jr|luke-jr]]&lt;br /&gt;
|Once installed, works fine.&lt;br /&gt;
|-&lt;br /&gt;
|17.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:MarcusC|MarcusC]]&lt;br /&gt;
|XFCE4 and virt-manager verified&lt;br /&gt;
|-&lt;br /&gt;
|[http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/ Whonix] ([https://www.whonix.org/ clearnet link])&lt;br /&gt;
|14&lt;br /&gt;
|ppc64le&lt;br /&gt;
|[[User:JeremyRand|JeremyRand]]&lt;br /&gt;
|Appears to work fine when the [[Whonix]] instructions are followed; host OS used for testing was Debian 10.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== BSDs ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Distribution&lt;br /&gt;
|Version&lt;br /&gt;
|Architecture&lt;br /&gt;
|Reported by&lt;br /&gt;
|Notes&lt;br /&gt;
|-&lt;br /&gt;
|rowspan=&amp;quot;2&amp;quot;|[https://www.freebsd.org/ FreeBSD]&lt;br /&gt;
|12.0&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Contains initial POWER9 support&lt;br /&gt;
|-&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Ongoing development activity, better than releases for the time being&lt;br /&gt;
|-&lt;br /&gt;
|[https://github.com/POWER9BSD/ POWER9BSD]&lt;br /&gt;
|13-CURRENT&lt;br /&gt;
|ppc64&lt;br /&gt;
|[[User:kev009|kev009]]&lt;br /&gt;
|Advance POWER9 features for FreeBSD like Radix MMU, amdgpu etc&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Ports in progress===&lt;br /&gt;
Rapid progress is being made on these ports by members of the community.&lt;br /&gt;
&lt;br /&gt;
* NixOS&lt;br /&gt;
* GuixSD ([[User:Isengaara|Isengaara]])&lt;br /&gt;
* Parabola GNU/Linux-libre ([[User:Ebrasca|Ebrasca]])&lt;br /&gt;
* Void Linux ([[User:q66|q66]])&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=Talos_II/Hardware_Compatibility_List&amp;diff=1841</id>
		<title>Talos II/Hardware Compatibility List</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=Talos_II/Hardware_Compatibility_List&amp;diff=1841"/>
		<updated>2018-12-09T22:33:46Z</updated>

		<summary type="html">&lt;p&gt;Q66: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a collection of components known to work with the [[Talos_II|Talos™ II]]-based solutions. It's maintained by both [[Raptor Computing Systems|Raptor CS]] and community members.&lt;br /&gt;
&lt;br /&gt;
== Cases ==&lt;br /&gt;
&lt;br /&gt;
=== Good Cases ===&lt;br /&gt;
&lt;br /&gt;
These cases were successfully used by someone.&lt;br /&gt;
&lt;br /&gt;
* '''SuperMicro SC732i-500B'''&lt;br /&gt;
** Not recommended for 12 core and higher CPUs&lt;br /&gt;
&lt;br /&gt;
* '''SuperMicro SC732D3-903B'''&lt;br /&gt;
** No NIC 2 LED on front panel&lt;br /&gt;
** Needed [https://www.startech.com/Cables/Computer-Power/Internal/12in-4-Pin-Fan-Power-Extension-Cable~FAN4EXT12 four pin extension cable] for main chassis fan&lt;br /&gt;
&lt;br /&gt;
* '''SuperMicro SC732D4-903B'''&lt;br /&gt;
** Add-on sound card recommended&lt;br /&gt;
** Add-on USB 2.0 card or USB 3.0 hub recommended&lt;br /&gt;
&lt;br /&gt;
* '''SuperMicro SC747TQ-R1400B or SC747TG-R1400B-SQ'''&lt;br /&gt;
** Hot swap drive capable; SAS recommended&lt;br /&gt;
** Recommended for use with one or more high-end GPUs&lt;br /&gt;
** Listed as EoL by Supermicro, replaced with 1620 versions. Same fan modules and PDU used in newer, higher watt, version. ([[User:Robbieab|Robbieab]] ([[User talk:Robbieab|talk]]))&lt;br /&gt;
** [[:File:TalosII_SystemAssembly_nashimus_v3.mp4|System Assembly Video - SC747TG-R1400B-SQ]]&lt;br /&gt;
&lt;br /&gt;
* '''Rosewill RSV-L4500'''&lt;br /&gt;
** Fans are two wire and use molex connectors&lt;br /&gt;
&lt;br /&gt;
* '''TCG TGC-H4-650'''&lt;br /&gt;
** Physical dimensions and mounting hardware fit perfectly&lt;br /&gt;
** Extremely Inexpensive Bare-bones 4U Chassis&lt;br /&gt;
&lt;br /&gt;
=== Problematic Cases ===&lt;br /&gt;
&lt;br /&gt;
* '''BeQuiet Dark Base 900''' ([[User:Robbieab|Robbieab]] ([[User talk:Robbieab|talk]]))&lt;br /&gt;
** Claims to support E-ATX on the BeQuiet website&lt;br /&gt;
** Infographic showing the motherboard space to only be 322mm deep, which is 8.2mm short of the full-size E-ATX. &lt;br /&gt;
** Emailed them for clarification, but no response. Can't confirm either way.&lt;br /&gt;
&lt;br /&gt;
* '''SuperMicro SC822'''&lt;br /&gt;
** Low speed fans provide insufficient airflow over CPU0, leading to overheating if more than one 4-core CPU is installed.&lt;br /&gt;
&lt;br /&gt;
* '''Athena Power RM-3U8G1043'''&lt;br /&gt;
** Some motherboard standoffs needed to be removed, and others needed additional hight.&lt;br /&gt;
**There was no standoff hole for the top right. &lt;br /&gt;
**The support beam across the top of the case interferes with CPU2 heatsink, but can be easily removed.&lt;br /&gt;
&lt;br /&gt;
==== Standoff Issues ====&lt;br /&gt;
&lt;br /&gt;
Stand off issues appear to be a very common problem. In many cases mitigation may be possible.&lt;br /&gt;
&lt;br /&gt;
* '''Fractal Design Define XL R2'''&lt;br /&gt;
** Missing standoff holes for the top-left and top-middle positions.&lt;br /&gt;
** Some alternative standoff in at least the top-middle position may be required to prevent too much bending of the motherboard while inserting RAM.&lt;br /&gt;
&lt;br /&gt;
* '''BitFenix Aurora'''&lt;br /&gt;
** [[User:MarcusC/BitFenix_Aurora|Multiple missing standoff holes]], some mitigation possible.&lt;br /&gt;
&lt;br /&gt;
* '''Thermaltake Core W100''' (See the ''[https://wiki.raptorcs.com/wiki/Category:Gallery Morgan's Revenge]'', by [[User:Peter Easton|JollyRoger]])&lt;br /&gt;
** The positions of some standoffs are under components mounted on the back of the board. Careful measurement and attachment of only the standoffs that fit prior to installation of the motherboard is ''a necessity'' to avoid damaging the motherboard upon installation.&lt;br /&gt;
** An add-on internal USB header is necessary to activate the extra 2 USB3 ports on the front panel.&lt;br /&gt;
** The case is very spacious, with plenty of room and lots of space for many fans. Works well to provide necessary airflow and pressure within the case.  &lt;br /&gt;
** It is extremely important to have a good quality, powerful fan capable of withstanding high temperatures is required for the rear exhaust fan, which is very close to the rear CPU exhaust. A low quality fan in the rear exhaust port may hinder cooling.&lt;br /&gt;
&lt;br /&gt;
* '''Thermaltake Core W200'''&lt;br /&gt;
** Heavy, expensive, massive.&lt;br /&gt;
** Compatible ''with caveats''&lt;br /&gt;
*** Talos™ II mainboard will fit in E-ATX compatible side only (when viewed from rear of case, the right side) if the dual system case.&lt;br /&gt;
*** Missing standoff holes for the top-left and top-middle positions. (non-essential but ensure proper support when inserting and removing RAM to avoid bending mainboard)&lt;br /&gt;
*** Must remove wire-hole rubber grommets present under Talos™ II mainboard on right lower side for proper fit&lt;br /&gt;
&lt;br /&gt;
* '''Nanoxia Deep Silence2''' ([[User:Sharkcz|Sharkcz]], [[User:q66|q66]])&lt;br /&gt;
** missing top-middle standoff hole, but I've used a plastic &amp;quot;flat&amp;quot; standoff instead ([[User:Sharkcz|Sharkcz]])&lt;br /&gt;
** also missing top-left standoff hole at least on earlier DS2 revisions ([[User:q66|q66]], solved by drilling holes for both top-left and top-middle without using plastic standoffs, I sent feedback to Nanoxia in late December 2016 so perhaps the top-left hole was introduced silently)&lt;br /&gt;
** all other standoff holes are present on the case&lt;br /&gt;
** Power LED - red goes to pin 15, black to pin 16&lt;br /&gt;
&lt;br /&gt;
* '''RAIJINTEK ASTERION PLUS (Model 0R200049)''' ([[User:cyrozap|cyrozap]])&lt;br /&gt;
** Missing standoff holes for the top-left and top-middle positions.&lt;br /&gt;
*** As a workaround the standoffs can be unscrewed and placed upside-down (screw threads facing up) under the motherboard holes.&lt;br /&gt;
*** This actually works surprisingly well, and thanks to the other screw points the motherboard is rigid enough that I don't worry too much about the weight of the HSFs flexing it.&lt;br /&gt;
*** That said, it's probably a good idea to always transport the system on its side and avoid bumping it if possible.&lt;br /&gt;
** The hinged panels that open with handles are much nicer than fiddling with thumb screws, but annoying since it makes it slightly trickier to do things that involve both the inside and back panel of the case (e.g., inserting PCI-e cards).&lt;br /&gt;
** The PSU is at the very bottom of the case, while all the motherboard power connectors are at the very top of the case, so this can cause some issues if your PSU's cables aren't long enough.&lt;br /&gt;
*** The EPS12V cables on my power supply had a few inches left over, but the main motherboard power cable was just barely able to reach from the other side of the case to the power connector.&lt;br /&gt;
** The front of the case is sheet metal stuck to plastic using some double-sided adhesive tape, which doesn't seem to work very well.&lt;br /&gt;
*** When I received the case the front metal was starting to peel off a few inches (several cm) at the top and bottom.&lt;br /&gt;
*** It sticks back in place when I press on it, but I may need to get some better adhesive and re-apply it later.&lt;br /&gt;
** For $170, I was hoping for something a little more robust, but at least it's pretty.&lt;br /&gt;
&lt;br /&gt;
* possible mitigation is plastic standoff like [https://www.kangyang-europe.com/product/pc-board-hardware/ass-10/ ASS-10]&lt;br /&gt;
&lt;br /&gt;
* '''Corsair 760T''' ([[User:mosst|mosst]])&lt;br /&gt;
** Reasonably cheap.&lt;br /&gt;
** Unusually tasteful aesthetics for a consumer/gaming case. Looks like something Aperture Science would come up with.&lt;br /&gt;
** E-ATX boards fit, but the top-left and top-middle standoffs are missing, however this isn't much of a problem as the I/O panel helps hold the board in place.&lt;br /&gt;
** Cable management may be difficult, as E-ATX boards cover most of the cable holes.&lt;br /&gt;
&lt;br /&gt;
* '''Lian Li PC-V1000L''' ([[User:Maxmillian|Maxmillian]] ([[User talk:Maxmillian|talk]]))&lt;br /&gt;
** Very &amp;quot;Apple&amp;quot; brushed aluminum aesthetic.&lt;br /&gt;
** E-ATX boards fit, but standoff holes for the top-left and top-middle positions are missing. There's a hole where the top-right standoff is supposed to be, but it's too big to screw in an ordinary standoff.&lt;br /&gt;
&lt;br /&gt;
=== Candidate Cases ===&lt;br /&gt;
&lt;br /&gt;
These cases claim E-ATX support and are planned to be used, or were considered, by someone.&lt;br /&gt;
&lt;br /&gt;
== Power Supplies ==&lt;br /&gt;
When planning to run with both CPU sockets populated keep in mind that the power-supply should support also 2 8-pin EPS connectors.&lt;br /&gt;
&lt;br /&gt;
* Seasonic PRIME 1300W&lt;br /&gt;
* Seasonic PRIME Ultra 850W Gold&lt;br /&gt;
* Seasonic PRIME Ultra 650W&lt;br /&gt;
* Seasonic PRIME Ultra Titanium 1000W (SSR-1000TR)&lt;br /&gt;
* FSP Group Twins ATX 1+1 Dual Module 700W 80 PLUS GOLD Hot Swappable Redundant Digital Power Supply ([[User:ebrasca|ebrasca]])&lt;br /&gt;
** Customer reported good build quality and proper functionality&lt;br /&gt;
* Corsair TX550M 80+ GOLD ([[User:MarcusC|MarcusC]])&lt;br /&gt;
** 2nd EPS power cable sold separately&lt;br /&gt;
* Corsair AX860 &lt;br /&gt;
* EVGA SuperNova 1200P2 1200W Platinum([[User:mosst|mosst]])&lt;br /&gt;
** Works well, but the included ATX power cables may be too short if your PSU is mounted on the bottom of the case.&lt;br /&gt;
* SilverStone Strider gold S series 850W ATX. 80 plus gold certification. ([[User:Xilinder|Xilinder]])&lt;br /&gt;
&lt;br /&gt;
== Memory ==&lt;br /&gt;
&lt;br /&gt;
The criteria are basically &amp;quot;is it ECC, is it registered, is it NOT LRDIMM&amp;quot;&lt;br /&gt;
&lt;br /&gt;
From the manual:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|Total Slots&lt;br /&gt;
|16 (4 channels per CPU)&lt;br /&gt;
|-&lt;br /&gt;
|Capacity&lt;br /&gt;
|2TB maximum&lt;br /&gt;
|-&lt;br /&gt;
|Memory Type&lt;br /&gt;
|DDR4 1600/1866/2133/2400/2666&lt;br /&gt;
|-&lt;br /&gt;
|Memory Features&lt;br /&gt;
|ECC&lt;br /&gt;
|-&lt;br /&gt;
|Module Sizes&lt;br /&gt;
|8GB, 16GB, 32GB, 64GB, 128GB (RDIMM)&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Tested Memory ===&lt;br /&gt;
&lt;br /&gt;
==== Good Memory ====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
!colspan=&amp;quot;6&amp;quot;|Module&lt;br /&gt;
!colspan=&amp;quot;4&amp;quot;|Validation&lt;br /&gt;
|-&lt;br /&gt;
!Manufacturer&lt;br /&gt;
!Model&lt;br /&gt;
!Size&lt;br /&gt;
!Speed&lt;br /&gt;
!Type&lt;br /&gt;
!ECC&lt;br /&gt;
!Stepping&lt;br /&gt;
!Firmware&lt;br /&gt;
!Source&lt;br /&gt;
!Notes&lt;br /&gt;
|-&lt;br /&gt;
|Pacific Sun&lt;br /&gt;
|X10723042S&lt;br /&gt;
|8GB&lt;br /&gt;
|PC4-19200&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.1&lt;br /&gt;
|Hostboot cc2d45a&lt;br /&gt;
|Official&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Hynix&lt;br /&gt;
|HMA82GR7AFR8N-UH&lt;br /&gt;
|16GB&lt;br /&gt;
|PC4-19200&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|Hostboot e36ec63&lt;br /&gt;
|Official&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Samsung&lt;br /&gt;
|M393A1G40DB0-CPB&lt;br /&gt;
|8GB&lt;br /&gt;
|PC4-17000&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|Hostboot 30dfd3b&lt;br /&gt;
|meklort&lt;br /&gt;
|Requires [[Talos_II/Firmware|System Package v1.02]]&lt;br /&gt;
|-&lt;br /&gt;
|Kingston&lt;br /&gt;
|KTH-PL424/16G&lt;br /&gt;
|16GB&lt;br /&gt;
|PC4-19200&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.1&lt;br /&gt;
|Hostboot cc2d45a&lt;br /&gt;
|Official&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Micron&lt;br /&gt;
|MTA18ASF2G72PZ-2G3B1&lt;br /&gt;
|16GB&lt;br /&gt;
|PC4-19200&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|Hostboot 28927a7&lt;br /&gt;
|Official&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Micron&lt;br /&gt;
|MTA18ASF2G72PDZ-2G3D1&lt;br /&gt;
|16GB&lt;br /&gt;
|PC4-19200&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.1&lt;br /&gt;
|Hostboot cc2d45a&lt;br /&gt;
|Official&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Micron&lt;br /&gt;
|MTA18ASF2G72PDZ-2G6D1&lt;br /&gt;
|16GB&lt;br /&gt;
|PC4-21333&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|Hostboot 884b60b&lt;br /&gt;
|[[User:Smaeul|smaeul]]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Micron&lt;br /&gt;
|MTA36ASF4G72PZ-2G6D1&lt;br /&gt;
|32GB&lt;br /&gt;
|PC4-21333&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|Hostboot 6ffaeb4&lt;br /&gt;
|[[User:cyrozap|cyrozap]]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Samsung&lt;br /&gt;
|M393A4K40BB1-CRC&lt;br /&gt;
|32GB&lt;br /&gt;
|PC4-19200&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.1&lt;br /&gt;
|Hostboot 1e2221d&lt;br /&gt;
|Official&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Samsung&lt;br /&gt;
|M393A8K40B22-CWD&lt;br /&gt;
|64GB&lt;br /&gt;
|PC4-21300&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|Hostboot 884b60b&lt;br /&gt;
|Official&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Samsung&lt;br /&gt;
|M393A2K40BB2-CTD&lt;br /&gt;
|16GB&lt;br /&gt;
|PC4-21300&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|Hostboot 0c8fa110&lt;br /&gt;
|meklort&lt;br /&gt;
|Will run at 2400MT/s with [[Talos_II/Firmware|System Package v1.00]]&lt;br /&gt;
|-&lt;br /&gt;
|Samsung&lt;br /&gt;
|M393A4K40BB2-CTD8Q&lt;br /&gt;
|32GB&lt;br /&gt;
|PC4-21333&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|Hostboot 28927a7&lt;br /&gt;
|luke-jr&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Samsung&lt;br /&gt;
|M393A2G40EB2-CTD&lt;br /&gt;
|16GB &lt;br /&gt;
|PC4-21300V-R&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|Hostboot 30dfd3b&lt;br /&gt;
|JSharp&lt;br /&gt;
|Tested extensively with [[Talos_II/Firmware|System Package v1.02]] but does boot on v1.00, Dual 8-Core POWER9, x8 DIMM Modules (RCS Recommended Slot Configuration) 128GiB total; also tested x4 DIMM Modules (RCS Recommended Slot Configuration) 64GiB total&lt;br /&gt;
|-&lt;br /&gt;
|Samsung&lt;br /&gt;
|M393A4K40CB2-CTD6Q&lt;br /&gt;
|32GB&lt;br /&gt;
|PC4-21300&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|hostboot-884b60b&lt;br /&gt;
|kev009&lt;br /&gt;
|8 DIMMs working well&lt;br /&gt;
|-&lt;br /&gt;
|Kingston&lt;br /&gt;
|KVR24R17S8K4/32&lt;br /&gt;
|8GB&lt;br /&gt;
|PC4-19200&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|1.04, PNOR d286337d&lt;br /&gt;
|sharkcz&lt;br /&gt;
| kit 4x 8GB, got 1 stick faulty, but 3x 8GB worked OK&lt;br /&gt;
|-&lt;br /&gt;
|Kingston&lt;br /&gt;
|KVR24R17D8/16MA&lt;br /&gt;
|16GB&lt;br /&gt;
|PC4-19200&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|1.04, PNOR d286337d&lt;br /&gt;
|sharkcz&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Crucial&lt;br /&gt;
|CT4G4RFS8266&lt;br /&gt;
|4GB&lt;br /&gt;
|PC4-21300&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|&lt;br /&gt;
|[[User:Robbieab|Robbieab]]&lt;br /&gt;
|Purchased as the CT2K4G4RFS8266 8GB kit. Confirmed functional from the petitboot shell.&lt;br /&gt;
|-&lt;br /&gt;
|Crucial&lt;br /&gt;
|CT8G4RFS8266&lt;br /&gt;
|8GB&lt;br /&gt;
|PC4-21300&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|CT2K8G4RFS8266 16GB kit (8GBx2). DDR4 PC4-21300 • CL=19 • Single Ranked • x8 based • Registered • ECC • DDR4-2666 • 1.2V • 1024Meg x 72. Confirmed with a working Debian GNU and Devuan GNU+Linux installation.&lt;br /&gt;
|-&lt;br /&gt;
|Ventura (Samsung)&lt;br /&gt;
|D4-62JA402SV-15&lt;br /&gt;
|16GB&lt;br /&gt;
|PC4-17000&lt;br /&gt;
|Registered&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.2&lt;br /&gt;
|&lt;br /&gt;
|mosst&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Incompatible Memory ====&lt;br /&gt;
&lt;br /&gt;
NOTE: Memory may be removed from this table after firmware support has been added, or there may be a fundamental hardware incompatibility.  If you have incompatible memory listed in the table below, you may want to bookmark and check this page from time to time to see if a firmware update has resolved the issue.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
!colspan=&amp;quot;6&amp;quot;|Module&lt;br /&gt;
!colspan=&amp;quot;4&amp;quot;|Test Conditions&lt;br /&gt;
|-&lt;br /&gt;
!Manufacturer&lt;br /&gt;
!Model&lt;br /&gt;
!Size&lt;br /&gt;
!Speed&lt;br /&gt;
!Type&lt;br /&gt;
!ECC&lt;br /&gt;
!Stepping&lt;br /&gt;
!Firmware&lt;br /&gt;
!Last Test&lt;br /&gt;
|-&lt;br /&gt;
|Samsung&lt;br /&gt;
|M386A8K40BMB-CRC&lt;br /&gt;
|64GB&lt;br /&gt;
|PC4-19200&lt;br /&gt;
|Registered LRDIMM&lt;br /&gt;
|Yes&lt;br /&gt;
|POWER9 DD2.1&lt;br /&gt;
|Hostboot 1e2221d&lt;br /&gt;
|02/14/2018&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== SAS/SATA Storage Drives ==&lt;br /&gt;
&lt;br /&gt;
Connected via optional on-board [[PM8068]] controller, or via PCIe controller. NVMe cards are also [[#NVMe Storage Drives|supported]].&lt;br /&gt;
&lt;br /&gt;
Boards with onboard SAS have one Mini-SAS HD 4i (SFF-8643) port, and four standard SATA-III ports. Both support both SAS and SATA at the electrical level.&lt;br /&gt;
&lt;br /&gt;
Note: Microsemi Adaptec Series 8 RAID controllers [http://download.adaptec.com/pdfs/readme/microsemi_series-8-controller_readme_4_2018.pdf do not support ATAPI CD-ROM, DVD, or tape devices.]&lt;br /&gt;
&lt;br /&gt;
== PCIe Devices ==&lt;br /&gt;
&lt;br /&gt;
=== Storage Controllers ===&lt;br /&gt;
&lt;br /&gt;
* IOCrest SI-PEX40062 (Chipset: Marvell 88SE9235, PCI id 1B4B:9235)&lt;br /&gt;
* Kouwell PE-115H (Chipset: Marvell 88SE9130, PCI id 1b4b:9130)&lt;br /&gt;
* LSI 9300/9200 SAS HBAs&lt;br /&gt;
** May require updating to IT firmware on a x86 machine&lt;br /&gt;
* [[PM8068]]-based SAS HBAs &lt;br /&gt;
* Supermicro AOC-SLG3-4E2P 4-port OCuLink adapter&lt;br /&gt;
* Jmicron JMB 363 SATA PCIe card. SATA ports work with Petitboot.&lt;br /&gt;
&lt;br /&gt;
==== non working ====&lt;br /&gt;
* AXAGON PCES-SA2 (ASMedia chipset)&lt;br /&gt;
&lt;br /&gt;
=== NICs ===&lt;br /&gt;
* Broadcom [[BCM5719]]&lt;br /&gt;
* Chelsio T6225-SO-CR&lt;br /&gt;
&lt;br /&gt;
=== NVMe M.2 Adapters ===&lt;br /&gt;
* [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)]&lt;br /&gt;
* [http://www.delock.com/produkte/G_89370/merkmale.html Delock PCI Express x4 Card &amp;gt; 1 x internal NVMe M.2 Key M 80 mm - Low Profile Form Factor]&lt;br /&gt;
* [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]&lt;br /&gt;
* [https://www.newegg.com/Product/Product.aspx?Item=N82E16815124167 SYBA SI-PEX40110 M.2 PCI-e To PCI-e 3.0 x4]&lt;br /&gt;
&lt;br /&gt;
==== Non-Working ====&lt;br /&gt;
&lt;br /&gt;
* [https://www.amazon.com/gp/product/B074WV4ZN4 Aplicata Quad M.2 NVMe SSD PCIe x16 Adapter] -- only recognizes lowest M.2 slot (tried in all three x16 PCIe slots).  POWER9 Sforza supports PCIe trifurcation but TalosII does not seem to.&lt;br /&gt;
&lt;br /&gt;
=== NVMe Storage Drives ===&lt;br /&gt;
* Samsung 950 PRO (with M.2 to PCIe adapter)&lt;br /&gt;
* Samsung 960 EVO / PRO (with M.2 to PCIe adapter)&lt;br /&gt;
* Samsung 970 PRO (with M.2 to PCIe adapter)&lt;br /&gt;
* Intel Optane 900P NVMe XPoint PCIe&lt;br /&gt;
* Intel Optane 905P NVMe XPoint PCIe AIC&lt;br /&gt;
* WD Black PCIe (with M.2 to PCIe adapter)&lt;br /&gt;
* MyDigitalSSD BPX 480GB (with M.2 to PCIe adapter)&lt;br /&gt;
&lt;br /&gt;
=== Graphics Cards ===&lt;br /&gt;
&lt;br /&gt;
No display?  Check out the [[Troubleshooting/GPU|GPU Troubleshooting]] page.&lt;br /&gt;
&lt;br /&gt;
==== AMD ====&lt;br /&gt;
&lt;br /&gt;
All AMD GPUs currently have DMA issues (limited to 32-bit, which can cause crashes) with the current Talos II firmware.&lt;br /&gt;
This is expected to be fixed in future firmware updates.&lt;br /&gt;
&lt;br /&gt;
* AMD Radeon HD 5850 - Must disable onboard VGA first. Currently has issues with only using 32-bit DMA.&lt;br /&gt;
* AMD Radeon HD 6850 - Disable AST VGA with jumper. 32 bit.&lt;br /&gt;
* 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.&lt;br /&gt;
* AMD Radeon HD 7950 - Must disable onboard VGA first. Currently has issues with only using 32-bit DMA.&lt;br /&gt;
* AMD Radeon R5 220&lt;br /&gt;
* AMD Radeon R5 230 - Works in BE mode (use &amp;lt;code&amp;gt;Option &amp;quot;AccelMethod&amp;quot; &amp;quot;EXA&amp;quot;&amp;lt;/code&amp;gt; for Xorg)&lt;br /&gt;
* AMD Radeon R7 240&lt;br /&gt;
* Radeon R9 290X&lt;br /&gt;
* AMD Radeon Pro WX7100 (Polaris10 core) - Available pre-installed on Talos II workstation, server, and desktop configurations.&lt;br /&gt;
* AMD Radeon Pro WX5100&lt;br /&gt;
* AMD Radeon Pro WX4100 (Polaris11 core) - May need at least linux 4.16 in order to get Xorg to work.&lt;br /&gt;
* AMD 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. &lt;br /&gt;
&lt;br /&gt;
The core name is important when storing the firmware into the BOOTKERNFW partition in PNOR for use by skiroot.&lt;br /&gt;
&lt;br /&gt;
==== NVIDIA ====&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
=== Sound Cards ===&lt;br /&gt;
&lt;br /&gt;
* Creative Sound Blaster Audigy FX SB1570 PCIe 5.1 Sound Card&lt;br /&gt;
* Creative Sound Blaster X-Fi Xtreme Fidelity PCIe Audio Sound Card (SB0880)&lt;br /&gt;
* AMD Radeon HD 5850 and 7950 (HDMI audio)&lt;br /&gt;
* [http://www.vantecusa.com/products_detail.php?p_id=156&amp;amp;p_name=+USB+Stereo+Audio+Adapter&amp;amp;pc_id=9&amp;amp;pc_name=Adapters&amp;amp;pt_id=3&amp;amp;pt_name=Audio+%2B++Video#tab-1 VANTEC NBA-120U (USB)]&lt;br /&gt;
* [http://mackie.com/products/onyx-blackjack Mackie Onyx Blackjack (USB) Recording Interface]&lt;br /&gt;
* RME HDSPe AIO (FreeBSD tested)&lt;br /&gt;
&lt;br /&gt;
=== USB controllers ===&lt;br /&gt;
* Insignia USB 3.0 PCI-e NS-PCCUP53 V1.0 (Chipset: NEC D720202)&lt;br /&gt;
* AGAXO PCEU-23R (Chipset: Renesas uPD720202, PCI id 1912:0015)&lt;br /&gt;
* Terminus Technology Inc. FE 2.1 7-port Hub&lt;br /&gt;
* [https://www.sonnettech.com/product/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)&lt;br /&gt;
&lt;br /&gt;
==== non-working ====&lt;br /&gt;
* AXAGON PCEU-43V - chipset Via VL805 - PCI id 1106:3483&lt;br /&gt;
* StarTech PEXUSB314A2V - 2x ASM1142 host controllers and a PCIe switch&lt;br /&gt;
* QNINE USB 3.1 Gen2 (Type-A and Type-C) - ASM1142&lt;br /&gt;
** It's based on the the same reference design as all the other cheap ASM1142 cards, so there's a good chance those won't work either.&lt;br /&gt;
* Ableconn PU31-2C-2 - ASM2142&lt;br /&gt;
&lt;br /&gt;
=== TV Tuners ===&lt;br /&gt;
* Hauppauge WinTV-quadHD&lt;br /&gt;
&lt;br /&gt;
== CAPI Devices ==&lt;br /&gt;
&lt;br /&gt;
* Mellanox ConnectX-6 EN 200Gb/s Adapter Card&lt;br /&gt;
&lt;br /&gt;
== Serial Adapters for J7701 Header ==&lt;br /&gt;
* [http://pinoutguide.com/Motherboard/rs232_header_pinout.shtml Pinout Details]&lt;br /&gt;
=== DTK/INTEL (compatible) ===&lt;br /&gt;
* CablesToGo 09480 (unverified)&lt;br /&gt;
* [https://www.pccables.com/DB9M-TO-IDC10-SERIAL-DTK-PORT.html DB9M TO IDC10 SERIAL DTK PORT 07121]&lt;br /&gt;
* Assmann Serial Slot Bracket AK-610300-003-E, sold under PremiumCord brand (used by [[User:Sharkcz|Sharkcz]])&lt;br /&gt;
* E-ITX ACC3100[https://www.amazon.com/dp/B00DSTTDQW/] (tested by [[User:Bdragon|Bdragon]])&lt;br /&gt;
&lt;br /&gt;
=== AT/EVEREX (not compatible) ===&lt;br /&gt;
* StarTech PLATE9M16&lt;br /&gt;
* Gigabyte COM port&lt;br /&gt;
* CablesToGo 27550 (labelled Intel-compatible, but does not work) [https://www.cablestogo.com/product/27550/16in-db9m-serial-rs232-add-a-port-adapter-cable-with-bracket-for-intel-motherboards]&lt;br /&gt;
&lt;br /&gt;
== Serial Adapters for BMC TTL Auxiliary Serial Header ==&lt;br /&gt;
* Adafruit USB to TTL Serial Cable - Debug / Console Cable for Raspberry Pi [https://www.adafruit.com/product/954]&lt;br /&gt;
&lt;br /&gt;
Unfortunately the auxiliary serial port is disabled in software by default.  To enable it temporarily for a given boot, interrupt U-Boot through the serial port in the prior section, and then enter the following commands at the '''ast#''' prompt:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
setenv fit 0x20080000&lt;br /&gt;
setenv other_rfs 0x20300000&lt;br /&gt;
setenv uart2_fdt 0x90000000&lt;br /&gt;
fdt addr ${fit}&lt;br /&gt;
fdt get addr fit_fdt /images/fdt@1 data&lt;br /&gt;
fdt move ${fit_fdt} ${uart2_fdt}&lt;br /&gt;
fdt addr ${uart2_fdt}&lt;br /&gt;
fdt resize&lt;br /&gt;
setenv pin_path &amp;quot;/ahb/apb/syscon@1e6e2000/pinctrl@1e6e2000/&amp;quot;&lt;br /&gt;
setenv phandle 80&lt;br /&gt;
for pin in txd2 rxd2 nrts2 ndtr2 ndsr2 ncts2 ndcd2 nri2&lt;br /&gt;
do&lt;br /&gt;
    fdt set ${pin_path}${pin}_default linux,phandle &amp;lt;${phandle}&amp;gt;&lt;br /&gt;
    fdt set ${pin_path}${pin}_default phandle &amp;lt;${phandle}&amp;gt;&lt;br /&gt;
    setexpr phandle ${phandle} + 1&lt;br /&gt;
done&lt;br /&gt;
setenv uart2_path &amp;quot;/ahb/apb/serial@1e78d000&amp;quot;&lt;br /&gt;
fdt set ${uart2_path} status &amp;quot;okay&amp;quot;&lt;br /&gt;
fdt set ${uart2_path} pinctrl-names &amp;quot;default&amp;quot;&lt;br /&gt;
fdt set ${uart2_path} pinctrl-0 &amp;lt;0x00000050 0x00000051 0x00000052 0x00000053 0x00000054 0x00000055 0x00000056 0x00000057&amp;gt;&lt;br /&gt;
fdt addr ${fit}&lt;br /&gt;
if fdt get value ramdisk_conf /configurations/conf@1 ramdisk&lt;br /&gt;
then&lt;br /&gt;
    bootm ${fit}#conf@1 ${fit}#conf@1 ${uart2_fdt}&lt;br /&gt;
else&lt;br /&gt;
    bootm ${fit}#conf@1 ${other_rfs} ${uart2_fdt}&lt;br /&gt;
fi&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After the system has booted, you can enable logins over the auxiliary serial port with:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
systemctl start serial-getty@ttyS1.service&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.raptorcs.com/w/index.php?title=User:Q66&amp;diff=1840</id>
		<title>User:Q66</title>
		<link rel="alternate" type="text/html" href="https://wiki.raptorcs.com/w/index.php?title=User:Q66&amp;diff=1840"/>
		<updated>2018-12-09T22:30:31Z</updated>

		<summary type="html">&lt;p&gt;Q66: Created page with &amp;quot;q66 on IRC, Samsung Open Source developer, working on Enlightenment Foundation Libraries, FreeBSD and Void Linux user, porting Void Linux to Talos&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;q66 on IRC, Samsung Open Source developer, working on Enlightenment Foundation Libraries, FreeBSD and Void Linux user, porting Void Linux to Talos&lt;/div&gt;</summary>
		<author><name>Q66</name></author>
		
	</entry>
</feed>