Home Home > Distribution > Factory
Sign up | Login

Archive for the ‘Factory’ Category

openSUSE ARM image

January 21st, 2012 by

When I wrote this week, how I ran openSUSE on my genesi smarttop some people asked for a ready-to-use image. After spending less than 8 hours fiddling with u-boot-scripts, partition tables, tuning ext3 and initrds, it was done… and is now so easy:

wget http://www.zq1.de/efika.img.xz # 83MB
xz -cd efika.img.xz | dd of=/dev/sdX bs=1M

with sdX being the device name of your SD-card (e.g. “mmcblk0″ on the smarttop itself) with at least 1GB (actually 1024000000 bytes) of free space.

When inserted at boot, it should just boot up within 23 seconds and let you login as root with password “linux” on SSH, serial and with a USB-keyboard on HDMI. I spent some effort on putting as few packages as possible into it. Still, you have zypper to install packages and nano to edit files.

There is still a known hangup when you try to reboot. Workaround is: init 2 ; sleep 12 ; killall rsyslogd ; umount /boot/ ; mount -o remount,ro / ; reboot

As it still uses the original linux-2.6.31 kernel, it has another bug that also happens with pre-installed Ubuntu: sometimes (in ~40% of cases), boot stopps early, before graphics is initialized, when the last line on serial is “console handover: boot [ttymxc0] -> real [tty1]“. Try turning it off and on again.

This should allow you to have a whole lot of fun…

running openSUSE on ARM

January 19th, 2012 by

This week I finally got my genesi efika MX box. By default it has on old Ubuntu version installed on its internal IDE-attached 8GB SSD. It features 512 MB RAM and a 800 MHz ARMv7 CPU.

Using a HDMI-cable and an HDMI-DVI-Adaptor I got it connected to a monitor, plugged in a USB keyboard+mouse and it pretty much worked out of the box with WLAN,Ethernet,X11 (except for a bug that causes it to force you to change PW on every console login). How boring.

Having read about recent progress with openSUSE on ARM I wanted the excitement of running it on this box.

Michal’s image and script (now in alpha) was very helpful to get me started within 15 minutes.

If you have any (e.g. x86) openSUSE system running, there is another easy way to create a working ARM chroot-environment:

zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/openSUSE_12.1/openSUSE:Tools:Unstable.repo
zypper install qemu osc
osc co openSUSE:Factory:ARM bash
cd openSUSE:Factory:ARM/bash
edit bash.spec # add lines with your packages like BuildRequires: zypper,vim
osc build –no-verify –clean standard armv7l

If it worked well, /var/tmp/build-root/ should contain a chroot environment. E.g. you can run

file /var/tmp/build-root/bin/bash
/var/tmp/build-root/bin/bash: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, BuildID[sha1]=0xed9ca12f44c8591560d780cf807b6b6cf8ca8873, stripped

I partitioned my SD-card into two partitions. The first one for /boot with ext2 (needs only 150MB) and the second one for / to contain the rootfs. Be sure to have barrier=0 in your fstab for all ext[34] partitions so that writing to SD will not be as slow. The default U-Boot configuration first checks on the first partition of an SD-card for boot.scr which is a uImage-formatted version of a U-boot script. I copied all of Ubuntu’s /boot and /lib/modules/, slightly adapted their boot.script file to have root=/dev/mmcblk0p2 and uImage/uInitrd-2.6.31.14.26-efikamx as kernel/initrd, dropped “quiet splash” and added “console=ttymxc0,115200″ to see more of the boot and ran a line from another helpful site:

mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n “my boot script” -d boot.script boot.scr
echo mxc0:S12345:respawn:/sbin/agetty -L 115200 ttymxc0 vt102 >> /etc/inittab # for serial console

