Known Problems in This Release
The open source projects are continuously working on correcting
reported problems. Corrections to bugs detected by Enea are submitted
upstream, and the corrections are included in Enea Linux regardless of
when they will be included by the open source project. Remaining issues are
listed below.
Yocto
The Yocto Project community uses a Bugzilla database to track
information on reported bugs and other issues:
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
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
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.