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.

I have a computer about ten years old, and I would like to install a PCIe M.2 NVMe SSD in it. Unfortunately, the BIOS cannot boot from the SSD, because it doesn't know how to boot from a PCIe SSD. This means that I must use SATA instead of PCIe, which means giving up the speed benefits PCIe would offer. I've been trying to find a way which would allow me to boot into Windows 10 (on the PCIe SSD) and here's what I'm thinking: - I use a separate SATA SSD and install Linux on it - the BIOS can boot from that. - I dd my current Windows 10 installation (presently on a regular HDD) to the NVMe SSD, using the Linux install (should work, right?) - I set up the GRUB bootloader to allow me to boot either into Linux or the Windows 10 installation on the NVMe SSD. If GRUB knows how to setup the PCIe SSD, it should be able to bootstrap Windows 10 - right? Does this have a chance of working? Thanks!

I am using Debian 12, and I am trying to add a new line in the grub menu. This PC has two SSD drives, the first one has Windows 10 and the second one has Debian 12. **How can I boot Windows from the Debian Grub?** The output of lsblk -f is: NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sdb ├─sda1 ext4 1.0 fec4ac01-0518-472e-a773-398e89e38283 378.9G 14% / ├─sda2 └─sda5 swap 1 1bb8cacf-1774-44b8-9ae7-f939de2cf231 [SWAP] nvme0n1 ├─nvme0n1p1 vfat FAT32 4643-C150 ├─nvme0n1p2 ├─nvme0n1p3 ntfs 18964D7F964D5DFE └─nvme0n1p4 ntfs 3480ABF880ABBF2C And the output of sudo blkid /dev/nvme0n1p3 is: BLOCK_SIZE="512" UUID="18964D7F964D5DFE" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="548d364e-48f1-499a-8eb3-75e127585773" After that I updated the grub: sudo update-grub The file in /etc/grub.d/40_custom is: #!/bin/sh exec tail -n +3 $0 # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. menuentry "Windows 10"{ search --fs-uuid --no-floppy --set=root 18964D7F964D5DFE chainloader /EFI/Microsoft/Boot/bootmgfw.efi } But after the reboot, the grub entry appers but there is a message that says that there is not any system... Any ideas to solve this? Thanks in advance!

When I turn on the PC the GRUB screen doesn't display and goes directly to any OS (which is configured on the F2 boot start list) and when I tried to find the /etc/default/grub file it's missing there. I am using dual boot with Windows 11 (default from my PC). I would like to know how to recover it.

I'm not too familiar with Linux in general so please bare with me. | TLDR | | -------- | | I tried installing KDE Neon on an external USB hard drive, but when I tried booting my computer back into KDE Neon (not from the USB hard drive, the computer already had KDE Neon installed on its hard drive) I got the GRUB Rescue prompt. Attempting to fix this by booting back into the KDE Neon install USB and running boot-repair made it so now when the computer is booted, the GRUB "Select Operating System" menu appears but selecting any option caused the computer to freeze and become unresponsive. | I have a pretty old computer that I installed KDE Neon on a long time ago. I wanted to install a full copy of KDE Neon onto an external hard drive like what is done in this video. When rebooting my computer after this attempt and booting back into KDE Neon which was on the computers hard drive already, I saw the prompt for GRUB Rescue show on the screen which makes me think I mightove forgotten to change the boot loader installation device to the external hard drive, and may have left it on the internal hard drive that already had KDE Neon installed. To try and fix this I booted back into my KDE Neon install USB and installed boot-repair then ran the recommended repair all following this article. After this I restarted, and now when trying to boot back into KDE Neon which again was on the computers hard drive already, it showed the GRUB "Select Operating System" menu, but whenever I choose any option from the list, pressed C to open the GRUB console, or pressed E to edit, everything would just freeze and become unresponsive forcing me to manually turn off the computer using the power button. Is there any way I could boot back into my existing KDE Neon install on the computers hard drive again like I was able to before I tried installing KDE Neon on the external drive (which also didn't boot by the way)? Again the computer I'm using for this is very old if that matters. Thanks. | System Information | | | -------- | -------------- | | GRUB Version | Running grub-install -V on the KDE Neon install USB returns grub-install (GRUB) 2.06-2ubuntu7.1 | | KDE Neon Version | 5.27 | | Ubuntu Version | 22.04 | | Computer | Dell XPS 400 (Released 2005) | | CPU | Intel Pentium D CPU 2.80GHZ |

