You are here

Fedora 5

Media (DVD, mp3, etc) playback in Fedora

The Fedora project believes in free software, and seeing as such patent-encumbered or proprietary formats are not included in the Fedora distributions. Unfortunately, that means that that media such as DVDs, MP3s, many types of video, Java content and .swf Flash content cannot be viewed on a fresh install of Fedora. This guide will show you how to install various plugins and codecs to allow the playback of this type of content.

Need more help or want to ask a question? Discuss this topic here.

Requirements

 

All at Once!

To install all the codecs, applications and plugins mentioned in this howto at once, run:

yum -y remove totem totem-plparser;yum -y install totem-xine totem-xine-plparser rhythmbox \
libdvdcss libdvdread libdvdplay livdvdnav lsdvd libdvbpsi mplayerplug-in mplayer mplayer-gui \
xine-lib-extras-nonfree xine-lib-extras libdvdcss libdvdread libdvdplay compat-libstdc++-33

Remember that removing totem may remove additional applications - If you'd like them back, make sure you add them to the 'yum install' command.

DVD Playback

yum -y install libdvdcss libdvdread libdvdplay libdvdnav lsdvd libdvbpsi

Note that libdvdcss and the other libraries listed here may be illegal to distribute, install or use depending on your local copyright laws. Distribute/install/use at your own risk, I'm not responsible for anything that happens as a result.

Totem-Xine

Totem-Xine is a movie player that is based on Xine and not GStreamer. While the interface is exactly the same as Fedora's Totem player, using the Xine backend will allow for playback of media such as DVD, WMV, MPEG video and more.

yum -y remove totem totem-plparser;yum -y install totem-xine totem-xine-plparser rhythmbox \
xine-lib-extras-nonfree xine-lib-extras
Remember that removing totem may remove additional applications - If you'd like them back, make sure you add them to the 'yum install' command.

MPlayer and MPlayerPlug-In

MPlayer is also a movie player like Totem, although I find interface of MPlayer harder to use compared to totem-xine and additionally there is no support for DVD menus at the moment. Still, mplayer offers a web plugin for Mozilla/Firefox and packs in tons of codecs making it a valuable package.

yum -y install mplayer mplayer-gui mplayerplug-in

 

GStreamer plugins

Seeing as Fedora uses the GStreamer engine for many programs, it's a must to install the extra GStreamer plugin packs. This is the package that will allow for MP3 playback on your Fedora system.

yum -y install gstreamer gstreamer-plugins-good gstreamer-plugins-bad gstreamer-plugins-ugly

 

Macromedia Adobe Flash Player

rpm -Uhv http://linuxdownload.adobe.com/adobe-release/adobe-release-i386-1.0-1.noarch.rpm
yum -y install flash-plugin

Java (JRE) and JRE web plugin

Please see this howto for instructions.

 

RealPlayer

Please click 'Download RPM Package' on this page, then save that file in your home. Open a terminal (Applications > Accessories or System Tools > Terminal) and type:

rpm -Uhv RealPlayer10GOLD.rpm && rm RealPlayer10GOLD.rpm -f

RealPlayer and the Mozilla plugin should now be installed.

 
Need more help or want to ask a question? Discuss this topic here.
Blog Tags: 
Rating: 

Installing 3rd party repositories for Yum

There are many third party RPM repositores available for Fedora and/or RedHat based repos such as Livna, FreshRPMs, Dries (RPMForge) and Dribble. Soon many of these will merge into one repo called RPMFusion, but until then this guide will show you how to install these third party repos without giving you headaches.

Before we start...

Q: What in the world is a repository?
A:
A repository (often called a 'repo') in terms of Yum (Yellow dog Updater, Modified) is a location which Yum can use to download packages from. Fedora offers Core and Extras as the official repositories, however many third-party repos are available that allow for the installation of various codecs such as mp3/dvd/wmv playback or for packages that are not allowed to be packaged in the Core and Extras due to legal reasons.

 

