Language Selection

English French German Italian Portuguese Spanish

Battle of the Titans: Mandriva 2008 vs openSUSE 10.3

Filed under

I've followed development of openSUSE and Mandriva fairly closely over the years, albeit a bit closer of openSUSE. I write about how nice they both are. I pick out the new features and test basic functionality. I see what's included and what makes up the base system. I like them both. But a visitor and contributor here at tuxmachines asked which would be better for his laptop and that gave me the idea to compare these large multi-CD Titans of Linux development.

In the blue corner weighing in at 4.3 GB, Mandriva 2008.0. In the green corner weighing in at 4.2 GB, openSUSE 10.3.


Both have a pretty graphical installer that walks the user through configuration by asking for user input in easy to understand / easy to answer formats. Both have advanced options available for those with more individualized needs. Both offer differing levels of user input for package selection either by main desktop, area selections, or individual packages. They both take roughly the same time to install. Both install a bootloader of your choice while detecting most other systems on your machine. In all these areas, I'm going to declare a tie.

Mandriva has a wonderful graphic partitioner. It lays out the hard drives in an image to represent the size, type, and placement of each partition in differing colors for each filesystem type. Options and choices are input from the same screen so you can always refer back to what's there. This is great for new users and the experienced alike. openSUSE's partitioner is text listing of the partitions in tree form. The edit/create/other buttons are at the bottom, and editing or creating a partition opens another window. Hands down, Mandriva's partitioner wins this round.

Both offer excellent hardware detection and auto-configuration and both have a summary screen for user changes. Both detect and correctly set-up all the same hardware on my test system and neither can set up my Windows dependent wireless ethernet chip. Mandriva does offer to use Ndiswrapper and allows for graphical navigation to the driver on my Windows partition. It doesn't work for me this release, but I think it'd work for some others. If your device is detected, both offer a convenient wizard for setting up the options. It's close here, but Mandriva takes it because of the wizard that includes the Ndiswrapper choice.

So Mandriva is the winner of the installation phase.

Winner: Mandriva

Curb Appeal

This area is going to be highly subjective. Both openSUSE and Mandriva appear to spend a lot of time and effort to make their operating system pretty to the eye. Both have lovely customized Grub screens, silent splashes, desktop splashes, nice icons, customized panels and menus, and lovely Wallpapers. openSUSE's tend to be a bit more understated while Mandriva's offer a bit more flash. Again, subjective, but I think Mandriva is just a tad prettier than openSUSE.

Winner: Mandriva

Installed Software

openSUSE 10.3 was released a few weeks before Mandriva 2008.0, so Mandriva might have a bit of an unfair advantage when considering the versions of components used. Also, it's a misnomer to assume the latest is always the greatest, but generally we tend to feel that way.

Both offer KDE and GNOME as the main desktops while offering to install some of the smaller choices. Both have software for all the tasks commonly accomplished with computers. But let's compare a few version numbers:

openSUSE 10.3 Mandriva 2008.0
2.40 (rc2)

As you can see, there isn't a whole lot of difference in software offerings. Mandriva offers the newer GIMP and Pidgin, but then makes a serious faux pas sending out 2.2.11. The updates to it were for security vulnerabilities and it probably should have been updated. So, I'm going to say openSUSE takes this one.

Winner: openSUSE

Software Management

Both Mandriva and OpenSUSE offer a graphical software manager and a seperate online update with system tray applet. Although the same functionality exists between the two, Mandriva's software manager has a cleaner, easier-to-use interface. It seems openSUSE's interface is more cluttered and busy, and takes a bit of investigating to reach the same level of comfort and ease found in Mandriva's. In addition, I prefer the commandline functionality of urpmi to that of zypper. Both the online updates go out and fetch a mirror for you. Both show the updates and allow the user to decide if to apply them or not. As far as the updater, it's a tie. But, for me at least, I like Mandriva's software management system better.

Winner: Mandriva

Hardware Support

Again, the two contenders are almost equally competent in this area. For me, both offered my preferred screen resolution by default using "nv," both configured my touchpad and add-on mouse correctly, both configured my sound, and offered to mount removable media in KDE and just mounted them in GNOME. Both will allow me to set up my wireless chip using Ndiswrapper at the commandline. The only difference I found was in the area of laptop hibernation features. Both had CPU scaling out of the box, but neither could suspend to ram. Only Mandriva could suspend to disk and wake up properly. (Mandriva Power Pack could do both). So, only by a hair does Mandriva win this round.

