http://together.chrisfaulkner.org/api.php?action=feedcontributions&feedformat=atom&user=CfaulknerTogether - User contributions [en]2026-07-29T11:15:02ZUser contributionsMediaWiki 1.43.1http://together.chrisfaulkner.org/index.php?title=AzerothCore_Debian_Install&diff=107AzerothCore Debian Install2019-02-14T07:12:29Z<p>Cfaulkner: /* Finishing up */</p>
<hr />
<div>This will be a HowTo on how to get AzerothCore compiled and running on Debian in a VirtualBox Setting. This should work on a Non-VM install as well. Other Debian variants like Ubuntu and LinuxMint will and should work as well. If you are running anything else, just use your best judgment on command usage.<br />
<br />
== Installing Debian ==<br />
<br />
Create a new virtual machine, I'm using the Debian 9.7.0 NetInst version using these settings as a baseline. You can tweak these for yourself but i'm going with a bare minimum just to get running. I'm going with 1GB RAM on a 20GB partition since we are not going to use a GUI, and why would you? :) After you get things setup, be sure to set the video ram to 12MB (the lowest) because we aren't using a GUI, it's not needed and we need all the ram we can get. Boot to the ISO, follow these steps to get a base system loaded:<br />
<br />
Skip the Graphical Install and go for regular "Install", go thru the screens to your liking, set the name to whatever you like, you can leave domain blank. Set your Root password. Create your regular user, we are going to set a azerothcore user later on. Set your time zone. On "Partition Disks", select "Guided - Use entire disk".. Unless you know what you're doing. All files in one partition. If you are setting up a server for a production use, you'd probably want to separate partitions and assign disk space where you want it but for the purpose of this HowTo, we are going to keep things simple. Then, Finish partitioning and write changes to disk. Now it's going to install the base system. Remember, we are going for bare minimal into a CLI (Command Line Interface). Don't be scared, this is how we do it, we don't want to waste any cycles on GUI management. Lean and Mean is what we want.<br />
<br />
On configure the package manager, choose "No" on scan another CD or DVD. Pick a close mirror and let it scan that mirror and update during "Configuring apt". Now, on to Select and install software section. Remember, we are going for lean so we only install what we are going to need. For now we are just going to install the system just so it will boot on its own so we can get to installing AzerothCore. On "Configuring popularity contest" choose what you want. <br />
<br />
Uncheck "Debian desktop environment" and "print server" and check "SSH server". This way, you can SSH in from your other computer or whatever. And leave standard system utilities" checked as well. Choose to Install the GRUB boot loader to the Master boot record.. Yes. and which drive. On Installation Complete, choose Continue. It should reboot into debian. Go ahead and login, we are ready to prepare system for AzerothCore compile.<br />
<br />
== Preparation for compile ==<br />
<br />
Go ahead and login. After you login with your user, type in "su" and enter your root password. Let's go ahead and run updates and upgrades so type in "apt update" and when it finishes, type in "apt upgrade". This is just to make sure the system is current. It should come back with 0 packages to update. <br />
<br />
<pre><br />
apt install build-essential git cmake clang default-libmysqlclient-dev libssl1.0-dev libbz2-dev libreadline-dev libncurses5-dev mysql-server libace-dev<br />
</pre><br />
<br />
== Getting and compiling the source ==<br />
<br />
First we need to clone the source:<br />
<br />
<pre><br />
cd ~<br />
mkdir source<br />
cd source<br />
git clone https://github.com/azerothcore/azerothcore-wotlk.git azerothcore<br />
</pre><br />
<br />
== Compiling the source ==<br />
<br />
Now, the moment of truth. :)<br />
<br />
<pre><br />
cd azerothcore<br />
mkdir build<br />
cd build<br />
cmake ../ -DCMAKE_INSTALL_PREFIX=/opt/azerothcore/ -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++ -DTOOLS=1 -DSCRIPTS=1<br />
make -j4<br />
make install<br />
<pre><br />
<br />
On the make -j4 command, substitute the number 4 for how many cores you have or want to use.<br />
<br />
== Finishing up ==<br />
<br />
Start with number 4 on https://github.com/AzerothCore/azerothcore-wotlk/wiki/Installation#4-setting-the-configuration-files . I may finish the entire thing, but for now this will do</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AzerothCore_Debian_Install&diff=106AzerothCore Debian Install2019-02-14T06:52:21Z<p>Cfaulkner: /* Compiling the source */</p>
<hr />
<div>This will be a HowTo on how to get AzerothCore compiled and running on Debian in a VirtualBox Setting. This should work on a Non-VM install as well. Other Debian variants like Ubuntu and LinuxMint will and should work as well. If you are running anything else, just use your best judgment on command usage.<br />
<br />
== Installing Debian ==<br />
<br />
Create a new virtual machine, I'm using the Debian 9.7.0 NetInst version using these settings as a baseline. You can tweak these for yourself but i'm going with a bare minimum just to get running. I'm going with 1GB RAM on a 20GB partition since we are not going to use a GUI, and why would you? :) After you get things setup, be sure to set the video ram to 12MB (the lowest) because we aren't using a GUI, it's not needed and we need all the ram we can get. Boot to the ISO, follow these steps to get a base system loaded:<br />
<br />
Skip the Graphical Install and go for regular "Install", go thru the screens to your liking, set the name to whatever you like, you can leave domain blank. Set your Root password. Create your regular user, we are going to set a azerothcore user later on. Set your time zone. On "Partition Disks", select "Guided - Use entire disk".. Unless you know what you're doing. All files in one partition. If you are setting up a server for a production use, you'd probably want to separate partitions and assign disk space where you want it but for the purpose of this HowTo, we are going to keep things simple. Then, Finish partitioning and write changes to disk. Now it's going to install the base system. Remember, we are going for bare minimal into a CLI (Command Line Interface). Don't be scared, this is how we do it, we don't want to waste any cycles on GUI management. Lean and Mean is what we want.<br />
<br />
On configure the package manager, choose "No" on scan another CD or DVD. Pick a close mirror and let it scan that mirror and update during "Configuring apt". Now, on to Select and install software section. Remember, we are going for lean so we only install what we are going to need. For now we are just going to install the system just so it will boot on its own so we can get to installing AzerothCore. On "Configuring popularity contest" choose what you want. <br />
<br />
Uncheck "Debian desktop environment" and "print server" and check "SSH server". This way, you can SSH in from your other computer or whatever. And leave standard system utilities" checked as well. Choose to Install the GRUB boot loader to the Master boot record.. Yes. and which drive. On Installation Complete, choose Continue. It should reboot into debian. Go ahead and login, we are ready to prepare system for AzerothCore compile.<br />
<br />
== Preparation for compile ==<br />
<br />
Go ahead and login. After you login with your user, type in "su" and enter your root password. Let's go ahead and run updates and upgrades so type in "apt update" and when it finishes, type in "apt upgrade". This is just to make sure the system is current. It should come back with 0 packages to update. <br />
<br />
<pre><br />
apt install build-essential git cmake clang default-libmysqlclient-dev libssl1.0-dev libbz2-dev libreadline-dev libncurses5-dev mysql-server libace-dev<br />
</pre><br />
<br />
== Getting and compiling the source ==<br />
<br />
First we need to clone the source:<br />
<br />
<pre><br />
cd ~<br />
mkdir source<br />
cd source<br />
git clone https://github.com/azerothcore/azerothcore-wotlk.git azerothcore<br />
</pre><br />
<br />
== Compiling the source ==<br />
<br />
Now, the moment of truth. :)<br />
<br />
<pre><br />
cd azerothcore<br />
mkdir build<br />
cd build<br />
cmake ../ -DCMAKE_INSTALL_PREFIX=/opt/azerothcore/ -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++ -DTOOLS=1 -DSCRIPTS=1<br />
make -j4<br />
make install<br />
<pre><br />
<br />
On the make -j4 command, substitute the number 4 for how many cores you have or want to use.<br />
<br />
== Finishing up ==<br />
<br />
Start with number 4 on Azeroth's Installation Instructions. I may finish the entire thing, but for now this will do</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AzerothCore_Debian_Install&diff=105AzerothCore Debian Install2019-02-14T06:38:13Z<p>Cfaulkner: /* Preparation for compile */</p>
<hr />
<div>This will be a HowTo on how to get AzerothCore compiled and running on Debian in a VirtualBox Setting. This should work on a Non-VM install as well. Other Debian variants like Ubuntu and LinuxMint will and should work as well. If you are running anything else, just use your best judgment on command usage.<br />
<br />
== Installing Debian ==<br />
<br />
Create a new virtual machine, I'm using the Debian 9.7.0 NetInst version using these settings as a baseline. You can tweak these for yourself but i'm going with a bare minimum just to get running. I'm going with 1GB RAM on a 20GB partition since we are not going to use a GUI, and why would you? :) After you get things setup, be sure to set the video ram to 12MB (the lowest) because we aren't using a GUI, it's not needed and we need all the ram we can get. Boot to the ISO, follow these steps to get a base system loaded:<br />
<br />
Skip the Graphical Install and go for regular "Install", go thru the screens to your liking, set the name to whatever you like, you can leave domain blank. Set your Root password. Create your regular user, we are going to set a azerothcore user later on. Set your time zone. On "Partition Disks", select "Guided - Use entire disk".. Unless you know what you're doing. All files in one partition. If you are setting up a server for a production use, you'd probably want to separate partitions and assign disk space where you want it but for the purpose of this HowTo, we are going to keep things simple. Then, Finish partitioning and write changes to disk. Now it's going to install the base system. Remember, we are going for bare minimal into a CLI (Command Line Interface). Don't be scared, this is how we do it, we don't want to waste any cycles on GUI management. Lean and Mean is what we want.<br />
<br />
On configure the package manager, choose "No" on scan another CD or DVD. Pick a close mirror and let it scan that mirror and update during "Configuring apt". Now, on to Select and install software section. Remember, we are going for lean so we only install what we are going to need. For now we are just going to install the system just so it will boot on its own so we can get to installing AzerothCore. On "Configuring popularity contest" choose what you want. <br />
<br />
Uncheck "Debian desktop environment" and "print server" and check "SSH server". This way, you can SSH in from your other computer or whatever. And leave standard system utilities" checked as well. Choose to Install the GRUB boot loader to the Master boot record.. Yes. and which drive. On Installation Complete, choose Continue. It should reboot into debian. Go ahead and login, we are ready to prepare system for AzerothCore compile.<br />
<br />
== Preparation for compile ==<br />
<br />
Go ahead and login. After you login with your user, type in "su" and enter your root password. Let's go ahead and run updates and upgrades so type in "apt update" and when it finishes, type in "apt upgrade". This is just to make sure the system is current. It should come back with 0 packages to update. <br />
<br />
<pre><br />
apt install build-essential git cmake clang default-libmysqlclient-dev libssl1.0-dev libbz2-dev libreadline-dev libncurses5-dev mysql-server libace-dev<br />
</pre><br />
<br />
== Getting and compiling the source ==<br />
<br />
First we need to clone the source:<br />
<br />
<pre><br />
cd ~<br />
mkdir source<br />
cd source<br />
git clone https://github.com/azerothcore/azerothcore-wotlk.git azerothcore<br />
</pre><br />
<br />
== Compiling the source ==<br />
<br />
Now, the moment of truth. :)<br />
<br />
<pre><br />
cd azerothcore<br />
mkdir build<br />
cd build<br />
cmake ../ -DCMAKE_INSTALL_PREFIX=/home/youruser/azeroth-server/ -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++ -DTOOLS=1 -DSCRIPTS=1<br />
make -j4<br />
make install<br />
<pre><br />
<br />
On the make -j4 command, substitute the number 4 for how many cores you have or want to use.<br />
<br />
== Finishing up ==<br />
<br />
Start with number 4 on Azeroth's Installation Instructions. I may finish the entire thing, but for now this will do</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AzerothCore_Debian_Install&diff=104AzerothCore Debian Install2019-02-14T06:37:28Z<p>Cfaulkner: </p>
<hr />
<div>This will be a HowTo on how to get AzerothCore compiled and running on Debian in a VirtualBox Setting. This should work on a Non-VM install as well. Other Debian variants like Ubuntu and LinuxMint will and should work as well. If you are running anything else, just use your best judgment on command usage.<br />
<br />
== Installing Debian ==<br />
<br />
Create a new virtual machine, I'm using the Debian 9.7.0 NetInst version using these settings as a baseline. You can tweak these for yourself but i'm going with a bare minimum just to get running. I'm going with 1GB RAM on a 20GB partition since we are not going to use a GUI, and why would you? :) After you get things setup, be sure to set the video ram to 12MB (the lowest) because we aren't using a GUI, it's not needed and we need all the ram we can get. Boot to the ISO, follow these steps to get a base system loaded:<br />
<br />
Skip the Graphical Install and go for regular "Install", go thru the screens to your liking, set the name to whatever you like, you can leave domain blank. Set your Root password. Create your regular user, we are going to set a azerothcore user later on. Set your time zone. On "Partition Disks", select "Guided - Use entire disk".. Unless you know what you're doing. All files in one partition. If you are setting up a server for a production use, you'd probably want to separate partitions and assign disk space where you want it but for the purpose of this HowTo, we are going to keep things simple. Then, Finish partitioning and write changes to disk. Now it's going to install the base system. Remember, we are going for bare minimal into a CLI (Command Line Interface). Don't be scared, this is how we do it, we don't want to waste any cycles on GUI management. Lean and Mean is what we want.<br />
<br />
On configure the package manager, choose "No" on scan another CD or DVD. Pick a close mirror and let it scan that mirror and update during "Configuring apt". Now, on to Select and install software section. Remember, we are going for lean so we only install what we are going to need. For now we are just going to install the system just so it will boot on its own so we can get to installing AzerothCore. On "Configuring popularity contest" choose what you want. <br />
<br />
Uncheck "Debian desktop environment" and "print server" and check "SSH server". This way, you can SSH in from your other computer or whatever. And leave standard system utilities" checked as well. Choose to Install the GRUB boot loader to the Master boot record.. Yes. and which drive. On Installation Complete, choose Continue. It should reboot into debian. Go ahead and login, we are ready to prepare system for AzerothCore compile.<br />
<br />
== Preparation for compile ==<br />
<br />
Go ahead and login. After you login with your user, type in "su" and enter your root password. Let's go ahead and run updates and upgrades so type in "apt update" and when it finishes, type in "apt upgrade". This is just to make sure the system is current. It should come back with 0 packages to update. <br />
<br />
apt install build-essential git cmake clang default-libmysqlclient-dev libssl1.0-dev libbz2-dev libreadline-dev libncurses5-dev mysql-server libace-dev <br />
<br />
== Getting and compiling the source ==<br />
<br />
First we need to clone the source:<br />
<br />
<pre><br />
cd ~<br />
mkdir source<br />
cd source<br />
git clone https://github.com/azerothcore/azerothcore-wotlk.git azerothcore<br />
</pre><br />
<br />
== Compiling the source ==<br />
<br />
Now, the moment of truth. :)<br />
<br />
<pre><br />
cd azerothcore<br />
mkdir build<br />
cd build<br />
cmake ../ -DCMAKE_INSTALL_PREFIX=/home/youruser/azeroth-server/ -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++ -DTOOLS=1 -DSCRIPTS=1<br />
make -j4<br />
make install<br />
<pre><br />
<br />
On the make -j4 command, substitute the number 4 for how many cores you have or want to use.<br />
<br />
== Finishing up ==<br />
<br />
Start with number 4 on Azeroth's Installation Instructions. I may finish the entire thing, but for now this will do</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AzerothCore_Debian_Install&diff=103AzerothCore Debian Install2019-02-13T12:56:13Z<p>Cfaulkner: </p>
<hr />
<div>This will be a HowTo on how to get AzerothCore compiled and running on Debian in a VirtualBox Setting. This should work on a Non-VM install as well. Other Debian variants like Ubuntu and LinuxMint will and should work as well. If you are running anything else, just use your best judgment on command usage.<br />
<br />
== Installing Debian ==<br />
<br />
Create a new virtual machine, I'm using the Debian 9.7.0 NetInst version using these settings as a baseline. You can tweak these for yourself but i'm going with a bare minimum just to get running. I'm going with 1GB RAM on a 20GB partition since we are not going to use a GUI, and why would you? :) After you get things setup, be sure to set the video ram to 12MB (the lowest) because we aren't using a GUI, it's not needed and we need all the ram we can get. Boot to the ISO, follow these steps to get a base system loaded:<br />
<br />
Skip the Graphical Install and go for regular "Install", go thru the screens to your liking, set the name to whatever you like, you can leave domain blank. Set your Root password. Create your regular user, we are going to set a azerothcore user later on. Set your time zone. On "Partition Disks", select "Guided - Use entire disk".. Unless you know what you're doing. All files in one partition. If you are setting up a server for a production use, you'd probably want to separate partitions and assign disk space where you want it but for the purpose of this HowTo, we are going to keep things simple. Then, Finish partitioning and write changes to disk. Now it's going to install the base system. Remember, we are going for bare minimal into a CLI (Command Line Interface). Don't be scared, this is how we do it, we don't want to waste any cycles on GUI management. Lean and Mean is what we want.<br />
<br />
On configure the package manager, choose "No" on scan another CD or DVD. Pick a close mirror and let it scan that mirror and update during "Configuring apt". Now, on to Select and install software section. Remember, we are going for lean so we only install what we are going to need. For now we are just going to install the system just so it will boot on its own so we can get to installing AzerothCore. On "Configuring popularity contest" choose what you want. <br />
<br />
Uncheck "Debian desktop environment" and "print server" and check "SSH server". This way, you can SSH in from your other computer or whatever. And leave standard system utilities" checked as well. Choose to Install the GRUB boot loader to the Master boot record.. Yes. and which drive. On Installation Complete, choose Continue. It should reboot into debian. Go ahead and login, we are ready to prepare system for AzerothCore compile.<br />
<br />
== Preparation for compile ==<br />
<br />
Go ahead and login. After you login with your user, type in "su" and enter your root password. Let's go ahead and run updates and upgrades so type in "apt update" and when it finishes, type in "apt upgrade". This is just to make sure the system is current. It should come back with 0 packages to update. <br />
<br />
apt install build-essential git cmake clang default-libmysqlclient-dev libssl1.0-dev libbz2-dev libreadline-dev libncurses-dev mysql-server libace</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AzerothCore_Debian_Install&diff=102AzerothCore Debian Install2019-02-13T12:18:21Z<p>Cfaulkner: </p>
<hr />
<div>This will be a HowTo on how to get AzerothCore compiled and running on Debian in a VirtualBox Setting. This should work on a Non-VM install as well. Other Debian variants like Ubuntu and LinuxMint will and should work as well. If you are running anything else, just use your best judgment on command usage.<br />
<br />
== Installing Debian ==<br />
<br />
Create a new virtual machine, I'm using the Debian 9.7.0 NetInst version using these settings as a baseline. You can tweak these for yourself but i'm going with a bare minimum just to get running. I'm going with 1GB RAM on a 20GB partition since we are not going to use a GUI, and why would you? :) After you get things setup, be sure to set the video ram to 12MB (the lowest) because we aren't using a GUI, it's not needed and we need all the ram we can get. Boot to the ISO, follow these steps to get a base system loaded:<br />
<br />
Skip the Graphical Install and go for regular "Install", go thru the screens to your liking, set the name to whatever you like, you can leave domain blank. Set your Root password. Create your regular user, we are going to set a azerothcore user later on. Set your time zone. On "Partition Disks", select "Guided - Use entire disk".. Unless you know what you're doing. All files in one partition. If you are setting up a server for a production use, you'd probably want to separate partitions and assign disk space where you want it but for the purpose of this HowTo, we are going to keep things simple. Then, Finish partitioning and write changes to disk. Now it's going to install the base system. Remember, we are going for bare minimal into a CLI (Command Line Interface). Don't be scared, this is how we do it, we don't want to waste any cycles on GUI management. Lean and Mean is what we want.<br />
<br />
On configure the package manager, choose "No" on scan another CD or DVD. Pick a close mirror and let it scan that mirror and update during "Configuring apt". Now, on to Select and install software section. Remember, we are going for lean so we only install what we are going to need. For now we are just going to install the system just so it will boot on its own so we can get to installing AzerothCore. On "Configuring popularity contest" choose what you want. <br />
<br />
Uncheck "Debian desktop environment" and "print server" and check "SSH server". This way, you can SSH in from your other computer or whatever. And leave standard system utilities" checked as well.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AzerothCore_Debian_Install&diff=101AzerothCore Debian Install2019-02-13T12:02:22Z<p>Cfaulkner: </p>
<hr />
<div>This will be a HowTo on how to get AzerothCore compiled and running on Debian in a VirtualBox Setting. This should work on a Non-VM install as well. Other Debian variants like Ubuntu and LinuxMint will and should work as well. If you are running anything else, just use your best judgment on command usage.<br />
<br />
== Installing Debian ==<br />
<br />
Create a new virtual machine, I'm using the Debian 9.7.0 NetInst version using these settings as a baseline. You can tweak these for yourself but i'm going with a bare minimum just to get running. I'm going with 1GB RAM on a 20GB partition since we are not going to use a GUI, and why would you? :) After you get things setup, be sure to set the video ram to 12MB (the lowest) because we aren't using a GUI, it's not needed and we need all the ram we can get. Boot to the ISO, follow these steps to get a base system loaded:<br />
<br />
Skip the Graphical Install and go for regular "Install", go thru the screens to your liking, set the name to whatever you like, you can leave domain blank. Set your Root password. Create your regular user, we are going to set a azerothcore user later on. Set your time zone. On "Partition Disks", select "Guided - Use entire disk".. Unless you know what you're doing. All files in one partition. If you are setting up a server for a production use, you'd probably want to separate partitions and assign disk space where you want it but for the purpose of this HowTo, we are going to keep things simple. Then, Finish partitioning and write changes to disk. Now it's going to install the base system. Remember, we are going for bare minimal into a CLI (Command Line Interface). Don't be scared, this is how we do it, we don't want to waste any cycles on GUI management. Lean and Mean is what we want.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AzerothCore_Debian_Install&diff=100AzerothCore Debian Install2019-02-13T11:53:24Z<p>Cfaulkner: </p>
<hr />
<div>This will be a HowTo on how to get AzerothCore compiled and running on Debian in a VirtualBox Setting. This should work on a Non-VM install as well. Other Debian variants like Ubuntu and LinuxMint will and should work as well. If you are running anything else, just use your best judgment on command usage.<br />
<br />
== Installing Debian ==<br />
<br />
Create a new virtual machine, I'm using the Debian 9.7.0 NetInst version using these settings as a baseline. You can tweak these for yourself but i'm going with a bare minimum just to get running. I'm going with 1GB RAM on a 20GB partition since we are not going to use a GUI, and why would you? :) After you get things setup, be sure to set the video ram to 12MB (the lowest) because we aren't using a GUI, it's not needed and we need all the ram we can get. Boot to the ISO, follow these steps to get a base system loaded:<br />
<br />
Skip the Graphical Install and go for regular "Install", go thru the screens to your liking, set the name to whatever you like, you can leave domain blank. Set your Root password. Create your regular user, we are going to set a azerothcore user later on. Set your time zone. On "Partition Disks", select "Guided - Use entire disk".. Unless you know what you're doing. All files in one partition. If you are setting up a server for a production use, you'd probably want to separate partitions and assign disk space where you want it but for the purpose of this HowTo, we are going to keep things simple. Then, Finish partitioning and write changes to disk.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AzerothCore_Debian_Install&diff=99AzerothCore Debian Install2019-02-13T11:39:47Z<p>Cfaulkner: </p>
<hr />
<div>This will be a HowTo on how to get AzerothCore compiled and running on Debian in a VirtualBox Setting. This should work on a Non-VM install as well. Other Debian variants like Ubuntu and LinuxMint will and should work as well. If you are running anything else, just use your best judgment on command usage.<br />
<br />
== Installing Debian ==<br />
<br />
Create a new virtual machine, I'm using the Debian 9.7.0 NetInst version using these settings as a baseline. You can tweak these for yourself but i'm going with a bare minimum just to get running. I'm going with 1GB RAM on a 20GB partition since we are not going to use a GUI, and why would you? :) After you get things setup, be sure to set the video ram to 12MB (the lowest) because we aren't using a GUI, it's not needed and we need all the ram we can get. Boot to the ISO</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AzerothCore_Debian_Install&diff=98AzerothCore Debian Install2019-02-13T11:38:22Z<p>Cfaulkner: Created page with "This will be a HowTo on how to get AzerothCore compiled and running on Debian in a VirtualBox Setting. This should work on a Non-VM install as well. == Installing Debian ==..."</p>
<hr />
<div>This will be a HowTo on how to get AzerothCore compiled and running on Debian in a VirtualBox Setting. This should work on a Non-VM install as well.<br />
<br />
== Installing Debian ==<br />
<br />
Create a new virtual machine, I'm using the Debian 9.7.0 NetInst version using these settings as a baseline. You can tweak these for yourself but i'm going with a bare minimum just to get running. I'm going with 1GB RAM on a 20GB partition since we are not going to use a GUI, and why would you? :) After you get things setup, be sure to set the video ram to 12MB (the lowest) because we aren't using a GUI, it's not needed and we need all the ram we can get. Boot to the ISO</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=97AMDGPU-PRO Gentoo Install2018-12-22T12:24:40Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
#First of all, make sure that in /etc/portage/make.conf you have the line '''''VIDEO_CARDS="amdgpu radeonsi"'''''<br />
#Edit the file /etc/portage/package.mask and add the lines<br><br />
#Mask old version of packages for AMDGPU-PRO<br /><sys-kernel/gentoo-sources-4.9.0<br />>=sys-kernel/gentoo-sources-4.11.0<br />x11-drivers/amdgpu-pro::farmboy0<br><br />
#Then, update your system: '''''emerge --update --deep --newuse -1 world'''''<br />
#When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed): '''''emerge linux-firmware'''''<br />
#Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
<pre><br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
</pre><br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=96AMDGPU-PRO Gentoo Install2018-12-22T12:23:20Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
#First of all, make sure that in /etc/portage/make.conf you have the line '''''VIDEO_CARDS="amdgpu radeonsi"'''''<br />
#Edit the file /etc/portage/package.mask and add the lines<br />
<pre>#Mask old version of packages for AMDGPU-PRO<br /><sys-kernel/gentoo-sources-4.9.0<br />>=sys-kernel/gentoo-sources-4.11.0<br />x11-drivers/amdgpu-pro::farmboy0</pre><br />
#Then, update your system: '''''emerge --update --deep --newuse -1 world'''''<br />
#When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed): '''''emerge linux-firmware'''''<br />
#Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
<pre><br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
</pre><br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=95AMDGPU-PRO Gentoo Install2018-12-22T12:22:44Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
#First of all, make sure that in /etc/portage/make.conf you have the line '''''VIDEO_CARDS="amdgpu radeonsi"'''''<br />
#Edit the file /etc/portage/package.mask and add the lines<br />
<pre>#Mask old version of packages for AMDGPU-PRO<br><sys-kernel/gentoo-sources-4.9.0<br>>=sys-kernel/gentoo-sources-4.11.0<br>x11-drivers/amdgpu-pro::farmboy0</pre><br />
#Then, update your system: '''''emerge --update --deep --newuse -1 world'''''<br />
#When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed): '''''emerge linux-firmware'''''<br />
#Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
<pre><br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
</pre><br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=94AMDGPU-PRO Gentoo Install2018-12-22T12:22:08Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
#First of all, make sure that in /etc/portage/make.conf you have the line '''''VIDEO_CARDS="amdgpu radeonsi"'''''<br />
#Edit the file /etc/portage/package.mask and add the lines<pre>#Mask old version of packages for AMDGPU-PRO<br><sys-kernel/gentoo-sources-4.9.0<br>>=sys-kernel/gentoo-sources-4.11.0<br>x11-drivers/amdgpu-pro::farmboy0</pre><br />
#Then, update your system: '''''emerge --update --deep --newuse -1 world'''''<br />
#When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed): '''''emerge linux-firmware'''''<br />
#Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
<pre><br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
</pre><br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=93AMDGPU-PRO Gentoo Install2018-12-22T12:21:15Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
#First of all, make sure that in /etc/portage/make.conf you have the line '''''VIDEO_CARDS="amdgpu radeonsi"'''''<br />
#Edit the file /etc/portage/package.mask and add the lines<br />
##<pre>#Mask old version of packages for AMDGPU-PRO<br />
<sys-kernel/gentoo-sources-4.9.0<br />
>=sys-kernel/gentoo-sources-4.11.0<br />
x11-drivers/amdgpu-pro::farmboy0<br />
</pre><br />
#Then, update your system: '''''emerge --update --deep --newuse -1 world'''''<br />
#When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed): '''''emerge linux-firmware'''''<br />
#Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
<pre><br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
</pre><br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=92AMDGPU-PRO Gentoo Install2018-12-22T12:19:55Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
#First of all, make sure that in /etc/portage/make.conf you have the line '''''VIDEO_CARDS="amdgpu radeonsi"'''''<br />
#Edit the file /etc/portage/package.mask and add the lines<br />
<code>#Mask old version of packages for AMDGPU-PRO<br />
<sys-kernel/gentoo-sources-4.9.0<br />
>=sys-kernel/gentoo-sources-4.11.0<br />
x11-drivers/amdgpu-pro::farmboy0<br />
</code><br />
#Then, update your system: '''''emerge --update --deep --newuse -1 world'''''<br />
#When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed): '''''emerge linux-firmware'''''<br />
#Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
<pre><br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
</pre><br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=91AMDGPU-PRO Gentoo Install2018-12-22T12:18:47Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
#First of all, make sure that in /etc/portage/make.conf you have the line '''''VIDEO_CARDS="amdgpu radeonsi"'''''<br />
<br />
#Edit the file /etc/portage/package.mask and add the lines<br />
<pre>#Mask old version of packages for AMDGPU-PRO<br />
<sys-kernel/gentoo-sources-4.9.0<br />
>=sys-kernel/gentoo-sources-4.11.0<br />
x11-drivers/amdgpu-pro::farmboy0<br />
</pre><br />
#Then, update your system: '''''emerge --update --deep --newuse -1 world'''''<br />
#When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed): '''''emerge linux-firmware'''''<br />
#Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
<pre><br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
</pre><br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=90AMDGPU-PRO Gentoo Install2018-12-22T12:18:04Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
#First of all, make sure that in /etc/portage/make.conf you have the line '''''VIDEO_CARDS="amdgpu radeonsi"'''''<br />
<br />
#Edit the file /etc/portage/package.mask and add the lines<br />
<pre>[[Wikipedia:Number_sign|number sign]]Mask old version of packages for AMDGPU-PRO<br />
<sys-kernel/gentoo-sources-4.9.0<br />
>=sys-kernel/gentoo-sources-4.11.0<br />
x11-drivers/amdgpu-pro::farmboy0<br />
</pre><br />
#Then, update your system: '''''emerge --update --deep --newuse -1 world'''''<br />
#When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed): '''''emerge linux-firmware'''''<br />
#Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
<pre><br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
</pre><br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=89AMDGPU-PRO Gentoo Install2018-12-22T12:16:03Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
#First of all, make sure that in /etc/portage/make.conf you have the line '''''VIDEO_CARDS="amdgpu radeonsi"'''''<br />
<br />
2. Edit the file /etc/portage/package.mask and add the lines<br />
# Mask old version of packages for AMDGPU-PRO<br />
<sys-kernel/gentoo-sources-4.9.0<br />
>=sys-kernel/gentoo-sources-4.11.0<br />
x11-drivers/amdgpu-pro::farmboy0<br />
<br />
3. Then, update your system:<br />
emerge --update --deep --newuse -1 world<br />
<br />
4. When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed):<br />
emerge linux-firmware<br />
<br />
5. Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
<pre><br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
</pre><br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=88AMDGPU-PRO Gentoo Install2018-12-22T12:15:29Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
#First of all, make sure that in /etc/portage/make.conf you have the line ''VIDEO_CARDS="amdgpu radeonsi"''<br />
<br />
2. Edit the file /etc/portage/package.mask and add the lines<br />
# Mask old version of packages for AMDGPU-PRO<br />
<sys-kernel/gentoo-sources-4.9.0<br />
>=sys-kernel/gentoo-sources-4.11.0<br />
x11-drivers/amdgpu-pro::farmboy0<br />
<br />
3. Then, update your system:<br />
emerge --update --deep --newuse -1 world<br />
<br />
4. When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed):<br />
emerge linux-firmware<br />
<br />
5. Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
<pre><br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
</pre><br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=87AMDGPU-PRO Gentoo Install2018-12-22T12:13:21Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
1. First of all, make sure that in /etc/portage/make.conf you have the line<br />
VIDEO_CARDS="amdgpu radeonsi"<br />
<br />
2. Edit the file /etc/portage/package.mask and add the lines<br />
# Mask old version of packages for AMDGPU-PRO<br />
<sys-kernel/gentoo-sources-4.9.0<br />
>=sys-kernel/gentoo-sources-4.11.0<br />
x11-drivers/amdgpu-pro::farmboy0<br />
<br />
3. Then, update your system:<br />
emerge --update --deep --newuse -1 world<br />
<br />
4. When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed):<br />
emerge linux-firmware<br />
<br />
5. Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
<pre><br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
</pre><br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=86AMDGPU-PRO Gentoo Install2018-12-22T12:11:58Z<p>Cfaulkner: </p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
''Note: this page was copied from the Warwick site that is no longer available. I'm going to try to maintain this to keep it going in case anyone wants the closed-source drivers.''<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
1. First of all, make sure that in /etc/portage/make.conf you have the line<br />
VIDEO_CARDS="amdgpu radeonsi"<br />
<br />
2. Edit the file /etc/portage/package.mask and add the lines<br />
# Mask old version of packages for AMDGPU-PRO<br />
<sys-kernel/gentoo-sources-4.9.0<br />
>=sys-kernel/gentoo-sources-4.11.0<br />
x11-drivers/amdgpu-pro::farmboy0<br />
<br />
3. Then, update your system:<br />
emerge --update --deep --newuse -1 world<br />
<br />
4. When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed):<br />
emerge linux-firmware<br />
<br />
5. Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=AMDGPU-PRO_Gentoo_Install&diff=85AMDGPU-PRO Gentoo Install2018-12-22T12:10:44Z<p>Cfaulkner: Created page with " =AMDGPU-PRO driver guide for Gentoo= NOTE: This page is no longer maintained. I currently have no AMD cards that are supported by the proprietary driver and for which I need..."</p>
<hr />
<div><br />
=AMDGPU-PRO driver guide for Gentoo=<br />
<br />
NOTE: This page is no longer maintained. I currently have no AMD cards that are supported by the proprietary driver and for which I need to use it. I do not know whether, in the future, the situation will change. If so, I may try to keep updating the ebuilds and patches. I am leaving the instructions below for reference, should they be of use to anyone.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
The following is a short guide to install the proprietary AMDGPU-PRO driver in Gentoo linux.<br />
<br />
This driver seems to produce a good increase of performance on older workstation cards (GCN1), but, perhaps more importantly, it introduces support for Raven Ridge. Also, it supports hybrid configurations, including the latest RX500 series.<br />
<br />
In the following, I assume you know how to maintain your system, change keywords on a package basis, etc. Needless to say, you need to be root for all these steps. Before the actual steps, a few notes:<br />
- This guide is for driver version 17.40.492261. I know that there is a newer driver, but it requires at least version 1.0.65 of vulkan-loader, which, at the moment, is not available in Portage.<br />
- The steps below assume you are making a new installation. If, instead, you are updating from a previous version of the same driver, you should simply install the new ebuild and proceed as for a normal system update (including of course unmasking its keyword, potentially recompiling the kernel and building the new dkms module).<br />
- During the installation of the driver or later, during a normal system update, it is possible to get compilation errors with libtool complaining about gbm-related stuff. This is a known problem due to libtool getting confused during the link stage, and it happens in exactly the same way for users of the proprietary nVidia driver. Typically the error will occur while compiling mesa or cairo, but it may happen when building other packages as well. The workaround is to run "eselect opengl xorg-x11", then emerge the package that was failing, then run "eselect opengl amdgpu-pro", and finally continue whatever you were doing before.<br />
- The ebuild also works for hybrid configurations, such as new laptops with an integrated Intel card and a discrete AMD one. For such cases, make sure you activate the "hybrid" USE flag and take care of the necessary changes, explained below.<br />
- For hybrid configurations, in step 1, ensure that the VIDEO_CARDS variable includes the values needed for the integrated card. For example, if you have a laptop with an Intel Core i7 8550U, you will need VIDEO_CARDS="amdgpu radeonsi intel i965". To know what values to use, please refer to the relevant guide.<br />
- In step 5, make sure to specify the right spare region number for the MTRR in CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT. In the instructions, I used the value 2, but this may be different for your card. You can check the right region by running cat /proc/mtrr. Also, the CONFIG_EXTRA_FIRMWARE line is a correct example for an RX480 card. If your card is a different model, you must replace the file names with the appropriate firmware files. To find which firmware files to include, check the list here. However, note that the cards mentioned at this link are all desktop cards. If you are setting up a workstation or a laptop, you can check the type of microarchitecture of your card here and then refer to the previous list, considering that the driver works on cards starting from GCN first generation. Also, if your card is a Southern Islands or a Sea Islands card, then you must also have CONFIG_DRM_AMDGPU_SI=y or CONFIG_DRM_AMDGPU_CIK=y, respectively.<br />
- The ebuild assumes that the PCI bus of the card is 1:0:0. If this is not the case for your card, after step 7 is complete you must modify the file /etc/X11/xorg.conf.d/10-device.conf and replace the BusID value with the right one, which you can find using lspci. Also, optionally, you can modify the various identifiers in the same file as well as in /etc/X11/xorg.conf.d/10-monitor.conf and /etc/X11/xorg.conf.d/10-screen.conf to match those of your hardware (this has no effect whatsoever on the functioning of your card). Note that this step is not needed if you have a hybrid configuration; in fact, in this case, these files will not even be created.<br />
<br />
<br />
<br />
<br />
<br />
Now, the actual step-by-step guide.<br />
<br />
1. First of all, make sure that in /etc/portage/make.conf you have the line<br />
VIDEO_CARDS="amdgpu radeonsi"<br />
<br />
2. Edit the file /etc/portage/package.mask and add the lines<br />
# Mask old version of packages for AMDGPU-PRO<br />
<sys-kernel/gentoo-sources-4.9.0<br />
>=sys-kernel/gentoo-sources-4.11.0<br />
x11-drivers/amdgpu-pro::farmboy0<br />
<br />
3. Then, update your system:<br />
emerge --update --deep --newuse -1 world<br />
<br />
4. When the system is properly updated, and any rebuilding and fixing is done, install the firmware package (if it is not already installed):<br />
emerge linux-firmware<br />
<br />
5. Next step is making sure the kernel has the right configuration. Note that you must ensure that you are running a 4.9 kernel, which may mean you must manually accept its keyword. At the moment, I tested it with the latest available kernel of the series, which is the 4.9.85, and which I use in the instructions below. In the kernel configuration, verify that the following options are as shown (please note that some must be modules):<br />
CONFIG_MTRR = y<br />
# CONFIG_TRIM_UNUSED_KSYMS is not set<br />
CONFIG_MTRR_SANITIZER = y<br />
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT = 1<br />
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT = 2<br />
CONFIG_BINFMT_ELF=y<br />
CONFIG_COMPAT_BINFMT_ELF=y<br />
CONFIG_BINFMT_SCRIPT=y<br />
CONFIG_BINFMT_MISC=y<br />
CONFIG_FW_LOADER = y<br />
CONFIG_FIRMWARE_IN_KERNEL = y<br />
CONFIG_EXTRA_FIRMWARE = "amdgpu/polaris10_ce.bin amdgpu/polaris10_mc.bin amdgpu/polaris10_me.bin amdgpu/polaris10_mec2.bin amdgpu/polaris10_mec.bin amdgpu/polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin"<br />
CONFIG_EXTRA_FIRMWARE_DIR = "/lib/firmware"<br />
CONFIG_AGP = y<br />
CONFIG_VGA_SWITCHEROO = y<br />
CONFIG_DRM = y<br />
CONFIG_DRM_FBDEV_EMULATION = y<br />
CONFIG_DRM_AMDGPU = m<br />
CONFIG_DRM_AMDGPU_USERPTR = y<br />
CONFIG_FB = y<br />
CONFIG_FB_MODE_HELPERS = y<br />
CONFIG_FB_VESA = y<br />
# CONFIG_DRM_RADEON is not set<br />
# CONFIG_FB_RADEON is not set<br />
DEBUG_KERNEL = n<br />
<br />
If needed, recompile the kernel and make sure modules, firmware and system map are installed:<br />
make<br />
make modules_install<br />
make firmware_install<br />
cp arch/x86/boot/bzImage /boot/kernel<br />
cp System.map /boot/System.map-4.9.85-gentoo<br />
<br />
Reboot into the new kernel.<br />
<br />
6. Next, install dkms. The easiest way is to use the farmboy0 overlay. Emerge layman (if it is not already installed), then do<br />
layman -a farmboy0<br />
layman -S<br />
emerge dkms<br />
<br />
7. Create a local overlay. I call mine parawlay. If you don't know how to do this, see here or here. Inside the overlay, create the category "x11-drivers", and inside this the directory "amdgpu-pro". Then, downoad this ebuild and put it inside this directory. Create the manifest:<br />
ebuild amdgpu-pro-17.40.492261-r2.ebuild manifest<br />
Install the various driver components:<br />
emerge amdgpu-pro<br />
Of course, you can choose whatever use flags you want/need, they are self-explanatory.<br />
<br />
8. Now, create a directory in which you are going to extract the dkms code, patch it and compile it. For example:<br />
mkdir amdgpupro-17.40.492261_4.9.85<br />
Go there, copy the source in it, extract it and go to the directory with the source code:<br />
cd amdgpupro-17.40.492261_4.9.85<br />
cp /usr/portage/distfiles/amdgpu-pro-17.40-492261.tar.xz .<br />
tar xJf amdgpu-pro-17.40-492261.tar.xz<br />
rm amdgpu-pro-17.40-492261.tar.xz<br />
cd amdgpu-pro-17.40-492261/<br />
ar x amdgpu-pro-dkms_17.40-492261_all.deb<br />
tar xJf data.tar.xz<br />
rm *<br />
cd usr/src/<br />
Inside this directory you have the code for the module, which needs to be patched. To do so, download these patches and extract them where you are. Then, patch the code:<br />
cd amdgpu-17.40-492261/<br />
for i in `seq 1 1 11`; do patch -p0 < ../patch${i}; done<br />
cd ..<br />
If (and only if) you are currently running an old version of the proprietary drive module, uninstall it. For example, if you are running the old driver version 17.10-401251, do<br />
dkms remove amdgpu-pro/17.10-401251 --all<br />
Then, install the new driver:<br />
dkms install amdgpu-17.40-492261 -k 4.9.85-gentoo --force<br />
<br />
9. Run<br />
eselect opengl amdgpu-pro<br />
eselect opencl amdgpu-pro<br />
<br />
10. Finally, if you intend to use the card for cryptocurrency mining, edit the file /etc/grub.d/40_custom and add the option amdgpu.vm_fragment_size=9 in the kernel line, and rebuild the grub config file (typically running grub-mkconfig -o /boot/grub/grub.cfg). Do not perform this step if you will use the card for regular gaming/rendering/computing jobs.<br />
<br />
<br />
Reboot and you are done. In general, update and maintain your system (and overlays) as usual. However, if you recompile the kernel, you will need to reinstall the dkms module. Whenever a new version of the driver is released or there is some change in something, and I have time, I will update the guide.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=WotLK_3.3.5a_client_in_WINE&diff=84WotLK 3.3.5a client in WINE2018-12-22T11:59:49Z<p>Cfaulkner: </p>
<hr />
<div>'''WotLK 3.3.5a Client in Linux'''<br />
<br />
==Download the client==<br />
There are several sites out there that have torrents running for the 3.3.5a client which most WotLK servers run. The one that I play is on www.warmane.com and they also have a few patches you can put in the data directory for extra models and such. I'd suggest that one as I've had no issues running it in Wine.<br />
== Installing Wine ==<br />
Be sure to check with your distros install. I use Gentoo so just doing "emerge wine-staging" did it for me. Make sure you are running wine-staging and vanilla-wine or any other version will not work. Be sure to install winetricks as well.<br />
===Configuring Wine===<br />
I'm running my instance in 32-bit mode on my Multilib 32/64 bit system. Your mileage may vary. I was running in 64 bit mode, but switched to 32-bit mode for compatibility and it seems to run better. First thing you want to do is create a directory off your home directory. Do all this as a user and not as root.<br />
<pre><br />
cd ~<br />
mkdir WineWoW<br />
WINEARCH=win32 WINEPREFIX=~/WineWoW winetricks d3dx9_43 d3dx10_43 d3dx11_43<br />
</pre><br />
<br />
This will install DirectX 9,10 and 11<br />
<br />
Now we go into winecfg<br />
<br />
<pre><br />
WINEARCH=win32 WINEPREFIX=~/WineWoW winecfg<br />
</pre><br />
<br />
Make sure it says Windows 7 and OK out of winecfg<br />
<br />
==Running WoW==<br />
<br />
Be sure to copy the game client files to ~/WineWoW/drive_c/Program Files/, then goto ~/WineWoW/drive_c/Program Files/WoW and type WINEARCH=win32 WINEPREFIX=~/WineWoW wine WoW.exe<br />
<br />
===Installing Lutris===<br />
On the other hand, you can do what I do and install Lutris, according to your distro package system. Install game manually. Make sure you specify WINEARCH and WINEPREFIX and most things set as default.</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=WotLK_3.3.5a_client_in_WINE&diff=83WotLK 3.3.5a client in WINE2018-12-22T11:59:20Z<p>Cfaulkner: </p>
<hr />
<div>'''WotLK 3.3.5a Client in Linux'''<br />
<br />
==Download the client==<br />
There are several sites out there that have torrents running for the 3.3.5a client which most WotLK servers run. The one that I play is on www.warmane.com and they also have a few patches you can put in the data directory for extra models and such. I'd suggest that one as I've had no issues running it in Wine.<br />
== Installing Wine ==<br />
Be sure to check with your distros install. I use Gentoo so just doing "emerge wine-staging" did it for me. Make sure you are running wine-staging and vanilla-wine or any other version will not work. Be sure to install winetricks as well.<br />
===Configuring Wine===<br />
I'm running my instance in 32-bit mode on my Multilib 32/64 bit system. Your mileage may vary. I was running in 64 bit mode, but switched to 32-bit mode for compatibility and it seems to run better. First thing you want to do is create a directory off your home directory. Do all this as a user and not as root.<br />
<pre><br />
cd ~<br />
mkdir WineWoW<br />
WINEARCH=win32 WINEPREFIX=~/WineWoW winetricks d3dx9_43 d3dx10_43 d3dx11_43<br />
</pre><br />
<br />
This will install DirectX 9,10 and 11<br />
<br />
Now we go into winecfg<br />
<br />
<pre><br />
WINEARCH=win32 WINEPREFIX=~/WineWoW winecfg<br />
</pre><br />
<br />
Make sure it says Windows 7 and OK out of winecfg<br />
<br />
==Running WoW==<br />
<br />
Be sure to copy the game client files to ~/WineWoW/drive_c/Program Files/, then goto ~/WineWoW/drive_c/Program Files/WoW and type WINEARCH=win32 WINEPREFIX=~/WineWoW wine WoW.exe<br />
<br />
===Installing Lutris===<br />
On the other hand, you can do what I do and install Lutris, according to your distro package system. Install game manually. Make sure you specify WINEARCH and WINE</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=WotLK_3.3.5a_client_in_WINE&diff=82WotLK 3.3.5a client in WINE2018-12-22T11:48:37Z<p>Cfaulkner: </p>
<hr />
<div>'''WotLK 3.3.5a Client in Linux'''<br />
<br />
==Download the client==<br />
There are several sites out there that have torrents running for the 3.3.5a client which most WotLK servers run. The one that I play is on www.warmane.com and they also have a few patches you can put in the data directory for extra models and such. I'd suggest that one as I've had no issues running it in Wine.<br />
== Installing Wine ==<br />
Be sure to check with your distros install. I use Gentoo so just doing "emerge wine-staging" did it for me. Make sure you are running wine-staging and vanilla-wine or any other version will not work. Be sure to install winetricks as well.<br />
===Configuring Wine===<br />
I'm running my instance in 32-bit mode on my Multilib 32/64 bit system. Your mileage may vary. I was running in 64 bit mode, but switched to 32-bit mode for compatibility and it seems to run better. First thing you want to do is create a directory off your home directory. Do all this as a user and not as root.<br />
<code><br />
cd ~<br />
mkdir WineWoW<br />
WINEARCH=win32 WINEPREFIX=~/WineWoW winetricks d3dx9_43 d3dx10_43 d3dx11_43<br />
</code><br />
<br />
This will install DirectX 9,10 and 11<br />
<br />
<br />
=== Test 3 ===</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=WotLK_3.3.5a_client_in_WINE&diff=81WotLK 3.3.5a client in WINE2018-12-22T11:34:33Z<p>Cfaulkner: Created page with "'''WotLK 3.3.5a Client in Linux'''"</p>
<hr />
<div>'''WotLK 3.3.5a Client in Linux'''</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Deepin_WM_on_Gentoo_Linux&diff=80Deepin WM on Gentoo Linux2018-09-08T18:35:19Z<p>Cfaulkner: /* Installing Deepin on Gentoo */</p>
<hr />
<div>=== Installing Deepin on Gentoo ===<br />
I've had some difficulty with this overlay. Here's what i've done so far:<br />
<br />
''layman -L && layman -a deepin''<br />
<br />
Then put these into a /etc/portage/package.use/10deepin<br />
<code><pre>sys-devel/gcc go<br />
media-libs/cogl gles2<br />
dev-libs/libxslt python<br />
media-libs/clutter egl<br />
</pre></code><br />
Then, start installing the packages<br />
<code><pre><br />
emerge -av deepin-desktop-base<br />
emerge -av deepin-tool-kit deepin-gettext-tools go go-x11-client dde-polkit-agent dde-go-essential deepin-tool-kit<br />
emerge -av deepin-desktop-base<br />
emerge -av deepin-wm<br />
</pre></code><br />
This is where i've stopped because of errors, will update soon</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Deepin_WM_on_Gentoo_Linux&diff=79Deepin WM on Gentoo Linux2018-09-08T18:34:59Z<p>Cfaulkner: /* Installing Deepin on Gentoo */</p>
<hr />
<div>=== Installing Deepin on Gentoo ===<br />
I've had some difficulty with this overlay. Here's what i've done so far:<br />
<br />
''layman -L && layman -a deepin''<br />
<br />
Then put these into a /etc/portage/package.use/10deepin<br />
<br />
<code><pre>sys-devel/gcc go<br />
media-libs/cogl gles2<br />
dev-libs/libxslt python<br />
media-libs/clutter egl<br />
</pre></code><br />
<br />
Then, start installing the packages<br />
<code><pre><br />
emerge -av deepin-desktop-base<br />
emerge -av deepin-tool-kit deepin-gettext-tools go go-x11-client dde-polkit-agent dde-go-essential deepin-tool-kit<br />
emerge -av deepin-desktop-base<br />
emerge -av deepin-wm<br />
</pre></code><br />
This is where i've stopped because of errors, will update soon</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Deepin_WM_on_Gentoo_Linux&diff=78Deepin WM on Gentoo Linux2018-09-08T18:34:04Z<p>Cfaulkner: </p>
<hr />
<div>=== Installing Deepin on Gentoo ===<br />
I've had some difficulty with this overlay. Here's what i've done so far:<br />
<br />
''layman -L && layman -a deepin''<br />
<br />
Then put these into a /etc/portage/package.use/10deepin<br />
<br />
<code>sys-devel/gcc go<br />
media-libs/cogl gles2<br />
dev-libs/libxslt python<br />
media-libs/clutter egl<br />
</code><br />
<br />
Then, start installing the packages<br />
<code><br />
emerge -av deepin-desktop-base<br />
emerge -av deepin-tool-kit deepin-gettext-tools go go-x11-client dde-polkit-agent dde-go-essential deepin-tool-kit<br />
emerge -av deepin-desktop-base<br />
emerge -av deepin-wm<br />
</code><br />
This is where i've stopped because of errors, will update soon</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Deepin_WM_on_Gentoo_Linux&diff=77Deepin WM on Gentoo Linux2018-09-08T18:32:39Z<p>Cfaulkner: </p>
<hr />
<div>=== Installing Deepin on Gentoo ===<br />
I've had some difficulty with this overlay. Here's what i've done so far:<br />
<br />
''layman -L && layman -a deepin''<br />
<br />
Then put these into a /etc/portage/package.use/10deepin<br />
<br />
''sys-devel/gcc go''<br />
' '<br />
''media-libs/cogl gles2''<br />
''dev-libs/libxslt python''<br />
''media-libs/clutter egl''<br />
<br />
<br />
Then, start installing the packages<br />
<br />
''emerge -av deepin-desktop-base''<br />
''emerge -av deepin-tool-kit deepin-gettext-tools go go-x11-client dde-polkit-agent dde-go-essential deepin-tool-kit''<br />
''emerge -av deepin-desktop-base''<br />
''emerge -av deepin-wm''<br />
<br />
This is where i've stopped because of errors, will update soon</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Deepin_WM_on_Gentoo_Linux&diff=76Deepin WM on Gentoo Linux2018-09-08T18:32:18Z<p>Cfaulkner: </p>
<hr />
<div>=== Installing Deepin on Gentoo ===<br />
I've had some difficulty with this overlay. Here's what i've done so far:<br />
<br />
''layman -L && layman -a deepin''<br />
<br />
Then put these into a /etc/portage/package.use/10deepin<br />
<br />
''sys-devel/gcc go''<br />
''media-libs/cogl gles2''<br />
''dev-libs/libxslt python''<br />
''media-libs/clutter egl''<br />
<br />
<br />
Then, start installing the packages<br />
<br />
''emerge -av deepin-desktop-base''<br />
''emerge -av deepin-tool-kit deepin-gettext-tools go go-x11-client dde-polkit-agent dde-go-essential deepin-tool-kit''<br />
''emerge -av deepin-desktop-base''<br />
''emerge -av deepin-wm''<br />
<br />
This is where i've stopped because of errors, will update soon</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Deepin_WM_on_Gentoo_Linux&diff=75Deepin WM on Gentoo Linux2018-09-08T18:30:57Z<p>Cfaulkner: </p>
<hr />
<div>=== Installing Deepin on Gentoo ===<br />
I've had some difficulty with this overlay. Here's what i've done so far:<br />
<br />
''layman -L && layman -a deepin''<br />
<br />
Then put these into a /etc/portage/package.use/10deepin<br />
<br />
''sys-devel/gcc go<br />
media-libs/cogl gles2<br />
dev-libs/libxslt python<br />
media-libs/clutter egl<br />
''<br />
<br />
Then, start installing the packages<br />
<br />
''emerge -av deepin-desktop-base<br />
emerge -av deepin-tool-kit deepin-gettext-tools go go-x11-client dde-polkit-agent dde-go-essential deepin-tool-kit<br />
emerge -av deepin-desktop-base<br />
emerge -av deepin-wm''<br />
<br />
This is where i've stopped because of errors, will update soon</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Deepin_WM_on_Gentoo_Linux&diff=74Deepin WM on Gentoo Linux2018-09-08T18:29:45Z<p>Cfaulkner: </p>
<hr />
<div>=== Installing Deepin on Gentoo ===<br />
I've had some difficulty with this overlay. Here's what i've done so far:<br />
<br />
''layman -L && layman -a deepin''<br />
<br />
Then put these into a /etc/portage/package.use/10deepin<br />
<br />
''sys-devel/gcc go<br />
# required by media-libs/clutter-1.26.2-r1::gentoo[egl]<br />
# required by x11-wm/deepin-mutter-3.20.34::deepin[kms]<br />
# required by x11-wm/deepin-wm-1.9.31::deepin<br />
# required by deepin-wm (argument)<br />
media-libs/cogl gles2<br />
# required by x11-libs/bamf-0.5.3::deepin<br />
# required by x11-wm/deepin-wm-1.9.31::deepin<br />
# required by deepin-wm (argument)<br />
dev-libs/libxslt python<br />
# required by x11-wm/deepin-mutter-3.20.34::deepin[kms]<br />
# required by x11-wm/deepin-wm-1.9.31::deepin<br />
# required by deepin-wm (argument)<br />
media-libs/clutter egl<br />
''<br />
<br />
Then, start installing the packages<br />
<br />
''emerge -av deepin-desktop-base<br />
emerge -av deepin-tool-kit deepin-gettext-tools go go-x11-client dde-polkit-agent dde-go-essential deepin-tool-kit<br />
emerge -av deepin-desktop-base<br />
emerge -av deepin-wm''<br />
<br />
This is where i've stopped because of errors, will update soon</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Deepin_WM_on_Gentoo_Linux&diff=73Deepin WM on Gentoo Linux2018-09-08T18:23:34Z<p>Cfaulkner: </p>
<hr />
<div>=== Installing Deepin on Gentoo ===<br />
I've had some difficulty with this overlay. Here's what i've done so far:<br />
<br />
''layman -L && layman -a deepin''</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Deepin_WM_on_Gentoo_Linux&diff=72Deepin WM on Gentoo Linux2018-09-08T18:22:42Z<p>Cfaulkner: Created page with "=== Installing Deepin on Gentoo === I've had some difficulty with this overlay"</p>
<hr />
<div>=== Installing Deepin on Gentoo ===<br />
I've had some difficulty with this overlay</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Raspberry_Pi_Distros&diff=71Raspberry Pi Distros2018-08-25T08:15:54Z<p>Cfaulkner: </p>
<hr />
<div>This is a collection of links i've found for Raspberry Pi Distros<br />
<br />
= Distros =<br />
== Raspberry Pi 1 ==<br />
<br />
== Raspberry Pi 2 ==<br />
<br />
== Raspberry Pi 3 ==</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Raspberry_Pi_Distros&diff=70Raspberry Pi Distros2018-08-25T08:15:31Z<p>Cfaulkner: </p>
<hr />
<div>This is a collection of links i've found for Raspberry Pi Distros<br />
<br />
== Raspberry Pi 1 ==<br />
<br />
== Raspberry Pi 2 ==<br />
<br />
== Raspberry Pi 3 ==</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Raspberry_Pi_Distros&diff=69Raspberry Pi Distros2018-08-25T08:14:50Z<p>Cfaulkner: </p>
<hr />
<div>This is a collection of links i've found for Raspberry Pi Distros<br />
<br />
= Raspberry Pi =<br />
<br />
== Raspberry Pi 1 ==<br />
<br />
== Raspberry Pi 2 ==<br />
<br />
== Raspberry Pi 3 ==</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Raspberry_Pi_Distros&diff=68Raspberry Pi Distros2018-08-25T08:13:19Z<p>Cfaulkner: Created page with "== Raspberry pi 1 == == Raspberry Pi 2 == == Raspberry Pi 3 =="</p>
<hr />
<div>== Raspberry pi 1 ==<br />
<br />
== Raspberry Pi 2 ==<br />
<br />
== Raspberry Pi 3 ==</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Main_Page&diff=67Main Page2018-08-25T08:10:50Z<p>Cfaulkner: Reverted edits by Cfaulkner (talk) to last revision by MediaWiki default</p>
<hr />
<div><strong>MediaWiki has been successfully installed.</strong><br />
<br />
Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.<br />
<br />
== Getting started ==<br />
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]<br />
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]<br />
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
* [//www.mediawiki.org/wiki/Localisation#Translation_resources Localise MediaWiki for your language]</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=Main_Page&diff=66Main Page2018-08-25T08:09:50Z<p>Cfaulkner: </p>
<hr />
<div><templatestyles src="Template:Main_page/styles.css" /><div class="mainpage_topbox"><br />
<div class="mainpage_pagetitle">'''{{Main page/include|welcome|{{{1|}}}|3=[[MediaWiki|<span class="mainpage_mwtitle">MediaWiki.org</span>]]}}'''</div><br />
<div class="mainpage_boxcontents">{{Main page/include|intro|{{{1|}}}}}</div><br />
<div class="mainpage_sitelinks"><br />
{{Main page/include|sitelink1|{{{1|}}}}} &nbsp; | &nbsp; <br />
{{Main page/include|sitelink2|{{{1|}}}}} &nbsp; | &nbsp; <br />
{{Main page/include|sitelink3|{{{1|}}}}} &nbsp; | &nbsp; <br />
{{Main page/include|sitelink4|{{{1|}}}}} &nbsp; | &nbsp;<br />
{{Main page/include|sitelink5|{{{1|}}}}}<br />
</div><br />
</div><!--<br />
<div class ="mainpage_notice"><br />
{{Main page/include|notice|{{{1|}}}}}<br />
</div>--><br />
<div class="mainpage_row2"><br />
<div class="mainpage_hubbox"><br />
<div class="mainpage_boxtitle">{{Main page/include|users title|{{{1|}}}}}</div><br />
<div class="mainpage_boxcontents"><br />
[[File:Crystal Clear app display.png|x80px|center|link={{#if: {{{1|}}}|{{#ifexist: User hub/{{{1}}}|User hub/{{{1}}}|User hub}}|User hub}}]]<br />
{{Main page/include|users text|{{{1|}}}}}<br />
</div><br />
</div><br />
<div class="mainpage_hubbox"><br />
<div class="mainpage_boxtitle">'''{{Main page/include|admins title|{{{1|}}}}}'''</div><br />
<div class="mainpage_boxcontents"><br />
[[File:Nuvola-inspired-terminal.svg|x80px|center|link={{#if: {{{1|}}}|{{#ifexist: Sysadmin hub/{{{1}}}|Sysadmin hub/{{{1}}}|Sysadmin hub}}|Sysadmin hub}}]]<br />
{{Main page/include|admins text|{{{1|}}}}}<br />
</div><br />
</div><br />
<div class="mainpage_hubbox"><br />
<div class="mainpage_boxtitle">'''{{Main page/include|devs title|{{{1|}}}}}'''</div><br />
<div class="mainpage_boxcontents"><br />
[[File:Crystal Clear app tutorials.png|x80px|center|link={{#if: {{{1|}}}|{{#ifexist: Developer hub/{{{1}}}|Developer hub/{{{1}}}|Developer hub}}|Developer hub}}]]<br />
{{Main page/include|devs text|{{{1|}}}}}<br />
</div><br />
</div><br />
</div><br />
<div class="mainpage_row3"><br />
<div class="mainpage_hubbox mainpage_downloadcell"><br />
<div class="mainpage_boxtitle">{{Main page/include|current versions|{{{1|}}}}}</div><br />
<div class="mainpage_boxcontents mainpage_boxcontents_small"><br />
{{Current versions}}<br />
<div style="width:90%; text-align:center; margin:10px auto;"><br />
<div style="border:2px outset #cccccc; background:#dddddd; margin:5px; padding:5px; white-space:nowrap;"><br />
[[File:Nuvola_apps_download_manager.png|40px|alt=|link={{#ifexist: Download/{{{1}}}|Download/{{{1}}}|Download}}]]<span style="padding-left:5px; font-size:130%; font-weight:bold;">[[{{#if: {{{1|}}}|{{#ifexist: Download/{{{1}}}|Download/{{{1}}}|Download}}|Download}}|{{Main page/include|download|{{{1|}}}}}]]</span><br />
</div><br />
</div><br />
</div><br />
</div><br />
<div class="mainpage_hubbox mainpage_newscell"><br />
<div class="mainpage_boxtitle">{{Main page/include|news title|{{{1|}}}}}</div><br />
<div class="mainpage_boxcontents mainpage_box contents_small"><br />
{{#if: {{{1|}}}|{{#ifexist: Template:MediaWiki News/{{{1}}}|{{MediaWiki News/{{{1}}}}}|{{MediaWiki News}}}}|{{MediaWiki News}}}}<br />
* '''{{Main page/include|old news link|{{{1|}}}}}'''<br />
</div><br />
</div><br />
</div><br />
<includeonly><div class="mainpage_languages">{{Languages}}</div></includeonly>__NOEDITSECTION__ __NOTOC__<noinclude>[[Category:Main page templates|*]]</noinclude></div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=MangosTwo_Install_-_Raspbian&diff=65MangosTwo Install - Raspbian2016-06-14T15:21:45Z<p>Cfaulkner: </p>
<hr />
<div>This howto will be on how to get MangosTwo running on Rasbian on a RaspberryPi 2<br />
<br />
== Installing Rasbian ==<br />
Download the Rasbian Image from the RaspberryPi Download page: [https://www.raspberrypi.org/downloads/raspbian/] and install it to your sd card. For mine, I am going to use an 8GB card and use a USB Flash Drive as extra storage. I'm using the 2016-05-27-raspbian-jessie-lite.img image<br />
<br />
== Starting up basic Rasbian Environment ==<br />
<br />
After creating the sd card and booting into Rasbian, the default login is username: pi password: raspberry<br />
<br />
check ifconfig for your ip address as I will be running on eth0 (hard wire) until after the compile is complete, then I will switch to running the RaspberryPi as an AP hotspot to make a portable WoW server. (Amazing little boxes these are).<br />
<br />
First thing is to update the OS<br />
<br />
<pre><br />
sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
<br />
Then, reboot and log back in<br />
<br />
== Setting up Build Environment for Mangos ==<br />
You can immediately SSH in now as the process is already running.<br />
<br />
After logging in, Add the user mangos and edit the /etc/sudoers file and add the mangos username<br />
<br />
<pre><br />
sudo adduser mangos<br />
<br />
edit /etc/sudoers<br />
<br />
Add under 'User Privilege Section' underneath root<br />
<br />
mangos ALL=(ALL) NOPASSWD: ALL<br />
<br />
Exit and save<br />
</pre><br />
<br />
Now type in exit and login as mangos username. You should have sudo rights now.<br />
<br />
Type in these commands to establish a build environment<br />
<pre><br />
sudo apt-get install -y autoconf automake clang cmake gcc g++ libtool make patch<br />
sudo apt-get install -y cmake-curses-gui git-core<br />
</pre><br />
<br />
With this version of Rasbian, all software was installed without an error because they were in the repositories.<br />
<br />
=== Installing the Development headers ===<br />
<br />
<pre><br />
sudo apt-get install -y libace-dev libbz2-dev libmysqlclient-dev libncurses5-dev libreadline-dev libssl-dev zlib1g-dev<br />
</pre><br />
<br />
== Installing the Database Server (MySQL) ==<br />
<br />
<pre><br />
sudo apt-get install -y mysql-server mysql-common mysql-client<br />
</pre><br />
<br />
Set the root password for the MySQL server<br />
<br />
=== Creating and Setting Permissions for MySQL User ===<br />
<br />
<pre><br />
mysql -u root -p<br />
<br />
CREATE USER 'mangos'@'localhost' IDENTIFIED BY 'password';<br />
</pre><br />
for Password, use whatever you want and for user mangos, use whatever you want.<br />
<br />
<pre><br />
GRANT ALL PRIVILEGES ON `mangos\_%` . * TO 'mangos'@'localhost';<br />
GRANT USAGE ON * . * TO 'mangos'@'localhost' IDENTIFIED BY 'password' WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ;<br />
</pre><br />
again for username and password, use whatever you want, just ensure they match<br />
<br />
=== Creating the Mangos Databases ===<br />
<br />
<pre><br />
<br />
CREATE DATABASE `mTwo_characters` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_realmd` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_world` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
FLUSH PRIVILEGES ;<br />
</pre><br />
<br />
== Downloading the Mangos-Two Source from github and compiling ==<br />
<br />
While you are in user mode and not root, create the mangos source directory<br />
<pre><br />
cd ~<br />
mkdir mangos-two<br />
cd mangos-two<br />
** Case Sensitive, be sure to take note of this as the branches are different **<br />
git clone --recursive -b develop21 https://github.com/mangoszero/server.git<br />
git clone --recursive -b Develop21 https://github.com/mangoszero/database.git<br />
</pre><br />
<br />
Be sure to use the '''--recursive''' so git will pull in everything, without this your compile will fail<br />
<br />
=== Compiling Mangos ===<br />
create the directories needed for build<br />
<pre><br />
sudo mkdir -p /opt/mTwo/<br />
sudo mkdir -p /opt/mTwo/logs/mangos-two/<br />
sudo mkdir -p /opt/mTwo/share/mangos-two/<br />
sudo chown -R mangos:mangos /opt/mTwo<br />
</pre><br />
<br />
<pre><br />
cd server<br />
mkdir _build<br />
cd _build<br />
cmake -DCMAKE_INSTALL_PREFIX=/opt/mTwo -DCMAKE_BUILD_TYPE=Debug -DACE_USE_EXTERNAL=1 -DSOAP=1 ..<br />
</pre><br />
<br />
DACE_USE_EXTERNAL=1 is important for the Tools to compile<br />
<br />
Now in the ~/mangos-two/server/_build directory<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
*** Errors on compile because the ARM Processor in the Raspberry Pi doesn't have SSE2 instructions ***<br />
**** STOP ****<br />
<br />
<br />
After a successful compile run this.<br />
<br />
<pre><br />
make install<br />
</pre><br />
<br />
== Configuration of Mangos ==<br />
<br />
<pre><br />
cd /opt/mTwo/etc<br />
cp ahbot.conf.dist ahbot.conf<br />
cp mangosd.conf.dist mangosd.conf<br />
cp realmd.conf.dist realmd.conf<br />
</pre><br />
<br />
<pre><br />
nano realmd.conf<br />
</pre><br />
<br />
The '''LoginDatabaseInfo''' Variable looks like this<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
</pre><br />
<br />
Change to<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realmd"<br />
</pre><br />
<br />
<br />
then for mangosd.conf<br />
<br />
<pre><br />
nano mangosd.conf<br />
</pre><br />
<br />
The lines that need to be changed are:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;mangos;characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
</pre><br />
<br />
These lines should be changed to:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realm"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_world"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_scripts"<br />
</pre><br />
<br />
Also in mangosd.conf, the "DataDir" needs to be changed from "." to "/opt/mTwo/data"<br />
<br />
== Map Extraction ==<br />
<br />
Go into /opt/mTwo/bin and copy these files to your main World of Warcraft directory ( c:\program files\World of Warcraft in Windows. You should know where it is )<br />
<br />
<pre><br />
cp map-extractor [WoW DIR]<br />
cp vmap-extractor [WoW DIR]<br />
cp vmap-assembler [WoW DIR]<br />
cp mmap-generator [WoW DIR]<br />
cp ExtractResources.sh [WoW DIR]<br />
cp MoveMapGen.sh [WoW DIR]<br />
cp offmesh.txt[WoW DIR]<br />
</pre><br />
<br />
Change to your WoW DIR<br />
<br />
<pre><br />
chown +x ExtractResources.sh<br />
./ExtractResources.sh<br />
</pre><br />
<br />
Answer the questions, should take a while. If you ever edit the offmesh.txt file, you have to re-run the ExtractResources.sh again.<br />
<br />
After it's done, Create a 'data' directory in /opt/mTwo and copy the dbc,vmaps and mmaps directories to /opt/mTwo/data<br />
<br />
== Inserting Database Information ==<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Setup<br />
mysql -u root -p mTwo_realmd < realmdLoadDB.sql<br />
cd ~/mangos-two/database/Character/Setup<br />
mysql -u root -p mTwo_characters < characterLoadDB.sql<br />
cd ~/mangos-two/database/World/Setup<br />
mysql -u root -p mTwo_world < mangosdLoadDB.sql<br />
</pre><br />
<br />
=== Inserting Table Information and Full DB ===<br />
<br />
<pre><br />
cd ~/mangos-two/database/<br />
<br />
chmod +x make_full_WorldDB.sh<br />
./make_full_WorldDB.sh<br />
mysql -u root -p mTwo_world < full_db.sql<br />
</pre><br />
<br />
== Running the Server ==<br />
<br />
=== Realmd (Realm Server) ===<br />
<br />
go to /opt/mTwo/bin and run the realmd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./realmd<br />
</pre><br />
<br />
If after running realmd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Updates/Rel20<br />
mysql -u root -p mTwo_realm < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get realmd listening for connections at this time.<br />
<br />
=== Mangos (World Server) ===<br />
go to /opt/mTwo/bin and run the mangosd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./mangosd<br />
</pre><br />
<br />
If after running mangosd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/World/Updates/Rel20<br />
mysql -u root -p mTwo_world < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get mangosd listening for connections at this time.<br />
<br />
== Finalizing running the server ==<br />
<br />
I use Screen so you'll have to install this<br />
<br />
<pre><br />
sudo apt-get install screen<br />
</pre><br />
<br />
Then, in the /opt/mTwo/bin directory, create a file called runserver.sh<br />
<br />
<pre><br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosworld ./mangosd<br />
<br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosrealm ./realmd<br />
</pre><br />
<br />
Save it and then chmod +x runserver.sh<br />
<br />
== Credits ==<br />
<br />
If you have any issues with this, please feel free to email me at me@chrisfaulkner.org</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=MangosTwo_Install_-_Raspbian&diff=64MangosTwo Install - Raspbian2016-06-14T14:24:09Z<p>Cfaulkner: </p>
<hr />
<div>This howto will be on how to get MangosTwo running on Rasbian on a RaspberryPi 2<br />
<br />
== Installing Rasbian ==<br />
Download the Rasbian Image from the RaspberryPi Download page: [https://www.raspberrypi.org/downloads/raspbian/] and install it to your sd card. For mine, I am going to use an 8GB card and use a USB Flash Drive as extra storage. I'm using the 2016-05-27-raspbian-jessie-lite.img image<br />
<br />
== Starting up basic Rasbian Environment ==<br />
<br />
After creating the sd card and booting into Rasbian, the default login is username: pi password: raspberry<br />
<br />
check ifconfig for your ip address as I will be running on eth0 (hard wire) until after the compile is complete, then I will switch to running the RaspberryPi as an AP hotspot to make a portable WoW server. (Amazing little boxes these are).<br />
<br />
First thing is to update the OS<br />
<br />
<pre><br />
sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
<br />
Then, reboot and log back in<br />
<br />
== Setting up Build Environment for Mangos ==<br />
You can immediately SSH in now as the process is already running.<br />
<br />
After logging in, Add the user mangos and edit the /etc/sudoers file and add the mangos username<br />
<br />
<pre><br />
sudo adduser mangos<br />
<br />
edit /etc/sudoers<br />
<br />
Add under 'User Privilege Section' underneath root<br />
<br />
mangos ALL=(ALL) NOPASSWD: ALL<br />
<br />
Exit and save<br />
</pre><br />
<br />
Now type in exit and login as mangos username. You should have sudo rights now.<br />
<br />
Type in these commands to establish a build environment<br />
<pre><br />
sudo apt-get install -y autoconf automake clang cmake gcc g++ libtool make patch<br />
sudo apt-get install -y cmake-curses-gui git-core<br />
</pre><br />
<br />
I had an issue with these commands not being found so I had to add the default repos in /etc/apt/sources.list<br />
<br />
<pre><br />
deb http://http.debian.net/debian wheezy main<br />
deb-src http://http.debian.net/debian wheezy main<br />
<br />
deb http://http.debian.net/debian wheezy-updates main<br />
deb-src http://http.debian.net/debian wheezy-updates main<br />
</pre><br />
<br />
run sudo apt-get update<br />
<br />
to update the repos<br />
<br />
=== Installing the Development headers ===<br />
<br />
<pre><br />
sudo apt-get install -y libace-dev libbz2-dev libmysqlclient-dev libncurses5-dev libreadline-dev libssl-dev zlib1g-dev<br />
</pre><br />
<br />
== Installing the Database Server (MySQL) ==<br />
<br />
<pre><br />
sudo apt-get install -y mysql-server mysql-common mysql-client<br />
</pre><br />
<br />
Set the root password for the MySQL server<br />
<br />
=== Creating and Setting Permissions for MySQL User ===<br />
<br />
<pre><br />
mysql -u root -p<br />
<br />
CREATE USER 'mangos'@'localhost' IDENTIFIED BY 'password';<br />
</pre><br />
for Password, use whatever you want and for user mangos, use whatever you want.<br />
<br />
<pre><br />
GRANT ALL PRIVILEGES ON `mangos\_%` . * TO 'mangos'@'localhost';<br />
GRANT USAGE ON * . * TO 'mangos'@'localhost' IDENTIFIED BY 'password' WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ;<br />
</pre><br />
again for username and password, use whatever you want, just ensure they match<br />
<br />
=== Creating the Mangos Databases ===<br />
<br />
<pre><br />
mysql -u root -p<br />
<br />
CREATE DATABASE `mTwo_characters` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_realmd` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_world` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
FLUSH PRIVILEGES ;<br />
</pre><br />
<br />
== Downloading the Mangos-Two Source from github and compiling ==<br />
<br />
While you are in user mode and not root, create the mangos source directory<br />
<pre><br />
cd ~<br />
mkdir mangos-two<br />
cd mangos-two<br />
** Case Sensitive, be sure to take note of this as the branches are different **<br />
git clone --recursive -b develop21 https://github.com/mangoszero/server.git<br />
git clone --recursive -b Develop21 https://github.com/mangoszero/database.git<br />
</pre><br />
<br />
Be sure to use the '''--recursive''' so git will pull in everything, without this your compile will fail<br />
<br />
=== Compiling Mangos ===<br />
create the directories needed for build<br />
<pre><br />
sudo mkdir -p /opt/mTwo/<br />
sudo mkdir -p /opt/mTwo/logs/mangos-two/<br />
sudo mkdir -p /opt/mTwo/share/mangos-two/<br />
sudo chown -R mangos:mangos mTwo<br />
</pre><br />
<br />
<pre><br />
cd server<br />
mkdir _build<br />
cd _build<br />
cmake -DCMAKE_INSTALL_PREFIX=/opt/mTwo -DCMAKE_BUILD_TYPE=Debug -DACE_USE_EXTERNAL=1 -DSOAP=1 <br />
..<br />
</pre><br />
<br />
DACE_USE_EXTERNAL=1 is important for the Tools to compile<br />
<br />
Now in the ~/mangos-two/server/_build directory<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
After a successful compile run this.<br />
<br />
<pre><br />
make install<br />
</pre><br />
<br />
== Configuration of Mangos ==<br />
<br />
<pre><br />
cd /opt/mTwo/etc<br />
cp ahbot.conf.dist ahbot.conf<br />
cp mangosd.conf.dist mangosd.conf<br />
cp realmd.conf.dist realmd.conf<br />
</pre><br />
<br />
<pre><br />
nano realmd.conf<br />
</pre><br />
<br />
The '''LoginDatabaseInfo''' Variable looks like this<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
</pre><br />
<br />
Change to<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realmd"<br />
</pre><br />
<br />
<br />
then for mangosd.conf<br />
<br />
<pre><br />
nano mangosd.conf<br />
</pre><br />
<br />
The lines that need to be changed are:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;mangos;characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
</pre><br />
<br />
These lines should be changed to:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realm"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_world"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_scripts"<br />
</pre><br />
<br />
Also in mangosd.conf, the "DataDir" needs to be changed from "." to "/opt/mTwo/data"<br />
<br />
== Map Extraction ==<br />
<br />
Go into /opt/mTwo/bin and copy these files to your main World of Warcraft directory ( c:\program files\World of Warcraft in Windows. You should know where it is )<br />
<br />
<pre><br />
cp map-extractor [WoW DIR]<br />
cp vmap-extractor [WoW DIR]<br />
cp vmap-assembler [WoW DIR]<br />
cp mmap-generator [WoW DIR]<br />
cp ExtractResources.sh [WoW DIR]<br />
cp MoveMapGen.sh [WoW DIR]<br />
cp offmesh.txt[WoW DIR]<br />
</pre><br />
<br />
Change to your WoW DIR<br />
<br />
<pre><br />
chown +x ExtractResources.sh<br />
./ExtractResources.sh<br />
</pre><br />
<br />
Answer the questions, should take a while. If you ever edit the offmesh.txt file, you have to re-run the ExtractResources.sh again.<br />
<br />
After it's done, Create a 'data' directory in /opt/mTwo and copy the dbc,vmaps and mmaps directories to /opt/mTwo/data<br />
<br />
== Inserting Database Information ==<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Setup<br />
mysql -u root -p mTwo_realmd < realmdLoadDB.sql<br />
cd ~/mangos-two/database/Character/Setup<br />
mysql -u root -p mTwo_characters < characterLoadDB.sql<br />
cd ~/mangos-two/database/World/Setup<br />
mysql -u root -p mTwo_world < mangosdLoadDB.sql<br />
</pre><br />
<br />
=== Inserting Table Information and Full DB ===<br />
<br />
<pre><br />
cd ~/mangos-two/database/<br />
<br />
chmod +x make_full_WorldDB.sh<br />
./make_full_WorldDB.sh<br />
mysql -u root -p mTwo_world < full_db.sql<br />
</pre><br />
<br />
== Running the Server ==<br />
<br />
=== Realmd (Realm Server) ===<br />
<br />
go to /opt/mTwo/bin and run the realmd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./realmd<br />
</pre><br />
<br />
If after running realmd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Updates/Rel20<br />
mysql -u root -p mTwo_realm < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get realmd listening for connections at this time.<br />
<br />
=== Mangos (World Server) ===<br />
go to /opt/mTwo/bin and run the mangosd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./mangosd<br />
</pre><br />
<br />
If after running mangosd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/World/Updates/Rel20<br />
mysql -u root -p mTwo_world < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get mangosd listening for connections at this time.<br />
<br />
== Finalizing running the server ==<br />
<br />
I use Screen so you'll have to install this<br />
<br />
<pre><br />
sudo apt-get install screen<br />
</pre><br />
<br />
Then, in the /opt/mTwo/bin directory, create a file called runserver.sh<br />
<br />
<pre><br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosworld ./mangosd<br />
<br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosrealm ./realmd<br />
</pre><br />
<br />
Save it and then chmod +x runserver.sh<br />
<br />
== Credits ==<br />
<br />
If you have any issues with this, please feel free to email me at me@chrisfaulkner.org</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=MangosTwo_Install_-_Raspbian&diff=63MangosTwo Install - Raspbian2016-06-14T14:10:48Z<p>Cfaulkner: Created page with "This howto will be on how to get MangosTwo running on Rasbian on a RaspberryPi 2 == Installing Rasbian == Download the Rasbian Image from the RaspberryPi Download page: [http..."</p>
<hr />
<div>This howto will be on how to get MangosTwo running on Rasbian on a RaspberryPi 2<br />
<br />
== Installing Rasbian ==<br />
Download the Rasbian Image from the RaspberryPi Download page: [https://www.raspberrypi.org/downloads/raspbian/] and install it to your sd card. For mine, I am going to use an 8GB card and use a USB Flash Drive as extra storage. I'm using the 2016-05-27-raspbian-jessie-lite.img image<br />
<br />
== Starting up basic Rasbian Environment ==<br />
<br />
After creating the sd card and booting into Rasbian, the default login is username: pi password: raspberry<br />
<br />
check ifconfig for your ip address as I will be running on eth0 (hard wire) until after the compile is complete, then I will switch to running the RaspberryPi as an AP hotspot to make a portable WoW server. (Amazing little boxes these are).<br />
<br />
First thing is to update the OS<br />
<br />
<pre><br />
sudo apt-get update<br />
sudo apt-get upgrade<br />
</pre><br />
<br />
Then, reboot and log back in<br />
<br />
== Setting up Build Environment for Mangos ==<br />
<br />
Login as root, we need to install a few things first. After looking at top, I only have 58 processes total running and about 56k of RAM used. not bad at all. We want the OS to be as trim as possible, that is one of the goals for this article.<br />
<br />
As root, type in:<br />
<pre><br />
apt-get install sudo ssh<br />
</pre><br />
<br />
After install of sudo, Add the user mangos and edit the /etc/sudoers file and add the mangos username<br />
<br />
<pre><br />
adduser mangos<br />
<br />
edit /etc/sudoers<br />
<br />
Add under 'User Privilege Section' underneath root<br />
mangos ALL=(ALL:ALL) ALL<br />
<br />
Exit and save<br />
</pre><br />
<br />
Now type in exit and login as mangos username. You should have sudo rights now.<br />
<br />
Type in these commands to establish a build environment<br />
<pre><br />
sudo apt-get install -y autoconf automake clang cmake gcc g++ libtool make patch<br />
sudo apt-get install -y cmake-curses-gui git-core<br />
</pre><br />
<br />
I had an issue with these commands not being found so I had to add the default repos in /etc/apt/sources.list<br />
<br />
<pre><br />
deb http://http.debian.net/debian wheezy main<br />
deb-src http://http.debian.net/debian wheezy main<br />
<br />
deb http://http.debian.net/debian wheezy-updates main<br />
deb-src http://http.debian.net/debian wheezy-updates main<br />
</pre><br />
<br />
run sudo apt-get update<br />
<br />
to update the repos<br />
<br />
=== Installing the Development headers ===<br />
<br />
<pre><br />
sudo apt-get install -y libace-dev libbz2-dev libmysqlclient-dev libncurses5-dev libreadline-dev libssl-dev zlib1g-dev<br />
</pre><br />
<br />
== Installing the Database Server (MySQL) ==<br />
<br />
<pre><br />
sudo apt-get install -y mysql-server mysql-common mysql-client<br />
</pre><br />
<br />
Set the root password for the MySQL server<br />
<br />
=== Creating and Setting Permissions for MySQL User ===<br />
<br />
<pre><br />
mysql -u root -p<br />
<br />
CREATE USER 'mangos'@'localhost' IDENTIFIED BY 'password';<br />
</pre><br />
for Password, use whatever you want and for user mangos, use whatever you want.<br />
<br />
<pre><br />
GRANT ALL PRIVILEGES ON `mangos\_%` . * TO 'mangos'@'localhost';<br />
GRANT USAGE ON * . * TO 'mangos'@'localhost' IDENTIFIED BY 'password' WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ;<br />
</pre><br />
again for username and password, use whatever you want, just ensure they match<br />
<br />
=== Creating the Mangos Databases ===<br />
<br />
<pre><br />
mysql -u root -p<br />
<br />
CREATE DATABASE `mTwo_characters` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_realmd` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_world` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
FLUSH PRIVILEGES ;<br />
</pre><br />
<br />
== Downloading the Mangos-Two Source from github and compiling ==<br />
<br />
While you are in user mode and not root, create the mangos source directory<br />
<pre><br />
cd ~<br />
mkdir mangos-two<br />
cd mangos-two<br />
** Case Sensitive, be sure to take note of this as the branches are different **<br />
git clone --recursive -b develop21 https://github.com/mangoszero/server.git<br />
git clone --recursive -b Develop21 https://github.com/mangoszero/database.git<br />
</pre><br />
<br />
Be sure to use the '''--recursive''' so git will pull in everything, without this your compile will fail<br />
<br />
=== Compiling Mangos ===<br />
create the directories needed for build<br />
<pre><br />
sudo mkdir -p /opt/mTwo/<br />
sudo mkdir -p /opt/mTwo/logs/mangos-two/<br />
sudo mkdir -p /opt/mTwo/share/mangos-two/<br />
sudo chown -R mangos:mangos mTwo<br />
</pre><br />
<br />
<pre><br />
cd server<br />
mkdir _build<br />
cd _build<br />
cmake -DCMAKE_INSTALL_PREFIX=/opt/mTwo -DCMAKE_BUILD_TYPE=Debug -DACE_USE_EXTERNAL=1 -DSOAP=1 <br />
..<br />
</pre><br />
<br />
DACE_USE_EXTERNAL=1 is important for the Tools to compile<br />
<br />
Now in the ~/mangos-two/server/_build directory<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
After a successful compile run this.<br />
<br />
<pre><br />
make install<br />
</pre><br />
<br />
== Configuration of Mangos ==<br />
<br />
<pre><br />
cd /opt/mTwo/etc<br />
cp ahbot.conf.dist ahbot.conf<br />
cp mangosd.conf.dist mangosd.conf<br />
cp realmd.conf.dist realmd.conf<br />
</pre><br />
<br />
<pre><br />
nano realmd.conf<br />
</pre><br />
<br />
The '''LoginDatabaseInfo''' Variable looks like this<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
</pre><br />
<br />
Change to<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realmd"<br />
</pre><br />
<br />
<br />
then for mangosd.conf<br />
<br />
<pre><br />
nano mangosd.conf<br />
</pre><br />
<br />
The lines that need to be changed are:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;mangos;characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
</pre><br />
<br />
These lines should be changed to:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realm"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_world"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_scripts"<br />
</pre><br />
<br />
Also in mangosd.conf, the "DataDir" needs to be changed from "." to "/opt/mTwo/data"<br />
<br />
== Map Extraction ==<br />
<br />
Go into /opt/mTwo/bin and copy these files to your main World of Warcraft directory ( c:\program files\World of Warcraft in Windows. You should know where it is )<br />
<br />
<pre><br />
cp map-extractor [WoW DIR]<br />
cp vmap-extractor [WoW DIR]<br />
cp vmap-assembler [WoW DIR]<br />
cp mmap-generator [WoW DIR]<br />
cp ExtractResources.sh [WoW DIR]<br />
cp MoveMapGen.sh [WoW DIR]<br />
cp offmesh.txt[WoW DIR]<br />
</pre><br />
<br />
Change to your WoW DIR<br />
<br />
<pre><br />
chown +x ExtractResources.sh<br />
./ExtractResources.sh<br />
</pre><br />
<br />
Answer the questions, should take a while. If you ever edit the offmesh.txt file, you have to re-run the ExtractResources.sh again.<br />
<br />
After it's done, Create a 'data' directory in /opt/mTwo and copy the dbc,vmaps and mmaps directories to /opt/mTwo/data<br />
<br />
== Inserting Database Information ==<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Setup<br />
mysql -u root -p mTwo_realmd < realmdLoadDB.sql<br />
cd ~/mangos-two/database/Character/Setup<br />
mysql -u root -p mTwo_characters < characterLoadDB.sql<br />
cd ~/mangos-two/database/World/Setup<br />
mysql -u root -p mTwo_world < mangosdLoadDB.sql<br />
</pre><br />
<br />
=== Inserting Table Information and Full DB ===<br />
<br />
<pre><br />
cd ~/mangos-two/database/<br />
<br />
chmod +x make_full_WorldDB.sh<br />
./make_full_WorldDB.sh<br />
mysql -u root -p mTwo_world < full_db.sql<br />
</pre><br />
<br />
== Running the Server ==<br />
<br />
=== Realmd (Realm Server) ===<br />
<br />
go to /opt/mTwo/bin and run the realmd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./realmd<br />
</pre><br />
<br />
If after running realmd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Updates/Rel20<br />
mysql -u root -p mTwo_realm < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get realmd listening for connections at this time.<br />
<br />
=== Mangos (World Server) ===<br />
go to /opt/mTwo/bin and run the mangosd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./mangosd<br />
</pre><br />
<br />
If after running mangosd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/World/Updates/Rel20<br />
mysql -u root -p mTwo_world < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get mangosd listening for connections at this time.<br />
<br />
== Finalizing running the server ==<br />
<br />
I use Screen so you'll have to install this<br />
<br />
<pre><br />
sudo apt-get install screen<br />
</pre><br />
<br />
Then, in the /opt/mTwo/bin directory, create a file called runserver.sh<br />
<br />
<pre><br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosworld ./mangosd<br />
<br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosrealm ./realmd<br />
</pre><br />
<br />
Save it and then chmod +x runserver.sh<br />
<br />
== Credits ==<br />
<br />
If you have any issues with this, please feel free to email me at me@chrisfaulkner.org</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=MangosTwo_Install_-_Debian&diff=62MangosTwo Install - Debian2016-06-13T15:54:47Z<p>Cfaulkner: </p>
<hr />
<div>This howto will be on how to get MangosTwo running on Debian in VirtualBox as Windows 7 64 Bit as the host<br />
<br />
== Installing VirtualBox ==<br />
This part should be self-explanatory, I may recap on certain settings like BIOS and other default settings<br />
<br />
== Starting up Virtual box and Installing the base operating system ==<br />
<br />
Create a new virtual machine, I'm going with a 64-bit install with Debian 7.2.0 ISOs. 512MB ram, create a 20GB dynamic partition. After the new virtual machine has been set up, give the server 12MB of video ram which is more than enough to run a server.<br />
<br />
Start the server, and select your settings as you wish.<br />
<br />
When installing packages, only install what you need because we want this server to be as trim as possible. No Desktop, XWindow or gui, just a straight server.<br />
<br />
On the Software Selection screen, Unselect Everything but the standard system utilities.<br />
<br />
Install the Grub boot loader<br />
<br />
== Setting up Build Environment for Mangos ==<br />
<br />
Login as root, we need to install a few things first. After looking at top, I only have 58 processes total running and about 56k of RAM used. not bad at all. We want the OS to be as trim as possible, that is one of the goals for this article.<br />
<br />
As root, type in:<br />
<pre><br />
apt-get install sudo ssh<br />
</pre><br />
<br />
After install of sudo, Add the user mangos and edit the /etc/sudoers file and add the mangos username<br />
<br />
<pre><br />
adduser mangos<br />
<br />
edit /etc/sudoers<br />
<br />
Add under 'User Privilege Section' underneath root<br />
mangos ALL=(ALL:ALL) ALL<br />
<br />
Exit and save<br />
</pre><br />
<br />
Now type in exit and login as mangos username. You should have sudo rights now.<br />
<br />
Type in these commands to establish a build environment<br />
<pre><br />
sudo apt-get install -y autoconf automake clang cmake gcc g++ libtool make patch<br />
sudo apt-get install -y cmake-curses-gui git-core<br />
</pre><br />
<br />
I had an issue with these commands not being found so I had to add the default repos in /etc/apt/sources.list<br />
<br />
<pre><br />
deb http://http.debian.net/debian wheezy main<br />
deb-src http://http.debian.net/debian wheezy main<br />
<br />
deb http://http.debian.net/debian wheezy-updates main<br />
deb-src http://http.debian.net/debian wheezy-updates main<br />
</pre><br />
<br />
run sudo apt-get update<br />
<br />
to update the repos<br />
<br />
=== Installing the Development headers ===<br />
<br />
<pre><br />
sudo apt-get install -y libace-dev libbz2-dev libmysqlclient-dev libncurses5-dev libreadline-dev libssl-dev zlib1g-dev<br />
</pre><br />
<br />
== Installing the Database Server (MySQL) ==<br />
<br />
<pre><br />
sudo apt-get install -y mysql-server mysql-common mysql-client<br />
</pre><br />
<br />
Set the root password for the MySQL server<br />
<br />
=== Creating and Setting Permissions for MySQL User ===<br />
<br />
<pre><br />
mysql -u root -p<br />
<br />
CREATE USER 'mangos'@'localhost' IDENTIFIED BY 'password';<br />
</pre><br />
for Password, use whatever you want and for user mangos, use whatever you want.<br />
<br />
<pre><br />
GRANT ALL PRIVILEGES ON `mangos\_%` . * TO 'mangos'@'localhost';<br />
GRANT USAGE ON * . * TO 'mangos'@'localhost' IDENTIFIED BY 'password' WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ;<br />
</pre><br />
again for username and password, use whatever you want, just ensure they match<br />
<br />
=== Creating the Mangos Databases ===<br />
<br />
<pre><br />
mysql -u root -p<br />
<br />
CREATE DATABASE `mTwo_characters` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_realmd` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_world` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
FLUSH PRIVILEGES ;<br />
</pre><br />
<br />
== Downloading the Mangos-Two Source from github and compiling ==<br />
<br />
While you are in user mode and not root, create the mangos source directory<br />
<pre><br />
cd ~<br />
mkdir mangos-two<br />
cd mangos-two<br />
** Case Sensitive, be sure to take note of this as the branches are different **<br />
git clone --recursive -b develop21 https://github.com/mangoszero/server.git<br />
git clone --recursive -b Develop21 https://github.com/mangoszero/database.git<br />
</pre><br />
<br />
Be sure to use the '''--recursive''' so git will pull in everything, without this your compile will fail<br />
<br />
=== Compiling Mangos ===<br />
create the directories needed for build<br />
<pre><br />
sudo mkdir -p /opt/mTwo/<br />
sudo mkdir -p /opt/mTwo/logs/mangos-two/<br />
sudo mkdir -p /opt/mTwo/share/mangos-two/<br />
sudo chown -R mangos:mangos mTwo<br />
</pre><br />
<br />
<pre><br />
cd server<br />
mkdir _build<br />
cd _build<br />
cmake -DCMAKE_INSTALL_PREFIX=/opt/mTwo -DCMAKE_BUILD_TYPE=Debug -DACE_USE_EXTERNAL=1 -DSOAP=1 <br />
..<br />
</pre><br />
<br />
DACE_USE_EXTERNAL=1 is important for the Tools to compile<br />
<br />
Now in the ~/mangos-two/server/_build directory<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
After a successful compile run this.<br />
<br />
<pre><br />
make install<br />
</pre><br />
<br />
== Configuration of Mangos ==<br />
<br />
<pre><br />
cd /opt/mTwo/etc<br />
cp ahbot.conf.dist ahbot.conf<br />
cp mangosd.conf.dist mangosd.conf<br />
cp realmd.conf.dist realmd.conf<br />
</pre><br />
<br />
<pre><br />
nano realmd.conf<br />
</pre><br />
<br />
The '''LoginDatabaseInfo''' Variable looks like this<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
</pre><br />
<br />
Change to<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realmd"<br />
</pre><br />
<br />
<br />
then for mangosd.conf<br />
<br />
<pre><br />
nano mangosd.conf<br />
</pre><br />
<br />
The lines that need to be changed are:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;mangos;characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
</pre><br />
<br />
These lines should be changed to:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realm"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_world"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_scripts"<br />
</pre><br />
<br />
Also in mangosd.conf, the "DataDir" needs to be changed from "." to "/opt/mTwo/data"<br />
<br />
== Map Extraction ==<br />
<br />
Go into /opt/mTwo/bin and copy these files to your main World of Warcraft directory ( c:\program files\World of Warcraft in Windows. You should know where it is )<br />
<br />
<pre><br />
cp map-extractor [WoW DIR]<br />
cp vmap-extractor [WoW DIR]<br />
cp vmap-assembler [WoW DIR]<br />
cp mmap-generator [WoW DIR]<br />
cp ExtractResources.sh [WoW DIR]<br />
cp MoveMapGen.sh [WoW DIR]<br />
cp offmesh.txt[WoW DIR]<br />
</pre><br />
<br />
Change to your WoW DIR<br />
<br />
<pre><br />
chown +x ExtractResources.sh<br />
./ExtractResources.sh<br />
</pre><br />
<br />
Answer the questions, should take a while. If you ever edit the offmesh.txt file, you have to re-run the ExtractResources.sh again.<br />
<br />
After it's done, Create a 'data' directory in /opt/mTwo and copy the dbc,vmaps and mmaps directories to /opt/mTwo/data<br />
<br />
== Inserting Database Information ==<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Setup<br />
mysql -u root -p mTwo_realmd < realmdLoadDB.sql<br />
cd ~/mangos-two/database/Character/Setup<br />
mysql -u root -p mTwo_characters < characterLoadDB.sql<br />
cd ~/mangos-two/database/World/Setup<br />
mysql -u root -p mTwo_world < mangosdLoadDB.sql<br />
</pre><br />
<br />
=== Inserting Table Information and Full DB ===<br />
<br />
<pre><br />
cd ~/mangos-two/database/<br />
<br />
chmod +x make_full_WorldDB.sh<br />
./make_full_WorldDB.sh<br />
mysql -u root -p mTwo_world < full_db.sql<br />
</pre><br />
<br />
== Running the Server ==<br />
<br />
=== Realmd (Realm Server) ===<br />
<br />
go to /opt/mTwo/bin and run the realmd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./realmd<br />
</pre><br />
<br />
If after running realmd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Updates/Rel20<br />
mysql -u root -p mTwo_realm < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get realmd listening for connections at this time.<br />
<br />
=== Mangos (World Server) ===<br />
go to /opt/mTwo/bin and run the mangosd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./mangosd<br />
</pre><br />
<br />
If after running mangosd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/World/Updates/Rel20<br />
mysql -u root -p mTwo_world < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get mangosd listening for connections at this time.<br />
<br />
== Finalizing running the server ==<br />
<br />
I use Screen so you'll have to install this<br />
<br />
<pre><br />
sudo apt-get install screen<br />
</pre><br />
<br />
Then, in the /opt/mTwo/bin directory, create a file called runserver.sh<br />
<br />
<pre><br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosworld ./mangosd<br />
<br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosrealm ./realmd<br />
</pre><br />
<br />
Save it and then chmod +x runserver.sh<br />
<br />
== Credits ==<br />
<br />
If you have any issues with this, please feel free to email me at me@chrisfaulkner.org</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=MangosTwo_Install_-_Debian&diff=61MangosTwo Install - Debian2016-06-13T15:13:49Z<p>Cfaulkner: </p>
<hr />
<div>This howto will be on how to get MangosTwo running on Debian in VirtualBox as Windows 7 64 Bit as the host<br />
<br />
== Installing VirtualBox ==<br />
This part should be self-explanatory, I may recap on certain settings like BIOS and other default settings<br />
<br />
== Starting up Virtual box and Installing the base operating system ==<br />
<br />
Create a new virtual machine, I'm going with a 64-bit install with Debian 7.2.0 ISOs. 512MB ram, create a 20GB dynamic partition. After the new virtual machine has been set up, give the server 12MB of video ram which is more than enough to run a server.<br />
<br />
Start the server, and select your settings as you wish.<br />
<br />
When installing packages, only install what you need because we want this server to be as trim as possible. No Desktop, XWindow or gui, just a straight server.<br />
<br />
On the Software Selection screen, Unselect Everything but the standard system utilities.<br />
<br />
Install the Grub boot loader<br />
<br />
== Setting up Build Environment for Mangos ==<br />
<br />
Login as root, we need to install a few things first. After looking at top, I only have 58 processes total running and about 56k of RAM used. not bad at all. We want the OS to be as trim as possible, that is one of the goals for this article.<br />
<br />
As root, type in:<br />
<pre><br />
apt-get install sudo ssh<br />
</pre><br />
<br />
After install of sudo, Add the user mangos and edit the /etc/sudoers file and add the mangos username<br />
<br />
<pre><br />
adduser mangos<br />
<br />
edit /etc/sudoers<br />
<br />
Add under 'User Privilege Section' underneath root<br />
mangos ALL=(ALL:ALL) ALL<br />
<br />
Exit and save<br />
</pre><br />
<br />
Now type in exit and login as mangos username. You should have sudo rights now.<br />
<br />
Type in these commands to establish a build environment<br />
<pre><br />
sudo apt-get install -y autoconf automake clang cmake gcc g++ libtool make patch<br />
sudo apt-get install -y cmake-curses-gui git-core<br />
</pre><br />
<br />
I had an issue with these commands not being found so I had to add the default repos in /etc/apt/sources.list<br />
<br />
<pre><br />
deb http://http.debian.net/debian wheezy main<br />
deb-src http://http.debian.net/debian wheezy main<br />
<br />
deb http://http.debian.net/debian wheezy-updates main<br />
deb-src http://http.debian.net/debian wheezy-updates main<br />
</pre><br />
<br />
run sudo apt-get update<br />
<br />
to update the repos<br />
<br />
=== Installing the Development headers ===<br />
<br />
<pre><br />
sudo apt-get install -y libace-dev libbz2-dev libmysqlclient-dev libncurses5-dev libreadline-dev libssl-dev zlib1g-dev<br />
</pre><br />
<br />
== Installing the Database Server (MySQL) ==<br />
<br />
<pre><br />
sudo apt-get install -y mysql-server mysql-common mysql-client<br />
</pre><br />
<br />
Set the root password for the MySQL server<br />
<br />
=== Creating and Setting Permissions for MySQL User ===<br />
<br />
<pre><br />
mysql -u root -p<br />
<br />
CREATE USER 'mangos'@'localhost' IDENTIFIED BY 'password';<br />
</pre><br />
for Password, use whatever you want and for user mangos, use whatever you want.<br />
<br />
<pre><br />
GRANT ALL PRIVILEGES ON `mangos\_%` . * TO 'mangos'@'localhost';<br />
GRANT USAGE ON * . * TO 'mangos'@'localhost' IDENTIFIED BY 'password' WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ;<br />
</pre><br />
again for username and password, use whatever you want, just ensure they match<br />
<br />
=== Creating the Mangos Databases ===<br />
<br />
<pre><br />
mysql -u root -p<br />
<br />
CREATE DATABASE `mTwo_characters` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_realm` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_world` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
FLUSH PRIVILEGES ;<br />
</pre><br />
<br />
== Downloading the Mangos-Two Source from github and compiling ==<br />
<br />
While you are in user mode and not root, create the mangos source directory<br />
<pre><br />
cd ~<br />
mkdir mangos-two<br />
cd mangos-two<br />
** Case Sensitive, be sure to take note of this as the branches are different **<br />
git clone --recursive -b develop21 https://github.com/mangoszero/server.git<br />
git clone --recursive -b Develop21 https://github.com/mangoszero/database.git<br />
</pre><br />
<br />
Be sure to use the '''--recursive''' so git will pull in everything, without this your compile will fail<br />
<br />
=== Compiling Mangos ===<br />
create the directories needed for build<br />
<pre><br />
sudo mkdir -p /opt/mTwo/<br />
sudo mkdir -p /opt/mTwo/logs/mangos-two/<br />
sudo mkdir -p /opt/mTwo/share/mangos-two/<br />
sudo chown -R mangos:mangos mTwo<br />
</pre><br />
<br />
<pre><br />
cd server<br />
mkdir _build<br />
cd _build<br />
cmake -DCMAKE_INSTALL_PREFIX=/opt/mTwo -DDEBUG=1 -DBUILD_TOOLS=1 -DACE_USE_EXTERNAL=1 ..<br />
</pre><br />
<br />
DACE_USE_EXTERNAL=1 is important for the Tools to compile<br />
<br />
Now in the ~/mangos-two/server/_build directory<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
After a successful compile run this.<br />
<br />
<pre><br />
make install<br />
</pre><br />
<br />
== Configuration of Mangos ==<br />
<br />
<pre><br />
cd /opt/mTwo/etc<br />
cp ahbot.conf.dist ahbot.conf<br />
cp mangosd.conf.dist mangosd.conf<br />
cp realmd.conf.dist realmd.conf<br />
</pre><br />
<br />
<pre><br />
nano realmd.conf<br />
</pre><br />
<br />
The '''LoginDatabaseInfo''' Variable looks like this<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
</pre><br />
<br />
Change to<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realm"<br />
</pre><br />
<br />
<br />
then for mangosd.conf<br />
<br />
<pre><br />
nano mangosd.conf<br />
</pre><br />
<br />
The lines that need to be changed are:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;mangos;characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
</pre><br />
<br />
These lines should be changed to:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realm"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_world"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_scripts"<br />
</pre><br />
<br />
== Map Extraction ==<br />
<br />
Go into /opt/mTwo/bin and copy these files to your main World of Warcraft directory ( c:\program files\World of Warcraft in Windows. You should know where it is )<br />
<br />
<pre><br />
cp map-extractor [WoW DIR]<br />
cp vmap-extractor [WoW DIR]<br />
cp vmap-assembler [WoW DIR]<br />
cp mmap-generator [WoW DIR]<br />
cp ExtractResources.sh [WoW DIR]<br />
cp MoveMapGen.sh [WoW DIR]<br />
cp offmesh.txt[WoW DIR]<br />
</pre><br />
<br />
Change to your WoW DIR<br />
<br />
<pre><br />
chown +x ExtractResources.sh<br />
./ExtractResources.sh<br />
</pre><br />
<br />
Answer the questions, should take a while. If you ever edit the offmesh.txt file, you have to re-run the ExtractResources.sh again.<br />
<br />
After it's done, Create a 'data' directory in /opt/mTwo and copy the dbc,vmaps and mmaps directories to /opt/mTwo/data<br />
<br />
== Inserting Database Information ==<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Setup<br />
mysql -u root -p mTwo_realm < realmdLoadDB.sql<br />
cd ~/mangos-two/database/Character/Setup<br />
mysql -u root -p mTwo_characters < characterLoadDB.sql<br />
cd ~/mangos-two/database/World/Setup<br />
mysql -u root -p mTwo_world < mangosdLoadDB.sql<br />
</pre><br />
<br />
=== Inserting Table Information and Full DB ===<br />
<br />
<pre><br />
cd ~/mangos-two/database/<br />
<br />
chmod +x make_full_WorldDB.sh<br />
./make_full_WorldDB.sh<br />
mysql -u root -p mTwo_world < full_db.sql<br />
</pre><br />
<br />
== Running the Server ==<br />
<br />
=== Realmd (Realm Server) ===<br />
<br />
go to /opt/mTwo/bin and run the realmd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./realmd<br />
</pre><br />
<br />
If after running realmd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Updates/Rel20<br />
mysql -u root -p mTwo_realm < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get realmd listening for connections at this time.<br />
<br />
=== Mangos (World Server) ===<br />
go to /opt/mTwo/bin and run the mangosd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./mangosd<br />
</pre><br />
<br />
If after running mangosd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/World/Updates/Rel20<br />
mysql -u root -p mTwo_world < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get mangosd listening for connections at this time.<br />
<br />
== Finalizing running the server ==<br />
<br />
I use Screen so you'll have to install this<br />
<br />
<pre><br />
sudo apt-get install screen<br />
</pre><br />
<br />
Then, in the /opt/mTwo/bin directory, create a file called runserver.sh<br />
<br />
<pre><br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosworld ./mangosd<br />
<br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosrealm ./realmd<br />
</pre><br />
<br />
Save it and then chmod +x runserver.sh<br />
<br />
== Credits ==<br />
<br />
If you have any issues with this, please feel free to email me at me@chrisfaulkner.org</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=MangosTwo_Install_-_Debian&diff=60MangosTwo Install - Debian2016-06-13T15:04:47Z<p>Cfaulkner: Created page with "This howto will be on how to get MangosTwo running on Debian in VirtualBox as Windows 7 64 Bit as the host == Installing VirtualBox == This part should be self-explanatory, I..."</p>
<hr />
<div>This howto will be on how to get MangosTwo running on Debian in VirtualBox as Windows 7 64 Bit as the host<br />
<br />
== Installing VirtualBox ==<br />
This part should be self-explanatory, I may recap on certain settings like BIOS and other default settings<br />
<br />
== Starting up Virtual box and Installing the base operating system ==<br />
<br />
Create a new virtual machine, I'm going with a 64-bit install with Debian 7.2.0 ISOs. 512MB ram, create a 20GB dynamic partition. After the new virtual machine has been set up, give the server 12MB of video ram which is more than enough to run a server.<br />
<br />
Start the server, and select your settings as you wish.<br />
<br />
When installing packages, only install what you need because we want this server to be as trim as possible. No Desktop, XWindow or gui, just a straight server.<br />
<br />
On the Software Selection screen, Unselect Everything but the standard system utilities.<br />
<br />
Install the Grub boot loader<br />
<br />
== Setting up Build Environment for Mangos ==<br />
<br />
Login as root, we need to install a few things first. After looking at top, I only have 58 processes total running and about 56k of RAM used. not bad at all. We want the OS to be as trim as possible, that is one of the goals for this article.<br />
<br />
As root, type in:<br />
<pre><br />
apt-get install sudo ssh<br />
</pre><br />
<br />
After install of sudo, Add the user mangos and edit the /etc/sudoers file and add the mangos username<br />
<br />
<pre><br />
adduser mangos<br />
<br />
edit /etc/sudoers<br />
<br />
Add under 'User Privilege Section' underneath root<br />
mangos ALL=(ALL:ALL) ALL<br />
<br />
Exit and save<br />
</pre><br />
<br />
Now type in exit and login as mangos username. You should have sudo rights now.<br />
<br />
Type in these commands to establish a build environment<br />
<pre><br />
sudo apt-get install -y autoconf automake clang cmake gcc g++ libtool make patch<br />
sudo apt-get install -y cmake-curses-gui git-core<br />
</pre><br />
<br />
I had an issue with these commands not being found so I had to add the default repos in /etc/apt/sources.list<br />
<br />
<pre><br />
deb http://http.debian.net/debian wheezy main<br />
deb-src http://http.debian.net/debian wheezy main<br />
<br />
deb http://http.debian.net/debian wheezy-updates main<br />
deb-src http://http.debian.net/debian wheezy-updates main<br />
</pre><br />
<br />
run sudo apt-get update<br />
<br />
to update the repos<br />
<br />
=== Installing the Development headers ===<br />
<br />
<pre><br />
sudo apt-get install -y libace-dev libbz2-dev libmysqlclient-dev libncurses5-dev libreadline-dev libssl-dev zlib1g-dev<br />
</pre><br />
<br />
== Installing the Database Server (MySQL) ==<br />
<br />
<pre><br />
sudo apt-get install -y mysql-server mysql-common mysql-client<br />
</pre><br />
<br />
Set the root password for the MySQL server<br />
<br />
=== Creating and Setting Permissions for MySQL User ===<br />
<br />
<pre><br />
mysql -u root -p<br />
<br />
CREATE USER 'mangos'@'localhost' IDENTIFIED BY 'password';<br />
</pre><br />
for Password, use whatever you want and for user mangos, use whatever you want.<br />
<br />
<pre><br />
GRANT ALL PRIVILEGES ON `mangos\_%` . * TO 'mangos'@'localhost';<br />
GRANT USAGE ON * . * TO 'mangos'@'localhost' IDENTIFIED BY 'password' WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ;<br />
</pre><br />
again for username and password, use whatever you want, just ensure they match<br />
<br />
=== Creating the Mangos Databases ===<br />
<br />
<pre><br />
mysql -u root -p<br />
<br />
CREATE DATABASE `mTwo_characters` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_realm` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
CREATE DATABASE `mTwo_world` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;<br />
FLUSH PRIVILEGES ;<br />
</pre><br />
<br />
== Downloading the Mangos-Two Source from github and compiling ==<br />
<br />
While you are in user mode and not root, create the mangos source directory<br />
<pre><br />
cd ~<br />
mkdir mangos-two<br />
cd mangos-two<br />
** Case Sensitive, be sure to take note of this as the branches are different **<br />
git clone --recursive -b develop21 https://github.com/mangoszero/server.git<br />
git clone --recursive -b Develop21 https://github.com/mangoszero/database.git<br />
</pre><br />
<br />
Be sure to use the '''--recursive''' so git will pull in everything, without this your compile will fail<br />
<br />
=== Compiling Mangos ===<br />
create the directories needed for build<br />
<pre><br />
sudo mkdir -p /opt/mTwo/<br />
sudo mkdir -p /opt/mTwo/logs/mangos-two/<br />
sudo mkdir -p /opt/mTwo/share/mangos-two/<br />
sudo chown -R mangos:mangos mTwo<br />
</pre><br />
<br />
<pre><br />
cd server<br />
mkdir _build<br />
cd _build<br />
cmake -DCMAKE_INSTALL_PREFIX=/opt/mTwo -DDEBUG=1 -DBUILD_TOOLS=1 -DACE_USE_EXTERNAL=1 ..<br />
</pre><br />
<br />
DACE_USE_EXTERNAL=1 is important for the Tools to compile<br />
<br />
Now in the ~/mangos-two/server/_build directory<br />
<br />
<pre><br />
make<br />
</pre><br />
<br />
After a successful compile run this.<br />
<br />
<pre><br />
make install<br />
</pre><br />
<br />
== Configuration of Mangos ==<br />
<br />
<pre><br />
cd /opt/mTwo/etc<br />
cp ahbot.conf.dist ahbot.conf<br />
cp mangosd.conf.dist mangosd.conf<br />
cp realmd.conf.dist realmd.conf<br />
</pre><br />
<br />
<pre><br />
nano realmd.conf<br />
</pre><br />
<br />
The '''LoginDatabaseInfo''' Variable looks like this<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
</pre><br />
<br />
Change to<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realm"<br />
</pre><br />
<br />
<br />
then for mangosd.conf<br />
<br />
<pre><br />
nano mangosd.conf<br />
</pre><br />
<br />
The lines that need to be changed are:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;mangos;realmd"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;mangos;characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;mangos;mangos"<br />
</pre><br />
<br />
These lines should be changed to:<br />
<pre><br />
LoginDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_realm"<br />
WorldDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_world"<br />
CharacterDatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_characters"<br />
ScriptDev2DatabaseInfo = "127.0.0.1;3306;mangos;password;mTwo_scripts"<br />
</pre><br />
<br />
== Map Extraction ==<br />
<br />
Go into /opt/mTwo/bin and copy these files to your main World of Warcraft directory ( c:\program files\World of Warcraft in Windows. You should know where it is )<br />
<br />
<pre><br />
cp map-extractor [WoW DIR]<br />
cp vmap-extractor [WoW DIR]<br />
cp vmap-assembler [WoW DIR]<br />
cp mmap-generator [WoW DIR]<br />
cp ExtractResources.sh [WoW DIR]<br />
cp MoveMapGen.sh [WoW DIR]<br />
cp offmesh.txt[WoW DIR]<br />
</pre><br />
<br />
Change to your WoW DIR<br />
<br />
<pre><br />
chown +x ExtractResources.sh<br />
./ExtractResources.sh<br />
</pre><br />
<br />
Answer the questions, should take a while. If you ever edit the offmesh.txt file, you have to re-run the ExtractResources.sh again.<br />
<br />
After it's done, Create a 'data' directory in /opt/mTwo and copy the dbc,vmaps and mmaps directories to /opt/mTwo/data<br />
<br />
== Inserting Database Information ==<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Setup<br />
mysql -u root -p mTwo_realm < realmdLoadDB.sql<br />
cd ~/mangos-two/database/Character/Setup<br />
mysql -u root -p mTwo_characters < characterLoadDB.sql<br />
cd ~/mangos-two/database/World/Setup<br />
mysql -u root -p mTwo_world < mangosdLoadDB.sql<br />
</pre><br />
<br />
=== Inserting Table Information and Full DB ===<br />
<br />
<pre><br />
cd ~/mangos-two/database/<br />
nano make_full_WorldDB.sh<br />
<br />
Change the last line to look like this:<br />
<br />
for i in /home/mangos/mangos-two/database/World/Setup/FullDB/*.sql; do tail -n +18 $i >> full_db.sql; done<br />
<br />
Save the file<br />
<br />
bash make_full_WorldDB.sh<br />
mysql -u root -p mTwo_world < full_db.sql<br />
</pre><br />
<br />
== Running the Server ==<br />
<br />
=== Realmd (Realm Server) ===<br />
<br />
go to /opt/mTwo/bin and run the realmd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./realmd<br />
</pre><br />
<br />
If after running realmd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/Realm/Updates/Rel20<br />
mysql -u root -p mTwo_realm < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get realmd listening for connections at this time.<br />
<br />
=== Mangos (World Server) ===<br />
go to /opt/mTwo/bin and run the mangosd server<br />
<br />
<pre><br />
cd /opt/mTwo/bin<br />
./mangosd<br />
</pre><br />
<br />
If after running mangosd and you get an error<br />
<br />
<pre><br />
cd ~/mangos-two/database/World/Updates/Rel20<br />
mysql -u root -p mTwo_world < update_the_SQL_file_it_was_screaming_for.sql<br />
</pre><br />
<br />
You should get mangosd listening for connections at this time.<br />
<br />
== Finalizing running the server ==<br />
<br />
I use Screen so you'll have to install this<br />
<br />
<pre><br />
sudo apt-get install screen<br />
</pre><br />
<br />
Then, in the /opt/mTwo/bin directory, create a file called runserver.sh<br />
<br />
<pre><br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosworld ./mangosd<br />
<br />
#!/bin/sh<br />
cd /opt/mTwo/bin<br />
screen -A -m -d -S mangosrealm ./realmd<br />
</pre><br />
<br />
Save it and then chmod +x runserver.sh<br />
<br />
== Credits ==<br />
<br />
If you have any issues with this, please feel free to email me at me@chrisfaulkner.org</div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=RT-N12/D1&diff=59RT-N12/D12014-12-06T01:46:40Z<p>Cfaulkner: </p>
<hr />
<div>== Board ==<br />
1.-->GND<br />
2.-->RXD<br />
3.-->TXD<br />
4.-->+3.3V<br />
[[File:RT-N12-D1-Board.jpg|none|left]]<br />
<br />
== /proc info ==<br />
<br />
=== cat /proc/meminfo ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/meminfo<br />
total: used: free: shared: buffers: cached:<br />
Mem: 26787840 13647872 13139968 0 1306624 4194304<br />
Swap: 0 0 0<br />
MemTotal: 26160 kB<br />
MemFree: 12832 kB<br />
MemShared: 0 kB<br />
Buffers: 1276 kB<br />
Cached: 4096 kB<br />
SwapCached: 0 kB<br />
Active: 1122 kB<br />
Inactive: 541 kB<br />
HighTotal: 0 kB<br />
HighFree: 0 kB<br />
LowTotal: 26160 kB<br />
LowFree: 12832 kB<br />
SwapTotal: 0 kB<br />
SwapFree: 0 kB<br />
Dirty: 0 kB<br />
Writeback: 0 kB<br />
Mapped: 214 kB<br />
Slab: 129 kB<br />
CommitLimit: 13080 kB<br />
Committed_AS: 3264 kB<br />
PageTables: 1343 kB<br />
VmallocTotal: 1015800 kB<br />
VmallocUsed: 20 kB<br />
VmallocChunk: 1015760 kB<br />
</pre><br />
<br />
=== cat /proc/devices ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/devices<br />
Character devices:<br />
1 mem<br />
2 pty<br />
3 ttyp<br />
4 ttyS<br />
5 /dev/tty<br />
5 /dev/console<br />
5 /dev/ptmx<br />
10 misc<br />
90 mtd<br />
108 ppp<br />
127 gpio<br />
128 ptm<br />
136 pts<br />
229 nvram<br />
254 devfs<br />
<br />
Block devices:<br />
31 mtdblock<br />
</pre><br />
=== cat /proc/vmstat ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/vmstat<br />
nr_free_pages 3178<br />
nr_inactive 541<br />
nr_active 1138<br />
nr_anon_pages 338<br />
nr_mapped 258<br />
nr_file_pages 1343<br />
nr_dirty 0<br />
nr_writeback 0<br />
nr_slab_reclaimable 129<br />
nr_slab_unreclaimable 1455<br />
nr_page_table_pages 45<br />
nr_unstable 0<br />
nr_bounce 0<br />
nr_vmscan_write 0<br />
</pre><br />
=== cat /proc/iomem ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/iomem<br />
00000000-01ffffff : System RAM<br />
00001000-00371a13 : Kernel code<br />
00371a14-004c90bf : Kernel data<br />
</pre><br />
=== cat /proc/cpuinfo ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/cpuinfo<br />
system type : Broadcom BCMD144 chip rev 1<br />
processor : 0<br />
cpu model : MIPS 74K V4.9<br />
BogoMIPS : 149.91<br />
wait instruction : no<br />
microsecond timers : yes<br />
tlb_entries : 32<br />
extra interrupt vector : no<br />
hardware watchpoint : yes<br />
ASEs implemented : mips16 dsp<br />
shadow register sets : 1<br />
VCED exceptions : not available<br />
VCEI exceptions : not available<br />
<br />
dcache hits : 2147483648<br />
dcache misses : 4025974527<br />
icache hits : 2147483648<br />
icache misses : 2129788862<br />
instructions : 2147483648<br />
</pre><br />
=== cat /proc/partitions ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/partitions<br />
major minor #blocks name<br />
<br />
31 0 128 mtdblock0<br />
31 1 8000 mtdblock1<br />
31 2 1989 mtdblock2<br />
31 3 64 mtdblock3<br />
31 4 4608 mtdblock4<br />
</pre><br />
=== cat /proc/kmsg ===<br />
<pre><br />
<5>Linux version 2.6.24.111 (root@dd-wrt) (gcc version 4.1.2) #9550 Mon Mar 19 00:53:46 CET 2012<br />
<4>CPU revision is: 00019749<br />
<4>Found a 8MB ST compatible serial flash<br />
<4>Determined physical RAM map:<br />
<4> memory: 02000000 @ 00000000 (usable)<br />
<7>Entering add_active_range(0, 0, 8192) 0 entries of 256 used<br />
<4>Zone PFN ranges:<br />
<4> Normal 0 -> 8192<br />
<4> HighMem 8192 -> 8192<br />
<4>Movable zone start PFN for each node<br />
<4>early_node_map[1] active PFN ranges<br />
<4> 0: 0 -> 8192<br />
<7>On node 0 totalpages: 8192<br />
<7> Normal zone: 0 pages used for memmap<br />
<7> Normal zone: 0 pages reserved<br />
<7> Normal zone: 8192 pages, LIFO batch:1<br />
<7> HighMem zone: 0 pages used for memmap<br />
<7> Movable zone: 0 pages used for memmap<br />
<4>Built 1 zonelists in Zone order. Total pages: 8192<br />
<5>Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd<br />
<4>Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.<br />
<4>Primary data cache 32kB, 4-way, linesize 32 bytes.<br />
<6>Synthesized TLB refill handler (20 instructions).<br />
<6>Synthesized TLB load handler fastpath (32 instructions).<br />
<6>Synthesized TLB store handler fastpath (32 instructions).<br />
<6>Synthesized TLB modify handler fastpath (31 instructions).<br />
<4>PID hash table entries: 256 (order: 8, 1024 bytes)<br />
<4>CPU: BCMd144 rev 1 at 300 MHz<br />
<4>Using 150.000 MHz high precision timer.<br />
<6>console [ttyS0] enabled<br />
<6>Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)<br />
<6>Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)<br />
<6>Memory: 25956k/32768k available (3522k kernel code, 6796k reserved, 1373k data, 188k init, 0k highmem)<br />
<7>Calibrating delay loop... 149.91 BogoMIPS (lpj=749568)<br />
<4>Mount-cache hash table entries: 512<br />
<6>NET: Registered protocol family 16<br />
<6>Generic PHY: Registered new driver<br />
<4>PCI: no core<br />
<4>PCI: no core<br />
<4>PCI: Fixing up bus 0<br />
<6>NET: Registered protocol family 2<br />
<6>Time: MIPS clocksource has been installed.<br />
<6>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)<br />
<6>TCP established hash table entries: 1024 (order: 1, 8192 bytes)<br />
<6>TCP bind hash table entries: 1024 (order: 0, 4096 bytes)<br />
<6>TCP: Hash tables configured (established 1024 bind 1024)<br />
<6>TCP reno registered<br />
<6>devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)<br />
<6>devfs: boot_options: 0x1<br />
<6>squashfs: version 3.0 (2006/03/15) Phillip Lougher<br />
<6>io scheduler noop registered<br />
<6>io scheduler deadline registered (default)<br />
<6>HDLC line discipline: version $Revision: 4.8 $, maxframe=4096<br />
<6>N_HDLC line discipline registered.<br />
<6>Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled<br />
<6>serial8250: ttyS0 at MMIO 0x0 (irq = 8) is a 16550A<br />
<6>PPP generic driver version 2.4.2<br />
<6>PPP Deflate Compression module registered<br />
<6>PPP BSD Compression module registered<br />
<6>MPPE/MPPC encryption/compression module registered<br />
<6>NET: Registered protocol family 24<br />
<6>PPPoL2TP kernel driver, V1.0<br />
<6>tun: Universal TUN/TAP device driver, 1.6<br />
<6>tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com><br />
<4>et_module_init: passivemode set to 0x0<br />
<7>PCI: Setting latency timer of device 0000:00:02.0 to 64<br />
<4>eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138.9<br />
<7>PCI: Setting latency timer of device 0000:00:01.0 to 64<br />
<3>pflash: found no supported devices<br />
<0>bootloader size: 131072<br />
<0>nvram size: 32768<br />
<0>sflash: Filesystem type: squashfs, size=0x1ee540<br />
<0>partition size = 2036736<br />
<5>Creating 5 MTD partitions on "sflash":<br />
<5>0x00000000-0x00020000 : "cfe"<br />
<5>0x00020000-0x007f0000 : "linux"<br />
<5>0x0017ec00-0x00370000 : "rootfs"<br />
<4>mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only<br />
<5>0x007f0000-0x00800000 : "nvram"<br />
<5>0x00370000-0x007f0000 : "ddwrt"<br />
<6>Broadcom Watchdog Timer: 0.07 initialized.<br />
<4>u32 classifier<br />
<4> Actions configured<br />
<4>Netfilter messages via NETLINK v0.30.<br />
<4>nf_conntrack version 0.5.0 (1024 buckets, 4096 max)<br />
<4>ctnetlink v0.93: registering with nfnetlink.<br />
<6>IPv4 over IPv4 tunneling driver<br />
<6>GRE over IPv4 tunneling driver<br />
<6>ip_tables: (C) 2000-2006 Netfilter Core Team<br />
<5>ClusterIP Version 0.8 loaded successfully<br />
<6>TCP bic registered<br />
<6>TCP cubic registered<br />
<6>TCP westwood registered<br />
<6>TCP highspeed registered<br />
<6>TCP hybla registered<br />
<6>TCP htcp registered<br />
<6>TCP vegas registered<br />
<6>TCP scalable registered<br />
<6>NET: Registered protocol family 1<br />
<6>NET: Registered protocol family 17<br />
<4>Welcome to PF_RING 3.2.1<br />
<4>(C) 2004-06 L.Deri <deri@ntop.org><br />
<6>NET: Registered protocol family 27<br />
<4>PF_RING: bucket length 128 bytes<br />
<4>PF_RING: ring slots 4096<br />
<4>PF_RING: sample rate 1 [1=no sampling]<br />
<4>PF_RING: capture TX No [RX only]<br />
<4>PF_RING: transparent mode Yes<br />
<4>PF_RING initialized correctly.<br />
<4>PF_RING: registered /proc/net/pf_ring/<br />
<6>802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com><br />
<6>All bugs added by David S. Miller <davem@redhat.com><br />
<0>decode 1f02<br />
<4>VFS: Mounted root (squashfs filesystem) readonly.<br />
<6>Mounted devfs on /dev<br />
<6>Freeing unused kernel memory: 188k freed<br />
<3>br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.<br />
</pre></div>Cfaulknerhttp://together.chrisfaulkner.org/index.php?title=RT-N12/D1&diff=58RT-N12/D12014-12-06T01:46:16Z<p>Cfaulkner: </p>
<hr />
<div>== Board ==<br />
1.-->GND<br />
2.-->RXD<br />
3.-->TXD<br />
4.-->+3.3V<br />
[[File:RT-N12-D1-Board.jpg|none|200px|left]]<br />
== /proc info ==<br />
<br />
=== cat /proc/meminfo ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/meminfo<br />
total: used: free: shared: buffers: cached:<br />
Mem: 26787840 13647872 13139968 0 1306624 4194304<br />
Swap: 0 0 0<br />
MemTotal: 26160 kB<br />
MemFree: 12832 kB<br />
MemShared: 0 kB<br />
Buffers: 1276 kB<br />
Cached: 4096 kB<br />
SwapCached: 0 kB<br />
Active: 1122 kB<br />
Inactive: 541 kB<br />
HighTotal: 0 kB<br />
HighFree: 0 kB<br />
LowTotal: 26160 kB<br />
LowFree: 12832 kB<br />
SwapTotal: 0 kB<br />
SwapFree: 0 kB<br />
Dirty: 0 kB<br />
Writeback: 0 kB<br />
Mapped: 214 kB<br />
Slab: 129 kB<br />
CommitLimit: 13080 kB<br />
Committed_AS: 3264 kB<br />
PageTables: 1343 kB<br />
VmallocTotal: 1015800 kB<br />
VmallocUsed: 20 kB<br />
VmallocChunk: 1015760 kB<br />
</pre><br />
<br />
=== cat /proc/devices ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/devices<br />
Character devices:<br />
1 mem<br />
2 pty<br />
3 ttyp<br />
4 ttyS<br />
5 /dev/tty<br />
5 /dev/console<br />
5 /dev/ptmx<br />
10 misc<br />
90 mtd<br />
108 ppp<br />
127 gpio<br />
128 ptm<br />
136 pts<br />
229 nvram<br />
254 devfs<br />
<br />
Block devices:<br />
31 mtdblock<br />
</pre><br />
=== cat /proc/vmstat ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/vmstat<br />
nr_free_pages 3178<br />
nr_inactive 541<br />
nr_active 1138<br />
nr_anon_pages 338<br />
nr_mapped 258<br />
nr_file_pages 1343<br />
nr_dirty 0<br />
nr_writeback 0<br />
nr_slab_reclaimable 129<br />
nr_slab_unreclaimable 1455<br />
nr_page_table_pages 45<br />
nr_unstable 0<br />
nr_bounce 0<br />
nr_vmscan_write 0<br />
</pre><br />
=== cat /proc/iomem ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/iomem<br />
00000000-01ffffff : System RAM<br />
00001000-00371a13 : Kernel code<br />
00371a14-004c90bf : Kernel data<br />
</pre><br />
=== cat /proc/cpuinfo ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/cpuinfo<br />
system type : Broadcom BCMD144 chip rev 1<br />
processor : 0<br />
cpu model : MIPS 74K V4.9<br />
BogoMIPS : 149.91<br />
wait instruction : no<br />
microsecond timers : yes<br />
tlb_entries : 32<br />
extra interrupt vector : no<br />
hardware watchpoint : yes<br />
ASEs implemented : mips16 dsp<br />
shadow register sets : 1<br />
VCED exceptions : not available<br />
VCEI exceptions : not available<br />
<br />
dcache hits : 2147483648<br />
dcache misses : 4025974527<br />
icache hits : 2147483648<br />
icache misses : 2129788862<br />
instructions : 2147483648<br />
</pre><br />
=== cat /proc/partitions ===<br />
<pre><br />
root@DD-WRT:/proc# cat /proc/partitions<br />
major minor #blocks name<br />
<br />
31 0 128 mtdblock0<br />
31 1 8000 mtdblock1<br />
31 2 1989 mtdblock2<br />
31 3 64 mtdblock3<br />
31 4 4608 mtdblock4<br />
</pre><br />
=== cat /proc/kmsg ===<br />
<pre><br />
<5>Linux version 2.6.24.111 (root@dd-wrt) (gcc version 4.1.2) #9550 Mon Mar 19 00:53:46 CET 2012<br />
<4>CPU revision is: 00019749<br />
<4>Found a 8MB ST compatible serial flash<br />
<4>Determined physical RAM map:<br />
<4> memory: 02000000 @ 00000000 (usable)<br />
<7>Entering add_active_range(0, 0, 8192) 0 entries of 256 used<br />
<4>Zone PFN ranges:<br />
<4> Normal 0 -> 8192<br />
<4> HighMem 8192 -> 8192<br />
<4>Movable zone start PFN for each node<br />
<4>early_node_map[1] active PFN ranges<br />
<4> 0: 0 -> 8192<br />
<7>On node 0 totalpages: 8192<br />
<7> Normal zone: 0 pages used for memmap<br />
<7> Normal zone: 0 pages reserved<br />
<7> Normal zone: 8192 pages, LIFO batch:1<br />
<7> HighMem zone: 0 pages used for memmap<br />
<7> Movable zone: 0 pages used for memmap<br />
<4>Built 1 zonelists in Zone order. Total pages: 8192<br />
<5>Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd<br />
<4>Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.<br />
<4>Primary data cache 32kB, 4-way, linesize 32 bytes.<br />
<6>Synthesized TLB refill handler (20 instructions).<br />
<6>Synthesized TLB load handler fastpath (32 instructions).<br />
<6>Synthesized TLB store handler fastpath (32 instructions).<br />
<6>Synthesized TLB modify handler fastpath (31 instructions).<br />
<4>PID hash table entries: 256 (order: 8, 1024 bytes)<br />
<4>CPU: BCMd144 rev 1 at 300 MHz<br />
<4>Using 150.000 MHz high precision timer.<br />
<6>console [ttyS0] enabled<br />
<6>Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)<br />
<6>Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)<br />
<6>Memory: 25956k/32768k available (3522k kernel code, 6796k reserved, 1373k data, 188k init, 0k highmem)<br />
<7>Calibrating delay loop... 149.91 BogoMIPS (lpj=749568)<br />
<4>Mount-cache hash table entries: 512<br />
<6>NET: Registered protocol family 16<br />
<6>Generic PHY: Registered new driver<br />
<4>PCI: no core<br />
<4>PCI: no core<br />
<4>PCI: Fixing up bus 0<br />
<6>NET: Registered protocol family 2<br />
<6>Time: MIPS clocksource has been installed.<br />
<6>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)<br />
<6>TCP established hash table entries: 1024 (order: 1, 8192 bytes)<br />
<6>TCP bind hash table entries: 1024 (order: 0, 4096 bytes)<br />
<6>TCP: Hash tables configured (established 1024 bind 1024)<br />
<6>TCP reno registered<br />
<6>devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)<br />
<6>devfs: boot_options: 0x1<br />
<6>squashfs: version 3.0 (2006/03/15) Phillip Lougher<br />
<6>io scheduler noop registered<br />
<6>io scheduler deadline registered (default)<br />
<6>HDLC line discipline: version $Revision: 4.8 $, maxframe=4096<br />
<6>N_HDLC line discipline registered.<br />
<6>Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled<br />
<6>serial8250: ttyS0 at MMIO 0x0 (irq = 8) is a 16550A<br />
<6>PPP generic driver version 2.4.2<br />
<6>PPP Deflate Compression module registered<br />
<6>PPP BSD Compression module registered<br />
<6>MPPE/MPPC encryption/compression module registered<br />
<6>NET: Registered protocol family 24<br />
<6>PPPoL2TP kernel driver, V1.0<br />
<6>tun: Universal TUN/TAP device driver, 1.6<br />
<6>tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com><br />
<4>et_module_init: passivemode set to 0x0<br />
<7>PCI: Setting latency timer of device 0000:00:02.0 to 64<br />
<4>eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138.9<br />
<7>PCI: Setting latency timer of device 0000:00:01.0 to 64<br />
<3>pflash: found no supported devices<br />
<0>bootloader size: 131072<br />
<0>nvram size: 32768<br />
<0>sflash: Filesystem type: squashfs, size=0x1ee540<br />
<0>partition size = 2036736<br />
<5>Creating 5 MTD partitions on "sflash":<br />
<5>0x00000000-0x00020000 : "cfe"<br />
<5>0x00020000-0x007f0000 : "linux"<br />
<5>0x0017ec00-0x00370000 : "rootfs"<br />
<4>mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only<br />
<5>0x007f0000-0x00800000 : "nvram"<br />
<5>0x00370000-0x007f0000 : "ddwrt"<br />
<6>Broadcom Watchdog Timer: 0.07 initialized.<br />
<4>u32 classifier<br />
<4> Actions configured<br />
<4>Netfilter messages via NETLINK v0.30.<br />
<4>nf_conntrack version 0.5.0 (1024 buckets, 4096 max)<br />
<4>ctnetlink v0.93: registering with nfnetlink.<br />
<6>IPv4 over IPv4 tunneling driver<br />
<6>GRE over IPv4 tunneling driver<br />
<6>ip_tables: (C) 2000-2006 Netfilter Core Team<br />
<5>ClusterIP Version 0.8 loaded successfully<br />
<6>TCP bic registered<br />
<6>TCP cubic registered<br />
<6>TCP westwood registered<br />
<6>TCP highspeed registered<br />
<6>TCP hybla registered<br />
<6>TCP htcp registered<br />
<6>TCP vegas registered<br />
<6>TCP scalable registered<br />
<6>NET: Registered protocol family 1<br />
<6>NET: Registered protocol family 17<br />
<4>Welcome to PF_RING 3.2.1<br />
<4>(C) 2004-06 L.Deri <deri@ntop.org><br />
<6>NET: Registered protocol family 27<br />
<4>PF_RING: bucket length 128 bytes<br />
<4>PF_RING: ring slots 4096<br />
<4>PF_RING: sample rate 1 [1=no sampling]<br />
<4>PF_RING: capture TX No [RX only]<br />
<4>PF_RING: transparent mode Yes<br />
<4>PF_RING initialized correctly.<br />
<4>PF_RING: registered /proc/net/pf_ring/<br />
<6>802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com><br />
<6>All bugs added by David S. Miller <davem@redhat.com><br />
<0>decode 1f02<br />
<4>VFS: Mounted root (squashfs filesystem) readonly.<br />
<6>Mounted devfs on /dev<br />
<6>Freeing unused kernel memory: 188k freed<br />
<3>br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.<br />
</pre></div>Cfaulkner