|
Dimensione: 31317
Commento:
|
← Versione 95 del 14/03/2011 12.48.47 ⇥
Dimensione: 3385
Commento: converted to 1.6 markup
|
| Le cancellazioni sono segnalate in questo modo. | Le aggiunte sono segnalate in questo modo. |
| Linea 1: | Linea 1: |
| [[BR]] ||<tablestyle="font-size: 18px; text-align: center; width:100%; background:red; margin: 0 0 0 0;" style="padding:0.5em;">'''ATTENZIONE: Questa è una pagina di prove, le seguenti informazioni possono essere inesatte, si sconsiglia la visione'''|| [[BR]] [[BR]] |
## page was renamed from Saurus/Prove <<BR>> <<Indice>> <<BR>> |
| Linea 10: | Linea 7: |
| Le seguenti guide sono in formato "beta" ossia ancora in attesa di approvazione (e non è detto che siano approvate)! Il loro contenuto è utilizzabile a rischio e pericolo dell'utente e per questo non mi assumo responsabilità alcuna ;-)[[BR]] Saluti, ["Saurus"] | Le seguenti guide sono in formato "beta" ossia ancora in attesa di approvazione (e non è detto che siano approvate)! Il loro contenuto è utilizzabile a rischio e pericolo dell'utente e per questo non mi assumo responsabilità alcuna ;-)<<BR>> Saluti, [[Saurus]] |
| Linea 12: | Linea 9: |
| [[BR]] == DriverBinariHowtoATI == ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| |
<<BR>> = Guide candidate = |
| Linea 16: | Linea 12: |
| Di default Ubuntu usa i [:Hardware/Video/Ati/RadeonDriver:driver open source] per schede prodotte da ATI. Alcuni utenti preferiscono i driver proprietari 'fglrx' per svariate ragioni. Le istruzioni in questa pagina spiegheranno come usare questi driver. | == UUID == UUID "'''U'''niversally '''U'''nique '''Id'''entifier" è utilizzato nel settore del software, tradotto in lingua italiana non è altro che "Identificatore Unico Universale". Si tratta di un prodotto realizzato dall'Open Software Foundation (OSF) come parte del sistema DCE. Un UUID è essenzialmente un numero di 16-byte (128-bit). |
| Linea 18: | Linea 15: |
| Ci sono 2 modi per poter installare i driver proprietari fglrx. Il metodo preferito è usare i driver disponibili repository di Ubuntu. Altri utenti avanzati possono tuttavia provare ad usare i driver dal sito ati.com. Entrambi gli approcci sono documentati qui di seguito ma bisogna sceglierne '''soltanto uno''' da usare. L'installazione dei driver ospitati dai repository di Ubuntu è il metodo più sicuro, mentre l'installazione dei driver di ati.com può essere utile solo se si ritenga di averne bisogno qualora il computer vada per esempio in ibernazione. | Nella relativa forma esadecimale un UUID può assomigliare a questo: 0aa86c61-0df9-4f1a-8c0b-34abbee6b769 |
| Linea 20: | Linea 17: |
| Come accennato altrove, se incontrate bugs con questi driver closed-source, gli sviluppatori non potranno aiutare nella risoluzione dei problemi. L'uso dunque è a proprio rischio e pericolo. Si consiglia agli utenti di preferire i [:Hardware/Video/Ati/RadeonDriver:driver open source]. | Sebbene l'UUID non garantisca un'effettiva unicità, il numero possibile di combinazioni è talmente elevato da evitare una possibile coincidenza tra due codici. Il numero possibile di combinazione degli UUID è 2^128^ = 256^16^ = circa 3.4 x 10^38^. Ciò significa che 1 trilione di UUID devono essere generati ogni nanosecondo affinché tra 10 miliardi di anni si esaurisca il numero di UUID e tornare a rigenerare lo stesso UUID. |
| Linea 22: | Linea 19: |
| == Requisiti == Assicurarsi che i seguenti requisiti corrispondano alla scheda video: * E' una scheda 'Radeon' * Il modello della scheda è della serie 9xxx, 9500 o superiore, o è della serie X (Ad esempio X200), o ha la predisposizione TV-Out. I driver 'fglrx' non sono supportati da schede precedenti la serie 9500. * Il comando lspci rivela una scheda con la dicitura "ATI" nel suo nome * Si deve avere la necessità di abilitare l'accelerazione hardware 3D, o il refresh del display superiore ai 60 Hz. Altrimenti i driver open source sono buoni per tutte le altre operazioni. * Inoltre bisogna avere una certa conoscenza basilare di una linea di comando Linux. |
Diverse sono le sue applicazioni nel mondo digitale; più generalmente, l'UUID viene utilizzato per identificare in maniera univoca un determinato componente... |
| Linea 30: | Linea 21: |
| Nota che se la tua scheda ATI dalla serie R400 o inferiore, funziona il 2D e probabilmente anche il 3D con i driver di default. Queste schede includono: | == Ulteriori risorse == |
| Linea 32: | Linea 23: |
| * Serie R400 Xnnn (X800, X700, etc) (il 3D funziona) * Serie R300 (9300+) (il 3D funziona) * Serie R200 e R100 (9200) |
* [[http://en.wikipedia.org/wiki/UUID|UUID su wikipedia in lingua inglese]] |
| Linea 36: | Linea 25: |
| Per specifici chipsets e modelli, vedere [http://xorg.freedesktop.org/releases/X11R6.7.0/doc/radeon.4.html le Note di Rilascio di Xorg 7.0 in inglese]. | <<BR>> |
| Linea 38: | Linea 27: |
| L'uscita TV 'TV-Out' potrebbe non funzionare con i driver open source; se non si ha l'uscita TV o non lo si vuole usare, probabilmente non si ha bisogno di usare i driver 'fglrx'. == Installazione dai repository di Ubuntu (il più semplice) == === Istruzioni per Ubuntu 7.04 (Feisty Fawn) === '''Nota:''' Se si usa Kubuntu bisogna seguire le istruzioni per la versione 6.10 (Edgy)-- * Installare linux-restricted-modules e restricted-manager disponibili nei repository restricted: {{{sudo apt-get update sudo apt-get install linux-restricted-modules-generic restricted-manager}}} Open the restricted drivers manager included in 7.04 "System -> Administration -> Restricted Drivers Manager" and select "ATI accelerated graphics driver". This will hopefully enable fglrx in a painless way. If not, follow the instructions for Edgy. === Instructions for 6.10 (Edgy) === * Install the driver provided by ati included in the repositories: {{{sudo apt-get update sudo apt-get install xorg-driver-fglrx}}} * You might also want to install a control panel for your graphic card. Please note that I do not recommend it, as it seems to be buggy, and generally doesnt work. |
= Guide in prova e migliorabili = == UtenteRoot == Nei sistemi operativi di tipo Unix si indica con root l'utente dotato di massimi privilegi, ossia l'amministratore di sistema, detto anche super utente o superuser. <<BR>> L'account root su sistemi Unix è paragonabile a quello di administrator su sistemi Windows NT/XP/Vista. <<BR>> L'utente root può fare tutto ciò che si desidera sul sistema: questo che apparentemente sembra essere un vantaggio, in realtà in parte è uno svantaggio. È di fatto ritenuto pericoloso compiere le normali sessioni di lavoro come ad esmpio lanciare X in qualità di root. Infatti un qualsiasi programma lanciato in esecuzione da root ha potenzialmente la possibilità di effettuare qualunque operazione sulla macchina sulla quale viene eseguito. Se lo stesso programma viene lanciato in esecuzione da un utente con privilegi non amministrativi, non potrà effettuare operazioni pericolose come cancellare file essenziali per il sistema operativo. <<BR>> E' buona norma pertanto avere almeno due utenti sulla macchina di cui uno root ed un altro a scelta con privilegi non amministrativi e quest'ultimo sarà quello che verrà utilizzato per svolgere qualsiasi cosa col computer.<<BR>> Qualora occorresse eseguire programmi con privilegi di root, basta dare da shell |
| Linea 63: | Linea 32: |
| sudo apt-get install fglrx-control}}} * Make sure fglrx is not disabled: {{{gksudo gedit /etc/default/linux-restricted-modules-common}}}, or in Kubuntu {{{kdesu kate /etc/default/linux-restricted-modules-common}}}. * Generate a new set of module dependencies so the fglrx driver starts properly. |
sudo [applicazione] }}} ed inserire la password di root richiesta. Tuttavia quando è necessario avviare da terminale un'applicazione grafica usando i privilegi di root, bisogna usare il comando:<<BR>> per Gnome |
| Linea 70: | Linea 37: |
| sudo depmod -a}}} * You now have to configure xorg to use your graphic card. The aticonfig tool, provided with the driver, will do that for you: {{{sudo aticonfig --initial sudo aticonfig --overlay-type=Xv}}} * ATI are well known not to be able to provide correct drivers for their hardware so you will have to deactivate the composite extension in /etc/X11/xorg.conf , otherwise you will get a jerky video display: {{{gksudo gedit /etc/X11/xorg.conf}}} or if on Kubuntu: {{{kdesu kate /etc/X11/xorg.conf}}}, and add the following lines at the end of the file: |
gksudo [applicazione] }}} o per KDE: |
| Linea 80: | Linea 41: |
| Section "Extensions" Option "Composite" "disable" EndSection}}} // After making all those modifications, your X server might not want to start again. Don't worry, you can still modify xorg.conf using nano {{{sudo nano /etc/X11/xorg.conf}}}. To save changes press Ctrl-O and to quit press Ctrl-X. To start X again type startx // Save and restart xorg by pressing Ctrl Alt and Backspace simultaneously. Confirm it worked, by issuing the "fglrxinfo" command: * fglrxinfo/glxinfo may not work properly for you via SSH and via the console when logged in as root. {{{ $ fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON 9700 Generic OpenGL version string: 2.0.5755 (8.24.8) |
kdesu [applicazione] |
| Linea 97: | Linea 43: |
==== Troubleshooting ==== If fglrxinfo gives you the following, your installation is not completed correctly: {{{$ fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: Mesa project: www.mesa3d.org OpenGL renderer string: Mesa GLX Indirect OpenGL version string: 1.2 (1.5 Mesa 6.4.1)}}} These two commands might fix your installation, try this, reboot, and run fglrxinfo again: {{{sudo mkdir -p /usr/X11R6/lib/modules/dri sudo ln -s /usr/lib/dri/fglrx_dri.so /usr/X11R6/lib/modules/dri }}} [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian Source for the Mesa fix, with in-depth explanation] If the above fix did not work, watch for these things: * As fglrx is proprietary, just like many other proprietary software you might want to try to reboot your machine. * Make sure that the resctricted-modules package installed correspond to the kernel your are running and that you can load the fglrx driver, either by issuing the command "sudo modprobe fglrx" or by verifying that the module appears in the list of loaded modules, by issuing the command "lsmod"; * It may be necessary to establish a symbolic link for the /usr/lib/dri folder, by issuing the following command: "sudo ln -s /usr/lib/dri /usr/lib/xorg/modules/dri"; * You may have to unload the radeon and dri modules, by issuing "sudo rmmod radeon" and "sudo rmmod dri"; * Make sure you unload the module ati-agp by issuing "sudo rmmod ati-agp" and blacklist it in /etc/modprobe.d/blacklist. * Check the /etc/X11/xorg.conf in Section "Module" to have this line: Load "dri" and it is not commented. * Check the /var/log/Xorg.0.log file for errors. Firstly, search for (EE) (You can probably ignore any wacom entries). If you find the following then the Composite extension has been enabled (on my system it seems to be enabled by default, and must be explicitly disabled): {{{(II) fglrx(0): Composite extension enabled, disabling direct rendering (WW) fglrx(0): *********************************************** (WW) fglrx(0): * DRI initialization failed! * (WW) fglrx(0): * (maybe driver kernel module missing or bad) * (WW) fglrx(0): * 2D acceleraton available (MMIO) * (WW) fglrx(0): * no 3D acceleration available * (WW) fglrx(0): ********************************************* *}}} The ATI binary drivers do not support Composite. Ensure that the following entry is not in your xorg.conf: {{{Section "Extensions" Option "Composite" "true" EndSection}}} If there is no Composite entry, add one specifying "false" rather than true. This was necessary on my system. If you are looking for a specific video configuration please read the driver's manual. It will tell you all about dual-head configurations for example :) . {{{ man fglrx}}} If you suffer from a "white screen" overlayed onto gdm upon logout and the system seizing up, i.e., if you share the Ubuntu system with multiple users, then modify the file /etc/X11/gdm/gdm.conf and either add or change the AlwaysRestartServer option: {{{ AlwaysRestartServer=true}}} === Instructions for 6.06 (Dapper) === Install the kernel drivers. These drivers should be installed by default, but it's better to make sure they are installed. You need the package linux-{{{$arch}}}, where you replace {{{$arch}}} by the CPU architecture for the machine. This is 386 for Intel Pentium, 686 for Celeron, Pentium Pro, Pentium II, Pentium III, and Pentium 4 without Hyper-Threading. 686-smp for Pentium 4 with Hyper-Threading, or k7 or k7-smp for AMD athlon. On 64-bit systems, this may be amd64-generic, amd64-k8, amd64-k8-smp, or amd64-xeon. {{{ sudo apt-get install linux-686 or sudo apt-get install linux-k7 or ...}}} You also need to install the restricted-modules package that match ***exactly*** the kernel you are running, as well as specific required packages: (if you ran the previous command, make sure to reboot on your new kernel, otherwise this will install the wrong kernel modules !) {{{sudo apt-get update sudo apt-get install linux-restricted-modules-$(uname -r) sudo apt-get install xorg-driver-fglrx fglrx-control}}} Please note that the fglrx-control package is not compulsory as it seems to be buggy (but wont affect your machine in anyway :) ). If the restricted-modules package for the kernel you are running is not available (it happens sometimes with K/Ubuntu), you may have to opt for running a kernel for which this package is available or to install the drivers directly from the setup script provided by ATI (https://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&folderID=27) Once the above packages are correctly installed, run these commands: {{{sudo aticonfig --initial sudo aticonfig --overlay-type=Xv}}} Then go back and edit xorg.conf with your favorite editor, perhaps:{{{ gksudo gedit /etc/X11/xorg.conf}}} or:{{{ kdesu kate /etc/X11/xorg.conf}}} and make sure that under the "Device" section, the Driver is set to {{{ Driver "fglrx"}}} You will have 2 device sections related to your graphic card, one is the pre-aticonfig one, and should use the ati or radeon driver. No need to change this part as it is not used by xorg anymore. The other device section however will have to use the fglrx driver. It appears that fglrx is often unstable, at least on AMD64. System may lock on 8.25 driver. 3D accell may not work on 8.28. The 8.26.18 driver may be your best bet, as of Sept2006. Instructions for updating drivers are at: http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide#Method_2:_Generating.2FInstalling_Ubuntu_packages_for_the_8.28.8_drivers_in_Ubuntu_Dapper_Manually But I recommend 8.26 at this time, not 8.28. Reboot. Confirm it worked, by issuing the "fglrxinfo" command: * fglrxinfo/glxinfo may not work properly for you via SSH and via the console when logged in as root. {{{ $ fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON 9700 Generic OpenGL version string: 2.0.5755 (8.24.8) }}} Source: http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide ==== Troubleshooting ==== You may see a message {{{Xlib: extension "XFree86-DRI" missing on display ":1.0}}}. If the line {{{load "dri"}}} in {{{Section "Module"}}} is missing from your {{{/etc/X11/xorg.conf}}} then add it. However this message does not necessarily indicate a problem. If fglrxinfo gives you the following, your installation is not completed correctly: * fglrxinfo/glxinfo may not work properly for you via SSH and via the console when logged in as root. {{{$ fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: Mesa project: www.mesa3d.org OpenGL renderer string: Mesa GLX Indirect OpenGL version string: 1.2 (1.5 Mesa 6.4.1)}}} In this case, watch for these things: * Make sure that the resctricted-modules package installed correspond to the kernel your are running and that you can load the fglrx driver, wether by issuing the command "sudo modprobe fglrx" or by verifying that the module appears in the list of loaded modules, by issuing the command "lsmod"; * It may be necessary to establish a symbolic link for the /usr/lib/dri folder, by issuing the following command: "sudo ln -s /usr/lib/dri /usr/lib/xorg/modules/dri"; * You may have to deload the radeon and dri modules, by issuing "sudo rmmod radeon" and "sudo rmmod dri"; * Make sure you deload the module ati-agp by issuing "sudo rmmod ati-agp" and blacklist it in /etc/modprobe.d/blacklist. * Check the /etc/X11/xorg.conf in Section "Module" to have this line: Load "dri" and it is not commented. == Install from ati.com (latest version of drivers) == === Instructions for 7.04 (Feisty) === ==== Preparation ==== Although it is possible to use the instructions for 6.10 on 7.04, there is a simpler and possibly more painless way to install of 7.04. First, download the drivers installer (not the rpms) from [http://ati.amd.com/support/driver.html ati.amd.com]. It is recommended to save it to an empty directory since the installer will create a bunch of files. Next, in order to build the packages, we need some basic developer tools. To get these tools, first enable the universe and restricted sections of Ubuntu (see AddingRepositoriesHowto for help). Once the repositories are enabled, install the needed developer tools with {{{sudo apt-get install module-assistant build-essential debhelper debconf dh-make fakeroot libstdc++5 linux-headers-generic}}} ==== Installation ==== Build Ubuntu packages from the installer by opening a terminal, entering the directory that you saved the installer to, and running {{{bash ./ati-driver-installer-<version>.run --buildpkg Ubuntu/feisty}}} where <version> is the version number of the driver you downloaded. This will take a short time. After finishing, the installer will create several debs. Use the command "dpkg -i <filename>" to install the fglrx-kernel-source<something>.deb and the xorg-driver-fglrx<something>.deb. The other two debs created will be fglrx development headers which you probably will not need and the AMD Control Panel which doesn't work. After installing the kernel source and xorg driver, you will now need to compile the fglrx kernel module in order to get 3-d rendering. Do so with the following commands: {{{sudo m-a prepare,update sudo m-a build,install fglrx-kernel (or module-assistant -f to force a rebuild if needed) sudo depmod sudo rm -f /usr/src/fglrx-kernel*.deb }}} ==== Configuration ==== Ubuntu 7.04 ships with a utility to automate configuration of fglrx. Open it at "System -> Administration -> Restricted Drivers Manager" (you may have to install the restricted-manager and linux-restricted-modules-generic package). Select "ATI accelerated graphics driver" and hit apply. The Restricted Drivers Manager will then automagically change xorg.conf and several other files. However, even at this point, the setup is '''not''' finished. At next boot, Ubuntu will load an old version of fglrx, so you have to blacklist it by changing /etc/default/linux-restricted-modules-common to include DISABLED_MODULES="somemodule2 fglrx" where somemodule2 is the old contents of that line. When you have finished this last change, reboot and (hopefully) enjoy your 3-d acceleration. ==== After kernel updates ==== After every update of the kernel (linux-image-<arch>), you will need to recompile the kernel module (make sure to get the latest linux-headers too) as explained under the installation section. After you recompile the module, you can regain direct rendering by logging into a console (ctrl+alt+f1) and typing: {{{ sudo /etc/init.d/gdm stop (kdm if you use Kubuntu) sudo rmmod fglrx (even if this command fails, go on) sudo modprobe fglrx sudo /etc/init.d/gdm start (again, Kubuntu users type kdm) }}} === Instructions for 6.10 (Edgy) === '''Download what's needed:''' * Download the appropiate drivers from [http://ati.amd.com/support/driver.html ati.amd.com]. You will need the ATI Driver Installer, not the separate XFree86/X.org rpm packages. Save the installer into an empty directory (or at least one containing no *.deb files), since it will create some new files. * Make sure the universe section of the Ubuntu repositories is enabled (See the AddingRepositoriesHowto), and then run: {{{ sudo aptitude install module-assistant build-essential debhelper debconf dh-make fakeroot libstdc++5 linux-headers-$(uname -r) }}} '''Disable Composite Extension:''' In Ubuntu Edgy the Composite extension is enabled by default, however, fglrx does not yet support Composite with DRI. To disable Composite you must edit the /etc/X11/xorg.conf file, so add these lines at the end of xorg.conf: {{{ Section "Extensions" Option "Composite" "Disable" EndSection }}} '''Blacklist old fglrx module from linux-restricted-modules''' As ubuntu's linux-restricted-modules package includes the fglrx module from an old driver version (8.28.8), we have to blacklist this module to make sure the new kernel module which is needed by the new driver will be used instead. {{{ gksudo gedit /etc/default/linux-restricted-modules-common or, on Kubuntu, kdesu kate /etc/default/linux-restricted-modules-common We need to add fglrx (only! don't remove anything!) to this: DISABLED_MODULES="somemodule2 fglrx" }}} '''Next,''' * Perform the following commands (where ''<version>'' is the version number of the installer): {{{ sudo ln -sf bash /bin/sh bash ./ati-driver-installer-<version>.run --buildpkg Ubuntu/edgy sudo ln -sf dash /bin/sh You may need to wait a few mintues for this to complete. }}} This will create a number of .deb files in the current directory. '''next,''' {{{ sudo dpkg -i *.deb }}} next you build the kernel module - (also note, this has to be done every time you upgrade the kernel) {{{ sudo module-assistant prepare,update sudo module-assistant build,install fglrx-kernel (or module-assistant -f to force a rebuild if needed) sudo depmod sudo rm -f /usr/src/fglrx-kernel*.deb }}} now see '''Modifying xorg.conf'''. Skip the "lrm-manager" and "depmod" commands. After a reboot, confirm that it worked, by issuing the "fglrxinfo" command, as mentioned elsewhere on this page. Look at the troubleshooting sections to confirm if the output of the command is correct. === Instructions for 6.06 (Dapper) === 1. Download the apropiate drivers from [http://www.ati.com/support/driver.html ati.com]. You will need the ATI Driver Installer, not the seperate XFree86/X.org rpm packages. Save the installer into an empty directory (or at least one containing no *.deb files), since it will create several new files. 1. Make sure the universe section of the Ubuntu repositories is enabled (See the AddingRepositoriesHowto) 1. Perform the following commands (where ''<version>'' is the version number of the installer): {{{ $ sudo apt-get install fakeroot gcc-3.4 module-assistant build-essential debhelper $ fakeroot sh ./ati-driver-installer-<version>.run --buildpkg Ubuntu/edgy You may need to wait a few mintues for this to complete. }}} This will create a number of .deb files in the current directory. note: If you run Dapper, replace "edgy" (above) with "dapper". {{{ 1 sudo dpkg -i *.deb 2 sudo module-assistant prepare,update 3 sudo module-assistant build,install fglrx-kernel 4 sudo depmod note: You need to repeat steps 2-4 - building the kernel module - everytime you upgrade the kernel. }}} ==== Seveas Repository ==== You do not need to take all these steps if you run an up-to-date Dapper installation on a 32 bit system. Dennis Kaarsemaker provides these packages in a repository. Add the following line to /etc/apt/sources.list: {{{ deb http://mirror.ubuntulinux.nl/ dapper-seveas drivers }}} (There also is breezy-seveas for the Breezy users) Then you can simply install the ubuntu-fglrx-{{{$arch}}} (see above for the meaning of {{{$arch}}}) package. /!\ The fglrx driver on Dapper (8.26.18-1) can cause rss-glx screensavers to run very slowly. === Modifying xorg.conf === When you install from ati.com drivers or the dapper-seveas repository, you still need to change xorg.conf and add the fglrx module to /etc/modules as described under "Ubuntu provided drivers". There are scripts from ATI that may or may not work for you. They will backup xorg.conf before modifying it. {{{ $ sudo aticonfig --initial $ sudo aticonfig --overlay-type=Xv }}} /!\ Whether you install manually or from dapper-seveas, you MUST disable the Ubuntu-provided fglrx by performing these actions: * Disable fglrx in /etc/default/linux-restricted-modules-common * Run sudo /sbin/lrm-manager * Run sudo depmod -a * Reboot There is a [http://ubuntuforums.org/showthread.php?t=204910 forum thread] on installing ATI drivers from ati.com. Look there if you have trouble, and if your problem isn't already solved there, post a question. === Troubleshooting === * If you run Edgy, you might get something like ''./ati-installer.sh: 156: Syntax error: Bad substitution'' while trying to run the installer. This is because Edgy replaced the Shell ''sh'' with ''dash''. Here you can see my very brutal solution (take care!): {{{ $ sudo mv /bin/sh /bin/sh.old $ sudo ln -s /bin/bash /bin/sh $ fakeroot sh ./ati-driver-installer-<version>.run --buildpkg Ubuntu/edgy $ sudo rm /bin/sh $ sudo mv /bin/sh.old /bin/sh }}} * At the moment (Aug 14th, 2006), the installer can only build packages for dapper, not edgy. That's no problem, it'll still work. If the driver still doesn't run correctly, you might repeat the same steps like above, but with ''--extract'' instead of ''--buildpkg Ubuntu/dapper'': * With 8.30.3 (Nov 08th, 2006) ''--buildpkg Ubuntu/edgy'' worked. -- i cannot confirm that, i have 6.10 and it still doesn't work (error in line 999) {{{ $ sudo mv /bin/sh /bin/sh.old $ sudo ln -s /bin/bash /bin/sh $ fakeroot sh ./ati-driver-installer-<version>.run --extract $ sudo rm /bin/sh $ sudo mv /bin/sh.old /bin/sh }}} A new directory appears. Copy the X.org drivers where they belong to: {{{ $ sudo cp fglrx-install/x710/usr/X11R6/lib/modules/drivers/fglrx_drv.so /usr/lib/xorg/modules/drivers/fglrx_drv.so $ sudo cp fglrx-install/x710/usr/X11R6/lib/modules/linux/libfglrxdrm.so /usr/lib/xorg/modules/linux/libfglrxdrm.so }}} Ok, that's it. Time to clean up: {{{ $ rm -rf fglrx-install fglrx-installer_8.27.10-1_i386.changes }}} Good Luck! === More Troubleshooting === * If after everything you still get indirect rendering when typing "fglrxinfo" run: {{{ $ depmod -ae }}} Now reboot and hope for the best. * If you're using an AMD64 configuration and your Xorg.0.log mentions a 'duplicate symbol rol_long' message, comment out the 'Load "int10"' line in the Module section of /etc/X11/xorg.conf * If you are using an ATI Radeon Xpress 200M on an AMD64 CPU and the fglrx driver crashes with a blank screen on startup, change your BIOS settings to use the UMA+Sideport Video Mode with 128MB of Shared Video Memory. See http://ensode.net/ati_radeon_xpress_200m_linux.html * If you are going to compile 3d applications, you will want to install the `fglrx-driver-dev` package * The fglrx doesn't support 16 bit colour on some chip sets, if you have problems with X locking up on boot try setting this in your xorg.conf file to 24 * If you are having problems related to DRI or 3d acceleration and the following lines show up in your /var/log/Xorg.0.log {{{ (WW) fglrx(0): Kernel Module version does *not* match driver. (EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work}}} then make sure you installed either linux-{{{$arch}}} or ubuntu-fglrx-{{{$arch}}}. Another reason for either this error message, or incorrect driver information when running fglrxinfo (reports that the mesa driver is still being used) could be that the (K)Ubuntu fglrx drivers were not uninstalled before installing the ATI driver, or that the restricted-modules package is installed. To fix this issue, start Adept or Synaptic and remove the fglrx packages supplied with (K)Ubuntu as well as the restricted-modules package. Quit KDE and go to a console. {{{ $ sudo modprobe -r fglrx $ gksudo gedit /etc/X11R6/xorg.conf or $ kdesu kate /etc/X11R6/xorg.conf }}} Change the driver for the device to 'ati' instead of fglrx to use the standard Xorg supplied driver. {{{ $ startx }}} Now re-run the ATI driver installation * If there are no obvious error messages in {{{Xorg.0.log}}} but 3D acceleration is still not working, you should look at {{{glxinfo}}} output in debug mode: {{{ LIBGL_DEBUG=verbose glxinfo }}} Possibly there are some errors in the beginning concerning not found drivers in {{{/usr/X11R6/lib/modules/dri/}}}. This could be the case if you used the driver from ATI and are now using again the provided fglrx driver. ATI's fglrx driver installs a script in {{{/etc/X11/Xsession.d/10fglrx}}} which changes the search path for libraries, causing 3D-related errors. In this case just remove the script: {{{ $ sudo rm /etc/X11/Xsession.d/10fglrx }}} * Sometimes 2D acceleration with xv is not enabled. You need this for smooth video playback among other things. In this case you should check if your {{{/etc/X11/xorg.conf}}} contains the line {{{Option "VideoOverlay" "on"}}} in the corresponding section: {{{ Section "Device" Identifier "ATI Radeon" Driver "fglrx" Option "VideoOverlay" "on" BusID "PCI:1:0:0" EndSection }}} * You might want to install the fglrx-control package, which provides a control panel to configure graphics card options such as dual-head display (two monitors) and TV out. * Some people might experience random hangups. I heard that this ''might'' help: Edit {{{/etc/X11/xorg.conf}}} and add the following options in the corresponding section: {{{ Section "Device" Identifier "ATI Technologies, Inc. ATI Default Card" Driver "fglrx" Option "no_accel" "no" Option "no_dri" "no" Option "DynamicClocks" "on" Option "mtrr" "on" Option "DesktopSetup" "Single" Option "ScreenOverlap" "0" Option "Capabilities" "0x00000000" Option "CapabilitiesEx" "0x00000000" Option "VideoOverlay" "on" Option "OpenGLOverlay" "off" Option "CenterMode" "off" Option "PseudoColorVisuals" "off" Option "Stereo" "off" Option "StereoSyncEnable" "1" Option "FSAAEnable" "no" Option "FSAAScale" "1" Option "FSAADisableGamma" "no" Option "FSAACustomizeMSPos" "no" Option "FSAAMSPosX0" "0.000000" Option "FSAAMSPosY0" "0.000000" Option "FSAAMSPosX1" "0.000000" Option "FSAAMSPosY1" "0.000000" Option "FSAAMSPosX2" "0.000000" Option "FSAAMSPosY2" "0.000000" Option "FSAAMSPosX3" "0.000000" Option "FSAAMSPosY3" "0.000000" Option "FSAAMSPosX4" "0.000000" Option "FSAAMSPosY4" "0.000000" Option "FSAAMSPosX5" "0.000000" Option "FSAAMSPosY5" "0.000000" Option "UseFastTLS" "0" Option "BlockSignalsOnLock" "on" Option "UseInternalAGPGART" "no" Option "ForceGenericCPU" "no" Option "KernelModuleParm" "agplock=0" Option "PowerState" "1" BusID "PCI:1:0:0" EndSection}}} * On laptops, in /etc/default/acpi-support, consider setting {{{ ENABLE_LAPTOP_MODE=true }}} The comments in that file mention that this setting can cause mysterious hangs, but battery life is considerably improved. If you don't mind tinkering, you can get an ACPI capable laptop boot in lower power mode, as described here: ["BinaryDriverHowto/Fglrx lowpower"] Note: {{{fglrx: version magic '2.6.17-10-generic SMP mod_unload 586 REGPARM gcc-3.3' should be '2.6.17-10-generic SMP mod_unload 586 REGPARM gcc-4.1'}}} - if you get errors similar to this (check via {{{dmesg|grep -i fglr}}}) and maybe if {{{modprobe fglrx}}} returns {{{"FATAL: Error running install command for fglrx"}}} then this means you did not compile the fglrx kernel module using the correct GCC version. In this example, gcc3.3 was used, while gcc4.1 is required. To fix: {{{ sudo aptitude install gcc-4.1 sudo ln -s /usr/bin/gcc-4.1 /usr/bin/gcc Now you should rebuild the fglrx kernel module. For example: sudo module-assistant -f build,install fglrx-kernel }}} If you need to remove the fglrx source code before rebuilding for some reason, you can try: {{{ sudo apt-get remove fglrx-kernel-source fglrx-kernel fglrx-kernel-$(uname -r) }}} you'll then need to again get the fglrx deb files (from the ATI installer) before you can build again. after all this, reboot. * Check the AGP aperture size. {{{ $ dmesg | grep aperture [ 30.1234] agppart: AGP aperture is 512M @ 0x0000000 or [ 30.1234] agppart: AGP aperture is 4M @ 0x0000000 }}} I have a Asus K8S-MX and a Radeon R350 (Radeon 9800 pro). I just had 4M. There is a know bug in the sis760 driver. I found some information here: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/34144 {{{the AGP aperture is only 4M this is never going to be big enough for the radeon driver you should check your BIOS to see if you can increase it.. that or the sis driver is getting the wrong size somehow..}}} a link to https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/45942 gives this 'solution' {{{I just renamed 'sis-agp.ko' to 'sis-agp.ko.bak' and everything worked.}}} I did the same and now I have xgl and beryl running. == Other links == *[http://support.ati.com/ics/survey/survey.asp?deptID=894&surveyID=508&type=web ATI's Driver Feedback Program] - (are you happy with their drivers? Maybe you'd prefer them to open-source their drivers so maintaining and installing would be easier for everyone...) *[:RadeonDriver: The ATI Radeon open-source driver HowTo @ubuntu] |
È sconsigliato usare sudo per avviare un'applicazione grafica, in quanto sudo non imposterà le variabili d'ambiente correttamente, in modo particolare in KDE. |
| Linea 552: | Linea 46: |
| [:Saurus:Saurus] | [[Saurus]] ---- CategoryHomepage |
Wiki di prova di Saurus
Le seguenti guide sono in formato "beta" ossia ancora in attesa di approvazione (e non è detto che siano approvate)! Il loro contenuto è utilizzabile a rischio e pericolo dell'utente e per questo non mi assumo responsabilità alcuna ;-)
Saluti, Saurus
Guide candidate
UUID
UUID "Universally Unique Identifier" è utilizzato nel settore del software, tradotto in lingua italiana non è altro che "Identificatore Unico Universale". Si tratta di un prodotto realizzato dall'Open Software Foundation (OSF) come parte del sistema DCE. Un UUID è essenzialmente un numero di 16-byte (128-bit).
Nella relativa forma esadecimale un UUID può assomigliare a questo: 0aa86c61-0df9-4f1a-8c0b-34abbee6b769
Sebbene l'UUID non garantisca un'effettiva unicità, il numero possibile di combinazioni è talmente elevato da evitare una possibile coincidenza tra due codici. Il numero possibile di combinazione degli UUID è 2128 = 25616 = circa 3.4 x 1038. Ciò significa che 1 trilione di UUID devono essere generati ogni nanosecondo affinché tra 10 miliardi di anni si esaurisca il numero di UUID e tornare a rigenerare lo stesso UUID.
Diverse sono le sue applicazioni nel mondo digitale; più generalmente, l'UUID viene utilizzato per identificare in maniera univoca un determinato componente...
Ulteriori risorse
Guide in prova e migliorabili
UtenteRoot
Nei sistemi operativi di tipo Unix si indica con root l'utente dotato di massimi privilegi, ossia l'amministratore di sistema, detto anche super utente o superuser.
L'account root su sistemi Unix è paragonabile a quello di administrator su sistemi Windows NT/XP/Vista.
L'utente root può fare tutto ciò che si desidera sul sistema: questo che apparentemente sembra essere un vantaggio, in realtà in parte è uno svantaggio. È di fatto ritenuto pericoloso compiere le normali sessioni di lavoro come ad esmpio lanciare X in qualità di root. Infatti un qualsiasi programma lanciato in esecuzione da root ha potenzialmente la possibilità di effettuare qualunque operazione sulla macchina sulla quale viene eseguito. Se lo stesso programma viene lanciato in esecuzione da un utente con privilegi non amministrativi, non potrà effettuare operazioni pericolose come cancellare file essenziali per il sistema operativo.
E' buona norma pertanto avere almeno due utenti sulla macchina di cui uno root ed un altro a scelta con privilegi non amministrativi e quest'ultimo sarà quello che verrà utilizzato per svolgere qualsiasi cosa col computer.
Qualora occorresse eseguire programmi con privilegi di root, basta dare da shell
sudo [applicazione]
ed inserire la password di root richiesta. Tuttavia quando è necessario avviare da terminale un'applicazione grafica usando i privilegi di root, bisogna usare il comando:
per Gnome
gksudo [applicazione]
o per KDE:
kdesu [applicazione]
È sconsigliato usare sudo per avviare un'applicazione grafica, in quanto sudo non imposterà le variabili d'ambiente correttamente, in modo particolare in KDE.
