![]() There is no need to use all caps when posting and it is usually considered rude and YELLING in tone when done. NOTE THAT THE FORUM JUST TOLD ME THAT AS A NEW USER I MUST WAIT 21 HOURS BEFORE └─sda6 LVM2_member LVM2 001 Gxu9EG-VDTd-Rw8v-haMR-Zgm5-uxb2-C8cjpa dev/mmcblk0p231 3934979 1.9G 6 fs]# lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS Sector size (logical/physical): 4096 bytes / 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I’m tempted to just replace /usr/libexec/os-probes/mounted/20microsoft with a file that outputs that when called with /dev/sda3 … but I also think this would be a bad idea, since os-probe for some reason I can’t figure out isn’t running the mounted/efi/20microsoft script, and the reason it’s not running it is probably fs]# fdisk -l Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Looking at that file it seems that if there is an $efi/$microsoft/$boot/$bootmgfw (I think it’s testing a file location but I haven’t figured out how all these variables are being set) it would output the line I need, I think: /dev/sda3:Windows Boot Manager:Windows. I see there is also a /usr/libexec/os-probes/mounted/efi/20microsoft. Now 20microsoft is being called with a third argument “fuse” or “fuseblk” and I don’t know what this means, so I deleted the experimental file. It logs “Skipping legacy bootloaders on UEFI system” ifĪs an experiment I created the above file and ran it. That script is called /usr/libexec/os-probes/mounted/20microsoft. Specifically, the microsoft detector is logging “Skipping legacy bootloaders on UEFI system.” I see they log stuff, so by running journalctl I see their output. Something interesting: os-probe is a shell script and runs other OS-specific shell scripts. I’ve googled ’ “Fedora 37” add windows to grub’ which even autocompleted so I assume it’s a common search, but after checking 20+ pages none seem to address this issue. Fedora Linux (6.0.86_64) 37 (Workstation Edition).Now I have a grub menu that stays up long enough to read, and I see it only has: I ran grub2-mkconfig -o /boot/grub2/grub.cfg I tried grub2-editenv - unset menu_auto_hide In /etc/default/grub I changed GRUB_TIMEOUT=-1. After much googling I determined I DO have a Grub working but it probably has auto_hide enabled, seemingly, and a timeout so fast I don’t see it. I thought I didn’t have a grub at all and Fedora was booting directly. (I made a backup copy of /etc, but not of /boot, so I don’t think I have a backup of what I actually need to simply diff myself.) Is there any way to recover the perfectly-working GRUB I had for the last 3-4 years? (This was a clean install, albeit on top of a working 33 that had been upgraded since 27 or something over 4-5 years and never a boot problem. Was the Fedora clean install supposed to prompt me for boot preferences? (It didn’t.)
0 Comments
Leave a Reply. |