--- xml/release-notes.xml | 42 +++++++++++++++++++++--------------------- 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/xml/release-notes.xml b/xml/release-notes.xml index 6a21d11..bafc561 100644 --- a/xml/release-notes.xml +++ b/xml/release-notes.xml @@ -161,7 +161,7 @@ or online on <ulink url="http://doc.opensuse.org"/>. <title>UEFI&mdash;Unified Extensible Firmware Interface</title> <para>CHECKIT:13.1</para> <para> 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 + 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. </para>

@@ -171,7 +171,7 @@ or online on <ulink url="http://doc.opensuse.org"/>. 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 (<literal>pstore</literal>) have been disabled by default. Nevertheless it is + information (<literal>pstore</literal>) have been disabled by default. Nevertheless, it is recommended to install any firmware updates the hardware vendor recommends. </para> </section>

@@ -180,11 +180,11 @@ or online on <ulink url="http://doc.opensuse.org"/>. <!-- bnc#850056 --> <title>UEFI, GPT, and MS-DOS Partitions</title> <para>CHECKIT:13.1</para> - <para> Together with the EFI/UEFI specification a new style of partitioning arrived: GPT (GUID + <para> Together with the EFI/UEFI specification, a new style of partitioning arrived: GPT (GUID Partition Table). This new schema uses globally unique identifiers (128-bit values displayed in 32 hexadecimal digits) to identify devices and partition types. </para> <para> Additionally, the UEFI specification also allows legacy MBR (MS-DOS) partitions. The Linux - boot loaders (ELILO or GRUB2) try to generate automatically a GUID for those legacy partitions, + boot loaders (ELILO or GRUB2) try to automatically generate a GUID for those legacy partitions, and write them to the firmware. Such a GUID can change frequently, causing a rewrite in the firmware. A rewrite consist of two different operation: removing the old entry and creating a new entry that replaces the first one. </para> @@ -202,7 +202,7 @@ or online on <ulink url="http://doc.opensuse.org"/>. <para> This only affects machines in UEFI mode with secure boot enabled. </para> <para> The new version of the shim loader allows more machines to boot with Secure Boot enabled than with openSUSE 12.3. Nevertheless, in case of trouble, first update the BIOS of your machine - to the latest version. If the BIOS update does not help, report the model of your machine it the + to the latest version. If the BIOS update does not help, report the model of your machine to the wiki (http://en.opensuse.org/openSUSE:UEFI). Then we can track it for the next release. </para> </section>

@@ -225,34 +225,34 @@ or online on <ulink url="http://doc.opensuse.org"/>. <!-- 13.2: to be removed from the release notes: https://bugzilla.novell.com/show_bug.cgi?id=849188 --> - <para> With openSUSE 11.3 we switched to KMS (Kernel Mode Setting) for Intel, ATI and NVIDIA + <para> With openSUSE 11.3, we switched to KMS (Kernel Mode Setting) for Intel, ATI and NVIDIA graphics, which now is our default. If you encounter problems with the KMS driver support (intel, radeon, nouveau), disable KMS by adding <literal>nomodeset</literal> to the kernel boot command line. To set this permanently using Grub 2, the default boot loader, add it to the <literal>GRUB_CMDLINE_LINUX_DEFAULT</literal> kernel default load options line in your <filename>/etc/default/grub</filename> text file as root and running the terminal command </para> <screen>sudo /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg</screen> - <para> for the changes to take effect. Else, for Grub Legacy, add it to the kernel command line + <para> for the changes to take effect. For Grub Legacy, add it to the kernel command line in <filename>/boot/grub/menu.lst</filename>, also done as root. This option makes sure the appropriate kernel module (intel, radeon, nouveau) is loaded with <literal>modeset=0</literal> in <filename>initrd</filename>, i.e. KMS is disabled. </para>

- <para> In the rare cases when loading the DRM module from <filename>initrd</filename> is a + <para> In the rare cases, when loading the DRM module from <filename>initrd</filename> is a general problem and unrelated to KMS, it is even possible to disable loading of the DRM module - in <filename>initrd</filename> completely. For this set the <literal>NO_KMS_IN_INITRD</literal> + in <filename>initrd</filename> completely. For this, set the <literal>NO_KMS_IN_INITRD</literal> sysconfig variable to <literal>yes</literal> via YaST, which then recreates <filename>initrd</filename> afterwards. Reboot your machine.</para>

