search for: initrds

Displaying 20 results from an estimated 4662 matches for "initrds".

Did you mean: initrd
2006 Jan 03
0
Isolinux.cfg issues on certain BIOSes
Howdy to all, We've been using isolinux quite successfully for quite some time now, and I have come across a couple of laptops where isolinux balks at my config file.. Upon booting on this systems, the image background appears corrupted, and at the boot prompt, the following happens automatically. Unknown keyword in config file. Could not find kernel image: 1 boot: Any label input here
2018 Jan 31
4
How is initrd.img packed and compressed?
Hi, In order to work around a known upstream bug I needed to add a udev rule to pxeboot initrd.img on CentOS 7. The process is straightforward: 1 - extract the pxeboot initrd.img to a new directory 2 - add the udev rule needed to fix the bug 3 - pack and compress it back in initrd.img format The resulting updated image works, it fixes the upstream bug and life is good. But although it works,
2006 Jun 19
2
Isolinux CD to Hard drive
Hi, I've been using Isolinux Boot CD for a while now and it's working great. This weekend, I decided to install it on my hard drive so I can boot Isolinux of the Hard drive. I used the famous command : "syslinux -s c:" to initialize the drive then I copied all the .img file to that drive. Then I renamed the "isolinux.cfg" to "syslinux.cfg" to get to my
2003 Dec 15
2
2 disks boot
Hi all! It's my first message on this ML. I just installed Fedora Core and I had a small problem... kernel + initrd do not fit in a 1.44 disks... I looked at documentation and at code (kernel.inc) and I saw that syslinux - load kernel - load initrd - boot kernel So perhaps a small workaround for above problem should be to add a configuration to initrd (ie initrd=@initrd.img) to just ask to
2005 Mar 04
1
Unicode problem.
Hi! Here is my isolinux.cfg. It's slackware based. ====================== default Kernels/bare.i/bzImage initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=8192 rw root=/dev/ram ZILIX_KERNEL=bare.i prompt 1 timeout 1200 font lat1-16.psfu display mensagem.msg F1 mensagem.msg F2 opcoes.msg F3 help.msg label linux kernel Kernels/bare.i/bzImage append - label adaptec.s kernel
2005 Mar 29
3
Query regarding initramfs
Hi 1. Is it possible to load an initrd from initramfs ? How would you do this if the initramfs is being loaded dynamically in the kernel (ie having the initramfs as initrd ) Because in this case, you will say root = /dev/initrd and specify 'initrd' as your 'initramfs source file' How will you specify the second initrd source? Thanks Rachita.
2015 May 15
2
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
On Thu, 2015-05-14 at 22:45 +0200, Stephan Seitz wrote: > On Wed, May 13, 2015 at 11:57:55AM -0400, Konrad Rzeszutek Wilk wrote: > >> > according to the documentation the option ucode=scan should tell XEN to > >> > look for a microcode update in an uncompressed initrd. > >> > > >> > While I don?t use the Debian kernel the tools to generate the
2013 Sep 06
1
[PATCH] arm: appliance: Add support for device trees (dtb's).
This is the libguestfs companion patch to: https://www.redhat.com/archives/libguestfs/2013-September/msg00045.html Rich.
2007 Jan 25
4
mount initrd
Hi, I try to mount the file /boot/initrd-2.6.9-42.ELsmp but I have a error [root at localhost ~]# cp /boot/initrd-2.6.9-42.ELsmp.img /root/ [root at localhost ~]# mv initrd-2.6.9-42.ELsmp.img initrd-2.6.9-42.ELsmp.gz [root at localhost ~]# gunzip initrd-2.6.9-42.ELsmp.gz [root at localhost ~]# mount initrd-2.6.9-42.ELsmp /tmp -o loop [root at localhost ~]# mount: you must specify the
2007 Jun 19
5
OpenSuse 10.2 & Xen 3.1 initrd file missing
Hi, I recently put together an OpenSuse 10.2 machine (Tyan motherboard with Opteron dual-core) and downloaded the Xen 3.1 rpm''s. After loading them and modifying grub to boot into the Xen kernel, I get a "file not found" error on the xen initrd file. As it turns out, there is a link for the xen initrd file in /boot/grub but the file doesn''t exist. Not sure what
2013 Mar 15
1
order of APPEND and INITRD
Igor asked about APPEND: > In other words: Can I break up a long line into multiple lines > in 5.01 or 5.10pre now or is that still not supported? I also wonder: can one control whether the INITRD parameter gets prepended or appended? Right now it seems to be placed after APPEND parameters, but might be more useful if it came first. The Debian/Ubuntu installers will copy parameters
2007 Jan 15
2
network booting initrd -mount: error 6 mounting ext3
Hi all, Im network booting initrd-2.6.9-22.EL.img from pxelinux. <snip from init script> echo Creating root device mkrootdev /dev/root umount /sys echo Mounting root filesystem mount -o defaults --ro -t ext3 /dev/root /sysroot mount -t tmpfs --bind /dev /sysroot/dev echo Switching to new root switchroot /sysroot echo UMOUNTING initrd-dev umount /initrd/dev </snip> I receive error
2003 Aug 08
3
isolinux.cfg/syslinux.cfg
Hi: I am having problems with isolinux.cfg I am receiving several error messages. 'Missing parameter in config file' and 'Unknown keyword in config file'. Here is a copy of my Isolinux.cfg maybe sombody can help me figure it out: default ks prompt 1 timeout 60 display custom.msg F1 boot.msg F2 options.msg F3 general.msg F4 param.msg F5 rescue.msg F7 custom.msg
2003 Aug 10
7
pxelinux - loading vmlinuz and initrd.gz
Greetings, Hopefully a quick question.. I have been experimenting with pxelinux and have noticed the following, when using initrd.gz - vmlinuz needs to exist 'tftpboot' directory, else I get an error from pxelinux. eg. kernel/vmlinuz - vmlinux also needs to exist in initrd.gz (in the same relative path eg. kernel/vmlinuz) else Linux is not booted. [I haven't confirmed
2010 May 13
5
what does "initrd-2.6.32.9.img" contains
Hi all If I use nfsroot boot the xen dom0, I find it works well if not use initrd-2.6.32.9.img. what does "initrd-2.6.32.9.img" contains? Thanks Lei -- "We learn from failure, not from success!" _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2015 May 13
3
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
> > according to the documentation the option ucode=scan should tell XEN to > > look for a microcode update in an uncompressed initrd. > > > > While I don?t use the Debian kernel the tools to generate the initrd are > > part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? > > creates the directory structure
2005 Nov 03
2
simple menu limitations
I am using the following simple menu and have noticed that items at the bottom are dropping off. I seem to be limited to 12 items. Is there a limit to how many items can be on the simple menu? default pxelinux.cfg/menu.c32 prompt 0 MENU TITLE UWSP PXE Boot Menu # TIMEOUT 200 LABEL bartpe MENU LABEL Build 12 KERNEL /STARTROM.0 APPEND keeppxe LABEL 11dnet MENU LABEL Build 11DNET beta
2006 Nov 16
0
Greeter Application Problems
Many times when i boot my Xen machine i get a message saying something like "The greeter application has failed many times, using alternative greeter." From there on I can do everything OK as far as i can see. Sometimes when i boot the machine, it just randomly restarts halfway through the boot process. It has also been crashing alot lately when i try to run it 24/7. Any ideas? here
2006 Dec 28
1
modifying initrd.img to run custom application
Im n/w booting machine with kernel - vmlinuz and initrd initrd.img. I copied vmlinuz & initrd.img from RHEL4 iso. I want to modify initrd.img so that when 2nd stage boot loader loads initrd, my custom application gets executed. linuxrc in initrd.img is sym-link to /sbin/init. My steps: 1. Renamed linuxrc to linuxrc1 2. created new linuxrc script & invoked "/linuxrc1" from
2014 May 18
2
Booting new kernels
On Sun, May 18, 2014 at 7:08 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> > On 05/16/2014 01:35 PM, Tal Lubko wrote: >> > > For some reason when I use kernel 3.7.1 and above the system crashes > during boot and I have no reason why. >> Consider a lack of init or otherwise improper initrd (cpio format, > compression, etc). Consider trying your old kernel