So, I am basically a Linux user and just hop onto Windows whenever I want to play games or anything stupid. Most of my games now actually run when secure boot is enabled but as I am using Kali already as my main and working OS. So, is it possible that I can enable secure boot and when I am done using Windows I restart disable the secure boot and run grub boot loader which is by default right now? Or will it cause errors? I don't know how to properly signed os right now.

I read here, once, that installing a Debian 9 on a pendrive (well, in my case it's a SDCard adapter) directly would work, and it did. The problem came up, though, after i unplugged the adapter from the computer; when i wanted to boot into linux, all i had to do was to choose the boot device labelled 'UEFI: debian' on the bios setup, but as soon as i removed the adapter, that option disappeared. I don't want to lose the debian installation, I want it working again. I need to get it booting again.

I dual booted windows 11 and Endeavor OS on my HP notebook without any problem, but after a BIOS update the Boot options menu listed Endeavour os as EFI hard drive. Also now the OS boot manager doesn't show Endeavour os as another OS and thus cannot choose the os on bootup. Any help would be much appreciated.

I have a Dell laptop and I'm trying to run Fedora KDE Desktop 42 from an external SSD. I've freshly installed Fedora in the external SSD using another USB flash drive containing the live image. When I boot up Fedora from the external SSD, it tells me to enter passphrase for the disk. After I enter the correct passphrase/password, it takes me to a loading screen and stays there forever. If I press ESC on that screen, it displays a completely blank screen. When I press ESC again, it takes me back to the loading screen. For the installation options I made the following choices: * I selected Storage Configuration as Automatic. I also deleted everything in the drive by selecting Delete all/Reclaim space. Then I selected Encrypt my data option. * I enabled root account. I also created a user with admin privilege. I have tried to troubleshoot it and made the following adjustments as suggested by others in the Dell UEFI settings: * I have enabled all the thunderbolt related options (since I'm using thunderbolt 4 port to connect to the external SSD). Namely, *Enabled Thunderbolt Technology Support*, *Enable Thunderbolt Boot Support*, *Enable Thunderbolt (and PCle behind TBT) pre-boot modules*. * Selected Storage -> *AHCI* (default was *RAID On*, it didn't work when I tried with *RAID On* either) * Selected Pre-boot Behaviour -> *Thorough* (default was *Fastboot*) * Tried turning *Secure Boot* on and off, which made no difference (I understand that Fedora 42 is supposed to work with secure boot, but it was worth a try) #### Hardware specs - Dell Latitude 5530 - CPU: 12th Gen Intel(R) Core(TM) i5-1245U (1.60 GHz) - RAM: 16.0 GB (15.7 GB usable) - Internal Graphics Card: Intel(R) Iris(R) Xe Graphics - Internal 500 GB SSD (Contains Windows 11) - [This](https://www.amazon.co.uk/dp/B0B9C3ZVHR) Samsung 990 pro 1TB external SSD (to run Fedora) - [This](https://www.amazon.co.uk/dp/B0C8CTW8M6) ACASIS SSD enclosure, which uses thunderbolt 4 cable Any kind of help to resolve this would be appreciated. --- Edit: Just reinstalled Fedora without using the Encrypt Drive option, now I can see the following output/log when I press ESC on the loading screen. (Please note that it scrolls really fast at times so I couldn't take a proper sequential set of photos)

I recently compiled and installed a Linux kernel on my Kubuntu computer. The way I did this was, I downloaded the source .tar.gz from kernel.org, extracted it and used the following commands (running in the top directory of the source package) to compile and install it: make oldconfig make -j4 sudo make modules_install sudo make install When I rebooted, however, I got a message saying "Error: out of memory" and when I pressed a key to continue it gave a kernel panic screen saying "not syncing: VFS: Unable to mount root fs on unknown-block(0,0)". My other kernels work fine, so I can still boot up normally. But I'm curious to know why that kernel doesn't work and what I can do to get it working. I tried this with a few versions (5.9.12, 5.9.14 and 5.10.2) and got the same result, so the exact version doesn't seem to be the issue here. But I know that I used to compile kernels like this all the time and they ran without issues. So I tried a bunch of stuff and eventually figured out that UEFI appears to be the culprit. This same kernel will work if I install it on a legacy system. Secure boot is disabled on the (UEFI) PC in question, so I figure it can't have to do with secure boot keys. It seems to be something about UEFI, but not secure boot, that breaks it. However, upon searching the internet I couldn't find anything on getting a compiled Linux kernel to boot with UEFI. So is there really some additional thing I must do? Or is the problem something else? **Edit:** I don't understand why my question was closed. But in case it requires more clarification, I am asking as follows: If I download the linux kernel source code from kernel.org or the code from which the Ubuntu kernels are built from here (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.4/) and compile it using the commands above, I find that it will boot fine in BIOS but not UEFI. My question is why.

I am attempting to install a dualboot (Ubuntu on top of Windows 10) to a PC I have just built myself. I have no problem installing Ubuntu, its just I am unable to setup my computer to boot into it afterwards. During the instalation I am told that the GRUB does not install properly and I also hit errors when trying to run a boot repair program in terminal. I am creating the installation using Rufus, and making use of the MBR parition scheme. The Disk I am creating it on is GPT, but when I try use this partition scheme in Rufus an error scheme comes up when I try boot this from a USB stick. This is shown in the next image (and note my bios mode is set to UEFI). For reference my motherboard is a "MSI B450 TOMAHAWK MAX Motherboard ATX". What is the best course of action to take? I found some videos that showed how to convert my from UEFI to legacy boot and to change my disk to a MSB partition, would this be the best solution or will this create further problems down the line?

In a simple install of Redhat from rhel-8.10-x86_64-dvd.iso I have this /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/fbx64.efi /boot/efi/EFI/redhat/grubx64.efi /boot/efi/EFI/redhat/mmx64.efi /boot/efi/EFI/redhat/shimx64.efi /boot/efi/EFI/redhat/shimx64-redhat.efi Can a quick explanation be given of each? On a Dell server, in the F11 boot menu when making an Add Boot option, which of the above is the proper one to choose?

I'm using a red hat developer subscription, so no official support from red hat. I have a rhel 9.6 installed to a 2TB nvme SSD, whose partitions are as follows: - 1 : 600MB (EFI) - 2 : 1GB (forget what it is, seemed to be a rhel boot-related partition) - 3 : 904.01GB (rhel main partition) - 4 : 200GB (a Windows 11 system partition) - 5 : 200GB - 6 : 557.41GB After I executed `dnf update and reboot` as normal, grub cannot find any of my rhel kernel(including rescue mode). The only thing grub found was Windows boot manager. Then I boot into Windows to check my partitions, finding that all my partitions were fine. So how to find my rhel back? Please help.

I have one hard drive that I want to split into two separate FreeBSD OS installs and I'm running into a wall trying to figure out how to get it working. I followed Installing FreeBSD Root on ZFS using GPT in order to get a single OS up and running. There are no problems and everything works great. However, I do not know how to modify this in order to get a second OS up and running. I repeat from steps 2 onward to create the second partition and second zpool. Once I restart the FreeBSD boot menu does not show any boot options (i.e. no option for Boot Environment in option 8). If I do a zpool import it will show my second zpool that is a part of the other partition. I can even mount it using zpool import -R /mnt zroot2 and I can see the files. This is the point I'm quite lost. I can't figure out what I did to do. I looked into efibootmgr and bectl, but I'm not sure either is the right option. bectl seems to create Boot Environments from snapshots and not from other partitions. efibootmgr seems to need the file system mounted. Essentially my current progress is: - nda0p1 efi - nda0p2 freebsd-swap - nda0p3 freebsd-zfs (OS 1) - nda0p4 freebsd-zfs (OS 2) How do I get the FreeBSD boot manager to recognize the second OS? edit1: I tried installing twice through the UI and it did put another entry into the efibootmgr, but both options boot the newest install even though they point to separate files (\EFI\BOOT\BOOTX64.efi and \EFI\freebsd\loader.efi). The original install doesn't boot. edit2: I think the reason they both boot the same instance is they're both the same UI. You copy the efi into to the BOOTX64.efi location in the steps from above. From what I understand this efi automatically finds the FreeBSD instance. How does one create an EFI that points directly to an instance?

I am dual booting a Dell Precision 7520 with Fedora 35 and Windows. Worked fine with Windows 10. "Up"graded to Windows 11 and now every time I boot into W11 it puts its own boot loader ahead of "fedora" in UEFI Setup. So every time after booting into W11, I need to hit F2 and reset the boot order in the UEFI Setup. I've developed a workaround, but it doesn't survive an update to W11's bootmgfw.efi file, nor an update to grub.cfg. Nevertheless, my solution means that I can go for many months without having to do it again. Here is my workaround: 1. boot into Linux 2. Make a backup of the MS Boot directory, just in case:

cd /boot/efi/EFI/Microsoft
cp -a Boot Boot.bak

3. Then do the following,

cd /boot/efi/EFI/Microsoft/Boot
cp -p bootmgfw.efi bootmgf2.efi
cp -p /boot/efi/EFI/fedora/grubx64.efi bootmgfw.efi
cd /boot/efi/EFI/fedora
cp -p grub.cfg grub.cfg.bak

4. Now edit grub.cfg and replace "bootmgfw" with "bootmgf2" (note that the real grub.cfg might be in /boot/grub2 rather than in /boot/efi/EFI/fedora) 5. reboot Now when Windows 11 puts itself top of the list in the boot order, and boots its bootmgfw.efi, it is actually booting grubx64.efi, which loads grub.cfg. As mentioned, you'll have to repeat steps 3 and 4 when bootmgfw.efi and/or grub.cfg are updated. I turned the above into a script which I only have to run once every several months when W11 updates its bootmgfw.efi file. Given the non-permanent nature of the above solution, is there a better solution? Note that after weeks of researching this problem, I came across a solution suggested by "Piotr" a few years ago to reset Windows "{bootmgr}" to \EFI\fedora\grubx64.efi, but that didn't work. Windows had no idea about \EFI\fedora...

So I converted a usb live linux install (Tails) from USB to virtualbox using VBoxManage convertfromraw. For it to boot in virtualbox, I need to remove one thing from the boot commandline (live-media=removable). This option is not in the usual /etc/default/grub or grub.d locations. I did find it in: /lib/live/mount/medium/syslinux/live.cfg. I'm not sure how that ends up in the grub commandline. In fact, there is nothing in /boot/grub except unicode.pf2, so I think there is some other mechanism going on here. This is EFI, also. I'm reluctant to run update-grub in case this command line is being put together in a different manner.

I'm trying to boot mfsBSD ISO via PXE on a host with UEFI boot enabled. It was a pretty simple task with BIOS boot, the ipxe config for this task looked like this: kernel --name freebsd http://pxe.host/memdisk initrd http://pxe.host/mfsbsd.img imgargs freebsd harddisk raw boot Since memdisk way is not supported with UEFI boot method and it seems like there is no other way to boot mfsBSD directly, I switched to booting GRUB2 first: kernel --name grub2 http://pxe.host/grub2.efi boot So now I'm trying to boot an mfsBSD ISO from there, here's how my grub.cfg looks like: insmod efinet insmod tftp insmod loopback insmod iso9660 insmod ufs2 insmod part_msdos insmod gfxterm insmod vbe menuentry "mfs12.1.iso" { set isofile=(tftp)/mfs12.1.iso loopback loop $isofile echo "ISO mounted" set root=(loop) kfreebsd /boot/kernel/kernel.gz echo "kernel loaded" kfreebsd_loadenv /boot/device.hints kfreebsd_module /boot/kernel/ahci.ko echo "ahci.ko loaded" kfreebsd_module /mfsroot.gz type=mfs_root set kFreeBSD.vfs.root.mountfrom="ufs:/dev/md0" echo "set kFreeBSD.vfs.root.mountfrom" set kFreeBSD.mfs_type="mfs_root" echo "set kFreeBSD.mfs_type" set kFreeBSD.mfs_name="/mfsroot" echo "set kFreeBSD.mfs_name" set kFreeBSD.mfsbsd.autodhcp="YES" echo "set kFreeBSD.mfsbsd.autodhcp" } Unfortunately, the boot hangs every time with no information on screen: I've tried changing kFreeBSD.vfs.root.mountfrom to "cd9660:/dev/md0" with no result, tried different mfsBSD versions and also built an EFI-enabled ISO using this solution: https://github.com/mmatuska/mfsbsd/pull/100 Is there anything I am missing in this setup? I would greatly appreciate any help.

I was trying to tweak Core linux to boot in uefi mode, but it's only working in legacy mode and i don't really know how to start with it, i tried copying efi from ubuntu server install but i just booted to uefi shell. Tree looks like this Core ├───boot │ │ core.gz │ │ vmlinuz │ │ │ └───grub │ │ efi.img │ │ font.pf2 │ │ grub.cfg │ │ loopback.cfg │ │ │ └───x86_64-efi │ acpi.mod │ adler32.mod │ ahci.mod │ all_video.mod │ aout.mod │ appleldr.mod │ archelp.mod │ ata.mod │ at_keyboard.mod │ backtrace.mod │ bfs.mod │ bitmap.mod │ bitmap_scale.mod │ blocklist.mod │ boot.mod │ bsd.mod │ bswap_test.mod │ btrfs.mod │ bufio.mod │ cat.mod │ cbfs.mod │ cbls.mod │ cbmemc.mod │ cbtable.mod │ cbtime.mod │ chain.mod │ cmdline_cat_test.mod │ cmp.mod │ cmp_test.mod │ command.lst │ cpio.mod │ cpio_be.mod │ cpuid.mod │ crc64.mod │ crypto.lst │ crypto.mod │ cryptodisk.mod │ cs5536.mod │ ctz_test.mod │ date.mod │ datehook.mod │ datetime.mod │ disk.mod │ diskfilter.mod │ div.mod │ div_test.mod │ dm_nv.mod │ echo.mod │ efifwsetup.mod │ efinet.mod │ efi_gop.mod │ efi_uga.mod │ ehci.mod │ elf.mod │ eval.mod │ exfat.mod │ exfctest.mod │ ext2.mod │ f2fs.mod │ fat.mod │ fdt.lst │ file.mod │ fixvideo.mod │ font.mod │ fs.lst │ gcry_arcfour.mod │ gcry_blowfish.mod │ gcry_camellia.mod │ gcry_cast5.mod │ gcry_crc.mod │ gcry_des.mod │ gcry_dsa.mod │ gcry_idea.mod │ gcry_md4.mod │ gcry_md5.mod │ gcry_rfc2268.mod │ gcry_rijndael.mod │ gcry_rmd160.mod │ gcry_rsa.mod │ gcry_seed.mod │ gcry_serpent.mod │ gcry_sha1.mod │ gcry_sha256.mod │ gcry_sha512.mod │ gcry_tiger.mod │ gcry_twofish.mod │ gcry_whirlpool.mod │ geli.mod │ gettext.mod │ gfxmenu.mod │ gfxterm.mod │ gfxterm_background.mod │ gfxterm_menu.mod │ gptsync.mod │ grub.cfg │ gzio.mod │ halt.mod │ hashsum.mod │ hdparm.mod │ help.mod │ hexdump.mod │ hfs.mod │ hfsplus.mod │ hfspluscomp.mod │ http.mod │ iorw.mod │ jfs.mod │ jpeg.mod │ keylayouts.mod │ keystatus.mod │ ldm.mod │ legacycfg.mod │ legacy_password_test.mod │ linux.mod │ linux16.mod │ linuxefi.mod │ loadbios.mod │ loadenv.mod │ loopback.mod │ ls.mod │ lsacpi.mod │ lsefi.mod │ lsefimmap.mod │ lsefisystab.mod │ lsmmap.mod │ lspci.mod │ lssal.mod │ luks.mod │ lvm.mod │ lzopio.mod │ macbless.mod │ macho.mod │ mdraid09.mod │ mdraid09_be.mod │ mdraid1x.mod │ memrw.mod │ minicmd.mod │ minix2.mod │ minix2_be.mod │ minix3.mod │ minix3_be.mod │ minix_be.mod │ mmap.mod │ moddep.lst │ morse.mod │ mpi.mod │ msdospart.mod │ multiboot.mod │ multiboot2.mod │ mul_test.mod │ nativedisk.mod │ net.mod │ newc.mod │ ntfs.mod │ ntfscomp.mod │ odc.mod │ offsetio.mod │ ohci.mod │ partmap.lst │ parttool.lst │ parttool.mod │ part_acorn.mod │ part_amiga.mod │ part_apple.mod │ part_bsd.mod │ part_dfly.mod │ part_dvh.mod │ part_gpt.mod │ part_msdos.mod │ part_plan.mod │ part_sun.mod │ part_sunpc.mod │ password.mod │ password_pbkdf2.mod │ pata.mod │ pbkdf2.mod │ pbkdf2_test.mod │ pcidump.mod │ pgp.mod │ play.mod │ png.mod │ priority_queue.mod │ probe.mod │ procfs.mod │ progress.mod │ raid5rec.mod │ raid6rec.mod │ random.mod │ rdmsr.mod │ read.mod │ reboot.mod │ regexp.mod │ reiserfs.mod │ relocator.mod │ romfs.mod │ scsi.mod │ serial.mod │ setjmp.mod │ setjmp_test.mod │ setpci.mod │ shift_test.mod │ shim_lock.mod │ signature_test.mod │ sleep.mod │ sleep_test.mod │ smbios.mod │ spkmodem.mod │ squash4.mod │ strtoull_test.mod │ syslinuxcfg.mod │ terminal.lst │ terminal.mod │ terminfo.mod │ test.mod │ testload.mod │ testspeed.mod │ test_blockarg.mod │ tftp.mod │ tga.mod │ time.mod │ tpm.mod │ tr.mod │ trig.mod │ true.mod │ udf.mod │ ufs1.mod │ ufs1_be.mod │ ufs2.mod │ uhci.mod │ usb.mod │ usbms.mod │ usbserial_common.mod │ usbserial_ftdi.mod │ usbserial_pl2303.mod │ usbserial_usbdebug.mod │ usbtest.mod │ usb_keyboard.mod │ verifiers.mod │ video.lst │ video.mod │ videoinfo.mod │ videotest.mod │ videotest_checksum.mod │ video_bochs.mod │ video_cirrus.mod │ video_colors.mod │ video_fb.mod │ wrmsr.mod │ xfs.mod │ xnu.mod │ xnu_uuid.mod │ xnu_uuid_test.mod │ xzio.mod │ zfscrypt.mod │ zstd.mod │ ├───EFI │ └───BOOT │ BOOTx64.EFI │ grubx64.efi │ mmx64.efi │ └───isolinux boot.cat boot.msg f2 f3 f4 isolinux.bin isolinux.cfg How Can I enable the UEFI boot?

Every time I boot into Windows (11/10) on my dual-boot system, the GRUB entry vanishes from the UEFI boot menu. I reinstall GRUB from a live Kali USB, and the entry comes back. Then I reboot into Windows, and—poof—it's gone again. Even mounting the EFI partition shows no GRUB files. **System Details:** Motherboard: Gigabyte B550M DS3H BIOS Version/Date: American Megatrends International, LLC. F2, 22-03-2024 Distribution: Kali Linux (UEFI install) Disk Setup: NVMe drive with GPT partitioning EFI partition: FAT32, mounted at /boot/efi Windows: UEFI install, Fast Startup OFF, Bitlocker OFF, Secure Boot OFF **What I've Tried:** Reinstalled GRUB using:

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=kali
sudo update-grub

Checked and modified UEFI entries with efibootmgr; GRUB shows up but disappears after rebooting Windows. Disabled Windows Fast Startup, Secure Boot, and Bitlocker. Mounting the EFI partition shows no GRUB or /EFI/GRUB content after disappearances. After mounting the EFI partition /dev/nvme0n1p1, in a live system I see only the /EFI/Microsoft folder. /EFI/kali or grubx64.efi is completely missing. What is removing the GRUB entry/EFI files? Is it Windows itself, firmware updates, or something else? How can I make the UEFI entry for Kali persist through Windows boots? Are there any EFI tweaks or BIOS settings I’m missing?

My Lenovo laptop is running Arch Linux with a UEFI GPT partition table. One day I powered up my laptop, but couldn't get passed the Lenovo boot screen. I used a USB stick to boot up and reinstall Arch. However after this I still couldn't get passed the Lenovo boot screen. I tried to reinstall it again using the same USB stick and ended up with two entries in my UEFI boot menu. I formatted the GUID partition to FAT32 using GPARTED live USB which deleted them. However I can no longer use my Arch UEFI USB stick to boot up. I get to the bootloader menu on the USB stick but after the timeout I get a blank screen.

I was using a dual boot of openSUSE and Windows and I decided to delete OpenSUSE by deleting the partition. On rebooting, I found out that the secure boot for openSUSE was still there, leading to an error. to make things worse, the Windows boot loader was no longer there and I have to access it through the UEFI settings. How do I change this to automatically boot windows again?

How do we edit grub in a UEFI HDD to have multi boot option having more than just one linux one Windows OS, readily being selected and run at PC startup

I recently installed Zorin OS on my Lenovo Yoga 2. I completely got rid of Windows and am not dual booting. I am now trying to get back to Windows 10. I created a Windows 10 USB drive, but I can't get the computer to boot from it. When I change the UEFI boot order, it still boots into Zorin, and when I go back to the UEFI, it has changed the boot order back. I also created another Zorin USB drive, thinking I would boot from it, then format the Zorin partition so it would have to boot from USB. Same thing, it just won't boot from USB. Is there a way to trigger booting from USB from within Zorin? If not, any ideas on how to get rid of Zorin some other way?

I have a 2TB external SSD connected to a server. Using the server, I booted into the RHEL8 installer and successfully installed onto the external drive, however during the post-install reboot (and all reboot attempts after) the boot hangs at the switch-root step. Obviously the drive is recognized by the system and is able to provide the bootloader / initramfs, but dracut/systemd seems to just hit a hard stop when switching to /sysroot using the slash partition on the drive (non-llvm ext4 formatted). The interesting thing is several machines (laptops, desktops) will successfully boot from the drive into the OS, indicating the server chipset/usb bus is the cause. Unfortunately, I am stuck with the server (a Gigabyte... didn't realize they made more than boards) and the external drive (a Kanguru UltraLock SSD). Kanguru claims there are no drivers required for their drive, which makes sense. Also, I have not attempted to update/flash the UEFI on the server. I've avoided it for fear of making things worse. I did try adding a short delay in a pre-mount-hooked dracut script within the initramfs, thinking it might be a race condition of some sort, but it had no effect. That script also does an ls /dev/disk/by-uuid which shows the drives and partitions as they should be (i.e. the root=UUID:.. in the kernelopts matches the partition in the list). Anything obvious I'm missing? Update: I realized that I actually used a PXE kickstart to install the OS because I was unable to boot into the RHEL8 installer using my thumbdrive USB stick. Initially I thought the issue was my stick (old USB2 SanDisk), so I switched to my PXE server on my laptop. I just tested a theory now and was able to boot into System Rescue (CD) on that same USB stick that did not work with the RHEL8 installer. System Rescue CD uses the typical embedded busybox boot approach, which seems to point to a dracut issue in RHEL with regard to the server's hardware or USB connections? Thanks in advance!

RHEL 8 supports UEFI in Secure Boot enabled as well as with Disabled mode. That is a very good change, as Most of the new machines only support UEFI mode. But while installing RHEL 8 with UEFI mode, why in custom partition; I had to choose both * /boot in standard partition * /boot/efi The Custom partition wold looks like this

/                LVM 
/boot            Standard
/boot/efi        
/swap            LVM

Why not only /boot/efi works ? I tried going with /boot/efi in different file formats, removing /boot. But every time it says format not supported. Now I am stuck with this question help me understand this.