Referring to here , with a configuration as > grub> root (hd0,0) > grub> kernel /vmlinuz-i686-up-4GB root=/dev/hda9 > grub> boot > > The preceding is usually sufficient to boot a Linux box. The standalone root statement tells the partition containing the kernel. The kernel statement describes the path and filename, _within the partition containing the kernel_, of the kernel. The argument to the root= argument to the kernel statement tells the partition containing /sbin/init, which of course turns out to be the root partition in the booted system. > > Be careful of these duelling root keywords. The standalone one is the root as seen from grub, and contains the kernel. The argument to the kernel statement is the root as seen from the fully booted system, and contains /sbin/init. I don't quite get the meaning of the 2 root configs. Does it mean the OS stays on /dev/hda9 to be mounted on (hd0, 0), or the OS is /vmlinuz to be mounted to /dev/had9 ?

Bluetooth is a mess in linux. After hours of trying to make bluetooth even turn on, I found out that adding this to the grub fixed the issue to where now it's at least turning on albeit not pairing with any devices. I went and reconfigured my GRUB legacy in /etc/default/grub and added GRUB_CMDLINE_LINUX_DEFAULT=btusb.enable_autosuspend=n But can someone tell me what this actually did and why it worked? My guess is it's telling bluetooth to not suspend automatically but why would bluetooth do that in the first place when turning on my arch device? I am using Arch linux on a dell with Intel centrum 1000 N

Today on an internal, legacy centos 6.10 server I run > yum update It downloaded and installed, without errors, these packages: kernel-headers-2.6.32-754.15.3.el6.x86_64 Tue 25 Jun 2019 09:46:52 AM CEST microcode_ctl-1.17-33.13.el6_10.x86_64 Tue 25 Jun 2019 09:46:51 AM CEST kernel-2.6.32-754.15.3.el6.x86_64 Tue 25 Jun 2019 09:46:48 AM CEST bind-utils-9.8.2-0.68.rc1.el6_10.3.x86_64 Tue 25 Jun 2019 09:46:40 AM CEST bind-libs-9.8.2-0.68.rc1.el6_10.3.x86_64 Tue 25 Jun 2019 09:46:39 AM CEST kernel-firmware-2.6.32-754.15.3.el6.noarch Tue 25 Jun 2019 09:46:38 AM CEST python-libs-2.6.6-68.el6_10.x86_64 Tue 25 Jun 2019 09:46:32 AM CEST python-2.6.6-68.el6_10.x86_64 Tue 25 Jun 2019 09:46:29 AM CEST I check /etc/grub.conf and it lists as first entry the new kernel: > title CentOS (2.6.32-754.15.3.el6.x86_64) I reboot the server and... > uname -a > > Linux goofy.local 2.6.32-754.14.2.el6.x86_64 In the last months I see other kernel 2.6.* updates, they were fine. Why isn't the new kernel running? How can I troubleshoot this? --- These are the new files in /boot -rw-r--r-- 1 root root 106K 2019-06-18 18:29 config-2.6.32-754.15.3.el6.x86_64 -rw------- 1 root root 18M 2019-06-25 09:47 initramfs-2.6.32-754.15.3.el6.x86_64.img -rw-r--r-- 1 root root 212K 2019-06-18 18:29 symvers-2.6.32-754.15.3.el6.x86_64.gz -rw-r--r-- 1 root root 2.6M 2019-06-18 18:29 System.map-2.6.32-754.15.3.el6.x86_64 -rwxr-xr-x 1 root root 4.2M 2019-06-18 18:29 vmlinuz-2.6.32-754.15.3.el6.x86_64 -rw-r--r-- 1 root root 171 2019-06-18 18:29 .vmlinuz-2.6.32-754.15.3.el6.x86_64.hmac --- > grubby --default-kernel > > /boot/vmlinuz-2.6.32-754.15.3.el6.x86_64

