XPost: uk.comp.os.linux   
   From: nospam@needed.invalid   
      
   On 4/15/2024 8:06 AM, Java Jive wrote:   
   > Problem as per subject.  I have a laptop triple booting into Ubuntu 22,   
   Windows 7, & Windows 10.  GRUB has the correct settings to remember the last   
   boot choice and correctly does so for Ubuntu & Windows 10, but, if I choose   
   Windows 7, at the next    
   boot it offers Windows 10 as the default, not Windows 7.  All I can find   
   online is many different explanations for how to set up dual-booting and have   
   it remember the last choice, not what to do if for some reason this doesn't   
   work.   
   >   
   > Can anyone advise?   
   >   
   > The relevant settings are reproduced below, and yes I have remembered to run   
   update-grub, in fact I've done it twice, but despite everything looking   
   correct, the problem persists.  Note that in the resulting grub.cfg the two   
   Windows sections are    
   identical except where they should differ in designating the relevant   
   partition, and that the W10 section has an extra penultimate line 'drivemap   
   ...', but I don't know enough about how GRUB works to know whether that would   
   be relevant ...   
   >   
   > /etc/default/grub:   
   >   
   > # 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=saved   
   > GRUB_SAVEDEFAULT=true   
   > GRUB_TIMEOUT_STYLE=hidden   
   > GRUB_TIMEOUT=5   
   > GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`   
   > GRUB_CMDLINE_LINUX_DEFAULT=""   
   > GRUB_CMDLINE_LINUX=""   
   >   
   > [rest is commented out, until]   
   >   
   > # Uncomment to get a beep at grub start   
   > GRUB_INIT_TUNE="480 440 1"   
   >   
   > /boot/grub/grub.cfg:   
   >   
   > [...]   
   >   
   > ### BEGIN /etc/grub.d/30_os-prober ###   
   > menuentry 'Windows 10 (on /dev/sda1)' --class windows --class os   
   $menuentry_id_option 'osprober-chain-C00A7FAA0A7F9BDA' {   
   >     savedefault   
   >     insmod part_msdos   
   >     insmod ntfs   
   >     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  C00A7FAA0A7F9BDA   
   >     else   
   >       search --no-floppy --fs-uuid --set=root C00A7FAA0A7F9BDA   
   >     fi   
   >     parttool ${root} hidden-   
   >     drivemap -s (hd0) ${root}   
   >     chainloader +1   
   > }   
   > menuentry 'Windows 7 (on /dev/sda2)' --class windows --class os   
   $menuentry_id_option 'osprober-chain-C00A7FAA0A7F9BDA' {   
   >     savedefault   
   >     insmod part_msdos   
   >     insmod ntfs   
   >     set root='hd0,msdos2'   
   >     if [ x$feature_platform_search_hint = xy ]; then   
   >       search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2   
   --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  C00A7FAA0A7F9BDA   
   >     else   
   >       search --no-floppy --fs-uuid --set=root C00A7FAA0A7F9BDA   
   >     fi   
   >     parttool ${root} hidden-   
   >     chainloader +1   
   > }   
   >   
   > [...]   
   >   
   > [In case it matters, but I don't think it does, this laptop is a Dell   
   Precision M6700 which I bought recently because the video card in my best old   
   Dell Precision M6300 died, which is the default manner for those PCs to die    
   -  even though this new    
   one also has a good 17" screen, it's wider and shorter than the old one, which   
   I preferred. There are a couple of over-priced video cards on eBay for nearly   
   the same sort of price as you could get a working machine of the same model,   
   but it's just not    
   worth spending that sort of money on such an old machine. Sniff!]   
   >   
      
   If the Windows Boot Manager intercepts your chainload, it might   
   well boot the "default" OS selection. Instead of going "GRUB --> Windows 7",   
   it might well be going "GRUB --> Windows Boot Manager --> (Default selection,   
   currently Windows 10).   
      
   Remember - these things have folders in ESP, a "Ubuntu" folder, a "Windows"   
   folder.   
   There is no "Windows 7" folder and "Windows 10" folder. I would be more hopeful   
   for your mission, if the storage in ESP was separated. The other guys who   
   suggested   
   separate disks (as a means to get "unique"/"single" boot entries), are   
   basically   
   trying to do the same thing. They're trying to create entries that cannot   
   foul up. Now, the problem with this, is the motherboard UEFI, does not "Well   
   Tolerate"   
   finding multiple Windows Boot Manager folders on the computer during the UEFI   
   scan. It can   
   easily throw a hissy fit - this especially happens when two disks are the same   
   model (I have lots of WDC Black 1TB scratch drives, select SATA1, and SATA2   
   boots!).   
      
   You shouldn't be booting that way anyway :-)   
      
   You should be using Popup Boot. On my Asus machine, that's F8.   
   Then I see the blue-bordered rectangle, with entries like...   
      
   1) "some ubuntu choice"  ( for which there is a folder in ESP ) -- then the   
   GRUB menu appears and you select a Linux OS   
      
   2) "some Windows Boot Manager choice"  (for which there is a folder in ESP   
   labeled Windows)   
      
   When you select (2), you end up in a dialog like this.   
      
         Windows 10   
      
         Windows 7   
      
   The dialog can either have two tiles ("wrong") or the window   
   can have a black background and two lines of text like it   
   is Windows XP ("right"). The reason the legacy mode is right,   
   is it only required one boot cycle to get into any OS in that sub-menu.   
   If you allow the stupid Microsoft default way to rule (tile interface), it   
   takes   
   two boot cycles to get into the non-default Windows OS.   
      
   To enable the legacy boot menu in the Windows Boot Manager on a single disk,   
   try   
      
      administrator terminal:   
      
         bcdedit /set {bootmgr} displaybootmenu True   
      
   I think the notion of chainloading directly, on the four partition legacy   
   MSDOS disk,   
   that makes more sense. That's more likely to work the way you expected, but   
   considering   
   the "litter" that Windows brings with it, it's a bit harder to manage the   
   Extended/Logical   
   and keep everybody happy in there. I don't like having to fool around with   
   resizing Extended/Logical to add OSes to a multiboot. That's why it is GPT,   
   Popup Boot,   
   two stage selection. I have had a shitload of OSes on an Extended/Logical, just   
   for the experience, but I deleted that drive content as it was getting   
   on my nerves.   
      
   If you take hands-off-keyboard, turn on system power, Microsoft set up that   
   UEFI spec   
   and ESP, to benefit themselves. The Windows Boot Manager is likely to boot,   
   even after   
   GRUB is installed. There is some utility for changing that behavior (long   
   string of letters,   
   list of bootable things), but for the user who doesn't know about it,   
   Microsoft may appear   
   to have the upper hand.   
      
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)