Home Home > 2011 > 02 > 19
Sign up | Login

Deprecation notice: openSUSE Lizards user blog platform is deprecated, and will remain read only for the time being. Learn more...

Archive for February 19th, 2011

ATI/AMD fglrx 8.821 Catalyst 11.2 available for openSUSE 11.2, 11.3, 11.4

February 19th, 2011 by

Updated : April 4th 2011

Preambule : free software

Warning

I would notice everybody which will install these software : you will install proprietary softwares on your computer. Nobody will be able to debug them, nor help you to resolve what can be happen. That must be said !

The free future

The real future is already in place : it’s called radeon (or free-radeon), it’s fully integrated in kernel & xorg. Actually ( for openSUSE 11.4, or openSUSE 11.3 with kernel-stable + X11 obs repo ). Support for many chipset is in real progress even for the 6xxx series.
Give it a try before using the proprietary software, report any bugs you find with it. Only your contributions can help and will make a real differences. Thanks for doing that !

Unofficial but working repository

I offer for those of you that for any reasons can’t use successfully the free-radeon drivers a repository where you will find the latest fglrx/catalyst drivers following the packaging policy made avalaible by AMD.
Thanks to Sebastian Siebert ( check his blog ) to work in coordination with ati/amd and follow the catalyst packaging. His work allow us to have that driver available for openSUSE.

The quick how-to

Adding the repository

For openSUSE Factory
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_Factory/ "ATI/AMD FGLRX"
For openSUSE 11.4
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.4/ "ATI/AMD FGLRX"
For openSUSE 11.3
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.3/ "ATI/AMD FGLRX"
For openSUSE 11.2
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.2/ "ATI/AMD FGLRX"

Installing the driver

Nota previous version

Due to change in ati/amd way of life, it’s recommanded to completely remove any version of fglrx previously installed with a zypper rm

I can only recommand to also (as root)

# Remove old conf & stuff
rm -fr /etc/ati
# Remove any old fglrx inside kernel modules
find /lib/modules -type f -iname "fglrx.ko" -exec rm -fv {} \;
New installation

Once the repo has been added, you will certainly have to reboot to get ride off free radeon module. At boot on the grub line add
nomodeset blacklist=radeon 3
Don’t panic you will be land to a console, open it with root account to install fglrx.
Search the software you want for example under openSUSE 11.4

zypper se -s fglrx
Loading repository data...
Reading installed packages...

S | Name                  | Type    | Version | Arch   | Repository
--+-----------------------+---------+---------+--------+-----------
i | fglrx64_xpic_SUSE114  | package | 8.831-1 | x86_64 | ATI/AMD fglrx non-official  
  | fglrx64_xpic_SUSE114  | package | 8.821-1 | x86_64 | ATI/AMD fglrx non-official  
  | fglrx_xpic_SUSE114    | package | 8.831-1 | i586   | ATI/AMD fglrx non-official
  | fglrx_xpic_SUSE114    | package | 8.821-1 | i586   | ATI/AMD fglrx non-official

Starting with 8.821 (Catalyst 11.2) ATI use now xpic (full explanation)
So use that one. I’ve removed all non xpic drivers the 2 April 2011.

For a 64bits version
zypper in fglrx64_xpic_SUSE114
For a 32bits version
zypper in fglrx_xpic_SUSE114

During the installation process, all the dependencies will be added, which mostly are needed to build the kernel modules. Expect around 200MB to dowload.

Then the installer will build the module for your installed kernel.
And if there’s a kernel update, the script will automagically detect that, and will rebuild the module for the new kernel installed. (So if you find that your workstation is slow on reboot just press the esc key to see the details … )

Preparing xorg to use fglrx

Once the module is build and installed, you should have a file fglrx.conf or 50-fglrx.conf in /etc/modprobe.d

cat /etc/modprobe.d/50-fglrx.conf
blacklist radeon

Next ati recommend to use ati –initial-config but that break the auto-detect stack of xorg. So I recommend changing one line in file /etc/X11/xorg.conf.d/50-device.conf
just change driver line to driver “fglrx”
All the rest of the setup (double screen etc) will be made lately with the ati catalyst control center (command is amdcccle).
For those of you which want to have an xorg.conf file just have a look at aticonfig –help command.

Start X

If you are inside the console we start to use before just run “init 5” to start xorg, and normally you will find your normal xorg login screen (kdm, gdm, ldm, xdm).
Hit ctrl+alt+f1 to return to the console and type exit or logout or ctrl+d to close it.
then ctrl+alt+f7 to return to the xorg session.

Updates

ati/amd catalyst are release on a month basis, but this vary from 3 weeks to 8 weeks.

  • Catalyst 11.2 – fglx 8.821 : 14 February 2011

References

