Home Home > 2013 > 12
Sign up | Login

Archive for December, 2013

Proprietary AMD/ATI fglrx 13.251-1 Catalyst 13.12 rpm finally released

December 21st, 2013 by

Proprietary AMD/ATI Catalyst fglrx 13.12 (13.251-1) rpm released

Geeko Santa Claus - Crédits Carlos Ribeiro

Geeko Santa Claus – Crédits Carlos Ribeiro

Patience is a virtue, months of it and finally we got a proof that Santa Claus exist 🙂
This release allow me to wish you a Merry Christmas!

Notice

This release concern only owners of radeon HD5xxx or above.
For older gpu, the fglrx-legacy is still 13.1, and thus didn’t work with openSUSE 12.3 or above.
SDB:AMD_fgrlx_legacy
Beware of that, and prefer the free open-source radeon driver which came out of the box from your openSUSE distribution.
For 12.3 and especially 13.1 the free radeon often offer a better experience than the old fglrx-legacy.

Changing the signer of package

I’ve done a change with which key used for signing the package and repository. So you will need to trust the new key for the repository

zypper ref -f -r amd-fglrx
Forcing raw metadata refresh
Retrieving repository 'amd-fglrx' metadata ---------------------------------------------------------------------------------------------------------------------------------------------[\]

New repository or package signing key received:
Key ID: 484F703065BE584C
Key Name: builder Ioda-Net (Building and signing packages build at Ioda-Net) 
Key Fingerprint: 80D079EBFB1AB0FEE3CA41E6484F703065BE584C
Key Created: lun 30 jui 2012 15:27:35 CEST
Key Expires: sam 29 jui 2017 15:27:35 CEST
Repository: amd-fglrx

Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a

fglrx-13.12-capture01

Help for spreading the word

Dear fellow I’m counting on you to spread the word, in the different social media you’re subscribed, and also on Mailing list, forums.
Feel free also to translate it into your native language

Release note about 13.12

This Catalyst fglrx version support openSUSE version from 11.4 to 13.1 and also Tumbleweed (thus also kernel 3.12/13 series).
A special thanks to Sebastian Siebert for his effort on making this driver working under openSUSE.

If a kind German geeko can take the time to translate his article, put the result in comments below, you will understand that getting it working,
is not just Fun.

Notice for users of the -beta repository

If you previously used the fglrx drivers using the -beta created for fglrx 13.11, you could not switch back the url of the repository to the standard one.
The beta will contain now outdated driver until AMD release a new one.
If you were using the normal repository the update should appear directly

To change the url if your repository is called FGLRX
zypper mr -n FLGRX http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_13.1

Tumbleweed

For tumbleweed due to the change of openSUSE version from 12.3 to 13.1, you will certainly have remove the old package and install the new one.

zypper rm fglrx64_xpic_SUSE123

zypper in fglrx64_xpic_SUSE131
[snipped par of installation]
Calling 'depmod -a 3.12.5-3.g48b587a-desktop' this may take a while...

Summary report:
================================================================================

   Kernel     => 3.12.5-3.g48b587a-desktop
   Detected   => RPM package
   Build      => [ OK ]
   Install    => [ OK ]

*************************************************************
Please read "/usr/share/doc/packages/fglrx/README.SuSE" for
configuration details when using SaX2.
*************************************************************
...

Release Note

A release note is available on AMD website

Fixed issues

    [384861]: Ultra slow dota2 fps
    [383176]: System hang when startx after enable Eyefinity
    [383109]: System hang when run Unigine Heaven 4.0
    [382494]: Screen corruption when run C4Engine with GL_ARB_texture_array enabled
    [384193]: Fix the procfs permission issue on kernel 3.10 and later
    [373812]: System hang when run some OpenGL stress test
    [383430]: Glxtest failed with force AA
    [383372]: Fail to launch cairo-dock
    [384509]: glClientWaitSync is waiting even when timeout is 0
    [383573]: AC/DC switching is broken
    [384194]: Tear-Free Desktop sets V-Sync to 30Hz instead of 60Hz
    [385123]: CrossFire aspect observed in CCCLE where it should not
    [385414]: Steam crashes and games hang on a black screen when Force AA is on
    [387027]: Glxtest failed on SLED11 SP3
    [382079]: MARI crash with weird stack
    [387797]: X crash when kill X with Xserver 1.13 and 1.14
    [389431]: Screens are distorted when connecting an external monitor on some PowerXpress platform with Intel Haswell
    [389728]: Segfault after disabling display on re-launch of CCCLE
    [387573]: Soft hang and error observed on BasicDebug sample for OpenCL when run on x86
    [385704]: Black window when run glxgears with TWM
    [376115]: Display corruption when using rotation

 Known Bugs
	

