回复: [linux-yocto][v5.4/standard/preempt-rt][yocto-kernel-cache][PATCH] firmware: fix CONFIG_FW_LOADER option mismatch warning

[Zhang, Qiang]

发件人: Bruce Ashfield 
发送时间: 2021年1月20日 12:23
收件人: Zhang, Qiang
抄送: Linux Yocto
主题: Re: [linux-yocto][v5.4/standard/preempt-rt][yocto-kernel-cache][PATCH] 
firmware: fix CONFIG_FW_LOADER option mismatch warning

>I tweaked the shortlog slightly.
>
>But this is now merged.

 Thank you Bruce
  
 Qiang
>
>Bruce

On Tue, Jan 19, 2021 at 9:36 PM  wrote:
>
> From: Zqiang 
>
> [NOTE]: 'CONFIG_FW_LOADER' last val (n) and .config val (y) do not match
> [INFO]: CONFIG_FW_LOADER : y ## .config: 1567 
> :configs/v5.4/ktypes/base/base.cfg (n)
> [INFO]: raw config text:
>
> config FW_LOADER
> tristate "Firmware loading facility" if EXPERT
> default y
> help
>   This enables the firmware loading facility in the kernel. 
> The kernel
>   will first look for built-in firmware, if it has any. Next, 
> it will
>   look for the requested firmware in a series of filesystem 
> paths:
>
> o firmware_class path module parameter or kernel boot 
> param
> o /lib/firmware/updates/UTS_RELEASE
> o /lib/firmware/updates
> o /lib/firmware/UTS_RELEASE
> o /lib/firmware
>
>   Enabling this feature only increases your kernel image by 
> about
>   828 bytes, enable this option unless you are certain you 
> don't
>   need firmware.
>
>   You typically want this built-in (=y) but you can also 
> enable this
>   as a module, in which case the firmware_class module will 
> be built.
>   You also want to be sure to enable this built-in if you are 
> going to
>   enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
>
> [INFO]: selection details for 'CONFIG_FW_LOADER':
> Symbols currently y-selecting this symbol:
>   - MICROCODE
>   - MICROCODE_INTEL
>   - R8169
>
> this warning happend in intel-x86-64-preempt-rt bsp, override
> CONFIG_FW_LOADER option in BSP.
>
> Signed-off-by: Zqiang 
> ---
>  bsp/intel-x86/intel-x86-64-preempt-rt.scc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/bsp/intel-x86/intel-x86-64-preempt-rt.scc 
> b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> index e759c884..e97de15b 100644
> --- a/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> +++ b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> @@ -4,6 +4,6 @@ define KTYPE preempt-rt
>  define KARCH x86
>
>  include ktypes/preempt-rt
> -
> +include features/firmware/firmware.scc
>  include intel-x86-64.scc
>  kconf hardware cfs-bandwidth.cfg
> --
> 2.29.2
>


--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9396): 
https://lists.yoctoproject.org/g/linux-yocto/message/9396
Mute This Topic: https://lists.yoctoproject.org/mt/79972335/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto][v5.4/standard/preempt-rt][yocto-kernel-cache][PATCH] firmware: fix CONFIG_FW_LOADER option mismatch warning

[Bruce Ashfield]

I tweaked the shortlog slightly.

But this is now merged.

Bruce

On Tue, Jan 19, 2021 at 9:36 PM  wrote:
>
> From: Zqiang 
>
> [NOTE]: 'CONFIG_FW_LOADER' last val (n) and .config val (y) do not match
> [INFO]: CONFIG_FW_LOADER : y ## .config: 1567 
> :configs/v5.4/ktypes/base/base.cfg (n)
> [INFO]: raw config text:
>
> config FW_LOADER
> tristate "Firmware loading facility" if EXPERT
> default y
> help
>   This enables the firmware loading facility in the kernel. 
> The kernel
>   will first look for built-in firmware, if it has any. Next, 
> it will
>   look for the requested firmware in a series of filesystem 
> paths:
>
> o firmware_class path module parameter or kernel boot 
> param
> o /lib/firmware/updates/UTS_RELEASE
> o /lib/firmware/updates
> o /lib/firmware/UTS_RELEASE
> o /lib/firmware
>
>   Enabling this feature only increases your kernel image by 
> about
>   828 bytes, enable this option unless you are certain you 
> don't
>   need firmware.
>
>   You typically want this built-in (=y) but you can also 
> enable this
>   as a module, in which case the firmware_class module will 
> be built.
>   You also want to be sure to enable this built-in if you are 
> going to
>   enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
>
> [INFO]: selection details for 'CONFIG_FW_LOADER':
> Symbols currently y-selecting this symbol:
>   - MICROCODE
>   - MICROCODE_INTEL
>   - R8169
>
> this warning happend in intel-x86-64-preempt-rt bsp, override
> CONFIG_FW_LOADER option in BSP.
>
> Signed-off-by: Zqiang 
> ---
>  bsp/intel-x86/intel-x86-64-preempt-rt.scc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/bsp/intel-x86/intel-x86-64-preempt-rt.scc 
> b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> index e759c884..e97de15b 100644
> --- a/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> +++ b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> @@ -4,6 +4,6 @@ define KTYPE preempt-rt
>  define KARCH x86
>
>  include ktypes/preempt-rt
> -
> +include features/firmware/firmware.scc
>  include intel-x86-64.scc
>  kconf hardware cfs-bandwidth.cfg
> --
> 2.29.2
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9395): 
https://lists.yoctoproject.org/g/linux-yocto/message/9395
Mute This Topic: https://lists.yoctoproject.org/mt/79970014/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][v5.4/standard/preempt-rt][yocto-kernel-cache][PATCH] firmware: fix CONFIG_FW_LOADER option mismatch warning

[Zhang, Qiang]

From: Zqiang 

[NOTE]: 'CONFIG_FW_LOADER' last val (n) and .config val (y) do not match
[INFO]: CONFIG_FW_LOADER : y ## .config: 1567 
:configs/v5.4/ktypes/base/base.cfg (n)
[INFO]: raw config text:

config FW_LOADER
tristate "Firmware loading facility" if EXPERT
default y
help
  This enables the firmware loading facility in the kernel. The 
kernel
  will first look for built-in firmware, if it has any. Next, 
it will
  look for the requested firmware in a series of filesystem 
paths:

o firmware_class path module parameter or kernel boot 
param
o /lib/firmware/updates/UTS_RELEASE
o /lib/firmware/updates
o /lib/firmware/UTS_RELEASE
o /lib/firmware

  Enabling this feature only increases your kernel image by 
about
  828 bytes, enable this option unless you are certain you don't
  need firmware.

  You typically want this built-in (=y) but you can also enable 
this
  as a module, in which case the firmware_class module will be 
built.
  You also want to be sure to enable this built-in if you are 
going to
  enable built-in firmware (CONFIG_EXTRA_FIRMWARE).

[INFO]: selection details for 'CONFIG_FW_LOADER':
Symbols currently y-selecting this symbol:
  - MICROCODE
  - MICROCODE_INTEL
  - R8169

this warning happend in intel-x86-64-preempt-rt bsp, override
CONFIG_FW_LOADER option in BSP.

Signed-off-by: Zqiang 
---
 bsp/intel-x86/intel-x86-64-preempt-rt.scc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bsp/intel-x86/intel-x86-64-preempt-rt.scc 
b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
index e759c884..e97de15b 100644
--- a/bsp/intel-x86/intel-x86-64-preempt-rt.scc
+++ b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
@@ -4,6 +4,6 @@ define KTYPE preempt-rt
 define KARCH x86
 
 include ktypes/preempt-rt
-
+include features/firmware/firmware.scc
 include intel-x86-64.scc
 kconf hardware cfs-bandwidth.cfg
-- 
2.29.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9394): 
https://lists.yoctoproject.org/g/linux-yocto/message/9394
Mute This Topic: https://lists.yoctoproject.org/mt/79970014/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

[Konrad Weihmann]

Just a wild guess, but could your corporate proxy, which is kind of 
visible in the provided logs, intervene with this - to me it seems to be 
some MITM box.

Do you have any chance to try it without that proxy involved?

On 19.01.21 21:42, Monsees, Steven C (US) via lists.yoctoproject.org wrote:

This is the types of error I am seeing:


WARNING: qemu-native-4.1.0-r0 do_fetch: Failed to fetch URL 
https://download.qemu.org/qemu-4.1.0.tar.xz, attempting MIRRORS if available
WARNING: libarchive-native-3.4.0-r0 do_fetch: Failed to fetch URL 
http://libarchive.org/downloads/libarchive-3.4.0.tar.gz, attempting MIRRORS if 
available
ERROR: libarchive-native-3.4.0-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; unset 
_PYTHON_SYSCONFIGDATA_NAME; export 
DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-WGeN1VUN5f,guid=5f3398a95f5d5aa6a98efe74600732fe"; export 
SSH_AGENT_PID="3519"; export SSH_AUTH_SOCK="/run/user/11588/keyring/ssh"; export 
PATH="/disk0/scratch/smonsees/yocto/workspace_3/poky/scripts/native-intercept:/disk0/scratch/smonsees/yocto/workspace_3/poky/scripts:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/usr/bin/x86_64-linux:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/usr/bin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/usr/sbin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/usr/bin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/sbin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/bin:/disk0/scratch/smonsees/yocto/workspace_3/poky/bitbake/bin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/hosttools";
 export HOME="/ede/smonsees"; /usr/bin/env wget -t 2 -T 30 --passive-ftp --no-check-certificate -P 
/disk0/scratch/smonsees/yocto/workspace_3/downloads/aarch64 'http://libarchive.org/downloads/libarchive-3.4.0.tar.gz' 
--progress=dot -v failed with exit code 3, output:
--2021-01-19 20:29:29--  http://libarchive.org/downloads/libarchive-3.4.0.tar.gz
Resolving libarchive.org (libarchive.org)... 99.84.191.71, 99.84.191.4, 
99.84.191.92, ...
Connecting to libarchive.org (libarchive.org)|99.84.191.71|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6908093 (6.6M) [application/octet-stream]
Saving to: 
‘/disk0/scratch/smonsees/yocto/workspace_3/downloads/aarch64/libarchive-3.4.0.tar.gz’

  0K 0%  290 =31s

2021-01-19 20:30:10 (290 B/s) - Connection closed at byte 8875. Retrying.

--2021-01-19 20:30:11--  (try: 2)  
http://libarchive.org/downloads/libarchive-3.4.0.tar.gz
Connecting to libarchive.org (libarchive.org)|99.84.191.71|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6908093 (6.6M) [application/octet-stream]
Saving to: 
‘/disk0/scratch/smonsees/yocto/workspace_3/downloads/aarch64/libarchive-3.4.0.tar.gz’

  0K 0% 0.00 =0.002s


Cannot write to 
‘/disk0/scratch/smonsees/yocto/workspace_3/downloads/aarch64/libarchive-3.4.0.tar.gz’
 (Success).

ERROR: libarchive-native-3.4.0-r0 do_fetch: Fetcher failure for URL: 
'http://libarchive.org/downloads/libarchive-3.4.0.tar.gz'. Unable to fetch URL 
from any source.
ERROR: Logfile of failure stored in: 
/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/temp/log.do_fetch.11418
ERROR: Task 
(virtual:native:/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/recipes-extended/libarchive/libarchive_3.4.0.bb:do_fetch)
 failed with exit code '1'
ERROR: qemu-native-4.1.0-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; 
export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-WGeN1VUN5f,guid=5f3398a95f5d5aa6a98efe74600732fe"; export 
SSH_AGENT_PID="3519"; export SSH_AUTH_SOCK="/run/user/11588/keyring/ssh"; export 

Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

[Richard Purdie]

On Tue, 2021-01-19 at 20:22 +, Monsees, Steven C (US) wrote:
> All but the following downloaded except these which failed (timing out):
> 
>  https://sourceware.org/elfutils/ftp/0.177/elfutils-0.177.tar.bz2
>  https://download.qemu.org/qemu-4.1.0.tar.xz
>  http://libarchive.org/downloads/libarchive-3.4.0.tar.gz
> 
> fyi... I am using zeus 3.0.4.

I did just check and these do seem to download ok here:

$ wget https://download.qemu.org/qemu-4.1.0.tar.xz
--2021-01-19 21:09:28--  https://download.qemu.org/qemu-4.1.0.tar.xz
Resolving download.qemu.org (download.qemu.org)... 172.99.69.163
Connecting to download.qemu.org (download.qemu.org)|172.99.69.163|:443... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 54001708 (52M) [application/x-xz]
Saving to: ‘qemu-4.1.0.tar.xz’

