Sorry I missed in December the annoucement release for the 8.920, but from what I’ve seen. zypper up do the job for you

Quick Résumé about 12.1

AMD rename their installer, So Sebastian did the same for his script.

I will just copy/google translate/paste here the comment made by Sebastian Siebert on his blog :

With this version AMD Catalyst Gnome 3.2 issues (flickering and screen cracks) are finally resolved.
According to AMD, the notebook with the PowerXpress technology (Intel-/AMD-Grafikkarte – discrete GPU) should work again.
I would be grateful if someone could test this functionality for me and give me feedback. Thank you.

See more at Sebastian’s blog. Don’t be shy, you can leave there the result of test in english too
See below what to do in case of troubles.

The rpms version 8.930 are available from Friday January 27th

My advise is to firstly remove any existing version with zypper rm, then just zypper in the new version, even if 8.930 are the first version I’ve seen making its upgrade correctly.

As usual, I let the last 2 previous versions in the repository, just in case you need it.

Catalyst 8.930 fglrx 12.1 in action

Tested on a fresh 12.1 + updates with a stock kde 4.7.2

Factory rpms are not available actually, I’ve not be able to build a new building machine for it.
Anyways, factory and 12.2 should keep their effort on debuging and testing widely the free radeon driver.

One-click-installer

As nobody killed me about the one click installer available, I upgrade its status to RC (feedback welcome)
For 32bits system :

For 64bits system :

(*) To know which kind of system you have, open a console, then run uname -a, and look the output if you see x86_64 on the line you are running a 64bits, otherwise a 32bits.

Installation, Caution, Troubles

Installation

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

For a first installation, if you don’t remove radeon from the initrd, you will get in trouble. Don’t thanks who removed that from the wiki.

Caution

• 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” inside
• AMD CCLE didn’t get correctly upgraded if xorg is running during the upgrade. My advise, let’s go to console and as root do the following :

  init 3
  rcatievenstd stop
  zypper ref
  zypper up
  init 6
  

  Let the package rebuild the kernel driver. And for me I always remove the newly xorg.conf file created.
  reboot is mandatory!

Debuging troubles

I recommend in case of trouble the use of his 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

su -c 'sh makerpm-amd-12.1.sh -ur'
The sytem 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.to? yes/no [y/n]: y

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

Copy paste the link in the comment zone of Sebatian post

Statistiques

December 2011 as shown a big bump on the server : 50,212 unique visitor for a roughly 320GB traffic for the rpm

1582GB has been distributed during 2011.

That’s all folks! Have fun!

If you live in the North hemisphere as I do, it’s winter time actually: cold temperature, freezing wind, snow … and 20 years older than your twenties, then you want to keep your head warm.
So the mission was : “what can I design (in other words : what crazy new idea can I have?) funky to wear, well fitting with the car design, and the rest of a geek’s wardrobe?
A beanie sounds perfect!

What

Something simple, quickly available, uni-geek-sex, nice etc. So 10 days ago, I’ve done my shopping with my favorite partner, and agree on a model, then checked cost and delivery time.
Here’s the picture, of how it should look.

I hope you will love it, and fight to get one for you?

Where When can I grab one?

There will be a small series (99) available on openSUSE’s booth during Fosdem (4-5 Feb) in Brussels. I will sold them 10€/piece, and half the money will goes to Fosdem organization. The rest cover the pre-serie cost.

My advice, don’t be in late!

How to build your own?

If you can’t attempt Fosdem, or can’t have one, you can easily start your own local production. I’ve choose the Myrtle Beach (MB 7584) white/lime,a Beanie with contrasting border, 100% polyacryl. They should be available in any clothes advertising shop. Then the logo is printed on it, better to have it embroidered but this is more expensive.

Have fun!

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…

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