(more…)

Owners of FGLRX card using openSUSE 12.1 – cleanup your repositories

December 21st, 2013 by

Important
If you’re still using openSUSE 12.1 and you have one day installed the AMD/ATI FGLRX long time ago, you certainly forget to adjust the new location of the repository.

My server indicate that still around 154 Geekos have their FGLRX repository pointing to the old urls :
http://geeko.ioda.net/mirror/ati/openSUSE_12.1/

The location changed long time ago, when AMD decide to split the drivers in two part (legacy HD2xxx-HD4xxx and normal HD5xxx or above).
The worst things, is that those are trying to refresh almost every half hour, generating 404 errors on my server, without help them to get the right driver.

I’ve made a call at that time to help to spread the information. Would be nice, if any of you could spread this reminder to your fellows.
Cause I can decide by a redirection, which gpu you have 🙂

The new location for 12.1 was setup as following :
For HD2xxx-HD4xxxx legacy :http://geeko.ioda.net/mirror/amd-fglrx-legacy/openSUSE_12.1/

For HD5xxx or above : http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_12.1/

Enter UnReal World RPG

December 19th, 2013 by

When I was kid Commodore 64 was big thing and I played ‘Gateway to Apshai‘ hour after hour. It really hit me. Others liked Ultimas but ‘Gateway to Apshai’ was THE thing to me. Years after C64 was gone with the wind I found world of Rogue, Omega and Nethack. Sweetest of them was Omega. Omega’s World map was big and you could do what ever you like and wander around and you didn’t have to fight all the time. As this was a long, long time ago none of those games are no more in active development but Sami Maaranen is still developing unique northern hemisphere survival game called UnReal World RPG.
UnReal World RPG 3.18beta3 start screenUnReal World RPG 3.18beta3
See bigger pictures at IndieDB
(more…)

Announcing openSUSE Education Li-f-e 13.1

December 17th, 2013 by

Get Li-f-e from here : Direct Download | Torrents | Metalinks | md5sum

openSUSE Education community is proud to bring you an early Christmas and New Year’s present: openSUSE Education Li-f-e. It is based on the recently released openSUSE 13.1 with all the official online updates applied.

We have put together a nice set of tools for everyone including teachers, students, parents and IT administrators.  It covers quite a lot of territory: from chemistry, mathematics to astronomy and Geography. Whether you are into software development or just someone looking for Linux distribution that comes with everything working out of the box, your search ends here.

Edit: We now also have x86_64 version supporting UEFI boot available for download.

(more…)

Waouh, Thank you, Merci, Danke, etc

December 16th, 2013 by

Thanks you!
I really & sincerely thank all of our members who not only took the risk of being recognized as active members, but also cast their vote to myself.

Thank you, Merci, Danke etc..

Thank you, Merci, Danke etc..

I’m deeply touched, now the time of let’s begin the fun has come.
Be assured to my strong commitment in our project and community.

See you on earth!

Continuing Opening YaST

December 16th, 2013 by

YaST switched to the GPL license back in 2004, but there were still a lot of obstacles to easy contributions to the project. There was a bunch of changes in the past to improve contribution to the project, like switching from the openSUSE subversion server to GitHub, generating documentation to doc.opensuse.org or having public IRC. But we are not satisfied and do even more steps to make it easy to contribute to YaST.

The most visible action in the last year was the conversion from YCP to Ruby. We found that having a special language just for YaST made some sense in the past, but now becomes useless and makes obstacles for newcomers which must at first learn a language before they can change anything. Ruby is a well known language with a nice ecosystem around including benchmarking, profiling, debugging or testing frameworks. The latest mentioned testing framework is quite important, because good test coverage allows reducing of fear from changes. For tests we chose the well known framework RSpec, so people coming from the Ruby world know it and others find it intuitive.

Related to tests are also continuous integration that tests code after each code change and automatically sends new packages to the devel project and to Factory if needed. We make our CI node publicly visible on the openSUSE CI server, so everyone can see if build succeeded and what is the reason if it failed.

We also decided to help newcomers with a quick introductory documentation. One page recently updated to reflect the current state is about code organization which helps newcomers to orient in current YaST modules. The content is a bit terse and a minority of pages links to some old tutorials and documentation, but we take care to quickly react to questions and suggestions.

Another change is deletion of the internal YaST IRC channel and now all communication happens on the #yast Freenode channel. This change really increases the chance that you catch YaST developers on IRC. Others ways are the YaST mailing list, Bugzilla, GitHub or openSUSE feature tracker.

So let’s start hacking YaST and if you find any obstacle, contact us, so we can remove it.

openSUSE and GCC part 9: Open Build Service why should I use it?

December 11th, 2013 by