qemu-4.1.0.tar.xz 
100%[===>]  
51.50M  8.77MB/sin 6.3s

2021-01-19 21:09:35 (8.21 MB/s) - ‘qemu-4.1.0.tar.xz’ saved [54001708/54001708]

$ wget https://sourceware.org/elfutils/ftp/0.177/elfutils-0.177.tar.bz2
--2021-01-19 21:09:38--  
https://sourceware.org/elfutils/ftp/0.177/elfutils-0.177.tar.bz2
Resolving sourceware.org (sourceware.org)... 2620:52:3:1:0:246e:9693:128c, 
8.43.85.97
Connecting to sourceware.org 
(sourceware.org)|2620:52:3:1:0:246e:9693:128c|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8852413 (8.4M) [application/x-bzip2]
Saving to: ‘elfutils-0.177.tar.bz2’

elfutils-0.177.tar.bz2
100%[===>]  
 8.44M  5.87MB/sin 1.4s

2021-01-19 21:09:40 (5.87 MB/s) - ‘elfutils-0.177.tar.bz2’ saved 
[8852413/8852413]

$ wget http://libarchive.org/downloads/libarchive-3.4.0.tar.gz
--2021-01-19 21:09:46--  http://libarchive.org/downloads/libarchive-3.4.0.tar.gz
Resolving libarchive.org (libarchive.org)... 
2600:9000:21c7:e600:16:e6b0:f440:93a1, 2600:9000:21c7:9000:16:e6b0:f440:93a1, 
2600:9000:21c7:2e00:16:e6b0:f440:93a1, ...
Connecting to libarchive.org 
(libarchive.org)|2600:9000:21c7:e600:16:e6b0:f440:93a1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6908093 (6.6M) [application/octet-stream]
Saving to: ‘libarchive-3.4.0.tar.gz’

libarchive-3.4.0.tar.gz   
100%[===>]  
 6.59M  8.25MB/sin 0.8s

2021-01-19 21:09:47 (8.25 MB/s) - ‘libarchive-3.4.0.tar.gz’ saved 
[6908093/6908093]

$ sha256sum libarchive-3.4.0.tar.gz elfutils-0.177.tar.bz2  qemu-4.1.0.tar.xz 
8643d50ed40c759f5412a3af4e353cffbce4fdf3b5cf321cb72cacf06b2d825e  
libarchive-3.4.0.tar.gz
fa489deccbcae7d8c920f60d85906124c1989c591196d90e0fd668e3dc05042e  
elfutils-0.177.tar.bz2
656e60218689bdeec69903087fd7582d5d3e72238d02f4481d8dc6d79fd909c6  
qemu-4.1.0.tar.xz

Cheers,

Richard



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52054): https://lists.yoctoproject.org/g/yocto/message/52054
Mute This Topic: https://lists.yoctoproject.org/mt/79951152/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #kernel:https://lists.yoctoproject.org/g/yocto/mutehashtag/kernel
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

[Monsees, Steven C (US) via lists.yoctoproject.org]

This is the types of error I am seeing:


WARNING: qemu-native-4.1.0-r0 do_fetch: Failed to fetch URL 
https://download.qemu.org/qemu-4.1.0.tar.xz, attempting MIRRORS if available
WARNING: libarchive-native-3.4.0-r0 do_fetch: Failed to fetch URL 
http://libarchive.org/downloads/libarchive-3.4.0.tar.gz, attempting MIRRORS if 
available
ERROR: libarchive-native-3.4.0-r0 do_fetch: Fetcher failure: Fetch command 
export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export 
DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-WGeN1VUN5f,guid=5f3398a95f5d5aa6a98efe74600732fe";
 export SSH_AGENT_PID="3519"; export 
SSH_AUTH_SOCK="/run/user/11588/keyring/ssh"; export 
PATH="/disk0/scratch/smonsees/yocto/workspace_3/poky/scripts/native-intercept:/disk0/scratch/smonsees/yocto/workspace_3/poky/scripts:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/usr/bin/x86_64-linux:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/usr/bin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/usr/sbin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/usr/bin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/sbin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/recipe-sysroot-native/bin:/disk0/scratch/smonsees/yocto/workspace_3/poky/bitbake/bin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/hosttools";
 export HOME="/ede/smonsees"; /usr/bin/env wget -t 2 -T 30 --passive-ftp 
--no-check-certificate -P 
/disk0/scratch/smonsees/yocto/workspace_3/downloads/aarch64 
'http://libarchive.org/downloads/libarchive-3.4.0.tar.gz' --progress=dot -v 
failed with exit code 3, output:
--2021-01-19 20:29:29--  http://libarchive.org/downloads/libarchive-3.4.0.tar.gz
Resolving libarchive.org (libarchive.org)... 99.84.191.71, 99.84.191.4, 
99.84.191.92, ...
Connecting to libarchive.org (libarchive.org)|99.84.191.71|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6908093 (6.6M) [application/octet-stream]
Saving to: 
‘/disk0/scratch/smonsees/yocto/workspace_3/downloads/aarch64/libarchive-3.4.0.tar.gz’

 0K 0%  290 =31s

2021-01-19 20:30:10 (290 B/s) - Connection closed at byte 8875. Retrying.

--2021-01-19 20:30:11--  (try: 2)  
http://libarchive.org/downloads/libarchive-3.4.0.tar.gz
Connecting to libarchive.org (libarchive.org)|99.84.191.71|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6908093 (6.6M) [application/octet-stream]
Saving to: 
‘/disk0/scratch/smonsees/yocto/workspace_3/downloads/aarch64/libarchive-3.4.0.tar.gz’

 0K 0% 0.00 =0.002s


Cannot write to 
‘/disk0/scratch/smonsees/yocto/workspace_3/downloads/aarch64/libarchive-3.4.0.tar.gz’
 (Success).

ERROR: libarchive-native-3.4.0-r0 do_fetch: Fetcher failure for URL: 
'http://libarchive.org/downloads/libarchive-3.4.0.tar.gz'. Unable to fetch URL 
from any source.
ERROR: Logfile of failure stored in: 
/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/libarchive-native/3.4.0-r0/temp/log.do_fetch.11418
ERROR: Task 
(virtual:native:/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/recipes-extended/libarchive/libarchive_3.4.0.bb:do_fetch)
 failed with exit code '1'
