From Mandriva Community Wiki

Jump to: navigation, search

List of errata related to Mandriva Linux 2006


Preliminary note

Other errata pages are also available for older versions:


Broken ataraid

Installation activates a software raid device whereas none exists or it is not wanted. The install boot option "nodmraid" should ensure it is discarded, but it's broken. Use this instead (how to use Installer Patches)

Existing linux software raid is badly detected, having size 0

Use this (how to use Installer Patches)

BIOS Software RAID is not enabled (dmraid)

If your BIOS software RAID is not enabled, and you have things like:

* got: /dev/sda: "sil" and "nvidia" formats discovered (using nvidia)!
* got: /dev/sdb: "sil" and "nvidia" formats discovered (using nvidia)!

in your log (ctrl-alt-F3 during install), use this (how to use Installer Patches)

See Image:bug_small.png Bug #19654

PCMCIA Card in AMD64 Laptop -WorkAround-

  • Tested with Mandriva 2006 x86_64 : Kernel 2.6.12-12mdk

There is a bad memory call for cardbus in notebooks with AMD64 CPU's and nVidia Nforce3 Chipset. Review your hardware and if you found something like this: (Edited)

YourPrompt%> lspci -v
00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2) (prog-if 00 [Normal decode])
   Flags: bus master, 66Mhz, fast devsel, latency 0
   Bus: primary=00, secondary=02, subordinate=04, sec-latency=128
   I/O behind bridge: 0000b000-0000dfff
   Memory behind bridge: f8a00000-feafffff

you must follow this steps:

  1. Eject the pcmcia card: carctl eject
  2. Set your correct subordinate bus: setpci 0:a.0 SUBORDINATE_BUS 0x0A
  3. Restart pcmcia service: service pcmcia restart
  4. insert pcmcia card: cardctl insert
  5. enjoy your card.

For more information about this problem see also Bugzilla Kernel 2944.

boot.iso and some recent hardware

The boot.iso doesn't contain the same kernel as the first CD of MDV2006.0, it only contains the older 2.6.8. This boot.iso doesn't have this issue. The boot.iso in the Community tree on the public mirrors - /devel/2006.0 - has also been updated.

Upgrading from 10.1 to 2006 with urpmi

If you wish to upgrade from MandrakeLinux 10.1 to Mandriva Linux 2006 using urpmi (rather than the installer), there is a known bug caused by a glibc packaging error that must be avoided. Instead of simply running

urpmi --auto-select

to start the upgrade process, first run

urpmi glibc urpmi

then - once the upgrade of glibc and urpmi is complete - run

urpmi --auto-select

For more information about this problem see alsoImage:bug_small.png Bug #20268.


Athlon XP-M CPU frequency scaling issue

It has been reported that some systems with Athlon XP-M CPUs do not work correctly with frequency scaling (a power-saving technique often used in laptops). In particular, the lowest possible frequency is incorrectly reported by the kernel as a much higher value than it should be, limiting the effectiveness of scaling. If you have such a CPU and you have configured frequency scaling correctly but the system still does not reduce the frequency as far as it ought to compared to other operating systems, you may attempt to resolve the problem by adding this line to the file /etc/modprobe.conf :

options powernow-k7 acpi_force=1

You will need to remove and reload the powernow-k7 module after making this change, or reboot the system. For more information on this issue, see Image:bug_small.png Bug #18746.

Issue with networking/firewire on the Zepto Znote 6515WD and possibly other Zepto/Compal laptops

Using these laptops you will get "Disabling IRQ# 11" (or similar) resulting in broken networking.

When installing press F1 when the first Mandriva logo appears then type this on the resulting commandline:

linux nofirewire

The installer should now work.

After installation this can be fixed by supplying the nofirewire option to the kernel like this:

linux nofirewire

on the LILO/GRUB commandline, or by disabling the ieee1394 module in /etc/modprobe.conf by adding:

alias ieee1394 off
blacklist ieee1394

to it. Alternatively you can add "nofirewire" to the append="" line in /etc/lilo.conf.

This will disable firewire, but otherwise the laptop will work perfectly. This workaround is required both for normal use and for the installer.

The issue can be found as bug Image:bug_small.png Bug #18938 in the Mandriva bugzilla.

Power management functionality missing on various laptops (HP Omnibook, Pavilion, Toshiba Satellite and others)

A change in the Linux kernel between 2.6.9 and 2.6.10 meant that some laptops whose power management features were previously fully supported by the kernel (and thus in Mandriva Linux 2005, which used kernel 2.6.8) now need the third party 'omnibook' kernel module to be loaded to be fully supported. The main Mandriva kernel does not include this module, so owners of the affected laptop models may see a regression in power management functionality - specifically, battery level monitoring may not work, and the system may not power down correctly at the end of a session. In order to restore full functionality, please follow these steps.

