Notice

This release concern only owners of radeon HD5xxx or above. And adventurous users who know how to deal with troubles.
The majority could easily wait the final release, expected somewhat later even if it take a long time

This is experimental & BETA software, it could fix issues you encountered, but also can eat your kittens. You’ve been warned !
flgrx build for 3.11 series kernel ( Tumbleweed & 13.1 ).
But this time I’ve to update the Sebastian script myself, so I consider also the package as beta stage.

Installing the new repository

Admitting you’ve the normal repository named FGLRX, (use zypper lr -d to find the number or name you give it). You have to start by disabling it
so you could fallback to it quickly. Open a root console or add sudo at your convenience and issue the following command:

zypper mr -dR FGLRX

The beta driver is available for 11.4 (evergreen kernel), 12.1, 12.2, 12.3, 13.1, Tumbleweed (12.3 based + kernel 3.11) at amd-fglrx-beta

To add another repository in the same console as root issue the following command which will install normally the right repository for your distribution

zypper ar -n FGLRX-BETA -cgf http://geeko.ioda.net/mirror/amd-fglrx-beta/openSUSE_`lsb-release -r | awk '{print $2}'` FGLRX-BETA

If you are using Tumbleweed use this one

zypper ar -n FGLRX-BETA -cgf http://geeko.ioda.net/mirror/amd-fglrx-beta/openSUSE_Tumbleweed FGLRX-BETA

Now the update/upgrade process

zypper dup -r FGLRX-BETA

Let the system upgrade the package, and try to enjoy the new beta

Release note about 13.10 BETA2 and new repository

This BETA Catalyst fglrx version support openSUSE version from 11.4 to 13.1 (new repository) and also Tumbleweed (thus also kernel 3.11x series).

We create a new repository, to avoid any mix between stable and beta. If you want to try it, you will have to disable the amd-fglrx, and install the
new repository. Also the signer of package have change and use now the generic builder gpg key at Ioda-Net. (gpg key id 65BE584C)

Release Note

A release note is available on AMD website

Highlights of the AMD Catalyst™ 13.10 Beta Driver for Linux:
This release of AMD Catalyst™ Linux introduces support for the following new features:

    Not Applicable

Resolved Issues:

    [383176] System hang up when startx after setting up an Eyefinity desktop
    [384193] Permission issue with procfs on kernel 3.10
    [373812] System hang observed while running disaster stress test on Ubuntu 12.10
    [383109] Hang is observed when running Unigine on Linux
    [383573] AC/DC switching is not automatically detected
    [383075] Laptop backlight adjustment is broken
    [383430] Glxtest failures observed in log file with forcing on Anti-Aliasing
    [383372] Cairo-dock is broken
    [378333] Severe desktop corruption is observed when enabled compiz in certain cases
    [384509] glClientWaitSync is waiting even when timeout is 0
    [382494] C4Engine get corruption with GL_ARB_texture_array enabled

Open Issues:

·   Not Applicable

Sebastien Siebert making script

This time Sebastian is doing work elsewhere, So I’ve adapted his beta1 to the new beta2

Raw & source for the script done

See below what to do in case of troubles.

Or you can also ping him on irc (freespacer) or me (tigerfoot)

Debugging troubles

I recommend in case of trouble the use of this script
which can collect the whole informations needed to help you. then you just have to issue a simple commande in console to collect all informations, you can review them, and finally transmit them.
Check the website to get the latest.

su -c 'sh makerpm-amd-13.10-beta2.sh -ur'
The system report 'amd-report.txt' was generated.                                                                                                          [ OK ]
Do you want to read the system report 'amd-report.txt' now? yes/no [y/n]: y
Are you sure to upload the above-named system report to sprunge.us? yes/no [y/n]: y

The report was uploaded to sprunge.us.
   The link is:  http://sprunge.us/eMEB

Copy paste the link in the comment zone of Sebastian post

Thanks to Ioda-Net Sàrl which proudly offer bandwidth & openSUSE powered server to serve you rpm.

Good tests, and don’t forget to give your feedback to AMD

update: new image with kernel-3.6 and minimal X11/icewm http://www.zq1.de/~bernhard/linux/opensuse/raspberrypi-opensuse-20130911x.img.xz (103MB)

We got a new armv6 based image for the Raspberry Pi.
This one is only 82MB compressed, so pretty minimalistic.
http://www.zq1.de/~bernhard/linux/opensuse/raspberrypi-opensuse-20130907.img.xz

The exciting new thing is that this was created using an alternative image building automatism which I wrote from scratch in three hours this morning.
The scripts can be found at
https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryPi/altimagebuild
and are also embedded within the image under /home/abuild/rpmbuild/SOURCES/

This means that everyone can now easily build his own images the way he likes and even branch and do submit requests for changes that are useful for others.
The way to use this is simple.
If you have 6GB RAM, you can speed things up with export OSC_BUILD_ROOT=/dev/shm/arm before you do
osc co devel:ARM:Factory:Contrib:RaspberryPi altimagebuild
cd devel:ARM:Factory:Contrib:RaspberryPi/altimagebuild
bash -x main.sh


This pseudo-package does not easily build within OBS or osc alone because it needs root permissions for some of the steps (chroot, mknod, mount), which could only be workarounded with User-Mode-Linux or patching osc.
The build consists of three steps that can be seen in main.sh:

1. First, osc build is used to pull in required packages and setup the armv6 rootfs.
2. Second, mkrootfs.sh modifies a copy of the rootfs under .root to contain all required configs
3. And finally, mkimage.sh takes the .root dir and creates a .img from it that can be booted

This can build an image from scatch in three minutes. And my Raspberry Pi booted successfully with it within 55 seconds.