I have a virtual box running with CentOS. I have attached a new virtual disk to the existing CentOS VM and I'm now trying to install GRUB on this newly attached disk. Later, I will bring up a second VM with a newly prepared bootable hard disk with a custom root filesystem and kernel. I have tried the following steps: - Attached a new virtual disk to the existing working CentOS machine. - Created a new partition with fdisk /dev/sdb. While partitioning, I chose the options primary partition, partition number 1 and other default options. - Formatted the disk with mkfs.ext3 /dev/sdb1. - Mounted the disk to /media/new_drive. - Installed GRUB grub-install /dev/sdb1 --root-directory=/media/new_drive/. After this, the second VM with the newly prepared hard disk didn't boot; I got the error: could not read from the boot medium. It seems the MBR is not updated after grub-install, but I can see GRUB installed under /boot/grub on the new drive. But the worst thing is, it has corrupted my existing CentOS GRUB: The CentOS VM hangs showing a black screen with the only text being GRUB. Why does grub-install /dev/sdb1 not modify the MBR of sdb1? Is this not the right way to install GRUB on new drive?

I just upgraded my parrot OS using the command line. And when I restarted the pc this error occurred : *Symbol ‘grub disk native sectors’ not found*. I have tried set command to solve this issue but didn’t work. When I start it in the normal mode , same error occurs … How to solve it?. Thanks in advance.

I've got Windows and Ubuntu installed. After turning off secure boot and selecting legacy boot mode, I proceeded with installation of Kali Linux from the flash drive. During the installation I have been warned that the only other OS detected was Ubuntu and it asked whether it want to store it in MBR or hard for booting unfortunately I selected Yes. Now I am unable open my windows 10. What shall I do now to show my Windows 10 in GRUB2 menu?

I went over many posts, books, blogs on Grub, UEFI,... and I can't figure out how to fix my grub. Situation: My main disk (SSD 500GB, now in /dev/sda) run debian using Grub2 in UEFI. All good. After messing, now I have two disks running debian: 1- previous one (SSD running debian), not booting anymore in UEFI or Legacy 2- an WD disk (1TB in /dev/sdc) running Debian 11 contains legacy MBR and grub From grub in legacy I can run WD-Debian 11 or SSD-Debian Computer does not boot in UEFI I want to switch my system back to UEFI. However I can't boot as UEFI, no grub starts in UEFI. lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT. sda 8:0 0 447.1G 0 disk ├─sda1 8:1 0 512M 0 part ├─sda2 8:2 0 414.7G 0 part └─sda3 8:3 0 31.9G 0 part sdb 8:16 0 7.3T 0 disk sdc 8:32 0 931.5G 0 disk ├─sdc1 8:33 0 930.6G 0 part / ├─sdc2 8:34 0 1K 0 part └─sdc5 8:37 0 976M 0 part [SWAP] I tried to install grub in sda, (sudo grub-install /dev/sda): But got error: > Installing for i386-pc platform. grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible. grub-install: error: embedding is not possible, but this is required for cross-disk install. I tried to use debian live, gparted live, etc but I could not find grub-install in these live iso. How could I rescue the grub in UEFI mode in my SSD disk? Thanks

