https://wiki.archlinux.org/api.php?action=feedcontributions&user=Jgaray&feedformat=atomArchWiki - User contributions [en]2024-03-28T20:59:46ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=LibreOffice_(Espa%C3%B1ol)&diff=162790LibreOffice (Español)2011-09-28T16:19:50Z<p>Jgaray: Partially corrected. Still a lot to be done.</p>
<hr />
<div>[[Category:Office (Español)]]<br />
{{i18n|LibreOffice}}<br />
[[fr:Openoffice]]<br />
<br />
de [http://www.libreoffice.org/ Home - LibreOffice]:<br />
<br />
:"LibreOffice es la poderosa suite de productividad personal de código abierto para Windows, Macintosh y Linux, que le ofrece seis aplicaciones ricas en funcionalidades para todas las necesidades de procesamiento de documentos y datos: Writer, Calc, Impress, Draw, Matemáticas y Base. Nuestra gran comunidad de diligentes usuarios, colaboradores y desarrolladores le ofrecen asistencia gratuita. ¡Usted también puede participar!''<br />
<br />
==LibreOffice en Arch Linux==<br />
<br />
El apoyo oficial a [[OpenOffice.org]] se abandonó en favor de LibreOffice. Más información: [http://mailman.archlinux.org/pipermail/arch-general/2011-March/018819.html Quitar OpenOffice Oracle (Arch-general)].<br />
<br />
LibreOffice es el fork de la ''Document Foundation'' en el repositorio extra, que incluye mejoras y nuevas características.<br />
<br />
==Instalación==<br />
<br />
Asegúrese de instalar las fuentes, de lo contrario verá sólo rectángulos:<br />
# pacman-S dejavu ttf-artwiz-fuentes<br />
<br />
Descargar la base para estable/beta/devel:<br />
# pacman-S libreoffice<br />
<br />
Descargar un paquete de idioma.<br />
# pacman-S libreoffice-es ....<br />
<br />
Examine las dependencias opcionales que pacman sugiere. Por ejemplo, puede instalar un entorno de ejecución Java (opcional pero muy recomendable). Ver: [[Java]]<br />
<br />
==Extensiones de gestión==<br />
<br />
Arch ofrece algunas extensiones adicionales. En este momento son: pdfimport presentation-minimizer presenter-screen report-builder wiki-publisher ct2n hunart numbertext oooblogger typo watch-window diagram.<br />
<br />
* Si usted considera que algunas de ellas pueden serle útiles, instálelas<br />
# pacman-S libreoffice-extensión-nlpsolver libreoffice-extensión-fu ...<br />
<br />
Compruebe el gestor de Extensiones incorporado en LibreOffice, u [http://libreplanet.org/wiki/Group:OpenOfficeExtensions/List Obtenga extensiones en Internet] si desea instalar más extensiones.<br />
<br />
==Corrección de ortografía==<br />
Para revisar la ortografía necesitará hunspell y un diccionario de hunspell (como hunspell-es, hunspell-en, etc.)<br />
# pacman -S hunspell hunspell-es<br />
<br />
==Reglas de división de palabras==<br />
Para disponer de las reglas de división también necesitará hyphen + un conjunto de reglas (hyphen-en, hyphen-de)<br />
# pacman -S hyphen hyphen-es<br />
<br />
==Sinónimos==<br />
Para la opción Sinónimos necesitará mythes + un libro de sinónimos de mythes (mythes-en mythes-es)<br />
# pacman -S mythes mythes-es<br />
<br />
==Instalando Macros==<br />
En la mayoría de las distros linux, la ruta predeterminada para las macros es la siguiente:<br />
~/.openoffice.org/3/user/Scripts/<br />
La ruta de este directorio para LibreOffice en Arch Linux es:<br />
~/.config/.libreoffice/3/user/Scripts/<br />
<br />
Otra cosa a tener en cuenta es que si desea utilizar las macros, debe tener habilitado JRE. El uso de un JRE es la opción por defecto, pero desactivar su uso es uno de los consejos que se dan más abajo para acelerar la velocidad de LibreOffice.<br />
<br />
==Ejecutar LibreOffice==<br />
<br />
Si desea ejecutar un módulo específico de LibreOffice (en lugar del Centro de Inicio de LibreOffice (soffice todavía se incluye por razones de compatibilidad)), por ejemplo, el procesador de texto (Write), hoja de cálculo (Calc) o el programa de presentaciones (Impress), pruebe los siguientes scripts:<br />
<br />
Writer<br />
/usr/bin/libreoffice -writer or /usr/bin/soffice -writer<br />
<br />
Calc<br />
/usr/bin/libreoffice -calc<br />
<br />
Impress<br />
/usr/bin/libreoffice -impress<br />
<br />
Draw<br />
/usr/bin/libreoffice -draw<br />
<br />
Math (Editor de formulas)<br />
/usr/bin/libreoffice -math<br />
<br />
Base (Interface de base de datos)<br />
/usr/bin/libreoffice -base<br />
<br />
==Acelerar LibreOffice==<br />
Algunos ajustes pueden mejorar el tiempo de carga LibreOffice y la capacidad de respuesta. Sin embargo, algunos también aumentar el uso de memoria RAM, así que úselos con cuidado. Se puede acceder a todos ellos en "Herramientas> Opciones".<br />
* Bajo "memoria":<br />
** Reducir el número de pasos de Deshacer a una cifra inferior a 100, por ejemplo entre 20 y 30 pasos.<br />
** En caché para gráficos, configure Uso para LibreOffice a 128 MB (desde el valor original de 20MB).<br />
** Configure la memoria para cada objeto a 20 MB (desde el valor predeterminado de 5 MB).<br />
** Si utiliza LibreOffice menudo, pruebe el Inicio Rápido de LibreOffice.<br />
* En Java'''', desactive Usar un entorno de ejecución Java.<br />
{{Nota | Para obtener una lista de las funciones que dependen de Java, consulte esta página: http://wiki.services.openoffice.org/wiki/Java - Aún se necesita}?}<br />
<br />
<br />
==Solución de problemas==<br />
===Sustitución de fuentes===<br />
<br />
Esta configuración se puede cambiar en las opciones LibreOffice. En el menú desplegable, seleccione ''Herramientas> Opciones> LibreOffice> Fuentes''. Marque la casilla que dice''Aplicar''sustitución de tablas. Escriba {{Codeline|Andale Sans UI}} en el cuadro Fuente y elija su tipo de letra seado para la opción de reemplazar''con''. Cuando termine, haga clic en la''marca''. A continuación, seleccione el''siempre''y''sólo''opciones de pantalla en el cuadro a continuación. Haga clic en Aceptar.<br />
A continuación, tendrá que ir a''Herramientas> Opciones LibreOffice>''> Ver y desmarque la opción "Usar fuente del sistema para la interfaz de usuario ". Si utiliza una fuente no antialised, como Arial, también tendrá que desactivar "anti-aliasing de pantalla de la fuente" antes de las fuentes de menú procesar correctamente.</div>Jgarayhttps://wiki.archlinux.org/index.php?title=ATI&diff=84808ATI2009-11-23T06:06:55Z<p>Jgaray: /* HDMI with sound */</p>
<hr />
<div>[[Category: Graphics (English)]]<br />
[[Category: X Server (English)]]<br />
[[Category: HOWTOs (English)]]<br />
{{Article summary start| Summary}}<br />
{{Article summary text|Information on ATi Proprietary and Opensource Drivers.}}<br />
{{Article summary heading|Available Languages}}<br />
{{i18n_entry|English|ATI}}<br />
{{i18n_entry|简体中文|ATI 驱动安装配置 (简体中文)}}<br />
{{i18n_entry|Italiano|ATI (Italiano)}}<br />
{{i18n_entry|Türkçe|ATI (Türkçe)}}<br />
{{i18n_entry|Русский|ATI (Русский)}}<br />
{{Article summary end}}<br />
<br />
'''ATI''' owners have a choice between the proprietary (''catalyst'') or the opensource counterparts, (''xf86-video-ati'' or ''RadeonHD'').<br />
<br />
Currently, the performance of the open-source drivers (xf86-video-ati or xf86-video-radeonhd) is not on par with that of the proprietary, on demanding OpenGL applications (like 3D Games). They also currently lack some features, such as reliable TV-out support. On the other hand, they offer better dual-head support (xf86-video-ati), excellent 2D acceleration and provide sufficient 3D acceleration for OpenGL accelerated window managers, like Compiz.<br />
<br />
If unsure of which to use, try the open-source drivers first, because they will suit most needs and are generally less problematic. Also see the [http://www.x.org/wiki/RadeonFeature feature matrix] for the current state of feature implementation.<br />
<br />
== Rxxx? ==<br />
The Rxxx name-scheme refers to the code-name of the product.<br />
For finding your Codename, refer to wikipedia:<br />
[http://en.wikipedia.org/wiki/Comparison_of_ATI_Graphics_Processing_Units]<br />
<br />
= Open-source drivers =<br />
== Differences between open-source drivers ==<br />
*<code>xf86-video-ati</code> (The '''radeon''' driver) : <br />
**Works with Radeon chipsets up to X1950 (latest R500 chipsets) as well as HD2xxx (latest R600 chipsets). <br />
**Radeons up to the 9200 series are fully supported, stable, and full 2D and 3D acceleration are provided. <br />
**Radeons from 9500 to X1950 have full 2D acceleration and functional 3D acceleration, but are not supported by all the features that the proprietary driver provides (for example, powersaving is still in a testing phase). <br />
**Supports DRI1, RandR 1.2/1.3, EXA acceleration and Kernel-Mode-Setting/DRI2 (with the latest Linux kernel, libDRM and Mesa versions).<br />
**All cards from HD2xxx (R6xx) and newer are supported, but for now, with 2D support only.<br />
<br />
A full list of supported chipsets can be found [http://dri.freedesktop.org/wiki/ATI here]. <br />
<br />
{{Note|'''HDMI''' support will soon be implemented in '''xf86-video-ati''' over AtomBIOS.}}<br />
<br />
*<code>xf86-video-radeonhd</code> (The '''radeonhd''' driver):<br />
**Driver for ATI R500 chipsets (Radeon X1000 series) and '''newer'''. <br />
**Written by Novell with specifications provided to the public by AMD. <br />
**Supports RandR 1.2 and is under heavy development. It does also support HDMI with sound, (if your hardware is so equipped).<br />
<br />
Generally, '''xf86-video-ati''' seems to offer more consistent performance as compared to '''xf86-video-radeonhd''', so it should be your first choice.<br />
<br />
== Installation and configuration ==<br />
<br />
=== Installation ===<br />
{{Note| If you have previously installed the proprietary driver, make sure to remove <code>catalyst</code> and '''reboot'''.}}<br />
<br />
To install <code>xf86-video-ati</code> :<br />
pacman -S xf86-video-ati libgl ati-dri<br />
<br />
To install <code>xf86-video-radeonhd</code> : <br />
pacman -S xf86-video-radeonhd libgl ati-dri<br />
<br />
{{Note|The GIT versions of these drivers can be found on [[AUR]]}}<br />
<br />
=== Configuration ===<br />
You now have the choice between creating an xorg.conf, or attempting to use the recently enabled '''Xorg''' autodetection. <br />
<br />
==== Running Xorg without xorg.conf ====<br />
In most cases, Xorg can '''autodetect''' your hardware settings. The Xorg.conf configuration file in /etc/X11 is optional since Xorg-server 1.5.x.<br />
<br />
Always make sure you have '''HAL''', '''mesa''', the group '''xorg''' and the group '''xorg-input-drivers''' installed:<br />
pacman -S hal xorg-input-drivers mesa xorg<br />
<br />
and that HAL has been added in DAEMONS array in '''/etc/rc.conf''' and is '''running'''.<br />
<br />
{{Note| With KMS (Kernel Mode Setting) enabled, '''xorg.conf may not be needed at all.''' For more info on Radeon Kernel mode-setting, read [http://wiki.archlinux.org/index.php/ATI#AMD.2FAti_cards_and_KernelModeSetting_.28KMS.29 this.]}}<br />
<br />
==== Running Xorg with expanded xorg.conf ====<br />
{{Note| /etc/X11/xorg.conf no longer requires sections for all input devices because HAL can configure some/all via hotplugging. (Ensure '''HAL''' is running and '''xorg-input-drivers''' are installed.)}}<br />
<br />
In case you want manual configuration, edit your [[xorg.conf]], and add or make sure you have the following in their given sections:<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "drm"<br />
EndSection<br />
<br />
Device section for <code>xf86-video-ati</code> :<br />
Section "Device"<br />
Identifier "name" # your alias<br />
Driver "radeon"<br />
EndSection<br />
<br />
Device section for <code>xf86-video-radeonhd</code> :<br />
Section "Device"<br />
Identifier "name" # your alias<br />
Driver "radeonhd"<br />
Option "AccelMethod" "exa" # to enable 2D and Xv acceleration on R6xx/R7xx - default AccelMethod shadowfb<br />
Option "DRI" "on" # to enable 2D and Xv acceleration on R6xx/R7xx - default DRI disabled<br />
EndSection<br />
<br />
{{Note|Try below for smooth performance,over Option "DRI", for RS780M/MN [Radeon HD 3200] using the radeonhd driver(as of 3rd May 2009)}}<br />
<br />
This section (DRI) is not needed (thus deprecated),'''but''' use it if you encounter DRI related problems.<br />
Section "DRI"<br />
Group "video"<br />
Mode 0666<br />
EndSection<br />
<br />
When using the opensource drivers, ensure <code>catalyst</code> is ''not'' installed-- use <code>ati-dri</code> instead. Otherwise, the wrong <code>libGL.so</code> will be installed, which will cause direct rendering to fail.<br />
== AMD/Ati cards and kernel mode-setting (KMS) ==<br />
'''Kernel mode-setting''' is a technology that puts the work of setting graphics output modes into kernel space. This allows for a cleaner implementation, and means that switching VTs (Ctrl+Alt+F1, etc.) is nearly instantaneous. KMS also allows a full-resolution framebuffer (which is nice for high-res displays in console mode). KMS requires Xorg free video userspace driver '''xf86-video-ati''' 6.12.4 or later. KMS enables more technologies (like DRI2) that will reduce artifacts and increase 3D performance. Eventually, all Xorg video drivers will be replaced by corresponding kernel drivers which support KMS.<br />
<br />
Since version 2.6.31, kms is available and '''''is enabled by default in the default Arch kernel'''''.<br />
<br />
{{Note| For now, only Radeons up to '''R5xx''' (X1xxx) support KMS. Support for later Radeon cards will be added in Linux kernel 2.6.32.}}<br />
<br />
=== Early start ===<br />
This method will start KMS as early as possible in the boot process, when the initramfs is loaded.<br />
<br />
1) Remove all '''"vga="''' and '''"video="''' options from your kernel appendline in /boot/grub/menu.lst. Using other framebuffer drivers (such as uvesafb/radeonfb) will conflict with KMS. Remove any framebuffer relates modules from /etc/mkinitcpio.conf.<br />
<br />
2) Add '''"radeon"''' (without quotes) to MODULES array in '''/etc/mkinitcpio.conf'''. Depending on your chipset it may be necessary to add "intel_agp" before the radeon module.<br />
<br />
3) Re-generate your initcpio:<br />
mkinitcpio -p kernel26<br />
<br />
4) '''Reboot''' your system.<br />
<br />
=== Late start ===<br />
With this choice, KMS will be enabled when the '''boot process''' says, "'''Loading modules'''."<br />
<br />
1) Remove all '''"vga="''' and '''"video="''' options from your kernel appendline in '''/boot/grub/menu.lst'''. Using other framebuffer drivers (such as uvesafb/radeonfb) will conflict with KMS. Remove any framebuffer relates modules from '''/etc/mkinitcpio.conf'''.<br />
<br />
2) Add '''"radeon"''' module or "intel_agp radeon" if needed to the modules array in your /etc/rc.conf<br />
<br />
Some users have reported '''udev''' module loading can be speed up by adding '''"options radeon modeset=1"''' to your /etc/modprobe.d/modprobe.conf file.<br />
<br />
3) '''Reboot''' your system.<br />
<br />
If you are lucky your system will boot with both possible ways straight with proper framebuffer resolution and Xorg will start very quick.<br />
<br />
{{Warning| If late start '''won't''' work for you, try the [http://wiki.archlinux.org/index.php/ATI#Early_start early start of Kernel Mode Setting].}}<br />
<br />
=== Kernel Mode Setting Troubleshooting ===<br />
<br />
==== Slow or no compositing after having KMS enabled ====<br />
You must have these package versions installed at least in order to have both KMS and 3D desktop compositing enabled:<br />
kernel26 2.6.31.x<br />
mesa 7.5.x<br />
ati-dri 7.5.x<br />
libgl 7.5.x<br />
xf86-video-ati 6.12.4<br />
<br />
If these are already installed but you still can't have both KMS and 3D compositing enabled (or if 3D compositing is slow), [http://wiki.archlinux.org/index.php/ATI#Disable_KMS disable KMS.]<br />
<br />
{{Note| ''Most'' problems and major drawbacks are supposed to be solved if the installed Mesa's version is at least 7.'''6'''.x. That's a warning for those that haven't upgraded to Mesa 7.6 yet.}}<br />
<br />
==== KMS related problems' solutions ====<br />
<br />
===== Disable KMS =====<br />
{{Warning| Follow this section, if you encounter such problems, like: '''kernel crash, Xorg refusing to start, Xorg unloading the DRI2 module and falling back to mesa software rasterizer meaning no 3D acceleration.'''}}<br />
<br />
The solution is to '''disable''' experimental KMS and fall back to the '''old''' behavior. <br />
<br />
1) Add '''"radeon.modeset=0"''' into the kernel append line<br />
in '''/boot/grub/menu.lst''' or the lilo configuration file. <br />
<br />
If '''"radeon.modeset=0"''' won't work, try adding '''"nomodeset"''' instead.<br />
<br />
2) If you have added '''"radeon"''' in MODULES array in '''mkinitcpio.conf''', remove it.<br />
<br />
3) '''Rebuild the initramfs''' with<br />
mkinitcpio -p kernel26<br />
<br />
{{Warning | Catalyst users: You will probably also need to blacklist module loading for radeon. Put "'''!'''radeon" into your modules array in /etc/rc.conf.}}<br />
<br />
* Options for modules can be provided in a file under '''/etc/modprobe.d/'''. If you are using the '''radeon''' module (which you can see if it's loaded with the command<br />
<code>lsmod | grep radeon </code>, you can switch off KMS by creating a file specifying the module options e.g. '''/etc/modprobe.d/radeon.conf''' <br />
options radeon modeset=0<br />
<br />
4) '''Reboot''' your system.<br />
<br />
===== Delete xorg.conf =====<br />
Deleting xorg.conf, which may include options that may cause problems regarding driver's behaviour, try making a backup of your xorg.conf, and then delete it.<br />
<br />
After that, '''restart''' Xorg.<br />
=== Performance tuning ===<br />
The following options apply to Section "'''Device'''" in /etc/X11/'''xorg.conf'''.<br />
<br />
==== Tuning performance with xf86-video-ati ====<br />
By design, xf86-video-ati runs at AGP 1x speed. It is generally safe to modify this. If you notice hangs, try reducing the value or removing the line entirely (you can use values 1, 2, 4, 8).<br />
Option "AGPMode" "4"<br />
<br />
'''ColorTiling''' is completely safe to enable and supposedly is enabled by default. People have noticed a performance increase when enabled via xorg.conf.<br />
Option "ColorTiling" "on"<br />
<br />
'''Acceleration architecture'''; this will work only on '''newer''' cards. If you enable this and then can't get back into X, remove it.<br />
Option "AccelMethod" "EXA"<br />
<br />
'''Page Flip''' is generally safe to enable. This would mostly be used on older cards, as enabling this would disable EXA. With recent drivers can be used together with EXA.<br />
Option "EnablePageFlip" "on" <br />
<br />
'''AGPFastWrite''' will enable fast writes for AGP cards. This one can be problematic, so be prepared to remove it if you can't get into X.<br />
Option "AGPFastWrite" "yes"<br />
<br />
'''EXAVSync ''' option attempts to avoid tearing by stalling the engine until the display controller has passed the destination region. It reduces tearing at the cost of performance and has been know to cause instability on some chips.<br />
Really usefull when enabling Xv overlay on videos on a 3D accelerated desktop. This will not be necessary when UXA acceleration (throught DRI2) will be implemented succesfully into the xf86-video-ati driver.<br />
<br />
Option "EXAVSync" "yes"<br />
<br />
See an example Device Section in xorg.conf:<br />
<pre><br />
Section "Device"<br />
Identifier "My Graphics Card"<br />
Driver "radeon"<br />
Option "DRI" "on" <br />
Option "DynamicPM" "on" # Dynamic powersaving.<br />
Option "ClockGating" "on" # Assisting option for powersaving.<br />
Option "AccelMethod" "EXA" # EXA should fit most cases.<br />
Option "EXAVSync" "on" # EXAVSync is explained above.<br />
Option "DMAForXv" "on" # Forced option in order to enable Xv overlay.<br />
Option "ScalerWidth" "2048" # That should fix some very rare bugs.<br />
Option "EnablePageFlip" "on" # It will not be enabled on R5xx cards.<br />
Option "RenderAccel" "on" # Optional. It should be enabled by default.<br />
Option "AccelDFS" "on" #Optional. See the man page.<br />
BusID "PCI:1:0:0"<br />
EndSection<br />
</pre><br />
<br />
<br />
'''See the manpage for more configuration options.'''<br />
<code>man radeon</code><br />
<br />
A fine tool to try is [http://aur.archlinux.org/packages.php?do_Details=1&ID=2994 driconf]. It will allow you to modify several settings, like vsync, anisotropic filtering, texture compression, etc. Using this tool it is also possible to "disable Low Impact fallback" needed by some programs (e.g. Google Earth).<br />
<br />
==== Tuning performance with xf86-video-radeonhd ====<br />
TODO<br />
<br />
=== TV out ===<br />
Since August 2007, there is TV-out support for all Radeons with integrated TV-out.<br />
<br />
It is somewhat limited for now, it doesn't always autodetect the output correctly and only NTSC mode works.<br />
<br />
First, check that you have an S-video output: <code>xrandr</code> should give you something like<br />
Screen 0: minimum 320x200, current 1024x768, maximum 1280x1200<br />
...<br />
S-video disconnected (normal left inverted right x axis y axis)<br />
<br />
Now we should tell Xorg that it is actually connected (it ''is'', right?)<br />
xrandr --output S-video --set load_detection 1<br />
<br />
Setting tv standard to use:<br />
xrandr --output S-video --set tv_standard ntsc<br />
<br />
Adding a mode for it (currently it supports only 800x600):<br />
xrandr --addmode S-video 800x600<br />
<br />
I'll go for a clone mode:<br />
xrandr --output S-video --same-as VGA-0<br />
<br />
So far so good. Now let's try to see what we have:<br />
xrandr --output S-video --mode 800x600<br />
<br />
At this point you should see a 800x600 version of your desktop on your TV.<br />
<br />
To disable the output, do<br />
xrandr --output S-video --off<br />
<br />
Also you may notice that the video is being played on monitor only and not on the TV. Where the Xv overlay is sent is controlled by XV_CRTC attribute.<br />
<br />
To send the output to the TV, I do<br />
xvattr -a XV_CRTC -v 1<br />
<br />
{{Note| you need to install '''xvattr''' from [[AUR]] to execute this command.}}<br />
<br />
To switch back to my monitor, I change this to <code>0</code>. <code>-1</code> is used for automatic switching in dualhead setups.<br />
<br />
Please see [http://www.x.org/wiki/radeonTV Enabling TV-Out Statically] for how to enable TV-out in your xorg config file.<br />
<math>Insert formula here</math><br />
<br />
=== HDMI with sound ===<br />
Given that your hardware supports it, and you have installed '''xf86-video-radeonhd''' (note: The driver '''xf86-video-ati''' will soon get HDMI support.) you can insert the following into xorg.conf to enable HDMI with sound:<br />
Section "Device"<br />
# ...<br />
Option "Audio" "on"<br />
Option "HDMI" "all"<br />
EndSection<br />
<br />
Restart X when you have done this, try to see if there is sound transmitted to TV via HDMI cable.<br />
# Connect your PC to the TV via HDMI cable (duh).<br />
# Use xrandr to get picture to the TV. Ex: <code>xrandr --output DVI-D_1 --mode 1280x768 --right-of PANEL</code>. Simply typing <code>xrandr</code> will give you a list of your valid outputs.<br />
# Run <code>aplay -l</code> to get the list of your sound devices. Find HDMI and note the card number and corresponding device number. Example of what you want to see: <code>card 1: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI]</code><br />
# Try sending sound to this device: <code>aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Center.wav</code>. Be sure to change plughw:z,y to match your hardware number found with last command. You should be able to hear the test sound from your TV.<br />
<br />
==== Note on RV730 and RV710 ====<br />
<br />
'''xf86-video-radeonhd''' does not support yet audio through HDMI for these chipsets, but work is in progress.<br />
<br />
== Troubleshooting (xf86-video-ati & xf86-video-radeonhd) ==<br />
<br />
=== I encounter artifacts when I am trying to login into my DE or WM ===<br />
If you seem to have artifacts, first choose to login into your favorite DE or WM without xorg.conf in /etc/X11/. Most people try to create a proper xorg.conf for their system, but sometimes it may cause trouble. <br />
<br />
If you do that, don't forget to have '''HAL''' installed and running, and the group '''xorg-input-drivers''' installed.<br />
<br />
{{Warning| It is possible that those issues are KMS related. If that is the problem, [http://wiki.archlinux.org/index.php/ATI#Disable_KMS disable KMS.]}}<br />
<br />
=== I have switched from catalyst to radeonhd or radeon and some things don't work ===<br />
First of all, don't panic. Uninstall catalyst, install xf86-video-radeonhd or xf86-video-ati and then '''''reboot'''''.<br />
<br />
Make sure you are not using the xorg.conf generated by catalyst. Your original should have been backed up and you can recall it:<br />
cp /etc/X11/xorg.conf.original-0 /etc/X11/xorg.conf<br />
<br />
Otherwise, stop your graphical server if running, and in a tty, type as root:<br />
Xorg -configure<br />
mv xorg.conf.new /etc/X11/xorg.conf<br />
and make sure you put the required options.<br />
<br />
If it still doesn't solve your problem, know that apparently catalyst has the bad idea to replace Xorg files with symbolic links pointing to its own files. The easiest at this point is to uninstall all catalyst stuff (just to be on the safe side) and then to reinstall xorg, libgl, ati-dri and xf86-video-radeonhd or xf86-video-ati.<br />
<br />
If it still doesn't work, then have a look into the forum, your problem might be a configuration issue.<br />
<br />
{{Note| When you switch to '''xf86-video-ati''' or '''xf86-video-radeonhd''', remember that you can login without xorg.conf as well (without problems in most cases), since Xorg can autodetect your settings. So '''xorg.conf''' is optional.}}<br />
<br />
=== I have installed a free driver and my card is painfully slow ===<br />
<br />
Some cards can be installed by default trying to use [[ATI#AMD/Ati cards and kernel mode-setting (KMS) |KMS]]. You can check whether this is your case running:<br />
dmesg|egrep "drm|radeon"<br />
<br />
This command might show something like this, meaning it is trying to default to KMS:<br />
[drm] radeon default to kernel modesetting.<br />
...<br />
[drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon, disabling IOCTL<br />
<br />
If you know your card is not supposed to support KMS (read the link above), then you can [[ATI#Disable KMS|disable KMS]]. This should fix the problem.<br />
<br />
= Proprietary Catalyst driver=<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 />
== Supported devices ==<br />
Since v. '''9.4''', the propriatery ATI driver '''supports only R600 and newer devices''' (that means, HD2xxx and newer). For older cards, especially laptop users, be aware that the ATI Catalyst 8-8 driver only supports Xorg <= 7.3. Xorg 7.4 support was not introduced until the 8-10 Catalyst driver release. This means that if you are using Xorg 7.4 or newer with an older card, your only current option is the open-source drivers, especially '''xf86-video-ati'''. While Xorg 7.4 support is contained in the Catalyst 8-10 through 9-3 releases for older cards, those drivers are not presently packaged for Archlinux and numerous older cards have had trouble with those driver releases.<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 Kernel ===<br />
<br />
====kernel26====<br />
''Temporary '''warning''''': ''Catalyst '''9.10''' only works with '''xorg-server=<1.6''', not with '''xorg-server>=1.7''' available in [extra].''<br />
''For more info visit this link: http://bbs.archlinux.org/viewtopic.php?pid=649160#p649160''<br />
<br />
To install ATI's fglrx driver for the <code>kernel26</code> package, you need to install the <code>catalyst</code> package, that [http://aur.archlinux.org/packages.php?ID=29111 can be found in AUR]. You can build it via [[makepkg]].<br />
<br />
For a stock kernel, that's it. Configure your [[Xorg | xorg.conf]] as usual, if desired.<br />
<br />
=== Custom Kernels ===<br />
To install catalyst for a custom kernel, you'll need to build your own <code>catalyst-$kernel</code> package containing the kernel module compiled specifically for your kernel.<br />
<br />
If you are at all uncomfortable or inexperienced making packages, read up the [[ABS]] wiki page first so things go smoothly.<br />
<br />
==== Obtaining PKGBUILD ====<br />
Obtain the <code>PKGBUILD</code> and <code>catalyst.install</code> files from [http://aur.archlinux.org/packages.php?ID=22899 AUR].<br />
<br />
==== Editing the PKGBUILD and building ====<br />
Three changes need to be made here: <br />
<br />
1. Change<br />
pkgname=catalyst<br />
to<br />
pkgname=catalyst-KERNEL_NAME<br />
where KERNEL_NAME is whatever you want (e.g. custom, mm, themostawesomekernelever)<br />
<br />
2. Remove <code>kernel26</code> from the dependencies list.<br />
<br />
Finally, build and install the package. (<code>makepkg -i</code> or <code>makepkg</code> followed by <code>pacman -U pkgname.pkg.tar.gz</code>)<br />
<br />
==== Notes ====<br />
* If you run multiple kernels, then install catalyst module packages for all kernels. They won't conflict with one another.<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 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 don't have an xorg.conf file yet, run the following command to generate one:<br />
# Xorg -configure<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 />
== Troubleshooting (catalyst) ==<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 />
===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 />
===Compaq Presario Laptops===<br />
Even after installing the drivers and editing the configuration file as required, some laptops (e.g. Presario R4000 with Xpress 200M) just come up with a blank screen.<br />
<br />
The problem seems to be incorrect memory detected by the kernel(even if you have 128M of video memory lspci -v always reports 256M). Changing the BIOS settings so that it uses the "SidePort+UMA" option and 128M video memory plus another 128M taken from the system seems to work fine.<br />
<br />
It could be a bug in the BIOS or in the Linux PCI code.<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 />
= External links =<br />
More info can be found here<br />
* [http://wiki.cchtml.com/index.php/Main_Page Unofficial ATI Wiki]<br />
* [http://ati.cchtml.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content= Unofficial ATI Linux Bugtracker]<br />
* [http://www.rage3d.com/board/forumdisplay.php?f=88 Rage3D ATI Linux Forums]<br />
* [http://www.thinkwiki.org/wiki/Problems_with_fglrx ThinkWiki fglrx Problems page]<br />
* [http://www.phoronix.com/scan.php?page=article&item=560 ATI R300: Open v. Closed Drivers] (''deprecated'' since April 2009)<br />
* [http://www.thinkwiki.org/wiki/Additional_options_for_the_radeon_driver Additional options for the radeon driver] (there are though deprecated options referenced there)<br />
* [http://www.phoronix.com/scan.php?page=article&item=936&num=1 Hidden ATI Feature For Textured XRendering]</div>Jgarayhttps://wiki.archlinux.org/index.php?title=ATI&diff=84413ATI2009-11-18T22:03:35Z<p>Jgaray: /* I have switched from catalyst to radeonhd or radeon and some things don't work */</p>
<hr />
<div>[[Category: Graphics (English)]]<br />
[[Category: X Server (English)]]<br />
[[Category: HOWTOs (English)]]<br />
{{Article summary start| Summary}}<br />
{{Article summary text|Information on ATi Proprietary and Opensource Drivers.}}<br />
{{Article summary heading|Available Languages}}<br />
{{i18n_entry|English|ATI}}<br />
{{i18n_entry|简体中文|ATI 驱动安装配置 (简体中文)}}<br />
{{i18n_entry|Italiano|ATI (Italiano)}}<br />
{{i18n_entry|Türkçe|ATI (Türkçe)}}<br />
{{i18n_entry|Русский|ATI (Русский)}}<br />
{{Article summary end}}<br />
<br />
'''ATI''' owners have a choice between the proprietary (''catalyst'') or the opensource counterparts, (''xf86-video-ati'' or ''RadeonHD'').<br />
<br />
Currently, ''xf86-video-ati'' is preferred for GPUs up to R5xx (X1xxx) and ''RadeonHD'' for cards from R5xx and newer. The proprietary ''catalyst'' only supports R6xx (HD2xxx) and ''newer'' cards.<br />
<br />
The proprietary driver, version 7.10 (8.42.3) and later, supports [[AIGLX]]. To use composite managers such as [[Compiz Fusion]] or [[KDE|KWin4]] you can now use the open-source drivers or the proprietary driver. Currently, the performance of the open-source drivers (xf86-video-ati or xf86-video-radeonhd) is not on par with that of the proprietary, on demanding OpenGL applications (like 3D Games). They also currently lack some features, such as reliable TV-out support. On the other hand, they offer better dual-head support (xf86-video-ati), excellent 2D acceleration and provide sufficient 3D acceleration for OpenGL accelerated window managers, like Compiz.<br />
<br />
If unsure of which to use, try the open-source drivers first, because they will suit most needs and are generally less problematic. Also see the [http://www.x.org/wiki/RadeonFeature feature matrix] for the current state of feature implementation.<br />
<br />
== Rxxx? ==<br />
The Rxxx name-scheme refers to the code-name of the product.<br />
For finding your Codename, refer to wikipedia:<br />
[http://en.wikipedia.org/wiki/Comparison_of_ATI_Graphics_Processing_Units]<br />
<br />
= Open-source drivers =<br />
<br />
== AMD/Ati cards and kernel mode-setting (KMS) ==<br />
'''Kernel mode-setting''' is a technology that puts the work of setting graphics output modes into kernel space. This allows for a cleaner implementation, and means that switching VTs (Ctrl+Alt+F1, etc.) is nearly instantaneous. KMS also allows a full-resolution framebuffer (which is nice for high-res displays in console mode). KMS requires Xorg free video userspace driver '''xf86-video-ati''' 6.12.4 or later. KMS enables more technologies (like DRI2) that will reduce artifacts and increase 3D performance. Eventually, all Xorg video drivers will be replaced by corresponding kernel drivers which support KMS.<br />
<br />
Since the official Kernel 2.6.31, experimental mode-setting is enabled.<br />
<br />
{{Note| For now, only Radeons up to '''R5xx''' (X1xxx) support KMS. Support for later Radeon cards will be added in Linux kernel 2.6.32.}}<br />
<br />
=== Early start ===<br />
This method will start KMS as early as possible in the boot process, when the initramfs is loaded.<br />
<br />
1) Remove all '''"vga="''' and '''"video="''' options from your kernel appendline in /boot/grub/menu.lst. Using other framebuffer drivers (such as uvesafb/radeonfb) will conflict with KMS. Remove any framebuffer relates modules from /etc/mkinitcpio.conf.<br />
<br />
2) Add '''"radeon"''' (without quotes) to MODULES array in '''/etc/mkinitcpio.conf'''. Depending on your chipset it may be necessary to add "intel_agp" before the radeon module.<br />
<br />
3) Re-generate your initcpio:<br />
mkinitcpio -p kernel26<br />
<br />
4) '''Reboot''' your system.<br />
<br />
=== Late start ===<br />
With this choice, KMS will be enabled when the '''boot process''' says, "'''Loading modules'''."<br />
<br />
1) Remove all '''"vga="''' and '''"video="''' options from your kernel appendline in '''/boot/grub/menu.lst'''. Using other framebuffer drivers (such as uvesafb/radeonfb) will conflict with KMS. Remove any framebuffer relates modules from '''/etc/mkinitcpio.conf'''.<br />
<br />
2) Add '''"radeon"''' module or "intel_agp radeon" if needed to the modules array in your /etc/rc.conf<br />
<br />
Some users have reported '''udev''' module loading can be speed up by adding '''"options radeon modeset=1"''' to your /etc/modprobe.d/modprobe.conf file.<br />
<br />
3) '''Reboot''' your system.<br />
<br />
If you are lucky your system will boot with both possible ways straight with proper framebuffer resolution and Xorg will start very quick.<br />
<br />
{{Warning| If late start '''won't''' work for you, try the [http://wiki.archlinux.org/index.php/ATI#Early_start early start of Kernel Mode Setting].}}<br />
<br />
=== Kernel Mode Setting Troubleshooting ===<br />
<br />
==== Slow or no compositing after having KMS enabled ====<br />
You must have these package versions installed at least in order to have both KMS and 3D desktop compositing enabled:<br />
kernel26 2.6.31.x<br />
mesa 7.5.x<br />
ati-dri 7.5.x<br />
libgl 7.5.x<br />
xf86-video-ati 6.12.4<br />
<br />
If these are already installed but you still can't have both KMS and 3D compositing enabled (or if 3D compositing is slow), [http://wiki.archlinux.org/index.php/ATI#Disable_KMS disable KMS.]<br />
<br />
{{Note| ''Most'' problems and major drawbacks are supposed to be solved if the installed Mesa's version is at least 7.'''6'''.x. That's a warning for those that haven't upgraded to Mesa 7.6 yet.}}<br />
<br />
==== KMS related problems' solutions ====<br />
<br />
===== Disable KMS =====<br />
{{Warning| Follow this section, if you encounter such problems, like: '''kernel crash, Xorg refusing to start, Xorg unloading the DRI2 module and falling back to mesa software rasterizer meaning no 3D acceleration.'''}}<br />
<br />
The solution is to '''disable''' experimental KMS and fall back to the '''old''' behavior. <br />
<br />
1) Add '''"radeon.modeset=0"''' into the kernel append line<br />
in '''/boot/grub/menu.lst''' or the lilo configuration file. <br />
<br />
If '''"radeon.modeset=0"''' won't work, try adding '''"nomodeset"''' instead.<br />
<br />
2) If you have added '''"radeon"''' in MODULES array in '''mkinitcpio.conf''', remove it.<br />
<br />
3) '''Rebuild the initramfs''' with<br />
mkinitcpio -p kernel26<br />
<br />
{{Warning | Catalyst users: You will probably also need to blacklist module loading for radeon. Put "'''!'''radeon" into your modules array in /etc/rc.conf.}}<br />
<br />
* Options for modules can be provided in a file under '''/etc/modprobe.d/'''. If you are using the '''radeon''' module (which you can see if it's loaded with the command<br />
<code>lsmod | grep radeon </code>, you can switch off KMS by creating a file specifying the module options e.g. '''/etc/modprobe.d/radeon.conf''' <br />
options radeon modeset=0<br />
<br />
4) '''Reboot''' your system.<br />
<br />
===== Delete xorg.conf =====<br />
Deleting xorg.conf, which may include options that may cause problems regarding driver's behaviour, try making a backup of your xorg.conf, and then delete it.<br />
<br />
After that, '''restart''' Xorg.<br />
<br />
== Differences between open-source drivers ==<br />
*<code>xf86-video-ati</code> (The '''radeon''' driver) : <br />
**Works with Radeon chipsets up to X1950 (latest R500 chipsets) as well as HD2xxx (latest R600 chipsets). <br />
**Radeons up to the 9200 series are fully supported, stable, and full 2D and 3D acceleration are provided. <br />
**Radeons from 9500 to X1950 have full 2D acceleration and functional 3D acceleration, but are not supported by all the features that the proprietary driver provides (for example, powersaving is still in a testing phase). <br />
**All cards from HD2xxx (R6xx) and newer are supported, but for now, with 2D support only. <br />
<br />
A full list of supported chipsets can be found [http://dri.freedesktop.org/wiki/ATI here]. The '''radeon''' driver also supports DRI1, RandR 1.2/1.3, EXA acceleration and Kernel-Mode-Setting/DRI2 (with the latest Linux kernel, libDRM and Mesa versions).<br />
<br />
{{Note|'''HDMI''' support will soon be implemented in '''xf86-video-ati''' over AtomBIOS.}}<br />
<br />
*<code>xf86-video-radeonhd</code> (The '''radeonhd''' driver):<br />
**Driver for ATI R500 chipsets (Radeon X1000 series) and '''newer'''. <br />
**Written by Novell with specifications provided to the public by AMD. <br />
**Supports RandR 1.2 and is under heavy development. It does also support HDMI with sound, (if your hardware is so equipped).<br />
<br />
Generally, '''xf86-video-ati''' seems to offer more consistent performance as compared to '''xf86-video-radeonhd''', so it should be your first choice.<br />
<br />
== Installation and configuration ==<br />
<br />
=== Packages' installation ===<br />
{{Note| If you have previously installed the proprietary driver, make sure to remove <code>catalyst</code> and <code>catalyst-utils</code> and '''reboot'''.}}<br />
<br />
To install <code>xf86-video-ati</code> :<br />
pacman -S xf86-video-ati libgl ati-dri<br />
<br />
To install <code>xf86-video-radeonhd</code> : <br />
pacman -S xf86-video-radeonhd libgl ati-dri<br />
<br />
{{Note|The GIT versions of these drivers can be found on [[AUR]]}}<br />
<br />
=== Configuration ===<br />
You now have the choice between creating an xorg.conf, or attempting to use the recently enabled '''Xorg''' autodetection. <br />
<br />
==== Running Xorg without xorg.conf ====<br />
In most cases, Xorg can '''autodetect''' your hardware settings. The Xorg.conf configuration file in /etc/X11 is optional since Xorg-server 1.5.x.<br />
<br />
Always make sure you have '''HAL''', '''mesa''', the group '''xorg''' and the group '''xorg-input-drivers''' installed:<br />
pacman -S hal xorg-input-drivers mesa xorg<br />
<br />
and that HAL has been added in DAEMONS array in '''/etc/rc.conf''' and is '''running'''.<br />
<br />
{{Note| With KMS (Kernel Mode Setting) enabled, '''xorg.conf may not be needed at all.''' For more info on Radeon Kernel mode-setting, read [http://wiki.archlinux.org/index.php/ATI#AMD.2FAti_cards_and_KernelModeSetting_.28KMS.29 this.]}}<br />
<br />
==== Running Xorg with expanded xorg.conf ====<br />
{{Note| /etc/X11/xorg.conf no longer requires sections for all input devices because HAL can configure some/all via hotplugging. (Ensure '''HAL''' is running and '''xorg-input-drivers''' are installed.)}}<br />
<br />
In case you want manual configuration, edit your [[xorg.conf]], and add or make sure you have the following in their given sections:<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "drm"<br />
EndSection<br />
<br />
Device section for <code>xf86-video-ati</code> :<br />
Section "Device"<br />
Identifier "name" # your alias<br />
Driver "radeon"<br />
EndSection<br />
<br />
Device section for <code>xf86-video-radeonhd</code> :<br />
Section "Device"<br />
Identifier "name" # your alias<br />
Driver "radeonhd"<br />
Option "AccelMethod" "exa" # to enable 2D and Xv acceleration on R6xx/R7xx - default AccelMethod shadowfb<br />
Option "DRI" "on" # to enable 2D and Xv acceleration on R6xx/R7xx - default DRI disabled<br />
EndSection<br />
<br />
{{Note|Try below for smooth performance,over Option "DRI", for RS780M/MN [Radeon HD 3200] using the radeonhd driver(as of 3rd May 2009)}}<br />
<br />
This section (DRI) is not needed (thus deprecated),'''but''' use it if you encounter DRI related problems.<br />
Section "DRI"<br />
Group "video"<br />
Mode 0666<br />
EndSection<br />
<br />
When using the opensource drivers, ensure <code>catalyst</code> and <code>catalyst-utils</code> are ''not'' installed-- use <code>ati-dri</code> instead. Otherwise, the wrong <code>libGL.so</code> will be installed, which will cause direct rendering to fail.<br />
<br />
=== Performance tuning ===<br />
The following options apply to Section "'''Device'''" in /etc/X11/'''xorg.conf'''.<br />
<br />
==== Tuning performance with xf86-video-ati ====<br />
By design, xf86-video-ati runs at AGP 1x speed. It is generally safe to modify this. If you notice hangs, try reducing the value or removing the line entirely (you can use values 1, 2, 4, 8).<br />
Option "AGPMode" "4"<br />
<br />
'''ColorTiling''' is completely safe to enable and supposedly is enabled by default. People have noticed a performance increase when enabled via xorg.conf.<br />
Option "ColorTiling" "on"<br />
<br />
'''Acceleration architecture'''; this will work only on '''newer''' cards. If you enable this and then can't get back into X, remove it.<br />
Option "AccelMethod" "EXA"<br />
<br />
'''Page Flip''' is generally safe to enable. This would mostly be used on older cards, as enabling this would disable EXA. With recent drivers can be used together with EXA.<br />
Option "EnablePageFlip" "on" <br />
<br />
'''AGPFastWrite''' will enable fast writes for AGP cards. This one can be problematic, so be prepared to remove it if you can't get into X.<br />
Option "AGPFastWrite" "yes"<br />
<br />
'''EXAVSync ''' option attempts to avoid tearing by stalling the engine until the display controller has passed the destination region. It reduces tearing at the cost of performance and has been know to cause instability on some chips.<br />
Really usefull when enabling Xv overlay on videos on a 3D accelerated desktop. This will not be necessary when UXA acceleration (throught DRI2) will be implemented succesfully into the xf86-video-ati driver.<br />
<br />
Option "EXAVSync" "yes"<br />
<br />
See an example Device Section in xorg.conf:<br />
<pre><br />
Section "Device"<br />
Identifier "My Graphics Card"<br />
Driver "radeon"<br />
Option "DRI" "on" <br />
Option "DynamicPM" "on" # Dynamic powersaving.<br />
Option "ClockGating" "on" # Assisting option for powersaving.<br />
Option "AccelMethod" "EXA" # EXA should fit most cases.<br />
Option "EXAVSync" "on" # EXAVSync is explained above.<br />
Option "DMAForXv" "on" # Forced option in order to enable Xv overlay.<br />
Option "ScalerWidth" "2048" # That should fix some very rare bugs.<br />
Option "EnablePageFlip" "on" # It will not be enabled on R5xx cards.<br />
Option "RenderAccel" "on" # Optional. It should be enabled by default.<br />
Option "AccelDFS" "on" #Optional. See the man page.<br />
BusID "PCI:1:0:0"<br />
EndSection<br />
</pre><br />
<br />
<br />
'''See the manpage for more configuration options.'''<br />
<code>man radeon</code><br />
<br />
A fine tool to try is [http://aur.archlinux.org/packages.php?do_Details=1&ID=2994 driconf]. It will allow you to modify several settings, like vsync, anisotropic filtering, texture compression, etc. Using this tool it is also possible to "disable Low Impact fallback" needed by some programs (e.g. Google Earth).<br />
<br />
==== Tuning performance with xf86-video-radeonhd ====<br />
TODO<br />
<br />
=== TV out ===<br />
Since August 2007, there is TV-out support for all Radeons with integrated TV-out.<br />
<br />
It is somewhat limited for now, it doesn't always autodetect the output correctly and only NTSC mode works.<br />
<br />
First, check that you have an S-video output: <code>xrandr</code> should give you something like<br />
Screen 0: minimum 320x200, current 1024x768, maximum 1280x1200<br />
...<br />
S-video disconnected (normal left inverted right x axis y axis)<br />
<br />
Now we should tell Xorg that it is actually connected (it ''is'', right?)<br />
xrandr --output S-video --set load_detection 1<br />
<br />
Setting tv standard to use:<br />
xrandr --output S-video --set tv_standard ntsc<br />
<br />
Adding a mode for it (currently it supports only 800x600):<br />
xrandr --addmode S-video 800x600<br />
<br />
I'll go for a clone mode:<br />
xrandr --output S-video --same-as VGA-0<br />
<br />
So far so good. Now let's try to see what we have:<br />
xrandr --output S-video --mode 800x600<br />
<br />
At this point you should see a 800x600 version of your desktop on your TV.<br />
<br />
To disable the output, do<br />
xrandr --output S-video --off<br />
<br />
Also you may notice that the video is being played on monitor only and not on the TV. Where the Xv overlay is sent is controlled by XV_CRTC attribute.<br />
<br />
To send the output to the TV, I do<br />
xvattr -a XV_CRTC -v 1<br />
<br />
{{Note| you need to install '''xvattr''' from [[AUR]] to execute this command.}}<br />
<br />
To switch back to my monitor, I change this to <code>0</code>. <code>-1</code> is used for automatic switching in dualhead setups.<br />
<br />
Please see [http://www.x.org/wiki/radeonTV Enabling TV-Out Statically] for how to enable TV-out in your xorg config file.<br />
<math>Insert formula here</math><br />
<br />
=== HDMI with sound ===<br />
Given that your hardware supports it, and you have installed '''xf86-video-radeonhd''' (note: The driver '''xf86-video-ati''' will soon get HDMI support.) you can insert the following into xorg.conf to enable HDMI with sound:<br />
Section "Device"<br />
# ...<br />
Option "Audio" "on"<br />
Option "HDMI" "all"<br />
EndSection<br />
<br />
Restart X when you have done this, try to see if there is sound transmitted to TV via HDMI cable.<br />
# Connect your PC to the TV via HDMI cable (duh).<br />
# Use xrandr to get picture to the TV. Ex: <code>xrandr --output DVI-D_1 --mode 1280x768 --right-of PANEL</code>. Simply typing <code>xrandr</code> will give you a list of your valid outputs.<br />
# Run <code>aplay -l</code> to get the list of your sound devices. Find HDMI and note the card number and corresponding device number. Example of what you want to see: <code>card 1: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI]</code><br />
# Try sending sound to this device: <code>aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Center.wav</code>. Be sure to change plughw:z,y to match your hardware number found with last command. You should be able to hear the test sound from your TV.<br />
<br />
== Troubleshooting (xf86-video-ati & xf86-video-radeonhd) ==<br />
<br />
=== I encounter artifacts when I am trying to login into my DE or WM ===<br />
If you seem to have artifacts, first choose to login into your favorite DE or WM without xorg.conf in /etc/X11/. Most people try to create a proper xorg.conf for their system, but sometimes it may cause trouble. <br />
<br />
If you do that, don't forget to have '''HAL''' installed and running, and the group '''xorg-input-drivers''' installed.<br />
<br />
{{Warning| It is possible that those issues are KMS related. If that is the problem, [http://wiki.archlinux.org/index.php/ATI#Disable_KMS disable KMS.]}}<br />
<br />
=== I have switched from catalyst to radeonhd or radeon and some things don't work ===<br />
First of all, don't panic. Uninstall catalyst and catalyst-utils, install xf86-video-radeonhd or xf86-video-ati and then '''''reboot'''''.<br />
<br />
Make sure you are not using the xorg.conf generated by catalyst. Your original should have been backed up and you can recall it:<br />
cp /etc/X11/xorg.conf.original-0 /etc/X11/xorg.conf<br />
<br />
Otherwise, stop your graphical server if running, and in a tty, type as root:<br />
Xorg -configure<br />
mv xorg.conf.new /etc/X11/xorg.conf<br />
and make sure you put the required options.<br />
<br />
If it still doesn't solve your problem, know that apparently catalyst has the bad idea to replace Xorg files with symbolic links pointing to its own files. The easiest at this point is to uninstall all catalyst stuff (just to be on the safe side) and then to reinstall xorg, libgl, ati-dri and xf86-video-radeonhd or xf86-video-ati.<br />
<br />
If it still doesn't work, then have a look into the forum, your problem might be a configuration issue.<br />
<br />
{{Note| When you switch to '''xf86-video-ati''' or '''xf86-video-radeonhd''', remember that you can login without xorg.conf as well (without problems in most cases), since Xorg can autodetect your settings. So '''xorg.conf''' is optional.}}<br />
<br />
=== I have installed a free driver and my card is painfully slow ===<br />
<br />
Some cards can be installed by default trying to use [[ATI#AMD/Ati cards and kernel mode-setting (KMS) |KMS]]. You can check whether this is your case running:<br />
dmesg|egrep "drm|radeon"<br />
<br />
This command might show something like this, meaning it is trying to default to KMS:<br />
[drm] radeon default to kernel modesetting.<br />
...<br />
[drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon, disabling IOCTL<br />
<br />
If you know your card is not supposed to support KMS (read the link above), then you can [[ATI#Disable KMS|disable KMS]]. This should fix the problem.<br />
<br />
= Proprietary Catalyst driver=<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 />
== Supported devices ==<br />
Since v. '''9.4''', the propriatery ATI driver '''supports only R600 and newer devices''' (that means, HD2xxx and newer). For older cards, especially laptop users, be aware that the ATI Catalyst 8-8 driver only supports Xorg <= 7.3. Xorg 7.4 support was not introduced until the 8-10 Catalyst driver release. This means that if you are using Xorg 7.4 with an older card, your only current option is the open-source drivers, especially '''xf86-video-ati'''. While Xorg 7.4 support is contained in the Catalyst 8-10 through 9-3 releases for older cards, those drivers are not presently packaged for Archlinux and numerous older cards have had trouble with those driver releases.<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] as well as [http://aur.archlinux.org/packages.php?ID=22510 catalyst-utils] are available on AUR.<br />
<br />
=== Stock Kernel ===<br />
<br />
====kernel26====<br />
''Temporary '''warning''''': ''Catalyst '''9.10''' only works with '''xorg-server=<1.6''', not with '''xorg-server>=1.7''' available in [extra].''<br />
''For more info visit this link: http://bbs.archlinux.org/viewtopic.php?pid=649160#p649160''<br />
<br />
To install ATI's fglrx driver for the <code>kernel26</code> package, you need to install the <code>catalyst</code> package, that [http://aur.archlinux.org/packages.php?ID=29111 can be found in AUR]. You can build it via [[makepkg]].<br />
<br />
This package contains '''only''' the kernel module, but also installs the <code>catalyst-utils</code> package as a dependency. The <code>catalyst-utils</code> package is kernel-independent and provides the libraries and utilities for Xorg, including ATI's own <code>libGL.so</code>.<br />
<br />
For a stock kernel, that's it. Configure your [[Xorg | xorg.conf]] as usual, if desired.<br />
<br />
=== Custom Kernels ===<br />
To install catalyst for a custom kernel, you'll need to build your own <code>catalyst-$kernel</code> package containing the kernel module compiled specifically for your kernel.<br />
<br />
If you are at all uncomfortable or inexperienced making packages, read up the [[ABS]] wiki page first so things go smoothly.<br />
<br />
==== Obtaining PKGBUILD ====<br />
Obtain the <code>PKGBUILD</code> and <code>catalyst.install</code> files from [http://aur.archlinux.org/packages.php?ID=22899 AUR].<br />
<br />
==== Editing the PKGBUILD and building ====<br />
Three changes need to be made here: <br />
<br />
1. Change<br />
pkgname=catalyst<br />
to<br />
pkgname=catalyst-KERNEL_NAME<br />
where KERNEL_NAME is whatever you want (e.g. custom, mm, themostawesomekernelever)<br />
<br />
2. Remove <code>kernel26</code> from the dependencies list.<br />
<br />
Finally, build and install the package. (<code>makepkg -i</code> or <code>makepkg</code> followed by <code>pacman -U pkgname.pkg.tar.gz</code>)<br />
<br />
==== Notes ====<br />
* If you run multiple kernels, then install catalyst module packages for all kernels. They won't conflict with one another.<br />
<br />
* No changes need to be made to the <code>catalyst-utils</code> package, which is completely kernel-independent. '''All''' you need to do is compile a kernel module.<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 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 don't have an xorg.conf file yet, run the following command to generate one:<br />
# Xorg -configure<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 />
== Troubleshooting (catalyst) ==<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 />
===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 and catalyst-utils. 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-utils</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 />
===Compaq Presario Laptops===<br />
Even after installing the drivers and editing the configuration file as required, some laptops (e.g. Presario R4000 with Xpress 200M) just come up with a blank screen.<br />
<br />
The problem seems to be incorrect memory detected by the kernel(even if you have 128M of video memory lspci -v always reports 256M). Changing the BIOS settings so that it uses the "SidePort+UMA" option and 128M video memory plus another 128M taken from the system seems to work fine.<br />
<br />
It could be a bug in the BIOS or in the Linux PCI code.<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 />
= External links =<br />
More info can be found here<br />
* [http://wiki.cchtml.com/index.php/Main_Page Unofficial ATI Wiki]<br />
* [http://ati.cchtml.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content= Unofficial ATI Linux Bugtracker]<br />
* [http://www.rage3d.com/board/forumdisplay.php?f=88 Rage3D ATI Linux Forums]<br />
* [http://www.thinkwiki.org/wiki/Problems_with_fglrx ThinkWiki fglrx Problems page]<br />
* [http://www.phoronix.com/scan.php?page=article&item=560 ATI R300: Open v. Closed Drivers] (''deprecated'' since April 2009)<br />
* [http://www.thinkwiki.org/wiki/Additional_options_for_the_radeon_driver Additional options for the radeon driver] (there are though deprecated options referenced there)<br />
* [http://www.phoronix.com/scan.php?page=article&item=936&num=1 Hidden ATI Feature For Textured XRendering]</div>Jgarayhttps://wiki.archlinux.org/index.php?title=User:Jgaray&diff=40461User:Jgaray2008-04-29T09:59:38Z<p>Jgaray: </p>
<hr />
<div>Not much yet, huh?<br />
<br />
Well, just to remember, my ''.bashrc'' prompt line:<br><br />
<br />
As regular user:<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)]\[\033[0;32m\]\h[\w]\\$\[\033[37m\]"<br />
</code><br />
<br />
As root:<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)]\[\033[0;31m\]\h[\w]\\$\[\033[37m\]"<br />
</code><br />
<br />
And don't forget to use gconf-editor :-)</div>Jgarayhttps://wiki.archlinux.org/index.php?title=User:Jgaray&diff=39816User:Jgaray2008-04-14T09:52:50Z<p>Jgaray: </p>
<hr />
<div>Not much yet, huh?<br />
<br />
Well, just to remember, my ''.bashrc'' prompt line:<br><br />
<br />
As regular user:<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;32m\][\w] \\$\[\033[37m\]"<br />
</code><br />
<br />
As root:<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;31m\][\w] \\$\[\033[37m\]"<br />
</code><br />
<br />
And don't forget to use gconf-editor :-)</div>Jgarayhttps://wiki.archlinux.org/index.php?title=User:Jgaray&diff=39815User:Jgaray2008-04-14T09:51:00Z<p>Jgaray: </p>
<hr />
<div>Not much yet, huh?<br />
<br />
Well, just to remember, my ''.bashrc'' prompt line:<br><br />
<br />
As regular user:<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;32m\][\w] \\$\[\033[37m\]"<br />
</code><br />
<br />
As root:<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;31m\][\w] \\$\[\033[37m\]"<br />
</code><br />
<br />
And don't forget to use gconf-editor :-)<br />
<br />
<br />
Example of .conkyrc file:<br />
<code><br />
# note that the $xmms2_* and $mpd_* stuff will only work if you have support for them built into conky<br />
<br />
# Create own window instead of using desktop (required in nautilus)<br />
own_window yes<br />
own_window_type normal<br />
own_window_transparent yes<br />
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager<br />
<br />
# Use double buffering (reduces flicker, may not work for everyone)<br />
double_buffer yes<br />
<br />
# Text stuff<br />
draw_outline no # amplifies text if yes<br />
draw_borders no<br />
# font arial<br />
uppercase no # set to yes if you want all text to be in uppercase<br />
<br />
# Stippled borders?<br />
stippled_borders 3<br />
<br />
# Default colors and also border colors, grey90 == #e5e5e5<br />
default_color green<br />
color0 darkgreen<br />
color1 green<br />
<br />
own_window_colour brown<br />
own_window_transparent yes<br />
<br />
# border margins<br />
border_margin 9<br />
<br />
# border width<br />
border_width 10<br />
<br />
# Text alignment, other possible values are commented<br />
#alignment top_left<br />
#alignment top_right<br />
#alignment bottom_left<br />
alignment bottom_right<br />
<br />
# Gap between borders of screen and text<br />
gap_x 10<br />
gap_y 70<br />
<br />
TEXT<br />
$nodename - $sysname $kernel on $machine<br />
$hr<br />
${color0}En funcionamiento:$color $uptime<br />
${color0}Frecuencia (en GHz):$color $freq_g<br />
${color0}RAM en uso:$color $mem/$memmax - $memperc% ${membar 4}<br />
${color0}Swap en uso:$color $swap/$swapmax - $swapperc% ${swapbar 4}<br />
${color0}CPU en uso:$color $cpu%<br />
${color1}${cpugraph}<br />
${color0}Procesos:$color $processes ${color0}En ejecucion:$color $running_processes${color0} Los 5 principales:<br />
${color0} Nombre PID CPU% MEM%<br />
$color1 ${top name 1} ${top pid 1} ${top cpu 1} ${top mem 1}<br />
$color1 ${top name 2} ${top pid 2} ${top cpu 2} ${top mem 2}<br />
$color1 ${top name 3} ${top pid 3} ${top cpu 3} ${top mem 3}<br />
$color1 ${top name 4} ${top pid 4} ${top cpu 4} ${top mem 4}<br />
$color1 ${top name 5} ${top pid 5} ${top cpu 5} ${top mem 5}<br />
${color0}${tail /var/log/Xorg.0.log 3}";<br />
$hr<br />
${color0}Sistemas de archivos: <br />
$color / ${color0}Total:$color ${fs_size /} ${color0}Libre:$color ${fs_free /} ${fs_bar 6,230 /}<br />
$color /home ${color0}Total:$color ${fs_size /home} ${color0}Libre:$color ${fs_free /home} ${fs_bar 6,62 /home}<br />
${color0}Red - Subida:$color ${upspeed eth0} k/s${color0} Red - Bajada:$color ${downspeed eth0} k/s<br />
${color1}${downspeedgraph eth0 32,220} ${color1}${upspeedgraph eth0 32,220}<br />
$hr<br />
${color0}MPD: $mpd_status $mpd_artist - $mpd_title from $mpd_album at $mpd_vol<br />
Bitrate: $mpd_bitrate\n" "Progreso: $mpd_bar<br />
${color0}XMMS2: $xmms2_status $xmms2_artist - $xmms2_title from $xmms2_album<br />
Progress: $xmms2_bar<br />
</code></div>Jgarayhttps://wiki.archlinux.org/index.php?title=User:Jgaray&diff=39814User:Jgaray2008-04-14T09:48:41Z<p>Jgaray: </p>
<hr />
<div>Not much yet, huh?<br />
<br />
Well, just to remember, my ''.bashrc'' prompt line:<br><br />
<br />
As regular user:<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;32m\][\w] \\$\[\033[37m\]"<br />
</code><br />
<br />
As root:<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;31m\][\w] \\$\[\033[37m\]"<br />
</code><br />
<br />
And don't forget to use gconf-editor :-)<br />
<br />
<br />
Example of .conkyrc file:<br />
<code><br />
# note that the $xmms2_* and $mpd_* stuff will only work if you have support for them built into conky<br />
<br />
# Create own window instead of using desktop (required in nautilus)<br />
own_window yes<br />
own_window_type normal<br />
own_window_transparent yes<br />
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager<br />
<br />
# Use double buffering (reduces flicker, may not work for everyone)<br />
double_buffer yes<br />
<br />
# Text stuff<br />
draw_outline no # amplifies text if yes<br />
draw_borders no<br />
# font arial<br />
uppercase no # set to yes if you want all text to be in uppercase<br />
<br />
# Stippled borders?<br />
stippled_borders 3<br />
<br />
# Default colors and also border colors, grey90 == #e5e5e5<br />
default_color green<br />
color0 darkgreen<br />
color1 green<br />
<br />
own_window_colour brown<br />
own_window_transparent yes<br />
<br />
# border margins<br />
border_margin 9<br />
<br />
# border width<br />
border_width 10<br />
<br />
# Text alignment, other possible values are commented<br />
#alignment top_left<br />
#alignment top_right<br />
#alignment bottom_left<br />
alignment bottom_right<br />
<br />
# Gap between borders of screen and text<br />
gap_x 10<br />
gap_y 70<br />
<br />
TEXT<br />
$nodename - $sysname $kernel on $machine<br />
$hr<br />
${color0}En funcionamiento:$color $uptime<br />
${color0}Frecuencia (en GHz):$color $freq_g<br />
${color0}RAM en uso:$color $mem/$memmax - $memperc% ${membar 4}<br />
${color0}Swap en uso:$color $swap/$swapmax - $swapperc% ${swapbar 4}<br />
${color0}CPU en uso:$color $cpu%<br />
${color1}${cpugraph}<br />
${color0}Procesos:$color $processes ${color0}En ejecucion:$color $running_processes${color0} Los 5 principales:<br />
${color0} Nombre PID CPU% MEM%<br />
$color1 ${top name 1} ${top pid 1} ${top cpu 1} ${top mem 1}<br />
$color1 ${top name 2} ${top pid 2} ${top cpu 2} ${top mem 2}<br />
$color1 ${top name 3} ${top pid 3} ${top cpu 3} ${top mem 3}<br />
$color1 ${top name 4} ${top pid 4} ${top cpu 4} ${top mem 4}<br />
$color1 ${top name 5} ${top pid 5} ${top cpu 5} ${top mem 5}<br />
${color0}${tail /var/log/Xorg.0.log 3}";<br />
$hr<br />
${color0}Sistemas de archivos: <br />
$color / ${color0}Total:$color ${fs_size /} ${color0}Libre:$color ${fs_free /} ${fs_bar 6,230 /}<br />
$color /home ${color0}Total:$color ${fs_size /home} ${color0}Libre:$color ${fs_free /home} ${fs_bar 6,62 /home}<br />
${color0}Red - Subida:$color ${upspeed eth0} k/s${color0} Red - Bajada:$color ${downspeed eth0} k/s<br />
${color1}${downspeedgraph eth0 32,220} ${color1}${upspeedgraph eth0 32,220}<br />
$hr<br />
${color0}MPD: $mpd_status $mpd_artist - $mpd_title from $mpd_album at $mpd_vol<br />
Bitrate: $mpd_bitrate\n" "Progreso: $mpd_bar<br />
${color0}XMMS2: $xmms2_status $xmms2_artist - $xmms2_title from $xmms2_album<br />
Progress: $xmms2_bar<br />
<code></div>Jgarayhttps://wiki.archlinux.org/index.php?title=Gnome_Menu_tweaking&diff=39648Gnome Menu tweaking2008-04-07T05:40:09Z<p>Jgaray: /* Group menus, System menus */</p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
==Speed Tweak==<br />
You can remove the delay in GNOME menus by running this command:<br />
<br />
echo "gtk-menu-popup-delay = 0" >> ~/.gtkrc-2.0<br />
<br />
Or just add "gtk-menu-popup-delay = 0" (without quotes) to .gtkrc-2.0<br />
<br />
==Menu Editing==<br />
Most Gnome users complain about the menu. Changing menu entries system-wide or for one or several users alone is poorly documented.<br />
<br />
===User menus===<br />
(Note: It was believed that this article was obsolete. gnome 2.14 has its own menu editor (half functional). Half-functional indeed, so using this manual method is still effective until the new gnome menu editor is fully functional.)<br />
<br />
As a user, you may add starters for applications to your desktop. Once you have created and tested one, start nautilus and type <code>applications:///</code> in the location bar. Take the menu group you want, and place your starter there. You now have a new entry in your Gnome menu.<br />
<br />
Or install Alacarte, which makes it easy to create, change and remove menu entries with a GUI. Do this with:<br />
<br />
pacman -S alacarte<br />
<br />
===Group menus, System menus===<br />
You find common gnome menu entries as 'appname.desktop' objects inside /usr/share/gnome/share/applications. <br />
* Edit one of them to fit your needs for a new application, then save it.<br />
* Save it as a menu entry for all users <br> In common, you will set this files permissions to 644 (root: rw group: r others: r), so all users can see it.<br />
* Save it as a menu entry for a group or user alone <br> You may also have different user permissions; for example, some menu entries should only be available for a group or for one user.<br />
<br />
Here is an example how a Scite menu entry definition file could look:<br />
<br />
<pre><br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Name=SciTE<br />
Comment=SciTE editor<br />
Type=Application<br />
Exec=/usr/bin/scite<br />
Icon=/usr/share/pixmaps/scite_48x48.png<br />
Terminal=false<br />
Categories=GNOME;Application;Development;<br />
StartupNotify=true<br />
</pre><br />
<br />
Hint: Folders in Gnome menu:<br />
<br />
When you create a folder in applications:/// and want to change the icon - Right click, and choose "edit launcher" then change icon. If you right click and choose "Properties" and change the icon the icon will not change in menu.<br />
<br />
==See also==<br />
* [[Gnome]]<br />
* [[Gnome Tips]]</div>Jgarayhttps://wiki.archlinux.org/index.php?title=How_to_make_wget_to_work_with_proxy_and_proxy_authentification&diff=34508How to make wget to work with proxy and proxy authentification2008-01-02T12:54:42Z<p>Jgaray: </p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:HOWTOs (English)]]<br />
You may want to run wget inside a network environment, where a proxy requests authentication. Or you may like to use pacman in such an environment. You can do so by activating using wget in /etc/pacman.conf. The following scenario is typical for Windows networks. Let the proxy have the IP <i>192.168.10.11</i> and listening on port <i>8080</i>. In this example, for authentication you have to submit the name of a Windows domain user account. The domain's name is <i>wonderwall</i>, the user account reads <i>JohnDoe</i>, and the password is <i>Go4It</i>. Let us further assume you want to fetch <i>arch-0.6.iso</i> from <i>prdownloads.sourceforge.net</i>.<br />
<br />
* Add the following lines to your environment:<br />
<pre><br />
export http_proxy="http://192.168.10.11:8080"<br />
export ftp_proxy="http://192.168.10.11:8080"<br />
</pre><br />
<br />
* Now, start wget with some enhanced options:<br />
<i><br />
--proxy-user="string"<br />
--proxy-passwd="string"<br />
</i><br />
<br />
<pre>wget --proxy-user "Wonderwall\JohnDoe" --proxy-passwd "Go4It" http://prdownloads.sourceforge.net/archlinux/arch-0.6.iso</pre><br />
<br />
* You can create an alias to save that configuration, although it may be a security risk to save a passwd inside it:<br />
<pre><br />
alias wget 'wget --proxy-user "Wonderwall\JohnDoe" --proxy-passwd="Go4It"'<br />
</pre><br />
<br />
* Alternatively, you may use the username/password in the http_proxy/ftp_proxy variables:<br />
<br />
<pre><br />
export http_proxy="http://wonderwall\\johndoe:Go4It@192.168.10.11:8080"<br />
export ftp_proxy="http://wonderwall\\johndoe:Go4It@192.168.10.11:8080"<br />
</pre></div>Jgarayhttps://wiki.archlinux.org/index.php?title=User:Jgaray&diff=34507User:Jgaray2008-01-02T12:46:36Z<p>Jgaray: </p>
<hr />
<div>Not much yet, huh?<br />
<br />
Well, just to remember, my ''.bashrc'' prompt line:<br><br />
<br />
As regular user:<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;32m\][\w] \\$\[\033[37m\]"<br />
</code><br />
<br />
As root:<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;31m\][\w] \\$\[\033[37m\]"<br />
</code><br />
<br />
And don't forget to use gconf-editor :-)</div>Jgarayhttps://wiki.archlinux.org/index.php?title=User:Jgaray&diff=34505User:Jgaray2008-01-02T12:45:58Z<p>Jgaray: </p>
<hr />
<div>Not much yet, huh?<br />
<br />
Well, just to remember, my ''.bashrc'' prompt line:<br><br />
<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;32m\][\w] \\$\[\033[37m\]"<br />
</code><br />
<br />
Como root:<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;31m\][\w] \\$\[\033[37m\]"<br />
</code><br />
<br />
And don't forget to use gconf-editor :-)</div>Jgarayhttps://wiki.archlinux.org/index.php?title=User:Jgaray&diff=22591User:Jgaray2007-04-05T08:41:14Z<p>Jgaray: </p>
<hr />
<div>Not much yet, huh?<br />
<br />
Well, just to remember, my ''.bashrc'' prompt line:<br><br />
<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;32m\][\w] \\$\[\033[37m\]"<br />
</code><br />
<br />
And don't forget to use gconf-editor :-)</div>Jgarayhttps://wiki.archlinux.org/index.php?title=Main_Page_(Espa%C3%B1ol)&diff=22529Main Page (Español)2007-04-03T12:06:53Z<p>Jgaray: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
{{Navigate_i18n_mainpages}}{{newpagelinksmain}}<br />
<br />
{{translateme}}<br />
<br />
== Wiki de ArchLinux ==<br />
Bienvenido al Wiki de [[ArchLinux]] . <br />
<br />
{{sn|Comenzando:<br />
* [[ArchLinux]]<br />
* [[Arch vs Others]]<br />
* [[FAQ]]<br />
* [[The Arch Way]]<br />
* [[ArchWiki Tutorial]]<br />
}}<br />
<br />
=== Noticias del Wiki ===<br />
Ocasionalmente algo es de interés periodístico, pero sólo para el wiki.<br />
En éstos casos, visita la página de [[Wiki News]] para ver la última información del Wiki.<br />
<br />
=== Obteniendo Ayuda ===<br />
<br />
¿Tienes problemas para configurar algo? ¿No sabes dónde mirar?<br />
<br />
Aunque estamos intentando archivar tantos temas como sea posible, estamos actualmente en curso de corregir la estructura del wiki, y muchos de los archivos se están moviendo.<br />
<br />
Échale una ojeada a la '''[[:Category:HowTos|lista obsoleta de categorías]]'''. Ésta sección aún contiene información valiosa que no ha sido movida a las nuevas secciones.<br />
<br />
Páginas que ya han sido movidas pueden ser '''[[:Category:Pages sorted by topic|seleccionadas en función del tema]]'''. Hay también nuevas secciones en la '''[[:Category:Pages sorted by type|lista de artículos por tipos]]''' (P. ej: HOWTO, Tutoriales, etc).<br />
<br />
'''TIP:''' El motor de búsqueda no parece trabajar como esperan los usuarios. Hasta que este asunto se resuelva, deberías usar la [[:Category:Pages sorted by type|lista de artículos por tipos]] y usar la función ''Buscar'' de tu navegador para buscar títulos que puedan interesarte. Si te sientes con suerte, aún puedes usar el motor de búsqueda de ArchWiki (Accesible a través del panel de la izquierda).<br />
<br />
=== Ayudando ===<br />
<br />
El equipo del Wiki busca voluntarios para ayudar a reestructurar y reorganizar el wiki. Si tienes algo de tiempo para hacer algunas modificaciones menores o mayores, echa un vistazo a las '''[[Priority Todo|tareas prioritarias pendientes]]''' y a la lista general de '''[[WikiTodo|tareas pendientes]]''' para ver cómo puedes ayudar. Estamos especialmente interesados en tener gente para re-categorizar las páginas que no están en inglés. Coordina tus actividades con [[ContactList|administradores y operadores]], y con los [[ArchWiki maintainers (English)|encargados de mantenimiento]].<br />
<br />
=== Creando tus propias páginas ===<br />
<br />
Es necesario crear una cuenta de usuario antes de comenzar a editar páginas. Cuando lo hayas hecho, puedes ejercitarte en el [[Sandbox|cajón de arena]] para familiarizarte con la sintaxis del ArchWiki. Tu página de usuario/a es otro buen sitio para practicar. Hay una lista de elementos sintácticos simples en la [[:Category:Help|Categoría de ayuda]]. También puedes encontrar este enlace en la barra de navegación. Además hay una [[:Category:ArchWiki Tools (English)|sección nueva]] con algunos archivos ''HOWTO'' y con varias normas (parte de la futura ''Guía de los escritores y editores del wiki'').<br />
<br />
=== Contactos ===<br />
<br />
Para cualquier pregunta o sugerencia ver la [[ContactList|lista de contactos]].<br />
<br />
{{navigatearchlinux|}}</div>Jgarayhttps://wiki.archlinux.org/index.php?title=The_Arch_Way&diff=22055The Arch Way2007-03-19T12:02:48Z<p>Jgaray: /* Comments */</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:General (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|The Arch Way}}<br />
{{i18n_entry|Polski|The Arch Way (Polski)}}<br />
{{i18n_entry|Русский|Путь_Arch}}<br />
{{i18n_links_end}}<br />
<br />
<br />
= Arch Principles & Philosophy =<br />
This page attempts to describe the principles and philosophy of [[ArchLinux|Arch Linux]]. There once was no written document about the Arch Way; most likely that will never happen again. In short, the Arch Way stands for "<b>freedom of choice, keep it simple, learning, and user-control</b>".<br />
<br />
== Principles ==<br />
I, Judd Vinet, started building Arch for two reasons:<br />
<br />
# I didn't find any other distributions that met my ideals. Some came very close to what I wanted but there were annoying quirks or needless complexity that seemed to hurt more than help;<br />
# For fun - to give a little something back to the free software community, from which I've taken so much.<br />
<br />
<br />
By its basic nature, Arch is:<br />
<br />
* Lightweight and simple. Note that doesn't mean it's for everyone....<br />
<br />
* NOT designed as a newbie distro; it's intended for more experienced users. The aim is to develop Arch into as nearly a perfect base as is humanly possible. A base doesn't include fancy tools and auto configuration mechanisms, but rather contains manual configuration tools and few functions, for the users to further develop and/or learn on their own.<br />
<br />
* A free gift, again, "...to give a little something back to the free software community, from which I've taken so much." When you receive a gift from someone, it's usually expected to give something in return. As such, users are welcome to contribute their ideas, tools and suggestions.<br />
<br />
* Aware there are two sides which contribute to Arch Linux: Developers and Users. Don't expect the two sides to merge, but to have a mutual relationship whereby anyone can pick up what they want to add to their machine; our GOALs are to:<br />
<br />
* NOT let configure tools / GUIs control the system, but that they be controlled by the user. There is nothing wrong with GUIs as long as they follow this principle.<br />
<br />
* NOT be controlled by or dependent on what tools offer. When developing or selecting a utility tool, it should be written in a hackable/readable programming language (KISS) to enable users to modify it if they so choose.<br />
<br />
* The core development of Arch Linux will NOT be providing any "newbie-friendly" GUIs/utilities at any time in the near future.<br />
<br />
* We humble developers will continue to provide Arch as a solid base for everyone and anyone. If you guys want to make it pretty, give 'er a rip. Free speech, free beer, and all that.<br />
<br />
== Philosophy ==<br />
<br />
The System of values by which Arch develops:<br />
<br />
* KISS (Keep It Simple, ...) is the basis of Arch development.<br />
<br />
* In Arch, 'simple' doesn't always mean what it does in other distros. It's our philosophy that the learning is more important than getting something easily done.<br />
<br />
* Relying on GUIs to build and use your system is just going to hurt a user in the end. At some point in time a user will need to know all that some GUIs hide.<br />
<br />
* If you try to hide the complexity of the system, you'll end up with a more complex system. Instead, try to make the system simpler and more logical from the inside.<br />
<br />
* Sooner or later, you'll have to find the information on the web and usenet (if man is not enough). Learning how and where to find it on the net should be the first thing a newbie has to learn.<br />
<br />
* Where some users say "...such and such distro isn't like so and so distro," Arch allows the user to make all the contributions they want as long as it doesn't go against the ideals of the design or philosophy.<br />
<br />
* Arch Linux is different from the others: at Arch, the user isn't the only concern. Minimizing development of new tools and docs while maximizing understanding of Linux' inner workings, while keeping a watchful eye always on the "KISS" aim and philosophy of Arch Linux in general...is what makes the "Arch Way" truly different.<br />
<br />
* The great thing about contributions is that you don't need anyone's permission to make them. (See?) No one can physically stop you from writing something that you (personally) find useful, even if the "powers that be" don't see it as a blessing. Write it and put it up in the User Contributions forum. If other people like it, you'll receive feedback. If virtually everyone out there hates it but you, you'll receive feedback, for sure - but who cares? It took you 20 minutes to write, and you learned something along the way. It's a winning situation no matter what.<br />
<br />
* It is what you make it.<br />
<br />
== Comments ==<br />
<br />
What users have said about Arch:<br />
<br />
* "After spending a lot of time with other distributions (debian, gentoo, mandrake, redhat, fedora, slackware) and even FreeBSD. I think that I finally found the distribution I was looking for."<br />
<br />
* Same thing with (k)ubuntu, Mandriva, and several others. Well, openSUSE is nice and easy (that's the one I would advice for my sister); but Arch is the One which really *rocks*.<br />
<br />
* "I have tried several distro's and even took (tired?) RHCE (took it BACK?), but there was always something I disliked about each."<br />
<br />
* "My dream distro was always the simplicity of Slackware with real dependency support like Debian's, and guess what - that's Arch."<br />
<br />
* "I also found Arch my final distro."<br />
<br />
* "After trying out almost all the available distributions, I have to agree that Arch is the best."<br />
<br />
* "Hi all. I just registered here so I could report all the problems I'm having, and ask for help. Funny thing is, I HAVE NO PROBLEMS!!! I really can't believe this, but everything is just working! I installed Arch today, had a little trouble with xorg and sound setup, but found all the answers I needed in the documentation and the forums!"<br />
<br />
* "I tried Mandrake, Yoper, FC3/4, Mepis and Ubuntu. I was looking for the perfect distro. I am glad that I found Arch."<br />
<br />
----<br />
<br />
= PROS and CONS =<br />
<br />
== PROS ==<br />
<br />
* i686-optimized<br />
* [[pacman]]: 'System Upgrade' is ONE command: "pacman -Suy"<br />
* [[pacman]]: Dependency-control, no X/GUI needed<br />
* [[ABS]]: the package-building function need only be done once - building another version of a package is extremely easy<br />
* [[ABS]]: you can build all the packages on your machine with one command<br />
* fully up-to-date packages at your request, and fully customizable<br />
* the people behind the scenes are gentle, motivated and able<br />
* less than 20 minutes to create a fully functional system<br />
* the perfect environment to learn Linux in<br />
* not really popular, because not known (still relevant?)<br />
<br />
== CONS ==<br />
<br />
* [[pacman]]: needs a fast internet connection to stay always up-to-date easily (less of a problem as time marches forward)<br />
* some conflicts from using the newest libs ("bleeding edge")<br />
* lack of newbie-friendly features<br />
* very little hardware detection (relevant?)<br />
* info files are almost always way more detailed than man-pages (gcc.info e.g.)<br />
* not really popular, because not known</div>Jgarayhttps://wiki.archlinux.org/index.php?title=User:Jgaray&diff=21901User:Jgaray2007-03-14T15:07:01Z<p>Jgaray: </p>
<hr />
<div>Not much yet, huh?<br />
<br />
Well, just to remember, my ''.bashrc'' prompt line:<br><br />
<br />
<code><br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;32m\][\w] \\$\[\033[37m\]"<br />
</code></div>Jgarayhttps://wiki.archlinux.org/index.php?title=User:Jgaray&diff=21900User:Jgaray2007-03-14T15:05:46Z<p>Jgaray: New page: Not much yet, huh? Well, just to remember, my Bash prompt: export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;32m\][\w] \\$\[\033[37m\]"</p>
<hr />
<div><br />
Not much yet, huh?<br />
<br />
Well, just to remember, my Bash prompt:<br />
export PS1="\[\033[0;36m\][\$(date +%H:%M)] \[\033[0;32m\][\w] \\$\[\033[37m\]"</div>Jgarayhttps://wiki.archlinux.org/index.php?title=General_purpose_mouse&diff=21899General purpose mouse2007-03-14T15:00:34Z<p>Jgaray: </p>
<hr />
<div>[[Category:Daemons and system services (English)]]<br />
[[Category:Input devices (English)]]<br />
[[Category:HOWTOs (English)]]<br />
====Q: How do I configure a mouse to be used in the console?====<br />
<b>A: </b>To use your mouse in the console, you need the '''pgm''' package. If it is not installed, get it with:<br />
<br />
<code>pacman -S gpm</code>.<br />
<br />
To use it, you can load gpm from the /etc/rc.conf file, adding it to the daemons line. Here is an example of this line, including gpm:<br />
<br />
<pre><br />
DAEMONS=(syslog-ng !hotplug !pcmcia network netfs openntpd crond cups gpm)<br />
</pre><br />
<br />
The gpm package needs to be started with a few parameters. These parameters can be added in the file ''/etc/conf.d/gpm''. Here is an example of the content of the file:<br />
<br />
<pre><br />
#<br />
# Parameters to be passed to gpm<br />
#<br />
GPM_ARGS="-m /dev/input/mice -t ps2"<br />
</pre><br />
<br />
The -m parameter precedes the declaration of the mouse to be used. The -t parameter precedes the type of mouse you are using (A PS2 mouse in this case). If you do not know what types are there to be chosen, load the package using a fake name (e.g. "helpme"). In this way you will get a list of available types.<br />
<br />
For more info see <code>man gpm</code>.</div>Jgarayhttps://wiki.archlinux.org/index.php?title=General_purpose_mouse&diff=21898General purpose mouse2007-03-14T14:58:40Z<p>Jgaray: Adding a category</p>
<hr />
<div>[[Category:Daemons and system services (English)]]<br />
====Q: How do I configure a mouse to be used in the console?====<br />
<b>A: </b>To use your mouse in the console, you need the '''pgm''' package. If it is not installed, get it with:<br />
<br />
<code>pacman -S gpm</code>.<br />
<br />
To use it, you can load gpm from the /etc/rc.conf file, adding it to the daemons line. Here is an example of this line, including gpm:<br />
<br />
<pre><br />
DAEMONS=(syslog-ng !hotplug !pcmcia network netfs openntpd crond cups gpm)<br />
</pre><br />
<br />
The gpm package needs to be started with a few parameters. These parameters can be added in the file ''/etc/conf.d/gpm''. Here is an example of the content of the file:<br />
<br />
<pre><br />
#<br />
# Parameters to be passed to gpm<br />
#<br />
GPM_ARGS="-m /dev/input/mice -t ps2"<br />
</pre><br />
<br />
The -m parameter precedes the declaration of the mouse to be used. The -t parameter precedes the type of mouse you are using (A PS2 mouse in this case). If you do not know what types are there to be chosen, load the package using a fake name (e.g. "helpme"). In this way you will get a list of available types.<br />
<br />
For more info see <code>man gpm</code>.</div>Jgarayhttps://wiki.archlinux.org/index.php?title=General_purpose_mouse&diff=21897General purpose mouse2007-03-14T14:53:12Z<p>Jgaray: Page created</p>
<hr />
<div>====Q: How do I configure a mouse to be used in the console?====<br />
<b>A: </b>To use your mouse in the console, you need the '''pgm''' package. If it is not installed, get it with:<br />
<br />
<code>pacman -S gpm</code>.<br />
<br />
To use it, you can load gpm from the /etc/rc.conf file, adding it to the daemons line. Here is an example of this line, including gpm:<br />
<br />
<pre><br />
DAEMONS=(syslog-ng !hotplug !pcmcia network netfs openntpd crond cups gpm)<br />
</pre><br />
<br />
The gpm package needs to be started with a few parameters. These parameters can be added in the file ''/etc/conf.d/gpm''. Here is an example of the content of the file:<br />
<br />
<pre><br />
#<br />
# Parameters to be passed to gpm<br />
#<br />
GPM_ARGS="-m /dev/input/mice -t ps2"<br />
</pre><br />
<br />
The -m parameter precedes the declaration of the mouse to be used. The -t parameter precedes the type of mouse you are using (A PS2 mouse in this case). If you do not know what types are there to be chosen, load the package using a fake name (e.g. "helpme"). In this way you will get a list of available types.<br />
<br />
For more info see <code>man gpm</code>.</div>Jgaray