On which disk is your Windows install and on which disk did you install Ubuntu? @wizardfromoz is probably one of the best people to help you since he has a lot of experience with dual/multi-boots.Okay here it goes.
On which disk is your Windows install and on which disk did you install Ubuntu? @wizardfromoz is probably one of the best people to help you since he has a lot of experience with dual/multi-boots.Okay here it goes.
Okay so here's what I have.On which disk is your Windows install and on which disk did you install Ubuntu? @wizardfromoz is probably one of the best people to help you since he has a lot of experience with dual/multi-boots.
sudo nano /etc/default/grub
cat /etc/default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
sudo update-grub
...@wizardfromoz is probably one of the best people to help you since he has a lot of experience with dual/multi-boots.
Mint is based on Ubuntu, what @Fanboi mentioned still applies for Ubuntu.As you see right here I don't use Linux Mint it's rather Ubuntu Linux 24.04.02 LTS including GNU nano 7.2. See?
Mint is based on Ubuntu, what @Fanboi mentioned still applies for Ubuntu.
If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || ec>
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
GRUB_DISABLE_OS_PROBER=false
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
luke1@luke1-B450-AORUS-ELITE:~$ sudo nano /etc/default/grub
[sudo] password for luke1:
luke1@luke1-B450-AORUS-ELITE:~$ sudo update-grub
[sudo] password for luke1:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.11.0-19-generic
Found initrd image: /boot/initrd.img-6.11.0-19-generic
Found linux image: /boot/vmlinuz-6.11.0-17-generic
Found initrd image: /boot/initrd.img-6.11.0-17-generic
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/sdb1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
luke1@luke1-B450-AORUS-ELITE:~$ sudo nano /etc/default/grub
luke1@luke1-B450-AORUS-ELITE:~$
This shows that it detected Windows and it should have added a Windows entry to the Grub menu. Try rebooting your system and see if you have both an Ubunut and Windows boot option.luke1@luke1-B450-AORUS-ELITE:~$ sudo update-grub [sudo] password for luke1: Sourcing file `/etc/default/grub' Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.11.0-19-generic Found initrd image: /boot/initrd.img-6.11.0-19-generic Found linux image: /boot/vmlinuz-6.11.0-17-generic Found initrd image: /boot/initrd.img-6.11.0-17-generic Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Windows Boot Manager on /dev/sdb1@/efi/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for UEFI Firmware Settings ... done
I did it anyway.This shows that it detected Windows and it should have added a Windows entry to the Grub menu. Try rebooting your system and see if you have both an Ubunut and Windows boot option.
Depending on your circumstances, you might want to think twice about displaying your password on a youtube video
Okay, I see two things: 1. It boots from post screen very fast. 2. You have succeeded.My own selfie stick got broken not so quite long time ago so it was hard to me to record it without visible keyboard anyway I was holding my own smartphone with two hands. You see in some cases you can’t record video without for instance smartphone nowadays…etc. Well I can at least give a try to re-record it once again and upload share a link with to you to anyone right here.
By saying Reboot did you mean to Power Off… instead of Restart?Okay, I see two things: 1. It boots from post screen very fast. 2. You have succeeded.
My guess: Somehow the wrong disk is booting and starting up Ubuntu on the right disk (something like HD0 boots GRUB, GRUB on HD0 boots Ubuntu on HD1 straight from GRUB). Never seen this happen, but there are stranger things and it could very well have been you somehow overwrote the UEFI partition on the Windows disk by mistake.
So...
1. Instead of rebooting, do a full shutdown instead (always -- until resolved)
2. Now call the UEFI boot menu, F12 (I think it's F12, I looked up Aorus mobos)
3. Try booting the first disk / entry.
If this does the same thing, repeat steps 1 & 2, then try the next disk / entry... and so on.
4. When you find the right device / entry, you'll need to open your UEFI settings.
4.1. Power off completely.
4.2. Mash the Del key (again, what the spec sheet says, it may vary)
5. In the menu go to "Boot" and make sure "Option #1" points to the correct disk / entry
6. Disable "Fast Boot" as this can mess with things in general.
If that doesn't work, we'll have to pull up a GRUB console (mashing Shift) and see what's going on. That's a separate post, though. Good luck, let us know.
when we say re-boot , then yes it means a full power reboot of the whole system, not a re-start which only reinitiates the OSBy saying Reboot did you mean to Power Off
I did it more or less like the way you told me to do so.Okay, I see two things: 1. It boots from post screen very fast. 2. You have succeeded.
My guess: Somehow the wrong disk is booting and starting up Ubuntu on the right disk (something like HD0 boots GRUB, GRUB on HD0 boots Ubuntu on HD1 straight from GRUB). Never seen this happen, but there are stranger things and it could very well have been you somehow overwrote the UEFI partition on the Windows disk by mistake.
So...
1. Instead of rebooting, do a full shutdown instead (always -- until resolved)
2. Now call the UEFI boot menu, F12 (I think it's F12, I looked up Aorus mobos)
3. Try booting the first disk / entry.
If this does the same thing, repeat steps 1 & 2, then try the next disk / entry... and so on.
4. When you find the right device / entry, you'll need to open your UEFI settings.
4.1. Power off completely.
4.2. Mash the Del key (again, what the spec sheet says, it may vary)
5. In the menu go to "Boot" and make sure "Option #1" points to the correct disk / entry
6. Disable "Fast Boot" as this can mess with things in general.
If that doesn't work, we'll have to pull up a GRUB console (mashing Shift) and see what's going on. That's a separate post, though. Good luck, let us know.
You need to access your motherboard's UEFI/BIOS... If pressing F12 at startup doesn't bring up the boot menu, you may want to check you board's manual. Alternatively, just try and get into the Settings. Again, check the manual if Del doesn't work. What's happening is you're booting straight into the bootloader on HDX and that won't do so well. No matter what changes you make on HDY, if HDX is higher boot priority, only the UEFI/BIOS can change that, and to a more limited degree, the program efibootmgr (not 100% with all boards/configs which is why I suggest you enter the BIOS/UEFI).
I did it more or less like the way you told me to do so.
I did it however I’m still having black screen after doing that.You need to access your motherboard's UEFI/BIOS... If pressing F12 at startup doesn't bring up the boot menu, you may want to check you board's manual. Alternatively, just try and get into the Settings. Again, check the manual if Del doesn't work. What's happening is you're booting straight into the bootloader on HDX and that won't do so well. No matter what changes you make on HDY, if HDX is higher boot priority, only the UEFI/BIOS can change that, and to a more limited degree, the program efibootmgr (not 100% with all boards/configs which is why I suggest you enter the BIOS/UEFI).
Switch on your PC while pressing F12 repeatedly (or whatever they key -- check your manual). Failing that, move straight to trying it with Del (or, again, whatever the manual says).