Winner: Mandriva


I always kinda hate to talk about stability in a distro. Loading a distro and using it for a few hours or even a few days to open the apps, test a few file formats support, and surf the internet some doesn't really tell the tale. One really needs to use a distro for an extended period of time for everything they do to get an accurate picture. I try to always qualify my stability reports with something like "for the time I tested" or "the small amount I tested." So, for the small amount of testing in these distros, a few days of light tasks for each, I found them to be equally stable.

Winner: Neither (tie)


One of the new features of openSUSE was a faster boot process. But in tests here, I didn't find it any faster than previous versions really, it was always fast here. It seems both distros are running fairly close on this race as well. Let's look at some numbers in seconds:

openSUSE 10.3 Mandriva 2008.0
Boot up
Shut down

As you can see, the numbers are pretty close. openSUSE seems to edge Mandriva out of a few seconds here and there, but really drops the ball with GNOME. I tested this several times, including rebooting. I don't know if this GNOME figure is universal or just me. Assuming it's not an anomaly, openSUSE still wins by my unscientific method of adding up how long it takes to get to each desktop with the above listed apps open and dividing by two. openSUSE scored a total of 65 seconds and Mandriva scored a total of 77 seconds.

Winner: openSUSE

Overall Winner

In our little just-for-fun comparison, we the judges find that Mandriva wins by 4 categories to 2. But to the original question the answer would be to go buy the Mandriva Power Pack2 or try PCLOS or ALT Linux in which advanced power saving feature do work out of the box. Also, YMMV.

However, don't forget that both openSUSE and Mandriva are both nice distros. This little article is highly subjective and you may not agree. That's okay. I love them both.

Winner: Mandriva 2008.0

UPDATE 1: Adam Williamson, of Mandriva, has written to inform users that their version of has had update backports to close any known vulnerabilities. More information available at Beranger's Blog. Fri, 10/19/2007 - 17:38

UPDATE 2: Or if you have an NVIDIA chip, install the NVIDIA proprietary graphic drivers from Mandriva's non-free repository. Suspend to disk will work with the NVIDIA drivers installed. Users of other graphic chips may have the desired results out of the box. Sat, 10/20/2007 - 00:18

Well, OpenSUSE 10.3 didn't

Well, OpenSUSE 10.3 didn't even install on a VirtualBox Disk.
Among all distros i have tested so far on this environment, this is really the only one that has failed to install.

Starting from Susan's Mandriva vs. openSUSE...

Susan's comparative review Battle of the Titans: Mandriva 2008 vs openSUSE 10.3 is not perfect, but not that bad either. I would have preferred some numerical values, and a final score for each of them. But anyway...

Anyway, the sad part is an unexpected secrecy with Mandriva: try a search for and you will get a blunt:

You are not authorized to access bug #33759.


More Here

There no hidden bug and the bug has been fixed


[root@info1 network-scripts]# rpm -q --changelog | grep CVE-2007-2834
- Added patch Closes: #33824

[root@info1 network-scripts]# rpm -q

So Mandriva package is not vulnerable and the bug report is accessible, it's #33824 :

Close the World, Open the Net : security

As Fabrice noted, the package in Mandriva Linux 2008 has all security fixes from 2.3.0 backported. It is not vulnerable to any known security issue.
Adam Williamson
Community manager | Newsletter editor | Bugmaster | Proofreader | Packager

Suspend / resume

