Differences

This shows you the differences between two versions of the page.

--- linux:rbs [2021/11/11 10:41] – [Razer Core X eGPU] mh
+++ linux:rbs [2022/01/07 09:37] (current) – [Razer Core X eGPU] mh
@@ Line 245: / Line 245: @@
 ===== Razer Core X eGPU =====
-I chose Core X over Core X Chroma when I ordered in November 2021 because the price difference between both cases was huge (220€ vs 365€) with the only benefit of an added 4 USB 3.0 ports and a 1Gbps Ethernet port. Although having those ports directly on the thunderbolt bus would be great and works well in Windows and MacOS it isn't so in Linux (as of 2020) due to a few bugs in the integration of the USB controller used in the Core X Chroma.
+=== Introduction ===
-Another argument in favor of not choosing the Core X Chroma is that I believe it is best (in Linux that is, with current state of development) to separate power and eGPU on the dedicated thunderbolt bus and use another USB 3.0 adapter for Ethernet and eventually a few added USB ports. Such adapters are worth a lot less than the 150€ price difference between Core X and Core X Chroma and should work better together, as some users have reported issues with networking and USB hubs while tunneling PCIe to take advantage of the eGPU. That being said, the Thunderbolt implementation reserves a 10Gb/s bandwith specifically for other devices than PCIe (i.e. network, USB, etc.)
+When it came to selecting an eGPU to use under Linux the Razer Core X seemed to be a great value for the money in fall 2021.
-[[https://y.tsutsumi.io/2020/08/15/egpu-linux-core-x-chroma/|Blog Post of Core X Chroma integration in Linux]]
+I chose the Core X over the Core X Chroma because the price difference was huge (220€ vs 365€) with the only benefit of an added 4 USB 3.0 ports, a 1Gbps Ethernet port and of course some LED lighting. Although having those ports directly on the thunderbolt bus would be great and works well in Windows and MacOS, people have reported issues in Linux (as of 2020) due to a few bugs in the integration of the USB controller used in the Core X Chroma.
-[[https://www.kernel.org/doc/html/latest/admin-guide/thunderbolt.html|Linux Kernel page over thunderbolt]]
+Although the Thunderbolt implementation reserves a 10Gb/s bandwith specifically for other devices than PCIe (i.e. network, USB, etc.) and the problem above might one day be solved by new patches in the Linux Kernel, there are plenty of USB 3.0 adapters/hubs that also include Gigabit Ethernet for a lot less than 150€, and the Razer Blade Stealth has 2 USB 3.0 ports available.
+=== Installing and Initializing ===
 <code bash>
@@ Line 263: / Line 265: @@
 $boltctl authorize xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx
 </code>
-//<-- Replace by the UUID of your device. Do this step only if the status is 'connected' and not 'authorized' when using 'boltctl' at previous step//
+//Replace the last argument by the UUID of your device. Do this step only if the status is 'connected' and not 'authorized' when using 'boltctl' at previous step//
 <code bash>
 $lspci
 </code>
 //The eGPU should appear in a line starting with 'VGA compatible controller [...]//
-</code>
 Install appropriate drivers for the eGPU you are tunneling through Thunderbolt.
+=== Configuring X11 ===
+You need to write an ''xorg.conf'' file to force X11 to use the eGPU. Create/Edit ''/etc/X11/xorg.conf'' and add the followin lines :
+<code bash>
+Section "Module"
+    Load "modesetting"
+EndSection
+Section "Device"
+    Identifier "Device0"
+    Driver     "nvidia"
+    BusID      "PCI:7:0:0" //Switch this to your BusID as revealed by using 'lspci' command
+    Option     "AllowEmptyInitialConfiguration"
+    Option     "AllowExternalGpus" "True"
+EndSection
+</code>
+One of the drawbacks of eGPU usage in Linux is the lack of hotplug functionnality. The above ''xorg.conf'' file must be removed or commented out after unplugging the eGPU so as to have X11 not rely on it anymore.
+=== GSwitch Project ===
+Which brings us to this simple tool developped to simplify the loading/unloading process : [[https://github.com/karli-sjoberg/gswitch|GSwitch Git Hub]]
+Simply follow the instructions to install and setup (very easy and straightforward) and it will swap from external to internal gpu using the following commands :
+<code bash>
+$sudo gswitch egpu
+$sudo gswitch internal
+</code>
+Note that the thunderbolt device has to be in ''authorized'' status for this to work, and this has to be done manually at every connection (unless you automate it).
+=== Useful Ressources ===
+[[https://egpu.io/forums/thunderbolt-linux-setup/ubuntu-19-04-easy-to-use-setup-script-for-your-egpu/|eGPU.io Forum]]
+[[https://egpu.io/forums/thunderbolt-linux-setup/a-script-to-change-xorg-config/|Another eGPU.io Forum]]
+[[https://github.com/claudio-walser/egpu-setup|Claudio Walser eGPU Setup Git Hub]]
+[[https://y.tsutsumi.io/2020/08/15/egpu-linux-core-x-chroma/|Blog Post of Core X Chroma integration in Linux]]
+[[https://www.blog.nodrama.io/razer-core-egpu-linux/|Antoher (more complete) Blog Post of Core X integration]]
+[[https://www.kernel.org/doc/html/latest/admin-guide/thunderbolt.html|Linux Kernel page over thunderbolt]]
+[[https://github.com/karli-sjoberg/gswitch|GSwitch Git Hub]]
+[[http://pocketnix.org/posts/eGPUs%20under%20Linux%3A%20an%20advanced%20guide|A 2017 dated advanced eGPU guide in Linux. Useful for in-depth tech info]]