Hi
At the target lib/modules is not listing and lsmod is not tainted.
Any suggestions.
Thanks
UmaMahesh
::DISCLAIMER::
The contents of this e-mai
On Wed, Oct 18, 2017 at 3:13 PM, Marlon Smith wrote:
> Hi everyone,
>
> I'm trying to build the Linux backports project to get updated wifi drivers
> on an older kernel. The problem is that when building backports, it first
> builds several tools that need to be run natively before cross-compilin
I tried building backports under Yocto a few years back using Yocto daisy
branch with kernel 3.4 for x86 and kernel 3.12 for ARM. After a fair amount of
pain I was able to get it to sort of work. The problem was mainly a sysroot
arm-wrestle between kernel and backports because they both genera
Darcy, thanks for the detailed reply!
Do you remember how you were able to get it to compile in the first
place? I end up with this error:
./kconf/conf: 1: ./kconf/conf: Syntax error: word unexpected (expecting
")")
..because backports needs to compile conf for x86_64, but instead
compiles it for
Hi,
I usually build a debug kernel with debug info included, which makes it
run "suboptimal". Distros build the kernel with CONFIG_DEBUG_INFO
enables, but strip symbols out of the resulting kernel and kernel
modules, and place them in the separate debuginfo packages. This makes
the kernel muc
Hi everyone,
I'm trying to build the Linux backports project to get updated wifi
drivers on an older kernel. The problem is that when building
backports, it first builds several tools that need to be run natively
before cross-compiling the rest of the project.
I know how to write a bitbake recip
Hello,
When I target raspberrypi3 and have tools-testapps listed in
EXTRA_IMAGE_FEATURES in my local.conf, build errors occur.
The errors come from the building of mesa-demos and gst-player. If I remove
those targets from packagegroup-core-tools-testapps.bb, I don’t get errors.
The errors see
On Wednesday, 18 October 2017 3:11:59 AM NZDT Marc Ferland wrote:
> On Tue, Oct 17, 2017 at 9:12 AM, Robert Berger
> wrote:
> > Hi,
> >
> > Imagine you have only a limited bandwidth to your devices available for SW
> > update. So you would like to minimize what's uploaded (over the air) to
your
>
On Wed, 18 Oct 2017 14:29:08 +0300
Alexander Kanavin wrote:
> On 10/18/2017 02:08 PM, a...@auh.yoctoproject.org wrote:
> > TOTAL: attempted=147 succeeded=25(17.01%) failed=122(82.99%)
>
> With this kind of success rate, should we continue to run and develop
> the thing?
>
> I think it's b
I figured out.
udevadm monitor ist provided by the SystemV package.
Problem solved!
Stefan
ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 181
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-gri
On 10/18/2017 02:08 PM, a...@auh.yoctoproject.org wrote:
TOTAL: attempted=147 succeeded=25(17.01%) failed=122(82.99%)
With this kind of success rate, should we continue to run and develop
the thing?
I think it's better to just send notifications to maintainers without
attempting to upd
AUH finished upgrade batch the result patches/logs can be found at:
https://logs.yoctoproject.org/auh//20171017113055, next are the statistics:
Recipe upgrade statistics:
* Succeeded: 25
libdrm, 2.4.84, Otavio Salvador
python3-numpy, 1.13.3, Jose Lamego
libunwind, 1.
Hej,
Actually I am playing a bit arround with udev rules. For that I like to
use the udevadm monitor. The udev is provided by
/meta/recipes-core/udev/eudev_3.2.2.bb
In this recipe there is no udevadm option. While checking, I saw it was
once in udev-utils and been moved to udev.inc.
https://
> On 18 Oct 2017, at 07:22, Craig McQueen wrote:
>
> I wrote:
>>
>> I'm trying to upgrade from mono 4.6.x to 5.2.x. I see resulting image size
>> increases by about 10 MB in my usage. It appears that a significant
>> contributing factor is the presence of *.pdb files in 5.2.x which weren't in
14 matches
Mail list logo