There are some remaining open issues:

• the repo key is initially untrusted
• still uses old 3.1 kernel – solved
• build scripts have no error handling

Compared to the old image, this one has some advantages:

• It is easier to resize because the root partition is the last one
• Compressed image is much smaller
• Reproducible image build, so easy to customize
• It is armv6 with floating point support, so could be faster
• We have over 5200 successfully built packages from openSUSE:Factory:ARM
  so for example you can install a minimalistic graphical environment with zypper install xauth twm xorg-x11-server xinit and start it with startx

So if you wanted to play with openSUSE on RPi, you can do so right now and have a lot of fun.

I personally already thanks of the actual donors. You rocks !
We are almost done at today, but almost is not done

So if you can spread the word a bit more, that’s would be really cool. My objective is been able to give the money back to Sebastian Siebert during our openSUSE conference. And so create a kind of ceremonial.

Can I count on you ?

 

So how can we help him? Simply giving back a little amount of money, if you can afford it.
I’ve opened a pledgie for that : see the full explanation at
pledgie.com/campaigns/15879.

I really count on you. Spread the word.

ps : Catalyst 11.8 is out, stay tuned, I’ll be back this week-end.

ETHZ building

A group of 20 people met in ETHZ F26.3 room Friday afternoon (3pm to 7pm). To assist the Gnome 3 Launch party. We were expecting more people, but a so sunny weather, and a Monday off in Zürich doesn’t help to keep people inside after a long winter.

Marcus Moeller showed us a deep overview of the whole Gnome 3 desktop, with the strength and weakness (non yet finished features or controversial ones).

Then there’s some talks about features, what will happen unity/ubuntu/gnome etc …

On my side I did a late presentation about what’s openSUSE project is, and its associated SUPER COOL tools like OBS and susestudio.
It was supposed to last 15 minutes long. I was asked only Tuesday night to do it! But in fact we spend more than half an hour demoing obs and susestudio. Really was cool to do.

A special thanks to Biju Gopi Thilaka for setting up that party.

Biju Gopi was kind enough to share his slides with us, so keep reading …

Gnome3 resources

Go to gnome3.org website, to get a idea about the new features, you can eventually get the live cd (an openSUSE 11.4 32/64 bits) is proposed and a 32bits fedora latest

I (with the help of Izabele Valverde in fact) also found this videos series on you tube.

GNOME 3: Deeper Hardware Integration

GNOME 3: App-based Window Management

GNOME 3: Accessing Apps Quickly

GNOME 3: Fewer Interruptions

GNOME 3: Creating a Workspace

GNOME 3: Working with Windows

That’s all folks for this openSUSE Ambassador report

Nota : just a word to my KDE’s relatives, no I didn’t nor will change my desktop. Gnome 3 looks pleasant but miss some keys features I need, and have under kde4

Story board

Everything starts with an envelope

Hey the new issue (126) arrived today

A good geek doesn’t spend time to open it

This issue contain the openSUSE 11.4 dvd

Brand New, Get started sounds good!

Linux Magazine issue 126

Open the mag, and you can’t escape it!

Not only the dvd, there's the famous poster

11.4 on the wall, Cool Green!

first face 11.4

Let examine cheat-sheet

Zypper

detailled view on openSUSE ressource

openSUSE resources

details about zypper on the cheatsheet face

global view

the full view of cheatsheet

Thanks

This poster wouldn’t exist without a big collaboration effort of several openSUSE members and contributors.

To distribute for GNOME:Ayatana on the 11.4 cycle, I’m going to use ‘Spaceman Goldrush Edition’ from ‘mydarktime’, a German artist. I’m happy that mydarktime has been so kind in allowing openSUSE to distribute this package under CC-BY-SA. I will also take the opportunity to quote him:

“(…)  I would be very pleased to see mine in it” (wallpaper pack on GNOME:Ayatana).

I find this wallpaper very attractive and it doesn’t really tire me up from looking at it, which is really, really nice! I hope everyone else likes it also!

Spaceman Goldrush Edition @ Deviant ART

Here is what you need to participate:
– a recent version of openSUSE (11.3 or a milestone of 11.4). It’s okay to run openSUSE in a virtual machine.
– an IRC client to interact with the other participants
– good mood

A small team will organize the event by providing lists of bugs, and will be available to guide new contributors if needed. So it will be easy to help!

For this specific Bug Day, we will focus on the “zombie” bug reports: those are reports against old versions of openSUSE (openSUSE 10.x and 11.0). As some reports might still be valid, we don’t want to close all of them automatically. We will therefore check all those reports to see if they are still valid in the latest version of openSUSE (11.3 or a milestone of 11.4). The goal is to close those bug reports if possible, or, if they are still valid, to move them to a current version of openSUSE so that they’re not lost in limbo. So during a full day, people come on irc and help each other triage bugs.

Please note that this is only for openSUSE bugs (living in bugzilla.novell.com), but a solution for some bugs might be to forward them upstream.

Come on #opensuse-bug (freenode) on a Saturday 27.11.2010, we’ll be glad to have you join the fun!

this post is just request for all obs-packagers. Please, don’t forget write some documentation about your projects (which you maintain or develop). I mean, documentation for developers. This make more easy to understand logic of program, connection between some modules inside or interfaces between widget/applet and “system/hardware part”. For sure, comments in source code (or in changelog) help, but some times they give not so much clarity.

This is not so complicated to write one-two pages about project, which you hack. This also can save time of new developers. They will not ask you about architecture of project, and that will save your time too

I don’t know how will be better to do it: use wiki (create a new page) or add just text-file in source project. Anyway it’s not so important where will be this documentation, main things that this documentation will be exist