Difference between pages "Install/pt-br/Network" and "Steam"

< Install‎ | pt-br(Difference between pages)
(Configuring your network)
 
m (Steam segfaults after 2nd start!)
 
Line 1: Line 1:
=== Configurando sua rede ===
+
Steam is a content delivery system for linux gaming.
  
É importante assegurar-se de que você será capaz de se conectar a sua rede de área local (local-area network) depois que você reinicializar no Funtoo Linux. There are three approaches you can use for configuring your network: NetworkManager, dhcpcd, and the [[Funtoo Linux Networking]] scripts. Here's how to choose which one to use based on the type of network you want to set up.
+
== install part 1 ==
 
+
funtoo & gentoo have ebuilds in the gamerlay overlay. the steam-meta ebuild was removed.
==== Wi-Fi ====
+
===== Using NetworkManager =====
+
For laptop/mobile systems where you will be using Wi-Fi and connecting to various networks, NetworkManager is strongly recommended. The Funtoo version of NetworkManager is fully functional even from the command-line, so you can use it even without X or without the Network Manager applet. Here are the steps involved in setting up NetworkManager:
+
  
 
<console>
 
<console>
(chroot) # ##i##emerge linux-firmware
+
###i## layman -a gamerlay
(chroot) # ##i##emerge networkmanager
+
###i## layman -S
(chroot) # ##i##rc-update add NetworkManager default
+
###i## emerge steam-launcher
 
</console>
 
</console>
  
Above, we installed linux-firmware which contains a complete collection of available firmware for many hardware devices including Wi-Fi adapters, plus NetworkManager to manage our network connection. Then we added NetworkManager to the <code>default</code> runlevel so it will start when Funtoo Linux boots.
+
== install part 2 ==
 +
steam has its own internal package management system.  Portage will not track its files, or games installed.  the ebuild simply pulls in the steam installer, to run the steam installer:
  
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:
+
<console>###i## /usr/bin/steam</console>
  
{{Note|The following command will not work as long as you are in chroot environment. The reason for this is that addwifi will need dbus and rfkill to be set up. So don't forget to reboot!}}
+
the installer will prompt you with several questions, once done running the installer command will load the latest version of steam.
  
 +
== Troubleshooting ==
 +
=== Steam segfaults after 2nd start! ===
 +
I do not know much about this behaviour, but I found a workaround.
 
<console>
 
<console>
# ##i##addwifi -S wpa -K 'wifipassword' mywifinetwork
+
$ ##i##mkdir -p ~/backup
 +
$ ##i##mv ~/.local/share/Steam/steamapps ~/backup
 +
$ ##i##steam --reset
 +
$ ##i##mv ~/backup ~/.local/share/Steam/steamapps
 
</console>
 
</console>
 
+
It resets all the Steam settings (except that were in Steam Cloud), but does not delete games.
The <code>addwifi</code> command is used to configure and connect to a WPA/WPA2 Wi-Fi network named <code>mywifinetwork</code> with the password <code>wifipassword</code>. This network configuration entry is stored in <code>/etc/NetworkManager/system-connections</code> so that it will be remembered in the future. You should only need to enter this command once for each Wi-Fi network you connect to.
+
 
+
===== Using wpa_supplicant =====
+
If for some reason you don't want to use a tool such as NetworkManager or <code>wicd</code>, you can use wpa_supplicant for wireless network connections.
+
 
+
First, emerge wpa_supplicant:
+
 
+
<console>
+
(chroot) ###i## emerge -a wpa_supplicant
+
</console>
+
 
+
Now, edit the wpa_supplicant configuration file, located at /etc/wpa_supplicant/wpa_supplicant.conf.
+
The syntax is very easy:
+
<pre>
+
network={
+
ssid="MyWifiName"
+
psk="lol42-wifi"
+
}
+
 
+
network={
+
ssid="Other Network"
+
psk="6d96270004515a0486bb7f76196a72b40c55a47f"
+
}
+
</pre>
+
 
+
You will need to add both <code>wpa_supplicant</code> and <code>dhcpcd</code> to the default runlevel. <code>wpa_supplicant</code> will connect to your access point, and <code>dhcpcd</code> will acquire an IP address via DHCP:
+
 
+
<console>
+
(chroot) # ##i##rc-update add dhcpcd default
+
(chroot) # ##i##rc-update add wpa_supplicant default
+
</console>
+
 
+
==== Desktop (Wired Ethernet) ====
+
 
+
For a home desktop or workstation with wired Ethernet that will use DHCP, the simplest and most effective option to enable network connectivity is to simply add <code>dhcpcd</code> to the default runlevel:
+
 
+
<console>
+
(chroot) # ##i##rc-update add dhcpcd default
+
</console>
+
 
+
When you reboot, <code>dhcpcd</code> will run in the background and manage all network interfaces and use DHCP to acquire network addresses from a DHCP server.
+
 
+
==== Server (Static IP) ====
+
 
+
For servers, the [[Funtoo Linux Networking]] scripts are recommended. They are optimized for static configurations and things like virtual ethernet bridging for virtualization setups. See [[Funtoo Linux Networking]] for information on how to use Funtoo Linux's template-based network configuration system.
+

Revision as of 16:43, March 5, 2015

Steam is a content delivery system for linux gaming.

install part 1

funtoo & gentoo have ebuilds in the gamerlay overlay. the steam-meta ebuild was removed.

# layman -a gamerlay
# layman -S
# emerge steam-launcher

install part 2

steam has its own internal package management system. Portage will not track its files, or games installed. the ebuild simply pulls in the steam installer, to run the steam installer:

# /usr/bin/steam

the installer will prompt you with several questions, once done running the installer command will load the latest version of steam.

Troubleshooting

Steam segfaults after 2nd start!

I do not know much about this behaviour, but I found a workaround.

$ mkdir -p ~/backup
$ mv ~/.local/share/Steam/steamapps ~/backup
$ steam --reset
$ mv ~/backup ~/.local/share/Steam/steamapps

It resets all the Steam settings (except that were in Steam Cloud), but does not delete games.