Home Home > Tag > openSUSE
Sign up | Login

Posts Tagged ‘openSUSE’

Fosscomm 2011 in Patras – Greece

April 25th, 2011 by

Fosscomm 2011

The event will take place in Patras this year. For those of you who don’t know, fosscomm is one of the major foss event in Greece.

I’ll go there and will make a presentation :
Amazing openSUSE : we, you, together a promizing future!

I hope to see all of you there! Come and meet the growing openSUSE Greek community, and most of the Greek ambassadors.

Follow them on Twitter. The official hashtag of FOSSCOMM 2011 is: #fosscomm2011

Official Patras city website

PS: The websites is also available in english :-)

Talk

Title :

Amazing openSUSE
We, you, together a promising future !

Talk Audience

general public, which would like to contribute in FOSS

No special IT knowledge is required.

Abstract

openSUSE project is open: there’s a place for everybody!

Come and (re)discover one of the oldest Linux distribution and one of the most youngest community.

This talk is about the community powering the whole actual openSUSE Project :

We will overfly openSUSE’s history, and the actual projects like open-build-service, susestudio, tumbleweed, evergreen, connect, openqa, and the near future a word about the openSUSE Foundation.

Follow us deeper inside with examples how collaboration works between contributors, users, across the borders with others distributions and upstream projects.

Want to be part of? Let’s talk about the “right” place for you!

 

Intel GMA500 Poulsbo drivers and openSUSE

April 12th, 2011 by

It was little bit annoying to notice that openSUSE only had Poulsbo (GMA500) drivers for openSUSE 11.2 (Sorry if i’m wrong just couldn’t find them on obs).
Poulsbo seems to be popular with notebooks (Acer Aspire One for example) and some embedded devices. These are not so good drivers but they work until we get better from FSF.
(more…)

GNOME3 iso by fcrozat and ATI radeon driver… a quick easy fix!

April 10th, 2011 by

Hi all,

For some time I wanted to check out GNOME3 and gnome-shell… My current chipset is ATI M92 RV710 and while the thermal performance with the proprietary driver is somewhat what I expect, the open source radeon driver does overheat my laptop a lot compared to flgrx. For the time being, fglrx isn’t really a choice because it just borgs the ‘activities’ bar on top… And until ATI fixes their driver, there’s no other choice than running with the standard radeon drm driver, which does provide a very pleasant experience with GNOME3 / gnome-shell.

For all that matters, KMS is to be enabled, period, full stop. And from this point… we have two options regarding power management:

1. Dynamic Frequency switching (not really working for me);
2. Profile based frequency switching (does provide what I need);

For all that matters regarding ‘profile based frequency switching’ we have 5 profiles available:

  • “default” uses the default clocks and does not change the power state. This is the default behavior.
  • “auto” selects between “mid” and “high” power states based on the whether the system is on battery power or not. The “low” power state are selected when the monitors are in the dpms off state.
  • “low” forces the gpu to be in the low power state all the time. Note that “low” can cause display problems on some laptops; this is why auto only uses “low” when displays are off.
  • “mid” forces the gpu to be in the “mid” power state all the time. The “low” power state is selected when the monitors are in the dpms off state.
  • “high” forces the gpu to be in the “high” power state all the time. The “low” power state is selected when the monitors are in the dpms off state.

Now, what I did might not be an option to everyone, but for sure it does provide a nice solution for my problem… So be mindful of that… this is a personal preference based on the fact that I don’t require intensive GPU usage, neither I run intensive GPU requiring applications within GNOME3/gnome-shell (I have a normal openSUSE 11.4 with GNOME 2.32.x with fglrx dual boot config for those apps).

The first thing we might want to do is to switch to profile based frequency switching… how do we this? As root:

[code] echo profile > /sys/class/drm/card0/device/power_method[/code]

Now we have to pick one of those 5 profiles… and since I’ve already stated… I want the ‘low’ profile since I don’t really do much intensive GPU work…

[code] echo low > /sys/class/drm/card0/device/power_profile[/code]

Now… you might want to check out the different profiles and the different clocks used… this can be done through:

[code] cat /sys/kernel/debug/dri/0/radeon_pm_info[/code]

and will report something like this:

[code]linux-331w:~ # cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 680000 kHz
current engine clock: 299530 kHz
default memory clock: 800000 kHz
current memory clock: 249750 kHz
voltage: 900 mV
PCIE lanes: 16[/code]

