Pour des informations détaillées sur l'installation, voir Section 3.1, « Documentation openSUSE ».

CHECKIT:12.3

Directly after installation, NetworkManager is not started automatically and thus WiFi cannot be configured. To enable networking (WiFi), reboot the machine once manually.

CHECKIT:12.3

Default and new users are no longer added to the video group automatically. But the proprietary NVIDIA driver requires users to have access to /dev/nvidia* devices.

Because the NVIDIA driver does not use the usual kernel methods that allow to install ACLs on the device nodes, users have to be added manually to the video group; as root call (replace $USER with the actual username):

usermod -a -G video $USER

Find the documentation in /usr/share/doc/manual/opensuse-manuals_$LANG after installing the package opensuse-startup_$LANG, or online on http://doc.opensuse.org.

The following YaST modules were obsolete and rarely used these days:

The main reason for dropping was to decrease the maintenance effort and better focus on other more used modules.

CHECKIT:12.3

Prior to installing openSUSE on a system that boots using UEFI (Unified Extensible Firmware Interface) you are urgently advised to check for any firmware updates the hardware vendor recommends and, if available, to install such an update. A pre-installed Windows 8 is a strong indication that your system boots using UEFI.

Background: Some UEFI firmware has bugs that cause it to break if too much data gets written to the UEFI storage area. Nobody really knows how much "too much" is, though. openSUSE minimizes the risk by not writing more than the bare minimum required to boot the OS. The minimum means telling the UEFI firmware about the location of the openSUSE boot loader. Upstream Linux Kernel features that use the UEFI storage area for storing boot and crash information (pstore) have been disabled by default. Nevertheless it is recommended to install any firmware updates the hardware vendor recommends.

CHECKIT:12.3

Ceci n'affecte que les machines en mode UEFI avec le démarrage sécurisé (secure boot) activé.

YaST does not automatically detect if the machine has secure boot enabled and will therefore install an unsigned bootloader by default. But the unsigned bootloader will not be accepted by the firmware. To have a signed bootloader installed the option "Enable Secure Boot" has to be manually enabled.

CHECKIT:12.3

Ceci n'affecte que les machines en mode UEFI.

When using the installer on the live medium, YaST does not detect UEFI mode and therefore installs the legacy bootloader. This results in a not bootable system. The bootloader has to be switched from grub2 to grub2-efi manually.

CHECKIT:12.3

This only affects installations in UEFI mode.

In the partitioning proposal when checking the option to use LVM (which is required for full disk encryption) YaST does not create a separate /boot partition. That means kernel and initrd end up in the (potentially encrypted) LVM container, inaccessible to the boot loader. To get full disk encryption when using UEFI, partitioning has to be done manually.

CHECKIT:12.3

By default, you use the YaST Network Settings dialog (yast2 network) to activate NetworkManager. If you want to activate NetworkManager, proceed as follows.

The NETWORKMANAGER sysconfig variable in /etc/sysconfig/network/config to activate NetworkManager has been replaced with a systemd network.service alias link, which will be created with the

systemctl enable  NetworkManager.service

command. It causes the creation of a network.service alias link pointing to the NetworkManager.service, and thus deactivates the /etc/init.d/network script. The command

systemctl -p Id show network.service

allows to query the currently selected network service.

Pour activer NetworkManager, utilisez :

Pour désactiver NetworkManager, utilisez :

To query the currently selected service, use:

systemctl -p Id show     network.service

It returns "Id=NetworkManager.service" if the NetworkManager service is enabled, otherwise "Id=network.service" and /etc/init.d/network is acting as the network service.

CHECKIT:12.3

The SYSLOG_DAEMON variable has been removed. Previously, it was used to select the syslog daemon. Starting with openSUSE 12.3, only one syslog implementation can be installed at a time on a system and will be selected automatically for usage.

Pour plus de détails, voir la page de manuel syslog(8).

CHECKIT:12.3

Depuis openSUSE 11.3, KMS (Kernel Mode Setting) est activé par défaut pour les cartes graphiques Intel, ATI et NVIDIA. Si vous rencontrez des problèmes avec le support de KMS par les pilotes (intel, radeon, nouveau), désactivez KMS en ajoutant nomodeset à la ligne de commande d'amorçage du noyau. Pour définir ceci de manière permanente, avec Grub2,le chargeur d'amorçage par défaut, ajoutez-le à la ligne de chargement du noyau GRUB_CMDLINE_LINUX_DEFAULT dans le fichier texte /etc/default/grub en tant que root et en exécutant la command

sudo /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg

pour que les changements prennent effet. Sinon, pour Grub Legacy, ajoutez-le à la ligne de commande du noyau dans /boot/grub/menu.lst, également en tant que root. Cette option permet de s'assurer que le module du noyau (intel, radeon, nvidia) est chargé avec modeset=0 dans initrd, c'est à dire que KMS est désactivé.

Dans les rares cas où le chargement du module DRM depuis initrd pose problème, sans relation avec KMS, il est même possible de désactiver complètement le chargement du module DRM dans initrd. Pour cela, définissez la variable sysconfig NO_KMS_IN_INITRD à yes via YaST, ce qui recrée ensuite l'initrd. Redémarrez votre machine.

Sur Intel sans KMS, le serveur X se replie vers le pilote fbdev (le pilote intel ne supporte que KMS) ; alternativement, il existe aussi le pilote "intellegacy" (paquet xorg-x11-driver-video-intel-legacy) qui supporte toujours UMS (User Mode Setting). Pour l'utiliser, éditez /etc/X11/xorg.conf.d/50-device.conf et changez la valeur de driver à intellegacy.

Sur ATI pour les cartes graphiques actuelles, le serveur X se rabat sur radeonhd. Sur NVIDIA sans KMS, le pilote nv est utilisé (le pilote nouveau ne supporte que KMS). Notez que les cartes graphiques ATI et NVIDIA les plus récentes basculeront sur fbdev si vous spécifiez le paramètre d'amorçage du noyau nomodeset.

CHECKIT:12.3

Avec openSUSE 12.3, SuSEconfig.postfix a été renommé en /usr/sbin/config.postfix. Si vous paramétrer les variables sysconfig dans /etc/sysconfig/postfix ou /etc/sysconfig/mail, vous devez exécuter manuellement /usr/sbin/config.postfix en tant que root.

CHECKIT:12.3

In Gnome 3.6 use the following workaround to set Shift or Ctrl+Shift as shortcut keys for input source selection:

This is also being tracked in the upstream bug report https://bugzilla.gnome.org/show_bug.cgi?id=689839.

The new default for xinetd changes the default target for logging from /var/log/xinetd.log to the system log. This means all messages from xinetd will appear in a system log as a facility daemon and log level info.

If you want to switch back the the old way, find a proper snippet in /etc/xinetd.conf. The template for the logrotate script for xinetd.log can be found in /usr/share/doc/packages/xinetd/logrotate.

Apache 2.4 features various changes in the configuration files. For more information about upgrading from a previous version, see http://httpd.apache.org/docs/2.4/upgrading.html.

The tomcat startup scripts doe no longer write the output to /var/log/tomcat/catalina.out. All messages are now redirected to the system log via tomcat.service (tomcat-jsvc.service) and log level info.

If upgrading from a previous release to openSUSE 13.1 old cache files may no longer work. In this case removing ~/.cache/darktable/mipmaps is necessary.