https://wiki.archlinux.org/api.php?action=feedcontributions&user=LeCrayonVert&feedformat=atomArchWiki - User contributions [en]2024-03-28T21:04:26ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Steam&diff=290498Steam2013-12-26T18:04:34Z<p>LeCrayonVert: Fix package name.</p>
<hr />
<div>[[Category:Gaming]]<br />
[[Category:Wine]]<br />
[[ja:Steam]]<br />
[[zh-CN:Steam]]<br />
{{Related articles start}}<br />
{{Related|Wine}}<br />
{{Related|Steam/Game-specific troubleshooting}}<br />
{{Related articles end}}<br />
From [[Wikipedia:Steam (software)|Wikipedia]]:<br />
: ''Steam is a digital distribution, digital rights management, multiplayer and communications platform developed by Valve Corporation. It is used to distribute games and related media online, from small independent developers to larger software houses.''<br />
<br />
[http://store.steampowered.com/about/ Steam] is best known as the platform needed to play Source Engine games (e.g. Half-Life 2, Counter-Strike). Today it offers many games from many other developers.<br />
<br />
== Native Steam on Linux ==<br />
<br />
{{Note|<br />
* Arch Linux is '''not''' [https://support.steampowered.com/kb_article.php?ref&#61;1504-QHXN-8366 officially supported].<br />
* Because the Steam client is a 32-bit application, you will need to enable the [[multilib]] repository if you have a 64-bit system. It may also make sense to install {{Grp|multilib-devel}} to provide some important multilib libraries. You also most likely need to install the 32-bit version of your graphics driver to run Steam.<br />
}}<br />
<br />
Steam can be installed with the package {{Pkg|steam}}, available in the [[official repositories]]. If you have a 64-bit system, enable the [[multilib]] repository first.<br />
<br />
Steam is not supported on this distribution. As such some fixes are needed on the users part to get things functioning properly:<br />
<br />
*Steam makes heavy usage of the Arial font. A decent Arial font to use is {{Pkg|ttf-liberation}} or one of the official Microsoft fonts packages containing Arial: {{AUR|ttf-microsoft-arial}}, {{AUR|ttf-ms-win8}},{{AUR|ttf-office-2007-fonts}}, {{AUR|ttf-win7-fonts}} or {{AUR|ttf-ms-fonts}}. See [[MS Fonts]] for more details. Asian languages require {{Pkg|wqy-zenhei}} to display properly.<br />
<br />
*Most games require {{Pkg|libtxc_dxtn}} and {{Pkg|lib32-libtxc_dxtn}} when using mesa drivers, so it is recommended to install these packages.<br />
<br />
*Several games have dependencies which may be missing from your system. If a game fails to launch (often without error messages) then make sure all of the libraries listed in [[Steam/Game-specific troubleshooting]] are installed. <br />
<br />
=== Troubleshooting ===<br />
<br />
{{Note|<br />
* In addition to being documented here, any bug/fix/error should be, if not already, reported on Valve's bug tracker on their [https://github.com/ValveSoftware/steam-for-linux GitHub page].<br />
* Connection problems may occur when using DD-WRT with peer-to-peer traffic filtering.<br />
}}<br />
<br />
==== GUI problems with KDE ====<br />
<br />
: Valve GitHub [https://github.com/ValveSoftware/steam-for-linux/issues/594 issue 594]<br />
<br />
If you are using KDE and you have problems with the GUI (such as lag or random crashes), in KDE system settings, go to ''Workspace Appearance and Behaviour > Desktop Effects > Advanced''. Change "Compositing type" from "XRender" to "OpenGL".<br />
<br />
==== The close button only minimizes the window ====<br />
<br />
: Valve GitHub [https://github.com/ValveSoftware/steam-for-linux/issues/1025 issue 1025]<br />
<br />
To close the Steam window (and remove it from the taskbar) when you press '''x''', but keep Steam running in the tray, set the environment variable {{ic|STEAM_FRAME_FORCE_CLOSE}} to {{ic|1}}. You can do this by launching Steam using the following command.<br />
$ STEAM_FRAME_FORCE_CLOSE=1 steam<br />
<br />
==== Flash not working on 64-bit systems ====<br />
<br />
: Steam Support [https://support.steampowered.com/kb_article.php?ref=1493-GHZB-7612 article]<br />
<br />
First ensure {{Pkg|lib32-flashplugin}} is installed. It should be working at this point, if not create a local Steam Flash plugin folder:<br />
$ mkdir ~/.steam/bin32/plugins/<br />
and set a symbolic link to the global lib32 flash plugin file in your upper new folder<br />
$ ln -s /usr/lib32/mozilla/plugins/libflashplayer.so ~/.steam/bin32/plugins/<br />
<br />
==== Text is corrupt or missing ====<br />
<br />
The Steam Support [https://support.steampowered.com/kb_article.php?ref=1974-YFKL-4947 instructions] for Windows seem to work on Linux also: Simply download [https://support.steampowered.com/downloads/1974-YFKL-4947/SteamFonts.zip SteamFonts.zip] and install them (copying to {{ic|~/.fonts/}} works at least).<br />
<br />
==== Error on some games: black textures/S3TC support is missing ====<br />
<br />
Install the following dependencies:<br />
* {{Pkg|libtxc_dxtn}}<br />
* {{Pkg|lib32-libtxc_dxtn}}<br />
<br />
==== SetLocale('en_US.UTF-8') fails at game startup ====<br />
<br />
Uncomment {{ic|en_US.UTF-8 UTF-8}} in {{ic|/etc/locale.gen}} and then run {{ic|locale-gen}} as root.<br />
<br />
==== Could not find required OpenGL entry point 'glGetError' ====<br />
<br />
Make sure you are running the "libgl" for your video card driver. Im my case I had to replace {{Pkg|lib32-mesa-libgl}} with {{Pkg|lib32-nvidia-libgl}}. This only works with proprietary Nvidia drivers.<br />
$ sudo pacman -Rdds lib32-mesa-libgl && sudo pacman -Syu lib32-nvidia-libgl<br />
<br />
==== The game crashes immediately after start ====<br />
<br />
If your game crashes immediately after start, try to disable "Steam Community In-Game": Open the game properties and unset "Enable Steam Community In-Game" (under General).<br />
<br />
==== Considerable lag with Intel-based graphics cards on certain games ====<br />
<br />
If Steam seems to work otherwise well, but certain games that work well on Windows are unplayable due to lag, launch Steam from a console and look for these errors:<br />
<br />
libGL error: failed to load driver: i965<br />
libGL error: Try again with LIBGL_DEBUG=verbose for more details.<br />
<br />
This means that the 32 bit driver is not properly loaded. This can be fixed by installing {{Pkg|lib32-intel-dri}}:<br />
<br />
$ sudo pacman -S lib32-intel-dri<br />
<br />
=== Launching games with custom commands, such as Bumblebee/Primus ===<br />
<br />
Steam has fortunately added support for launching games using your own custom command. To do so, navigate to the Library page, right click on the selected game, click Properties, and Set Launch Options. Steam replaces the tag {{ic|%command%}} with the command it actually wishes to run. For example, to launch Team Fortress 2 with primusrun and at resolution 1920x1080, you would enter:<br />
<br />
primusrun %command% -w 1920 -h 1080<br />
<br />
If you are running the [[Linux-ck]] kernel, you may have some success in reducing overall latencies and improving performance by launching the game in SCHED_ISO (low latency, avoid choking CPU) via {{Pkg|schedtool}}<br />
<br />
# schedtool -I -e %command% ''other arguments''<br />
<br />
==== Killing standalone compositors when launching games ====<br />
<br />
Further to this, utilising the {{ic|%command%}} switch, you can kill standalone compositors (such as Xcompmgr or [[Compton]]) - which can cause lag and tearing in some games on some systems - and relaunch them after the game ends by adding the following to your game's launch options.<br />
<br />
killall compton && %command%; nohup compton &<br />
<br />
Replace {{ic|compton}} in the above command with whatever your compositor is. You can also add -options to {{ic|%command%}} or {{ic|compton}}, of course.<br />
<br />
Steam will latch on to any processes launched after {{ic|%command%}} and your Steam status will show as in game. So in this example, we run the compositor through {{ic|nohup}} so it is not attached to Steam (it will keep running if you close Steam) and follow it with an ampersand so that the line of commands ends, clearing your Steam status.<br />
<br />
=== Using native runtime ===<br />
<br />
Steam, by default, ships with a copy of every library it uses, packaged within itself, so that games can launch without issue. This can be a resource hog, and the slightly out-of-date libraries they package may be missing important features (Notably, the OpenAL version they ship lacks HRTF and surround71 support). To use your own system libraries, you can run Steam with:<br />
<br />
STEAM_RUNTIME=0 steam<br />
<br />
However, if you're missing any libraries Steam makes use of, this will fail to launch properly. An easy way to find the missing libraries is to run the following commands:<br />
<br />
cd ~/.local/share/Steam/ubuntu12_32<br />
LD_LIBRARY_PATH=".:${LD_LIBRARY_PATH}" ldd $(file *|sed '/ELF/!d;s/:.*//g')|grep 'not found'|sort|uniq<br />
<br />
Note that the libraries will have to be 32-bit, which means you may have to download some from the AUR if on x86_64, such as NetworkManager.<br />
<br />
Once you've done this, run steam again with STEAM_RUNTIME=0 steam and verify it's not loading anything outside of the handful of steam support libraries:<br />
<br />
cat /proc/$(pidof steam)/maps|sed '/\.local/!d;s/.* //g'|sort|uniq<br />
<br />
=== Skins for Steam ===<br />
<br />
The Steam interface can be fully customized by copying its various interface files in its skins directory and modifying them.<br />
<br />
==== Steam skin manager ====<br />
<br />
The process of applying a skin to Steam can be greatly simplified using {{AUR|steam-skin-manager}} from the AUR. The package also comes with a hacked version of the Steam launcher which allows the window manager to draw its borders on the Steam window.<br />
<br />
As a result, skins for Steam will come in two flavors, one with and one without window buttons. The skin manager will prompt you whether you use the hacked version or not, and will automatically apply the theme corresponding to your GTK+ theme if it is found. You can of course still apply another skin if you want.<br />
<br />
The package ships with two themes for the default Ubuntu themes, Ambiance and Radiance. A Faience theme is under development and already has its own package on the AUR {{AUR|steam-skin-faience-git}}.<br />
<br />
== Steam on Wine ==<br />
<br />
Install Wine as described in [[Wine]].<br />
<br />
Install the required Microsoft fonts: {{AUR|ttf-microsoft-tahoma}} and {{AUR|ttf-ms-fonts}} from the [[AUR]]. You can also install these fonts through [[Wine#Winetricks|Winetricks]]: {{ic|winetricks corefonts}}.<br />
{{Note|If you have access to Windows discs, you may want to install {{AUR|ttf-ms-win8}} or {{AUR|ttf-win7-fonts}} instead.}}<br />
<br />
=== Installation ===<br />
<br />
Download and run the Steam installer from [http://store.steampowered.com/about/ steampowered.com]. It is a {{ic|.msi}} file so you have to start it with {{ic|msiexec}}: <br />
$ msiexec /i SteamInstall.msi<br />
<br />
=== Starting Steam ===<br />
<br />
On x86:<br />
$ wine ~/.wine/drive_c/Program\ Files/Steam/Steam.exe<br />
<br />
On x86_64:<br />
$ wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe<br />
<br />
{{Note|<br />
*If text is not rendered (properly), append {{ic|-no-dwrite}} to this command. See [[#No text rendered problem]] for more information.<br />
*If you are using an Nvidia card through [[Bumblebee]], you should prefix this command with {{ic|optirun}}.<br />
}}<br />
<br />
You should consider making an alias to easily start Steam (and put it in your shell's rc file), example:<br />
alias steam-wine='wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe >/dev/null 2>&1 &'<br />
<br />
=== Tips ===<br />
<br />
==== Performance ====<br />
<br />
Consider disabling wine debugging output by adding this to your shell rc file:<br />
export WINEDEBUG=-all<br />
or, just add it to your {{ic|steam-wine}} alias to only disable it for Steam:<br />
alias steam-wine='WINEDEBUG=-all wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe >/dev/null 2>&1 &'<br />
Additionally, Source games rely on a paged pool memory size specification for audio, and WINE by default does not have this set. To set it:<br />
$ wine reg add "HKLM\\System\\CurrentControlSet\\Control\\Session Manager\\Memory Management\\" /v PagedPoolSize /t REG_DWORD /d 402653184 /f<br />
<br />
==== Source engine launch options ====<br />
<br />
Go to ''Properties > Set Launch Options'', e.g.:<br />
-console -dxlevel 90 -width 1280 -height 1024<br />
* {{ic|console}}<br />
: Activate the console in the application to change detailed applications settings.<br />
* {{ic|dxlevel}}<br />
: Set the application's DirectX level, e.g. 90 for DirectX Version 9.0. It is recommended to use the video card's DirectX version to prevent crashes. See the official Valve Software wiki https://developer.valvesoftware.com/wiki/DirectX_Versions for details.<br />
* {{ic|width}} and {{ic|height}}<br />
: Set the screen resolution. In some cases the graphic settings are not saved in the application and the applications always starts in the default resolution.<br />
Please refer to https://developer.valvesoftware.com/wiki/Command_Line_Options for a complete list of launch options.<br />
<br />
==== Using a pre-existing Steam installation ====<br />
<br />
If you have a shared drive with Windows, or already have a Steam installation somewhere else, you can simply symlink the Steam directory to {{ic|~/.wine/drive_c/Program Files/Steam/}} . However, be sure to do '''all''' the previous steps in this wiki. Confirm Steam launches and logs into your account, ''then'' do this:<br />
<br />
$ cd ~/.wine/drive_c/Program\ Files/ <br />
$ mv Steam/ Steam.backup/ (or you can just delete the directory)<br />
$ ln -s /mnt/windows_partition/Program\ Files/Steam/<br />
<br />
{{Note|<br />
* If you have trouble starting Steam after symlinking the entire Steam folder, try linking only the {{ic|steamapps}} subdirectory in your existing wine steam folder instead.<br />
* If you still have trouble starting games, use {{ic|# mount --bind /path/to/SteamApps ~/.local/share/Steam/SteamApps -ouser&#61;your-user-name }}, this is the only thing that worked for me with {{ic|TF2}}.<br />
}}<br />
<br />
==== Steam links in Firefox, Chrome, etc ====<br />
<br />
To make {{ic|steam://}} urls in your browser connect with Steam in Wine, there are several things you can do. One involves making steam url-handler keys in gconf, another involves making protocol files for KDE, others involve tinkering with desktop files or the Local State file for Chromium. These seem to only work in Firefox or under certain desktop configurations. One way to do it that works more globally is using mimeo, a tool made by Xyne (an Arch TU) which follows. For another working and less invasive (but Firefox-only) way, see the first post [http://ubuntuforums.org/showthread.php?t=433548 here] .<br />
<br />
* Make {{ic|/usr/bin/steam}} with your favorite editor and paste:<br />
<br />
{{bc|<br />
#!/bin/sh<br />
#<br />
# Steam wrapper script<br />
#<br />
exec wine "c:\\program files\\steam\\steam.exe" "$@"<br />
}}<br />
<br />
* Make it executable:<br />
<br />
# chmod +x /usr/bin/steam<br />
<br />
* Install {{AUR|mimeo}} and {{AUR|xdg-utils-mimeo}} from AUR. You will need to replace the existing {{Pkg|xdg-utils}} if installed. In XFCE, you will also need {{Pkg|xorg-utils}}.<br />
<br />
* Create {{ic|~/.config/mimeo.conf}} with your favorite editor and paste:<br />
<br />
{{bc|<br />
/usr/bin/steam %u<br />
^steam://<br />
}}<br />
<br />
* Lastly, open {{ic|/usr/bin/xdg-open}} in your favorite editor. Go to the {{ic|detectDE()}} section and change it to look as follows:<br />
<br />
{{bc|<nowiki><br />
detectDE()<br />
{<br />
#if [ x"$KDE_FULL_SESSION" = x"true" ]; then DE=kde;<br />
#elif [ x"$GNOME_DESKTOP_SESSION_ID" != x"" ]; then DE=gnome;<br />
#elif $(dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetNameOwner string:org.gnome.SessionManager > /dev/null 2>&1) ; then DE=gnome;<br />
#elif xprop -root _DT_SAVE_MODE 2> /dev/null | grep ' = \"xfce4\"$' >/dev/null 2>&1; then DE=xfce;<br />
#elif [ x"$DESKTOP_SESSION" == x"LXDE" ]; then DE=lxde;<br />
#else DE=""<br />
#fi<br />
DE=""<br />
}<br />
</nowiki>}}<br />
<br />
* Restart the browser and you should be good to go. In Chromium, you cannot enter a {{ic|steam://}} link in the url box like you can with Firefox. The forum link above has a {{ic|steam://open/friends}} link to try if needed.<br />
<br />
{{Note|<br />
* If you have any problems with file associations after doing this, simply revert to regular xdg-utils and undo your changes to {{ic|/usr/bin/xdg-open}}.<br />
* Those on other distributions that stumble upon this page, see the link above for firefox specific instructions. No easy way to get it working on Chromium on other distros exists.<br />
}}<br />
<br />
==== No text rendered problem ====<br />
<br />
If there is no text/font rendered when starting steam you should try to start steam with the parameter {{ic|-no-dwrite}}. Read more in [https://bbs.archlinux.org/viewtopic.php?id=146223 the forum thread about it.]<br />
{{bc|wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe -no-dwrite}}<br />
<br />
{{Note|It is important to note that although this method does currently work, It is not persistent if Steam relaunches automatically (i.e. update), or if you follow a URL link. <br />
*This can be achieved by going through '''''winecfg > Libraries''''' and setting the '''"dwrite"''' override to ''"disable"''<br />
'''Or'''<br />
*{{ic|$ wine reg add 'HKCU\Software\Valve\Steam' /v DWriteEnable /t REG_DWORD /d 00000000}}<br />
}}<br />
<br />
== See also ==<br />
<br />
* https://wiki.gentoo.org/wiki/Steam<br />
* [http://appdb.winehq.org/objectManager.php?sClass=version&iId=19444 Wine Application Database]</div>LeCrayonVerthttps://wiki.archlinux.org/index.php?title=Synchronization_and_backup_programs&diff=128155Synchronization and backup programs2011-01-15T10:05:52Z<p>LeCrayonVert: </p>
<hr />
<div>{{i18n|Backup_Programs}}<br />
<br />
== Intro ==<br />
<br />
This wiki page contains information about various backup programs. It's a good idea to ''have'' regular backups of important data, most notably configuration files (<tt>/etc/*</tt>) and local pacman database (usually <tt>/var/lib/pacman/local/*</tt>).<br />
<br />
Few words to end the introduction: before you start trying programs out, try to think about your needs, e.g. consider the following questions:<br />
* What backup medium do I have available?<br />
** cd / dvd<br />
** remote server (With what access? Ssh? Can I install some software on it (necessary for e.g. rsync-based solutions)?)<br />
** external harddrive<br />
* How often do I plan to backup?<br />
** daily?<br />
** weekly?<br />
** less often?<br />
* What goodies do I expect from the backup solution?<br />
** compression? (what algorithms?)<br />
** encryption? (gpg or something more straightforward?)<br />
* Most importantly: how do I plan to restore backups if needed?<br />
<br />
All right, enough with this, let's see some options!<br />
<br />
== Incremental backups ==<br />
<br />
The point with these is that they remember what has been backed up during the last run, and back up only what has changed. Great if you back up often.<br />
<br />
=== Rsync-type backups ===<br />
The main characteristic of this type of backups is that they maintain a copy of the directory you want to keep a backup of, in a traditional "mirror" fashion.<br />
<br />
Certain rsync-type packages also do snapshot backups by storing files which describe the how the contents of files and folders changed from the last backup (the so-called 'diffs'). Hence, they are inherently incremental, but usually they don't have compression/encryption. On the other hand, a working copy of everything is immediately available, no decompression/decryption needed. Finally the way it works makes it hard to burn backups to cd/dvd..<br />
<br />
===== CLI =====<br />
*[[rsync]] (in extra repo)<br />
**rsync almost always makes a mirror of the source<br />
**Impossible to restore a full backup before the most recent backup (but you can use --backup to keep old versions of the files)<br />
**Standard install on all distros<br />
**Can run over SSH (port 22) or native rsync protocol (port 873)<br />
**Win32 version available<br />
*[http://www.nongnu.org/rdiff-backup/ rdiff-backup] (in community repo)<br />
**Stores most recent backup as regular files<br />
**To revert to older versions, you apply the diff files to recreate the older versions<br />
**It is granularly incremental (delta backup), it only stores changes to a file; will not create a new copy of a file upon change<br />
**Required python and librsync<br />
**Win32 version available<br />
*[http://www.rsnapshot.org rsnapshot] (in community repo) <br />
**Does not store diffs, instead it copies entire files if they have changed<br />
**Creates hard links between a series of backed-up trees (snapshots)<br />
**It is differential in that the size of the backup is only the original backup size plus the size of all files that have changed since the last backup.<br />
**Destination filesystem must support hard links<br />
**Requires perl<br />
**Win32 version available<br />
*[http://safekeep.sourceforge.net/ SafeKeep] (in AUR)<br />
**Enhancement to rdiff-backup<br />
**Integrates with Linux LVM and databases to create consistent backups<br />
**Bandwidth throttling<br />
* [http://www.scottlu.com/Content/Link-Backup.html Link-Backup] ([http://aur.archlinux.org/packages.php?ID=16929 AUR] may be patched with additional features) is similar to rsync based scripts, but does not use rsync<br />
** Creates hard links between a series of backed-up trees (snapshots)<br />
** Intelligently handles renames, moves, and duplicate files without additional storage or transfer<br />
** dstdir/.catalog is a catalog of all unique file instances; backup trees hard-link to the catalog<br />
** Transfer occurs over standard I/O locally or remotely between a client and server instance of this script<br />
** It copies itself to the server; it does not need to be installed on the server<br />
** Requires SSH for remote backups<br />
** It resumes stopped backups; it can even be told to run for n minutes<br />
<br />
===== GUI =====<br />
*[http://backintime.le-web.org/ Back In Time] (in [http://aur.archlinux.org/packages.php?ID=23002 AUR])<br />
**Creates hard links between a series of backed-up trees (snapshots)<br />
**Inspired by FlyBack and TimeVault<br />
**Really is just a front-end to rsync, diff, cp<br />
**A new snapshot is created only if something changed since the last snapshot<br />
*[http://www.flyback-project.org/ FlyBack] (in [http://aur.archlinux.org/packages.php?ID=14575 AUR])<br />
**A clone of Apple's Mac OS X Time Machine software<br />
*[http://areca.sourceforge.net/ Areca Backup] (in [http://aur.archlinux.org/packages.php?ID=13637 AUR])<br />
**Written in Java<br />
**Primarily archive-based (ZIP), but will do file-based backup as well<br />
**Claims delta backup supported (stores only changes)<br />
*[https://wiki.ubuntu.com/TimeVault TimeVault]<br />
**Creates hard links between a series of backed-up trees (snapshots)<br />
**Imitates Windows Volume Shadow Copy feature in that it integrates with Nautilus to provide a "Previous Versions" tab in the Properties dialog.<br />
*[http://luckybackup.sourceforge.net/index.html Luckybackup] (in [http://aur.archlinux.org/packages.php?ID=23121 AUR])<br />
**Luckybackup it's an easy program to backup and sync your files.<br />
**It is written in Qt and C++<br />
**It has Sync,Backup (with include and exclude options),Restore operations,Remote connection backup,Scheduled backups,Command line mode and more abilities.<br />
<br />
=== Not rsync-based ===<br />
<br />
They tend to create (big) archive files (like tar.bz2), and (of course) keep track of what's been archived. Now creating tar.bz2 or tar.gz archives has the advantage that you can extract the backups with just tar/bzip2/gzip, so you don't need to have the backup program around.<br />
<br />
* [http://aur.archlinux.org/packages.php?ID=4351 backup-manager] (in AUR); [http://www.backup-manager.org/ homepage] Backup Manager is a command line backup tool for GNU/Linux, designed to help you make daily archives of your file system. Written in bash and perl, it can make archives in lots of open formats (tar, gzip, bzip2, lzma, dar, zip) and provides lots of interesting features (such as network exports or CD/DVD automated-burning). The program is designed to be as easy to use as possible and is popular with desktop users and sysadmins. The whole backup process is defined in one full-documented configuration file which needs no more than 5 minutes to tune for your needs. It just works. Archives are kept for a given number of days and the upload system can use ftp or scp to transfer the generated archives to a list of remote hosts. Gettext is used for internationalization.<br />
** 1 configuration file, 5 minutes setup<br />
** Manually invoke backup process or run daily unattended via CRON<br />
** Backup files, MySQL databases and Subversion repositories<br />
** Specify multiple targets to backup at once (/etc, /home, etc…)<br />
** Ability to exclude files from backup<br />
** Automatically purge old backups<br />
** Full backup only or Full + Incremental backup<br />
** Backup to an attached disk, LAN or Internet<br />
** Burns backup to CD/DVD with MD5 checksum verification<br />
** Archives in lots of open formats: tar, gzip, bzip2, lzma, dar, zip<br />
** Slice archives to 2 GB if using dar archives format<br />
** Backup over SSH<br />
** Encrypts archives<br />
** Offsite remote upload of archives via FTP, SSH, RSYNC or Amazon S3<br />
** Can run with different configuration files concurrently<br />
** Easy external hooks<br />
**Simply uncompressed the open format backup archives with any command line or GUI tool<br />
<br />
* [[Backup with arch-backup|arch-backup]] (in community repo); [http://code.google.com/p/archlinux-stuff/ website]); trivial backup scripts with simple configuration:<br />
** compression method can be configured<br />
** possible to specify more directories to backup<br />
<br />
* [[Backup with hdup|hdup]] (in extra repo; [http://miek.nl/projects/hdup2/ website]; it's no longer developed, the author develops rdup now (below); but it's still a decent one):<br />
** creates tar.gz or tar.bz2 archives<br />
** supports gpg encryption<br />
** supports pushing over ssh<br />
** possible to specify more directories to backup<br />
<br />
* [http://miek.nl/projects/rdup rdup] (in [http://aur.archlinux.org/packages.php?ID=3728 AUR]) successor to hdup: the program *just determines* which files have changed since the last backup. It's completely up to you what do you want to do with that list. Some helper scripts are supplied, and with them it supports:<br />
** creating tar.gz archives '''or''' rsync-type copy<br />
** encryption (gpg and usual strong (eg. blowfish)), also applies for rsync-type copy<br />
** compression (also for rsync-type copy)<br />
<br />
* [http://www.nongnu.org/duplicity/ duplicity] is simple command-line utilty which allows encrypted compressed incremental backup to nearly any storage. For even simpler usage there is [http://sourceforge.net/projects/ftplicity/ duply] frontend.<br />
** supports gpg encryption and signing<br />
** supports gzip compression<br />
** supports full or incremental backups, incremental backup stores only difference between new and old file<br />
** supports pushing over ftp, ssh/scp, rsync, WebDAV, WebDAVs, HSi and Amazon S3 or local filesystem<br />
<br />
* [http://dar.linux.free.fr/ dar] (in community repo): <br />
** it uses its own format for archives (so you need to have it around when you want to restore)<br />
** supports splitting backups into more files by size<br />
** makefile-type config files, some custom scripts are available along with it<br />
** supports basic encryption (not gpg; but also strong, but you need to supply a password every time)<br />
** some gui tools for inspecting backups are also available (kdar, in [http://aur.archlinux.org/packages.php?ID=7586 AUR], but current dar needs beta version)<br />
** a script suitable for running from cron is [http://sarab.sourceforge.net/ sarab] (in [http://aur.archlinux.org/packages.php?ID=17044 AUR]): supports pretty much any backup scheme (Towers of Hanoi, Grandfather-Father-Son, etc..)<br />
<br />
* [http://sourceforge.net/projects/backerupper/ backerupper] (in [http://aur.archlinux.org/packages.php?ID=17441 AUR]) Backerupper is a simple program for backing up selected directories over a local network. Its main intended purpose is backing up a user's personal data.<br />
** GUI based<br />
** creating tar.gz archives<br />
** possible to define : backup frequency, backup time, Max copies<br />
<br />
* [http://trac.manent-backup.com/ Manent] (in [http://aur.archlinux.org/packages.php?ID=19241 AUR]) is an algorithmically strong backup and archival program. It's Python based and has the following features:<br />
** Efficient backup to anything that looks like a storage<br />
** Works well over a slow and unreliable network<br />
** Offers online access to the contents of the backup<br />
** Backed up storage is completely encrypted<br />
** Several computers can use the same storage for backup, automatically sharing data<br />
** Not reliant on timestamps of the remote system to detect changes<br />
** Cross-platform support for Unicode file names<br />
<br />
=== Cloud backups ===<br />
<br />
* [http://www.getdropbox.com Dropbox] (in [http://aur.archlinux.org/packages.php?ID=19615 AUR] with Gnome support, and also [http://aur.archlinux.org/packages.php?ID=23363 AUR] without Gnome dependencies). <br />
** A daemon monitors a specified directory, and uploads incremental changes to Dropbox.com. <br />
** Changes automatically show up on your other computers. <br />
** Includes file sharing and a public directory. <br />
** You can recover deleted files. <br />
** Community written add-ons. <br />
** Free accounts have 2GB storage.<br />
<br />
* [http://www.jungledisk.com/ Jungle Disk] (in [http://aur.archlinux.org/packages.php?ID=15015 AUR])<br />
** Automatic backups to Amazon's servers.<br />
** Not free, but very low prices.<br />
<br />
== Not incremental backups ==<br />
* [http://k7z.sourceforge.net/ Q7Z] (in [http://aur.archlinux.org/packages.php?ID=12822 AUR]) is a P7Zip GUI for Linux, which attempts to simplify data compression and backup. It can create the following archive types: 7z, BZip2, Zip, GZip, Tar. Use Q7Z if you want to:<br />
** Update existing archives quickly<br />
** Backup multiple folders to a storage location<br />
** Create or extract protected archives<br />
** Lessen effort by using archiving profiles and lists<br />
* "Just copy everything into one big archive, but support writing to cd/dvd"-type: [http://www2.backup-manager.org/ backup-manager] (in [http://aur.archlinux.org/packages.php?ID=4351 AUR])<br />
* [[Partclone]] -- back up and restore only the used blocks of a partition<br />
* [http://redobackup.org/ Redo Backup and Recovery] - a nice liveCD that uses xPUD for the GUI and partclone for the backend.<br />
* filesystem-backup -- simple bash script (was originally a MySQL backup script) that creates a rolling 7 days, rolling 4 weeks and static monthly backups in tar format. Good for servers without a GUI. Available in repo: http://repo.falconn.nl/any/<br />
* [http://clonezilla.org/ Clonezilla]<br />
**Boots from live CD, USB flash drive, or PXE server<br />
**Uses Partimage, ntfsclone, partclone, and dd, <br />
**Compatability with many file systems (ext2, ext3, ext4, reiserfs, xfs, jfs of GNU/Linux, FAT, NTFS, and HFS+)<br />
**Multicasting server to restore to many machines at once<br />
**If file system is supported , only used blocks in harddisk are saved and restored. For unsupported file system, sector-to-sector copy is done<br />
* [http://www.partimage.org/Main_Page Partimage]<br />
*[http://www.fsarchiver.org/Main_Page Fsarchiver] (in extra repo)<br />
**Support for basic file attributes (permissions, owner, ...)<br />
**Support for multiple file-systems per archive<br />
**Support for extended attributes (they are used by SELinux)<br />
**Support the basic file-system attributes (label, uuid, block-size) for all linux file-systems<br />
**Support for [http://www.fsarchiver.org/Cloning-ntfs ntfs filesystems] (ability to create flexible clones of windows partitions)<br />
**Checksumming of everything which is written in the archive (headers, data blocks, whole files)<br />
**Ability to restore an archive which is corrupt (it will just skip the current file)<br />
**Multi-threaded lzo, gzip, bzip2, lzma [[Compression|compression]]: if you have a dual-core / quad-core it will use all the power of your cpu<br />
**Lzma [[Compression|compression]] (slow but very efficient algorithm) to make your archive smaller.<br />
**Support for splitting large archives into several files with a fixed maximum size<br />
**Encryption of the archive using a password. Based on blowfish from libcrypto from openssl.<br />
**Support backup of a mounted root filesystem (-A option)<br />
<br />
*[http://www.mondorescue.org/ Mondo Rescue]<br />
**Image-based backups, supporting Linux/Windows, I don't think it cares much about filesystems. Backs up MBR too, along with partition layout.<br />
**Compression rate adjustable<br />
**Can backup live systems (without having to halt it, unlike most, e.g. Clonezilla).<br />
**Can split image over as many as you want (just set the size for a CD - 700 MB to backup to CD, etc.).<br />
**Supports booting to a "live cd", in a sense, to perform a full restore.<br />
**Can backup/restore over NFS, cd's, tape drives and what not.<br />
**Can verify backups<br />
**Neat-o ncurses interface. Plus a free progressbar!<br />
**Customizable to all kinds of ends<br />
**Can get a bit confusing/time consuming to get up and running, and verify everything works.<br />
== Versioning systems ==<br />
<br />
These are traditionally used for keeping track of software development; but if you want to have a simple way to manage your config files in one directory, it might be a good solution.<br />
<br />
* [http://www.selenic.com/mercurial/wiki/ mercurial] or [http://git.or.cz/ git] (both in extra repo)<br />
* [http://eigenclass.org/hiki/gibak-backup-system-introduction gibak]: a backup system based on git. it also supports binary diffs (for binaries, e-books, pictures, multimedia files, etc). on the homepage there is a short usage advice. it is meant to backup only the $HOME directory. one could also backup other directories (like /etc) by changing the $HOME variable to point to that directory (though i don't really recommend this). gibak is handy for people who are familiar with git. it uses .gitignore to filter files and one can use the git commands to restore files, browse through logs, diffs, etc. if one needs a gui, it is also possible to use gitk or qgit to browse through commits or do whatever these interfaces support. get it from AUR: http://aur.archlinux.org/packages.php?ID=18318.<br />
== External Resources ==<br />
<br />
* [http://www.halfgaar.net/backing-up-unix Backing up Linux and other Unix(-like) systems]<br />
* [http://www.askapache.com/security/mirror-using-rsync-ssh.html Mirroring an Entire Site using Rsync over SSH]<br />
<br />
[[Category:System recovery (English)]]</div>LeCrayonVerthttps://wiki.archlinux.org/index.php?title=AMD_Catalyst&diff=115846AMD Catalyst2010-08-29T08:26:21Z<p>LeCrayonVert: /* Archive repositories */</p>
<hr />
<div>[[Category: Graphics (English)]]<br />
[[Category: X Server (English)]]<br />
[[Category: HOWTOs (English)]]<br />
{{i18n|ATI Catalyst}}<br />
{{Article summary start}}<br />
{{Article summary text|An overview of ATI's proprietary "Catalyst" video card driver.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|ATI}}<br />
{{Article summary wiki|Intel}}<br />
{{Article summary wiki|NVIDIA}}<br />
{{Article summary wiki|Xorg}}<br />
{{Article summary heading|Resources}}<br />
{{Article summary link|cchtml.com - Unofficial Wiki for the ATI Linux Driver|http://wiki.cchtml.com/index.php/Main_Page}}<br />
{{Article summary link|Unofficial ATI Linux Driver Bugzilla|http://ati.cchtml.com/query.cgi}}<br />
{{Article summary end}}<br />
Formerly known as ''fglrx'', ATI has rebranded their proprietary Linux driver, which is now known as ''Catalyst''. Currently, only the package name has changed, while the kernel module retains its original ''fglrx'' name, therefore any mention of fglrx below is specifically in reference to the kernel module, ''not the package.''<br />
<br />
==Naming conventions==<br />
ATI's [[Wikipedia:Radeon|Radeon]] brand follows a naming scheme that relates each product to a market segment. Within this article, readers will see both ''product'' names (e.g. HD 4850, X1900) and ''code'' or ''core'' names (e.g. RV770, R580). Traditionally, a ''product series'' will correspond to a ''core series'' (e.g. the "X1000" product series includes the X1300, X1600, X1800, and X1900 products which utilize the "R500" core series &ndash; including the RV515, RV530, R520, and R580 cores).<br />
<br />
For a table of core and product series, see [[Wikipedia:Comparison of AMD graphics processing units]].<br />
<br />
== Supported devices ==<br />
Since v. '''9.4''', the proprietary ATI driver '''supports only R600 and newer devices''' (that means, '''HD2xxx''' and '''newer'''). For older cards, you can only use '''xf86-video-ati'''.<br />
<br />
== Installation ==<br />
Catalyst was once a precompiled package offered by Arch in the <code>extra</code> repository, but as of March 2009, official support has been dropped because of dissatisfaction with the quality and speed of development of the proprietary driver. The [http://aur.archlinux.org/packages.php?ID=29111 catalyst driver] is available on AUR.<br />
<br />
=== Stock and Custom Kernels ===<br />
<br />
You can build [http://aur.archlinux.org/packages.php?ID=29111 AUR's catalyst] package via [[makepkg]] (recommended) or by using popular AUR's packages manager like bauerbill/yaourt.<br />
<br />
{{Note| You may get an error about the Catalyst package conflicting with ''libgl''. In that case, run the following code to remove libgl without checking dependencies (Catalyst provides libgl package, so this is safe):<br />
# pacman -Rd libgl<br />
After doing this you can install catalyst package using ie. # pacman -U /patch/to/builded/catalyst_package.tar.xz}}<br />
<br />
After installing package you probably need to configure xorg. Using provided '''aticonfig''' tool is recommended:<br />
<pre><br />
# aticonfig --initial<br />
(or for Dual Head: # aticonfig --initial=dual-head)<br />
# aticonfig -v<br />
</pre><br />
And add '''nomodeset''' to your kernel line in /boot/grub/menu.lst , ie.:<br />
<code>kernel /boot/vmlinuz26 root=/dev/sda1 ro nomodeset</code><br />
Plus add '''fglrx''' to the MODULES list in /etc/rc.conf."<br />
<br />
You may now reboot your system, or just load fglrx module with:<br />
# modprobe fglrx<br />
and restart/start X.<br />
<br />
Now if you have got x86_64 architecture system and want to use some 32-bit opengl programs or wine games you will have to install [http://aur.archlinux.org/packages.php?ID=24824 AUR's lib32-catalyst-utils]<br />
<br />
Since version 10.6 arch's catalyst package is providing simple script/command called '''catalyst_build_module''' which is able to compile and install fglrx module for every kernel you are using. This command is called with every catalyst's package install/update.<br />
You may also run it manually as root to build fglrx module for kernel you are currently running.<br />
<br />
If you are using '''more than one kernel''' - you can simply build fglrx module for whatever kernel you've got without even booting that kernel, do it as root with this command:<br />
# catalyst_build_module ''kernel_version''<br />
where ''kernel_version'' is version of kernel for which you want to build fglrx module, more precise example:<br />
# catalyst_build_module 2.6.35-rc4-rc<br />
<br />
You may also use this command:<br />
# catalyst_build_module all<br />
to build fglrx module for every working system's kernel.<br />
<br />
Use '''catalyst_build_module remove''' command to remove every unused fglrx module:<br />
# catalyst_build_module remove<br />
<br />
catalyst_build_module is storing all informations about compilling/installig fglrx module in '''log''' file placed in /var/log/catalys-install.log. But you don't need to remember it, you will be informed about that fact whenever installation fails.<br />
<br />
If you '''aren't using stock kernel''' (kernel26) at all - you can remove it from dependency array (depends=) in catalyst's PKGBUILD.<br />
<br />
''If you need more information on catalyst, visit [http://bbs.archlinux.org/viewtopic.php?id=57084 this thread] or create a new one, and ask there.''<br />
<br />
<br />
==== Automatic re-compilation of fglrx module with every kernel update (important) ====<br />
<br />
Since version 10.7-3 catalyst is '''optionally''' providing 'automatic re-compilation of fglrx module with every kernel update' functionality. It is done by a '''fglrx hook''' on [[mkinitcpio]] with combination of forcing to update package '''kernel26-headers''' in first place.<br />
<br />
The hook will call '''catalyst_build_module''' command to update fglrx module for the version of your new kernel, and additionally it will call '''catalyst_build_module remove''' command to remove unneeded flgrx module(s).<br />
<br />
This auto re-compilation functionality is '''bypassing Arch Way by making entries in system's config files''' (adding fglrx to HOOKS list of /etc/mkinitcpio.conf and adding kernel26-headers to SyncFirst list of /etc/pacman.conf) so it cannot be enabled by default. '''Although it's recommended to use this feature''' - especially for people who like comfort or for those who aren't sure will they remember to run 'catalyst_build_module new_kernel_version' after every main kernel update.<br />
<br />
It's very easy to enable this functionality, just run this command as root:<br />
# catalyst_build_module auto<br />
You can also turn it off with:<br />
# catalyst_build_module autooff<br />
<br />
{{Note| If you are using this functionality it's '''important''' to look at the installation process of kernel26 (or any other kernel) package. fglrx hook will tell you is everything all right.}}<br />
{{Note| If your '''custom kernel''' is using some '''non-standard mkinitcpio configuration file''' (ie. kernel26-zen is using /etc/mkinitcpio-zen.conf) you'll have to manually add '''fglrx''' to HOOKS array so it can be auto-recompiled with kernel's update.}}<br />
{{Note| If you '''aren't using stock kernel26''' at all and still wanna use auto recompilation you should remove kernel26-headers from SyncFirst list of /etc/pacman.conf after running 'catalyst_build_module auto'.}}<br />
<br />
===== Troubleshooting =====<br />
There is some '''disadvantage of using automatic re-compilation''' - but should exist only with catalyst < 10.7-2 when kernel26 got some main update (ie. 2.6.34->2.6.35, not 2.6.34.1->2.6.34.2) because package kernel26-headers is installed after kernel26 installation, and so fglrx hook have no headers to build fglrx module. In that situation run:<br />
# catalyst_build_module ''new_kernel_version''<br />
ie. # catalyst_build_module 2.6.35-ARCH<br />
just after main kernel26/kernel26-headers update.<br />
<br />
=== Catalyst's repositories ===<br />
<br />
There are some unofficial repositories containing the newest (or older) catalyst packages along with the appropriate libs and software in order to use the driver.<br />
<br />
{{Note| If you want to know what packages are inside any given repository you need to first add repository to pacman.conf and then list repository with pacman -Sl command, ie.:<br />
# pacman -Sl catalyst<br />
}}<br />
<br />
==== [xorg18] repository ====<br />
Catalyst '''isn't working with current xorg-server 1.9''' (checked also with IgnoreAbi flag) which has just landed in [testing] repository and will be moved to mainline in some short time - that's the reason why [xorg18] repo with xserver 1.8 and some additional packages arrived.<br />
To use it you need edit /etc/pacman.conf and add those lines above all other repositories:<br />
<br />
For i686 systems:<br />
[xorg18]<br />
Server = http://catalyst.apocalypsus.net/repo/xorg18/i686<br />
<br />
For x86_64 systems:<br />
[xorg18]<br />
Server = http://catalyst.apocalypsus.net/repo/xorg18/x86_64<br />
<br />
After doing it use this command:<br />
pacman -Suu<br />
<br />
==== Main repository ====<br />
There is a repository called '''[catalyst]''' which contains '''newest stable catalyst driver''' and some additional packages like '''patched xorg-server'''.<br />
This repository should now work with any kernel and with multiple-kernels systems (read [http://wiki.archlinux.org/index.php/ATI_Catalyst#Stock_and_Custom_Kernels Stock and Custom Kernels] section) and it is updated most frequently.<br />
To use it you need as root:<br />
<br />
'''1)''' Edit /etc/pacman.conf and add those lines above all other repositories:<br />
<br />
For i686 systems:<br />
[catalyst]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/i686<br />
<br />
For x86_64 systems:<br />
[catalyst]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/x86_64<br />
<br />
ie. for x86_64 systems pacman.conf should look like:<br />
<br />
(...)<br />
[catalyst]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/x86_64<br />
[core]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
[extra]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
(...)<br />
<br />
'''2)''' Update repositories and packages with:<br />
# pacman -Syy<br />
# pacman -Suu<br />
<br />
'''3)''' Remove libgl package and install catalyst:<br />
# pacman -Rd libgl<br />
# pacman -S catalyst<br />
<br />
'''4)''' '''Don't forget''' to prepare your /etc/X11/xorg.conf for catalyst. Use aticonfig --initial if you don't have prepared xorg.conf.<br />
Also add fglrx module to MODULES array in /etc/rc.conf<br />
<br />
'''5) Reboot'''<br />
<br />
[catalyst] repo brings package called '''catalyst-module-only''' which provides working fglrx module for stock ARCH kernel. It is directed to people who are getting problems with compilation.<br />
Note versioning of this package - ie. '''10.7'''-'''34''' is telling with which catalyst (here '''10.7''') it is working and which ARCH stock kernel (here 2.6.'''34'''-ARCH) it supports.<br />
<br />
For '''x86_64''' users '''[catalyst]''' provides lib32-catalyst-utils package needed to run 32-bit opengl applications and wine games.<br />
<br />
Repository also contains '''xvba-video''' package so you may easily use '''video acceleration''' described [http://wiki.archlinux.org/index.php/ATI_Catalyst#Video_acceleration below].<br />
<br />
<br />
===== Troubleshooting =====<br />
<br />
====== Black/grey/white boxes/artifacts mainly in firefox/thunderbird ======<br />
With catalyst 10.6 AMD/ATi announce new method of 2D acceleration for radeons, that funcionality has fixed problems with maximizing/resizing windows. Unfortunately this step causes bugs for some users. To turn on old (slower xaa) method of 2d rendering please kill your desktop environment and Xserver and type this command as root:<br />
aticonfig --set-pcs-str=DDX,ForceXAA,TRUE<br />
<br />
If you do that '''it's better to use one of patched xorg-server packages''' delivered by [catalyst] repository.<br />
<br />
'''[catalyst]''' repository contains [http://catalyst.apocalypsus.net/tarball/xorg-server-backclear.tar.gz xorg-server-backclear] (patched with backclear patch) and [http://aur.archlinux.org/packages.php?ID=36328 xorg-server-1.8-'''catalyst-maximize-fix'''] (patched with fedora patch) packages. Both this patches are fixing problems with '''maximizing/resizing''' but they are doing it in different way - you may choose which patched xserver is best for you. To remove xorg-server and install xorg-server-backclear just type:<br />
# pacman -Rd xorg-server<br />
# pacman -S xorg-server-backclear<br />
Similar with xorg-server-1.8-catalyst-maximize-fix.<br />
<br />
====== Xserver segmentation fault ======<br />
Rebuild your xorg.conf with:<br />
aticonfig --initial<br />
or: <br />
aticonfig --initial --force<br />
(if its still not woking then remove /etc/X11/xorg.conf and use one of these two commands mentioned above)<br />
<br />
====== Keyboard/mouse not working ======<br />
Please remember that old hal's input config''' doesn't work with new xorg-server'''.<br />
<br />
Well it should work out of the box with provided with xorg-server 1.8 package files: /etc/X11/xorg.conf.d/'''10-evdev.conf''' and /etc/X11/xorg.conf.d/'''10-quirks.conf'''<br />
but it could happen that's not working / fitting to you so read more here [http://wiki.archlinux.org/index.php/Xorg Arch's Xorg wiki] or here [https://fedoraproject.org/wiki/Input_device_configuration Fedora's wiki for Input device configuration] but don't forget that in archlinux we are using '''/etc/X11/xorg.conf.d''' directory instead of fedora's /etc/xorg.conf.d<br />
<br />
{{Warning| '''Do not''' add any new xserver Section into your /etc/X11/xorg.conf - this file is still used by catalyst - i mean ie dont add any Section "InputClass" into xorg.conf because when you do this both aticonfig and amdcccle wont start cause of parsing xorg.conf error (just use /etc/X11/xorg.conf.d directory for it)}}<br />
<br />
==== Archive repositories ====<br />
<br />
'''[catalyst-10.7]''' repository works fine with any kernel < 2.6.36 rc2 and with multiple-kernels systems (read [http://wiki.archlinux.org/index.php/ATI_Catalyst#Stock_and_Custom_Kernels Stock and Custom Kernels] section). <br />
<br />
For '''x86_64''' users '''[catalyst]''' provides lib32-catalyst-utils package (which should work fine with '''[multilib] repository''') needed to run 32-bit opengl applications and wine games.<br />
<br />
For i686:<br />
[catalyst-10.7]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/i686<br />
For x86_64:<br />
[catalyst-10.7]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/x86_64<br />
<br />
Repository also contains '''xvba-video''' package so you may easily use '''video acceleration''' described [http://wiki.archlinux.org/index.php/ATI_Catalyst#Video_acceleration below].<br />
<br />
Troubleshooting for this repository is the same as for [http://wiki.archlinux.org/index.php/ATI_Catalyst#Troubleshooting_2 main one].<br />
<br />
<br />
'''[catalyst-10.5]''' repository works fine with 2.6.34-ARCH kernel and xserver 1.8. xorg-server package here is patched with backclear patch, and xorg-server-1.8-catalyst-maximize-fix package is patched with fedora's backfill patch.<br />
<br />
For i686:<br />
[catalyst-10.5]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/i686<br />
For x86_64:<br />
[catalyst-10.5]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/x86_64<br />
<br />
<br />
{{Note| Archive repositories listed below '''work only with kernel 2.6.33-ARCH and xserver 1.7'''. You may find xserver 1.7 packages in '''[xorg17]''' repository mentioned below. If you are using kernel other than 2.6.33-ARCH please use one of [http://catalyst.apocalypsus.net/tarball/ archive tarballs] to build catalyst for your kernel.<br />
}}<br />
<br />
<br />
'''[xorg17] repository''' contains xserver 1.7 packages, use it only if you are experiencing problems with newer xserver 1.8.<br />
<br />
'''[xorg17]''' repository contains [http://catalyst.apocalypsus.net/tarball/xorg-server-1.7-backclear.tar.gz xorg-server-backclear] (patched with backclear patch) and [http://aur.archlinux.org/packages.php?ID=35686 xorg-server-1.7-catalyst-maximize-fix] (patched with fedora patch) packages. Both this patches fix problems with '''maximizing/resizing''' but they are doing it in different way - you may choose which patched xserver is best for you. To remove xorg-server and install xorg-server-backclear just type:<br />
# pacman -Rd xorg-server<br />
# pacman -S xorg-server-backclear<br />
Similar with xorg-server-1.7-catalyst-maximize-fix<br />
<br />
To use [xorg17] repo please put those lines at the top of all other repositories in '''/etc/pacman.conf''':<br />
<br />
For i686:<br />
[xorg17]<br />
Server = http://catalyst.apocalypsus.net/repo/xorg17/i686<br />
<br />
For x86_64:<br />
[xorg17]<br />
Server = http://catalyst.apocalypsus.net/repo/xorg17/x86_64<br />
<br />
<br />
'''catalyst-10.6''' works well with xserver-1.7, got opengl 3.3/4 support, brings new 2D acceleration support, got some problems with gamma, wine games, and texturing in basing on q3a engine games:<br />
<br />
For i686:<br />
[catalyst-10.6]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/i686<br />
<br />
For x86_64:<br />
[catalyst-10.6]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/x86_64<br />
<br />
<br />
If you are experiencing known bugs/errors (ie. lots of artifacts) with catalyst 10.6 you may still use older '''catalyst-10.5''' or '''catalyst-10.4''' or '''catalyst-10.3''' repositories.<br />
<br />
'''catalyst-10.5''' and '''catalyst-10.4''' repositories contain [http://aur.archlinux.org/packages.php?ID=26687 xorg-server] (for this repositories patched with backclear patch) and [http://aur.archlinux.org/packages.php?ID=35686 xorg-server-1.7-catalyst-maximize-fix] (patched with fedora patch) packages. Both this patches fix problems with '''maximizing/resizing''' but they are doing it in different way - you may choose which patched xserver is best for you. To remove xorg-server and install xorg-server-1.7-catalyst-maximize-fix just type:<br />
# pacman -Rd xorg-server<br />
# pacman -S xorg-server-1.7-catalyst-maximize-fix<br />
<br />
<br />
'''catalyst-10.5''' works well with xserver-1.7, got opengl 3.3/4 support, but still got some problems with gamma, wine games, and texturing in basing on q3a engine games:<br />
<br />
For i686:<br />
[catalyst-10.5]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/i686<br />
<br />
For x86_64:<br />
[catalyst-10.5]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/x86_64<br />
<br />
'''catalyst-10.5''' repository also contains '''libva-sds''', '''mplayer-vaapi''' and '''xvba-video''' packages so you may easily use '''video acceleration''' described [http://wiki.archlinux.org/index.php/ATI_Catalyst#Video_acceleration below].<br />
<br />
<br />
If you don't like catalyst-10.5 you may still use older '''catalyst 10.4''' which work well with xserver-1.7, but still got some problems with gamma and wine games:<br />
<br />
For i686:<br />
[catalyst-10.4]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/i686<br />
<br />
For x86_64:<br />
[catalyst-10.4]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/x86_64<br />
<br />
<br />
Or '''catalyst-10.3'''. Catalyst 10.3 is still using old''' xserver 1.6''', which is also provided by '''[catalyst-10.3]''' repository.<br />
<br />
To use '''catalyst-10.3''' you need as root:<br />
<br />
'''1)''' Edit /etc/pacman.conf and add those lines above all other repositories:<br />
For i686:<br />
[catalyst-10.3]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/i686<br />
<br />
For x86_64:<br />
[catalyst-10.3]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/x86_64<br />
<br />
'''2)''' Sync and downgrade packages with this commands<br />
# pacman -Syy<br />
# pacman -Suu<br />
<br />
'''3)''' Remove xf86-video-ati and ati-dri packages if you have them installed.<br />
<br />
'''4)''' (Recommended) If you dont like speed of xorg-server - remove it:<br />
# pacman -Rd xorg-server<br />
and try xorg-server-catalyst-maximize-fix:<br />
# pacman -S xorg-server-catalyst-maximize-fix<br />
<br />
'''5)''' Remove libgl and install catalyst:<br />
# pacman -Rd libgl<br />
# pacman -S catalyst<br />
'''6)''' '''Don't forget''' to prepare your /etc/X11/xorg.conf for catalyst. Use aticonfig --initial if you don't have prepared xorg.conf.<br />
Also add fglrx module to MODULES array in /etc/rc.conf<br />
<br />
'''7)''' Reboot<br />
<br />
=== ATI/AMD Installer ===<br />
{{Warning| Using the installer from ati.com/amd.com is NOT recommended for inexperienced users! Doing so may cause file conflicts and X failures. The packages available through pacman are configured specifically for Arch Linux and so should be used instead.}}<br />
<br />
If you have attempted a manual install from the official installer, and are finding that nothing works correctly anymore, there should be an uninstall script placed at /usr/share/ati - run that, then try the pacman packages.<br />
<br />
If you ''must'' use the installer from ATI/AMD for some reason, the following steps '''might''' work for you:<br />
<br />
*Download AMD/ATI driver installer from the official site only.<br />
*Make it executable.<br />
*Execute a terminal emulator (e.g Konsole) and be root.<br />
*Install mesa package<br />
pacman -S mesa<br />
*(Re)Install Xorg <br />
*Check for other required things for ATI/AMD installer listed on their website<br />
#pacman -Q | grep NameOfPackage<br />
*Use aticonfig as described below to update xorg.conf<br />
*Add ModulesPath into xorg.conf pointing at fglrx.so module if necessary<br />
<br />
== Configuration ==<br />
ATI provides the <code>aticonfig</code> tool to create new basic <code>xorg.conf</code> file or modify an existing <code>xorg.conf</code> file and configure essentially every aspect of the card. For a complete list of <code>aticonfig</code> options, run:<br />
$ aticonfig --help<br />
<br />
If you want to create new xorg.conf file with specific for your system options, run the following command to generate one:<br />
# Xorg -configure<br />
<br />
{{Warning| '''Xorg -configure''' isn't actually recommended - sometimes it doesn't work good with catalyst and could cause your Xserver to break at start with black screen of death. So use it only if you are 100% sure of what you are doing. In most cases '''aticonfig --initiall''' mentioned below should build working xorg.conf file and Xserver should automatically and correctly detect all your input devices.}}<br />
<br />
The simplest way to use <code>aticonfig</code> to adapt your <code>xorg.conf</code> file is listed in the examples at the end of the output if you run <code>aticonfig</code> without any command-line parameters:<br />
Examples:<br />
1. Setting up fglrx for the first time.<br />
Single head : aticonfig --initial --input=/etc/X11/xorg.conf<br />
Dual head : aticonfig --initial=dual-head --screen-layout=above<br />
This command will generate a dual head configuration<br />
file with the second screen located above the first<br />
screen.<br />
<br />
Just adapt one of those two lines for your personal setup.<br />
<br />
{{Warning| Please check the generated xorg.conf file before you copy it to /etc/X11/xorg.conf and happily startx or reboot. Otherwise, you'll probably get a locked blank screen and won't be able to use your system anymore.}} The config files generated by preceding steps are sometimes incorrect. If you want, you can compare the generated files to one of the [http://wiki.archlinux.org/index.php?title=Xorg7#Sample_Xorg.conf_Files Sample Xorg.conf files] listed on the Xorg wiki page.<br />
<br />
Please ensure that in the "Screen" section you have "DefaultDepth 24" and there is a "DRI" section with "Mode 666" in it. The fglrx driver needs those lines to work, but the generated files by preceding programs don't have it. Without those lines, you might get an unresponsive black screen after reboot. Besides, since most of the parts are now automatically detected in modern Xorg, you don't need to write so many things in xorg.conf as you did before with ancient Xorg versions.<br />
So, some config sections/values in the generated xorg.conf are redundant.<br />
<br />
Here is a minimal working example:<br />
<pre><br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "dbe"<br />
Load "xtrap"<br />
Load "record"<br />
Load "dri"<br />
Load "glx"<br />
Load "GLcore"<br />
Load "freetype"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "fglrx"<br />
VendorName "ATI Technologies Inc"<br />
BoardName "Radeon Mobility X1400"<br />
BusID "PCI:1:0:0"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</pre><br />
<br />
Next, make sure the fglrx module and any needed agp modules are loaded. <br />
# modprobe fglrx <br />
<br />
Add them to the '''MODULES''' array of your /etc/rc.conf to ensure that they load when you boot. <br />
<br />
Finally, run Xorg with <code>startx</code> or by using GDM/KDM and verify that direct rendering is enabled by running the following command in a terminal:<br />
$ glxinfo | grep direct<br />
<br />
If it says "direct rendering: yes" then you're good to go! If the glxinfo command is not found, you may need to install the mesa package as well.<br />
<br />
{{Warning| In recent versions of Xorg, the paths of libs are changed. So, sometimes '''libGL.so''' cannot be correctly loaded even if it's installed. Don't forget to check this if your GL is not working. Please read "Troubleshooting" section for details.}}<br />
<br />
== Video acceleration ==<br />
'''[http://en.wikipedia.org/wiki/Video_Acceleration_API Video Acceleration API] (VA API)''' is an open source software library ("libVA") and API specification which enables and provides access to '''graphics hardware (GPU) acceleration''' for video processing on Linux and UNIX based operating systems.<br />
The main motivation for VA API is to enable hardware accelerated video decode at various entry-points (VLD, IDCT, Motion Compensation, deblocking) for the prevailing coding standards today (MPEG-2, MPEG-4 ASP/H.263, MPEG-4 AVC/H.264, and VC-1/WMV3).<br />
<br />
In November 2009, VA-API gained a new proprietary '''xvba-video''' backend which allows VA-API powered applications to take advantage of AMD Radeon's UVD2 chipsets via the [http://en.wikipedia.org/wiki/XvBA XvBA (X-Video Bitstream Acceleration API designed by AMD)] library.<br />
<br />
XvBA support and xvba-video is still under development, however in nowadays it is '''working very well in most cases''' and with '''mplayer''' (and mplayer front-ends), so feel free to check it. You have to build [http://aur.archlinux.org/packages.php?ID=31723 xvba-video] package and install mplayer-vaapi (available in community repository) & libva (available in extra repository) packages.<br />
Then just set your video player to use vaapi:gl as video output.<br />
<br />
Ie. for '''mplayer''':<br />
$ mplayer -vo vaapi:gl -va vaapi movie.avi<br />
<br />
Ie. for '''smplayer''':<br />
Options -> Preferences -> General -> Video (tab) -> Output driver: User Defined : vaapi:gl<br />
Options -> Preferences -> General -> Video (tab) -> Double buffering '''on'''<br />
Options -> Preferences -> Advanced -> Options for MPlayer -> Options: -va vaapi<br />
Options -> Preferences -> General -> General -> Screenshots -> Turn screenshots '''off'''<br />
<br />
Don't forget to enable v-sync in '''amdcccle''':<br />
3D -> More Settings -> Wait for vertical refresh = Always On<br />
<br />
Note: If you are using '''compiz/kwin''' please note that the only way to '''avoid video flickering''' is to watch videos in '''full-screen''', and only when '''Unredirect Fullscreen is off'''.<br />
<br />
In '''compiz''' you need to set '''Redirected Direct Rendering''' in General Options of ccsm.<br />
<br />
Its off by default in '''kwin''', but if you see flickering you need to add UnredirectFullscreen=off line to [Compositing] section in ~/.kde4/share/config/kwinrc file.<br />
<br />
If its still flickering try to disable this option in ccsm (or change UnredirectFullscreen=off to UnredirectFullscreen=on in kwinrc).<br />
<br />
=== Troubleshooting ===<br />
==== Problems with video colours ====<br />
You may still use vaapi:gl to avoid video flickering, but without video acceleration<br />
<br />
Run '''mplayer''' without '''-va vaapi''' switch.<br />
<br />
For '''smplayer''' remove '''-va vaapi''' from Options -> Preferences -> Advanced -> Options for MPlayer -> Options: -va vaapi<br />
<br />
Plus for '''smplayer''' you may now safely turn screenshots on.<br />
<br />
== Troubleshooting (catalyst) ==<br />
<br />
=== KWin and composite ===<br />
<br />
Use the XRender instead of OpenGL as Composite-Type for best performance! This even solves any artifacts!<br />
<br />
=== Rectangle/Checkerbox corruption with OpenGL programs ===<br />
''This was fixed in catalyst '' 8.9.'' It may occur though in later versions.''<br />
<br />
OpenGL programs like e.g. blender in windowed mode, show a rectangle/checkerbox corruption.<br />
This can be solved by using a Virtual display setting with a multiple of 64 bigger than your actual resolution like 1664 instead 1600 for width:<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Depth 24<br />
Virtual 1664 1200<br />
EndSubSection<br />
EndSection<br />
<br />
===Black screen with complete lockups / hangs after reboot or startx===<br />
<br />
==== Faulty or corrupted amdpcsdb database ====<br />
Fglrx and its Catalyst Control Center stores data on a database called '''amdpcsdb''', located under '''/etc/ati'''. It isn't human readable, but only parsable by Catalyst Control Center. Sometimes, after updates, the settings in there aren't compatible with the new version of fglrx, so you end up with a black screen when starting X. <br />
<br />
So, there is one thing to do.<br />
<br />
Boot to init3, add the number 3 at the end of the menu.lst kernel options:<br />
# rm /etc/ati/amdpcsdb<br />
and restart Xorg (or even reboot).<br />
<br />
{{Warning|Be careful. If you have saved settings through Catalyst Control Center, which are stored under that file, they may now have been lost. You should edit xorg.conf instead, by using '''aticonfig'''.}}<br />
<br />
Be careful though. '''aticonfig''' stores its settings in '''amdpcsdb''' database like Catalyst Control Center. If you want that they're stored in xorg.conf instead, each time you use the aticonfig tool, add '''--input=/etc/X11/xorg.conf''' in the end of the command options as well.<br />
<br />
==== Faulty ACPI hardware calls ====<br />
It is possible that fglrx doesn't cooperate well with the system's ACPI hardware calls, so it autodisables itself and there is no screen output. <br />
<br />
So try to run this:<br />
aticonfig --acpi-services=off<br />
<br />
==== nForce 4 Incompatibility ====<br />
Starting with 9.10 onward, the fglrx drivers are incompatible with nForce 4 chipsets. Use the open source drivers until a fix is created.<br />
<br />
See [http://ati.cchtml.com/show_bug.cgi?id=1794 bug report].<br />
<br />
===KDM disappears after logout===<br />
If you are running the '''catalyst''' proprietary driver and you get a console (tty1) instead of the expected KDM greeting when you log out, you must instruct KDM to restart the X server after each logout:<br />
$ sudo nano /usr/share/config/kdm/kdmrc<br />
<br />
Uncomment the following line under the section titled [X-:*-Core]:<br />
TerminateServer=True<br />
<br />
KDM should now appear when you log out of KDE.<br />
<br />
=== Bad screen resolution at login manager ===<br />
If the resolution for your login manager is for example 1600x1200 and you want 1280x1024 you can fix it by using a xorg.conf (newer X-servers using the open source drivers normally don't need a xorg.conf, so if you don't have a xorg.conf you need to create one). In the "Screen" section add a modes lines:<br />
Section "Screen"<br />
Identifier "aticonfig-Screen[0]-0"<br />
Device "aticonfig-Device[0]-0"<br />
Monitor "aticonfig-Monitor[0]-0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
Modes "1280x1024" "2048x1536"#<-add this line to change the default login screen resolution<br />
EndSubSection<br />
EndSection<br />
The first argument of modes is the resolution, which will be used by default. The second argument is the maximum resolution supported by your monitor. This is needed so that you are able to choose higher screen resolutions using for example the KDE systemsettings.<br />
<br />
===Direct Rendering Doesn't Work===<br />
This problem may occur when using the proprietary '''catalyst''' driver. <br />
<br />
{{Warning|Make sure that you own a '''R6xx''' ('''HD2xxx''') or newer card or the driver '''won't''' be enabled. You may encounter that error if you try to enable your display by using catalyst and a card older than the R6xx ones.}}<br />
<br />
{{Warning|This error would also appear if you haven't '''rebooted''' your system after the installation or upgrade of catalyst. The system needs to load the fglrx.ko module in order to make the driver work.}}<br />
<br />
If you have problem with direct rendering, run:<br />
$ LIBGL_DEBUG=verbose glxinfo > /dev/null<br />
at the command prompt. At the very start of the output, it'll usually give you a nice error message saying why you don't have direct rendering.<br />
<br />
Common errors, and their solutions, are:<br />
'''libGL error: XF86DRIQueryDirectRenderingCapable returned false'''<br />
<br />
* Ensure that you are loading the correct agp modules for your AGP chipset before you load the fglrx kernel module. To determine which agp modules you'll need, run <code>hwdetect --show-agp</code>, then ensure that all modules listed from that command are in the <code>MODULES=</code> array in rc.conf, '''before''' fglrx.<br />
'''libGL error: failed to open DRM: Operation not permitted'''<br />
'''libGL error: reverting to (slow) indirect rendering'''<br />
<br />
* For this, make sure you have the following section in your <code>xorg.conf</code> somewhere:<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
'''libGL: OpenDriver: trying /usr/lib/xorg/modules/dri//fglrx_dri.so'''<br />
'''libGL error: dlopen /usr/lib/xorg/modules/dri//fglrx_dri.so failed (/usr/lib/xorg/modules/dri//fglrx_dri.so: cannot open shared object file: No such file or directory)'''<br />
'''libGL error: unable to find driver: fglrx_dri.so'''<br />
<br />
* Something hasn't been installed correctly. If the paths in the error message are <code>/usr/X11R6/lib/modules/dri/fglrx_dri.so</code>, then ensure you've logged completely out of your system, then back in. If you're using a graphical login manager (gdm, kdm, xdm), ensure that /etc/profile is sourced every time you log in. This is usually accomplished by adding <code>source /etc/profile</code> into <code>~/.xsession</code> or <code>~/.xinitrc</code>, but may vary between login managers.<br />
<br />
* If the paths above in your error message _are_ <code>/usr/lib/xorg/modules/dri/fglrx_dri.so</code>, then something hasn't been correctly installed. Try reinstalling the <code>catalyst</code> package.<br />
<br />
Errors such as:<br />
'''fglrx: libGL version undetermined - OpenGL module is using glapi fallback'''<br />
could be caused by having multiple versions of <code>libGL.so</code> on your system. Run:<br />
$ sudo updatedb<br />
$ locate libGL.so<br />
<br />
This should return the following output:<br />
$ locate libGL.so<br />
/usr/lib/libGL.so<br />
/usr/lib/libGL.so.1<br />
/usr/lib/libGL.so.1.2<br />
$<br />
<br />
These are the only three libGL.so files you should have on your system. If you have any more (e.g. <code>/usr/X11R6/lib/libGL.so.1.2</code>), then remove them. This should fix your problem. <br />
<br />
You might not get any error to indicate that this is a problem. If you are using X11R7, make sure you do '''not''' have these files on your system:<br />
/usr/X11R6/lib/libGL.so.1.2<br />
/usr/X11R6/lib/libGL.so.1<br />
<br />
===Hibernate/Sleep Issues===<br />
<br />
==== Video fails to enter suspend/hibernate ====<br />
If <code>fglrx</code> returns an error when attempting to suspend through hibernate scripts, a solution may be to add the following line to your "Device" section in <code>/etc/X11/xorg.conf</code>, which should allow the <tt>fglrx</tt> module to enter suspend mode.<br />
Option "UseInternalAGPGart" "no"<br />
<br />
==== Video fails to resume from suspend2ram ====<br />
ATI's proprietary <tt>catalyst</tt> driver cannot resume from suspend if the framebuffer is enabled. To disable the framebuffer, add '''vga=0''' to your kernel options in <code>/boot/grub/menu.lst</code>, for example:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda2 ro '''''vga=0'''''<br />
initrd /kernel26.img<br />
<br />
===System Freezes/Hard locks===<br />
* To prevent system lockups, try adding the following lines to your fglrx "Device" section in <code>xorg.conf</code><br />
Option "UseInternalAGPGART" "no"<br />
Option "KernelModuleParm" "agplock=0" # AGP locked user pages: disabled<br />
<br />
{{Note|Neither option is necessary anymore since 8.24.18 because ATI has removed the internal AGP GART support from the driver.}}<br />
<br />
* As well, the <code>radeonfb</code> framebuffer drivers have been known in the past to cause problems of this nature. If your kernel has radeonfb support compiled in, you may want to try a different kernel and see if this helps. <br />
<br />
===Hardware Conflicts===<br />
Radeon cards used in conjunction with some versions of the nForce3 chipset (e.g. nForce 3 250Gb) won't have 3D acceleration. Currently the cause of this issue is unknown, but some sources indicate that it may be possible to get acceleration with this combination of hardware by booting Windows with the drivers from nVIDIA and then rebooting the system. This can be verified by issuing in a root console the following command:<br />
dmesg | grep agp<br />
<br />
If you get something similar to this (using an nForce3-based system)<br />
agpgart: Detected AGP bridge 0<br />
agpgart: Setting up Nforce3 AGP.<br />
agpgart: aperture base > 4G<br />
<br />
and also if issuing this command...<br />
tail -n 100 /var/log/Xorg.0.log | grep agp<br />
<br />
...gets something similar to:<br />
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENODEV"<br />
<br />
Then you have this bug.<br />
<br />
Some sources indicate that in some situations, downgrading the motherboard BIOS may help, but this cannot be verified in all cases. Also, a bad BIOS downgrade can render your hardware useless, so beware.<br />
<br />
See bug http://bugzilla.kernel.org/show_bug.cgi?id=6350 for more information and a potential fix.<br />
<br />
===Temporary hangs when playing video===<br />
This problem may occur when using the proprietary '''catalyst''' driver.<br />
<br />
If you experience temporary hangs lasting from a few seconds to several minutes occuring randomly during playback with mplayer, check /var/log/messages.log for output like:<br />
Nov 28 18:31:56 pandemonium [<c01c64a6>] ? proc_get_sb+0xc6/0x160<br />
Nov 28 18:31:56 pandemonium [<c01c64a6>] ? proc_get_sb+0xc6/0x160<br />
Nov 28 18:31:56 pandemonium [<f8bc628c>] ? ip_firegl_ioctl+0x1c/0x30 [fglrx]<br />
Nov 28 18:31:56 pandemonium [<c01c64a6>] ? proc_get_sb+0xc6/0x160<br />
Nov 28 18:31:56 pandemonium [<c0197038>] ? vfs_ioctl+0x78/0x90<br />
Nov 28 18:31:56 pandemonium [<c01970b7>] ? do_vfs_ioctl+0x67/0x2f0<br />
Nov 28 18:31:56 pandemonium [<c01973a6>] ? sys_ioctl+0x66/0x70<br />
Nov 28 18:31:56 pandemonium [<c0103ef3>] ? sysenter_do_call+0x12/0x33<br />
Nov 28 18:31:56 pandemonium [<c01c64a6>] ? proc_get_sb+0xc6/0x160<br />
Nov 28 18:31:56 pandemonium =======================<br />
<br />
Adding the nopat kerneloption to /boot/grub/menu.lst and rebooting fixed the problem at least for me.<br />
<br />
===After a kernel upgrade: X doesn't start/modprobe doesn't find fglrx===<br />
Reinstall the catalyst drivers.<br />
<br />
Or since catalyst 10.6-3 use:<br />
# catalyst_build_module<br />
<br />
===Catalyst 10.6/10.7 : black/grey/white boxes/artifacts in firefox/thunderbird===<br />
With catalyst 10.6 AMD/ATi announce new method of 2D acceleration for radeons, unfortunately this step causes bugs for some users. To turn on old (slower xaa) method of 2d rendering please kill your desktop environment and Xserver and type this command as root:<br />
aticonfig --set-pcs-str=DDX,ForceXAA,TRUE<br />
Now you'll probably need patched xorg-server to fix problems with resizing/maximizing windows, read about it ie. [http://wiki.archlinux.org/index.php/ATI_Catalyst#Black.2Fgrey.2Fwhite_boxes.2Fartifacts_mainly_in_firefox.2Fthunderbird here].</div>LeCrayonVerthttps://wiki.archlinux.org/index.php?title=AMD_Catalyst&diff=115845AMD Catalyst2010-08-29T08:24:36Z<p>LeCrayonVert: /* Archive repositories */</p>
<hr />
<div>[[Category: Graphics (English)]]<br />
[[Category: X Server (English)]]<br />
[[Category: HOWTOs (English)]]<br />
{{i18n|ATI Catalyst}}<br />
{{Article summary start}}<br />
{{Article summary text|An overview of ATI's proprietary "Catalyst" video card driver.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|ATI}}<br />
{{Article summary wiki|Intel}}<br />
{{Article summary wiki|NVIDIA}}<br />
{{Article summary wiki|Xorg}}<br />
{{Article summary heading|Resources}}<br />
{{Article summary link|cchtml.com - Unofficial Wiki for the ATI Linux Driver|http://wiki.cchtml.com/index.php/Main_Page}}<br />
{{Article summary link|Unofficial ATI Linux Driver Bugzilla|http://ati.cchtml.com/query.cgi}}<br />
{{Article summary end}}<br />
Formerly known as ''fglrx'', ATI has rebranded their proprietary Linux driver, which is now known as ''Catalyst''. Currently, only the package name has changed, while the kernel module retains its original ''fglrx'' name, therefore any mention of fglrx below is specifically in reference to the kernel module, ''not the package.''<br />
<br />
==Naming conventions==<br />
ATI's [[Wikipedia:Radeon|Radeon]] brand follows a naming scheme that relates each product to a market segment. Within this article, readers will see both ''product'' names (e.g. HD 4850, X1900) and ''code'' or ''core'' names (e.g. RV770, R580). Traditionally, a ''product series'' will correspond to a ''core series'' (e.g. the "X1000" product series includes the X1300, X1600, X1800, and X1900 products which utilize the "R500" core series &ndash; including the RV515, RV530, R520, and R580 cores).<br />
<br />
For a table of core and product series, see [[Wikipedia:Comparison of AMD graphics processing units]].<br />
<br />
== Supported devices ==<br />
Since v. '''9.4''', the proprietary ATI driver '''supports only R600 and newer devices''' (that means, '''HD2xxx''' and '''newer'''). For older cards, you can only use '''xf86-video-ati'''.<br />
<br />
== Installation ==<br />
Catalyst was once a precompiled package offered by Arch in the <code>extra</code> repository, but as of March 2009, official support has been dropped because of dissatisfaction with the quality and speed of development of the proprietary driver. The [http://aur.archlinux.org/packages.php?ID=29111 catalyst driver] is available on AUR.<br />
<br />
=== Stock and Custom Kernels ===<br />
<br />
You can build [http://aur.archlinux.org/packages.php?ID=29111 AUR's catalyst] package via [[makepkg]] (recommended) or by using popular AUR's packages manager like bauerbill/yaourt.<br />
<br />
{{Note| You may get an error about the Catalyst package conflicting with ''libgl''. In that case, run the following code to remove libgl without checking dependencies (Catalyst provides libgl package, so this is safe):<br />
# pacman -Rd libgl<br />
After doing this you can install catalyst package using ie. # pacman -U /patch/to/builded/catalyst_package.tar.xz}}<br />
<br />
After installing package you probably need to configure xorg. Using provided '''aticonfig''' tool is recommended:<br />
<pre><br />
# aticonfig --initial<br />
(or for Dual Head: # aticonfig --initial=dual-head)<br />
# aticonfig -v<br />
</pre><br />
And add '''nomodeset''' to your kernel line in /boot/grub/menu.lst , ie.:<br />
<code>kernel /boot/vmlinuz26 root=/dev/sda1 ro nomodeset</code><br />
Plus add '''fglrx''' to the MODULES list in /etc/rc.conf."<br />
<br />
You may now reboot your system, or just load fglrx module with:<br />
# modprobe fglrx<br />
and restart/start X.<br />
<br />
Now if you have got x86_64 architecture system and want to use some 32-bit opengl programs or wine games you will have to install [http://aur.archlinux.org/packages.php?ID=24824 AUR's lib32-catalyst-utils]<br />
<br />
Since version 10.6 arch's catalyst package is providing simple script/command called '''catalyst_build_module''' which is able to compile and install fglrx module for every kernel you are using. This command is called with every catalyst's package install/update.<br />
You may also run it manually as root to build fglrx module for kernel you are currently running.<br />
<br />
If you are using '''more than one kernel''' - you can simply build fglrx module for whatever kernel you've got without even booting that kernel, do it as root with this command:<br />
# catalyst_build_module ''kernel_version''<br />
where ''kernel_version'' is version of kernel for which you want to build fglrx module, more precise example:<br />
# catalyst_build_module 2.6.35-rc4-rc<br />
<br />
You may also use this command:<br />
# catalyst_build_module all<br />
to build fglrx module for every working system's kernel.<br />
<br />
Use '''catalyst_build_module remove''' command to remove every unused fglrx module:<br />
# catalyst_build_module remove<br />
<br />
catalyst_build_module is storing all informations about compilling/installig fglrx module in '''log''' file placed in /var/log/catalys-install.log. But you don't need to remember it, you will be informed about that fact whenever installation fails.<br />
<br />
If you '''aren't using stock kernel''' (kernel26) at all - you can remove it from dependency array (depends=) in catalyst's PKGBUILD.<br />
<br />
''If you need more information on catalyst, visit [http://bbs.archlinux.org/viewtopic.php?id=57084 this thread] or create a new one, and ask there.''<br />
<br />
<br />
==== Automatic re-compilation of fglrx module with every kernel update (important) ====<br />
<br />
Since version 10.7-3 catalyst is '''optionally''' providing 'automatic re-compilation of fglrx module with every kernel update' functionality. It is done by a '''fglrx hook''' on [[mkinitcpio]] with combination of forcing to update package '''kernel26-headers''' in first place.<br />
<br />
The hook will call '''catalyst_build_module''' command to update fglrx module for the version of your new kernel, and additionally it will call '''catalyst_build_module remove''' command to remove unneeded flgrx module(s).<br />
<br />
This auto re-compilation functionality is '''bypassing Arch Way by making entries in system's config files''' (adding fglrx to HOOKS list of /etc/mkinitcpio.conf and adding kernel26-headers to SyncFirst list of /etc/pacman.conf) so it cannot be enabled by default. '''Although it's recommended to use this feature''' - especially for people who like comfort or for those who aren't sure will they remember to run 'catalyst_build_module new_kernel_version' after every main kernel update.<br />
<br />
It's very easy to enable this functionality, just run this command as root:<br />
# catalyst_build_module auto<br />
You can also turn it off with:<br />
# catalyst_build_module autooff<br />
<br />
{{Note| If you are using this functionality it's '''important''' to look at the installation process of kernel26 (or any other kernel) package. fglrx hook will tell you is everything all right.}}<br />
{{Note| If your '''custom kernel''' is using some '''non-standard mkinitcpio configuration file''' (ie. kernel26-zen is using /etc/mkinitcpio-zen.conf) you'll have to manually add '''fglrx''' to HOOKS array so it can be auto-recompiled with kernel's update.}}<br />
{{Note| If you '''aren't using stock kernel26''' at all and still wanna use auto recompilation you should remove kernel26-headers from SyncFirst list of /etc/pacman.conf after running 'catalyst_build_module auto'.}}<br />
<br />
===== Troubleshooting =====<br />
There is some '''disadvantage of using automatic re-compilation''' - but should exist only with catalyst < 10.7-2 when kernel26 got some main update (ie. 2.6.34->2.6.35, not 2.6.34.1->2.6.34.2) because package kernel26-headers is installed after kernel26 installation, and so fglrx hook have no headers to build fglrx module. In that situation run:<br />
# catalyst_build_module ''new_kernel_version''<br />
ie. # catalyst_build_module 2.6.35-ARCH<br />
just after main kernel26/kernel26-headers update.<br />
<br />
=== Catalyst's repositories ===<br />
<br />
There are some unofficial repositories containing the newest (or older) catalyst packages along with the appropriate libs and software in order to use the driver.<br />
<br />
{{Note| If you want to know what packages are inside any given repository you need to first add repository to pacman.conf and then list repository with pacman -Sl command, ie.:<br />
# pacman -Sl catalyst<br />
}}<br />
<br />
==== [xorg18] repository ====<br />
Catalyst '''isn't working with current xorg-server 1.9''' (checked also with IgnoreAbi flag) which has just landed in [testing] repository and will be moved to mainline in some short time - that's the reason why [xorg18] repo with xserver 1.8 and some additional packages arrived.<br />
To use it you need edit /etc/pacman.conf and add those lines above all other repositories:<br />
<br />
For i686 systems:<br />
[xorg18]<br />
Server = http://catalyst.apocalypsus.net/repo/xorg18/i686<br />
<br />
For x86_64 systems:<br />
[xorg18]<br />
Server = http://catalyst.apocalypsus.net/repo/xorg18/x86_64<br />
<br />
After doing it use this command:<br />
pacman -Suu<br />
<br />
==== Main repository ====<br />
There is a repository called '''[catalyst]''' which contains '''newest stable catalyst driver''' and some additional packages like '''patched xorg-server'''.<br />
This repository should now work with any kernel and with multiple-kernels systems (read [http://wiki.archlinux.org/index.php/ATI_Catalyst#Stock_and_Custom_Kernels Stock and Custom Kernels] section) and it is updated most frequently.<br />
To use it you need as root:<br />
<br />
'''1)''' Edit /etc/pacman.conf and add those lines above all other repositories:<br />
<br />
For i686 systems:<br />
[catalyst]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/i686<br />
<br />
For x86_64 systems:<br />
[catalyst]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/x86_64<br />
<br />
ie. for x86_64 systems pacman.conf should look like:<br />
<br />
(...)<br />
[catalyst]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/x86_64<br />
[core]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
[extra]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
(...)<br />
<br />
'''2)''' Update repositories and packages with:<br />
# pacman -Syy<br />
# pacman -Suu<br />
<br />
'''3)''' Remove libgl package and install catalyst:<br />
# pacman -Rd libgl<br />
# pacman -S catalyst<br />
<br />
'''4)''' '''Don't forget''' to prepare your /etc/X11/xorg.conf for catalyst. Use aticonfig --initial if you don't have prepared xorg.conf.<br />
Also add fglrx module to MODULES array in /etc/rc.conf<br />
<br />
'''5) Reboot'''<br />
<br />
[catalyst] repo brings package called '''catalyst-module-only''' which provides working fglrx module for stock ARCH kernel. It is directed to people who are getting problems with compilation.<br />
Note versioning of this package - ie. '''10.7'''-'''34''' is telling with which catalyst (here '''10.7''') it is working and which ARCH stock kernel (here 2.6.'''34'''-ARCH) it supports.<br />
<br />
For '''x86_64''' users '''[catalyst]''' provides lib32-catalyst-utils package needed to run 32-bit opengl applications and wine games.<br />
<br />
Repository also contains '''xvba-video''' package so you may easily use '''video acceleration''' described [http://wiki.archlinux.org/index.php/ATI_Catalyst#Video_acceleration below].<br />
<br />
<br />
===== Troubleshooting =====<br />
<br />
====== Black/grey/white boxes/artifacts mainly in firefox/thunderbird ======<br />
With catalyst 10.6 AMD/ATi announce new method of 2D acceleration for radeons, that funcionality has fixed problems with maximizing/resizing windows. Unfortunately this step causes bugs for some users. To turn on old (slower xaa) method of 2d rendering please kill your desktop environment and Xserver and type this command as root:<br />
aticonfig --set-pcs-str=DDX,ForceXAA,TRUE<br />
<br />
If you do that '''it's better to use one of patched xorg-server packages''' delivered by [catalyst] repository.<br />
<br />
'''[catalyst]''' repository contains [http://catalyst.apocalypsus.net/tarball/xorg-server-backclear.tar.gz xorg-server-backclear] (patched with backclear patch) and [http://aur.archlinux.org/packages.php?ID=36328 xorg-server-1.8-'''catalyst-maximize-fix'''] (patched with fedora patch) packages. Both this patches are fixing problems with '''maximizing/resizing''' but they are doing it in different way - you may choose which patched xserver is best for you. To remove xorg-server and install xorg-server-backclear just type:<br />
# pacman -Rd xorg-server<br />
# pacman -S xorg-server-backclear<br />
Similar with xorg-server-1.8-catalyst-maximize-fix.<br />
<br />
====== Xserver segmentation fault ======<br />
Rebuild your xorg.conf with:<br />
aticonfig --initial<br />
or: <br />
aticonfig --initial --force<br />
(if its still not woking then remove /etc/X11/xorg.conf and use one of these two commands mentioned above)<br />
<br />
====== Keyboard/mouse not working ======<br />
Please remember that old hal's input config''' doesn't work with new xorg-server'''.<br />
<br />
Well it should work out of the box with provided with xorg-server 1.8 package files: /etc/X11/xorg.conf.d/'''10-evdev.conf''' and /etc/X11/xorg.conf.d/'''10-quirks.conf'''<br />
but it could happen that's not working / fitting to you so read more here [http://wiki.archlinux.org/index.php/Xorg Arch's Xorg wiki] or here [https://fedoraproject.org/wiki/Input_device_configuration Fedora's wiki for Input device configuration] but don't forget that in archlinux we are using '''/etc/X11/xorg.conf.d''' directory instead of fedora's /etc/xorg.conf.d<br />
<br />
{{Warning| '''Do not''' add any new xserver Section into your /etc/X11/xorg.conf - this file is still used by catalyst - i mean ie dont add any Section "InputClass" into xorg.conf because when you do this both aticonfig and amdcccle wont start cause of parsing xorg.conf error (just use /etc/X11/xorg.conf.d directory for it)}}<br />
<br />
==== Archive repositories ====<br />
<br />
'''[catalyst-10.7]''' repository works fine with any kernel < 2.6.36 rc2 and with multiple-kernels systems (read [http://wiki.archlinux.org/index.php/ATI_Catalyst#Stock_and_Custom_Kernels Stock and Custom Kernels] section). <br />
<br />
For '''x86_64''' users '''[catalyst]''' provides lib32-catalyst-utils package (which should work fine with '''[multilib] repository''') needed to run 32-bit opengl applications and wine games.<br />
<br />
For i686:<br />
[catalyst-10.7]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/i686<br />
For x86_64:<br />
[catalyst-10.7]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst/x86_64<br />
<br />
Repository also contains '''xvba-video''' package so you may easily use '''video acceleration''' described [http://wiki.archlinux.org/index.php/ATI_Catalyst#Video_acceleration below].<br />
<br />
Troubleshooting for this repository is the same as for [http://wiki.archlinux.org/index.php/ATI_Catalyst#Troubleshooting_2 main one].<br />
<br />
<br />
'''[catalyst-10.5]''' repository works fine with 2.6.34-ARCH kernel and xserver 1.8. xorg-server package here is patched with backclear patch, and xorg-server-1.8-catalyst-maximize-fix package is patched with fedora's backfill patch.<br />
<br />
For i686:<br />
[catalyst-10.5]<br />
http://catalyst.apocalypsus.net/repo/catalyst/i686<br />
For x86_64:<br />
[catalyst-10.5]<br />
http://catalyst.apocalypsus.net/repo/catalyst/x86_64<br />
<br />
<br />
{{Note| Archive repositories listed below '''work only with kernel 2.6.33-ARCH and xserver 1.7'''. You may find xserver 1.7 packages in '''[xorg17]''' repository mentioned below. If you are using kernel other than 2.6.33-ARCH please use one of [http://catalyst.apocalypsus.net/tarball/ archive tarballs] to build catalyst for your kernel.<br />
}}<br />
<br />
<br />
'''[xorg17] repository''' contains xserver 1.7 packages, use it only if you are experiencing problems with newer xserver 1.8.<br />
<br />
'''[xorg17]''' repository contains [http://catalyst.apocalypsus.net/tarball/xorg-server-1.7-backclear.tar.gz xorg-server-backclear] (patched with backclear patch) and [http://aur.archlinux.org/packages.php?ID=35686 xorg-server-1.7-catalyst-maximize-fix] (patched with fedora patch) packages. Both this patches fix problems with '''maximizing/resizing''' but they are doing it in different way - you may choose which patched xserver is best for you. To remove xorg-server and install xorg-server-backclear just type:<br />
# pacman -Rd xorg-server<br />
# pacman -S xorg-server-backclear<br />
Similar with xorg-server-1.7-catalyst-maximize-fix<br />
<br />
To use [xorg17] repo please put those lines at the top of all other repositories in '''/etc/pacman.conf''':<br />
<br />
For i686:<br />
[xorg17]<br />
Server = http://catalyst.apocalypsus.net/repo/xorg17/i686<br />
<br />
For x86_64:<br />
[xorg17]<br />
Server = http://catalyst.apocalypsus.net/repo/xorg17/x86_64<br />
<br />
<br />
'''catalyst-10.6''' works well with xserver-1.7, got opengl 3.3/4 support, brings new 2D acceleration support, got some problems with gamma, wine games, and texturing in basing on q3a engine games:<br />
<br />
For i686:<br />
[catalyst-10.6]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/i686<br />
<br />
For x86_64:<br />
[catalyst-10.6]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/x86_64<br />
<br />
<br />
If you are experiencing known bugs/errors (ie. lots of artifacts) with catalyst 10.6 you may still use older '''catalyst-10.5''' or '''catalyst-10.4''' or '''catalyst-10.3''' repositories.<br />
<br />
'''catalyst-10.5''' and '''catalyst-10.4''' repositories contain [http://aur.archlinux.org/packages.php?ID=26687 xorg-server] (for this repositories patched with backclear patch) and [http://aur.archlinux.org/packages.php?ID=35686 xorg-server-1.7-catalyst-maximize-fix] (patched with fedora patch) packages. Both this patches fix problems with '''maximizing/resizing''' but they are doing it in different way - you may choose which patched xserver is best for you. To remove xorg-server and install xorg-server-1.7-catalyst-maximize-fix just type:<br />
# pacman -Rd xorg-server<br />
# pacman -S xorg-server-1.7-catalyst-maximize-fix<br />
<br />
<br />
'''catalyst-10.5''' works well with xserver-1.7, got opengl 3.3/4 support, but still got some problems with gamma, wine games, and texturing in basing on q3a engine games:<br />
<br />
For i686:<br />
[catalyst-10.5]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/i686<br />
<br />
For x86_64:<br />
[catalyst-10.5]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/x86_64<br />
<br />
'''catalyst-10.5''' repository also contains '''libva-sds''', '''mplayer-vaapi''' and '''xvba-video''' packages so you may easily use '''video acceleration''' described [http://wiki.archlinux.org/index.php/ATI_Catalyst#Video_acceleration below].<br />
<br />
<br />
If you don't like catalyst-10.5 you may still use older '''catalyst 10.4''' which work well with xserver-1.7, but still got some problems with gamma and wine games:<br />
<br />
For i686:<br />
[catalyst-10.4]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/i686<br />
<br />
For x86_64:<br />
[catalyst-10.4]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/x86_64<br />
<br />
<br />
Or '''catalyst-10.3'''. Catalyst 10.3 is still using old''' xserver 1.6''', which is also provided by '''[catalyst-10.3]''' repository.<br />
<br />
To use '''catalyst-10.3''' you need as root:<br />
<br />
'''1)''' Edit /etc/pacman.conf and add those lines above all other repositories:<br />
For i686:<br />
[catalyst-10.3]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/i686<br />
<br />
For x86_64:<br />
[catalyst-10.3]<br />
Server = http://catalyst.apocalypsus.net/repo/catalyst-archive/x86_64<br />
<br />
'''2)''' Sync and downgrade packages with this commands<br />
# pacman -Syy<br />
# pacman -Suu<br />
<br />
'''3)''' Remove xf86-video-ati and ati-dri packages if you have them installed.<br />
<br />
'''4)''' (Recommended) If you dont like speed of xorg-server - remove it:<br />
# pacman -Rd xorg-server<br />
and try xorg-server-catalyst-maximize-fix:<br />
# pacman -S xorg-server-catalyst-maximize-fix<br />
<br />
'''5)''' Remove libgl and install catalyst:<br />
# pacman -Rd libgl<br />
# pacman -S catalyst<br />
'''6)''' '''Don't forget''' to prepare your /etc/X11/xorg.conf for catalyst. Use aticonfig --initial if you don't have prepared xorg.conf.<br />
Also add fglrx module to MODULES array in /etc/rc.conf<br />
<br />
'''7)''' Reboot<br />
<br />
=== ATI/AMD Installer ===<br />
{{Warning| Using the installer from ati.com/amd.com is NOT recommended for inexperienced users! Doing so may cause file conflicts and X failures. The packages available through pacman are configured specifically for Arch Linux and so should be used instead.}}<br />
<br />
If you have attempted a manual install from the official installer, and are finding that nothing works correctly anymore, there should be an uninstall script placed at /usr/share/ati - run that, then try the pacman packages.<br />
<br />
If you ''must'' use the installer from ATI/AMD for some reason, the following steps '''might''' work for you:<br />
<br />
*Download AMD/ATI driver installer from the official site only.<br />
*Make it executable.<br />
*Execute a terminal emulator (e.g Konsole) and be root.<br />
*Install mesa package<br />
pacman -S mesa<br />
*(Re)Install Xorg <br />
*Check for other required things for ATI/AMD installer listed on their website<br />
#pacman -Q | grep NameOfPackage<br />
*Use aticonfig as described below to update xorg.conf<br />
*Add ModulesPath into xorg.conf pointing at fglrx.so module if necessary<br />
<br />
== Configuration ==<br />
ATI provides the <code>aticonfig</code> tool to create new basic <code>xorg.conf</code> file or modify an existing <code>xorg.conf</code> file and configure essentially every aspect of the card. For a complete list of <code>aticonfig</code> options, run:<br />
$ aticonfig --help<br />
<br />
If you want to create new xorg.conf file with specific for your system options, run the following command to generate one:<br />
# Xorg -configure<br />
<br />
{{Warning| '''Xorg -configure''' isn't actually recommended - sometimes it doesn't work good with catalyst and could cause your Xserver to break at start with black screen of death. So use it only if you are 100% sure of what you are doing. In most cases '''aticonfig --initiall''' mentioned below should build working xorg.conf file and Xserver should automatically and correctly detect all your input devices.}}<br />
<br />
The simplest way to use <code>aticonfig</code> to adapt your <code>xorg.conf</code> file is listed in the examples at the end of the output if you run <code>aticonfig</code> without any command-line parameters:<br />
Examples:<br />
1. Setting up fglrx for the first time.<br />
Single head : aticonfig --initial --input=/etc/X11/xorg.conf<br />
Dual head : aticonfig --initial=dual-head --screen-layout=above<br />
This command will generate a dual head configuration<br />
file with the second screen located above the first<br />
screen.<br />
<br />
Just adapt one of those two lines for your personal setup.<br />
<br />
{{Warning| Please check the generated xorg.conf file before you copy it to /etc/X11/xorg.conf and happily startx or reboot. Otherwise, you'll probably get a locked blank screen and won't be able to use your system anymore.}} The config files generated by preceding steps are sometimes incorrect. If you want, you can compare the generated files to one of the [http://wiki.archlinux.org/index.php?title=Xorg7#Sample_Xorg.conf_Files Sample Xorg.conf files] listed on the Xorg wiki page.<br />
<br />
Please ensure that in the "Screen" section you have "DefaultDepth 24" and there is a "DRI" section with "Mode 666" in it. The fglrx driver needs those lines to work, but the generated files by preceding programs don't have it. Without those lines, you might get an unresponsive black screen after reboot. Besides, since most of the parts are now automatically detected in modern Xorg, you don't need to write so many things in xorg.conf as you did before with ancient Xorg versions.<br />
So, some config sections/values in the generated xorg.conf are redundant.<br />
<br />
Here is a minimal working example:<br />
<pre><br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/usr/share/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/misc"<br />
FontPath "/usr/share/fonts/100dpi:unscaled"<br />
FontPath "/usr/share/fonts/75dpi:unscaled"<br />
FontPath "/usr/share/fonts/TTF"<br />
FontPath "/usr/share/fonts/Type1"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "dbe"<br />
Load "xtrap"<br />
Load "record"<br />
Load "dri"<br />
Load "glx"<br />
Load "GLcore"<br />
Load "freetype"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
Driver "fglrx"<br />
VendorName "ATI Technologies Inc"<br />
BoardName "Radeon Mobility X1400"<br />
BusID "PCI:1:0:0"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
</pre><br />
<br />
Next, make sure the fglrx module and any needed agp modules are loaded. <br />
# modprobe fglrx <br />
<br />
Add them to the '''MODULES''' array of your /etc/rc.conf to ensure that they load when you boot. <br />
<br />
Finally, run Xorg with <code>startx</code> or by using GDM/KDM and verify that direct rendering is enabled by running the following command in a terminal:<br />
$ glxinfo | grep direct<br />
<br />
If it says "direct rendering: yes" then you're good to go! If the glxinfo command is not found, you may need to install the mesa package as well.<br />
<br />
{{Warning| In recent versions of Xorg, the paths of libs are changed. So, sometimes '''libGL.so''' cannot be correctly loaded even if it's installed. Don't forget to check this if your GL is not working. Please read "Troubleshooting" section for details.}}<br />
<br />
== Video acceleration ==<br />
'''[http://en.wikipedia.org/wiki/Video_Acceleration_API Video Acceleration API] (VA API)''' is an open source software library ("libVA") and API specification which enables and provides access to '''graphics hardware (GPU) acceleration''' for video processing on Linux and UNIX based operating systems.<br />
The main motivation for VA API is to enable hardware accelerated video decode at various entry-points (VLD, IDCT, Motion Compensation, deblocking) for the prevailing coding standards today (MPEG-2, MPEG-4 ASP/H.263, MPEG-4 AVC/H.264, and VC-1/WMV3).<br />
<br />
In November 2009, VA-API gained a new proprietary '''xvba-video''' backend which allows VA-API powered applications to take advantage of AMD Radeon's UVD2 chipsets via the [http://en.wikipedia.org/wiki/XvBA XvBA (X-Video Bitstream Acceleration API designed by AMD)] library.<br />
<br />
XvBA support and xvba-video is still under development, however in nowadays it is '''working very well in most cases''' and with '''mplayer''' (and mplayer front-ends), so feel free to check it. You have to build [http://aur.archlinux.org/packages.php?ID=31723 xvba-video] package and install mplayer-vaapi (available in community repository) & libva (available in extra repository) packages.<br />
Then just set your video player to use vaapi:gl as video output.<br />
<br />
Ie. for '''mplayer''':<br />
$ mplayer -vo vaapi:gl -va vaapi movie.avi<br />
<br />
Ie. for '''smplayer''':<br />
Options -> Preferences -> General -> Video (tab) -> Output driver: User Defined : vaapi:gl<br />
Options -> Preferences -> General -> Video (tab) -> Double buffering '''on'''<br />
Options -> Preferences -> Advanced -> Options for MPlayer -> Options: -va vaapi<br />
Options -> Preferences -> General -> General -> Screenshots -> Turn screenshots '''off'''<br />
<br />
Don't forget to enable v-sync in '''amdcccle''':<br />
3D -> More Settings -> Wait for vertical refresh = Always On<br />
<br />
Note: If you are using '''compiz/kwin''' please note that the only way to '''avoid video flickering''' is to watch videos in '''full-screen''', and only when '''Unredirect Fullscreen is off'''.<br />
<br />
In '''compiz''' you need to set '''Redirected Direct Rendering''' in General Options of ccsm.<br />
<br />
Its off by default in '''kwin''', but if you see flickering you need to add UnredirectFullscreen=off line to [Compositing] section in ~/.kde4/share/config/kwinrc file.<br />
<br />
If its still flickering try to disable this option in ccsm (or change UnredirectFullscreen=off to UnredirectFullscreen=on in kwinrc).<br />
<br />
=== Troubleshooting ===<br />
==== Problems with video colours ====<br />
You may still use vaapi:gl to avoid video flickering, but without video acceleration<br />
<br />
Run '''mplayer''' without '''-va vaapi''' switch.<br />
<br />
For '''smplayer''' remove '''-va vaapi''' from Options -> Preferences -> Advanced -> Options for MPlayer -> Options: -va vaapi<br />
<br />
Plus for '''smplayer''' you may now safely turn screenshots on.<br />
<br />
== Troubleshooting (catalyst) ==<br />
<br />
=== KWin and composite ===<br />
<br />
Use the XRender instead of OpenGL as Composite-Type for best performance! This even solves any artifacts!<br />
<br />
=== Rectangle/Checkerbox corruption with OpenGL programs ===<br />
''This was fixed in catalyst '' 8.9.'' It may occur though in later versions.''<br />
<br />
OpenGL programs like e.g. blender in windowed mode, show a rectangle/checkerbox corruption.<br />
This can be solved by using a Virtual display setting with a multiple of 64 bigger than your actual resolution like 1664 instead 1600 for width:<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Depth 24<br />
Virtual 1664 1200<br />
EndSubSection<br />
EndSection<br />
<br />
===Black screen with complete lockups / hangs after reboot or startx===<br />
<br />
==== Faulty or corrupted amdpcsdb database ====<br />
Fglrx and its Catalyst Control Center stores data on a database called '''amdpcsdb''', located under '''/etc/ati'''. It isn't human readable, but only parsable by Catalyst Control Center. Sometimes, after updates, the settings in there aren't compatible with the new version of fglrx, so you end up with a black screen when starting X. <br />
<br />
So, there is one thing to do.<br />
<br />
Boot to init3, add the number 3 at the end of the menu.lst kernel options:<br />
# rm /etc/ati/amdpcsdb<br />
and restart Xorg (or even reboot).<br />
<br />
{{Warning|Be careful. If you have saved settings through Catalyst Control Center, which are stored under that file, they may now have been lost. You should edit xorg.conf instead, by using '''aticonfig'''.}}<br />
<br />
Be careful though. '''aticonfig''' stores its settings in '''amdpcsdb''' database like Catalyst Control Center. If you want that they're stored in xorg.conf instead, each time you use the aticonfig tool, add '''--input=/etc/X11/xorg.conf''' in the end of the command options as well.<br />
<br />
==== Faulty ACPI hardware calls ====<br />
It is possible that fglrx doesn't cooperate well with the system's ACPI hardware calls, so it autodisables itself and there is no screen output. <br />
<br />
So try to run this:<br />
aticonfig --acpi-services=off<br />
<br />
==== nForce 4 Incompatibility ====<br />
Starting with 9.10 onward, the fglrx drivers are incompatible with nForce 4 chipsets. Use the open source drivers until a fix is created.<br />
<br />
See [http://ati.cchtml.com/show_bug.cgi?id=1794 bug report].<br />
<br />
===KDM disappears after logout===<br />
If you are running the '''catalyst''' proprietary driver and you get a console (tty1) instead of the expected KDM greeting when you log out, you must instruct KDM to restart the X server after each logout:<br />
$ sudo nano /usr/share/config/kdm/kdmrc<br />
<br />
Uncomment the following line under the section titled [X-:*-Core]:<br />
TerminateServer=True<br />
<br />
KDM should now appear when you log out of KDE.<br />
<br />
=== Bad screen resolution at login manager ===<br />
If the resolution for your login manager is for example 1600x1200 and you want 1280x1024 you can fix it by using a xorg.conf (newer X-servers using the open source drivers normally don't need a xorg.conf, so if you don't have a xorg.conf you need to create one). In the "Screen" section add a modes lines:<br />
Section "Screen"<br />
Identifier "aticonfig-Screen[0]-0"<br />
Device "aticonfig-Device[0]-0"<br />
Monitor "aticonfig-Monitor[0]-0"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
Modes "1280x1024" "2048x1536"#<-add this line to change the default login screen resolution<br />
EndSubSection<br />
EndSection<br />
The first argument of modes is the resolution, which will be used by default. The second argument is the maximum resolution supported by your monitor. This is needed so that you are able to choose higher screen resolutions using for example the KDE systemsettings.<br />
<br />
===Direct Rendering Doesn't Work===<br />
This problem may occur when using the proprietary '''catalyst''' driver. <br />
<br />
{{Warning|Make sure that you own a '''R6xx''' ('''HD2xxx''') or newer card or the driver '''won't''' be enabled. You may encounter that error if you try to enable your display by using catalyst and a card older than the R6xx ones.}}<br />
<br />
{{Warning|This error would also appear if you haven't '''rebooted''' your system after the installation or upgrade of catalyst. The system needs to load the fglrx.ko module in order to make the driver work.}}<br />
<br />
If you have problem with direct rendering, run:<br />
$ LIBGL_DEBUG=verbose glxinfo > /dev/null<br />
at the command prompt. At the very start of the output, it'll usually give you a nice error message saying why you don't have direct rendering.<br />
<br />
Common errors, and their solutions, are:<br />
'''libGL error: XF86DRIQueryDirectRenderingCapable returned false'''<br />
<br />
* Ensure that you are loading the correct agp modules for your AGP chipset before you load the fglrx kernel module. To determine which agp modules you'll need, run <code>hwdetect --show-agp</code>, then ensure that all modules listed from that command are in the <code>MODULES=</code> array in rc.conf, '''before''' fglrx.<br />
'''libGL error: failed to open DRM: Operation not permitted'''<br />
'''libGL error: reverting to (slow) indirect rendering'''<br />
<br />
* For this, make sure you have the following section in your <code>xorg.conf</code> somewhere:<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
'''libGL: OpenDriver: trying /usr/lib/xorg/modules/dri//fglrx_dri.so'''<br />
'''libGL error: dlopen /usr/lib/xorg/modules/dri//fglrx_dri.so failed (/usr/lib/xorg/modules/dri//fglrx_dri.so: cannot open shared object file: No such file or directory)'''<br />
'''libGL error: unable to find driver: fglrx_dri.so'''<br />
<br />
* Something hasn't been installed correctly. If the paths in the error message are <code>/usr/X11R6/lib/modules/dri/fglrx_dri.so</code>, then ensure you've logged completely out of your system, then back in. If you're using a graphical login manager (gdm, kdm, xdm), ensure that /etc/profile is sourced every time you log in. This is usually accomplished by adding <code>source /etc/profile</code> into <code>~/.xsession</code> or <code>~/.xinitrc</code>, but may vary between login managers.<br />
<br />
* If the paths above in your error message _are_ <code>/usr/lib/xorg/modules/dri/fglrx_dri.so</code>, then something hasn't been correctly installed. Try reinstalling the <code>catalyst</code> package.<br />
<br />
Errors such as:<br />
'''fglrx: libGL version undetermined - OpenGL module is using glapi fallback'''<br />
could be caused by having multiple versions of <code>libGL.so</code> on your system. Run:<br />
$ sudo updatedb<br />
$ locate libGL.so<br />
<br />
This should return the following output:<br />
$ locate libGL.so<br />
/usr/lib/libGL.so<br />
/usr/lib/libGL.so.1<br />
/usr/lib/libGL.so.1.2<br />
$<br />
<br />
These are the only three libGL.so files you should have on your system. If you have any more (e.g. <code>/usr/X11R6/lib/libGL.so.1.2</code>), then remove them. This should fix your problem. <br />
<br />
You might not get any error to indicate that this is a problem. If you are using X11R7, make sure you do '''not''' have these files on your system:<br />
/usr/X11R6/lib/libGL.so.1.2<br />
/usr/X11R6/lib/libGL.so.1<br />
<br />
===Hibernate/Sleep Issues===<br />
<br />
==== Video fails to enter suspend/hibernate ====<br />
If <code>fglrx</code> returns an error when attempting to suspend through hibernate scripts, a solution may be to add the following line to your "Device" section in <code>/etc/X11/xorg.conf</code>, which should allow the <tt>fglrx</tt> module to enter suspend mode.<br />
Option "UseInternalAGPGart" "no"<br />
<br />
==== Video fails to resume from suspend2ram ====<br />
ATI's proprietary <tt>catalyst</tt> driver cannot resume from suspend if the framebuffer is enabled. To disable the framebuffer, add '''vga=0''' to your kernel options in <code>/boot/grub/menu.lst</code>, for example:<br />
# (0) Arch Linux<br />
title Arch Linux<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda2 ro '''''vga=0'''''<br />
initrd /kernel26.img<br />
<br />
===System Freezes/Hard locks===<br />
* To prevent system lockups, try adding the following lines to your fglrx "Device" section in <code>xorg.conf</code><br />
Option "UseInternalAGPGART" "no"<br />
Option "KernelModuleParm" "agplock=0" # AGP locked user pages: disabled<br />
<br />
{{Note|Neither option is necessary anymore since 8.24.18 because ATI has removed the internal AGP GART support from the driver.}}<br />
<br />
* As well, the <code>radeonfb</code> framebuffer drivers have been known in the past to cause problems of this nature. If your kernel has radeonfb support compiled in, you may want to try a different kernel and see if this helps. <br />
<br />
===Hardware Conflicts===<br />
Radeon cards used in conjunction with some versions of the nForce3 chipset (e.g. nForce 3 250Gb) won't have 3D acceleration. Currently the cause of this issue is unknown, but some sources indicate that it may be possible to get acceleration with this combination of hardware by booting Windows with the drivers from nVIDIA and then rebooting the system. This can be verified by issuing in a root console the following command:<br />
dmesg | grep agp<br />
<br />
If you get something similar to this (using an nForce3-based system)<br />
agpgart: Detected AGP bridge 0<br />
agpgart: Setting up Nforce3 AGP.<br />
agpgart: aperture base > 4G<br />
<br />
and also if issuing this command...<br />
tail -n 100 /var/log/Xorg.0.log | grep agp<br />
<br />
...gets something similar to:<br />
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENODEV"<br />
<br />
Then you have this bug.<br />
<br />
Some sources indicate that in some situations, downgrading the motherboard BIOS may help, but this cannot be verified in all cases. Also, a bad BIOS downgrade can render your hardware useless, so beware.<br />
<br />
See bug http://bugzilla.kernel.org/show_bug.cgi?id=6350 for more information and a potential fix.<br />
<br />
===Temporary hangs when playing video===<br />
This problem may occur when using the proprietary '''catalyst''' driver.<br />
<br />
If you experience temporary hangs lasting from a few seconds to several minutes occuring randomly during playback with mplayer, check /var/log/messages.log for output like:<br />
Nov 28 18:31:56 pandemonium [<c01c64a6>] ? proc_get_sb+0xc6/0x160<br />
Nov 28 18:31:56 pandemonium [<c01c64a6>] ? proc_get_sb+0xc6/0x160<br />
Nov 28 18:31:56 pandemonium [<f8bc628c>] ? ip_firegl_ioctl+0x1c/0x30 [fglrx]<br />
Nov 28 18:31:56 pandemonium [<c01c64a6>] ? proc_get_sb+0xc6/0x160<br />
Nov 28 18:31:56 pandemonium [<c0197038>] ? vfs_ioctl+0x78/0x90<br />
Nov 28 18:31:56 pandemonium [<c01970b7>] ? do_vfs_ioctl+0x67/0x2f0<br />
Nov 28 18:31:56 pandemonium [<c01973a6>] ? sys_ioctl+0x66/0x70<br />
Nov 28 18:31:56 pandemonium [<c0103ef3>] ? sysenter_do_call+0x12/0x33<br />
Nov 28 18:31:56 pandemonium [<c01c64a6>] ? proc_get_sb+0xc6/0x160<br />
Nov 28 18:31:56 pandemonium =======================<br />
<br />
Adding the nopat kerneloption to /boot/grub/menu.lst and rebooting fixed the problem at least for me.<br />
<br />
===After a kernel upgrade: X doesn't start/modprobe doesn't find fglrx===<br />
Reinstall the catalyst drivers.<br />
<br />
Or since catalyst 10.6-3 use:<br />
# catalyst_build_module<br />
<br />
===Catalyst 10.6/10.7 : black/grey/white boxes/artifacts in firefox/thunderbird===<br />
With catalyst 10.6 AMD/ATi announce new method of 2D acceleration for radeons, unfortunately this step causes bugs for some users. To turn on old (slower xaa) method of 2d rendering please kill your desktop environment and Xserver and type this command as root:<br />
aticonfig --set-pcs-str=DDX,ForceXAA,TRUE<br />
Now you'll probably need patched xorg-server to fix problems with resizing/maximizing windows, read about it ie. [http://wiki.archlinux.org/index.php/ATI_Catalyst#Black.2Fgrey.2Fwhite_boxes.2Fartifacts_mainly_in_firefox.2Fthunderbird here].</div>LeCrayonVerthttps://wiki.archlinux.org/index.php?title=Talk:OpenSSH&diff=114712Talk:OpenSSH2010-08-22T19:31:42Z<p>LeCrayonVert: /* SendEnv */</p>
<hr />
<div>regarding X11 forwarding:<br />
i don't think it is necessary to enable X11Forwarding on the client on a global base:<br />
"Enable the ForwardX11 option in ssh_config on the client."<br />
<br />
simply specifing -X option to ssh works for me. [The preceding unsigned comment was added 2010-01-11T15:41:54 by [[User:Uwinkelvos|Uwinkelvos]] ([[User_talk:Uwinkelvos|Talk]] | [[Special:Contributions/Uwinkelvos|contribs]]).]<br />
<br />
== SendEnv ==<br />
<br />
I think we should add something about accent/UTF-8/encoding.<br />
Setting SendEnv LANG LC_* in /etc/ssh/ssh_config (client side) would be very useful.</div>LeCrayonVerthttps://wiki.archlinux.org/index.php?title=Talk:OpenSSH&diff=114711Talk:OpenSSH2010-08-22T19:28:58Z<p>LeCrayonVert: /* SendEnv */</p>
<hr />
<div>regarding X11 forwarding:<br />
i don't think it is necessary to enable X11Forwarding on the client on a global base:<br />
"Enable the ForwardX11 option in ssh_config on the client."<br />
<br />
simply specifing -X option to ssh works for me. [The preceding unsigned comment was added 2010-01-11T15:41:54 by [[User:Uwinkelvos|Uwinkelvos]] ([[User_talk:Uwinkelvos|Talk]] | [[Special:Contributions/Uwinkelvos|contribs]]).]<br />
<br />
== SendEnv ==<br />
<br />
I think we should add something about accent/UTF-8/encoding.<br />
Set SendEnv LANG LC_* in /etc/ssh/ssh_config (client side) would be very useful.</div>LeCrayonVerthttps://wiki.archlinux.org/index.php?title=Talk:OpenSSH&diff=114709Talk:OpenSSH2010-08-22T19:26:25Z<p>LeCrayonVert: /* SendEnv */ new section</p>
<hr />
<div>regarding X11 forwarding:<br />
i don't think it is necessary to enable X11Forwarding on the client on a global base:<br />
"Enable the ForwardX11 option in ssh_config on the client."<br />
<br />
simply specifing -X option to ssh works for me. [The preceding unsigned comment was added 2010-01-11T15:41:54 by [[User:Uwinkelvos|Uwinkelvos]] ([[User_talk:Uwinkelvos|Talk]] | [[Special:Contributions/Uwinkelvos|contribs]]).]<br />
<br />
== SendEnv ==<br />
<br />
I think we should add something about accent/UTF-8/encoding.<br />
Set SendEnv LANG LC_* as a default option in the /etc/ssh/ssh_config (client side) would be indeed useful.</div>LeCrayonVerthttps://wiki.archlinux.org/index.php?title=Pacman/Rosetta&diff=113660Pacman/Rosetta2010-08-10T15:24:15Z<p>LeCrayonVert: </p>
<hr />
<div>[[Category:Package management (English)]]<br />
{{i18n|Pacman Rosetta}}<br />
<br />
This page pulls heavily from [http://en.opensuse.org/Software_Management_Command_Line_Comparison openSUSE's Software Management Command Line Comparison]. It has been simplified and has added Arch to the comparison, as well as modified the order in which each distribution exists for the benefit of Arch users.<br />
<br />
{|<br />
| align="center" style="background:#f0f0f0;"|'''Action'''<br />
| align="center" style="background:#f0f0f0;"|'''arch'''<br />
| align="center" style="background:#f0f0f0;"|'''redhat/fedora'''<br />
| align="center" style="background:#f0f0f0;"|'''debian/ubuntu'''<br />
| align="center" style="background:#f0f0f0;"|'''old suse'''<br />
| align="center" style="background:#f0f0f0;"|'''opensuse'''<br />
| align="center" style="background:#f0f0f0;"|'''gentoo'''<br />
|-<br />
| Install a package(s) by name ||pacman -S||yum install ||apt-get install||rug install||zypper install zypper in|| emerge [-a]<br />
|- style="background:#e4e4e4"<br />
| Remove a package(s) by name ||pacman -R||yum remove/erase ||apt-get remove||rug remove/erase||zypper remove zypper rm ||emerge -C<br />
|-<br />
| Search for package(s) by searching the expression in name, description, short description. What exact fields are being searched by default varies in each tool. Mostly options bring tools on par. ||pacman -Ss||yum search ||apt-cache search||rug search||zypper search zypper se [-s]||emerge -S <br />
|- style="background:#e4e4e4"<br />
| Upgrade Packages - Install packages which have an older version already installed ||pacman -Syu||yum update ||apt-get upgrade||rug update||zypper update zypper up||emerge -u world<br />
|-<br />
| Upgrade Packages - Another form of the update command, which can perform more complex updates -- like distribution upgrades. When the usual update command will omit package updates, which include changes in dependencies, this command can perform those updates. ||pacman -Syu||yum upgrade ||apt-get dist-upgrade||||zypper dup||emerge -uDN world<br />
|- style="background:#e4e4e4"<br />
| Reinstall given Package - Will reinstall the given package without dependency hassle. ||pacman -S||||apt-get install --reinstall||||zypper install --force||emerge [-a]<br />
|-<br />
| Installs local package file, e.g. app.rpm and uses the installation sources to resolve dependencies ||pacman -U||yum localinstall ||dpkg -i && apt-get install -f||||zypper in /path/to/local.rpm||emerge<br />
|- style="background:#e4e4e4"<br />
| Updates package(s) with local packages and uses the installation sources to resolve dependencies ||pacman -U||yum localupdate ||||||n/a||emerge||<br />
|-<br />
| Use some magic to fix broken dependencies in a system || pacman dep level - testdb, shared lib level - findbrokenpkgs or lddd||||apt-get --fix-broken||rug* solvedeps ||n/a ||revdep-rebuild<br />
|- style="background:#e4e4e4"<br />
| Only downloads the given package(s) without unpacking or installing them ||pacman -Sw||yumdownloader (found in yum-utils package)||apt-get --download-only||||n/a||emerge --fetchonly <br />
|-<br />
| Remove dependencies that are no longer needed, because e.g. the package which needed the dependencies was removed. ||pacman -Qdt(only list them)||||apt-get autoremove ||||n/a||emerge --depclean <br />
|- style="background:#e4e4e4"<br />
| Downloads the corresponding source package(s) to the given package name(s) || yaourt -G <package> && makepkg -o ||||apt-get source ||||zypper source-install||emerge --fetchonly<br />
|-<br />
| Install/Remove packages to satisfy buid-dependencies. Uses information in the source package. ||automatic||||apt-get build-dep ||||zypper si -d||emerge -o <br />
|- style="background:#e4e4e4"<br />
| Add a package lock rule to keep its current state from being changed ||${EDITOR} /etc/pacman.conf<br/>modify IgnorePkg array||yum.conf <--”exclude” option (add/amend)||<nowiki>echo "$PKGNAME hold" | dpkg --set-selections</nowiki> ||rug* lock-add ||Put package name in /etc/zypp/locks||/etc/portage/package.mask<br />
|-<br />
| Delete a package lock rule ||remove package from IgnorePkg line in /etc/pacman.conf||yum.conf <--”exclude” option (remove/amend)||<nowiki>echo "$PKGNAME install" | dpkg --set-selections</nowiki> ||rug* lock-delete||Remove package name from /etc/zypp/locks||/etc/portage/package.mask (or package.unmask) <br />
|- style="background:#e4e4e4"<br />
| Show a listing of all lock rules ||cat /etc/pacman.conf||yum.conf (research needed)||/etc/apt/preferences ||rug* lock-list||View /etc/zypp/locks||cat /etc/portage/package.mask<br />
|-<br />
| Add a checkpoint to the package system for later rollback ||||||||rug* checkpoint-add ||n/a ||<br />
|- style="background:#e4e4e4"<br />
| Remove a checkpoint from the system ||N/A||||||rug* checkpoint-remove ||n/a ||<br />
|-<br />
| Provide a list of all system checkpoints ||N/A||||||rug* checkpoints ||n/a ||<br />
|- style="background:#e4e4e4"<br />
| Rolls entire packages back to a certain date or checkpoint. ||N/A||||||rug* rollback ||n/a ||<br />
|-<br />
| ||||||||||||<br />
|-<br />
| ||||||||||||<br />
|-<br />
| Package information management ||||||||||||<br />
|- style="background:#e4e4e4"<br />
| Get a dump of the whole system information - Prints, Saves or similar the current state of the package management system. Preferred output is text or XML. One version of rug dumps information as a sqlite database. (Note: Why either-or here? No tool offers the option to choose the output format.) ||(see /var/lib/pacman/local)||(see /var/lib/rpm/Packages)||apt-cache stats||rug dump||n/a ||emerge --info<br />
|-<br />
| Show all or most information about a package. The tools\' verbosity for the default command vary. But with options, the tools are on par with each other. ||pacman -[S<nowiki>|</nowiki>Q]i ||yum list or info ||apt-cache showpkg apt-cache show||rug info||zypper info zypper if||emerge -S; emerge -pv<br />
|- style="background:#e4e4e4"<br />
| Search for package(s) by searching the expression in name, description, short description. What exact fields are being searched by default varies in each tool. Mostly options bring tools on par. ||pacman -Ss ||yum search ||apt-cache search||rug search||zypper search zypper se [-s]||emerge -S <br />
|-<br />
| Lists packages which have an update available. Note: Some provide special commands to limit the output to certain installation sources, others use options. ||pacman -Qu ||yum list updates yum check-update ||apt-get upgrade -> n||rug list-updates rug summary||zypper list-updates zypper patch-check (just for patches) ||emerge -uDNp world<br />
|- style="background:#e4e4e4"<br />
| Display a list of all packages in all installation sources that are handled by the packages management. Some tools provide options or additional commands to limit the output to a specific installation source. ||pacman -Sl ||yum list available||apt-cache dumpavail apt-cache dump (Cache only) apt-cache pkgnames||rug packages||IN PROGRESS ||emerge -ep world<br />
|-<br />
| Displays packages which provide the given exp. aka reverse provides. Mainly a shortcut to search a specific field. Other tools might offer this functionality through the search command. ||pkgfile <filename>||yum whatprovides yum provides ||apt-file search <filename>||rug what-provides||zypper what-provides&nbsp;&nbsp;&nbsp; zypper wp|| equery belongs (only installed packages)<br />
|- style="background:#e4e4e4"<br />
| Display packages which require X to be installed, aka show reverse/ dependencies. rug\'s what-requires can operate on more than just package names. ||pacman -Qi||yum resolvedep ||apt-cache rdepends||rug what-requires||IN PROGRESS || equery depends<br />
|-<br />
| Display packages which conflict with given expression (often package). Search can be used as well to mimic this function. rug\'s what-conflicts function operates on more than just package names ||(none)||||||rug info-conflicts rug what-conflicts||IN PROGRESS ||<br />
|- style="background:#e4e4e4"<br />
| List all packages which are required for the given package, aka show dependencies. ||pacman -[S<nowiki>|</nowiki>Q]i||yum deplist ||apt-cache depends||rug info-requirements||IN PROGRESS || emerge -ep<br />
|-<br />
| List what the current package provides ||||yum provides ||||rug info-provides||IN PROGRESS||<br />
|- style="background:#e4e4e4"<br />
| List the files that the package holds. Again, this functionality can be mimicked by other more complex commands. ||pacman -Ql $pkgname <br/>pkgfile -l ||yum provides ||apt-file list||rug* file-list||IN PROGRESS ||equery files<br />
|-<br />
| Search all packages to find the one which holds the specified file. auto-apt is using this functionality. ||pkgfile -s||yum provides yum whatprovides ||apt-file search||rug* package-file rug what-provides||IN PROGRESS ||equery belongs<br />
|- style="background:#e4e4e4"<br />
| Display all packages that the specified packages obsoletes. ||||yum list obsoletes ||apt-cache / grep||rug info-obsoletes||IN PROGRESS|| <br />
|-<br />
| Verify dependencies of the complete system. Used if installation process was forcefully killed. ||N/A||yum deplist ||apt-get check ? apt-cache unmet||rug verify rug* dangling-requires||n/a || emerge -uDN world<br />
|- style="background:#e4e4e4"<br />
| Generates a list of installed packages ||pacman -Q||yum list installed ||apt-cache --installed||||n/a ||emerge -ep world<br />
|-<br />
| List packages that are installed but are not available in any installation source (anymore). ||pacman -Qm||yum list extras ||||||n/a||<br />
|- style="background:#e4e4e4"<br />
| List packages that were recently added to one of the installation sources, i.e. which are new to it. Note: Synaptic has this functionality, however apt doesn\'t seem to be the provider. ||(none)||yum list recent ||||||n/a||<br />
|-<br />
| Show a log of actions taken by the software management. ||cat /var/log/pacman.log ||||cat /var/log/dpkg.log||rug history ||n/a || located in /var/log/portage<br />
|- style="background:#e4e4e4"<br />
| Clean up all local caches. Options might limit what is actually cleaned. Autoclean removes only unneeded, obsolete information. ||pacman -Sc<br/>pacman -Scc ||yum clean ||apt-get clean apt-get autoclean||||n/a ||<br />
|-<br />
| Add a local package to the local package cache mostly for debugging purposes. ||cp $pkgname /var/cache/pacman/pkg/||||apt-cache add ||||n/a ||<br />
|- style="background:#e4e4e4"<br />
| Display the source package to the given package name(s) ||||||apt-cache showsrc ||||n/a||<br />
|-<br />
| Generates an output suitable for processing with dotty for the given package(s). ||||||apt-cache dotty ||||n/a ||<br />
|- style="background:#e4e4e4"<br />
| Set the priority of the given package to avoid upgrade, force downgrade or to overwrite any default behavior. Can also be used to prefer a package version from a certain installation source. ||${EDITOR} /etc/pacman.conf<br/>Modify HoldPkg and/or IgnorePkg arrays||yum-plugin-priorities and yum-plugin-protect-packages||/etc/apt/preferences smart priority –set||||n/a ||<br />
|-<br />
| Remove a previously set priority ||||||/etc/apt/preferences smart priority --remove ||||n/a ||<br />
|- style="background:#e4e4e4"<br />
| Show a list of set priorities. ||||||apt-cache policy /etc/apt/preferences smart priority --show ||||n/a ||<br />
|-<br />
| Ignores problems that priorities may trigger. ||||||||||n/a ||<br />
|-<br />
| ||||||||||||<br />
|-<br />
| ||||||||||||<br />
|- style="background:#e4e4e4"<br />
| Installation sources management ||${EDITOR} /etc/pacman.conf||||||||||<br />
|-<br />
| Add an installation source to the system. Some tools provide additional commands for certain sources, others allow all types of source URI for the add command. Again others, like apt and yum force editing a sources list. apt-cdrom is a special command, which offers special options design for CDs/DVDs as source. ||${EDITOR} /etc/pacman.conf||||apt-cdrom add||rug service-add rug mount /local/dir||zypper service-add ||layman, overlays<br />
|- style="background:#e4e4e4"<br />
| Refresh the information about the specified installation source(s) or all installation sources. ||pacman -Sy ||yum check-update ||apt-get update||rug refresh||zypper refresh zypper ref||layman -f<br />
|-<br />
| Prints a list of all installation sources including important information like URI, alias etc. ||cat /etc/pacman.d/mirrorlist||||||rug service-list||zypper service-list ||<br />
|- style="background:#e4e4e4"<br />
| Other commands ||||||||||||<br />
|-<br />
| Start a shell Start a shell to enter multiple commands in one session ||||yum shell ||apt-config shell||||zypper shell ||<br />
|-<br />
| ||||||||||||<br />
|-<br />
| ||||||||||||<br />
|- style="background:#e4e4e4"<br />
| Package Verification||||||||||||<br />
|-<br />
| Single package||||rpm -V <package>||debsums||rpm -V <package>||rpm -V <package>||equery check<br />
|- style="background:#e4e4e4"<br />
| All packages||||rpm -Va||debsums||rpm -Va||rpm -Va||equery check<br />
|-<br />
| ||||||||||||<br />
|-<br />
| ||||||||||||<br />
|-<br />
| Package Querying||||||||||||<br />
|- style="background:#e4e4e4"<br />
| List installed local packages along with version||pacman -Q||rpm -qa||dpkg-query -l||||||emerge -e world<br />
|-<br />
| Display package information: Name, version, description, etc.||pacman -Qi ||rpm -qi ||dpkg-query -p||||||emerge -pv and emerge -S<br />
|- style="background:#e4e4e4"<br />
| Display files provided by package||pacman -Ql ||rpm -ql ||dpkg-query -L||||||equery files<br />
|-<br />
| Query the package which provides FILE ||pacman -Qo ||rpm -qf ||dpkg-query -S||||||<br />
|- style="background:#e4e4e4"<br />
| Query a package supplied on the command line rather than an entry in the package management database||pacman -Qp||rpm -qp||dpkg-deb -I||||||<br />
|-<br />
| Show the changelog of a package||pacman -Qc||rpm -q --changelog|||||||||equery changes -f<br />
|}</div>LeCrayonVerthttps://wiki.archlinux.org/index.php?title=Synchronization_and_backup_programs&diff=113480Synchronization and backup programs2010-08-07T19:18:42Z<p>LeCrayonVert: </p>
<hr />
<div>== Intro ==<br />
<br />
This wiki page contains information about various backup programs. It's a good idea to ''have'' regular backups of important data, most notably configuration files (<tt>/etc/*</tt>) and local pacman database (usually <tt>/var/lib/pacman/local/*</tt>).<br />
<br />
Few words to end the introduction: before you start trying programs out, try to think about your needs, e.g. consider the following questions:<br />
* What backup medium do I have available?<br />
** cd / dvd<br />
** remote server (With what access? Ssh? Can I install some software on it (necessary for e.g. rsync-based solutions)?)<br />
** external harddrive<br />
* How often do I plan to backup?<br />
** daily?<br />
** weekly?<br />
** less often?<br />
* What goodies do I expect from the backup solution?<br />
** compression? (what algorithms?)<br />
** encryption? (gpg or something more straightforward?)<br />
* Most importantly: how do I plan to restore backups if needed?<br />
<br />
All right, enough with this, let's see some options!<br />
<br />
== Incremental backups ==<br />
<br />
The point with these is that they remember what has been backed up during the last run, and back up only what has changed. Great if you back up often.<br />
<br />
=== Rsync-type backups ===<br />
The main characteristic of this type of backups is that they maintain a copy of the directory you want to keep a backup of, in a traditional "mirror" fashion.<br />
<br />
Certain rsync-type packages also do snapshot backups by storing files which describe the how the contents of files and folders changed from the last backup (the so-called 'diffs'). Hence, they are inherently incremental, but usually they don't have compression/encryption. On the other hand, a working copy of everything is immediately available, no decompression/decryption needed. Finally the way it works makes it hard to burn backups to cd/dvd..<br />
<br />
===== CLI =====<br />
*[[rsync]] (in extra repo)<br />
**rsync almost always makes a mirror of the source<br />
**Impossible to restore a backup before the most recent backup<br />
**Win32 version available<br />
*[http://www.nongnu.org/rdiff-backup/ rdiff-backup] (in community repo)<br />
**Stores most recent backup as regular files<br />
**To revert to older versions, you apply the diff files to recreate the older versions<br />
**It is truly granularly incremental (delta backup), it only stores changes to a file; will not create a new copy of a file upon change<br />
**Win32 version available<br />
*[http://www.rsnapshot.org rsnapshot] (in community repo) <br />
**Does not store diffs, instead it copies entire files if they have changed<br />
**Creates hard links between a series of backed-up trees (snapshots)<br />
**It is incremental in that the size of the backup is only the original backup size plus the size of all files that have changed since the last backup.<br />
**Destination filesystem must support hard links<br />
**Win32 version available<br />
*[http://safekeep.sourceforge.net/ SafeKeep] (in AUR)<br />
**Enhancement to rdiff-backup<br />
**Integrates with Linux LVM and databases to create consistent backups<br />
**Bandwidth throttling<br />
* [http://www.scottlu.com/Content/Link-Backup.html Link-Backup] ([http://aur.archlinux.org/packages.php?ID=16929 AUR] may be patched with additional features) is similar to rsync based scripts, but does not use rsync<br />
** Creates hard links between a series of backed-up trees (snapshots)<br />
** Intelligently handles renames, moves, and duplicate files without additional storage or transfer<br />
** dstdir/.catalog is a catalog of all unique file instances; backup trees hard-link to the catalog<br />
** If a backup tree would be identical to the previous backup tree, it won't be needlessly created<br />
** Transfer occurs over standard I/O locally or remotely between a client and server instance of this script<br />
** It copies itself to the server; it does not need to be installed on the server<br />
** Remote backups rely on SSH<br />
** It resumes stopped backups; it can even be told to run for n minutes<br />
<br />
===== GUI =====<br />
*[http://backintime.le-web.org/ Back In Time] (in AUR)<br />
**Creates hard links between a series of backed-up trees (snapshots)<br />
**Inspired by FlyBack and TimeVault<br />
**Really is just a front-end to rsync, diff, cp<br />
**A new snapshot is created only if something changed since the last snapshot<br />
*[http://www.flyback-project.org/ FlyBack] (in AUR)<br />
**A clone of Apple's Mac OS X Time Machine software<br />
*[http://areca.sourceforge.net/ Areca Backup] (in AUR)<br />
**Written in Java<br />
**Primarily archive-based (ZIP), but will do file-based backup as well<br />
**Claims delta backup supported (stores only changes)<br />
*[https://wiki.ubuntu.com/TimeVault TimeVault] (in AUR)<br />
**Creates hard links between a series of backed-up trees (snapshots)<br />
**Imitates Windows Volume Shadow Copy feature in that it integrates with Nautilus to provide a "Previous Versions" tab in the Properties dialog.<br />
*[http://luckybackup.sourceforge.net/index.html Luckybackup] (in [http://aur.archlinux.org/packages.php?ID=23121 AUR])<br />
**Luckybackup it's an easy program to backup and sync your files.<br />
**It is written in Qt and C++<br />
**It has Sync,Backup (with include and exclude options),Restore operations,Remote connection backup,Scheduled backups,Command line mode and more abilities.<br />
<br />
=== Not rsync-based ===<br />
<br />
They tend to create (big) archive files (like tar.bz2), and (of course) keep track of what's been archived. Now creating tar.bz2 or tar.gz archives has the advantage that you can extract the backups with just tar/bzip2/gzip, so you don't need to have the backup program around.<br />
<br />
* [[backup-manager|backup-manager]] (in AUR); [http://www.backup-manager.org/ homepage] Backup Manager is a command line backup tool for GNU/Linux, designed to help you make daily archives of your file system. Written in bash and perl, it can make archives in lots of open formats (tar, gzip, bzip2, lzma, dar, zip) and provides lots of interesting features (such as network exports or CD/DVD automated-burning). The program is designed to be as easy to use as possible and is popular with desktop users and sysadmins. The whole backup process is defined in one full-documented configuration file which needs no more than 5 minutes to tune for your needs. It just works. Archives are kept for a given number of days and the upload system can use ftp or scp to transfer the generated archives to a list of remote hosts. Gettext is used for internationalization.<br />
** 1 configuration file, 5 minutes setup<br />
** Manually invoke backup process or run daily unattended via CRON<br />
** Backup files, MySQL databases and Subversion repositories<br />
** Specify multiple targets to backup at once (/etc, /home, etc…)<br />
** Ability to exclude files from backup<br />
** Automatically purge old backups<br />
** Full backup only or Full + Incremental backup<br />
** Backup to an attached disk, LAN or Internet<br />
** Burns backup to CD/DVD with MD5 checksum verification<br />
** Archives in lots of open formats: tar, gzip, bzip2, lzma, dar, zip<br />
** Slice archives to 2 GB if using dar archives format<br />
** Backup over SSH<br />
** Encrypts archives<br />
** Offsite remote upload of archives via FTP, SSH, RSYNC or Amazon S3<br />
** Can run with different configuration files concurrently<br />
** Easy external hooks<br />
**Simply uncompressed the open format backup archives with any command line or GUI tool<br />
<br />
* [[Backup with arch-backup|arch-backup]] (in community repo); [http://code.google.com/p/archlinux-stuff/ website]); trivial backup scripts with simple configuration:<br />
** compression method can be configured<br />
** possible to specify more directories to backup<br />
<br />
* [[Backup with hdup|hdup]] (in extra repo; [http://miek.nl/projects/hdup2/ website]; it's no longer developed, the author develops rdup now (below); but it's still a decent one):<br />
** creates tar.gz or tar.bz2 archives<br />
** supports gpg encryption<br />
** supports pushing over ssh<br />
** possible to specify more directories to backup<br />
<br />
* [http://miek.nl/projects/rdup rdup] (in [http://aur.archlinux.org/packages.php?ID=3728 AUR]) successor to hdup: the program *just determines* which files have changed since the last backup. It's completely up to you what do you want to do with that list. Some helper scripts are supplied, and with them it supports:<br />
** creating tar.gz archives '''or''' rsync-type copy<br />
** encryption (gpg and usual strong (eg. blowfish)), also applies for rsync-type copy<br />
** compression (also for rsync-type copy)<br />
<br />
* [http://www.nongnu.org/duplicity/ duplicity] (in community repo) is similar to hdup, supports tarring and encrypting. But:<br />
** the files backed up are "randomly" distributed between encrypted tar archives, which makes it harder to recover a particular file<br />
** you can backup just one directory at a time (while with hdup you can specify as many as you want in one backup profile)<br />
<br />
* [http://dar.linux.free.fr/ dar] (in community repo): <br />
** it uses its own format for archives (so you need to have it around when you want to restore)<br />
** supports splitting backups into more files by size<br />
** makefile-type config files, some custom scripts are available along with it<br />
** supports basic encryption (not gpg; but also strong, but you need to supply a password every time)<br />
** some gui tools for inspecting backups are also available (kdar, in [http://aur.archlinux.org/packages.php?ID=7586 AUR], but current dar needs beta version)<br />
** a script suitable for running from cron is [http://sarab.sourceforge.net/ sarab] (in [http://aur.archlinux.org/packages.php?ID=17044 AUR]): supports pretty much any backup scheme (Towers of Hanoi, Grandfather-Father-Son, etc..)<br />
<br />
* [http://sourceforge.net/projects/backerupper/ backerupper] (in [http://aur.archlinux.org/packages.php?ID=17441 AUR]) Backerupper is a simple program for backing up selected directories over a local network. Its main intended purpose is backing up a user's personal data.<br />
** GUI based<br />
** creating tar.gz archives<br />
** possible to define : backup frequency, backup time, Max copies<br />
<br />
* [http://trac.manent-backup.com/ Manent] (in [http://aur.archlinux.org/packages.php?ID=19241 AUR]) is an algorithmically strong backup and archival program. It's Python based and has the following features:<br />
** Efficient backup to anything that looks like a storage<br />
** Works well over a slow and unreliable network<br />
** Offers online access to the contents of the backup<br />
** Backed up storage is completely encrypted<br />
** Several computers can use the same storage for backup, automatically sharing data<br />
** Not reliant on timestamps of the remote system to detect changes<br />
** Cross-platform support for Unicode file names<br />
<br />
=== Cloud backups ===<br />
<br />
* [http://www.getdropbox.com Dropbox] (in [http://aur.archlinux.org/packages.php?ID=19615 AUR] with Gnome support, and also [http://aur.archlinux.org/packages.php?ID=23363 AUR] without Gnome dependencies). <br />
** A daemon monitors a specified directory, and uploads incremental changes to Dropbox.com. <br />
** Changes automatically show up on your other computers. <br />
** Includes file sharing and a public directory. <br />
** You can recover deleted files. <br />
** Community written add-ons. <br />
** Free accounts have 2GB storage.<br />
<br />
* [http://www.jungledisk.com/ Jungle Disk] (in [http://aur.archlinux.org/packages.php?ID=15015 AUR])<br />
** Automatic backups to Amazon's servers.<br />
** Not free, but very low prices.<br />
<br />
== Not incremental backups ==<br />
* [http://k7z.sourceforge.net/ Q7Z] (in [http://aur.archlinux.org/packages.php?ID=12822 AUR]) is a P7Zip GUI for Linux, which attempts to simplify data compression and backup. It can create the following archive types: 7z, BZip2, Zip, GZip, Tar. Use Q7Z if you want to:<br />
** Update existing archives quickly<br />
** Backup multiple folders to a storage location<br />
** Create or extract protected archives<br />
** Lessen effort by using archiving profiles and lists<br />
* "Just copy everything into one big archive, but support writing to cd/dvd"-type: [http://www2.backup-manager.org/ backup-manager] (in [http://aur.archlinux.org/packages.php?ID=4351 AUR])<br />
* [[Partclone]] -- back up and restore only the used blocks of a partition<br />
* filesystem-backup -- simple bash script (was originally a MySQL backup script) that creates a rolling 7 days, rolling 4 weeks and static monthly backups in tar format. Good for servers without a GUI. Available in repo: http://repo.falconn.nl/any/<br />
* [http://clonezilla.org/ Clonezilla]<br />
**Boots from live CD, USB flash drive, or PXE server<br />
**Uses Partimage, ntfsclone, partclone, and dd, <br />
**Compatability with many file systems (ext2, ext3, ext4, reiserfs, xfs, jfs of GNU/Linux, FAT, NTFS, and HFS+)<br />
**Multicasting server to restore to many machines at once<br />
**If file system is supported , only used blocks in harddisk are saved and restored. For unsupported file system, sector-to-sector copy is done<br />
* [http://www.partimage.org/Main_Page Partimage]<br />
*[http://www.fsarchiver.org/Main_Page Fsarchiver] (in extra repo)<br />
**Support for basic file attributes (permissions, owner, ...)<br />
**Support for multiple file-systems per archive<br />
**Support for extended attributes (they are used by SELinux)<br />
**Support the basic file-system attributes (label, uuid, block-size) for all linux file-systems<br />
**Support for [http://www.fsarchiver.org/Cloning-ntfs ntfs filesystems] (ability to create flexible clones of windows partitions)<br />
**Checksumming of everything which is written in the archive (headers, data blocks, whole files)<br />
**Ability to restore an archive which is corrupt (it will just skip the current file)<br />
**Multi-threaded lzo, gzip, bzip2, lzma [[Compression|compression]]: if you have a dual-core / quad-core it will use all the power of your cpu<br />
**Lzma [[Compression|compression]] (slow but very efficient algorithm) to make your archive smaller.<br />
**Support for splitting large archives into several files with a fixed maximum size<br />
**Encryption of the archive using a password. Based on blowfish from libcrypto from openssl.<br />
**Support backup of a mounted root filesystem (-A option)<br />
<br />
<br />
== Versioning systems ==<br />
<br />
These are traditionally used for keeping track of software development; but if you want to have a simple way to manage your config files in one directory, it might be a good solution.<br />
<br />
* [http://www.selenic.com/mercurial/wiki/ mercurial] or [http://git.or.cz/ git] (both in extra repo)<br />
* [http://eigenclass.org/hiki/gibak-backup-system-introduction gibak]: a backup system based on git. it also supports binary diffs (for binaries, e-books, pictures, multimedia files, etc). on the homepage there is a short usage advice. it is meant to backup only the $HOME directory. one could also backup other directories (like /etc) by changing the $HOME variable to point to that directory (though i don't really recommend this). gibak is handy for people who are familiar with git. it uses .gitignore to filter files and one can use the git commands to restore files, browse through logs, diffs, etc. if one needs a gui, it is also possible to use gitk or qgit to browse through commits or do whatever these interfaces support. get it from AUR: http://aur.archlinux.org/packages.php?ID=18318.<br />
== Articles ==<br />
<br />
* [http://www.halfgaar.net/backing-up-unix Backing up Linux and other Unix(-like) systems]<br />
<br />
[[Category:System recovery (English)]]</div>LeCrayonVert