Language Selection

English French German Italian Portuguese Spanish

openSUSE 10.3 alpha 3 Report

Filed under
Reviews
SUSE
-s

openSUSE 10.3 alpha 3 was released yesterday and it seems to be getting quite a lot of press from several sites this round. It's being announced with enthusiam as if it was a release candidate. Some exciting developments are occurring in the openSUSE camp and it's good to see some positive press for them. As usual I test drove alpha 3 and am ready to report my findings.

This release didn't bring any new visuals, other than fonts. It might be my imagination, but the fonts are a bit improved. It could be that all the press on the anti-aliasing has had some positive effects, or perhaps it was my using a different machine. Most likely it was my overactive wishful imagination. In any case, I'm having some issues with the dvd drive in my desktop machine, so this test was run on my HP laptop. I commented in the past, a couple of times, that the fonts were one of the major issues in my using openSUSE only as a backup or second choice to PCLOS on that machine, but testing 10.3 alpha 3 yesterday has me thinking this may no longer be the case. There are actually only a few of fonts installed by default that look exceptionally nice, but one only needs a couple really. Novell's position on Cleartype and the bytecode interpretter are clear, but perhaps they are working on alternative solutions.

This go around I didn't encounter any issues with libata drivers, but I wouldn't on that laptop anyway. During testing for my last report I erroneously thought openSUSE was following suite with Fedora in their handling of ata drives, but what turned out to be a bug was supposedly corrected for this release. And just my luck, I wasn't able to confirm it was all in the past. Hopefully I'll have a new dvd drive for my desktop soon (donations gratefully accepted <hint, hint>).

Last test I had problems with gnome as well. Unfortunately, they weren't corrected for the iso creation this release either. The panel crashes upon logging into Gnome and thus no menu is available. After being bitten on the ego last release, I did check with the Most Annoying Bugs list prior to testing (as opposed to after), so I wasn't surprised and also applied the fix which is to reinstall the gnome-main-menu rpm. There seems to be a problem with the Tango-icons rpm as it fails verification, so I had to use --nodeps as well as --force to reinstall this package. It was also recommended to use the control-center rpm available in the Extra-RPMS directory as well. So, I installed it at the same time. As a result, I had what appeared to be a fully functional gnome this time. The version numbers are still being reported as 2.18 although 2.18.1 was recently released. If openSUSE stays true to form, we will see an upgrade probably once they have all the kinks worked out in their current integration.

    


Speaking of gnome, this is perhaps the first time I've tested gnome on the laptop. In at least openSUSE's incarnation, we find power management and wireless connection (network manager) applets in the panel similar to found in KDE. They look very similar and have almost equal functionality. Almost. They don't have quite as many options available at click, but the basics are there. Additionally, just as kwallet offers to remember passwords and/or phrases, the keyring manager in gnome does the same. I don't usually opt for these password keepers, but decided to test it this round. It does appear to work well, although it seems just as annoying to input my keyring password each use as it would my wpa passphrase. I don't see the advantage, unless you have several to remember I suppose.

        


Some of the improvements announced this release include:

  • On x86-64: Firefox is now a 64-bit package and uses nspluginwrapper to handle 32-bit i386 plugins if needed.
  • AppArmor uses now a new parser. The kernel patches have been reworked completely.
  • GNOME 2.18 mostly integrated.
  • Update to Kernel 2.6.21 RC5
  • New opensuse-updater running natively under GNOME
  • Further fixes for using libata by default for IDE devices
  • New yast2-ftp-server module.
  • The package manager handles more than one CD/DVD drive.

The most annoying bugs list contains:

  • Java applications are not working due to implementation errors in SUN Java
  • The installation of vim-normal might fail
  • Branding and translations are still at the 10.2 level
  • The Radeon driver is broken and crashes the X server
  • Installation with several CD-ROMs might crash at some point
  • gnome-main-menu might crash in some installations

One point of note is the installation of vim-normal might fail. It did indeed here. In fact, I had a 1/2 dozen packages fail either due to what was reported as broken packages or failing verification. None seemed to be really important such as susehelp or tango-icons.

