| /Linux-v4.19/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 …]
|
| /Linux-v4.19/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()
41 if (load_initrd(initrd, area, size) == -1) in read_initrd()
51 initrd = line; in uml_initrd_setup()
|
| /Linux-v4.19/arch/arm/boot/bootp/ |
| D | init.S | 27 bl move @ move the initrd
33 ldmia r13, {r5-r9} @ get size and addr of initrd
36 @ r7 = initrd start
37 @ r8 = initrd end
59 mov r5, #4 @ Size of initrd tag (4 words)
79 data: .word initrd_start @ source initrd address
80 .word initrd_phys @ destination initrd address
81 .word initrd_size @ initrd size
|
| /Linux-v4.19/tools/testing/selftests/rcutorture/doc/ |
| D | initrd.txt | 1 This document describes one way to create the initrd directory hierarchy
2 in order to allow an initrd to be built into your kernel. The trick
3 here is to steal the initrd file used on your Linux laptop, Ubuntu in
10 zcat /initrd.img > /tmp/initrd.img.zcat
11 mkdir initrd
12 cd initrd
13 cpio -id < /tmp/initrd.img.zcat
19 the initrd directory hierarchy.
21 Here are the commands to create a initrd directory for rcutorture using
27 mkdir initrd
[all …]
|
| /Linux-v4.19/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=
101 initrd="$1"
213 isection=.kernel:initrd
253 isection=initrd
292 isection=.kernel:initrd
426 if [ -n "$initrd" ]; then
427 real_rd="$initrd"
434 if [ -z "$initrd" ]; then
455 if [ -n "$initrd" ]; then
456 addsec $tmp "$initrd" $isection
|
| D | main.c | 193 struct addr_range vmlinux, initrd; in start() local
219 initrd = prep_initrd(vmlinux, chosen, in start()
242 kentry((unsigned long)initrd.addr, initrd.size, in start()
|
| D | zImage.ps3.lds.S | 18 .kernel:initrd : { *(.kernel:initrd) }
|
| D | zImage.lds.S | 64 .kernel:initrd :
67 *(.kernel:initrd)
|
| /Linux-v4.19/Documentation/ |
| D | efi-stub.txt | 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
88 and is processed in the same manner as the "initrd=" option that is
|
| /Linux-v4.19/Documentation/power/ |
| D | swsusp-dmcrypt.txt | 11 You did read Documentation/admin-guide/initrd.rst and know how an initrd works.
12 You know how to create or how to modify an initrd.
17 an initrd that does your current crypto setup already.
23 or an usb stick prior to resume. So you need an initrd, that sets
29 always the same major/minor within the initrd as well as
41 Prepare your boot loader to use the initrd you will create or
46 initrd=/boot/initrd.gz
50 Finally you need to create or modify your initrd. Lets assume
51 you create an initrd that reads the required dm-crypt setup
55 named "swapkey". /etc/fstab of your initrd contains something
[all …]
|
| /Linux-v4.19/Documentation/x86/ |
| D | microcode.txt | 20 The microcode is stored in an initrd file. During boot, it is read from
23 The format of the combined initrd image is microcode in (uncompressed)
24 cpio format followed by the (possibly compressed) initrd image. The
25 loader parses the combined initrd image during boot.
33 scans the microcode file in the initrd. If microcode matching the
41 Here's a crude example how to prepare an initrd with microcode (this is
43 initrd, so you don't really have to do it yourself. It is documented
50 echo "You need to supply an initrd file"
57 TMPDIR=/tmp/initrd
|
| /Linux-v4.19/arch/openrisc/kernel/ |
| D | vmlinux.lds.S | 105 .initrd : AT(ADDR(.initrd) - LOAD_OFFSET)
108 *(.initrd) argument
|
| /Linux-v4.19/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-v4.19/arch/s390/kernel/ |
| D | kexec_image.c | 42 char *initrd, unsigned long initrd_len, in s390_image_load() argument
52 if (initrd) { in s390_image_load()
53 ret = kexec_file_add_initrd(image, &data, initrd, initrd_len); in s390_image_load()
|
| D | kexec_elf.c | 64 char *initrd, unsigned long initrd_len, in s390_elf_load() argument
111 if (initrd) { in s390_elf_load()
112 ret = kexec_file_add_initrd(image, &data, initrd, initrd_len); in s390_elf_load()
|
| /Linux-v4.19/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-v4.19/arch/arm/boot/ |
| D | Makefile | 93 $(obj)/bootp/bootp: $(obj)/zImage initrd FORCE
99 PHONY += initrd install zinstall uinstall
100 initrd: target
|
| /Linux-v4.19/arch/unicore32/boot/ |
| D | Makefile | 34 PHONY += initrd
35 initrd: target
|
| /Linux-v4.19/Documentation/ia64/ |
| D | xen.txt | 42 5. make initrd for Dom0/DomU
45 # mkinitrd -f /boot/efi/efi/redhat/initrd-2.6.18.8-xen.img \
110 initrd=initrd-2.6.18.8-xen.img
147 5. install the kernel and initrd
150 # mkinitrd -f /boot/efi/efi/redhat/initrd-2.6-pv_ops-xenU.img \
162 ramdisk = "/boot/efi/efi/redhat/initrd-2.6-pv_ops-xenU.img"
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | kirkwood-iconnect.dts | 19 linux,initrd-start = <0x4500040>;
20 linux,initrd-end = <0x4800000>;
164 label = "initrd";
|
| /Linux-v4.19/Documentation/acpi/ |
| D | ssdt-overlays.txt | 66 == Loading ACPI SSDTs from initrd ==
68 This option allows loading of user defined SSDTs from initrd and it is useful
71 It works in a similar way with initrd based ACPI tables override/upgrade: SSDT
72 aml code must be placed in the first, uncompressed, initrd under the
88 # Create the uncompressed cpio archive and concatenate the original initrd
91 cat /boot/initrd >>/boot/instrumented_initrd
|
| /Linux-v4.19/Documentation/powerpc/ |
| D | mpc52xx.txt | 24 # make zImage.initrd
28 DBug> dn -i zImage.initrd.lite5200
|
| /Linux-v4.19/arch/arm/configs/ |
| D | neponset_defconfig | 17 …arts=sa1100:512K(boot),1M(kernel),2560K(initrd),4M(root) load_ramdisk=1 prompt_ramdisk=0 mem=32M n…
|
| /Linux-v4.19/tools/testing/selftests/rcutorture/ |
| D | .gitignore | 1 initrd
|
