home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.suse      Suse is actually not that bad      138,051 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 136,732 of 138,051   
   Carlos E.R. to intertubes@gmx.net   
   Re: Dual Boot Problem   
   25 Jan 19 21:59:59   
   
   From: robin_listas@es.invalid   
      
   On 25/01/2019 18.55, intertubes@gmx.net wrote:   
   > On Friday, January 25, 2019 at 2:16:08 PM UTC+1, Carlos E.R. wrote:   
   >> On 23/01/2019 15.08, intertubes@gmx.net wrote:   
   >>> I have a Laptop with Windows 10 and Leap 15 installed, UEFI.   
   >>>   
   >>> Up until recently there were three boot entries - the usual two options   
   for Opensuse and "Windows Boot Manager".   
   >>> The last one has vanished and I can't see why.   
   >>> The only way I can enter Mordor now is to change the boot order in the   
   Bios to move the Mordor Boot Manager above opensuse.   
   >>>   
   >>> Any clues as to what could have happened or where I should be looking?   
   >>>   
   >>> I don't use that laptop much so I can't remember what the last thing I did   
   was, but my guess would be applying Opensuse patches early in January.   
   >>   
   >> Open YaST, go to "Boot Loader" module, and select the "bootloader   
   >> options" tab. In there, make sure that "Probe foreign OS" is ticket.   
   >>   
   >> If is not, tick and click OK to apply.   
   >>   
   >> If it is, change the timeout in one second, then OK to apply (this trick   
   >> makes YaST apply "changes" and write again all the boot files.   
   >>   
   >>   
   >> Try and comment back :-)   
      
      
   > Ho hum!   
   > On the day I made that posting, I applied the Opensuse updates (I think   
   there was one each for yast-bootmanager and for grub2) and then went into Win   
   10 and applied the January updates.   
   > Seeing your post today I changed the UEFI boot-order again to go into   
   Opensuse.   
   > It offered the usual 2 x Linux and 1 x Win 10 again.  Without me having to   
   apply either of the solutions here.   
   > Witchcraft?  (that implies Win 10 was the problem!)   
      
   Hypothesis:   
      
   Windows update changed something in itself that made Grub not find the   
   Windows boot partition. For example, change the partition UUID. A   
   subsequent update in Linux would make it "probe" of other systems and   
   thus Windows would be visible in Grub.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca