Searched full:init (Results 1 – 25 of 245) sorted by relevance
12345678910
| /Documentation/admin-guide/ |
| D | init.rst | 1 Explaining the "No working init found." boot hang message
7 (listed roughly in order of execution) to load the init binary.
12 2) **init binary doesn't exist on rootfs**: Make sure you have the correct
24 dependencies of the init binary such as ``/lib/ld-linux.so.2`` missing or
25 broken. Use ``readelf -d <INIT>|grep NEEDED`` to find out which libraries
35 execution. To find out more, add code ``to init/main.c`` to display
39 (after all loading the init binary is a CRITICAL and hard transition step
|
| D | initrd.rst | 35 5) /sbin/init is executed (this can be any valid executable, including
37 init can do).
38 6) init mounts the "real" root file system
39 7) init places the root file system at the root directory using the
41 8) init execs the ``/sbin/init`` on the new root filesystem, performing
150 environment. Don't forget the most important file, ``/sbin/init``
152 .. note:: ``/sbin/init`` permissions must include "x" (execute).
157 # chroot /mnt /sbin/init
174 only add a symbolic link from ``/sbin/init`` to ``/bin/sh``. Alternatively, you
213 When finished with its duties, init typically changes the root device
[all …]
|
| D | dynamic-debug-howto.rst | 41 init/main.c:1179 [main]initcall_blacklist =_ "blacklisting initcall %s\012
42 init/main.c:1218 [main]initcall_blacklisted =_ "initcall %s blacklisted\012"
43 init/main.c:1424 [main]run_init_process =_ " with arguments:\012"
44 init/main.c:1426 [main]run_init_process =_ " %s\012"
45 init/main.c:1427 [main]run_init_process =_ " with environment:\012"
46 init/main.c:1429 [main]run_init_process =_ " %s\012"
62 init/main.c:1424 [main]run_init_process =p " with arguments:\012"
63 init/main.c:1426 [main]run_init_process =p " %s\012"
64 init/main.c:1427 [main]run_init_process =p " with environment:\012"
65 init/main.c:1429 [main]run_init_process =p " %s\012"
[all …]
|
| /Documentation/translations/zh_TW/admin-guide/ |
| D | init.rst | 5 :Original: :doc:`../../../admin-guide/init`
12 解釋“No working init found.”啓動掛起消息
21 本文檔提供了加載初始化二進制（init binary）失敗的一些高層級原因（大致按執行
39 ``readelf -d <INIT>|grep NEEDED`` 找出需要哪些庫。
46 它能成功執行。要了解更多信息，請將代碼添加到 ``init/main.c`` 以顯示
|
| D | bootconfig.rst | 211 值對都將直接傳遞給內核命令行。此外， ``init`` 下的鍵值對將通過命令行傳遞給
216 [bootconfig params][cmdline params] -- [bootconfig init params][cmdline init params]
223 init {
|
| /Documentation/translations/zh_CN/admin-guide/ |
| D | init.rst | 3 :Original: :doc:`../../../admin-guide/init`
9 解释“No working init found.”启动挂起消息
18 本文档提供了加载初始化二进制（init binary）失败的一些高层级原因（大致按执行
36 ``readelf -d <INIT>|grep NEEDED`` 找出需要哪些库。
43 它能成功执行。要了解更多信息，请将代码添加到 ``init/main.c`` 以显示
|
| D | bootconfig.rst | 211 值对都将直接传递给内核命令行。此外， ``init`` 下的键值对将通过命令行传递给
216 [bootconfig params][cmdline params] -- [bootconfig init params][cmdline init params]
223 init {
|
| /Documentation/driver-api/early-userspace/ |
| D | early_userspace_support.rst | 113 - Almost all of init/do_mounts* (the beginning of this is already in
133 initrd. init/main.c:init() will call prepare_namespace() to mount the
134 final root filesystem, based on the root= option and optional init= to run
135 some other init binary than listed at the end of init/main.c:init().
146 initrd format, an cpio archive. It must be called "/init". This binary
149 To maintain backwards compatibility, the /init binary will only run if it
151 init/main.c:init() will run prepare_namespace() to mount the final root
152 and exec one of the predefined init binaries.
|
| /Documentation/devicetree/bindings/net/ |
| D | mdio-mux-gpio.yaml | 56 marvell,reg-init = <3 0x10 0 0x5777>,
65 marvell,reg-init = <3 0x10 0 0x5777>,
74 marvell,reg-init = <3 0x10 0 0x5777>,
83 marvell,reg-init = <3 0x10 0 0x5777>,
99 marvell,reg-init = <3 0x10 0 0x5777>,
108 marvell,reg-init = <3 0x10 0 0x5777>,
117 marvell,reg-init = <3 0x10 0 0x5777>,
126 marvell,reg-init = <3 0x10 0 0x5777>,
|
| D | broadcom-bcm87xx.txt | 9 - broadcom,c45-reg-init : one of more sets of 4 cells. The first cell
28 broadcom,c45-reg-init = <1 0xc808 0xff8f 0x70>;
|
| D | qcom,ipa.yaml | 146 modem-init:
179 # If qcom,gsi-loader is present, modem-init must not be present
185 modem-init: false
199 # If modem-init is not present, the AP loads GSI firmware, and
204 - modem-init
|
| /Documentation/filesystems/ |
| D | ramfs-rootfs-initramfs.rst | 80 same reason you can't kill the init process; rather than having special code
96 checks to see if rootfs contains a file "init", and if so it executes it as PID
97 1. If found, this init process is responsible for bringing the system the
99 any). If rootfs does not contain an init program after the embedded cpio
101 to locate and mount a root partition, then exec some variant of /sbin/init
117 - The program run by the old initrd (which was called /initrd, not /init) did
118 some setup and then returned to the kernel, while the init program from
119 initramfs is not expected to return to the kernel. (If /init needs to hand
120 off control it can overmount / with a new root device and exec another init
128 stdin/stdout/stderr to the new /dev/console, and exec the new init.
[all …]
|
| /Documentation/devicetree/bindings/fpga/ |
| D | xlnx,fpga-selectmap.yaml | 47 init-gpios:
70 - init-gpios
81 init-gpios = <&gpio5 8 GPIO_ACTIVE_LOW>;
|
| D | xlnx,fpga-slave-serial.yaml | 49 init-b-gpios:
60 - init-b-gpios
76 init-b-gpios = <&gpio0 28 GPIO_ACTIVE_LOW>;
|
| D | lattice,sysconfig.yaml | 34 init-gpios:
78 init-gpios = <&gpio3 3 GPIO_ACTIVE_LOW>;
|
| /Documentation/devicetree/bindings/phy/ |
| D | rockchip,rk3588-hdptx-phy.yaml | 40 - description: INIT reset line
50 - const: init
91 reset-names = "phy", "apb", "init", "cmn", "lane", "ropll", "lcpll";
|
| D | qcom,usb-hsic-phy.yaml | 38 - const: init
64 pinctrl-names = "init", "default";
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ibm,occ-hwmon.yaml | 24 ibm,no-poll-on-init:
38 ibm,no-poll-on-init;
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | omap.txt | 24 - ti,no-reset-on-init: When present, the module should not be reset at init
25 - ti,no-idle-on-init: When present, the module should not be idled at init
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | nxp,88w8987-bt.yaml | 26 fw-init-baudrate:
47 fw-init-baudrate = <3000000>;
|
| /Documentation/sound/soc/ |
| D | machine.rst | 70 .init = corgi_wm8731_init,
91 sockets in the machine init function.
97 Machine specific audio mixer controls can be added in the DAI init function.
|
| /Documentation/dev-tools/kunit/ |
| D | run_manual.rst | 89 However, this feature is not available with KUnit suites that use init data,
90 because init data may have been discarded after the kernel boots. KUnit
91 suites that use init data should be defined using the
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | lp855x-backlight.yaml | 35 init-brt:
126 init-brt = /bits/ 8 <0x10>;
141 init-brt = /bits/ 8 <0x0a>;
|
| /Documentation/devicetree/bindings/bus/ |
| D | ti-sysc.yaml | 161 ti,no-reset-on-init:
162 description: Interconnect target module shall not be reset at init
165 ti,no-idle-on-init:
166 description: Interconnect target module shall not be idled at init
|
| /Documentation/crypto/ |
| D | devel-algos.rst | 174 during any of these are in-flight. Please note that calling .init()
182 .init() -> .update() -> .final() ! .update() might not be called
188 .init() -> .update() -> .finup() ! .update() may not be called
206 .setkey() -> .init() -> .update() -> .export() at all in this scenario.
225 - call .init() and then (as many times) .update()
230 to .init() or .update(), since there might be no chance to free them.
|
12345678910