From 6871890f9e5778619c8d76117655dd075c1b7b78 Mon Sep 17 00:00:00 2001 From: Thomas Lundström Date: Wed, 8 Jun 2016 17:18:05 +0200 Subject: Updated release info --- .../doc/about_release.xml | 13 +- .../doc/common_bugs_and_limitations.xml | 450 -------------------- .../doc/known_bugs_and_limitations.xml | 455 ++++++++++++++++++++- .../doc/main_changes.xml | 3 +- 4 files changed, 451 insertions(+), 470 deletions(-) delete mode 100644 doc/book-enea-linux-release-info/doc/common_bugs_and_limitations.xml (limited to 'doc/book-enea-linux-release-info') diff --git a/doc/book-enea-linux-release-info/doc/about_release.xml b/doc/book-enea-linux-release-info/doc/about_release.xml index 500853e..2305b7d 100644 --- a/doc/book-enea-linux-release-info/doc/about_release.xml +++ b/doc/book-enea-linux-release-info/doc/about_release.xml @@ -171,7 +171,7 @@ - poky source + Poky source - gcc version + GCC version - 4.9was EneaLinux_GCC_VER Not in poky.ent + 5.3was EneaLinux_GCC_VER Not in poky.ent - Linux kernel version (all targets) - - 3.12was EneaLinux_KERNEL_VER Not in + Linux kernel versionwas EneaLinux_KERNEL_VER Not in poky.ent + + 3.12 (P2041RDB & LS1021a-IoT)4.4 + (QEmu targets) diff --git a/doc/book-enea-linux-release-info/doc/common_bugs_and_limitations.xml b/doc/book-enea-linux-release-info/doc/common_bugs_and_limitations.xml deleted file mode 100644 index 88763f2..0000000 --- a/doc/book-enea-linux-release-info/doc/common_bugs_and_limitations.xml +++ /dev/null @@ -1,450 +0,0 @@ - - -
- General Bugs and Limitations - - - -
- Yocto - - Open source projects often use bug databases for much more than - tracking bugs. The Yocto Project's Bugzilla database also functions as a - feature tracking program, both for the current release and for future - releases, and a way to track non-software issues, like documentation - changes. - - The following page shows a sampling of the database: https://www.yoctoproject.org/tools-resources/bugs. - - For the full database, visit https://bugzilla.yoctoproject.org. -
- -
- Toolchain / SDK - - - - Building the kernel might fail if GNU Make of version 3.82 has - been installed on the host. The mandatory recovery action is to revert - to version 3.81. - - - - Installing a second toolchain in the same directory as a - previous one will break the $PATH variable of the first - one.LXCR-3624 - - -
- -
- Smart Package Manager - - Installation of some packages might currently fail when installing - using the Smart Package Manager. An example is the qemu package. Errors - can e.g. be reported by smart about conflicts with files from other - packages. - - The recommended solution to this problem is to install the failing - package using rpm, already available in enea-image-base. In order to - install it using rpm, first install rpm using the command smart - install rpm, then download the package to the target, and - finally on the target use rpm -i - <packagename>.rpm. If not installed, several dependencies - can be reported as "Failed dependencies" with lines "x is needed by y". In - that case, install the required packages "x" found by dependencies by - using the smart package manager. Add a channel to an accessible directory - containing all missing rpm packages. Add packages detected to be missing, - until all dependencies are resolved.FIXME It would be nice to add - also a PowerPC example with qemu failing, the example below is for - ARM. - -
- Example with Failing QEMU Package - - As an example, the qemu installation can show the following - error. - - - The example below is for ARM, including the RPM names. For - PowerPC similar errors can occur and other packages are needed. - - - error: file /var/run from install of - qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 conflicts with file from package - base-files-3.0.14-r89.0.hierofalcon - - A solution to this problem is to install the above qemu package - using rpm, already available in enea-image-base. In order to install it - using rpm, first install rpm using the command smart install - rpm, then download the above package from - <build_dir>/tmp/deploy/rpm/aarch64. On target, use rpm -i - qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm. If not installed, - several dependencies can be seen, e.g.: - - error: Failed dependencies: - libpixman-1-0 >= 0.32.6 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 - libpixman-1.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 - libglib-2.0.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 - libcap2 >= 2.22 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 - libglib-2.0-0 >= 2.40.0 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 - bluez4 >= 4.101 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 - libbluetooth.so.3()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 - libcap.so.2()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 - - Install the required packages found by dependencies by using the - smart package manager, as specified in the User's Guide, by adding a - channel to an accessible directory containing all of the above rpm - packages. Suggestion for installing required packages, as in the - following example for qemu and ARM: - - smart install bash -smart install libcap -smart install bluez4 -smart install libpixman-1-0 -rpm -i qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm - - Add packages detected to be missing until all dependencies are - resolved. -
-
- -
- Eclipse Tools - - The Eclipse tools provided together with Enea Linux are part of the - Yocto Application Development Toolkit (ADT) and are maintained by - different open source projects. The list below outlines current problems - with the plug-ins as such, as well as kernel limitations when using a tool - towards the mentioned target: - - - - HOB is currently not supported - on Red Hat.LXCR-2994, LXCR-3222 - - - - SystemTap is currently not - supported on Red Hat.LXCR-3274 - - - - When running SystemTap for the - first time on a target, you may need to manually ssh into the target - beforehand, in order to add the RSA key of the host to the file - known_hosts. Failing to do so will result in Eclipse freezing with the - progress window displayed, and a terminal message The - authenticity of host <target_ip> can't be - established. - - - - SystemTap scripts sometimes - result crosstap error messages about inaccessible variables. This is - not an issue with the tool itself, but stems from the compiler - optimizing away some of the variables. See workaround in the User's - Guide.LXCR-2204 - - - - Currently BitBake Commander - projects can only be created for a local connection. Due to an - upstream bug, selecting a remote connection causes the Eclipse GUI to - freeze such that it must be killed.LXCR-2801 - - - - A limitation currently makes Eclipse non-responding when running a streaming - script, i.e. a script that runs continuously. - - - - The LatencyTop plug-in for the - P2041 target reports some errors due to the permissions configuration - on the target, but it works correctly if the - latencytop command is issued from the Eclipse - console.LXCR-6303 - - - - Currently LatencyTOP is not - available for ARM kernels built with SMP support due to an ARM - specific limitation in the Linux kernel. - - - - PowerTOP sometimes freezes - Eclipse after displaying a progress bar with message - Gathering powertop data file - remotely.LXCR-3143 - - - - When running powertop from the - Eclipse terminal towards p2020rdb targets it is necessary to specify - the full path in order to find the - command.LXCR-2265 - - - - When running powertop from the - Eclipse terminal towards zynq ZC702 targets it is necessary to specify - the full path in order to find the - command.LXCR-2265 - - - - The PowerTOP console in Eclipse - might display messages like Cannot load - /var/cache/powertop/<filename>. As a workaround, run - powertop --calibrate for a while to - generate the missing files. See Bugzilla - #698020.LXCR-3575 - - - - ssh-only is currently the only - supported connection type when running Eclipse tools towards a - target.LXCR-2799 - - - - Hyphen character '-' in the name of the Yocto ADT AutoTools project can cause - configuration errors.LXCR-2290 - - - - The LTTng tool does not work on - ARM targets, neither from within - Eclipse nor when run directly on target, due to a problem with - lttng-modules and gcc-4.8.x. See Bugzilla - #6015.LXCR-2653, LXCR-3053 - - - - When running LTTng from - Eclipse, it sometimes happens that a new session created in the - Control View does not immediately appear under Sessions for that - target. However, the session is created and will appear after - right-clicking "Sessions" and selecting "Refresh". - - - - The yocto-bsp properties page - has some problems in the graphical user interface. Occasionally it is - not possible to resize and scroll which makes it impossible to see the - lower part of the properties window.LXCR-3128 - - - - When connecting an Eclipse project configured for KGDB (GDB Hardware Debugging) to a 64-bit - PowerPC target, GDB fails to connect unless the architecture is - specified in .gdbinit. See Bugzilla - #457697.LXCR-3984 - - -
- -
- Target-Side Tools - - The target-side tools can be run stand-alone on target or from - Eclipse on host. The issues below are only observed when running the tools - directly on target: - - - - The perf report command hangs - or crashes due to segmentation fault on ARM - targets.LXCR-2708 - - - - The perf report does not show - any output for the PandaBoard target.LXCR-2710 - - - - perf top displays for a few - seconds the error message Failed to open - /tmp/perf-388.map. Any attempt to exit the subsequent window - causes the system to hang.LXCR-3113 - - - - When running the perf top command on the i.MX - 6Quad SABRE Lite target, the console text may become red after running - for some time (~ 1 minute).LXCR-3631 - - - - The LTTng tool does not work on - ARM targets, neither from within - Eclipse nor when run directly on target, due to a problem with - lttng-modules and gcc-4.8.x. See Bugzilla - #6015.LXCR-2653, LXCR-3053 - - - - The powertop --calibrate - command does not work on the Keystone k2hk-evm - target.LXCR-2660 - - - - The powertop command run with - --calibrate or --time arguments may show some warnings on - PowerPC targets. - - - - When running powertop on - ARM targets, the following - warning/error is repeated: clk_set_rate: failed to set - i2c0_aper rate . Then powertop stops and the statistics are - no longer updated. What probably happens here is that the cpufreq - governor tries to scale the CPU frequency, but since the I2C clock is - derived from the CPU frequency, the I2C driver implements some policy - to stay within legal frequency limits and rejects the frequency - changes, ending up with the warning message. A fix - has been merged in the linux-xlnx kernel but is not yet propagated - into meta-xilinx.LXCR-3205, LXCR-3106, - LXCR-2660 - - - - If you get an error message like Cannot load from file - /var/cache/powertop/saved_results.powertop when running - powertop, there is most likely not - enough measurement data collected yet. All you have to do is to keep - powertop running for a certain time.LXCR-2176, LXCR-2660, - LXCR-3106 - - - - The message Model-specific registers (MSR) not found - (try enabling CONFIG_X86_MSR) appears when you run powertop on non-x86 targets. powertop is mainly an x86n - tool, so it expects X*^_MSR config to be enabled in the kernel. For - non-x86 targets this config is not available in the kernel, hence, - powertop warns about it, but the message can be ignored on those - targets. LXCR-2176, LXCR-2660, LXCR-3106 - - - - powertop issues a message - sh: /usr/bin/xset: No such file or directory when - it tries to use xset to configure X display preferences but cannot - find the binary since the image by default contains no X system. The - message can simply be ignored.LXCR-2176 - - -
- -
- Virtualization - - - - virtualization: CONFIG_BRIDGE - is not included in the default p2020rdb - kernel.LXVTCR-273 - - - - lxc: - - - - User namespace is not available on PowerPC targets as it is - an experimental feature in the 3.8 kernel. - - - - If multiple Linux containers are started from the same - process and share resources, destroying the containers might - result in a race condition with error message "Error in - `./lxc-test-concurrent': double free or corruption (fasttop)" - followed by an application - crash."LXVTCR-365 - - - - - - libvirt: Default network does - not start.LXVTCR-240 - - -
- -
- Documentation - - - - PDF navigation: When using - links to open other PDFs, or jump to another place in the same PDF, - jumping back sometimes fails. This has been observed when opening a - PDF in Adobe Reader, inside a browser with PDF add-on, as well as when - the browser is configured to open PDF files in an external PDF reader. - As a workaround, open the HTML version of the - document.LXCR-3283 - - - - Internet Explorer (IE) cannot display some - web pages: It is recommended to use Firefox or another - non-IE browser for opening external links. If you prefer reading the - documentation in PDF format in Adobe Reader (not in an Adobe plug-in - in a browser), remember to configure a non-IE browser as default - browser to be able to follow all links from within Adobe Reader. - Example of a link that does not work in IE: https://rt.wiki.kernel.org/. - LXCR-3281 - - - - Characters not displayed properly in - PDF: When viewing PDF files in a browser, checkmarks (V) - and crosses (x) might display as 4 and 7, respectively. This has been - observed when reading Supported Targets in - Firefox. Installing the Adobe Acrobat add-on should fix the - problem.LXCR-3266 - - -
- -
- Miscellaneous - - - - Running QEMU from an exported - rootfs requires sudo privileges on the host. - - - - menuconfig requires Ncurses. If the terminal that pops up - immediately closes instead of showing the menuconfig interface, check - that the Ncurses development library is installed. - - -
-
\ No newline at end of file diff --git a/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml index a219fe4..2a9598b 100644 --- a/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml +++ b/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml @@ -14,27 +14,456 @@ targetptr="book_enea_linux_users_guide">Enea Linux User's Guide. -
- Release-Specific Problems +
+ Yocto -
- Problem with 32-bit Applications on 64-bit T4240 + Open source projects often use bug databases for much more than + tracking bugs. The Yocto Project's Bugzilla database also functions as a + feature tracking program, both for the current release and for future + releases, and a way to track non-software issues, like documentation + changes. - Currently in the Enea Linux 5.0-ppc release, cross-compiling - 32-bit applications to run on the T4240 64-bit target is not - supported. + The following page shows a sampling of the database: https://www.yoctoproject.org/tools-resources/bugs. + + For the full database, visit https://bugzilla.yoctoproject.org. +
+ +
+ Toolchain / SDK + + + + Building the kernel might fail if GNU Make of version 3.82 has + been installed on the host. The mandatory recovery action is to + revert to version 3.81. + + + + Installing a second toolchain in the same directory as a + previous one will break the $PATH variable of the first + one.LXCR-3624 + + +
+ +
+ Smart Package Manager + + Installation of some packages might currently fail when installing + using the Smart Package Manager. An example is the qemu package. Errors + can e.g. be reported by smart about conflicts with files from other + packages. + + The recommended solution to this problem is to install the failing + package using rpm, already available in enea-image-base. In order to + install it using rpm, first install rpm using the command smart + install rpm, then download the package to the target, and + finally on the target use rpm -i + <packagename>.rpm. If not installed, several + dependencies can be reported as "Failed dependencies" with lines "x is + needed by y". In that case, install the required packages "x" found by + dependencies by using the smart package manager. Add a channel to an + accessible directory containing all missing rpm packages. Add packages + detected to be missing, until all dependencies are + resolved.FIXME It would be nice to add also a PowerPC example + with qemu failing, the example below is for ARM. + +
+ Example with Failing QEMU Package + + As an example, the qemu installation can show the following + error. + + + The example below is for ARM, including the RPM names. For + PowerPC similar errors can occur and other packages are + needed. + + + error: file /var/run from install of + qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 conflicts with file from + package base-files-3.0.14-r89.0.hierofalcon + + A solution to this problem is to install the above qemu package + using rpm, already available in enea-image-base. In order to install + it using rpm, first install rpm using the command smart + install rpm, then download the above package from + <build_dir>/tmp/deploy/rpm/aarch64. On target, use rpm + -i qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm. If not + installed, several dependencies can be seen, e.g.: + + error: Failed dependencies: + libpixman-1-0 >= 0.32.6 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 + libpixman-1.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 + libglib-2.0.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 + libcap2 >= 2.22 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 + libglib-2.0-0 >= 2.40.0 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 + bluez4 >= 4.101 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 + libbluetooth.so.3()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 + libcap.so.2()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 + + Install the required packages found by dependencies by using the + smart package manager, as specified in the User's Guide, by adding a + channel to an accessible directory containing all of the above rpm + packages. Suggestion for installing required packages, as in the + following example for qemu and ARM: + + smart install bash + smart install libcap + smart install bluez4 + smart install libpixman-1-0 + rpm -i qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm + + Add packages detected to be missing until all dependencies are + resolved. +
+
+ +
+ Eclipse Tools + + The Eclipse tools provided together with Enea Linux are part of + the Yocto Application Development Toolkit (ADT) and are maintained by + different open source projects. The list below outlines current problems + with the plug-ins as such, as well as kernel limitations when using a + tool towards the mentioned target: + + + + HOB is currently not + supported on Red Hat.LXCR-2994, LXCR-3222 + + + + SystemTap is currently not + supported on Red Hat.LXCR-3274 + + + + When running SystemTap for + the first time on a target, you may need to manually ssh into the + target beforehand, in order to add the RSA key of the host to the + file known_hosts. Failing to do so will result in Eclipse freezing + with the progress window displayed, and a terminal message + The authenticity of host <target_ip> can't be + established. + + + + SystemTap scripts sometimes + result crosstap error messages about inaccessible variables. This is + not an issue with the tool itself, but stems from the compiler + optimizing away some of the variables. See workaround in the User's + Guide.LXCR-2204 + + + + Currently BitBake Commander + projects can only be created for a local connection. Due to an + upstream bug, selecting a remote connection causes the Eclipse GUI + to freeze such that it must be + killed.LXCR-2801 + + + + A limitation currently makes Eclipse non-responding when running a + streaming script, i.e. a script that runs continuously. + + + + The LatencyTop plug-in for + the P2041 target reports some errors due to the permissions + configuration on the target, but it works correctly if the + latencytop command is issued from the Eclipse + console.LXCR-6303 + + + + Currently LatencyTOP is not + available for ARM kernels built with SMP support due to an ARM + specific limitation in the Linux kernel. + + + + PowerTOP sometimes freezes + Eclipse after displaying a progress bar with message + Gathering powertop data file + remotely.LXCR-3143 + + + + When running powertop from + the Eclipse terminal towards p2020rdb targets it is necessary to + specify the full path in order to find the + command.LXCR-2265 + + + + When running powertop from + the Eclipse terminal towards zynq ZC702 targets it is necessary to + specify the full path in order to find the + command.LXCR-2265 + + + + The PowerTOP console in + Eclipse might display messages like Cannot load + /var/cache/powertop/<filename>. As a workaround, run + powertop --calibrate for a while to + generate the missing files. See Bugzilla + #698020.LXCR-3575 + + + + ssh-only is currently the + only supported connection type when running Eclipse tools towards a + target.LXCR-2799 + + + + Hyphen character '-' in the name of the Yocto ADT AutoTools project can cause + configuration errors.LXCR-2290 + + + + The LTTng tool does not work + on ARM targets, neither from within + Eclipse nor when run directly on target, due to a problem with + lttng-modules and gcc-4.8.x. See Bugzilla + #6015.LXCR-2653, LXCR-3053 + + + + When running LTTng from + Eclipse, it sometimes happens that a new session created in the + Control View does not immediately appear under Sessions for that + target. However, the session is created and will appear after + right-clicking "Sessions" and selecting "Refresh". + + + + The yocto-bsp properties page + has some problems in the graphical user interface. Occasionally it + is not possible to resize and scroll which makes it impossible to + see the lower part of the properties + window.LXCR-3128 + + + + When connecting an Eclipse project configured for KGDB (GDB Hardware Debugging) to a 64-bit + PowerPC target, GDB fails to connect unless the architecture is + specified in .gdbinit. See Bugzilla + #457697.LXCR-3984 + + +
+ +
+ Target-Side Tools + + The target-side tools can be run stand-alone on target or from + Eclipse on host. The issues below are only observed when running the + tools directly on target: + + + + The perf report command hangs + or crashes due to segmentation fault on ARM + targets.LXCR-2708 + + + + The perf report does not show + any output for the PandaBoard + target.LXCR-2710 + + + + perf top displays for a few + seconds the error message Failed to open + /tmp/perf-388.map. Any attempt to exit the subsequent + window causes the system to hang.LXCR-3113 + + + + When running the perf top command on the + i.MX 6Quad SABRE Lite target, the console text may become red after + running for some time (~ 1 minute).LXCR-3631 + + + + The LTTng tool does not work + on ARM targets, neither from within + Eclipse nor when run directly on target, due to a problem with + lttng-modules and gcc-4.8.x. See Bugzilla + #6015.LXCR-2653, LXCR-3053 + + + + The powertop --calibrate + command does not work on the Keystone k2hk-evm + target.LXCR-2660 + + + + The powertop command run with + --calibrate or --time arguments may show some warnings on + PowerPC targets. + + + + When running powertop on + ARM targets, the following + warning/error is repeated: clk_set_rate: failed to set + i2c0_aper rate . Then powertop stops and the statistics + are no longer updated. What probably happens here is that the + cpufreq governor tries to scale the CPU frequency, but since the I2C + clock is derived from the CPU frequency, the I2C driver implements + some policy to stay within legal frequency limits and rejects the + frequency changes, ending up with the warning message. A fix + has been merged in the linux-xlnx kernel but is not yet propagated + into meta-xilinx.LXCR-3205, LXCR-3106, + LXCR-2660 + + + + If you get an error message like Cannot load from + file /var/cache/powertop/saved_results.powertop when + running powertop, there is most + likely not enough measurement data collected yet. All you have to do + is to keep powertop running for a certain time.LXCR-2176, + LXCR-2660, LXCR-3106 + + + + The message Model-specific registers (MSR) not found + (try enabling CONFIG_X86_MSR) appears when you run + powertop on non-x86 targets. powertop is mainly an x86n + tool, so it expects X*^_MSR config to be enabled in the kernel. For + non-x86 targets this config is not available in the kernel, hence, + powertop warns about it, but the message can be ignored on those + targets. LXCR-2176, LXCR-2660, LXCR-3106 + + + + powertop issues a message + sh: /usr/bin/xset: No such file or directory when + it tries to use xset to configure X display preferences but cannot + find the binary since the image by default contains no X system. The + message can simply be ignored.LXCR-2176 + +
-
- +
+ Virtualization + + + + virtualization: CONFIG_BRIDGE + is not included in the default p2020rdb + kernel.LXVTCR-273 + + + + lxc: + + + + User namespace is not available on PowerPC targets as it + is an experimental feature in the 3.8 kernel. + + + + If multiple Linux containers are started from the same + process and share resources, destroying the containers might + result in a race condition with error message "Error in + `./lxc-test-concurrent': double free or corruption (fasttop)" + followed by an application + crash."LXVTCR-365 + + + + + + libvirt: Default network does + not start.LXVTCR-240 + + +
- +
+ Documentation + + + + PDF navigation: When using + links to open other PDFs, or jump to another place in the same PDF, + jumping back sometimes fails. This has been observed when opening a + PDF in Adobe Reader, inside a browser with PDF add-on, as well as + when the browser is configured to open PDF files in an external PDF + reader. As a workaround, open the HTML version of the + document.LXCR-3283 + + + + Internet Explorer (IE) cannot display + some web pages: It is recommended to use Firefox or + another non-IE browser for opening external links. If you prefer + reading the documentation in PDF format in Adobe Reader (not in an + Adobe plug-in in a browser), remember to configure a non-IE browser + as default browser to be able to follow all links from within Adobe + Reader. Example of a link that does not work in IE: https://rt.wiki.kernel.org/. + LXCR-3281 + + + + Characters not displayed properly in + PDF: When viewing PDF files in a browser, checkmarks (V) + and crosses (x) might display as 4 and 7, respectively. This has + been observed when reading Supported Targets in + Firefox. Installing the Adobe Acrobat add-on should fix the + problem.LXCR-3266 + + +
+ +
+ Miscellaneous + + + + Running QEMU from an exported + rootfs requires sudo privileges on the host. + + + + menuconfig requires Ncurses. If the terminal that pops up + immediately closes instead of showing the menuconfig interface, + check that the Ncurses development library is installed. + + +
Extracted from Jira - This section lists open bugs in Jira. + This section lists open bugs in Jira. project = "Linux CR" \ and issuetype = Bug \ @@ -144,4 +573,4 @@
- \ No newline at end of file + diff --git a/doc/book-enea-linux-release-info/doc/main_changes.xml b/doc/book-enea-linux-release-info/doc/main_changes.xml index 8647a83..4739669 100644 --- a/doc/book-enea-linux-release-info/doc/main_changes.xml +++ b/doc/book-enea-linux-release-info/doc/main_changes.xml @@ -18,7 +18,8 @@ New Yocto version () + xpointer="element(Yocto_VER/1)" />). See https://www.yoctoproject.org/downloads/core/krogoth21. -- cgit v1.2.3-54-g00ecf