ERROR: qemu-native-4.1.0-r0 do_fetch: Fetcher failure: Fetch command export 
PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export 
DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-WGeN1VUN5f,guid=5f3398a95f5d5aa6a98efe74600732fe";
 export SSH_AGENT_PID="3519"; export 
SSH_AUTH_SOCK="/run/user/11588/keyring/ssh"; export 

Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

[Monsees, Steven C (US) via lists.yoctoproject.org]

All but the following downloaded except these which failed (timing out):

 https://sourceware.org/elfutils/ftp/0.177/elfutils-0.177.tar.bz2
 https://download.qemu.org/qemu-4.1.0.tar.xz
 http://libarchive.org/downloads/libarchive-3.4.0.tar.gz

fyi... I am using zeus 3.0.4.

Steve

-Original Message-
From: yocto@lists.yoctoproject.org  On Behalf Of 
Monsees, Steven C (US) via lists.yoctoproject.org
Sent: Tuesday, January 19, 2021 9:25 AM
To: Richard Purdie ; 
yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.



From shell... I just checked the mega-manual, will rerun as described...

-Original Message-
From: Richard Purdie  
Sent: Tuesday, January 19, 2021 9:13 AM
To: Monsees, Steven C (US) ; 
yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


On Tue, 2021-01-19 at 14:08 +, Monsees, Steven C (US) wrote:
> That was set : export BB_GENERATE_MIRROR_TARBALLS=1

Just to be clear, where did you set that? In a .conf file? If so, you don't 
need the export bit. If it was in a shell it probably wouldn't work.

Also, you didn't answer my other question, did you refetch everything with that 
set?

Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52052): https://lists.yoctoproject.org/g/yocto/message/52052
Mute This Topic: https://lists.yoctoproject.org/mt/79951152/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #kernel:https://lists.yoctoproject.org/g/yocto/mutehashtag/kernel
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] insmod - huawei E3372h kernel module

[Zoran]

Zolee,

You need also to do on the target platform the following (very first time):

You must have header files, at minimum, in target's : /usr/src/$(uname -r)/

Or for yocto (AFAIK), maybe: /usr/src/kernel/$(uname -r)/

To prepare out-of-tree device driver compilation in /usr/src/kernel/$(uname -r)/

/usr/src/kernel/$(uname -r)$ make oldconfig && make prepare
/usr/src/kernel/$(uname -r)$ sudo make scripts prepare

Zee
___

On Tue, Jan 19, 2021 at 3:48 PM Zoltan Kerenyi Nagy
 wrote:
>
> My modeles.dep file looks like this on target:
>
> kernel/fs/nfs/flexfilelayout/nfs_layout_flexfiles.ko:
> kernel/crypto/echainiv.ko:
> kernel/crypto/gcm.ko:
> kernel/crypto/ccm.ko:
> kernel/crypto/ghash-generic.ko:
> kernel/drivers/char/hw_random/rng-core.ko:
> kernel/net/ipv4/tcp_bic.ko:
> kernel/net/ipv4/tcp_westwood.ko:
> kernel/net/ipv4/tcp_htcp.ko:
> kernel/net/bridge/br_netfilter.ko:
> kernel/net/wireless/cfg80211.ko: kernel/net/rfkill/rfkill.ko
> kernel/net/mac80211/mac80211.ko: kernel/net/wireless/cfg80211.ko 
> kernel/net/rfkill/rfkill.ko
> kernel/net/rfkill/rfkill.ko:
> kernel/net/rfkill/rfkill-regulator.ko: kernel/net/rfkill/rfkill.ko
> kernel/net/rfkill/rfkill-gpio.ko: kernel/net/rfkill/rfkill.ko
> extra/cdc-ncm.ko: extra/cdc-wdm.ko
> extra/hello.ko:
> extra/cdc-wdm.ko:
> extra/huawei_cdc_ncm.ko: extra/cdc-wdm.ko
>
> --
> Zolee
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52051): https://lists.yoctoproject.org/g/yocto/message/52051
Mute This Topic: https://lists.yoctoproject.org/mt/79498728/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Status WW03`21

[Stephen Jolley]

Current Dev Position: YP 3.3 M2 development

Next Deadline: 18th January 2021 YP 3.3 M2 build 

 

Next Team Meetings:

*   Bug Triage meeting Thursday Jan. 21st at 7:30am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Monthly Project Meeting Tuesday Feb. 2nd at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Weekly Engineering Sync Tuesday Jan. 19th at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   YP 3.3 M2 is due to be built once the currently queued patches are
stalised.
*   YP 3.1.5 has been built and is through QA and likely to be released
imminently after TSC review.
*   We're pleased to announce that Bootlin are going to be helping with
the build and integration work for the project, we'd like to welcome them on
board and also thank the projects member companies for making this possible.
*   Builds are continuing to show some intermittent instability.
Unfortunately we also suffered NAS issues and whilst there has been no data
loss, recovery of the system is slowing the autobuilder temporarily.
*   Intermittent autobuilder issues continue to occur and with more
invasive changes and higher rebuild rates, the numbers are increasing again.
You can see the list of failures we're continuing to see by searching for
the "AB-INT" tag in bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

 

Ways to contribute:

*   There are bugs identified as possible for newcomers to the project:

https://wiki.yoctoproject.org/wiki/Newcomers
*   There are bugs that are currently unassigned for YP 3.3. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enhan
cements.2FBugs
*   We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.

 

YP 3.3 Milestone Dates:

*   YP 3.3 M2 build date 2021/01/18
*   YP 3.3 M2 Release date 2021/01/29
*   YP 3.3 M3 build date 2021/03/01
*   YP 3.3 M3 Release date 2021/03/12
*   YP 3.3 M4 build date 2021/04/05
*   YP 3.3 M4 Release date 2021/04/30

 

Planned upcoming dot releases:

*   YP 3.1.5 is out of QA.
*   YP 3.2.2 build date 2021/02/08
*   YP 3.2.2 release date 2021/02/19
*   YP 3.1.6 build date 2021/02/22
*   YP 3.1.6 release date 2021/03/05
*   YP 3.1.7 build date 2021/03/22
*   YP 3.1.7 release date 2021/04/02

 

Tracking Metrics:

*   WDD 2634 (last week 2587) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1292 (last week 1298)
*   Patches in the Pending State: 503 (39%) [last week 503 (39%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52050): https://lists.yoctoproject.org/g/yocto/message/52050
Mute This Topic: https://lists.yoctoproject.org/mt/79954062/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] insmod - huawei E3372h kernel module

[Zoltan Kerenyi Nagy]

My modeles.dep file looks like this on target:

kernel/fs/nfs/flexfilelayout/nfs_layout_flexfiles.ko:
kernel/crypto/echainiv.ko:
kernel/crypto/gcm.ko:
kernel/crypto/ccm.ko:
kernel/crypto/ghash-generic.ko:
kernel/drivers/char/hw_random/rng-core.ko:
kernel/net/ipv4/tcp_bic.ko:
kernel/net/ipv4/tcp_westwood.ko:
kernel/net/ipv4/tcp_htcp.ko:
kernel/net/bridge/br_netfilter.ko:
kernel/net/wireless/cfg80211.ko: kernel/net/rfkill/rfkill.ko
kernel/net/mac80211/mac80211.ko: kernel/net/wireless/cfg80211.ko 
kernel/net/rfkill/rfkill.ko
kernel/net/rfkill/rfkill.ko:
kernel/net/rfkill/rfkill-regulator.ko: kernel/net/rfkill/rfkill.ko
kernel/net/rfkill/rfkill-gpio.ko: kernel/net/rfkill/rfkill.ko
extra/cdc-ncm.ko: extra/cdc-wdm.ko
extra/hello.ko:
extra/cdc-wdm.ko:
extra/huawei_cdc_ncm.ko: extra/cdc-wdm.ko

--
Zolee

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52049): https://lists.yoctoproject.org/g/yocto/message/52049
Mute This Topic: https://lists.yoctoproject.org/mt/79498728/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

[Monsees, Steven C (US) via lists.yoctoproject.org]

From shell... I just checked the mega-manual, will rerun as described...

-Original Message-
From: Richard Purdie  
Sent: Tuesday, January 19, 2021 9:13 AM
To: Monsees, Steven C (US) ; 
yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


On Tue, 2021-01-19 at 14:08 +, Monsees, Steven C (US) wrote:
> That was set : export BB_GENERATE_MIRROR_TARBALLS=1

Just to be clear, where did you set that? In a .conf file? If so, you don't 
need the export bit. If it was in a shell it probably wouldn't work.

Also, you didn't answer my other question, did you refetch everything with that 
set?

Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52048): https://lists.yoctoproject.org/g/yocto/message/52048
Mute This Topic: https://lists.yoctoproject.org/mt/79951152/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #kernel:https://lists.yoctoproject.org/g/yocto/mutehashtag/kernel
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

[Richard Purdie]

On Tue, 2021-01-19 at 14:08 +, Monsees, Steven C (US) wrote:
> That was set : export BB_GENERATE_MIRROR_TARBALLS=1

Just to be clear, where did you set that? In a .conf file? If so, you
don't need the export bit. If it was in a shell it probably wouldn't
work.

Also, you didn't answer my other question, did you refetch everything
with that set?

Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52047): https://lists.yoctoproject.org/g/yocto/message/52047
Mute This Topic: https://lists.yoctoproject.org/mt/79951152/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #kernel:https://lists.yoctoproject.org/g/yocto/mutehashtag/kernel
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

[Monsees, Steven C (US) via lists.yoctoproject.org]

That was set : export BB_GENERATE_MIRROR_TARBALLS=1

-Original Message-
From: yocto@lists.yoctoproject.org  On Behalf Of 
Richard Purdie
Sent: Tuesday, January 19, 2021 9:02 AM
To: Monsees, Steven C (US) ; 
yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


On Tue, 2021-01-19 at 13:42 +, Monsees, Steven C (US) via 
lists.yoctoproject.org wrote:
> When I generate MIRROR TARBALLS for my build it does not appear to 
> generate all the required tarballs…
>  
> I tested by tested by rebuilding with “BB_NO_NETWORK = 1”, and 
> received the following build Error (see below).
>  
> Is there something else I need to define to get all the required 
> tarballs in build ?

Did you set:

BB_GENERATE_MIRROR_TARBALLS = "1"

If not you need to set that. Also, you may need to refetch things initially to 
ensure all the right things are generated with that set.

Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52046): https://lists.yoctoproject.org/g/yocto/message/52046
Mute This Topic: https://lists.yoctoproject.org/mt/79951152/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #kernel:https://lists.yoctoproject.org/g/yocto/mutehashtag/kernel
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

[Richard Purdie]

On Tue, 2021-01-19 at 13:42 +, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:
> When I generate MIRROR TARBALLS for my build it does not appear to
> generate all the required tarballs…
>  
> I tested by tested by rebuilding with “BB_NO_NETWORK = 1”, and
> received the following build Error (see below).
>  
> Is there something else I need to define to get all the required
> tarballs in build ?

Did you set:

BB_GENERATE_MIRROR_TARBALLS = "1"

If not you need to set that. Also, you may need to refetch things
initially to ensure all the right things are generated with that set.

Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52045): https://lists.yoctoproject.org/g/yocto/message/52045
Mute This Topic: https://lists.yoctoproject.org/mt/79951152/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #kernel:https://lists.yoctoproject.org/g/yocto/mutehashtag/kernel
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] #yocto #kernel BB_GENERATE_MIRROR_TARBALLS

[Monsees, Steven C (US) via lists.yoctoproject.org]

When I generate MIRROR TARBALLS for my build it does not appear to generate all 
the required tarballs...

I tested by tested by rebuilding with "BB_NO_NETWORK = 1", and received the 
following build Error (see below).

Is there something else I need to define to get all the required tarballs in 
build ?

Thanks,
Steve