- <para> On Intel without KMS the Xserver falls back to the <literal>fbdev</literal> driver (the + <para> On Intel without KMS, the Xserver falls back to the <literal>fbdev</literal> driver (the <literal>intel</literal> driver only supports KMS); alternatively, for legacy GPUs from Intel the "intellegacy" driver (<systemitem>xorg-x11-driver-video-intel-legacy</systemitem> package) is available, which still supports UMS (User Mode Setting). To use it, edit <filename>/etc/X11/xorg.conf.d/50-device.conf</filename> and change the driver entry to <literal>intellegacy</literal>.</para>

- <para> On ATI for current GPUs it falls back to <literal>radeonhd</literal>. On NVIDIA without - KMS the <literal>nv</literal> driver is used (the <literal>nouveau</literal> driver supports - only KMS). Note, newer ATI and NVIDIA GPUs are falling back to <literal>fbdev</literal>, if you + <para> On current ATI GPUs, it falls back to <literal>radeonhd</literal>. On NVIDIA without + KMS, the <literal>nv</literal> driver is used (the <literal>nouveau</literal> driver supports + only KMS). Note that newer ATI and NVIDIA GPUs are falling back to <literal>fbdev</literal> if you specify the <literal>nomodeset</literal> kernel boot parameter.</para> </section>

@@ -277,7 +277,7 @@ or online on <ulink url="http://doc.opensuse.org"/>. <!-- via mail: ddiss --> <title>Samba Version 4.1</title> <para>CHECKIT:13.1</para> - <para> Samba version 4.1 shipped with openSUSE 13.1 does not include support to operate as an + <para> Samba version 4.1 shipped with openSUSE 13.1 does not include support for operating as an Active Directory style domain controller. This functionality is currently disabled, as it lacks integration with system-wide MIT Kerberos. </para> </section> @@ -292,8 +292,8 @@ or online on <ulink url="http://doc.opensuse.org"/>. the KDE workspace only supports Bluez version 4 in its currently-released versions. </para> <para> Therefore, the openSUSE KDE community team offers an unofficial Bluedevil package providing at least basic functionality such as device pairing or support for bluetooth mice; - Some other features are known not to work jet, like file transfer. </para> - <para> For the moment, bugs should not be filed against Bluetooth support in KDE as the Bluez 5 + Some other features are known not to work yet, like file transfer. </para> + <para> For the time being, bugs should not be filed against Bluetooth support in KDE, as the Bluez 5 port of Bluedevil is still ongoing. </para> </section>

@@ -302,11 +302,11 @@ or online on <ulink url="http://doc.opensuse.org"/>. <title>AppArmor and Permission Settings</title> <para>CHECKIT:13.1</para> <para> AppArmor is enabled by default. This means more security, but might prevent services from - working, if you run them in unexpected ways. If you encounter strange permission problems, try + working if you run them in unexpected ways. If you encounter strange permission problems, try to switch the AppArmor profile for the affected service to complain mode with: </para> <screen>aa-complain /usr/bin/$your_service</screen> <para> Complain mode means: allow everything, and log things that the profile would not allow. </para> - <para> Even if it helps report it as a bug! We want to fix AppArmor profiles to cover also corner + <para> Even if it helps, report it as a bug! We want to fix AppArmor profiles to also cover corner cases. </para> </section>

@@ -325,11 +325,11 @@ or online on <ulink url="http://doc.opensuse.org"/>. <!-- bnc#851588 --> <title>AutoYaST</title> <para>CHECKIT:13.1</para> - <para> If the autoyast profile contains entries in an <literal>&lt;add-on></literal> section + <para> If the autoyast profile contains entries in an <literal>&lt;add-on&gt;</literal> section, there is a bug triggered that prevents information in the profile from being transferred from - the first stage into the second stage. Therefore, in this case all second stage configuration + the first stage into the second stage, in which case, all second stage configuration steps are skipped, which normally leads to more or less completely unusable installations. </para> - <para> As a temporary workaround, avoid using <literal>&lt;add-on></literal> sections in + <para> As a temporary workaround, avoid using <literal>&lt;add-on&gt;</literal> sections in profiles with AutoYaST in openSUSE 13.1. </para> </section> </section>