Some changelog highlights include:

  • opensuse-updater-gnome:
    • fixed some memory management problems
    • v 0.2.1
    • changing applet icon according to current operation/status
  • various gnome components & applications updated to 2.18.0
  • nautilus:
    • Update to version 2.18.0.1
  • nano:
    • update to version GNU nano 2.0.4
  • helix-banshee:
    • Update to version 0.12.1
    • Added more translations from SLED SP1
  • control-center2:
    • Added "Use default web browser" option
  • kdebase3:
    • simplify resize and rotate settings dialog
    • update 3_5_BRANCH.diff
    • update kickoff.diff from SVN
  • k3b:
    • fix detection of "sox"
  • kernel:
    • update to 2.6.21-rc5-git13
    • libata fixes
  • NetworkManager-kde:
    • add patch knetworkmanager-wpaeap_storage-hschaa-01.patch
  • gnome-session:
    • Session start script (gnome) cleanup
  • powertweak:
    • Fix cpuid check
  • xorg-x11-driver-video:
    • updated "nvrandr12" driver to current git
    • intel driver release 1.9.94
  • xorg-x11-driver-input:
    • updated joystick driver to release 1.2.0
  • OpenOffice_org:
    • updated ooo-build to 2.1.10
  • cups:
    • Upgrade to cups-1.2.10
  • Full Changelog Here

Some RPM version highlighs are:

  • kernel-default-2.6.21_rc5_git13-2
  • xorg-x11-7.2-62
  • gcc-4.1.3-40
  • MozillaFirefox-2.0.0.2-10
  • OpenOffice_org-2.1-18
  • kdebase3-3.5.6-26
  • gnome-desktop-2.18.0-6
  • qt3-3.3.8-12
  • gtk-1.2.10-948
  • gimp-2.2.13-53
  • freetype2-2.3.1-7
  • Full RPM List

So all in all, they are moving right along. There wasn't any new eye candy or major changes on the surface, but there was a lot of bug fixes and feature updates under the hood. One thing I noticed was that the new logout dialog boxes that we discovered in alpha 1 are now gone again. These options have reverted back to the originals.

It's always amazing to me, even after all this time testing their alphas and betas, that openSUSE releases are so functional and stable even during developmental cycles. It's particularly amazing when you look at all the customization, the sheer volume of packages, and size of system. I hope to start seeing some new eye candy in the upcoming releases, although we are usually teased through the beta portion and early release candidates while final window dressings are saved for the last release candidate or final.

The roadmap is still not fully planned out, but final is tentatively scheduled for the end of September.





ATI(fglrx) + 2.6.21-rc5 + 64Bit

There is another change in the latest kernel code which means that if you tried to compile and install fglrx from the latest ati driver (8.35.5) then you won't be able to suceed. Sad

I know from experience that this is the case at least in 64bit (not tried 32bit). There is however a fix out there which allows for this to work.
You could extract the driver from the install package and use the patch from: http://www.phoronix.net/forums/showpost.php?p=5204&postcount=38

This patch will allow you to build a working module for your system and although it was released before the 8.35.5 driver this was not included?? shame, but oh well it's available at least Wink

I tried building and installing the rpm, then after it bailed out used the code not removed from: /usr/src/kernel-modules/fglrx
This works for me on openSuSE 10.2 with a more upto date kernel of the day. (2.6.21-rc4-git3 if i remember correctly)

I haven't tried this on the latest openSuSE alpha but as this new alpha is based on a kernel that won't cause my laptop to melt (laptop hp:nx6125 and kernel 2.6.21-rc* )
I will happily migrate this alpha soon som nice cutting edge versions of some progs. I can't wait for openSuSE 10.3 full and lets hope that it has early inclusion of KDE4 stuffs Smile

Just in case the patch shouldn't be available it is below (hope it displays correctly):

--- firegl_public.c-orig 2007-02-21 19:56:45.000000000 -0500
+++ firegl_public.c 2007-02-25 12:31:59.000000000 -0500
@@ -119,6 +119,7 @@

#include
#include
+#include
#include

//#include
@@ -204,6 +205,70 @@
int errno;
#endif // __ia64__