Q: I can't install anything! I'm getting transaction errors like this:

error: can't create transaction lock on /var/lib/rpm/__db.000

 A: This is because to install packages, you have to become the root user which is the only user which should have access to your package database. To do so, run this command before you start any of the commands below:

su -

(That's su followed by a space and a dash)
You'll only need to execute this command once before anything mentioned below, as you will stay as root until you close the terminal or type the exit command.

 

Livna

Livna is my personal favourite repo because it's fast, compatible with Fedora (Extras) and contains almost everything you'll need to get started: 

Dribble

The beauty of the Dribble repo is that one command will work for all Fedora versions. Make sure you have Livna installed and run:

rpm -ivh http://dribble.org.uk/repo/dribble-release-5-3.noarch.rpm

 

FreshRPMs

To install FreshRPMs, run:

wget http://ftp.freshrpms.net/pub/freshrpms/fedora/linux/5/freshrpms-release/\
freshrpms-release-1.1-1.fc.noarch.rpm

rpm -ihv freshrpms-release-1.1-1.fc.noarch.rpm
rm -f freshrpms-release-1.1-1.fc.noarch.rpm
exit

 

RPMForge (Dries)

Currently there is no release RPM for Dries (RPMForge) and as a result it must be manually configured. Below is a generic configuration that should work, however if it doesn't work properly, please see the Dries configuration page for more information. Place a the following contents into the /etc/yum.repos.d/rpmforge.repo file:

# Name: RPMforge RPM Repository for Fedora Core $releasever - $basearch
# URL: http://rpmforge.net/
[rpmforge]
name = Fedora Core 5 - i386 - RPMForge - Dries
baseurl = http://apt.sw.be/dries/fedora/fc$releasever/$basearch/dries/RPMS
enabled = 1
#gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dries
gpgcheck = 0

Common Questions

Concerning repos and Fedora development

If you are using rawhide (aka Fedora Development), follow the instructions like normal and if a specific version is required as in the case of Livna, use the latest version possible. To enable the development repo, look in the /etc/yum.repos.d folder and you should find name.repo file and a name-devel.repo file. Edit the name.repo file and change:

enabled=1 

to:

enabled=0

Now, in the name-devel.repo file, change:

enabled=0

 to:

enabled=1

This will disable the regular repository and enable the development repository so that the packages are compatible with the Fedora's development repository(ies).

 

 A note of warning

Please remember that until RpmFusion is completed, repositories such as FreshRPMs and ATRPMs have packages that conflict with packages from Livna and/or Fedora Core|Extras. If you would like to avoid these conflicts, it is recommended that you set the incompatible repos to the disabled state. Just as shown above, simply edit the respective .repo file and change

enabled=1

to

enabled=0 

Refer to the table below to find the location of the various .repo files:

Name of repository
Location of .repo file
FreshRPMs /etc/yum.repos.d/freshrpms.repo
ATrpms /etc/yum.repos.d/atrpms.repo
RPMForge (Dries) /etc/yum.repos.d/rpmforge.repo 
Dribble /etc/yum.repos.d/dribble.repo
Livna  /etc/yum.repos.d/livna.repo

 

 

 

 

 

 

Q: I would like to use a repo, but you recommended I disable it - What's the point!?
A:
Even if a repository is disabled, this does not mean Yum cannot use it - You can temporairily enable a repository by using the --enablerepo=name option with Yum or in Yumex by selecting the repositories for the run. For example:

yum --enablerepo=freshrpms install package_from_freshrpms

Will temporarily enable freshrpms and install package_from_freshrpms. Once yum has finished it's work, the FreshRPMs repo returns to it's normal disabled state.

 

Blog Tags: 
Rating: 

Getting nVidia cards to work in Fedora

Ensuring that your graphic card works the way you want it to in Linux can be a long and tenious task if you are encountering problems. This guide will show you how to setup the nv, nouveau or proprietary nvidia driver with your nVidia graphics card to make sure your card is functioning as it should.

Getting nVidia cards to work

Need more help or want to ask a question? Discuss this topic here.
 

Requirements

The 'nv' or 'nouveau' driver

The nv and nouveau drivers are the open-source alternatives to the proprietary nvidia driver, offering support for many of the nVidia cards. The downside to the nv driver is that unlike the open source 'radeon' driver for ATI cards, it does not support direct rendering, also called DRI or hardware-accelerated rendering. The nouveau project, however, aims to fix this by developing a new free driver with working DRI for nVidia cards. Currently, it is (as the name goes ;) ) a new project and it's not ready for everyday use quite yet.
 
