m (→GNOME: don't use the french version of the template) |
m (→Live images: fix layout) |
||
| Line 21: | Line 21: | ||
1) By default GNOME uses the Wayland display server. Wayland is still not fully mature, and may not work well on some hardware. Normally GNOME will automatically fall back to using the X.org display server if Wayland fails to start, but in some cases this fails to happen. If the GNOME desktop fails to launch after completing the initial language and locale selection, or if you experience display problems, you can try forcing GNOME to use the X.org display server by adding {{cmd|nowayland}} to the boot options in the initial boot menu (press {{keypress|e}} to edit the boot options). | 1) By default GNOME uses the Wayland display server. Wayland is still not fully mature, and may not work well on some hardware. Normally GNOME will automatically fall back to using the X.org display server if Wayland fails to start, but in some cases this fails to happen. If the GNOME desktop fails to launch after completing the initial language and locale selection, or if you experience display problems, you can try forcing GNOME to use the X.org display server by adding {{cmd|nowayland}} to the boot options in the initial boot menu (press {{keypress|e}} to edit the boot options). | ||
| − | |||
2) By default the NetworkManager service is enabled in place of the old network management services. You can use the drop-down menu accessible from the top right corner of the GNOME desktop to perform any necessary network configuration. For wired connections, the network is usually configured automatically and you don't need to do anything. For wireless networks, you will usually need to select an access point and, if it is password-protected, enter the password. Network configuration via the MCC/drakconnect should also work in most cases. | 2) By default the NetworkManager service is enabled in place of the old network management services. You can use the drop-down menu accessible from the top right corner of the GNOME desktop to perform any necessary network configuration. For wired connections, the network is usually configured automatically and you don't need to do anything. For wireless networks, you will usually need to select an access point and, if it is password-protected, enter the password. Network configuration via the MCC/drakconnect should also work in most cases. | ||
Revision as of 16:59, 6 November 2020
 |
Other languages Deutsch ; English ; Español ; Français ; Português(Portugal) |
Mageia 8
Note that we will be adding issues from the Mageia bugtracker list as they are reported.
Boot
Some recent Intel systems
As per https://bugs.mageia.org/show_bug.cgi?id=26829#c9, some recent Intel systems require changing noxconf to xdriver=modesetting in the kernel options when booting a Live system, for the graphics to work properly. If using the classical installer, at the summary screen reconfigure the graphics to use the Xorg/modesetting driver rather than the default Intel driver.
Live images
GNOME
1) By default GNOME uses the Wayland display server. Wayland is still not fully mature, and may not work well on some hardware. Normally GNOME will automatically fall back to using the X.org display server if Wayland fails to start, but in some cases this fails to happen. If the GNOME desktop fails to launch after completing the initial language and locale selection, or if you experience display problems, you can try forcing GNOME to use the X.org display server by adding nowayland to the boot options in the initial boot menu (press e to edit the boot options).
2) By default the NetworkManager service is enabled in place of the old network management services. You can use the drop-down menu accessible from the top right corner of the GNOME desktop to perform any necessary network configuration. For wired connections, the network is usually configured automatically and you don't need to do anything. For wireless networks, you will usually need to select an access point and, if it is password-protected, enter the password. Network configuration via the MCC/drakconnect should also work in most cases.
