RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Copyright 2016 RDK Management, LLC. All rights reserved. The contents of this document are RDK Management, LLC Proprietary and Confidential and may not be distributed or otherwise disclosed without prior written permission of RDK Management, LLC.
NOTE: Observing fetch errors in VMs with Ubuntu14.x. Thus, suggesting to use VMs with Ubuntu16.x or higher.
Note: Cloning the code before login once to code.rdkcentral.com, user would get the Authentication error, even though the account is in good standing and has all the required access. Please login to code.rdkcentral.com before attempting to clone.
Create workspace directory
mkdir <workspace dir> cd <workspace dir>
Follow below instructions to create build with external sources
repo init -u https://code.rdkcentral.com/r/manifests -m rdkb-turris-extsrc.xml -b dunfell repo sync -j4 --no-clone-bundle MACHINE=turris_5.10 source meta-turris/setup-environment bitbake rdk-generic-broadband-5.10-kernel-image
repo init -u https://code.rdkcentral.com/r/manifests -m rdkb-turris-nosrc.xml -b dunfell repo sync -j4 --no-clone-bundle MACHINE=turris_5.10 source meta-turris/setup-environment bitbake rdk-generic-broadband-5.10-kernel-image
Note: The kernel Image and root filesystem will be placed under <workspace dir>/build-turris/tmp/deploy/images/turris_5.10 folder
Error/ Issues | Layer and Recipe | Fix | |
---|---|---|---|
1 | [FAILED] Failed to mount NFSD configuration filesystem. See 'systemctl status proc-fs-nfsd.mount' for details. [DEPEND] Dependency failed for NFS Mount Daemon. [DEPEND] Dependency failed for NFS server and services. | linux-kernel 5.10 boot-up issue | |
2 | [ 4.425921] mv88e6085 f1072004.mdio-mii:10: this chip requires CONFIG_NET_DSA_MV88E6XXX_GLOBAL2 enabled [ 4.435356] mv88e6085: probe of f1072004.mdio-mii:10 failed with error -95 | linux-kernel 5.10 boot-up issue | |
3 | [FAILED] Failed to start network@bond0.service. See 'systemctl status network@bond0.service' for details. [FAILED] Failed to start network@dummy0.service. See 'systemctl status network@dummy0.service' for details. [FAILED] Failed to start network@eql.service. See 'systemctl status network@eql.service' for details. [FAILED] Failed to start network@erspan0.service. See 'systemctl status network@erspan0.service' for details. [FAILED] Failed to start network@eth0.service. See 'systemctl status network@eth0.service' for details. [FAILED] Failed to start network@eth1.service. See 'systemctl status network@eth1.service' for details. [FAILED] Failed to start network@eth2.service. See 'systemctl status network@eth2.service' for details. [FAILED] Failed to start network@gre0.service. See 'systemctl status network@gre0.service' for details. [FAILED] Failed to start network@gretap0.service. See 'systemctl status network@gretap0.service' for details. [FAILED] Failed to start network@ifb0.service. See 'systemctl status network@ifb0.service' for details. [FAILED] Failed to start network@ifb1.service. See 'systemctl status network@ifb1.service' for details. [FAILED] Failed to start network@lan0.service. See 'systemctl status network@lan0.service' for details. [FAILED] Failed to start network@lan1.service. See 'systemctl status network@lan1.service' for details. [FAILED] Failed to start network@lan2.service. See 'systemctl status network@lan2.service' for details. [FAILED] Failed to start network@lan3.service. See 'systemctl status network@lan3.service' for details. [FAILED] Failed to start network@lan4.service. See 'systemctl status network@lan4.service' for details. [FAILED] Failed to start network@teql0.service. See 'systemctl status network@teql0.service' for details. [FAILED] Failed to start network@tunl0.service. See 'systemctl status network@tunl0.service' for details. | linux-kernel 5.10 boot-up issue |
Basic sanity with kernel5.10 image is failing. The Validation is taken for upcoming sprint.