Either way, both of these drivers are included in part of the standard Xorg driver packages in Fedora, so they requires almost no configuration at all! Simply edit the /etc/X11/xorg.conf file and in the "Device" section you will come across a line like this:
Driver "DriverNameHere"

 Change this line to:

Driver "Name"

Where 'Name' is either 'nv' (recommended) or 'nouveau' if you're feeling lucky. Once you restart the computer everything should be functioning (or maybe not if you chose the 'nouveau' driver)

 

The 'nvidia' driver

A note on legacy drivers:

Please note that any card below the GeForce FX series is no longer supported by the mainstream nvidia drivers.

If you have a Riva or TNT card, you are going to have to use the nvidia legacy drivers. Simply follow the instructions below like normal but replace all instances of:

  • kmod-nvidia with kmod-nvidia-legacy
  • xorg-x11-drv-nvidia with xorg-x11-drv-nvidia-legacy
  • xorg-x11-drv-nvidia-libs-32bit with xorg-x11-drv-nvidia-legacy-libs-32bit
  • service nvidia [action] with service nvidia-legacy [action]

A full product support list for legacy is available here.

If you are using a GeForce2, 3 or 4 (including MX) card, a you are going to have to use the 96xx series nvidia drivers as your card is not designated as legacy but is no longer supported by the 97xx series drivers.
Simply follow the instructions like normal but replace:

  • kmod-nvidia with kmod-nvidia-96xx
  • xorg-x11-drv-nvidia with xorg-x11-drv-nvidia-96xx
  • xorg-x11-drv-nvidia-libs-32bit with xorg-x11-drv-nvidia-96xx-libs-32bit
  • service nvidia [action] with service nvidia-96xx [action]

A full product support list for the 96xx series driver is available here.

 
To install the nvidia driver, simply run the following commands:
su -
yum install kmod-nvidia xorg-x11-drv-nvidia
nvidia-config-display enable
service nvidia restart

Please note that for a xen kernel, 'kmod-nvidia-xen' will need to be installed. This rule is applied to all the kernel variants, such as PAE (kmod-nvidia-PAE) and so on. 

Additionally, if you are running a x86_64 (a 64-bit) operating system the 32bit libraries can be installed for compatibility reasons:

yum install -y xorg-x11-drv-nvidia-libs-32bit

Common Questions

Q: How can I test if the driver works now that it's installed?

A: Simply run 'glxgears' like this:

glxgears 

Alternatively you can also check the output of 'glxinfo':

glxinfo | grep direct -i
glxinfo | grep OpenGL -i
It should return "direct rendering: yes" and also various OpenGL information concerning "NVIDIA Corporation" along with your card name and version - NOT "Mesa Indirect".
 
Q: Help! I followed the instructions and DRI still isn't working!
A: If you're using the drivers from the nVidia website or if you've previously installed them, please see this post on the RedHat mailinglists as to why it could be a problem. In short, those drivers tend to overwrite other system files which can cause problems, where as the packaged drivers from Livna or other third party repositories do not. If you think this is your problem, pease reinstall all Mesa GL and Xorg server packages to restore the replaced system files.
Q: What if it still doesn't work?
A: If you are not using the Livna drivers, then your xorg.conf may not be automatically edited for you. You may need to add this option to your /etc/X11/xorg.conf under the "Device" section:
Option      "AddARGBGLXVisuals" "True"
Option "DisableGLXRootClipping" "True"
 