Initialising tasks: 100% 
|##| Time: 0:00:03
Sstate summary: Wanted 1412 Found 0 Missed 1412 Current 0 (0% match, 0% 
complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
ERROR: ncurses-native-6.1+20190803-r0 do_fetch: Network access disabled through 
BB_NO_NETWORK (or set indirectly due to use of BB_FETCH_PREMIRRORONLY) but 
access requested with command LANG=C git -c core.fsyncobjectfiles=0 clone 
--bare --mirror https://salsa.debian.org/debian/ncurses.git 
/disk0/scratch/smonsees/yocto/workspace_3/downloads/aarch64/git2/salsa.debian.org.debian.ncurses.git
 --progress (for url git://salsa.debian.org/debian/ncurses.git;protocol=https)
ERROR: Logfile of failure stored in: 
/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/ncurses-native/6.1+20190803-r0/temp/log.do_fetch.16824
ERROR: Task 
(virtual:native:/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/recipes-core/ncurses/ncurses_6.1+20190803.bb:do_fetch)
 failed with exit code '1'
NOTE: Tasks Summary: Attempted 99 tasks of which 0 didn't need to be rerun and 
1 failed.

Summary: 1 task failed:
  
virtual:native:/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/recipes-core/ncurses/ncurses_6.1+20190803.bb:do_fetch

ncurses_6.1+20190803.bb:

require ncurses.inc

SRC_URI += "file://0001-tic-hang.patch \
file://0002-configure-reproducible.patch \
file://config.cache \
file://0001-ncurses-selective-backport-of-20191012-patch.patch \
"
# commit id corresponds to the revision in package version
SRCREV = "3c9b2677c96c645496997321bf2fe465a5e7e21f"
S = "${WORKDIR}/git"
EXTRA_OECONF += "--with-abi-version=5 --cache-file=${B}/config.cache"
UPSTREAM_CHECK_GITTAGREGEX = "(?P\d+(\.\d+)+(\+\d+)*)"

CVE_VERSION = "6.1.${@d.getVar("PV").split('+')[1]}"

/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/x86_64-linux/ncurses-native/6.1+20190803-r0/temp/log.do_fetch.16824:

DEBUG: Executing python function extend_recipe_sysroot
NOTE: Direct dependencies are []
NOTE: Installed into sysroot: []
NOTE: Skipping as already exists in sysroot: []
DEBUG: Python function extend_recipe_sysroot finished
DEBUG: Executing python function do_fetch
DEBUG: Executing python function base_do_fetch
DEBUG: Trying PREMIRRORS
DEBUG: For url ['git', 'salsa.debian.org', '/debian/ncurses.git', '', '', 
OrderedDict([('protocol', 'https')])] comparing ['git', '.*', '/.*', '', '', 
OrderedDict()] to ['file', '', '//ede/tms/yocto/zeus/downloads/aarch64', '', 
'', OrderedDict()]
DEBUG: For url git://salsa.debian.org/debian/ncurses.git;protocol=https 
returning 
file:///ede/tms/yocto/zeus/downloads/aarch64/git2_salsa.debian.org.debian.ncurses.git.tar.gz
DEBUG: For url ['file', '', 
'/ede/tms/yocto/zeus/downloads/aarch64/git2_salsa.debian.org.debian.ncurses.git.tar.gz',
 '', '', OrderedDict()] comparing ['ftp', '.*', '/.*', '', '', OrderedDict()] 
to ['file', '', '//ede/tms/yocto/zeus/downloads/aarch64', '', '', OrderedDict()]
DEBUG: For url ['file', '', 
'/ede/tms/yocto/zeus/downloads/aarch64/git2_salsa.debian.org.debian.ncurses.git.tar.gz',
 '', '', OrderedDict()] comparing ['http', '.*', '/.*', '', '', OrderedDict()] 
to ['file', '', '//ede/tms/yocto/zeus/downloads/aarch64', '', '', OrderedDict()]
DEBUG: For url ['file', '', 
'/ede/tms/yocto/zeus/downloads/aarch64/git2_salsa.debian.org.debian.ncurses.git.tar.gz',
 '', '', OrderedDict()] comparing ['https', '.*', '/.*', '', '', OrderedDict()] 
to ['file', '', '//ede/tms/yocto/zeus/downloads/aarch64', '', '', OrderedDict()]
DEBUG: For url ['git', 'salsa.debian.org', '/debian/ncurses.git', '', '', 
OrderedDict([('protocol', 'https')])] comparing ['ftp', '.*', '/.*', '', '', 
OrderedDict()] to ['file', '', '//ede/tms/yocto/zeus/downloads/aarch64', '', 
'', OrderedDict()]
DEBUG: For url ['git', 'salsa.debian.org', '/debian/ncurses.git', '', '', 
OrderedDict([('protocol', 'https')])] comparing ['http', '.*', '/.*', '', '', 
OrderedDict()] to ['file', '', '//ede/tms/yocto/zeus/downloads/aarch64', '', 
'', OrderedDict()]
DEBUG: For url ['git', 'salsa.debian.org', '/debian/ncurses.git', '', '', 
OrderedDict([('protocol', 'https')])] comparing ['https', '.*', '/.*', '', '', 
OrderedDict()] to ['file', '', '//ede/tms/yocto/zeus/downloads/aarch64', '', 
'', OrderedDict()]
DEBUG: Mirror fetch failure for url 
file:///ede/tms/yocto/zeus/downloads/aarch64/git2_salsa.debian.org.debian.ncurses.git.tar.gz
 (original url: git://salsa.debian.org/debian/ncurses.git;protocol=https)
DEBUG: Fetcher failure: Unable to find file 

Re: [yocto] insmod - huawei E3372h kernel module

[Zoltan Kerenyi Nagy]

Here is an error message:

modprobe - insmod ( http://paste.ubuntu.com/p/hMWBQSDKcF/ )
--
Zolee

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52043): https://lists.yoctoproject.org/g/yocto/message/52043
Mute This Topic: https://lists.yoctoproject.org/mt/79498728/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] insmod - huawei E3372h kernel module

[Zoran]

Forwarded to r...@burtonini.com .

Thank you,
Zoran/Zee

-- Forwarded message -
From: Zoran via lists.yoctoproject.org

Date: Tue, Jan 19, 2021 at 2:23 PM
Subject: Re: [yocto] insmod - huawei E3372h kernel module
To: Zoltan Kerenyi Nagy , Burton, Ross

Cc: Yocto-mailing-list 

> As far as I understand the KERNEL_MODULE_AUTOLOAD directive will
> populate the /etc/modules file, however, after bitbaking, on the device there
> is no /etc/modules file or folder but another folder:
>
> root@barix-ipam400:~# ls /lib/modules/4.10.0/extra/
> cdc-ncm.ko cdc-wdm.ko hello.ko   huawei_cdc_ncm.ko

Hello Ross,

Any comment from you on the target module configuration?

My understanding is the same, the YOCTO building system should somehow
create targets' /etc/modules file, since every reboot should repeat
the order of modules loading (read from the same).

Thank you,
Zoran
___

On Tue, Jan 19, 2021 at 2:00 PM Zoltan Kerenyi Nagy
 wrote:
>
> I don have a recipie for /etc/modules
>
> To my understanding this order will cause the load:
>
> KERNEL_MODULE_AUTOLOAD += "ncm_driver"KERNEL_MODULE_PROBECONF += 
> "ncm_driver"cdc_ncm = "options ncm_driver 
> iProduct=USB_Host_Driver_for_Network_Control_Model iManufacturer=NCM"
>
> KERNEL_MODULE_AUTOLOAD += "wmc_device_managment"KERNEL_MODULE_PROBECONF += 
> "wmc_device"cdc_wdm = "options wmc_device 
> iProduct=USB_CDC_WCM_Device_Management iManufacturer=WMC"
>
> KERNEL_MODULE_AUTOLOAD += "lte"KERNEL_MODULE_PROBECONF += "lte"huawei_cdc_ncm 
> = "options lte iProduct=E3372h iManufacturer=Huawei"
>
> As far as I understand the KERNEL_MODULE_AUTOLOAD directive will populate the 
> /etc/modules file, however, after bitbaking, on the device there is no 
> /etc/modules file or folder but another folder:
>
> root@barix-ipam400:~# ls /lib/modules/4.10.0/extra/
> cdc-ncm.ko cdc-wdm.ko hello.ko   huawei_cdc_ncm.ko
>
>
>
> --
> Zolee
>
>



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52042): https://lists.yoctoproject.org/g/yocto/message/52042
Mute This Topic: https://lists.yoctoproject.org/mt/79498728/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] insmod - huawei E3372h kernel module

[Zoran]

> As far as I understand the KERNEL_MODULE_AUTOLOAD directive will
> populate the /etc/modules file, however, after bitbaking, on the device there
> is no /etc/modules file or folder but another folder:
>
> root@barix-ipam400:~# ls /lib/modules/4.10.0/extra/
> cdc-ncm.ko cdc-wdm.ko hello.ko   huawei_cdc_ncm.ko

Hello Ross,

Any comment from you on the target module configuration?

My understanding is the same, the YOCTO building system should somehow
create targets' /etc/modules file, since every reboot should repeat
the order of modules loading (read from the same).

Thank you,
Zoran
___

On Tue, Jan 19, 2021 at 2:00 PM Zoltan Kerenyi Nagy
 wrote:
>
> I don have a recipie for /etc/modules
>
> To my understanding this order will cause the load:
>
> KERNEL_MODULE_AUTOLOAD += "ncm_driver"KERNEL_MODULE_PROBECONF += 
> "ncm_driver"cdc_ncm = "options ncm_driver 
> iProduct=USB_Host_Driver_for_Network_Control_Model iManufacturer=NCM"
>
> KERNEL_MODULE_AUTOLOAD += "wmc_device_managment"KERNEL_MODULE_PROBECONF += 
> "wmc_device"cdc_wdm = "options wmc_device 
> iProduct=USB_CDC_WCM_Device_Management iManufacturer=WMC"
>
> KERNEL_MODULE_AUTOLOAD += "lte"KERNEL_MODULE_PROBECONF += "lte"huawei_cdc_ncm 
> = "options lte iProduct=E3372h iManufacturer=Huawei"
>
> As far as I understand the KERNEL_MODULE_AUTOLOAD directive will populate the 
> /etc/modules file, however, after bitbaking, on the device there is no 
> /etc/modules file or folder but another folder:
>
> root@barix-ipam400:~# ls /lib/modules/4.10.0/extra/
> cdc-ncm.ko cdc-wdm.ko hello.ko   huawei_cdc_ncm.ko
>
>
>
> --
> Zolee
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52041): https://lists.yoctoproject.org/g/yocto/message/52041
Mute This Topic: https://lists.yoctoproject.org/mt/79498728/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] preempt-rt build failure

[Bruce Ashfield]

On Tue, Jan 19, 2021 at 3:26 AM He Zhe  wrote:
>
> Hi Bruce,
>
> The following revert breaks preempt-rt build.
>

It fixes the build here.

That 5.10-stable change really shouldn't even be in -stable .. but yet
it is. It broke my -rt test builds, and rather than implementing a
slowpath for this, the revert fixed the build.

But I haven't completed those changes yet, they are still going
through AB testing, so I will have more changes before my SRCREVs are
sent.

Bruce

> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?h=v5.10/standard/preempt-rt/base=491a86a368de0c75f18b85d01a3390dc2811c343
>
> tmp-glibc/work-shared/qemux86-64/kernel-source/kernel/locking/rwsem.c:1517:54:
>  error: implicit declaration of function '__down_read_interruptible'; did you 
> mean 'down_read_interruptible'? [-Werror=implicit-function-declaration]
>
>
> Zhe



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9393): 
https://lists.yoctoproject.org/g/linux-yocto/message/9393
Mute This Topic: https://lists.yoctoproject.org/mt/79947169/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] insmod - huawei E3372h kernel module