However, this failed to boot. Using the serial debug console, I could see U-boot trying to load the boot.scr but it was thinking it was zero bytes for some strange reason. Re-creating my /boot partition as a raw copy of /dev/sda1 with my adaptions ontop finally gave me an SD-card that just boots openSUSE Factory on ARM with framebuffer console on HDMI/DVI.

Find more ARM-related info on our openSUSE ARM Portal

ATI/AMD fglrx 8.902 Catalyst 11.10 available for openSUSE 11.3, 11.4, 12.1 & Factory

November 5th, 2011 by

superseeded by http://lizards.opensuse.org/?p=8224

The AMD/ATI Catalyst 11.10 / fglrx 8.902 is now available

Importants informations are contained is this post, so carefully read it!

linux.ioda.net is replaced by geeko.ioda.net

I decide to re-organize the openSUSE stuff on my servers, and then I create a dedicated host geeko.ioda.net for that. I firstly link all old links as alias or setup redirection to the new host.
So if you can’t change the old address immediately don’t worry until December 31st.

Like before the server is fully accessible by ipv4 & ipv6, powered by openSUSE distribution.

Server layout

The new hostname is : http://geeko.ioda.net
Different kind of mirrored stuff /mirror
ATI fglrx mirrors http://geeko.ioda.net/mirror/ati
GIT Mirrors (sync every 10 minutes) /git
Gitorious clone of opensuse/art http://geeko.ioda.net/git/art/
Gitorious clone of opensuse-artwork http://geeko.ioda.net/git/opensuse-artwork/
GitHub clone of the new consolidated artwork http://geeko.ioda.net/git/artwork/

Rsync services

For those of you who need to sync the repository (ATI or GIT) you can now proceed with rsync.
rsync://geeko.ioda.net/ati/ for amd/ati repository and rsync://geeko.ioda.net/git/ for the artwork/marketing stuff

Example for a mirror of fglrx for openSUSE 12.1

rsync -av -P --no-checksum --no-o --no-g --delete -h rsync://geeko.ioda.net/ati/openSUSE_12.1/ /Your_Best_Path_Storage/mirror/ati/openSUSE_12.1/

We need you!

Even if today I already change the main ATI wiki page there will have a lot of stuff outside which contain the old server address. If you can fix them each time you saw that error, it will help any potential users to get the right informations.
About the wiki, the page need also your love and contribution, look at the wiki team remark in the header. So if you feel comfortable with wiki syntax, your help in fixing SDB/ATI will be really appreciate.

- Are you a virtuose on the forums, please pick and paste those informations there!
- Are you a social network addict, please forward as much as you can!
- Are you a designer/artist, I need something great to the home page of geeko.ioda.net, contact me, let a comment

You are brave, and knows how to fix your computer? There a beta one click installer available (feedback welcome)
AMD/ATI fglrx one click installer

(more…)

New Style for YaST2

October 24th, 2011 by

YaST2 got a lot of improvements which will be available in openSUSE 12.1. YaST doesn’t accidentally overwrite configuration files anymore (last bug fixed ;-) ) and snapper provides a rollback function for configuration options, just to mention a few. Therefore it’s time to give YaST2 a new and fresh style. As YaST Qt supports Stylesheets it’s simple to influence YaST’s style.

Screenshot of YaST's New Style

FACTORY contains the new style already. Packages for older releases are also available in my build service project: http://software.opensuse.org/download.html?project=home:tgoettlicher:Factory&package=branding-openSUSE.

I hope you like it. You can use YaST’s Stylesheet Editor to play around the the stylesheet as described in my this blog post. Please send me improvements you want to share. Thanks.

Factory Progress 2011-08-05

August 5th, 2011 by

The last few weeks have seen some a lot of package updates thus keeping our review and checkin team busy. I’d like to mention Sascha Peilicke who reviewed alone this week lots of packages. Have a look at just two numbers: In all of July we had 1001 check-ins and just from August 1st to 4th we had already 276 checkins.

