FAQ - Frequently Asked Questions - Revision history

Ilko: Add mask of systemd-oomd

2024-02-15T12:33:39Z

Add mask of systemd-oomd

← Older revision		Revision as of 14:33, 15 February 2024
Line 8:		Line 8:
	The simplest solution is to disable the OOM daemon:		The simplest solution is to disable the OOM daemon:
	$ sudo systemctl disable --now systemd-oomd		$ sudo systemctl disable --now systemd-oomd
			$ sudo systemctl mask systemd-oomd

	If the Yocto building is killed by OOM, and then again started, some tasks can fail.<br>		If the Yocto building is killed by OOM, and then again started, some tasks can fail.<br>

Ilko: Add "Why when building Yocto, sometimes the Ubuntu Terminal is closed without any notification"

2024-01-29T10:51:32Z

Add "Why when building Yocto, sometimes the Ubuntu Terminal is closed without any notification"

← Older revision		Revision as of 12:51, 29 January 2024
Line 1:		Line 1:
	__TOC__		__TOC__

			== Why when building Yocto, sometimes the Ubuntu Terminal is closed without any notification? ==
			Ubuntu 22.04 comes with the systemd-oomd service enabled by default, <br>
			which limits the RAM of a terminal application to no more than 50% by default. <br>
			If a terminal application uses more than 50% RAM, the OOM daemon kills the entire process tree, <br>
			so even the terminal hosting the processes that were killed will suddenly vanish.<br>
			The simplest solution is to disable the OOM daemon:
			$ sudo systemctl disable --now systemd-oomd

			If the Yocto building is killed by OOM, and then again started, some tasks can fail.<br>
			For example:<br>
			Summary: 3 tasks failed:
			/mnt/960GB/nxp/yocto-micledore/sources/poky/meta/recipes-devtools/binutils/binutils_2.40.bb:do_compile
			/mnt/960GB/nxp/yocto-micledore/sources/poky/meta/recipes-devtools/gdb/gdb_13.2.bb:do_compile
			/mnt/960GB/nxp/yocto-micledore/sources/poky/meta/recipes-devtools/gcc/gcc_12.3.bb:do_compile

			In this case, the failed tasks must be cleaned:
			$ bitbake -c cleanall binutils gdb gcc
			$ bitbake imx-image-core


	== How to rebase the Ronetix U-BOOT git repository? ==		== How to rebase the Ronetix U-BOOT git repository? ==

Ilko: Update

2024-01-22T08:01:48Z

Update

← Older revision		Revision as of 10:01, 22 January 2024
Line 3:		Line 3:
	== How to rebase the Ronetix U-BOOT git repository? ==		== How to rebase the Ronetix U-BOOT git repository? ==
	Here are the steps to rebase the U-BOOT repository:		Here are the steps to rebase the U-BOOT repository:
	$ git clone https://github.com/~~nxp-imx~~/~~uboot~~-~~imx~~.git		$ git clone https://github.com/ronetix/u-boot.git
	$ cd u-boot~~-imx~~		$ cd u-boot
	$ git remote add https://github.com/~~ronetix~~/u-~~boot~~.git		$ git remote add nxp https://github.com/nxp-imx/uboot-imx.git
	$ git checkout remotes/~~ronetix~~/lf_v2023.04 -b lf_v2023.04		$ git fetch nxp
	$ git rebase ~~origin~~/lf_v2023.04		$ git checkout remotes/origin/lf_v2023.04 -b lf_v2023.04
			$ git rebase nxp/lf_v2023.04

	If there are some conflicts, resolve them manually and ~~then~~ commit.		If there are some conflicts, resolve them manually, for example:
			$ vim arch/arm/mach-imx/imx9/Kconfig # fix and save
			$ git add arch/arm/mach-imx/imx9/Kconfig
			$ git commit -m "mach-imx/imx9/Kconfig : resolve merge conflict"
			$ git rebase --continue

Ilko: Add TOC

2024-01-19T15:50:36Z

Add TOC

← Older revision		Revision as of 17:50, 19 January 2024
Line 1:		Line 1:
			__TOC__

	== How to rebase the Ronetix U-BOOT git repository? ==		== How to rebase the Ronetix U-BOOT git repository? ==
	Here are the steps to rebase the U-BOOT repository:		Here are the steps to rebase the U-BOOT repository:

Ilko: Ilko moved page FAQ How to rebase U-BOOT git repository to FAQ - Frequently Asked Questions

2024-01-19T15:50:05Z

Ilko moved page FAQ How to rebase U-BOOT git repository to FAQ - Frequently Asked Questions

← Older revision	Revision as of 17:50, 19 January 2024
(No difference)

Ilko: Initial create

2024-01-19T15:47:43Z

Initial create

New page

== How to rebase the Ronetix U-BOOT git repository? ==
Here are the steps to rebase the U-BOOT repository:
$ git clone https://github.com/nxp-imx/uboot-imx.git
$ cd u-boot-imx
$ git remote add https://github.com/ronetix/u-boot.git
$ git checkout remotes/ronetix/lf_v2023.04 -b lf_v2023.04
$ git rebase origin/lf_v2023.04

If there are some conflicts, resolve them manually and then commit.