This one is using the ‘low’ profile… Feel free to test stuff around and find which one better answers your needs… Also there’s far more that can be done… I hope this helps ATI users with DRM driver to bring out the best of your system and improves your GNOME3 / gnome-shell experience, at so that you can run it with good thermal performance without fglrx.

NM

GSoC Idea: Build Service Plasma Widget Suite

March 24th, 2011 by

I’m blatantly abusing GSoC for a project that I would like to see in openSUSE but that I’ve never had time to work on. But really it’s a worthwhile thing to have: a set of Plasma widgets that users and developers can add to their workspace to make it easy to see what’s going on in OBS in the projects that matter to them. If you want to work on a fun project with cutting edge technologies such as Qt, QML, Plasma then head on over to the GSoC 2011 Ideas Page.

openSUSE 11.4 :: Wine… A practical case…

March 15th, 2011 by

For some time I follow the openSUSE Forums which provide me a very interesting view about what our users do with openSUSE. I’ve noticed there are some relevant questions about Wine once in a while in the Games forums.

A few time ago one of my friends nagged me a lot to do a couple of levels in Lord of the Rings Online which has a ‘Free Play’ plan in Europe. People can create an account and play for free the game with some restrictions (contents, equipment, items, etc). Players also have the option of using the online game store to unlock several aspects of the game. I’ve used a free play account for this, as I don’t really dedicate much time to it.

I’ve downloaded and installed the game in a Windows 7 computer (abour 10.5GB’s),  updated it and it works as expected. My laptop has somehow better hardware and I’ve decided to see how it would run under openSUSE through wine! On WineHQ there’s some extensive know-how shared by the community about this game… for my little experiment I’ve used the following:

* Lord of the Rings Online installation files pulled from the installer (since I had previously downloaded the game on a Windows machine, I’ve used those files to avoid downloading 10.5GB’s again).
* Wine 32 bits (1.3.12, shipped with openSUSE, LotRO requires also wine-gecko);
* openSUSE 11.4 x86_64;
* ATI FireGL drivers, release 11.2;
* PyLotRO Launcher (written in Python, used to launch LOTRO since the normal Turbine .NET launcher has some serious issues);

Looking at everything written on WineHQ about LotRO it seems quite a hard task to get this running, luckily it’s actually the opposite… pretty much a quick step, though time consuming due to the size of the game. Here’s the procedures:

  • Installing wine on openSUSE 11.4

Installing wine on openSUSE is pretty easy (like any other software package). Make sure you are networked and open your favourite terminal emulator and type in the following command: zypper install wine wine-gecko. Zypp client will pull all the required dependencies and install the software. Please be aware that your system needs to have 3D capable drivers, often proprietary drivers.

  • Installing Lord of the Rings Online

As I’ve stated previously, I’ve had available the installation cache files from a previous Windows installation which made my life easier (around 10.5GB). If this is not your case, you can look into WineHQ and check how it goes with the installer. An interesting thread can be found here.

When one installs LOTRO on a Windows Machine it will create a folder on the Desktop called LOTRO_* which will contain a local cache of the files necessary to install the game. Inside of this folder there’s a ‘lotrosetup.exe’ runs the installer. To start the installation is quite easy… open a terminal (with normal user), navigate to the directory where we have the cache files from the installer and run: wine lotrosetup.exe. The installer window pops up preceded by a small splash screen. Follow the instructions on the screen and wait until it deploys the game (took around 30/40 minutes).

  • PyLotRO Launcher for Linux

There’s ways to run the game and the Turbine launcher (.NET) isn’t really friendly of wine. I’ve decided to go for PyLotRO which is a small launcher written in Python. I’ve made a small test package which is available on my test repository in OBS (openSUSE Build Service) and called it python-lotro. You can find it here. For openSUSE 11.4 it can download this RPM, python-lotro-0.1.14-4.1.noarch.rpm and install it with: sudo zypper install python-lotro-0.1.14-4.1.noarch.rpm. This will also create a link on your Games menu entry (works in GNOME, never tested on KDE).

You have the Linux launcher installer and are a tiny step away from being able to play LoTRO…

  • Updating the Game…

PyLotRO provides a small interface with the very basic functionality available from the Turbine Launcher. Allows to configure wine debugging output and patch the game amongst other features. Here’s a small screenshot how it’s looks:

To update the game, it’s only required to hit the ‘Tools‘ menu and select ‘Patch‘. This will access the game contents, download, decrypt and update the game to the latest version. Due to the size of the game it really takes a bit of time, so be patient.

WARNING: Before launching the game make sure that you have 3D effects disabled on the Desktop (ex: disable compiz or composite in Kwin). If this step isn’t done, the game might suffer of great performance issues and weird behavior. If something looks fishy, then that’s because you forgot this step. This also made me think in one thing… What impact will Unity and gnome-shell have in cases like this… when the accelerated 3D Desktop will generate performance issues in applications like in this case… something to look for in the nearby future…

After the update it’s possible to login into the game, configure the options and give it a go… You will need a game account first than can be created for free (Europe only as far as I am aware, the game seems to be under subscription in the US), make sure you download the European client as well.

  • Gameplay

The game tries to detect the best configuration for your system (Low in my case)… I’ve forced it to Very High, selected my native resolution and gave it a go. The game is fluid enough, though lags a bit in big cities (ex: Bree), this is somehow something to expect, the same happens in Windows. While I haven’t seen much problems with performance, I’ve disabled dynamic lighting and it’s somehow a bit better. The runs nice and everything seems to work.

I know many tutorials talk about winetricks and d3dx9… I’ve not did such things and the game runs very nice with the native wine dll’s without having the need of installing Microsoft’s DirectX files.

This was a very pleasant experience, and it really surprised me on the positive. OpenSUSE has a very nice version of wine capable of running at least LotRO and World of Warcraft without any issues! It’s something that is worth trying with openSUSE!

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

Virtual launch party for openSUSE 11.4 : RC1 is done

February 14th, 2011 by

Successfull RC1 launch!


Dear followers, after the official announcement, we test yesterday the place, and check how fun and cool it can be with several attendees.

The danse party Pop/Rock music themed was animated by DJ Yazz (Brittany Haefeli). Starting at 8:30 CEST the party was crowded during it’s 2 hours and a half. More than 50 people came and visit us during that time. Great that was twice what we expected !
(more…)

Join us for the first virtual launch party openSUSE 11.4

February 3rd, 2011 by

Annoncing the first virtual launch party

Dear folk, we are organizing a special event for the openSUSE 11.4 launch, and you’re invited. Virtually all of you can participate, and increase the success of it. And spend a good time.

Too soon? Not really, we are in the process to organize also pre-release party, certainly for the RC1 and RC2 launch. So you can practice before the real event. Prepare your environment, and dress your avatars with decent clothes, and gadgets.

We will do our best to welcome you in english, french & greek.
If you want you can also anwser our short pool we are looking about help.

Where?

Geekos place bar in SL

On secondlife.com, go to area macedonia. at 183,213,21 coordinates
Or fire the search engine, and look after Geekos group, then join that group

When?

During 3 days March 9 10 & 11 2011
Party start at 16:00 UTC ( 8am SL time)

What?

Join our special place build for that event and let’s get

  • Dance party
  • Free drink
  • Goodies
  • Wall of pictures
  • 11.4 installations movies
  • open minded discussions
  • Experience exchange

Who?

tigerfoot on secondlife
Morgane Marquis on secondlife

Your guests would be myself (tigerfoot) & Morgane Marquis.
A team of excellent dj’s as Lillith from Australia, Esquievel from USA, Stefanos from France,
or our great Greeks neighbors

 

Why?

Hey not so long ago I was kicked by H!
Because it’s a place where people have also fun, and we want to talk with them about the freedom & openSUSE.
Did you never attempt to realize something that has not been made yet?
Just to have a lot of fun! The full explanation Here

How?

To access that 3D virtual world, you need a recent computer 1.5Ghz or +, and good internet access >3500/300bps, and a 3D enabled graphics cards like radeon HD4xxx or more, Nvidia Geforce >9600, Intel > i945 & Intel Extreme.

To be continued

In the next weeks, I will publish an more technical article about how to get 3D world viewer installed on your openSUSE. And we are just finishing the picture gallery about that project which should be online next week (due to FOSDEM) this week-end.

Stay tuned !

Boo

January 28th, 2011 by

