[opensuse] Can no longer dual boot after installing Leap 15
In the past I was always able to dual boot into window or Linux. I can no longer do this after installing Leap 15. Is it possible to fix this problem? Terry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/02/2019 21.05, Terrance Eck wrote:
In the past I was always able to dual boot into window or Linux. I can no longer do this after installing Leap 15. Is it possible to fix this problem?
Please describe in more detail. You could download and run this script: https://github.com/arvidjaar/bootinfoscript/raw/master/bootinfoscript post the resulting file on susepaste.org for a limited time, and post here the link. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Terrance Eck composed on 2019-02-05 14:05 (UTC-0600):
In the past I was always able to dual boot into window or Linux. I can no longer do this after installing Leap 15. Is it possible to fix this problem?
Simple answer: yes In addition to doing what Carlos suggested, tell us what exactly can and can't you do now. Which Windows version? Can you boot anything that's been installed? If so, what? Which Linux were you using before 15? Was your "installation" an upgrade? If yes, which was it, "online" (zypper), or "offline" (DVD or USB boot)? Which installation instructions did you follow (URL)? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Solved the problem. There is function under Yast to modify the boot loader. I still do not understand why SUSE changed the default installation. On 2/5/19 2:05 PM, Terrance Eck wrote:
In the past I was always able to dual boot into window or Linux. I can no longer do this after installing Leap 15. Is it possible to fix this problem?
Terry
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Terrance Eck
Solved the problem. There is function under Yast to modify the boot loader. I still do not understand why SUSE changed the default installation.
On 2/5/19 2:05 PM, Terrance Eck wrote:
In the past I was always able to dual boot into window or Linux. I can no longer do this after installing Leap 15. Is it possible to fix this problem?
Terry
there are a lot of ways in yast to modify the boot loader and you have provided as much information of the pertinent function as you have of the problem. if my car will not start and that is all the information I provide, how would you attempt to provide a solution? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan composed on 2019-02-05 17:56 (UTC-0500):
* Terrance Eck [02-05-19 16:41]:
Terrance Eck wrote:
In the past I was always able to dual boot into window or Linux. I can no longer do this after installing Leap 15. Is it possible to fix this problem?
Solved the problem. There is function under Yast to modify the boot loader. I still do not understand why SUSE changed the default installation.
What did you upgrade from? Had you still been using Grub Legacy and got switched to Grub2?
there are a lot of ways in yast to modify the boot loader and you have provided as much information of the pertinent function as you have of the problem. if my car will not start and that is all the information I provide, how would you attempt to provide a solution?
I know, I know! Call AAA!!! -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/02/2019 23.39, Terrance Eck wrote:
Solved the problem. There is function under Yast to modify the boot loader. I still do not understand why SUSE changed the default installation.
Neither can we, as you give no explanation whatsoever! -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
In data mercoledì 6 febbraio 2019 10:52:07 CET, Carlos E. R. ha scritto:
On 05/02/2019 23.39, Terrance Eck wrote:
Solved the problem. There is function under Yast to modify the boot loader. I still do not understand why SUSE changed the default installation.
Neither can we, as you give no explanation whatsoever! Well you can, mostly by the information he did not provide. He said: there is a function in the boot loader. The only function that might be there is "search for other OS". Now why he had it deactivated I do not know. What also happens is, that the first time you boot it is not available / Leap does not see a windows. Then after a dracut -f with that option activated, it actually does.
I remember I had this on one machine. But it was a new installation not an update. The problem there was the older BIOS that was not able to handle GPT partitions. So you had to format the disc with with an old 11.1 life disc and then disregard all the warnings of the installer about "you did choose not to modify the mbr, there is no boot partition defined" and so on. And it worked flawlessly. When booting I found that, from the scratch, search for other OS was not(!) activated. So there might be a glitch in the installer, maybe when using expert partitioning during installation, if he used a new install. Or if he choose "import existing installation". I would be nice if he could confirm, so we could search for this in Leap 15.1 alpha and correct it, if applicable. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2019 09.44, stakanov wrote:
In data mercoledì 6 febbraio 2019 10:52:07 CET, Carlos E. R. ha scritto:
On 05/02/2019 23.39, Terrance Eck wrote:
Solved the problem. There is function under Yast to modify the boot loader. I still do not understand why SUSE changed the default installation.
Neither can we, as you give no explanation whatsoever! Well you can, mostly by the information he did not provide. He said: there is a function in the boot loader. The only function that might be there is "search for other OS".
That is my guess as well, but he did not say.
I remember I had this on one machine. But it was a new installation not an update. The problem there was the older BIOS that was not able to handle GPT partitions.
This machine as GPT disks on an old BIOS machine, boots just fine :-) The trick is that GPT disks can also have an MBR sector which the BIOS finds ;-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
In data giovedì 7 febbraio 2019 10:59:14 CET, Carlos E. R. ha scritto:
On 07/02/2019 09.44, stakanov wrote:
In data mercoledì 6 febbraio 2019 10:52:07 CET, Carlos E. R. ha scritto:
On 05/02/2019 23.39, Terrance Eck wrote:
Solved the problem. There is function under Yast to modify the boot loader. I still do not understand why SUSE changed the default installation.
Neither can we, as you give no explanation whatsoever!
Well you can, mostly by the information he did not provide. He said: there is a function in the boot loader. The only function that might be there is "search for other OS".
That is my guess as well, but he did not say.
I remember I had this on one machine. But it was a new installation not an update. The problem there was the older BIOS that was not able to handle GPT partitions.
This machine as GPT disks on an old BIOS machine, boots just fine :-)
The trick is that GPT disks can also have an MBR sector which the BIOS finds ;-) Yes, but with me, that did not work (SSD disc new, in a HP PC from 2004. Quite a mature buddy. At that time there was still no GPT, and BIOS does not know what that is. But when I tried to set this in Leap 15 Installer, he said "set the boot bit" but he did not do it. And defaulted all the time to GPT formatting. So tell me the secret, how to work around it? I did with the 11.1 live disk and told the yast Leap15 installer: don't you dare to touch. And all went well.
_________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2019-02-07 a las 13:27 +0100, stakanov escribió:
In data giovedì 7 febbraio 2019 10:59:14 CET, Carlos E. R. ha scritto:
On 07/02/2019 09.44, stakanov wrote: ...
I remember I had this on one machine. But it was a new installation not an update. The problem there was the older BIOS that was not able to handle GPT partitions.
This machine as GPT disks on an old BIOS machine, boots just fine :-)
The trick is that GPT disks can also have an MBR sector which the BIOS finds ;-) Yes, but with me, that did not work (SSD disc new, in a HP PC from 2004. Quite a mature buddy. At that time there was still no GPT, and BIOS does not know what that is. But when I tried to set this in Leap 15 Installer, he said "set the boot bit" but he did not do it. And defaulted all the time to GPT formatting.
Yes, use GPT formatting and a BIOS partition if it wants it. YaST did it automatically, using 42.2 or 42.3. The partitioner in 15 has been reworked and may lack features or have bugs. The boot disk can not be larger than 2 Teras, because the BIOS can not read it for booting. A data disk can be larger. When using "bootinfoscript" on it, I see: => Syslinux GPTMBR (4.04-5.01) is installed in the MBR of /dev/sda. sda1: __________________________________________________________________________ File system: BIOS Boot partition Boot sector type: - Boot sector info: sda2: __________________________________________________________________________ File system: ext4 Boot sector type: Grub2 (v1.99-2.00) Boot sector info: Grub2 (v2.00) is installed in the boot sector of sda2 and looks at sector 21781680 of the same hard drive for core.img. core.img is at this location and looks for (,gpt2)/boot/grub2. It also embeds following components: modules ------------------------------------------------------- fshelp ext2 part_gpt biosdisk ------------------------------------------------------- Operating System: openSUSE Leap 42.1 (x86_64) Boot files: /boot/grub2/grub.cfg /boot/grub2/custom.cfg /etc/fstab /boot/grub2/i386-pc/core.img sda3: __________________________________________________________________________ File system: swap Boot sector type: - Boot sector info: sda4: __________________________________________________________________________ File system: ext2 Boot sector type: - Boot sector info: Operating System: Boot files: sda5: __________________________________________________________________________ File system: ext2 Boot sector type: Grub2 (v1.99-2.00) Boot sector info: Grub2 (v2.00) is installed in the boot sector of sda5 and looks at sector 75616872 of the same hard drive for core.img. core.img is at this location and looks for (,gpt5)/grub2. It also embeds following components: ... - -- Cheers Carlos E. R. (from openSUSE 15.0 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXFwshxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVK2MAnRiKb2BP2k5ehWc4qvje UFgoXAiJAJ9XPaa488a8nBV4oYHaRMXKwZApiQ== =Y91W -----END PGP SIGNATURE-----
participants (5)
-
Carlos E. R. -
Felix Miata -
Patrick Shanahan -
stakanov -
Terrance Eck