[Zoltan Kerenyi Nagy]

I don have a recipie for /etc/modules

To my understanding this order will cause the load:
KERNEL_MODULE_AUTOLOAD += "ncm_driver"KERNEL_MODULE_PROBECONF += 
"ncm_driver"cdc_ncm = "options ncm_driver 
iProduct=USB_Host_Driver_for_Network_Control_Model iManufacturer=NCM" 
KERNEL_MODULE_AUTOLOAD += "wmc_device_managment"KERNEL_MODULE_PROBECONF += 
"wmc_device"cdc_wdm = "options wmc_device 
iProduct=USB_CDC_WCM_Device_Management iManufacturer=WMC" 
KERNEL_MODULE_AUTOLOAD += "lte"KERNEL_MODULE_PROBECONF += "lte"huawei_cdc_ncm = 
"options lte iProduct=E3372h iManufacturer=Huawei"

As far as I understand the KERNEL_MODULE_AUTOLOAD directive will populate the 
/etc/modules file, however, after bitbaking, on the device there is no 
/etc/modules file or folder but another folder:

root@barix-ipam400:~# ls /lib/modules/4.10.0/extra/
cdc-ncm.ko cdc-wdm.ko hello.ko   huawei_cdc_ncm.ko --
Zolee

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52040): https://lists.yoctoproject.org/g/yocto/message/52040
Mute This Topic: https://lists.yoctoproject.org/mt/79498728/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] preempt-rt build failure

