Is it possible to run vmware-tools without an initrd? I don't know why I should use an initrd and it makes my kernel compilation more complicated. I can boot into my kernel without initrd but when I want to install vmware-tools it gives me an error message:
There was an error generating the initrd (1). Error /sbin/mkinitd -k vmlinuz...
Can I reboot?
Edit: It doesn't work without initrd.
I used the redhat RHEL6 boot with initrd but it failed, can sb help me
Code:
[root@localhost boot]# /usr/libexec/qemu-kvm --enable-kvm -smp 8 -m 1024 -net nic,model=virtio -net tap,script=/etc/qemu-ifup -initrd /boot/initramfs-2.6.32-279.el6.x86_64.img -kernel /boot/vmlinuz-2.6.32-279.el6.x86_64 -append "root=/dev/ram rw console=ttyS0,115200 " -nographic
Google, Inc.
Serial
I foolishly installed the newest kernel update... now I can't boot anymore.
Once I rebooted, grub presented me it's friendly console.
@dhave, I think they both worked for KairiTech, but only with the 0.5.4 version. Here is what I use for my system:# efibootmgr --create --disk /dev/sda --part 1 --label "Arch Linux" --loader '\EFI\arch\vmlinuz-linux.efi' -u "root=/dev/mapper/volgrp0-root_arch initrd=\\EFI\\arch\\initramfs-linux.img add_efi_memmap quiet libahci.ignore_sss=1"But you can also take
Grub can boot from any partition so there is no need to share boot partition.
Considering that GRUB executes following lines:
kernel /vmlinuz root=/dev/sda1 ro
initrd /initrd
On boot, how does the Linux kernel finds out about /dev/sda1 device node?
I know that initrd/initramfs images contain modules for storage (etc.) devices, which are loaded into memory to enable access to the storage.
hello everyone
i tried to compile linux kernel 2.6.31 on Fedora 12
the make , make modules and modules install ran successfully
but
problem with make install
while trying to create image it looks for mkinitrd command which is not available
i downloaded and installed the mkinitrd pckg and
make install was now successful
i got
it didn't work. so heres what i did.
Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
Im in the process of undervolting my CPU in 10.04 LTS using this guide: http://openmindedbrain.info/09/05/20...-04-lucid-lts/
my uname -r returned 2.6.32-37, no -phc, so I needed to go into gedit to change "GRUB_DEFAULT=0" to the corresponding line's number.