But in the uni-kit-verse there’s one you must known, especially if you are the proud owner of a laptop or one of this computer the manufacter deliver its firmware only in DOS exe format.
FirmwareUpdateKit (was introduced in 2008 in openSUSE by Steffen Winterfeldt

How that works?

As the title of the post give you the right command, open a console, then use the cnf (command-not-found) tool to learn what to do

Install the package

cnf fuk

The program 'fuk' can be found in the following package:
  * FirmwareUpdateKit [ path: /usr/bin/fuk, repository: zypp (repo-oss) ]

Try installing with:
    zypper install FirmwareUpdateKit

Pretty clear and cool, let’s install that stuff!

sudo zypper install FirmwareUpdateKit
root's password:
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW packages are going to be installed:
  FirmwareUpdateKit syslinux 

2 new packages to install.
Overall download size: 758.0 KiB. After the operation, additional 2.1 MiB will be used.
Continue? [y/n/?] (y): y
Retrieving package syslinux-4.04-12.1.3.x86_64 (1/2), 642.0 KiB (1.9 MiB unpacked)
Retrieving: syslinux-4.04-12.1.3.x86_64.rpm [done]
Retrieving package FirmwareUpdateKit-1.1-14.1.1.x86_64 (2/2), 116.0 KiB (178.0 KiB unpacked)
Retrieving: FirmwareUpdateKit-1.1-14.1.1.x86_64.rpm [done]
Installing: syslinux-4.04-12.1.3 [done]
Installing: FirmwareUpdateKit-1.1-14.1.1 [done]

Get your bios

Nothing easy for that, you will have to surf on boring mfg website, and find an appropriate bios for your computer.

Be serious during that selection, you can screw up totally your computer

Time to fuk

As always before running a program, it’s always good to check if there’s the fine manual (not the case here) or try a -h –help

fuk --help
Usage: fuk [OPTIONS] FILES
FirmwareUpdateKit version 1.1.

Create bootable DOS system and add FILES to it.
The main purpose is to assist with DOS-based firmware updates.

Options:
  --grub                        Add boot entry to /boot/grub/menu.lst.
  --lilo                        Add boot entry to /etc/lilo.conf.
  --title TITLE                 Use TITLE as label for boot menu entry.
  --iso FILE                    Create bootable CD.
  --floppy FILE                 Create bootable (1440 kB) floppy disk.
  --image FILE                  Create bootable harddisk.
  --run COMMAND                 Run COMMAND after booting DOS.
  --verbose                     Be more verbose.

Nothing complicated as a nuclear plan here, everything seems to be self explicit.
Let try it, and install a new grub entry for the new A8 version for my lappy.

fuk --verbose --grub --run M4600A08.exe /home/bruno/src_tmp/HARDWARE/DELL_M4600/M4600A08.exe
/tmp/fuk.lSVIgS0cMt/fwupdate.img: chs = 186/4/16, size = 11904 blocks
- writing mbr
- writing fat12 boot block
- copying:
    /usr/share/FirmwareUpdateKit/kernel.sys
    /usr/share/FirmwareUpdateKit/command.com
    /tmp/fuk.lSVIgS0cMt/config.sys
    /tmp/fuk.lSVIgS0cMt/autoexec.bat
    /home/bruno/src_tmp/HARDWARE/DELL_M4600/M4600_A08.exe
c-3po:~ #

That’s all I’ve now a new entry in my grub list

title Firmware Update
    kernel /boot/memdisk
    initrd /boot/fwupdate.img

Apply

Now just reboot and use the grub entry, then upgrade your bios, like you will normally have done with you old complicated build iso, or diskette (I’m joking)

There are some issues like it is still not possible to configure everything via a GUI(use dconf-editor). I guess this is because the project is in initial stage and the rough edges will be sorted out as further development and contributions flows in.

Some gnome-shell extensions have been ported to work with Cinnamon, to enable them use dconf-editor, for example the org -> cinnamon -> enabled-extensions should look like this for all available extensions to be enabled:

['system-monitor@paradoxxx.zero.gmail.com', 'apps-menu@gnome-shell-extensions.gnome.org', 'dock@gnome-shell-extensions.gnome.org', 'drive-menu@gnome-shell-extensions.gnome.org', 'places-menu@gnome-shell-extensions.gnome.org', 'windowsNavigator@gnome-shell-extensions.gnome.org', 'xrandr-indicator@gnome-shell-extensions.gnome.org']

Please note that the package is for testing purpose only, it will not be maintained/updated in future, so if you are a developer who can hack and want to contribute to that project check it out, please report bugs directly on cinnamon project issue tracker, preferably with a patch fixing the issue . More information about the project is here and here.

  more screenshots…

Softwares for mathematics, chemistry, astronomy etc, servers like KIWI-LTSP, Fedena school ERP, Moodle course management etc., full multimedia, graphics, office suite, many popular programming languages including AMP stack, java, C, C++, python, ruby, latest stable Gnome and KDE desktop environments and lot more is packed in this release. More about softwares included here.

To know more about openSUSE Education project, file bugs, request enhancements, participate, or to get in touch with us visit Education Portal.

Create live USB stick or DVD with this image. About 15GB disk space and 1GB RAM is required for installation, more is better. Please note that we release 32bit image only, for users with RAM 4G or more install and use kernel-pae package.

Happy holidays…

Hosted at sourceforge.net

Direct Download | md5sum

Hosted at opensuse-education.org

Direct Download | new metalink | old metalink | md5sum | torrent

Use download manager or Metalink client such as aria2c for most efficient way to download.

Helping users, and I don’t mean only new users, cannot be done with pointing them to Google all the time unless it’s a very well-known issue. A Unix system like Linux comes from a very good tradition of man pages, howtos and other local information e.g. files in /usr/share/doc/packages/. Unfortunately this tradition seems to be dying. This wouldn’t be dramatic if there would be more openSUSE specific documentation, but this is not the case. It’s either brief, old or fragmented over the net in blogs or mailing list archives. Especially the latter may be a good source for solving problems, but some threads are filled with long discussions and the satisfied solution cannot be found with a few glimpses or even clicks.

Therefore all of us need to write more documentation that can be found easily and at best on *.opensuse.org servers. Otherwise the search function there is pointless. The best place for documenting solutions to common and not-so-common problems is the support database in the openSUSE wiki:

http://en.opensuse.org/Portal:Support_database

Writing things in your personal blog is good and welcome, but at the same time there should be an SDB article about the provided solution.

I have to add that there are a lot of people who already put a lot of effort into documenting things. This post is not to criticize, but to support them, so that there are not only a few who contribute valuable help to users.

It continues the KDE3 series published by me for previous openSUSE releases, 11.3 and 11.4

Unlike other similar LiveCDs, this build includes extended set of software, not only from official openSUSE 12.1 repository, but also from KDE:KDE3 repo.

The image includes openSUSE-specific presets and an auto-updater applet which allows to keep your installation up-to-date.

Since the final KDE3 release KDE3 in openSUSE repository undergone several changes.

The most visible fixes include the appearance of the “classic” style of the taskbar (the button of the active window now appears pushed, something that was broke in the last KDE3 release); the selection of the icons on the desktop now resembles the style used in the file manager with rounded corners. The LiveDVD ships with openSUSE artwork and exclusive openSUSE-style window decorations.

Direct download link:

http://susestudio.com/download/2dd3fc0c6ad40f78c4a53b0e4fdd7a8b/OpenSUSE_12.1_KDE3.x86_64-1.0.7.iso

Appliance link in Suse Studio:

http://susestudio.com/a/vv1af0/opensuse-121-kde3

The appliance is capable of being cloned so to create derivatives.

Hope you like it.

PS: If you haven’t already voted for the openSUSE board, just take your chance and just do it … now!