1. Visit and follow the instructions to configure a 'contrib' software source. 2. Use urpmi or rpmdrake to install the and packages. 3. Edit the file /etc/modprobe.preload with a text editor (you must be root to edit the file) and add a new line:


4. Reboot the system and choose the 2612-12mm1 option on the boot menu.

You should now find that all power management functionality is restored. In future, you must always choose the 2612-12mm1 boot menu option. See Image:bug_small.png Bug #21957.


Turboprint incompatibility

If you are using the commercial printer driver suite Turboprint, version 1.92 and some older versions, you will probably not be able to print with Mandriva Linux 2006. This is caused by an incompatibility between Turboprint and the ESP Ghostscript 8.15.1rc4 shipped with our distribution (update to ESP Ghostscript 8.15.1 final will not fix the problem). The best solution is to update to version 1.93 of Turboprint which we have tested on Mandriva 2006 and it works perfectly. If you have a full license for any 1.x version, your key stays valid for 1.93.

If an update of Turboprint is not possible for your for some reason, the problem can easily be worked around without downloading and installing extra software. Edit the script /usr/lib/cups/filter/pstoturboprint, removing the part beginning with the line "# check if esp ghostscript ..." until the last non-empty line before "# put together first chunk...". You need to be logged in as root to be able to edit this file and do not forget to backup the file before editing it.

For more information about this problem see also Image:bug_small.png Bug #17682.

Canon LBP-810/1120 and some other printers do not get set up by printerdrake

Unfortunately, printerdrake has a bug which prevents some printer models from being set up by printerdrake. If the "Add Printer" wizard of printerdrake fails when configuring the printer, your printer is one of these models. In this case switch to Expert mode ("Options" menu in the main window of printerdrake/the printer screen of mcc) and do the printer setup again, there it will work correctly (See also %BUG{19524}%).

"printer-utils" package does not uninstall

The printer-utils package (2006-7mdk) shipped with Mandriva 2006 has a bug which prevents it from being uninstalled. If you want to uninstall it, open a terminal window, get root ("su -") and then execute the command rpm -e --noscripts printer-utils. See Image:bug_small.png Bug #19309.

New printing dialog in the GIMP

With the replacement of the former Gimp-Print by the new Gutenprint the printout quality on many printers (especially Epson inkjets) has improved and there are a lot more possibilities to adjust the output. This led also to a new printing dialog in the GIMP. This dialog provides the new adjustment options, but it also requires some configuration to get printing from the GIMP started.

Unfortunately, GIMP does not automatically get the information about the printer properties from the printing system, like or KDE applications do. So every printer to be printed on directly from the GIMP has to be set up explicitly.

To do so, open an arbitrary image file in the GIMP and choose "Print" in the image's "File" menu. In the printing dialog click "New Printer" (upper right, on the "Printer Settings" tab). Enter a name under which you want to set up your printer. It does not necessarily need to be the name of the print queue you want to use.

Click "Setup Printer" now. In the dialog choose your printer's manufacturer and model from the list. If it is not there, choose "Adobe" and "Postscript Level 2". If you have found your printer manufacturer and model, it is directly supported by Gutenprint and GIMP will use Gutenprint directly, controllable by the printing dialog. If you had to choose Adobe Postscript Level 2, Gutenprint does not support your printer, GIMP will send Postscript to the printing system and the printing system will use the driver which was chosen when the print queue was set up. If you are using Postscript Level 2, specify the printer's PPD file in the input field directly under the lists, the right PPD file is always /etc/cups/ppd/<name of your print queue>.ppd. In any case you should choose "Standard Command" and the name of the print queue on which you want to print. Then click OK.

Back in the printing dialog click "Save Settings" at the bottom, so that you can use these settings whenever you want later. Repeat the procedure if you also want to use other printers.

On the "Printer Settings" tab there are basic options, especially you should set paper size, paper tray, and image quality. On the "Output" tab you should click the big button and then in the dialog choose the image type, usually "Photograph". If you have set up yuor printer with Postscript Level 2 and miss some options, set appropriate defaults for your printer using printerdrake or the KDE Printing Manager.

Now you should be able to print your pictures.

See Image:bug_small.png Bug #19071.


Re-install Boot Loader bug

When choosing Re-install Boot Loader, one gets:

run_program can not output in /root/tmp/.drakx-stderr.1171 (mode '>')
lilo failed:  at /usr/lib/libDrakX/ line 1238, <STDIN> line1.

To workaround this:

  • choose Go to console
  • execute mkdir -p /root/tmp
  • exit the shell to get back to the rescue GUI menu
  • choose Re-install Boot Loader which will work.