+#if defined(__i386__)
+#define __syscall_return(type, res) \
+do { \
+ if ((unsigned long)(res) >= (unsigned long)(-(128 + 1))) { \
+ errno = -(res); \
+ res = -1; \
+ } \
+ return (type) (res); \
+} while (0)
+#define _syscall2(type,name,type1,arg1,type2,arg2) \
+type name(type1 arg1,type2 arg2) \
+{ \
+long __res; \
+__asm__ volatile ("push %%ebx ; movl %2,%%ebx ; int $0x80 ; pop %%ebx" \
+ : "=a" (__res) \
+ : "0" (__NR_##name),"ri" ((long)(arg1)),"c" ((long)(arg2)) \
+ : "memory"); \
+__syscall_return(type,__res); \
+}
+
+#define _syscall3(type,name,type1,arg1,type2,arg2,type3,arg3) \
+type name(type1 arg1,type2 arg2,type3 arg3) \
+{ \
+long __res; \
+__asm__ volatile ("push %%ebx ; movl %2,%%ebx ; int $0x80 ; pop %%ebx" \
+ : "=a" (__res) \
+ : "0" (__NR_##name),"ri" ((long)(arg1)),"c" ((long)(arg2)), \
+ "d" ((long)(arg3)) : "memory"); \
+__syscall_return(type,__res); \
+}
+#elif defined(__x86_64__)
+#define __syscall_clobber "r11","rcx","memory"
+#define __syscall "syscall"
+
+#define __syscall_return(type, res) \
+do { \
+ if ((unsigned long)(res) >= (unsigned long)(-127)) { \
+ errno = -(res); \
+ res = -1; \
+ } \
+ return (type) (res); \
+} while (0)
+#define _syscall2(type,name,type1,arg1,type2,arg2) \
+type name(type1 arg1,type2 arg2) \
+{ \
+long __res; \
+__asm__ volatile (__syscall \
+ : "=a" (__res) \
+ : "0" (__NR_##name),"D" ((long)(arg1)),"S" ((long)(arg2)) : __syscall_clobber ); \
+__syscall_return(type,__res); \
+}
+
+#define _syscall3(type,name,type1,arg1,type2,arg2,type3,arg3) \
+type name(type1 arg1,type2 arg2,type3 arg3) \
+{ \
+long __res; \
+__asm__ volatile (__syscall \
+ : "=a" (__res) \
+ : "0" (__NR_##name),"D" ((long)(arg1)),"S" ((long)(arg2)), \
+ "d" ((long)(arg3)) : __syscall_clobber); \
+__syscall_return(type,__res); \
+}
+#endif
+
// int mlock(const void *addr, size_t len);
_syscall2(int, mlock, const void *, addr, size_t, len )
// int munlock(const void *addr, size_t len);
@@ -4341,24 +4406,6 @@
#endif
}

-/** \brief Freeze the thread if kernel requested so because of going to suspend
- *
- * \return Nonzero if freeze has been performed, zero otherwise
- *
- */
-unsigned int kas_try_to_freeze(void)
-{
-#if LINUX_VERSION_CODE <= KERNEL_VERSION(2,6,10)
- return 0;
-#else
-#if LINUX_VERSION_CODE <= KERNEL_VERSION(2,6,12)
- return try_to_freeze(PF_FREEZE);
-#else
- return try_to_freeze();
-#endif
-#endif
-}
-
/** \brief Storage for execution level(s) */
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)
/* SMP support for 2.6.0 and higher */
@@ -4985,28 +5032,13 @@
unsigned int ret = 0;
kasSlabCache_t* slabcache_obj = (kasSlabCache_t*)hSlabCache;

- DBG_ENTER("0x%08X", hSlabCache);
-
- if (!(slabcache_obj->cache))
- {
- DBG_ERROR("slab object '%s' is not initialized");
- DBG_LEAVE("0");
- return 0;
- }
-
- DBG_TRACE("destroying slab object '%s'", slabcache_obj->name);
-
- if (kmem_cache_destroy(slabcache_obj->cache) == 0)
+ if (slabcache_obj->cache)
{
- ret = 1;
+ kmem_cache_destroy(slabcache_obj->cache);
slabcache_obj->cache = NULL;
- }
- else
- {
- DBG_ERROR("destroying failed");
+ ret = 1;
}

- DBG_LEAVE("%d", ret);
return ret;
}

@@ -5190,6 +5222,24 @@
return 1;
}

+/** \brief Freeze the thread if kernel requested so because of going to suspend
+ *
+ * \return Nonzero if freeze has been performed, zero otherwise
+ *
+ */
+unsigned int kas_try_to_freeze(void)
+{
+#if LINUX_VERSION_CODE <= KERNEL_VERSION(2,6,10)
+ return 0;
+#else
+#if LINUX_VERSION_CODE <= KERNEL_VERSION(2,6,12)
+ return try_to_freeze(PF_FREEZE);
+#else
+ return try_to_freeze();
+#endif
+#endif
+}
+
/** \brief Wait for the event
*
* If event is already signalled, return right away.

Well not quite SuSE

I want to stress that this is not only a openSuSE problem and *I think* it is another change in mainstream the kernel, just as 2.6.12 upset a few drivers.
I say this as I have read reports of Fedora Core 7 Test{2,3} having trouble with the same config, 64bit, 2.6.21-rc* and fglrx(8.35.5).

I personally think NO DISTRO should hack the kernel. I do not object to building say AppControl as a module, this seems ok to me but why does the kernel have to be altered from Vanilla? Most changes are simply just config (or should be).
If they want to backport fixes or experimental then thats their opinion, I either disagree or back em.

I always remember the Mandrake 9.1 physically damaging some optical drives. This is an example of what imho happens when ditro's go it alone on performance issues.

What has seriously annoyed me was a SuSE developer fixed an issue with the acpi error with my laptop, this was back with 2.6.18 and it has taken for 2.6.21 with this fix becoming vanilla for SuSE to build it into their kernel.

I have been wanting to go Gentoo, but as of now if I do I would either get a melted laptop or a 32bit system on my 64bit laptop. I could disable acpi (like most sane people) but I lost my Bios password so I would have to dismantle a laptop & remove battery or pay for ti to be done for me. I wouldn't mind but I have to remove everything but my processor to get to my battery.

And to be even more honest as soon as CLFS is more stable I will be building my own as close to vanilla/minimalist system as possible.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

digiKam 7.7.0 is released

After three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release. Read more

Dilution and Misuse of the "Linux" Brand

Samsung, Red Hat to Work on Linux Drivers for Future Tech

The metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world. Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility. Read more

today's howtos

  • How to install go1.19beta on Ubuntu 22.04 – NextGenTips

    In this tutorial, we are going to explore how to install go on Ubuntu 22.04 Golang is an open-source programming language that is easy to learn and use. It is built-in concurrency and has a robust standard library. It is reliable, builds fast, and efficient software that scales fast. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel-type systems enable flexible and modular program constructions. Go compiles quickly to machine code and has the convenience of garbage collection and the power of run-time reflection. In this guide, we are going to learn how to install golang 1.19beta on Ubuntu 22.04. Go 1.19beta1 is not yet released. There is so much work in progress with all the documentation.

  • molecule test: failed to connect to bus in systemd container - openQA bites

    Ansible Molecule is a project to help you test your ansible roles. I’m using molecule for automatically testing the ansible roles of geekoops.

  • How To Install MongoDB on AlmaLinux 9 - idroot

    In this tutorial, we will show you how to install MongoDB on AlmaLinux 9. For those of you who didn’t know, MongoDB is a high-performance, highly scalable document-oriented NoSQL database. Unlike in SQL databases where data is stored in rows and columns inside tables, in MongoDB, data is structured in JSON-like format inside records which are referred to as documents. The open-source attribute of MongoDB as a database software makes it an ideal candidate for almost any database-related project. This article assumes you have at least basic knowledge of Linux, know how to use the shell, and most importantly, you host your site on your own VPS. The installation is quite simple and assumes you are running in the root account, if not you may need to add ‘sudo‘ to the commands to get root privileges. I will show you the step-by-step installation of the MongoDB NoSQL database on AlmaLinux 9. You can follow the same instructions for CentOS and Rocky Linux.

  • An introduction (and how-to) to Plugin Loader for the Steam Deck. - Invidious
  • Self-host a Ghost Blog With Traefik

    Ghost is a very popular open-source content management system. Started as an alternative to WordPress and it went on to become an alternative to Substack by focusing on membership and newsletter. The creators of Ghost offer managed Pro hosting but it may not fit everyone's budget. Alternatively, you can self-host it on your own cloud servers. On Linux handbook, we already have a guide on deploying Ghost with Docker in a reverse proxy setup. Instead of Ngnix reverse proxy, you can also use another software called Traefik with Docker. It is a popular open-source cloud-native application proxy, API Gateway, Edge-router, and more. I use Traefik to secure my websites using an SSL certificate obtained from Let's Encrypt. Once deployed, Traefik can automatically manage your certificates and their renewals. In this tutorial, I'll share the necessary steps for deploying a Ghost blog with Docker and Traefik.