Tag Info

New answers tagged

0

let me try answer the second question about make a small system . since we are building on x86 i guess what is intended is to make a system to boot of a flash drive , rather than burn into embedded chips for which is a very different story . consider drop disk images and use a cpio initramfs . then boot like this . qemu-system-i386 -kernel vmlinuz -initrd ...


0

half-way fix: reboot, choose in boot menu older kernel, boot it. keyboard and mouse works. then you can login and fix your configs. ps: if you can not boot anymore (cause you kill your grub) then only one way to fix: you must make boot usb flash drive and boot from it. then mopunt your HDD and backup/fix your configs.


2

I had a similar problem, installing openSuSE 13.2 x86_64 from scratch, using a boot partition and an encrypted LVM containing root and swap. (Side note: It's not easy to do that actually since when creating an lvm partition the installer UI will not even let you chose "encrypt this device", you can "ungrey" the checkbox however by first chosing "format ...


0

There is a directory under /boot/git (besides fonts and locale). The name of this directory matches the platform in use. This directory contains mostly files with .mod extension and a few with .lst. The same directory (contents may differ slightly) exists in grub's lib path (on Debian this is /usr/lib/grub).


0

When you say "once selected and it attempts to boot", you mean Kali's own boot menu never appears? If it's own menu does appear that would mean it's already got grub working ok, but something else stops it from booting, maybe it needs a kernel option like nomodeset or noacpi or others. There might be easier ways to use Kali Linux from a USB though... Kali ...


0

This must be run first: mount /dev/sda1 /mnt mount --bind /dev /mnt/dev mount --bind /dev/pts /mnt/dev/pts mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys Plus, if booted off a flash recovery drive, chroot /mnt (source)



Top 50 recent answers are included