| /Linux-v5.4/Documentation/admin-guide/ |
| D | initrd.rst | 1 Using the initial RAM disk (initrd)
8 initrd provides the capability to load a RAM disk by the boot loader.
11 from a different device. The previous root (from initrd) is then moved
14 initrd is mainly designed to allow system startup to occur in two phases,
16 where additional modules are loaded from initrd.
18 This document gives a brief overview of the use of initrd. A more detailed
25 When using initrd, the system typically boots as follows:
28 2) the kernel converts initrd into a "normal" RAM disk and
29 frees the memory used by initrd
33 4) root device is mounted. if it is ``/dev/ram0``, the initrd image is
[all …]
|
| D | efi-stub.rst | 50 The "initrd=" option
54 multiple initrd files using the "initrd=" option. This is the only EFI
58 The path to the initrd file must be an absolute path from the
66 initrd-large.img
69 initrd-small.img
70 initrd-medium.img
72 to boot with the initrd-large.img file if the current working
75 fs0:\Kernels> bzImage.efi initrd=\Kernels\initrd-large.img
99 "dtb=" is processed in the same manner as the "initrd=" option that is
|
| /Linux-v5.4/tools/testing/selftests/rcutorture/doc/ |
| D | initrd.txt | 1 The rcutorture scripting tools automatically create the needed initrd
2 directory using dracut. Failing that, this tool will create an initrd
9 linking, you might wish to press an existing initrd into service:
13 zcat /initrd.img > /tmp/initrd.img.zcat
14 mkdir initrd
15 cd initrd
16 cpio -id < /tmp/initrd.img.zcat
17 # Manually verify that initrd contains needed binaries and libraries.
24 happen, put the following script in the initrd's tree's "/init" file,
37 initrd filesystem to be dispensed with, which can save significant
|
| /Linux-v5.4/arch/um/kernel/ |
| D | initrd.c | 14 static char *initrd __initdata = NULL;
23 if (initrd == NULL) in read_initrd()
26 err = os_file_size(initrd, &size); in read_initrd()
35 printk(KERN_ERR "\"%s\" is a zero-size initrd\n", initrd); in read_initrd()
43 if (load_initrd(initrd, area, size) == -1) in read_initrd()
53 initrd = line; in uml_initrd_setup()
|
| /Linux-v5.4/arch/arm/boot/bootp/ |
| D | init.S | 24 bl move @ move the initrd
30 ldmia r13, {r5-r9} @ get size and addr of initrd
33 @ r7 = initrd start
34 @ r8 = initrd end
56 mov r5, #4 @ Size of initrd tag (4 words)
76 data: .word initrd_start @ source initrd address
77 .word initrd_phys @ destination initrd address
78 .word initrd_size @ initrd size
|
| /Linux-v5.4/tools/testing/selftests/rcutorture/bin/ |
| D | mkinitrd.sh | 58 echo Creating $D/initrd using dracut.
62 mkdir -p initrd
63 cd initrd
67 echo Done creating $D/initrd using dracut
76 mkdir -p initrd
77 cd initrd
|
| /Linux-v5.4/arch/powerpc/boot/ |
| D | README | 2 To extract the kernel vmlinux, System.map, .config or initrd from the zImage binary:
7 objcopy -j .kernel:initrd -O binary zImage.initrd initrd.gz
|
| D | wrapper | 38 initrd=
103 initrd="$1"
227 isection=.kernel:initrd
274 isection=initrd
313 isection=.kernel:initrd
454 if [ -n "$initrd" ]; then
455 real_rd="$initrd"
462 if [ -z "$initrd" ]; then
483 if [ -n "$initrd" ]; then
484 addsec $tmp "$initrd" $isection
|
| D | zImage.ps3.lds.S | 18 .kernel:initrd : { *(.kernel:initrd) }
|
| D | main.c | 229 struct addr_range vmlinux, initrd; in start() local
255 initrd = prep_initrd(vmlinux, chosen, in start()
279 kentry((unsigned long)initrd.addr, initrd.size, in start()
|
| D | zImage.lds.S | 64 .kernel:initrd :
67 *(.kernel:initrd)
|
| /Linux-v5.4/Documentation/power/ |
| D | swsusp-dmcrypt.rst | 13 You did read Documentation/admin-guide/initrd.rst and know how an initrd works.
14 You know how to create or how to modify an initrd.
19 an initrd that does your current crypto setup already.
25 or an usb stick prior to resume. So you need an initrd, that sets
31 always the same major/minor within the initrd as well as
43 Prepare your boot loader to use the initrd you will create or
48 initrd=/boot/initrd.gz
52 Finally you need to create or modify your initrd. Lets assume
53 you create an initrd that reads the required dm-crypt setup
57 named "swapkey". /etc/fstab of your initrd contains something
[all …]
|
| /Linux-v5.4/Documentation/x86/ |
| D | microcode.rst | 24 The microcode is stored in an initrd file. During boot, it is read from
27 The format of the combined initrd image is microcode in (uncompressed)
28 cpio format followed by the (possibly compressed) initrd image. The
29 loader parses the combined initrd image during boot.
39 scans the microcode file in the initrd. If microcode matching the
47 Here's a crude example how to prepare an initrd with microcode (this is
49 initrd, so you don't really have to do it yourself. It is documented
56 echo "You need to supply an initrd file"
63 TMPDIR=/tmp/initrd
|
| /Linux-v5.4/arch/openrisc/kernel/ |
| D | vmlinux.lds.S | 101 .initrd : AT(ADDR(.initrd) - LOAD_OFFSET)
104 *(.initrd) argument
|
| /Linux-v5.4/arch/x86/boot/ |
| D | genimage.sh | 54 mcopy "$FDINITRD" a:initrd.img
66 mcopy "$FDINITRD" v:initrd.img
78 mcopy "$FDINITRD" w:initrd.img
115 cp "$FDINITRD" $tmp_dir/initrd.img
|
| /Linux-v5.4/Documentation/devicetree/bindings/ |
| D | chosen.txt | 124 linux,initrd-start and linux,initrd-end
127 These properties hold the physical start and end address of an initrd that's
128 loaded by the bootloader. Note that linux,initrd-start is inclusive, but
129 linux,initrd-end is exclusive.
134 linux,initrd-start = <0x82000000>;
135 linux,initrd-end = <0x82800000>;
|
| /Linux-v5.4/arch/parisc/kernel/ |
| D | kexec_file.c | 17 unsigned long kernel_len, char *initrd, in elf_load() argument
44 if (initrd != NULL) { in elf_load()
45 kbuf.buffer = initrd; in elf_load()
|
| /Linux-v5.4/arch/arm/boot/ |
| D | Makefile | 93 $(obj)/bootp/bootp: $(obj)/zImage initrd FORCE
99 PHONY += initrd install zinstall uinstall
100 initrd: target
|
| /Linux-v5.4/arch/unicore32/boot/ |
| D | Makefile | 34 PHONY += initrd
35 initrd: target
|
| /Linux-v5.4/arch/powerpc/kernel/ |
| D | kexec_elf_64.c | 27 unsigned long kernel_len, char *initrd, in elf64_load() argument
63 if (initrd != NULL) { in elf64_load()
64 kbuf.buffer = initrd; in elf64_load()
|
| /Linux-v5.4/Documentation/ia64/ |
| D | xen.rst | 43 5. make initrd for Dom0/DomU::
47 # mkinitrd -f /boot/efi/efi/redhat/initrd-2.6.18.8-xen.img \
121 initrd=initrd-2.6.18.8-xen.img
167 5. install the kernel and initrd::
171 # mkinitrd -f /boot/efi/efi/redhat/initrd-2.6-pv_ops-xenU.img \
183 ramdisk = "/boot/efi/efi/redhat/initrd-2.6-pv_ops-xenU.img"
|
| /Linux-v5.4/arch/arm64/kernel/ |
| D | machine_kexec_file.c | 180 char *initrd, unsigned long initrd_len, in load_other_segments() argument
193 if (initrd) { in load_other_segments()
194 kbuf.buffer = initrd; in load_other_segments()
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | kirkwood-iconnect.dts | 19 linux,initrd-start = <0x4500040>;
20 linux,initrd-end = <0x4800000>;
164 label = "initrd";
|
| /Linux-v5.4/Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 71 Loading ACPI SSDTs from initrd
74 This option allows loading of user defined SSDTs from initrd and it is useful
77 It works in a similar way with initrd based ACPI tables override/upgrade: SSDT
78 aml code must be placed in the first, uncompressed, initrd under the
94 # Create the uncompressed cpio archive and concatenate the original initrd
97 cat /boot/initrd >>/boot/instrumented_initrd
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | mpc52xx.rst | 27 # make zImage.initrd
31 DBug> dn -i zImage.initrd.lite5200
|