Trying to make an USB with full installed Linux distros, I've landed on a bunch of pages (like this: How can I repair grub? (How to get Ubuntu back after installing Windows?) ) explaining how to install/reinstall grub on a device. Trying to understand the procedures and methods, some questions raised: - How grub-install command knows where to find (partitions of) O.S.s to boot? I saw that - f.e. using a Linux USB live drive - we mount one of the partitions of the device where we want to install Grub and with the command: for i in /sys /proc /run /dev; do sudo mount --bind "$i" "/mnt$i"; done we mount all the directory grub-install needs to locate all the O.S. installed on all the recognized devices (as all the devices under the /dev/ directory should be taken into consideration). Did I got it the right way? I also thought that, once you mount and set up everything, grub-install creates a configuration which tells grub where the O.S. to boot are located on the device... Is that right? Is this configuration manually editable after the installation (e.g. Install a new S.O. and manually adding its boot instructions into grub configuration)? - What are the exact differences among grub-pc, grub-efi and grub-legacy packages? I know that grub can be installed both for legacy boot (boot with BIOS from MBR) and for EFI boot; but I also noticed that grub-install command, which you can launch after the installation of one among grub-pc, grub-efi and grub-legacy packages, have the --efi-directory parameter. This parameter allows you to specify where the ESP partition is mounted on the running system and, therefore, I think it allows to install Grub in EFI boot mode... Is this right? Does this mean that I can install Grub in EFI or BIOS mode with any of these packages? If yes, how? How can I specify that I want to install Grub in Bios or EFI mode with grub-install after the installation of one of these packages? Moreover, I noticed that it seems you can install only one of these packages (if you already have one and try to install a different one with aptitude, aptitude marks the currently installed package for removal), why this happens?

I installed MX Linux into my ssd to dual boot it with PopOS but I chose the grub option because it said that I can dual boot easily with it. But that one choice doomed my life. my main hard disk has been overwritten by grub and grub now doesn't recognise PopOS as a choice. I have been researching for months while using mx but nothing, absolutely nothing. Tried to edit the grub.cfg file, tried to edit the mx boot options, tried to literally **remove** the ssd and try to force boot the hard drive but it was of no use, nothing I found from here, youtube, mx forums, grub's website, nothing could help. I wanted to install windows as a replacement to the other os on my hard drive but for some reason grub prevented everything. I can provide you any details just please help me I feel like my pc is stuck in this state with no other way to even replace the os'es. I'm literally stuck with MX Linux

I tried to install Linux Mint Cinnamon on my Acer laptop, but after the installation there comes up a grub bootloader screen with this text. https://ibb.co/P9r0hpw So what can I do? It's now enough for me if I can format my harddisk and install only windows. Old System: Windows 10 Bios Legacy Mode Installation from Linux Mint in EFI mode.

In the /boot/grub/grub.conf file, how would I change the path name of where the kernel boots from if the boot file is located somewhere outside of /boot? For example, I would want to load the boot kernel from /home/root/kernel How would I specify that? The grub.conf file looks like this right now > title CentOS (2.6.32-358.6.1.el6.i686) > > kernel /vmlinuz-2.6.32-358.6.1.el6.i686 >initrd /initramfs-2.6.32-358.6.1.el6.i686.img I tried /../home/root/kernel but it didn't work. Would I have to change the partition?