Arts, buffer, check, clutter, cobbler, colorblind, concurrent, convert, cook, crash, dialog, dump, expect, file, folks, fortune, genius, global, hello, indent, less, links, meanwhile, mirror, screen, sparse, suck, tree, units, words. What do these ordinary English words have in common? They are also names of software projects, which becomes a problem if you want to recognize package names in text. I understand that in the old days, the name of a command or application was only relevant in the context of the computer it ran on, and file names had to be short. Some of these names have allowed for a variety of jokes. But why, in the age of portable programs, WWW and search engines, can’t people come up with less ambiguous names? I mean, it’s not hard to join two words, or, at a minimum, prefix a word with a vowel, like, uhm, a round fruit does. :)

Oh, and did I mention that we have over 160 packages with a 2-3 letter name? The one mentioned in the title is a programming language, btw.

Massive update on Ubuntu software…

January 20th, 2011 by

Screenshot using Radiance Light Theme and default Ubuntu indicator layout.

Some brief updates about the ongoing work towards bringing Ayatana Project software into openSUSE:

1. Software Updates

Canonical recently released a batch of updates which bring new functionality (Indicators seem to respond faster now) and very nice improvements, some of them contributed by down-streamers. From my humble experience I would risk to claim that Canonical is doing an excellent job as an upstreamer. I’ve updated all packages to the latest versions. This allowed to remove some patches.

2. Unity

Unity is now one step closer. For Unity I’ve started to package Compiz git snapshots from the correct branches pointed by Unity documentation. This brought something new to me, cmake. I’ve done this very slowly, reading some docs meanwhile about cmake. My packaging around Compiz is mainly based on OBS X11:Compiz repository, so pretty much all the credits should be for the original project Packagers which done an awesome job. Currently I’m missing only 3 packages to test Unity. Recently with kernel and mesa updates some issues around ATI hardware seem to have fixed for openSUSE Factory users, which enabled in my case FireGL, therefore I can test properly Unity now and check for the integration into openSUSE.

Unity by default uses the Ayatana’s Indicators, and if they are not present, it will fallback to GNOME’s applets. This is very nice and I’m thankful Canonical made it this way. This brings non-Ubuntu users the Unity experience at almost no trouble, since there isn’t actually much patching required to implement Unity.

3. GNOME:Ayatana Repository

GNOME:Ayatana Repository will be populated during the next two weeks with the latest changes and will provide for the time being the Ayatana’s Indicators and Unity. I am currently working around libappindicator stack and it’s Indicators. Currently I’m testing the patches required on the GTK+ stack and this is pretty much the last barrier before going into #STAGE2, polishing and populating GNOME:Ayatana.

It’s not decided yet what packages are going to present on Factory. My wish is to push only Unity into Factory and it’s dependencies, this might not happen for 11.4 as I’m not sure about the freeze schedules and it might be too late already, but since we’re depending on Compiz upstream, we’ll see what happens. Even if Unity isn’t going to be available on Factory, I’m sure we can use KIWI or SUSE Studio to release a small openSUSE Unity Spin.

I’ve also decided that I (typo: previously would) wouldn’t like to see Unity available by openSUSE before the official release from Ubuntu, for which I wish all the success.

Since the very early start that I’ve been using pkg-config as much as I can. According to some information that I collected previously, this would be great for cross-distribution build. Depending on the time and work done, I might make the necessary modifications and enable cross-distribution building on this project, thus, making it available for other RPM distributions supported by OBS. This will require a bit of testing before, so it will be work to be done after 11.4 is released and during it’s lifecycle. Maybe by the time of openSUSE 12 gets released, we will have this project also available for other RPM based distributions. I have no knowledge on Debian packaging, but Ubuntu ships this software and Debian probably has it also available so… that won’t be a problem.

4. Artwork

I am providing on GNOME:Ayatana Ubuntu’s Light Themes (Ambiance and Radiance) and offering a patched version of Metacity that renders those themes perfectly. I’m not changing the original colors from the themes or modifying them in any way. So they might be a bit more of orange and not green.

I’ve contacted some people to ask if they would be willing to donate some artwork to make a small package with Wallpapers, some have answered yes, so I will make a small package with a couple of wallpapers for the traditional resolutions and distribute it alongside with this software as optional as always.

5. GTK2, GTK3 and QT

Implementation of GTK3 will be done within the next days, as I am also considering enabling QT support for KDE users (Indicators only for now).

That’s pretty much the result of the last days of work… more news to come in the nearby future.