That grubby command would only show the linux kernels.
Did you run the kernel-install command as suggested while in the chroot?
The windows and uefi entries are non-fedora which is why they show up when running grub2-mkconfig.
Once booted back into the chroot environment as shown above we can do a bit more investigating.
I suspect it is related to the content of /etc/default/grub so please post that as soon as possible.
So i need to boot with live media and then
Do
1.su
2.mount -t btrfs -o subvol=root,compress=zstd:1 /dev/nvme0n1p6 /mnt
3.for file in sys run proc dev ; do mount -o bind /$file /mnt/$file ; done
4.chroot /mnt
5.mount -a
and after that
Kernel-install add-all
and post the output right?
Or the output of
cat /etc/default/grub
You can do both.
Also efibootmgr and kernel-install without arguments.
Ok now its confusing
So i need to do
kernel-install
and
efibootmgr
after the mount
Everything after chroot.
here are some result @vekruse
root@localhost-live:/# mount
/dev/nvme0n1p6 on / type btrfs (rw,relatime,seclabel,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/root)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel)
tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,size=1597428k,nr_inodes=819200,mode=755,inode64)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=4096k,nr_inodes=989057,mode=755,inode64)
/dev/nvme0n1p5 on /boot type ext4 (rw,relatime,seclabel)
/dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro)
/dev/nvme0n1p6 on /home type btrfs (rw,relatime,seclabel,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/home)
root@localhost-live:/# kernel-install
Kernel image not installed to '/usr/lib/modules/6.2.9-300.fc38.x86_64/vmlinuz', requiring manual kernel image path specification.
root@localhost-live:/# kernel-install add-all
Not adding version '6.2.9-300.fc38.x86_64', because kernel image not found.
Not adding version '6.3.11-200.fc38.x86_64', because kernel image not found.
Not adding version '6.3.12-200.fc38.x86_64', because kernel image not found.
^C
root@localhost-live:/# efibootmgr
EFI variables are not supported on this system.
root@localhost-live:/# cat /etc/default/grub
GRUB_TIMEOUT="10"
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT="saved"
GRUB_DISABLE_SUBMENU="true"
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rhgb quiet pci=noaer rd.driver.blacklist=nouveau modprobe.blacklist=nouveau"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG="true"
#GRUB_THEME="/boot/grub2/themes/CyberEXS/theme.txt"
root@localhost-live:/#
setting GRUB_ENABLE_BLSCFG="false" has also no luck
This mostly looks good. Can you run efibootmgr before mounting and chroot.
There seems to be a bit of cleanup in /usr/lib/modules, but that will be for later.
efkbootmgr needs the file system /sys/firmware/efi/efivars to be mounted, or it won’t work.
here is the result just live booted and run this
[liveuser@localhost-live ~]$ efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0005,0000,0001,0004,2001,2002,2003
Boot0000* Windows Boot Manager HD(1,GPT,c1bdfa82-dc3d-455b-a06f-1d4fb8afb2f1,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot0001* Linpus lite HD(1,MBR,0x3eb3c,0x800,0x1d0d000)/File(\EFI\Boot\grubx64.efi)RC
Boot0002* EFI PXE 0 for IPv4 (98-FA-9B-02-A4-7D) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(98fa9b02a47d,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0003* EFI PXE 0 for IPv6 (98-FA-9B-02-A4-7D) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(98fa9b02a47d,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0004* Fedora HD(1,GPT,c1bdfa82-dc3d-455b-a06f-1d4fb8afb2f1,0x800,0x32000)/File(\EFI\fedora\shim.efi) File(.䍒)
Boot0005* Fedora HD(1,GPT,c1bdfa82-dc3d-455b-a06f-1d4fb8afb2f1,0x800,0x32000)/File(\EFI\fedora\shimx64.efi)
Boot0009* EFI PXE 0 for IPv4 (98-FA-9B-02-A4-7D) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(98fa9b02a47d,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
[liveuser@localhost-live ~]$
With this error
I would guess that the live image is booted in legacy mode and the install is done in uefi mode.
Please shutdown and then when booting the live image make certain that it is booted into uefi mode.
Then while still in the live media please run sudo fdisk -l
We need to know if the possibility is with windows installed in uefi mode or not?
This could account for the inability to see fedora if the 2 OSes were installed in different boot modes. I do not suspect this but it may be worth checking.
I also would suggest removing the extra devices as much as possible while doing this troubleshooting.
Your post with the outpuf from the windows disk manager shows additional drives / partitions identified as D, E, F, G, & I as well as an efi partition of only 100MB.
When you select the boot entry in the UEFI menu, do you select the Linpus entry or one of the Fedora entries?
And, if I may ask, where does the Linupus entry come from?
the linpus entry
fedora entries are from the disk itself but those doesnt boot leads back to grub menu which has only windows boot option
i am not sure how to do that my lagacy boot option is disabled afaik but i am double checking it now
@vekruse
now you know thw answer about Linpus entry
Here are some images
Note I manually renamed Windows Boot to Windows 11 with grub-cutomizer gui which is showing here
As far as I can see the linpus will load some version which is not the Fedora grub2 version. Everything we have done until now is based on the assumption that you would load the Fedora version of Grub2. So, can you try the Fedora entries.
i already tried those arent booting and leads back to grub boot menu which has only windows 11 entry
More likely that the /sys/firmware/efi/efivars wasn’t available in the chroot environment.
Possibly, but they should have been if the live media were booted to uefi mode since /sys was mounted into the chroot environment. His output from eifbootmgr in the live media was correct.
@sreyaz01
Please boot to the live media then run efibootmgr so we can confirm efi boot mode.
If you have already done the chroot you can simply exit then run that command with the same effect.
Then in the chroot environment run the same command to ensure that it carries over.
without chroot
[liveuser@localhost-live ~]$ efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0005,0000,0001,0004,2001,2002,2003
Boot0000* Windows Boot Manager HD(1,GPT,c1bdfa82-dc3d-455b-a06f-1d4fb8afb2f1,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot0001* Linpus lite HD(1,MBR,0x3eb3c,0x800,0x1d0d000)/File(\EFI\Boot\grubx64.efi)RC
Boot0002* EFI PXE 0 for IPv4 (98-FA-9B-02-A4-7D) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(98fa9b02a47d,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0003* EFI PXE 0 for IPv6 (98-FA-9B-02-A4-7D) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(98fa9b02a47d,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0004* Fedora HD(1,GPT,c1bdfa82-dc3d-455b-a06f-1d4fb8afb2f1,0x800,0x32000)/File(\EFI\fedora\shim.efi) File(.䍒)
Boot0005* Fedora HD(1,GPT,c1bdfa82-dc3d-455b-a06f-1d4fb8afb2f1,0x800,0x32000)/File(\EFI\fedora\shimx64.efi)
Boot0009* EFI PXE 0 for IPv4 (98-FA-9B-02-A4-7D) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(98fa9b02a47d,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
[liveuser@localhost-live ~]$
[liveuser@localhost-live ~]$ efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0005,0000,0001,0004,2001,2002,2003
Boot0000* Windows Boot Manager HD(1,GPT,c1bdfa82-dc3d-455b-a06f-1d4fb8afb2f1,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot0001* Linpus lite HD(1,MBR,0x3eb3c,0x800,0x1d0d000)/File(\EFI\Boot\grubx64.efi)RC
Boot0002* EFI PXE 0 for IPv4 (98-FA-9B-02-A4-7D) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(98fa9b02a47d,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0003* EFI PXE 0 for IPv6 (98-FA-9B-02-A4-7D) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(98fa9b02a47d,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0004* Fedora HD(1,GPT,c1bdfa82-dc3d-455b-a06f-1d4fb8afb2f1,0x800,0x32000)/File(\EFI\fedora\shim.efi) File(.䍒)
Boot0005* Fedora HD(1,GPT,c1bdfa82-dc3d-455b-a06f-1d4fb8afb2f1,0x800,0x32000)/File(\EFI\fedora\shimx64.efi)
Boot0009* EFI PXE 0 for IPv4 (98-FA-9B-02-A4-7D) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(98fa9b02a47d,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
[liveuser@localhost-live ~]$
with Chroot
[liveuser@localhost-live ~]$ su
[root@localhost-live liveuser]# mount -t btrfs -o subvol=root,compress=zstd:1 /dev/nvme0n1p6 /mnt
[root@localhost-live liveuser]# for file in sys run proc dev ; do mount -o bind /$file /mnt/$file ; done
[root@localhost-live liveuser]# chroot /mnt
root@localhost-live:/# efibootmgr
EFI variables are not supported on this system.
root@localhost-live:/# mount -a
root@localhost-live:/# efibootmgr
EFI variables are not supported on this system.
root@localhost-live:/#
It is, but it should be bind-mounted the same way as /sys, /dev, and /run. Otherwise the filesystem becomes invisible after chroot.
root@localhost-live:/# fdisk -l
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10SPZX-24Z
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 79E6F94C-9018-4A40-A99F-47033A0BD840
Device Start End Sectors Size Type
/dev/sda1 2048 209745919 209743872 100G Microsoft basic data
/dev/sda2 209747968 695216127 485468160 231.5G Microsoft basic data
/dev/sda3 695216128 1324367871 629151744 300G Microsoft basic data
/dev/sda4 1324369920 1953521663 629151744 300G Microsoft basic data
Disk /dev/nvme0n1: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 970 EVO Plus 250GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 904AD29E-932B-4900-98F3-714A1C92FC49
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 206847 204800 100M EFI System
/dev/nvme0n1p2 206848 239615 32768 16M Microsoft reserved
/dev/nvme0n1p3 239616 309039045 308799430 147.2G Microsoft basic data
/dev/nvme0n1p4 309039104 310302719 1263616 617M Windows recovery environment
/dev/nvme0n1p5 310302720 312399871 2097152 1G Linux filesystem
/dev/nvme0n1p6 312399872 488396799 175996928 83.9G Linux filesystem
Disk /dev/sdb: 14.53 GiB, 15597568000 bytes, 30464000 sectors
Disk model: Cruzer Blade
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0003eb3c
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 30463999 30461952 14.5G c W95 FAT32 (LBA)
Disk /dev/loop0: 1.85 GiB, 1987653632 bytes, 3882136 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 7.57 GiB, 8128561152 bytes, 15876096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop2: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/live-rw: 7.57 GiB, 8128561152 bytes, 15876096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/live-base: 7.57 GiB, 8128561152 bytes, 15876096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/zram0: 7.62 GiB, 8177844224 bytes, 1996544 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
i forgot to post this result
also I am sorry but i cant remove HDD right now its inbuilt in laptop and will be hard to remove rn.
please focus on nvme0n1 which has all os related files
sda is only for storage