1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

New Approach To ATI Linux Driver Installation

Michael Larabel

Published on 25 January 2008
Written by Michael Larabel
Page 1 of 2 - 10 Comments

Back in June of 2005 with the ATI Linux 8.14.13 driver release was a new installer to more easily facilitate the installation of this binary graphics driver using a graphical interface for a generic setup or generating distribution-specific packages (at that time Red Hat was the only officially supported distribution). With time, this installer has evolved by gaining new features and more distributions are being supported through their --buildpkg command for generating custom driver packages. These packaging scripts are now even hosted in the open for more community interaction. With two new driver options that will be formally introduced next month in Ubuntu's packaging scripts for the Catalyst 8.02 Linux driver, the installation process of the ATI fglrx driver on Ubuntu will become several steps easier.

Starting next month with the Ubuntu packaging scripts for the ATI Linux driver, the --autopkg and --installpkg arguments will be supported. When using this new --autopkg argument, the Ubuntu packaging scripts will detect the distribution version, install any build-time dependencies for that distribution, builds the ATI Debian packages (the same as running --buildpkg manually), installs DKMS (Dynamic Kernel Module Support) and libGL package dependencies, and then finally installs the ATI driver packages. The distribution version is detected using lsb_release, the Linux Standard Base package. Using synaptic/apt-get, the auto-packaging scripts will then install any needed dependencies automatically without any end-user intervention. Having the installer automatically use the distribution's packaging system to satisfy any dependencies is great to see, cuts down on manually having to install these packages, and is certainly friendly to new Linux users. The build dependency resolution is done by parsing the Debian control file in each of the supported Ubuntu releases.

The --installpkg argument is used for just installing the generated ATI packages (and DKMS, if needed) and is the same as the last step in the --autopkg process. This option would be used if you had already ran --buildpkg to generate the Debian packages.

The --autopkg and --installpkg additions were created by Mario Limonciello with the Ubuntu packaging scripts. As of yet, no other Linux distribution has yet to adopt these changes in their packaging scripts. However, with time it will hopefully become standard among the maintainers and perhaps the --autopkg argument becoming standard to the ATI installer.

The reason for sharing this information now as opposed to in tandem with the Catalyst 8.02 release is that these new Ubuntu packaging scripts are already available to the public. As has been the case since last November, the ATI fglrx packaging scripts are housed in the open at Phorogit (Phoronix-Phorogit announcement). These scripts are backwards-compatible with the current ATI 8.01 Linux driver.

If you would like to try out --installpkg or --autopkg right now, on the next page we have a guide for using Phorogit with Catalyst 8.01.

<< Previous Page
1
Latest Linux Hardware Reviews
  1. CompuLab Intense-PC2: An Excellent, Fanless, Mini PC Powered By Intel's i7 Haswell
  2. From The Atom 330 To Haswell ULT: Intel Linux Performance Benchmarks
  3. AMD Radeon R9 285 Tonga Performance On Linux
  4. Apotop Wi-Copy
Latest Linux Articles
  1. AMD Moves Forward With Unified Linux Driver Strategy, New Kernel Driver
  2. MSI: Update Your BIOS From The Linux Desktop
  3. NVIDIA vs. AMD 2D Linux Drivers: Catalyst Is Getting Quite Good At 2D
  4. 15-Way GPU Comparison With Mesa 10.3 + Linux 3.17
Latest Linux News
  1. Phoronix Test Suite 5.4 M3 Is Another Hearty Update
  2. GParted 0.20 Improves Btrfs Support
  3. EXT4 In Linux 3.18 Has Clean-ups, Bug Fixes
  4. Emacs 24.4 Has Built-In Web Browser, Improved Multi-Monitor Support
  5. NVIDIA's NVPTX Support For GCC Is Close To Being Merged
  6. KDE's KWin On Wayland Begins Using Libinput
  7. Khronos Releases OpenVX 1.0 Specification
  8. Linux Kernel Working Towards GNU11/C11 Compatibility
  9. Ubuntu 15.04 Is Codenamed After A Monkey: Vivid Vervet
  10. Following GCC, Clang Looks To Default To C11
Latest Forum Discussions
  1. HOPE: The Ease Of Python With The Speed Of C++
  2. Updated and Optimized Ubuntu Free Graphics Drivers
  3. Users/Developers Threatening Fork Of Debian GNU/Linux
  4. Bye bye BSD, Hello Linux: A Sys Admin's Story
  5. NVIDIA Presents Its Driver Plans To Support Mir/Wayland & KMS On Linux
  6. AMD Is Restructuring Again, Losing 7% Of Employees
  7. Open-Source AMD Fusion E-350 Support Takes A Dive
  8. Upgrade to Kaveri, very slow VDPAU performance