Need more help or want to ask a question? Discuss this topic here.
Blog Tags: 
Rating: 

Desktop Effects - AIGLX, Xgl & Compiz, Beryl

Compiz and Beryl are advanced window managers that add some very amazing 3D visual effects to your desktop. This guide will provide you with step-by-step information on how to install these window managers along with setting up AIGLX and Xgl and also how to choose which one is right for you.

Desktop Effects - AIGLX, Xgl & Compiz, Beryl

Need more help or want to ask a question? Discuss this topic here.
 

Requirements

  • Yum configured to use the 3rd party Livna repository
  • A working graphics card (with direct rendering enabled). If you need help with this, please see the howtos for nVidia or ATI respectively
    Note: When using Xgl programs will always detect DRI to be disabled, even if it is functioning correctly. A test which can be performed to determine if it is really working is to run glxgears. If the animation is smooth, then DRI is working correctly even though it is not reported as so.
  • If using an nVidia card, please ensure your driver version is 1.0-9625 or greater.
  • livna-config-disply:
    su -
    yum install livna-config-display
    yum update livna-config-display
    exit

AIGLX

AIGLX - Prep

To ensure AIGLX is configured correctly, run:

livna-config-display

Select 'AIGLX' as the current configuration and apply it.

AIGLX - Compiz

su -c "yum install compiz"
gconftool-2 -s '/apps/metacity/general/compositing_manager' --type bool true
desktop-effects 

AIGLX - Beryl

su -c "yum install beryl-gnome beryl-kde"
beryl-manager
beryl-settings
 

Xgl

Xgl - Prep

To use Xgl, first the binaries must be installed as they are not (yet) included in the Fedora project. Please download the following packages from daMaestro's Xgl Files into your home directory:

Note: 32bit packages are hosted here; For other builds, please use the src (source) rpms to rebuild packages for your distribution.
Once you have downloaded the RPMs, run the following to install them:
su -c 'rpm -Uhv Xgl-settings*noarch*.rpm xorg-x11-server-Xgl*.rpm'

 Now that Xgl is installed, your desktop manager must be configured to use it too. livna-config-display can automatically configure GDM and KDM; for other managers you will have to find how to do this step on your own.

livna-config-display

Select 'Xgl' as the current configuration and apply it.

Xgl - Compiz

su -c "yum install compiz"
gconftool-2 -s '/apps/metacity/general/compositing_manager' --type bool true
desktop-effects

Xgl - Beryl

su -c "yum install beryl-gnome beryl-kde"
beryl-manager
beryl-settings

Common Questions

Q: What's the "Desktop Effects" people keep talking about?
A: I've used "Desktop Effects" in the title of this thread because the 3D effects are commonly called this, although technically Desktop Effects is just the name of the program used to start Compiz, one of many window managers. The window manager, such as Beryl or Compiz are what really provide the 3D effects.

Q: What's the difference between Compiz and Beryl? I've heard one is better than the other.
A: Compiz and Beryl are both new, advanced window managers so in that sense they are identical. Window managers control how window decorations (such as the minimize, maximize and close buttons on the title bar) and also how the windows are displayed - This is why they offer so many neat effects. Compiz and Beryl both use OpenGL (a free implementation of 3D) calls to create zoom, "wobbly", fade and transparency effects for example. The difference lies in the fact that Beryl is a community-maintained fork of Compiz, so naturally it has many more options, plugins and effects but consequently it is also less stable at the moment.
Note: Beryl and Compiz will merge into one big project soon.
Q: So then how do AIGLX and Xgl differ? 
A: First, let's define the X server: it is basically what programs use to display themselves on your screen. To use all these neat and fancy 3D calls, a new layer has to be introduced into the traditional X server for things to work properly.
Note: This is just my understanding... The X server is very complex and I could be (and probably am) incorrect at some point or other of this explanation, so this isn't necessarily all fact just more or less the "big picture".
AIGLX is an extension of the Xorg server, so essentially the change to AIGLX will be transparent to the user. It adds on to the existing Xorg code to add support for the fancy 3D calls. Xgl on the other hand is a complete rewrite of the X server to add support for the fancy 3D calls. While the Xorg and Xgl project share lots of code, in my opinion replacing the X server isn't the best option for two reasons: (1) AIGLX is a more incremental change then all-out replacing the X server and (2) replacing the X server means you're going to be affected by Xgl-related bugs that users of AIGLX won't. You can't be affected by what you don't run, right? This is why I think if it's possible, lean towards using AIGLX. However that's just my opinion and the final decision remains up to you.
 