There's no intentional reason Powerpack would work for suspend / resume on your system but Free / One would not. It's not a feature we've disabled in Free / One, or anything. I suspect it comes down to some kind of incidental installation detail, it might be hard to figure out what, though. I wouldn't expect this to be something consistent (i.e. it's not like suspend will *never* work on Free / One, but will always work on Powerpack).
Adam Williamson
Community manager | Newsletter editor | Bugmaster | Proofreader | Packager

re: Suspend / resume

Oh no one thinks, I wasn't trying to imply, it was intentional. The only obvious difference in my Power Pack and Free installs I can think of is some of the "extra" apps and the NVIDIA drivers. But otherwise, I chose the same categories under 'Custom Install' and turned off the same services (iptables, shorewall, and netfs).

OH, another difference is that the Power Pack's bootloader is installed on the MBR and Free's is on the / partition chainloaded. But both have the "resume" parameter defined in the kernel appends.

I found it a head scratcher too.

I was a bit surprised it was broken openSUSE as well. It always worked on it before, but sure enough, on the GM install it was inoperative (for me anyway).


It could potentially be the video driver. You could try installing the NVIDIA driver on the Free install (using the official repositories) and see if it works then. That's the only thing that springs to mind.
Adam Williamson
Community manager | Newsletter editor | Bugmaster | Proofreader | Packager

re: possibly

Yep that was it. It does work now using the NVIDIA proprietary graphic drives from the non-free sources.

I had thought of that, but then I thought I recalled suspend working with "nv" in some other distros.

okay, bingo. do you

okay, bingo. Smile do you remember on what distro suspend worked with nv, and what version of nv that distro had, by any chance?
Adam Williamson
Community manager | Newsletter editor | Bugmaster | Proofreader | Packager

Bad customer service

I'm posting here because that's the only way I can get someone from Mandriva to pay attention I guess. Mandriva *never* replied to any of my customer tickets (and yes [yawn] I was entitled to support).

Bought 2008 Powerpack DVD. Waited 10 days. Received an e-mail from Mandriva saying that 'their supplier' cannot send within (another) 10 days. Ooooh right - I forgot that we're dealing with Mandriva here. They took my money right away (about 50 euros) and then they SIT on it for 20 days (and maybe more) before shipping it. Not being able to burn a DVD? With respect: BS. I don't care - or need to care - about your internal problems.

So this reminded me instantly of my experiences when buying two earlier Mandriva versions on DVD. Both instances were extremely irritating at the time. So I decided to go with SuSE from then on, but seeing the good reviews I decided to try again. Third time now.

Just needed to say this.

Oh - and do something about the utterly confusing website.

Be happy with my money.

Suspend to disk/Suspend to RAM on openSUSE 10.3

My CompTIA certification book tells me that a computer with good ACPI support will have power management settings in the BIOS itself. My Presario V2000 laptop (with its ATI Radeon Mobility 200M chipset) doesn't — one drawback of buying an inexpensive laptop, I suppose. (In other words, without hardware support, suspend has to be done in software.) So, how well this works seems to depend a lot on your specific computer model's hardware.

On openSUSE 10.3, suspend-to-disk worked out of the box, with the ATI proprietary driver ("fglrx") installed, complete with a cute "going to sleep" graphic.

Suspend-to-RAM was another matter entirely. The openSUSE wiki has a few articles about it, including ACPI Suspend debugging (a good place to start); S2ram, and pm-utils.

In order to get suspend-to-ram working on my laptop, I had to:

  • delete the ATI ("fglrx") driver entirely and go back to the "radeon" driver — not just disable "fglrx" in xorg.conf, but completely remove it from the system;
  • set "vga=0" as a kernel parameter in /boot/grub/menu.lst. In other words, no more splashy; no nice 1024x768 framebuffer; just plain 80x25 text scrolling by at boot time;
  • find out the s2ram parameters that work for my laptop — "s2ram -f -a 1" in my case;
  • and add them to the "S2RAM_OPTS=" line in /usr/lib/pm-utils/defaults.

(Actually, you're supposed to make up your own configuration file in /etc/pm/config.d, because changes you make to /usr/lib/pm-utils/defaults could get overwritten by a package upgrade. But the documentation wasn't very clear about how to do that, so I'll play with it later.)

Now suspend-to-RAM works fine, at the expense of video acceleration (no great loss).

On another note, it's interesting how much openSUSE/Novell software's gone into common usage. Just off the top of my head, the grub-gfxmenu code (that enables animations), the "kickoff" KDE menu, and the Beagle desktop indexer all came from openSUSE. Debian uses openSUSE's S2ram code in its "uswsusp" package.

Comment viewing options

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

More in Tux Machines

How to build something ‘useful’ with a Raspberry Pi

In honor of Pi Day, Chaim Gartenberg and I cooked up a tiny little Raspberry Pi project for yesterday’s episode of Circuit Breaker Live. We started with a simple concept: a button that says “Why?” when you press it, in honor of our favorite podcast. So we knew we’d need a button, some sound files, a little bit of Python code, and, of course, a Raspberry Pi. A new Pi is $35, but we found an old Raspberry Pi 2 in my desk drawer, which was up to the task. (Newer Pis have built-in Wi-Fi and faster processors, but for our simple button project we didn’t need internet or extra horsepower.) Read more

Wine 3.4

  • Wine Announcement
    The Wine development release 3.4 is now available.
  • Wine 3.4 Release Continues With Vulkan Upbringing, Some Wine-Staging Patches
    The latest bi-weekly release of Wine is now available for running your favorite or necessary Windows programs/games on Linux and macOS. Wine 3.4 is this latest release and it's significant for continuing to land the "WineVulkan" code. This does include the latest Wine Vulkan patches as of yesterday including the first bits of apps/games working and integration with the X11 driver.

Graphics: AMDGPU, Mesa 17.3.7, RADV

  • Linux 4.17 To Enable AMDGPU DC By Default For All Supported GPUs
    Since the introduction of the AMDGPU DC display code (formerly known as DAL) in Linux 4.15, this modern display stack has just been enabled by default for newer Radeon Vega and Raven Ridge devices. With Linux 4.17 that is changing with AMDGPU DC being enabled by default across the board for supported GPUs. Building off the earlier DRM-Next material for Linux 4.17, Alex Deucher minutes ago sent in another round of feature updates for targeting this next kernel cycle. This latest batch has continued code refactoring around PowerPlay, support for fetching the video RAM type from the video BIOS, allowing the TTM memory manager to drop its backing store when not needed, DC bandwidth calculation updates, enabling DC backlight control for pre-DCE11 GPUs, various display code fixes, and other bug fixes.
  • AMDGPU / ATI 18.0.1 X.Org DDX Driver Releases, Fixes Infinite Loop & Crashes
    Michel Dänzer of AMD issued bug-fix updates on Thursday for the xf86-video-ati and xf86-video-amdgpu DDX drivers. Just two weeks after the AMDGPU 18.0 X.Org driver release as the first version under their new year-based versioning scheme, the 18.0.1 bug-fix release is out. The xf86-video-amdgpu 18.0.1 DDX update fixes a potential infinite loop after a xorg-server reset in some configurations, Xorg crashing when multiple primary screens are configured, and using the TearFree feature could trigger Pixman library debugging spew.
  • Mesa 17.3.7 Nearing Release With 50+ Changes
    While waiting for Mesa 18.0, the Mesa 17.3.7 point release will soon hit stable users of this open-source, user-space graphics stack.
  • RADV Patches Are Closer For Sub-Group Capabilities
    Daniel Schürmann continues hacking on the sub-group patch-set for the RADV Vulkan driver to expose this important feature of the recent Vulkan 1.1 release.

Server: Containers, Kubernetes, Varnish 6.0, HHVM 3.25.0, 3.24.4, and 3.21.8

  • Container Isolation Gone Wrong
    One of the main advantages of embracing containers is "lightweight virtualization." Since each container is just a thin layer around the containerized processes, the user gains enormous efficiencies, for example by increasing the container density per host, or by spinning containers up and down at a very fast pace. However, as the troubleshooting story in the article will show, this lightweight virtualization comes at the cost of sharing the underlying kernel among all containers, and in some circumstances, this can lead to surprising and undesirable effects that container users typically don't think about. This troubleshooting tale is rather involved. I've started from the basics and worked up to the more complex material in the hope that readers at all levels can get value out of it.
  • Introducing Agones: Open-source, multiplayer, dedicated game-server hosting built on Kubernetes
    In the world of distributed systems, hosting and scaling dedicated game servers for online, multiplayer games presents some unique challenges. And while the game development industry has created a myriad of proprietary solutions, Kubernetes has emerged as the de facto open-source, common standard for building complex workloads and distributed systems across multiple clouds and bare metal servers. So today, we’re excited to announce Agones (Greek for "contest" or "gathering"), a new open-source project that uses Kubernetes to host and scale dedicated game servers.
  • Varnish 6.0 Released
    It's that time of March again, and Varnish 6.0.0 is here.
  • HHVM 3.25.0, 3.24.4, and 3.21.8
    HHVM 3.25 is released! This release contains new features, bug fixes, performance improvements, and supporting work for future improvements. Packages have been published in the usual places.
  • HHVM 3.25 Released, Now Defaults To PHP7 Mode
    Facebook developers working on the HHVM Hack/PHP language stack have released version 3.25 of the HipHop Virtual Machine. HHVM 3.25's PHP support now defaults to PHP7 rather than the PHP5 mode, which is now in an unsupported state. As expressed previously, Facebook will be focusing more on their Hack language support than PHP7 thanks to all the upstream improvements with PHP 7 especially on the performance front. But the large compatibility with PHP7 will happen to continue at least for the time being. With HHVM 3.25 includes support for PHP7 Throwable/Error/Exception hierarchy, changes to visibility modifiers, and other compatibility work.