Sebastian Siebert blog ( German ) with nice howto and problem resolution.
My previous post on the subject

Indicators for GNOME2 – Update

February 19th, 2011 by

Canonical has been very active and released quite an impressive amount of bug fixes and features for their Ayatana Project software. I’ve been doing the updates, sent a couple of tiny patches upstream (mainly packaging issues) and with the RC1, I am very happy with the results accomplished.

Regarding this project, I’ve seen news, blog posts and lots of feedback from several distribution users. I’ve found contents in German, Portuguese (Brazilian Portuguese), English, Russian and Spanish. For the most I believe everyone is happy this is happening.

During the next week, I’m going to conduct an open-beta for the GNOME2 indicators from which I hope to get some feedback and improve things so that once openSUSE 11.4 is release, those users willing to use this software can do it safely, and off course in an openSUSE way, a rock solid and featured GNOME experience.

I’ve created a pattern which will duplicated in the GNOME:Ayatana repository named ‘gnome2-indicators’ which will install the 5 base indicators on Ubuntu Natty. About this indicators and some previous comments that I’ve seen online, I would like to clarify a couple of things:

* All the software is built on top of ‘openSUSE stack’, so we’re not really converting Ubuntu to RPM’s.
* The patch level applied from Ubuntu is minimum, only the mandatory feature patches were applied on pure openSUSE stack. Some of this features weren’t upstreamed, while others were turned down, so GNOME:Ayatana will also provide the modified software required, this is the case of GTK+ (2.0) which is properly tested and no issues were found against the regular GTK+ stack on 11.4.
* I’ve patched and built applications like Metacity, Empathy and gnome-session to enable functionality with the Indicators. I’m also serving this patched versions through GNOME:Ayatana, without them, there wouldn’t really be a pleasant indicator experience for openSUSE users. I would love to see community contributions to GNOME:Ayatana for all of those that aren’t available yet. Don’t be shy, we don’t bite! (A big plus is that you can actually learn a lot, and the openSUSE GNOME Team is very friendly and helpful. If you really want to help and improve yourself, step forward!.

Now for real… what does the GNOME2 Indicator pattern offers?

1. A 99% working Session Indicator, from where users can perform several session related tasks (ex: logout, restart, switch users, hibernate, etc). The only feature I know it’s not present is the “restart/relog” option after software updates. If anyone want to work this indicator to work with PackageKit / YaST or zypper, would be probably a big plus and significative contribution to openSUSE and upstream.

2. The ME Menu, which appears to be fully functional.

3. A simple clock indicator. This indicator is under very active development, and displays a simple calendar/clock with options to manage appointments (through Evolution). The ‘date/time’ configurations are disabled because on openSUSE we use YaST for it. Except for this, everything seems to be working.

4. Sound Menu indicator… the (in)famous Sound indicator from Ubuntu, which displays an horizontal slide bar for sound volume management and fully integrates with Banshee. Since I’m recent convert to Banshee from Totem because of the development of this project, I’ve also packaged and made available from GNOME:Ayatana two extensions:
* banshee-extension-soundmenu – Enables integration with soundmenu, really a plus/must if Banshee is your preferred multimedia player;
* banshee-extension-indicator – A Banshee indicator. I’ve only really packaged this because it offers integration with Notify OSD, the indicator itself is less featured than the traditional gnome extension.

5. The Messaging Menu – Another controversial indicator… Currently it’s working with Empathy (patched with libindicate on GNOME:Ayatana), xchat, evolution and gwibber. Other applications like pidgin are known to work up to a certain point. This indicator grabs any incoming messaging and alerts the user for it. It’s not really that bad once you get used to it (takes a couple of hours).

Additionally to  this, Notify OSD is also available for openSUSE 11.4, and doesn’t require any extra repository. openSUSE 11.4 ships with a version of Notify OSD that allows the user to skin/theme it in several ways. This behavior isn’t enabled on Ubuntu and relies on a patched refused by upstream by Roman Sokuchev. The development project for this package is GNOME:Apps, and my thanks to Vincent Untz and Dominique L. for helping with the process.

During next week, GNOME:Ayatana will be populated and a free open BETA will be start to gather feedback amongst our users.

A side note… Yesterday an update for Sound Menu was issued by Canonical and it deeply relies on libnotify >= 0.7.0. openSUSE 11.4 will ship with libnotify 0.6.0 and therefore I’m not committing more changes to Sound Menu and will only fix critical issues if found for this package.

After openSUSE 11.4 is released, I’ll start working on implementing this for GNOME3, and hopefully now I will have enough time to try to push them to Factory for openSUSE 12 (or whatever it will be called).

Contributions are accepted in any area not covered by me, or fixing  stuff, and also very important, in the KDE field. About Unity… here’s a riddle: “How can you tell if a ghost is about to faint?”.

nmarques.