[He Zhe]

Hi Bruce,

The following revert breaks preempt-rt build.

http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?h=v5.10/standard/preempt-rt/base=491a86a368de0c75f18b85d01a3390dc2811c343

tmp-glibc/work-shared/qemux86-64/kernel-source/kernel/locking/rwsem.c:1517:54: 
error: implicit declaration of function '__down_read_interruptible'; did you 
mean 'down_read_interruptible'? [-Werror=implicit-function-declaration]


Zhe

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9391): 
https://lists.yoctoproject.org/g/linux-yocto/message/9391
Mute This Topic: https://lists.yoctoproject.org/mt/79947169/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

回复: [linux-yocto] Question on CONFIG_FW_LOADER warning

[Zhang, Qiang]

> > > > 
> > > > 发件人: Bruce Ashfield 
> > > > 发送时间: 2021年1月15日 23:10
> > > > 收件人: Zhang, Qiang
> > > > 抄送: linux-yocto@lists.yoctoproject.org
> > > > 主题: Re: Question on CONFIG_FW_LOADER warning
> > > >
> > > > On Fri, Jan 15, 2021 at 3:43 AM Zhang, Qiang
>  wrote:
> > > > >
> > > > > Hello Brue
> > > > >
> > > > > [NOTE]: 'CONFIG_FW_LOADER' last val (n) and .config val (y) do not
> match
> > > > > [INFO]: CONFIG_FW_LOADER : y ## .config: 1567
> > > > > :configs/v5.4/ktypes/base/base.cfg (n)
> > > > >
> > > > > I find CONFIG_FW_LOADER option be set "n" in base.cfg, but in
> > > > > features/firmware/firmware.cfg and cfg/x86.cfg be enable in
> > > > > 5.4, 5.8 kernel, the CONFIG_FW_LOADER be set "n"  in base.cfg
> > > > > need to open it？
> > > >
> > > > >That won't solve all the cases. Tiny and standard end up with
> > > > >different values for that config, due to changing dependencies.
> > > > >
> > > > >I put in tweaks in 5.10/master to change the default, and then
> > > > >override it on a per-BSP basis (as well as in the feature fragment).
> > > > >
> > > > >Which combination of board/kernel are you seeing the warning ?
> > > >
> > > > Hello Bruce
> > > >
> > > > BSP is intel-x86-64, kernel is v5.4/standard/preempt-rt
> > >
> > > Thanks,
> > >
> > > I'll have a look at this today.
> >
> > >I just realized that I don't have access to a layer that defines that
> > >machine ? Is there a public layer that I can use ?
> > >
> > >I did configure and check qemux86-64 5.4 -rt and didn't get the
> > >warning, so I do need the details for the specific machine definition.
> >
> > Hello Bruce
> >
> > this is my config
> >
> > --accept-eula=yes --dl-layers --machines intel-x86-64 --distro wrlinux
>
> >That's the problem .. I don't have those layers for me to test against
> >just my pure yocto environment.
> >
> >I could craft my own machine configuration in a local layer, but it is
> >easier if there's a public machine layer that I can use (I don't think
> >there is, but I wanted to ask).
>
>   Hello Bruce
>
>   Sorry I forgot to say
>   Symbols currently y-selecting this symbol:
>   - MICROCODE
>   - MICROCODE_INTEL
>   - R8169
>
>thease config option be set enable, and be set CONFIG_FW_LOADER to 'y'.
>need to turn these options on in your environment

>This issue only happens on preempt-rt kernel.
>One method to fix it is that you can add "include 
>features/firmware/firmware.scc"
>in bsp/intel-x86/intel-x86-64-preempt-rt.scc.
>
Thank you Yongxin, I'll modify the test according to your suggestion.


>
>Thanks,
>Yongxin


>
>   Qiang
>
> >Bruce
>
> >
> > echo 'BB_NUMBER_PARSE_THREADS ?= "28"'
> > echo 'BB_NUMBER_THREADS ?= "28"'
> > echo 'PARALLEL_MAKE ?= "-j 28"'
> > echo 'BB_STRICT_CHECKSUM = "1"'
> > echo 'IMAGE_INSTALL_append = " lmsensors i2c-tools alsa-utils util-linux
> pciutils usbutils"'
> > echo 'IMAGE_FSTYPES_remove = " live hddimg iso"'
> > echo 'IMAGE_INSTALL_remove = "ceph"'
> > echo 'IMAGE_INSTALL_append = " bison flex bc xz elfutils-dev openssl-dev
> systemd-analyze memtester"'
> > echo 'IMAGE_INSTALL_append = " iperf3 util-linux pciutils usbutils
> netcat perf git fio"'
> > echo 'IMAGE_INSTALL_append = " schedtool-dl lttng-modules lttng-tools
> lttng-ust babeltrace"'
> > echo 'IMAGE_INSTALL_append = " iproute2 gdb busybox iproute2-tc systemd-
> analyze"'
> > echo 'PNWHITELIST_openembedded-layer += "fio"'
> > echo 'PNWHITELIST_openembedded-layer += "numactl"'
> > echo 'PNWHITELIST_realtime += "schedtool-dl"'
> > echo 'PNWHITELIST_openembedded-layer += "memtester"'
> > echo 'BB_NO_NETWORK_pn-memtester = "0"'
> > echo 'PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"'
> >
> > bitbake virtual/kernel
> >
> >
> > >Bruce
> >
> > >
> > > Bruce
> > >
> > > >
> > > > Cherrs
> > > >
> > > > >
> > > > >Bruce
> > > >
> > > > >
> > > > > Cheers
> > > > >
> > > >
> > > >
> > > > --
> > > > - Thou shalt not follow the NULL pointer, for chaos and madness
> > > > await thee at its end
> > > > - "Use the force Harry" - Gandalf, Star Trek II
> > >
> > >
> > >
> > > --
> > > - Thou shalt not follow the NULL pointer, for chaos and madness
> > > await thee at its end
> > > - "Use the force Harry" - Gandalf, Star Trek II
> > >
> > >
> > >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
>
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end
> - "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9390): 
https://lists.yoctoproject.org/g/linux-yocto/message/9390
Mute This Topic: https://lists.yoctoproject.org/mt/79947152/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-