Imagine yourself in place where: you have succeeded to create best open source project ever appeared in face of earth. Your project has most fabulous source management system ever imagined (mostly coded by you) and you release tar balls often with plenty new neat features. You have managed that your project users provide some binary builds for Windows, Mac OS X and some bunch of Linux distributions. So your ride is smooth and pleasant (Mr. Maslow just waves to you from bottom of pyramid). Then black clouds arise and some Linux build manager who is doing binary builds for spefic important Linux distribution just vanishes upon the earth or you notice it would be nice to support more wide range of distributions than you allready have. Then you should consider using Open Build Service or openSUSE version of it known as OBS. (more…)

Discussing about the future of openSUSE

December 11th, 2013 by

This week, the openSUSE team blog is written by Agustin, talking about the proposals the team has done for openSUSE development.

A few months ago the openSUSE Team started a journey that achieved an important milestone last Tuesday, Nov 26th 2013. We have worked on creating a picture of relevant areas of the project in 2016 together with some of the actions we think should be taken during the following months to achieve it. To stop working and raise your head once in a while to analyze what is around you and setting a direction is a very good exercise.

The process we followed

The first step was working on data mining. After many hours of analysis, we identified some clear trends that helped us to establish a solid starting point to begin to work with. Once that phase was over (this is an ongoing process, in fact), we worked for a few weeks/months in trying to define that future picture interviewing several dozens of people. We refined that first attempt through several iterations, including many of those who participated in the original round and others who didn’t. Susanne Oberhauser-Hirschoff was the person who drove that process with Agustin.

We soon realized that discussing high level ideas in a community used to “Get shit done” was going to be easier if we complement them with some more down to earth proposals, specially in technical aspects. We cannot forget that, after all, openSUSE is a technical (and very pragmatic) focused community.

So, in parallel with the already mentioned refinement of the big picture, we started discussing within the team the actions needed to take to make the big picture a reality, the openSUSE development version a.k.a Enhanced/New Factory. After many hours of (sometimes never ending) discussions, we agreed on the ideas we are currently being published, together with the motivations behind them.

Another aspect we tried to bring to the discussion has been a strong dose of realism, trying to ensure that whatever we came up to was compatible with the nature of the project. We have also put focus on making sure that the initial proposal is achievable. So as part of community, we understand very well we cannot succeed alone. We need to work with you. So we just opened with the community a process analogous to what we went through within the team. It might be different in form but similar in principles and goals.

What are we going through these days?

These days the proposals are being discussed in different mailing lists. We are collecting feedback, discussing it, summarizing it, adapting the proposal to it … trying to reach agreements before defining what to do next.

What the proposal looks like?

We divided the proposal in a series of smaller proposals we are publishing in the project mailing list, where the general community topics in openSUSE are discussed, and/or factory ML, where the more technical discussions take place.

  1. openSUSE 2016: taking a picture of openSUSE today
    This mail summarizes the analysis phase we went through. We have tried to provide a simple picture of openSUSE today so the following articles can be justified to some extend.
  2. openSUSE 2016 picture
    This text summarizes the proposed picture for the end of 2016 (in three years). The goal is to set a direction for openSUSE

  3. openSUSE Development Workflow

  4. O Factory – Where art Thou?
    Stephan Kulow summarizes the Action Plan for the first aspect pointed in the previous picture: the new Development process (Factory).

The following articles describe in more detail some relevant (also new) elements pointed in the previous article, since they are new or modify the current process significantly. Some of the articles are in the queue to be published.

  1. One of the options for staging projects
    In this mail Michal Hrusecky provides some details and examples on how the new staging projects might work in the future.
  2. openQA in the new proposal
    This text, written by Ludwig Nussel, explains the principles that should drive the inclusion of openQA in the Factory development process, according with the proposed workflow.
  3. Karma for all
    This mail, written by Ancor González, summarizes our ideas to include a social feature in the process to help achieving Factory goals.
  4. Policies, or why it’s good to know how to change things
    The new process needs to be adaptive. Antonio Larrosa proposed a way, taking what other projects do in this regard as reference.

There might be an eighth article describing some smaller, still relevant, ideas. After publishing the “content”, we will release one last article providing a information about how to achieve these ideas, describing also our compromise in terms of effort and pointing out the challenges we perceive in the plan from the execution point of view.

We would like to invite you to the debate if you haven’t raised your opinions yet.

openSUSE and GCC part 8: RPMs and how to write them

December 3rd, 2013 by

It seems this it’s already 8 of this 10 part series of using GCC with openSUSE. This time topic is: RPM. RPM started as Redhat Package Manager and then it involved to RPM package manager (self explaining acronym like GNU). RPM packages are just files containing all the needed stuff to install application, font or something else in to openSUSE system. (more…)