The legal team has also gone through the long list of new packages and package updates during the legal reviews and reduced this week the list from over 100 packages to 12 packages now. Thanks Ciaran and Christoper for your legal review!

(more…)

Factory Progress 2011-07-18

July 18th, 2011 by

I’ve noticed the following changes that might interest people using and developing openSUSE Factory:

Package changes

GNOME 3.1.3

The GNOME team plans to have GNOME 3.2 in for openSUSE 12.1 and thus have updated to the current development release 3.1.3. They have also started removing old GNOME 2 packages that are not needed anymore.

systemd

Frederic gave an update on systemd integration. The graphical bootloader allows now to switch during boot between systemd, SysVinit and also shell code.

Also, Lennart Poettering wrote in his “systemd for developers” series about socket activation where he uses cups as example.

(more…)

Factory Progress 2011-07-01

July 1st, 2011 by

Here’s with some delay the next incarnation of Factory Progress. I’ve noticed the following changes that might interest people using and developing openSUSE Factory:

Package changes

Linux 3.0

Linux kernel 3.0 rc5 is currently on its way to factory and the header files (in package linux-glibc-devel) have already been updated for it. If your software reads the Linux kernel version, please check that it can cope with the two digits instead of the three of the new version. Best would be to not read the version at all.

Systemd

Frederic has proposed a “Road to systemd for openSUSE 12.1″. Systemd is a replacement of the SysVinit scripts that we have been using and improving in the past with many new – including some controversial – ideas. Check his blog post for additional references about systemd. The majority of the distributions are moving to systemd as well and standarizing on it, will allow to share some more code and development in this area.

We’re now in phase 1 – which means: Get systemd running as an option. Once this is working satisfactory, we can switch the default (phase 2) and decide what to do with SysVinit support.

(more…)

ATI/AMD fglrx 8.861 Catalyst 11.6 available for openSUSE 11.2, 11.3, 11.4, Factory

June 17th, 2011 by

New version of catalyst 11.6 / fglrx 8.861 available

fglrx-8.861

Please refer to my previous article where all the installation procedure is explained.

  • Quick résumé :
  • There’s no full changelog about them, but Catalyst 11.6 installer (pdf)
  • Get the cheat-sheet 11.6 version
  • Kernel supported up to 3.0x version
  • Should be the latest version supporting 11.2
  • Wrong (to my point of view) create an xorg.conf file which is unneeded if you work with /etc/xorg.conf.d/50-device.conf and have driver "fglrx&quot inside

Warning

Some instabilities could happen. In case of crash like no keyboard, mouse, and blackscreen on reboot. Try to shutdown properly your computer with the shutdown poweroff button (or remote ssh). On reboot, just add 3 at the end of grub line to restart in console mode.
Then with yast or zypper you can always remove the actual version and try the previous version available in the repos.

All credits to Sebastian Siebert (freespacer) : 11.6 article (German)

What about tumbleweed, factory?

Users have reported that version 8.861 of catalyst 11.6 compile correctly under Tumbleweed with 2.6.39 kernel and the driver is ready for kernel 3.0x, so until xorg change too much and then AMD support for the new version, installing the 11.4 version should work

For factory, I’ve build a repository (see previous article) that can be used, and fglrx build.
The new package are called SUSE121 & no more SUSEFACTORY.

Stats Numbers ?

Month Unique IP Number of visits Pages Hits Bandwidth
Jan 2011 2355 6411 19688 35263 16.63 GB
Feb 2011 2906 7719 26383 41142 22.37 GB
Mar 2011 8055 21157 228494 258613 59.13 GB
Apr 2011 10592 29129 418281 437416 76.87 GB
May 2011 12511 36816 608350 626901 104.91 GB

All proudly served by openSUSE powered server! zypper dup from 11.2 to 11.4 in 45minutes last month

Factory Progress 2011-06-03

June 3rd, 2011 by

This week saw the release of the first milestone of openSUSE 12.1 and work on factory is continuing, I’ve found the following changes important:

GNU C Library (glibc) 2.13

We’ve updated glibc from version 2.11 to 2.13 which brings many bug fixes and AFAIK no major breakages to packages. The package itself got cleaned up a little bit as well, so please report any problems.

GO Programming Language

Factory now contains a compiler for the GO language which is “is an expressive, concurrent, garbage collected systems programming language that is type safe and memory safe.”. More details about GO are available on the openSUSE Wiki, the devel project with additional packages is devel:languages:go.

Packaging: Source Processing

The usage of _service files in Factory confused many packagers and resulted in broken packages so that these will be deprecated. As a replacement, Adrian implemented now a new source processing method and asks for testers.

Packaging: Adding useful Provides to cups drivers

Vincent “updated python-cups to a new version, and it is now shipping
files to automatically add Provides tag to packages that are shipping
cups drivers.”. This allows desktop packages to install the right printer driver – or users to do it via zypper. Packages with cups drivers just need to add a “BuildRequires: python-cups”.

Open Build Service Improvement

The “My Work” view has been updated to better show packages that are in review state and need your review. I suggest everybody to check out the page and cleanup your list.

Multiple Buildroots with osc

If you like to use more than one build at the same time, there are several options like pointed out on the opensuse-packaging mailing list:

  • Use of the environment variable OSC_BUILD_ROOT to define a build root.
  • Editing of the osc config file ~/.oscrc and setting build-root to contain the variables %(repo), %(arch),  %(project) or %(package).

Correction on auto-legal build service check

Jürgen corrected my report from last week: He would love to see the checks for auto-legal moved and welcomes any help.

Thanks

Thanks for the words of encouragement to my first blog post. I’ll try to continue this series. If there’s anything you think should be added to it, please contact me via email at aj at opensuse dot org.

Some updates on the Banshee repositories…

May 31st, 2011 by

Sometime ago Gabriel asked me if I could give him help with the Banshee repositories for openSUSE; This repositories have many users hanging around and some packages are enabled on other projects, which makes them somehow sensible to deep changes.

Today I’ve pushed to openSUSE:Factory Banshee 2.0.1 (latest stable release) and a few packages which live in the Banshee repository. I’ve also submitted a deletion request to ipod-sharp which is no longer maintained and was replaced in the past for libgpod.

I’ve fixed the pending issues I’ve seen on the Banshee repository and Banshee 2.0.1 and disabled SLE 11 builds (not requiring all the dependencies). The repository serves now the following platforms (banshee and banshee-community-extensions):
* SLE 11 SP1;
* openSUSE 11.3;
* openSUSE 11.4;
* openSUSE Factory;
* openSUSE Tumbleweed (new).

On Banshee:Unstable (which should hold the unstable releases, currently 2.1.0) I’ll be introducing some changes during the next days which will feature:
* Package being renamed to ‘banshee’, thus dropping the current banshee-1;
* Migration to pkgconfig() calls for >= 1130;
* Packages banshee and banshee-core get merged into banshee (currently banshee had only 4 documentation files);
*  New sub-package banshee-common to hold all the architecture independent files (ex: text files, icons, etc);
* A few cleanups on the spec file for unsupported platforms (SLE11 and SLE11SP1 do not meet the requirements for this version and superior).

Once this is implemented and tested I will look into Banshee:Alpha and see the best way to start building daily/weekly snapshots using the OBS magic available and some magic tricks hidden in Dimstar’s sleeve which kindly accepted my request to give me a hand on such evil task.

In the future, on the next stable release (2.2.0), I’ll move the changes from Banshee:Unstable to Banshee and hopefully change the development repository to Banshee (as if Factory has the latest stable release it makes no sense in having Banshee’s development repository in Banshee:Unstable) and synch all at once.

Users subscribed to Banshee:Unstable repository might see some turbulence during the next days, while users subscribing now through the 1-Click installer will already be installing Banshee with the changes described above.