Home
last modified time | relevance | path

Searched refs:initrd (Results 1 – 102 of 102) sorted by relevance

/linux-4.1.27/Documentation/x86/
Dearly-microcode.txt8 Microcode is stored in an initrd file. The microcode is read from the initrd
11 The format of the combined initrd image is microcode in cpio format followed by
12 the initrd image (maybe compressed). Kernel parses the combined initrd image
18 the initrd file, it parses the microcode and saves matching microcode in memory.
32 The following example script shows how to generate a new combined initrd file in
33 /boot/initrd-3.5.0.ucode.img with original microcode microcode.bin and
34 original initrd image /boot/initrd-3.5.0.img.
36 mkdir initrd
37 cd initrd
42 cat ucode.cpio /boot/initrd-3.5.0.img >/boot/initrd-3.5.0.ucode.img
D00-INDEX6 - How to load microcode from an initrd-CPIO archive early to fix CPU issues.
Dboot.txt16 Protocol 2.00: (Kernel 1.3.73) Added bzImage and initrd support, as
32 initrd address available to the bootloader.
178 0218/4 2.00+ ramdisk_image initrd load address (set by boot loader)
179 021C/4 2.00+ ramdisk_size initrd size (set by boot loader)
185 022C/4 2.03+ initrd_addr_max Highest legal initrd address
215 initrd not supported
940 an initrd, since an initrd should be placed near end of
944 initrd=<file>
945 An initrd should be loaded. The meaning of <file> is
1109 boot stub. The boot loader is required to load the kernel/initrd(s)
/linux-4.1.27/Documentation/
Dinitrd.txt1 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 …]
Defi-stub.txt47 **** The "initrd=" option
50 multiple initrd files using the "initrd=" option. This is the only EFI
54 The path to the initrd file must be an absolute path from the
62 initrd-large.img
65 initrd-small.img
66 initrd-medium.img
68 to boot with the initrd-large.img file if the current working
71 fs0:\Kernels> bzImage.efi initrd=\Kernels\initrd-large.img
83 and is processed in the same manner as the "initrd=" option that is
Dinit.txt21 to be pre-loaded by an initrd)
Dintel_txt.txt116 verify the kernel and initrd.
190 module /initrd-2.6.29-tip.img
Dgdb-kernel-debugging.txt35 -append, -initrd command line switches. This is generally only useful if
Dxz.txt37 For decompressing the kernel image, initramfs, and initrd, there
DChanges315 o <https://code.launchpad.net/initrd-tools/main>
D00-INDEX230 initrd.txt
Ddevices.txt109 250 = /dev/initrd Initial RAM disk
112 /dev/initrd refers to a RAM disk which was preloaded
114 the initrd.
Dkernel-parameters.txt1454 initrd= [BOOT] Specify the location of the initial ramdisk
3209 used for early userspace startup. See initrd.
3273 retain_initrd [RAM] Keep initrd memory after extraction
/linux-4.1.27/arch/um/kernel/
Dinitrd.c14 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()
55 initrd = line; in uml_initrd_setup()
DMakefile18 obj-$(CONFIG_BLK_DEV_INITRD) += initrd.o
/linux-4.1.27/arch/arm/boot/bootp/
Dinit.S27 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-4.1.27/arch/powerpc/boot/
DREADME2 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
Dwrapper36 initrd=
81 initrd="$1"
154 isection=.kernel:initrd
194 isection=initrd
233 isection=.kernel:initrd
354 if [ -n "$initrd" ]; then
355 real_rd="$initrd"
362 if [ -z "$initrd" ]; then
383 if [ -n "$initrd" ]; then
384 addsec $tmp "$initrd" $isection
Dmain.c178 struct addr_range vmlinux, initrd; in start() local
204 initrd = prep_initrd(vmlinux, chosen, in start()
223 kentry((unsigned long)initrd.addr, initrd.size, in start()
DzImage.ps3.lds.S17 .kernel:initrd : { *(.kernel:initrd) }
DzImage.lds.S63 .kernel:initrd :
66 *(.kernel:initrd)
DzImage.coff.lds.S31 *(.kernel:initrd)
D.gitignore22 zImage.initrd
/linux-4.1.27/tools/testing/selftests/rcutorture/doc/
Dinitrd.txt1 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
20 happen, put the following script in the initrd's tree's "/init" file,
/linux-4.1.27/Documentation/power/
Dswsusp-dmcrypt.txt11 You did read Documentation/initrd.txt 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 …]
Dswsusp.txt8 * If you do resume from initrd after your filesystems are mounted...
62 2) Manually from an initrd or initramfs: May be run from
261 …user processes are stopped (in common case there are none, but with resume-from-initrd, no one kno…
312 cannot be initiated from an initrd or initramfs image. See
345 /sys/power/resume file from initrd. Be sure not to mount
Dswsusp-and-swap-files.txt50 to a swap file allowing the resume to be initiated from an initrd or initramfs
/linux-4.1.27/arch/openrisc/kernel/
Dvmlinux.lds.S94 .initrd : AT(ADDR(.initrd) - LOAD_OFFSET)
97 *(.initrd) argument
/linux-4.1.27/arch/x86/boot/
DMakefile120 image_cmdline = default linux $(FDARGS) $(if $(FDINITRD),initrd=initrd.img,)
132 MTOOLSRC=$(obj)/mtools.conf mcopy '$(FDINITRD)' a:initrd.img ; \
144 MTOOLSRC=$(obj)/mtools.conf mcopy '$(FDINITRD)' v:initrd.img ; \
155 MTOOLSRC=$(obj)/mtools.conf mcopy '$(FDINITRD)' w:initrd.img ; \
175 cp '$(FDINITRD)' $(obj)/isoimage/initrd.img ; \
/linux-4.1.27/arch/unicore32/boot/
DMakefile34 PHONY += initrd FORCE
35 initrd: target
/linux-4.1.27/arch/arm/boot/
DMakefile83 $(obj)/bootp/bootp: $(obj)/zImage initrd FORCE
91 PHONY += initrd FORCE
92 initrd: target
/linux-4.1.27/arch/x86/kernel/cpu/microcode/
Dintel_early.c81 copy_initrd_ptrs(struct microcode_intel **mc_saved, unsigned long *initrd, in copy_initrd_ptrs() argument
87 mc_saved[i] = (struct microcode_intel *)(initrd[i] + off); in copy_initrd_ptrs()
111 load_microcode(struct mc_saved_data *mc_saved_data, unsigned long *initrd, in load_microcode() argument
118 copy_initrd_ptrs(mc_saved_tmp, initrd, initrd_start, count); in load_microcode()
527 scan_microcode(struct mc_saved_data *mc_saved_data, unsigned long *initrd, in scan_microcode() argument
547 mc_saved_data, initrd, uci); in scan_microcode()
691 unsigned long *initrd, in _load_ucode_intel_bsp() argument
699 ret = scan_microcode(mc_saved_data, initrd, start, size, &uci); in _load_ucode_intel_bsp()
703 ret = load_microcode(mc_saved_data, initrd, start, &uci); in _load_ucode_intel_bsp()
/linux-4.1.27/Documentation/ia64/
Dxen.txt42 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-4.1.27/arch/frv/boot/
DMakefile53 bootp/bootp: zImage initrd
56 initrd: target
/linux-4.1.27/arch/arm/boot/dts/
Dkirkwood-iconnect.dts18 linux,initrd-start = <0x4500040>;
19 linux,initrd-end = <0x4800000>;
173 label = "initrd";
Dtegra114-tn7.dts13 /* TN7's bootloader will place initrd at this address */
14 linux,initrd-start = <0x82000000>;
15 linux,initrd-end = <0x82800000>;
Dexynos4412-smdk4412.dts27 …bootargs ="root=/dev/ram0 rw ramdisk=8192 initrd=0x41000000,8M console=ttySAC1,115200 init=/linuxr…
Dexynos4210-smdkv310.dts29 …bootargs = "root=/dev/ram0 rw ramdisk=8192 initrd=0x41000000,8M console=ttySAC1,115200 init=/linux…
Dtegra114-roth.dts13 /* SHIELD's bootloader will place initrd at this address */
14 linux,initrd-start = <0x82000000>;
15 linux,initrd-end = <0x82800000>;
Dexynos4210-origen.dts33 …bootargs ="root=/dev/ram0 rw ramdisk=8192 initrd=0x41000000,8M console=ttySAC2,115200 init=/linuxr…
Darmada-xp-lenovo-ix4-300d.dts176 label = "initrd";
Dexynos5250-smdk5250.dts29 …bootargs = "root=/dev/ram0 rw ramdisk=8192 initrd=0x41000000,8M console=ttySAC2,115200 init=/linux…
/linux-4.1.27/Documentation/powerpc/
Dmpc52xx.txt24 # make zImage.initrd
28 DBug> dn -i zImage.initrd.lite5200
Dbootwrapper.txt110 Two special targets called 'zImage' and 'zImage.initrd' also exist. These
/linux-4.1.27/arch/arm/configs/
Dneponset_defconfig18 …arts=sa1100:512K(boot),1M(kernel),2560K(initrd),4M(root) load_ramdisk=1 prompt_ramdisk=0 mem=32M n…
Dhackkit_defconfig12 CONFIG_CMDLINE="console=ttySA0,115200 root=/dev/ram0 initrd=0xc0400000,8M init=/rootshell"
Dassabet_defconfig14 CONFIG_CMDLINE="mem=32M console=ttySA0,38400n8 initrd=0xc0800000,3M root=/dev/ram"
Dpleb_defconfig16 CONFIG_CMDLINE="console=ttySA0,9600 mem=16M@0xc0000000 mem=16M@0xc8000000 root=/dev/ram initrd=0xc0…
Ds5pv210_defconfig21 CONFIG_CMDLINE="root=/dev/ram0 rw ramdisk=8192 initrd=0x20800000,8M console=ttySAC1,115200 init=/li…
Dks8695_defconfig24 CONFIG_CMDLINE="mem=32M console=ttyS0,115200 initrd=0x20410000,3145728 root=/dev/ram0 rw"
Dacs5k_defconfig26 CONFIG_CMDLINE="mem=32M console=ttyS0,115200 initrd=0x20410000,3145728 root=/dev/ram0 rw"
Ds3c6400_defconfig22 CONFIG_CMDLINE="console=ttySAC0,115200 root=/dev/ram init=/linuxrc initrd=0x51000000,6M ramdisk_siz…
Dexynos_defconfig28 CONFIG_CMDLINE="root=/dev/ram0 rw ramdisk=8192 initrd=0x41000000,8M console=ttySAC1,115200 init=/li…
Dat91_dt_defconfig29 CONFIG_CMDLINE="console=ttyS0,115200 initrd=0x21100000,25165824 root=/dev/ram0 rw"
Dsama5_defconfig26 CONFIG_CMDLINE="console=ttyS0,115200 initrd=0x21100000,25165824 root=/dev/ram0 rw"
/linux-4.1.27/tools/testing/selftests/rcutorture/
D.gitignore1 initrd
/linux-4.1.27/arch/parisc/
Ddefpalo.conf15 --commandline=0/vmlinuz HOME=/ root=/dev/ram initrd=0/ramdisk panic_timeout=60 panic=-1
DKconfig188 be used for TFTP booting without the need to have an initrd ramdisk.
/linux-4.1.27/Documentation/filesystems/
Dramfs-rootfs-initramfs.txt99 All this differs from the old initrd in several ways:
101 - The old initrd was always a separate file, while the initramfs archive is
105 - The old initrd file was a gzipped filesystem image (in some file format,
112 - The program run by the old initrd (which was called /initrd, not /init) did
118 - When switching another root device, initrd would pivot_root and then
217 If the kernel has initrd support enabled, an external cpio.gz archive can also
218 be passed into a 2.6 kernel in place of an initrd. In this case, the kernel
219 will autodetect the type (initramfs, not initrd) and extract the external cpio
223 device) but the separate packaging of initrd (which is nice if you have
272 # Testing external initramfs using the initrd loading mechanism.
[all …]
Dromfs.txt30 floppy drives can be loaded later if you use the "initrd"--initial
/linux-4.1.27/Documentation/acpi/
Dinitrd_table_override.txt1 Overriding ACPI tables via initrd
68 # Create the uncompressed cpio archive and concatenate the original initrd
71 cat /boot/initrd >>/boot/instrumented_initrd
/linux-4.1.27/arch/arm/boot/compressed/
Datags_to_fdt.c176 initrd_start = atag->u.initrd.start; in atags_to_fdt()
177 initrd_size = atag->u.initrd.size; in atags_to_fdt()
/linux-4.1.27/arch/arm/mm/
Dinit.c73 phys_initrd_start = __virt_to_phys(tag->u.initrd.start); in parse_tag_initrd()
74 phys_initrd_size = tag->u.initrd.size; in parse_tag_initrd()
82 phys_initrd_start = tag->u.initrd.start; in parse_tag_initrd2()
83 phys_initrd_size = tag->u.initrd.size; in parse_tag_initrd2()
/linux-4.1.27/Documentation/early-userspace/
DREADME130 initrd. init/main.c:init() will call prepare_namespace() to mount the
135 initrd. The initrd must contain a binary '/linuxrc' which is supposed to
137 filesystem via linuxrc and use the pivot_root syscall. The initrd is
143 initrd format, an cpio archive. It must be called "/init". This binary
Dbuffer-format.txt10 memory buffer protocol used by the initrd protocol, but the contents
/linux-4.1.27/arch/x86/kernel/
Dkexec-bzimage64.c330 unsigned long kernel_len, char *initrd, in bzImage64_load() argument
449 if (initrd) { in bzImage64_load()
450 ret = kexec_add_buffer(image, initrd, initrd_len, initrd_len, in bzImage64_load()
/linux-4.1.27/Documentation/s390/
Dzfcpdump.txt34 The s390 zipl tool looks for the zfcpdump kernel and optional initrd/initramfs
43 initrd. It can also be included in a built-in kernel initramfs. The application
/linux-4.1.27/arch/arm/kernel/
Datags_compat.c139 tag->u.initrd.start = params->u1.s.initrd_start; in build_tag_list()
140 tag->u.initrd.size = params->u1.s.initrd_size; in build_tag_list()
/linux-4.1.27/arch/arm/include/uapi/asm/
Dsetup.h153 struct tag_initrd initrd; member
/linux-4.1.27/Documentation/blockdev/
Dramdisk.txt16 is required for initrd, an initial filesystem used if you need to load modules
17 in order to access the root filesystem (see Documentation/initrd.txt). It can
32 for /dev/ram0, etc. If used, modern kernels use /dev/ram0 for an initrd.
/linux-4.1.27/Documentation/zh_CN/arm/
DBooting119 标签列表必须置于内核自解压和 initrd'bootp' 程序都不会覆盖的内存区。
/linux-4.1.27/Documentation/devicetree/
Dusage-model.txt183 of an initrd image.
190 initrd-start = <0xc8000000>;
191 initrd-end = <0xc8200000>;
194 The bootargs property contains the kernel arguments, and the initrd-*
195 properties define the address and size of an initrd blob. Note that
196 initrd-end is the first address after the initrd image, so this doesn't
Dbooting-without-of.txt210 r3, r4 : address & length of an initrd if any or 0
289 or initrd address. It simply holds information which can not be retrieved
421 you are passing an initrd to the kernel, you should reserve it as
/linux-4.1.27/Documentation/x86/x86_64/
Duefi.txt30 initrd. Instructions on building elilo and its dependencies
/linux-4.1.27/arch/tile/kernel/
Dsetup.c1101 void *initrd; in load_hv_initrd() local
1128 initrd = alloc_bootmem_pages(stat.size); in load_hv_initrd()
1129 rc = hv_fs_pread(fd, (HV_VirtAddr) initrd, stat.size, 0); in load_hv_initrd()
1133 free_initrd_mem((unsigned long) initrd, stat.size); in load_hv_initrd()
1136 initrd_start = (unsigned long) initrd; in load_hv_initrd()
/linux-4.1.27/Documentation/kdump/
Dkdump.txt342 --initrd=<initrd-for-dump-capture-kernel> --args-linux \
349 --initrd=<initrd-for-dump-capture-kernel> \
356 --initrd=<initrd-for-dump-capture-kernel> \
/linux-4.1.27/Documentation/sound/oss/
Dmwave23 Copy the kernel, any initrd image, and loadlin to /dos95/linux/boot/.
112 initrd image, and has a parameter file named LINDOC3.PAR in c:\linux\boot\parms:
/linux-4.1.27/tools/testing/selftests/rcutorture/bin/
Dkvm.sh134 --no-initrd)
/linux-4.1.27/include/linux/
Dkexec.h202 unsigned long kernel_len, char *initrd,
/linux-4.1.27/arch/openrisc/
DREADME.openrisc83 fully functional sash-3.6 in default initrd.
/linux-4.1.27/arch/unicore32/configs/
Dunicore32_defconfig8 # Initial RAM filesystem and RAM disk (initramfs/initrd) support
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dfw-cfg.txt30 initrd images for direct kernel booting, virtual machine UUID, SMP information,
/linux-4.1.27/drivers/acpi/
DKconfig251 bool "ACPI tables override via initrd"
256 via initrd. No functional change if no ACPI tables are passed via
257 initrd, therefore it's safe to say Y.
/linux-4.1.27/arch/m32r/kernel/
Dhead.S248 ; to be needed to boot from initrd)
/linux-4.1.27/Documentation/tpm/
Dxen-tpmfront.txt111 the initrd, the xen-tpmfront driver must be compiled in to the kernel. If not
/linux-4.1.27/fs/xfs/
DKconfig22 to use an initial ramdisk (initrd) to boot.
/linux-4.1.27/tools/lguest/
Dlguest.txt58 http://xm-test.xensource.com/ramdisks/initrd-1.1-i386.img
/linux-4.1.27/arch/s390/kernel/
Dhead.S260 .Linitrd:.long _end # default address of initrd
/linux-4.1.27/arch/powerpc/
DMakefile242 BOOT_TARGETS1 := zImage zImage.initrd uImage
DKconfig671 'make zImage.initrd'.
/linux-4.1.27/drivers/base/
DKconfig104 such firmware and do not wish to use an initrd.
121 use an initrd).
/linux-4.1.27/arch/powerpc/boot/dts/
Dc2k.dts348 label = "initrd";
Dobs600.dts165 label = "kernel + initrd";
/linux-4.1.27/Documentation/networking/
Dcxgb.txt237 initrd /initrd-2.4.21-27.ELsmp.img
/linux-4.1.27/Documentation/fb/
Duvesafb.txt26 either compile it into the kernel or use it as an initrd.
/linux-4.1.27/Documentation/arm/
DBooting113 the kernel decompressor nor initrd 'bootp' program will overwrite
/linux-4.1.27/Documentation/filesystems/nfs/
Dnfsroot.txt14 ramfs-rootfs-initramfs.txt), a ramdisk (see Documentation/initrd.txt) or a
/linux-4.1.27/init/
DKconfig1279 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
1286 etc. See <file:Documentation/initrd.txt> for details.
1289 also enables initial RAM disk (initrd) support and adds
1965 an initrd or initramfs, it generally is more efficient to compress the whole
1966 initrd or initramfs instead.
/linux-4.1.27/Documentation/sysctl/
Dkernel.txt67 - real-root-dev ==> Documentation/initrd.txt
/linux-4.1.27/arch/x86/
DKconfig1153 at the beginning of initrd image. The data tells kernel to load
1155 microcode data is glued to the initrd, therefore it's safe to say Y.
/linux-4.1.27/Documentation/kbuild/
Dmakefiles.txt833 - Preparing initrd images and the like
/linux-4.1.27/drivers/staging/speakup/
Dspkguide.txt546 from an initrd. There is a third possibility. Speakup can be compiled