I write all of you because I have expended two weks trying to solve this problem, I have seen a lot of youtube videos and read a lot of forums but I cannot fix this. I want to clarify that I'm only a user but I'm not an expert in linux or windows.I have already installed dual-boot pcs in newer computers but I really really realy need some help! I'm having a lot of troubles trying to have pentium4 pc with dual boot, the idea is to have windows 7 and linux Mint. I also know that it is possible to have a dual OS system in this pc because this pc had windows 7 and it was updated to windows 10, afnter that I installed linux and it was fine, but as W10 was too slow for this pc, I re-installed a version of windows 7 and when I tried to re-install linux, all the problems started. After installing linux and rebooting, the grub does not work and show the grub-rescue message. I have tried all the standard solutions, changing the root in the grub-rescue terminal, using live usb sessions to install and use grub-installer, boot-repair, grub-customize and in windows, grub2win and easybcd2,4 but I always have this problem. I have triend installing the grub in the harddrive and also in the linux partition. I also have formatted my hard drive and installed windows and linux several times and I always have the same problem. When I want to boot windows I have to use bootrec to rebuild the bcd. The pc has a pentium 4, cpu 300GHz, RAM 2 Gb, 32bit and a HD of 160 Gb and I have 5 partitions: - sda1 100MB reserved for the system primary partition - sda2 C: primary partition NTFS for windows - sda3 D. primary partition NTFS for storage - Sda5 Logical partition ext 4, for linux - sda6 logical partition swap I don't know if the problem is because I try to install a recent version of linux and the grub assume that I have UEFi and search for efi . It is that, what would be the grub configuration for a pc without UEFI? (I also have tried to install Mint 14 and a few other light distros) I also have tried with the easybcd2.4 and it allowed me to create a boot menu with windows and linux but it fails to boot linux. I have tried to edit NEoGrub menu.lst file but I cannot find the right configuration. Do you have a sample file that could work for my configuration? I've read that it is based on grub4dos syntax but I have no idea about this. I want to resume my questions: - Is it different the grub.cfg file for PCs without UEFI? If it is different, someone could provide an example ( or help me to create) a grub cfg file for a dual windows-linux ? - I think that it could be easier to change the bcd configuration using the correct menu.lst file, someone could help me to write an appropiate file for my configuration? - If I'm doing the things in a really wrong direction, could you please show me how I could install the two OS and which version would fit more with my pc? - Do I need to provide more information related to my boot problem? How could I get it? - Could this be a problem related with windows and I should need an specific version? I want to sincerely thanks to the people that will take their time to read this message and for the comments and ideas that you could have.

My overall goal is to dual boot Linux Mint and Windows 10. The motherboard is legacy bios only. Firstly I installed Linux Mint then Windows 10 on a secondary partition. Because I forgot to make a separate boot partition... I moved everything 1000MB to the right, and created a ext4 boot partition at the beginning of sda. Running boot repair on a live Ubuntu USB with the options: - Separate /boot partition: sda4 (the first partition on disk) - GRUB Legacy (figured that was for legacy bios) - Reinstall GRUB (default) - Unhide boot menu: 10s (default) Boot Repair hangs at Purge kernels then reinstall last kernel sda1 (ins). This may require several minuets... I have let this running overnight, the process is still running. I have done a reboot and tried again, let the process run for 3 days. Nothing different. Boot Info Summary: http://paste.ubuntu.com/17678629/ *I have had gparted open at the same time, assuming that wouldn't have an affect.*

