On kernel version *4.15.0-sabayon*, the only way to load X is with the kernel options: acpi_osi=! acpi_osi='Windows 2009' (and acpi=off but that's radical and leaves me with no sensors). Otherwise I get unresponsive black screen and no obvious error in the X.org log. The problem with this option is that it turns off the *Elan 1200 touchpad* (not only for me, other people complain about it as well). So I'm looking for other (if possible tested) kernel options which might work on my laptop (or similar). I've tested already many permutations of different windows versions and modeset and acpi_rev_override=5 and pcie_port_pm=off, but obviously I can't cover them all so if anyone had success with this, please share.

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 am trying to dual boot Linux on my laptop (Dell XPS 15) which is running Windows 10 Pro. I did not have any problem dual booting the two operating systems on my desktop. I cannot boot up **ANY** Linux Distro, I have tried Mint, Ubuntu and Elementary OS. Whenever I try to boot from a live USB, I get the this message on all attempts: **GNU GRUB version 2.02~beta2-9ubuntu1** **Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists are possible device or file completions.** **grub>** When I type in "boot" I get the error: **you need to load the kernel first.** Secure boot is disabled, and I have tried both in legacy and UEFI BIOS mode. I have never come across this error before, what causes it?

I'm using dual boot Linux Mint 17.1 Cinnamon and Windows XP. So I want change grub2 black screen and I've tried to install gfxmenu theme for grub but it is not working; I see it's not installed in grub but in boot directory. I've tried also grub-customizer tool but it also does not work. ftp://cathbard.com/binary/cathbard-grub-mint-ladder_0.0.1-1_all.deb Above link is a file of grub ladder that I've installed.

I changed tomorrowto my old hdd to save some old files. After I installed again the new disk I cannot boot anymore in fedora and I see only the grub command display. Now I have only my phone so I took a picture and I don’t know what to enter in the ‘root=‘ command as you can see on the picture. Could you help me to restore the boot process on my pc?

My computer was running a dual boot with Arch and Manjaro on their own partitions. I decided I wanted to exchange Manjaro for Debian, so I flashed the USB and deleted the Manjaro partition. Apparently that's the one Grub wants to boot from though, so I get shifted into grub rescue> mode. I want to at least boot into Arch, and ideally get a grub menu where I can boot from the USB containing the Debian installer. The problem is when I run insmod normal, I get the error in the title.

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...

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 want to install grub on SD card because my laptop don't boot from external sata port. I've the SSD connected to the laptop through the external port sata to make it easier for me to boot the operating system also on my desktop. I would like only to have to install grub in the SD, but maybe the only solution is to install linux on the card just to modify the grub configuration and be able to launch the existing operating system on the ssd disk. I'll never use the OS written on the SD. Is possible setup grub on SD card? Thanks

I installed Debian Jessie on a new hard disk, and wanted to boot from this new disk. At the end of Debian setup, I choosed setup Grub also. But when booting, Grub falls into rescue mode with a File not found error. I tried several guides I found around to try to have it up again, with no success. Here is my configuration (I booted on a live Knoppix distro) knoppix@Microknoppix:~$ lsblk -f NAME FSTYPE LABEL MOUNTPOINT sda └─sda1 ext4 sdb ├─sdb1 ext4 ├─sdb2 └─sdb5 swap sdc └─sdc1 ntfs Stock sdd ├─sdd1 ext4 Debian ├─sdd2 └─sdd5 swap sdh └─sdh1 ntfs My Passport sr0 iso9660 KNOPPIX /mnt-system sr1 udf WD SmartWare zram0 swap [SWAP] cloop0 iso9660 KNOPPIX_FS /KNOPPIX blkid /dev/cloop0: LABEL="KNOPPIX_FS" TYPE="iso9660" /dev/zram0: UUID="770d53d4-32d4-4810-988a-ffb80edecc8f" TYPE="swap" /dev/sda1: UUID="2a0bdecf-9074-40de-8d23-bcaf01af17bb" TYPE="ext4" /dev/sdb1: UUID="a4eaeb3b-27d1-4285-a364-fcdfa601fb82" TYPE="ext4" /dev/sdb5: UUID="76381585-358a-46a1-bc16-feb51b08fe90" TYPE="swap" /dev/sdc1: LABEL="Stock" UUID="A2904C19904BF1F9" TYPE="ntfs" /dev/sdd1: LABEL="Debian" UUID="c45c0acc-f414-4c3e-a4ba-b3c1a33c3cbd" TYPE="ext4" /dev/sdd5: UUID="2f0c8892-f4a8-4312-bc19-1e8d72f23e6c" TYPE="swap" /dev/sr0: LABEL="KNOPPIX" TYPE="iso9660" /dev/sdh1: LABEL="My Passport" UUID="325220A852207331" TYPE="ntfs" /dev/sr1: LABEL="WD SmartWare" TYPE="udf" parted (parted) print all Model: ATA Maxtor 7V250F0 (scsi) Disk /dev/sda: 251GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 251GB 251GB primary ext4 boot Model: ATA Maxtor 7V300F0 (scsi) Disk /dev/sdb: 300GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 284GB 284GB primary ext4 2 284GB 300GB 16.1GB extended 5 284GB 300GB 16.1GB logical linux-swap(v1) ... The grub.cfg file contains thism which looks correct ### BEGIN /etc/grub.d/10_linux ### function gfxmode { set gfxpayload="${1}" } set linux_gfx_mode= export linux_gfx_mode menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-2a0bdecf-9074-40de-8d23-bcaf01af17bb' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 2a0bdecf-9074-40de-8d23-bcaf01af17bb else search --no-floppy --fs-uuid --set=root 2a0bdecf-9074-40de-8d23-bcaf01af17bb fi echo 'Loading Linux 3.16.0-4-amd64 ...' linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=2a0bdecf-9074-40de-8d23-bcaf01af17bb ro quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.16.0-4-amd64 } Note that the .mod files are in a seperate directory /boot/grub/i386-pc Is it usual? Thank you for helping me understand what is wrong and how to solve this?

I had Linux Mint on dualboot, but I was having problems with the audio, so I deleted the partition using disk manager on windows 10, and was going to install Debian, but when I try to boot Debian from the usb, it goes to GRUB and I am unable to get past this. I tried many solutions on various forums and none of them have removed this obstacle. Anyone got any ideas?

I'm having this issue for a few months now...I was using fedora for a long time but it broke after an update and since then I can't install or run a live environment of almost no distro...so far only Linux mint will boot into the live environment but when I install it I get the same error at bootup and the PC turns off. I've tried other distros but no luck. I'm stuck on windows for the time being. The error(s): Could not create MokListRT: Volume Full Could not create MokListXRT: Volume Full Could not create SbatLevelRT: Volume Full Could not create MokListTrustedRT: Volume Full Something has gone seriously wrong: import_mok_state() failed: Volume Full I would really appreciate any help with this issue

I have a Dell PowerEdge R420 which has installed Centos 7 and was working fine. One day I removed the disks that Centos 7 was installed (2 disks with RAID-1 layout) and I installed another clean disk to the rack in order to install Red Hat Enterprise Linux 7. For reasons I cannot describe here I wanted to have a disk with RHEL 7 installed so I can use it with another server. The installation of RHEL was also fine, but when I tried to put back the initial disks with Centos 7 into my initial Dell server I saw that I was stuck in Grub rescue mode. I used these steps in order to reinstall grub and know I am stuck into emergency mode. I see the following message: > Welcome to emergency mode! After logging in type "journalctl -xb" to > view system logs, "systemctl reboot" to reboot, "systemctl default" to > try again to boot into default mode. Give root password for > maintenance (or type Control-D to continue).

I am trying to setup proxmox on Dell r720xd, which does have UEFI boot option but can not boot from PCIe nvme drives. If I install proxmox (or any os) on a usb flash, it boots fine. For testing, I installed CentOS with advanced partitioning, and used USB flash as /boot partition, and nvme for all other partitions and that too works flawlessly. With proxmox, there is no custom partitioning option during the setup, so I was unable to set usb key as /boot partition during install. Other option listed in proxmox forums are - use clover as bootloader on a USB key, described here - install debian first with custom partition and then install proxmox over it and remove debian kernel. Obviously clover is adding a boot partition on usb and then forwarding the control to nvme. My question is, how to install proxmox on nvme and then migrate the /boot partition to the usb flash? Seems like a very straight forward process and I followed this guide to handle it, however, I could not get it to work. grub2 always complained with messages like - not matching UUID - you need to load kernel first - and so on any hints please. P.S. I also tried to edit the centos /boot installed on flash drive, by using grub2-mkconfig which found the proxmox and updated the grub.cfg but still got errors during boot like - error: cant't find command linux - error: cant't find command initrd fixed these errors (ref ) by linuxefi and initrdefi but then it could not find the drive with given UUID

I was trying to update grub config via Grub customizer, and it failed, and when I run update-grub2 I get this error output of update-grub2:

ks@ks-pc:~$ sudo update-grub2
[sudo] password for ks: 
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.2.0-25-generic
Found initrd image: /boot/initrd.img-6.2.0-25-generic
Found linux image: /boot/vmlinuz-6.2.0-24-generic
Found initrd image: /boot/initrd.img-6.2.0-24-generic
Found linux image: /boot/vmlinuz-5.15.0-76-generic
Found initrd image: /boot/initrd.img-5.15.0-76-generic
Found linux image: /boot/vmlinuz-6.2.0-25-generic
Found initrd image: /boot/initrd.img-6.2.0-25-generic
Found linux image: /boot/vmlinuz-6.2.0-24-generic
Found initrd image: /boot/initrd.img-6.2.0-24-generic
Found linux image: /boot/vmlinuz-5.15.0-76-generic
Found initrd image: /boot/initrd.img-5.15.0-76-generic
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Found linux image: /boot/vmlinuz-6.2.0-25-generic
Found initrd image: /boot/initrd.img-6.2.0-25-generic
Found linux image: /boot/vmlinuz-6.2.0-24-generic
Found initrd image: /boot/initrd.img-6.2.0-24-generic
Found linux image: /boot/vmlinuz-5.15.0-76-generic
Found initrd image: /boot/initrd.img-5.15.0-76-generic
Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
error: out of memory.
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 702
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.

/boot/grub/grub.cfg.new: https://pastebin.com/VpaF4Epa

For some time back I installed Linux mint 17 on my desktop machine, which is a dell studio 540. During the installation process, I did not have any internet connection, because my wireless card needed a proprietary driver to work (fixed using fwcutter). So recently I wanted to install a newer distro kernel due to some bug fixes, using the software manager. It installs fine, but when rebooting the grub won't run the new kernel. So I thought I should check out the grub versions: Grub version output from terminal: grub --version grub (GNU GRUB 0.97) Grub version from the grub menu when booting into grub: GNU GRUB version 2.02-beta2-9 Why are they not the same ? Could it be a missing update, due to the lost internet connection during installing the Linux mint ? btw: I have no problem installing new kernels on my laptop, which did not need any proprietary driver for the wireless.

AFAIK grub-mkconfig and grub-update/update-grub commands only run on the device that they are installed on. I want to run the commands on a usb drive, but - I don't know how to install them on the usb - I can't make the ones that are installed on my computer to run on usb(i.e they should update the usb's grub.cfg file) How can I do either of them? BTW I am using manjaro KDE