Or use the rescue.iso which is available in =devel/community/i586/install/images= on the mirrors

High CPU usage by

If you have an ACPI-enabled system on which both acpid and are running, you may experience high CPU usage in the release version of Mandriva Linux 2006. This problem is triggered when the logrotate tool is called to compress and rotate the system logs, so it will happen at 4 a.m. if your system is on and cron or anacron is enabled, or at the first boot after 4 a.m. if anacron is enabled and your system was off at 4 a.m. If you experience the problem, you must restart either or the system in order to stop the high CPU usage. This problem will be fixed as soon as possible by an official update. As a workaround, you can turn off the acpid service, or stop logrotate from rotating the acpid log file by removing the file /etc/logrotate.d/acpid . See also Image:bug_small.png Bug #18847. 6.9 issues with free drivers

In order to support new hardware and new video cards, Mandriva now uses 6.9.

This version is rather new and several issues have been reported with ATI and NVidia graphical cards when using free nv and ati drivers. If you experience problems with drivers provided with, you can use one of the solutions below :

  • use the driver for your card provided with Mandriva Linux commercial versions (Mandriva club and purchased boxes)
  • download the driver from your manufacturer's website (follow the instructions on this site for installation)
  • use the VESA standard video driver available through XFDrake

See Image:bug_small.png Bug #17532, Image:bug_small.png Bug #17752, Image:bug_small.png Bug #17906 Image:bug_small.png Bug #17517 and Image:bug_small.png Bug #19084.

No VGA signal with ATI Radeon Mobility

When a video-projector or an external screen is plugged in a laptop's VGA output using an ATI card, no signal is received or the screen is only 640x480. The radeon man page gives the solution : some options should be added to the "Device" section of /etc/X11/xorg.conf. For instance, the following section gives a 1024x768@60Hz VGA output :

Section "Device"
   Identifier "device1"
   VendorName "ATI"
   BoardName "ATI Radeon (fglrx)"
   Driver "ati"
   Option "DPMS"
   Option "CRT2Position" "clone"
   Option "MonitorLayout" "LVDS, CRT"
   Option "CRT2HSync" "31.5-55"
   Option "CRT2VRefresh" "40-70"

See Image:bug_small.png Bug #19861.

Kicker crashes when logging out

Kicker (the KDE bar containing generally the K or "star" menu) is crashing at logout under certain conditions. This workaround might help, but some still see kicker crashing despite applying it :

  • right click on the K (or "star") menu in kicker
  • choose "panel menu" then "configure the panel"
  • go to the "Menus" tab
  • uncheck all optional menus

See Image:bug_small.png Bug #16300


Automatic connection to open wireless networks

When an open wireless network is detected, some drivers automatically associate to the network. This can get wrong because, in Mandriva 2006, the wireless interfaces are configured by default to automatically connect to a network when the driver has associated with it. This behavior often leads to corrupted DNS addresses (though the default route should be ok, since wired networks have higher priorities).

A solution is to disable Network hotplugging for wireless interfaces in the connection wizard. This will disable the ifplugd' daemon for the selected interface (this daemon allows to automatically connect to networks when they are detected). Thus, no automatic connection will be done to open networks. But it will still be possible to manually connect to wireless networks using the wireless utilities (net_applet and drakroam).

Wireless roaming with orinoco based wifi cards

Wireless roaming uses wpa_supplicant to configure the wireless network card. It seems that wpa_supplicant doesn't fully support all cards yet, for instance it doesn't set the encryption key for orinoco based wifi cards using orinoco_cs correctly. As a workaround for that, you can add a line to the configuration file for the wireless network to set the encryption key using the old method as described in Image:bug_small.png Bug #17975.

Ndiswrapper incompatibility with SMP kernel

Ndiswrapper does not currently work with SMP kernels. SMP (Symmetric Multi Processor) kernels are installed on machines with more than one processor as well as on machines with Intel CPUs supporting the Hyperthreading feature. Some modern laptops have these CPUs. You can check the kernel version by running uname -r in a console. If the kernel name includes 'smp', you won't be able to use ndiswrapper, used for wireless connections. If you are running an SMP kernel and you would like to use ndiswrapper, you should use the Software Installer (urpmi or rpmdrake) to install the standard kernel (without SMP in the name), then reboot and use this kernel from now on. You won't be able to use the hyperthreading capabilities of your machine, but that shouldn't degrade performance much. See Image:bug_small.png Bug #15400.

Browsing samba/netbios servers

It is not currently possible to find smb server when using the broadcast way if the service shorewall is started. So browsers doing it won't work because of the firewall. In order to allow browsing server in the LAN, you can stop the firewall, but you won't be protected anymore:

# service shorewall stop

Or allow incoming connections from the LAN to the port 139:

# iptables -I INPUT -i $LAN_INTERFACE_NAME -p udp -s $LAN_IP_ADDRESSES --sport 139 -m mport --dports 1024:65535 -j ACCEPT

The second option is better, but it is again possible to scan the box with this rule, from the LAN, by creating packets that are matching UDP sport=139, and 1024 < UDP dport < 65535, so scan can be attempted against UDP ports > 1024

Slow or unreliable DNS lookups because of IPv6 support

If DNS lookups often fail or report answers after a very long timeout only, the IPv6 support may be causing trouble. Under some circumstances, DNS resolvers take a long time to lookup the address using the IPv6 protocol, even if all interfaces use IPv4 only.

IPv6 support in enabled by default in Mandriva Linux 2006. To disable IPv6, add NETWORKING_IPV6=no in =/etc/sysconfig/network=, and reboot your computer so that all IPv6 modules get properly unloaded.

Various software

Kaffeine crashes on exit

This is a known Kaffeine bug. It may be replaced by Codeine (xine based) or Kmplayer (mplayer based) which are unaffected by this problem.

See Image:bug_small.png Bug #15805 and Image:bug_small.png Bug #16965.

Issues with Mozilla based software when set up by the installer

Mozilla-thunderbird, -firefox and nvu may not work if installed by drakx ( i.e. when the distribution is installed for the first time). It seems to be related to scripts used to generate mozilla internal databases, that do not work under certain circumstances triggered by the installer ( like no $HOME, etc ). See Image:bug_small.png Bug #17146 for more explanations.

For mozilla-thunderbird, one solution is to run as root the script:

# rpm -ql mozilla-thunderbird | grep rebuild /usr/lib/mozilla-thunderbird-1.0.6/
# /usr/lib/mozilla-thunderbird-1.0.6/

Perl setuid not working properly

The perl-suid package doesn't work correctly; /usr/bin/sperl5.8.7 is supposed to be installed with the set-uid bit set. To fix this, use the command:

# chmod 4711 /usr/bin/sperl5.8.7

filesharing not working properly

quick filesharing using right click and "share" in nautilus and konqueror might not work properly. You need to install "perl-suid" package and also do :

# chmod 4711 /usr/bin/sperl5.8.7

FileRunner crashing when showing large files

FileRunner is an X11 file management tool similar to Midnight Commander. It's part of the Mandriva distros.

When FileRunner is used to display a directory containing very large files (> 2 Gigabytes), it crashes or displays abnormal sizes. This is due to the fact that the file sizes are displayed as 32-bit signed ints instead of 64-bit longs. To fix this problem, edit (as root) the /usr/lib/FileRunner/fr file, which is a Tcl program. In that file, search and replace all instances of the string =%7d= with =%7ld=. There are 8 such instances.

The resulting lines look like:

lappend fl [format "%-26s %7ld %s %s %s -> %s " " [lindex $k 1]@" "[lindex $k 3]" "[GetTimeFromSecs [lindex $k 4]]"

Restart the FileRunner app. Problem fixed.

gnome-cd crashes.

See :

A workaround if you have Gnome 2.12 (club version) is to use totem instead. To do so, do the following:

  1. Install libcdio6-0.75-2mdk and gstreamer-cdio-0.8.11-4mdk: urpmi libcdio6-0.75-2mdk gstreamer-cdio-0.8.11-4mdk
  2. If totem is not installed, install it: urpmi totem
  3. Edit /etc/dynamic/user-scripts/audio_cd.script and replace the following line:
    launch gnome-cd --unique --play --device "$DEV"

with :

    launch totem --play --enqueue "$DEV"

inserted audio CDs will now be played automaticaly by totem.

Alternately, to have audio CDs played automatically by xmms, edit the /etc/dynamic/user-scripts/audio_cd.script and change the part

if under_gnome; then
   launch gnome-cd --unique --play --device "$DEV"


if under_gnome; then
  launch xmms $(grep $DEV /etc/fstab|cut -d' ' -f2)

The grep expression extracts the CDROM drive mountpoint from /etc/fstab. It assumes that fstab contains a line defining the CDROM mount point.

Frozen Bubble fails to run on x86-64

Frozen Bubble does not work as released in 2006.0 x86-64. To make it work, edit the file /usr/games/frozen-bubble and add the following line to it somewhere:

$FPATH = "/usr/share/games/frozen-bubble";

Gnucash fails to run on x86-64

Due to a bug in guile package for x86-64 (Image:bug_small.png Bug #19978), if gnucash is selected when installing Mandriva Linux 2006, it won't start. Installing gnucash after Mandriva Linux 2006 is installed won't trigger this bug. To correct this bug, run the following command as root :

urpme guile
urpmi gnucash
Personal tools