Need more help or want to ask a question? Discuss this topic here.
Blog Tags: 
Rating: 

Getting ATI cards to work in Fedora

Ensuring that your graphic card works the way you want it to in Linux can be a long and tenious task if you are encountering problems. This guide will show you how to setup the radeon or the proprietary fglrx driver with your ATI graphics card to make sure your card is functioning as it should.

Getting ATI cards to work

Need more help or want to ask a question? Discuss this topic here.
 

Requirements

  • Yum configured to use the 3rd party Livna repository
  • If building the drivers using the packages directly from ATI/AMD's site, please install a few packages first:
    su -c 'yum install qt-devel compat-libstdc++-33 -y' 

 

The 'radeon' driver

Radeon is an open-source alternative to the proprietary fglrx driver, offering support for many (but not all) ATI cards including some that aren't supported any longer in the latest fglrx drivers! While it's performance may not match exactly that of fglrx, its performance is still very decent. It is included in part of the standard Xorg driver packages in Fedora, so it requires almost no configuration at all! Simply edit the /etc/X11/xorg.conf file and in the "Device" section you will come across a line like this:
Driver "DriverNameHere"

 Change this line to:

Driver "radeon"

Once you restart the computer everything should be functioning.

Please remember that if you previously were using another driver, you may need to use the livna-config-display tool to switch back to the 'AIGLX' configuration:

livna-config-display --tui -a

 

The 'fglrx' driver

To install the fglrx driver, simply run the following commands:
su -
yum install kmod-fglrx xorg-x11-drv-fglrx
fglrx-config-display enable
service fglrx restart

Please note that for a xen kernel, 'kmod-fglrx-xen' will need to be installed. This rule is applied to all the kernel variants, such as PAE (kmod-fglrx-PAE) and so on. 

Additionally, if you are running a x86_64 (a 64-bit) operating system the 32bit libraries can be installed for compatibility reasons:

yum install -y xorg-x11-drv-fglrx-libs-32bit  

Common Questions

Q: How can I test if the driver works now that it's installed?

A: Simply run 'glxgears' like this:

glxgears 

Alternatively you can also check the output of 'glxinfo':

glxinfo | grep direct -i
glxinfo | grep OpenGL -i
It should return "direct rendering: yes" and also various OpenGL information concerning "ATI Technologies" and not "Mesa".
 
Q: Help! I followed the instructions and DRI still isn't working!
A: If you're using the drivers from the ATI/AMD website or if you've previously installed them, please see this post on the RedHat mailinglists as to why it could be a problem. In short, those drivers tend to overwrite other system files which can cause problems, where as the packaged drivers from Livna or other third party repositories do not. If you think this is your problem, pease reinstall all Mesa GL and Xorg server packages to restore the replaced system files.
Q: What if it still doesn't work?
A: If you are not using the Livna drivers, then your xorg.conf may not be automatically edited for you. You may need to add this option to your /etc/X11/xorg.conf under the "Device" section:
Option "VideoOverlay" "On"
 
Need more help or want to ask a question? Discuss this topic here.
Blog Tags: 
Rating: 
Subscribe to RSS - Fedora 5