I recently installed Android x86 7.1-r3-i386 in a partition in the same hard drive my Debian 10 i386 system is. I edited /boot/grub/menu.lst to add a new option to run Android x86 in the boot menu. But after running update-grub and rebooting my computer the new entry doesn't show. Here is the content of /boot/grub/menu.lst > # menu.lst - See: grub(8), info grub, update-grub(8) > # grub-install(8), grub-floppy(8), > # grub-md5-crypt, /usr/share/doc/grub > # and /usr/share/doc/grub-legacy-doc/. > > ## default num > # Set the default entry to the entry number NUM. Numbering starts from 0, and > # the entry number 0 is the default if the command is not used. > # > # You can specify 'saved' instead of a number. In this case, the default entry > # is the entry saved with the command 'savedefault'. > # WARNING: If you are using dmraid do not change this entry to 'saved' or your > # array will desync and will not let you boot your system. > default 0 > > ## timeout sec > # Set a timeout, in SEC seconds, before automatically booting the default entry > # (normally the first entry defined). > timeout 5 > > # Pretty colours > color cyan/blue white/blue > > ## password ['--md5'] passwd > # If used in the first section of a menu file, disable all interactive editing > # control (menu entry editor and command-line) and entries protected by the > # command 'lock' > # e.g. password topsecret > # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/ > # password topsecret > > # > # examples > # > # title Windows 95/98/NT/2000 > # root (hd0,0) > # makeactive > # chainloader +1 > # > # title Linux > # root (hd0,1) > # kernel /vmlinuz root=/dev/hda2 ro > # > > # > # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST > > ### BEGIN AUTOMAGIC KERNELS LIST > ## lines between the AUTOMAGIC KERNELS LIST markers will be modified > ## by the debian update-grub script except for the default options below > > ## DO NOT UNCOMMENT THEM, Just edit them to your needs > > ## ## Start Default Options ## > ## default kernel options > ## default kernel options for automagic boot options > ## If you want special options for specific kernels use kopt_x_y_z > ## where x.y.z is kernel version. Minor versions can be omitted. > ## e.g. kopt=root=/dev/hda1 ro > ## kopt_2_6_8=root=/dev/hdc1 ro > ## kopt_2_6_8_2_686=root=/dev/hdc2 ro > # kopt=root=UUID=936b24d8-6e0b-4f5c-847f-0c1414bc48b1 ro > > ## default grub root device > ## e.g. groot=(hd0,0) > # groot=(hd0,0) > > ## should update-grub create alternative automagic boot options > ## e.g. alternative=true > ## alternative=false > # alternative=true > > ## should update-grub lock alternative automagic boot options > ## e.g. lockalternative=true > ## lockalternative=false > # lockalternative=false > > ## additional options to use with the default boot option, but not with the > ## alternatives > ## e.g. defoptions=vga=791 resume=/dev/hda5 > # defoptions= > > ## should update-grub lock old automagic boot options > ## e.g. lockold=false > ## lockold=true > # lockold=false > > ## Xen hypervisor options to use with the default Xen boot option > # xenhopt= > > ## Xen Linux kernel options to use with the default Xen boot option > # xenkopt=console=tty0 > > ## altoption boot targets option > ## multiple altoptions lines are allowed > ## e.g. altoptions=(extra menu suffix) extra boot options > ## altoptions=(single-user) single > # altoptions=(single-user mode) single > > ## controls how many kernels should be put into the menu.lst > ## only counts the first occurence of a kernel, not the > ## alternative kernel options > ## e.g. howmany=all > ## howmany=7 > # howmany=all > > ## should update-grub create memtest86 boot option > ## e.g. memtest86=true > ## memtest86=false > # memtest86=true > > ## should update-grub adjust the value of the default booted system > ## can be true or false > # updatedefaultentry=false > > ## should update-grub add savedefault to the default options > ## can be true or false > # savedefault=false > > ## ## End Default Options ## > > title Debian GNU/Linux, kernel 4.19.0-8-686-pae > root (hd0,0) > kernel /boot/vmlinuz-4.19.0-8-686-pae root=UUID=936b24d8-6e0b-4f5c-847f-0c1414bc48b1 ro > initrd /boot/initrd.img-4.19.0-8-686-pae > > title Debian GNU/Linux, kernel 4.19.0-8-686-pae (single-user mode) > root (hd0,0) > kernel /boot/vmlinuz-4.19.0-8-686-pae root=UUID=936b24d8-6e0b-4f5c-847f-0c1414bc48b1 ro single > initrd /boot/initrd.img-4.19.0-8-686-pae > > ### END DEBIAN AUTOMAGIC KERNELS LIST > > title Android x86 > root (hd0,3) > kernel /android-7.1-r3/kernel root=UUID=033e8fc7-4cfe-9454-bc59-df7329ca862d > initrd /android-7.1-r3/initrd.img What am I missing?

I have ssd and hdd. Both use mbr scheme. On my ssd I have mint and it is running well. I want to dual boot and install win10 on hdd but I have problem creating legacy bootable usb with win10 using linux mint to create. I have win10 iso and created bootable usb in legacy mode but when I select to boot from "usb drive" ( not uefi:usb drive) have an error "boot disc not found please insert bootable disc..." and wont start with installation however uefi mode boot fine from usb but because of mbr scheme cant install win10 on hdd. I dont want to change mbr to gpt. I want to stay on mbr. Can you please tell me how to create legacy bootable usb with win10 iso. Thanks!