[opensuse-factory] replacement for master-boot-code
A recent Tumbleweed snapshot removed master-boot-code. What is the replacement, has the replacement been tested? The code in master-boot-record.rpm did just look for a primary, active partition and loads/runs the startup code from that partition. What I learned the hard was a couple of times is that Windows, after certain updates are installed, will not boot anymore unless its boot partition is marked as active in the partition table. I think sometimes it would refuse to install certain updates if its boot partition is not marked as active. Olaf
On Thu, Mar 21, 2019 at 5:18 PM Olaf Hering <olaf@aepfle.de> wrote:
A recent Tumbleweed snapshot removed master-boot-code. What is the replacement, has the replacement been tested?
Sysliux MBR?
The code in master-boot-record.rpm did just look for a primary, active partition and loads/runs the startup code from that partition. What I learned the hard was a couple of times is that Windows, after certain updates are installed, will not boot anymore unless its boot partition is marked as active in the partition table. I think sometimes it would refuse to install certain updates if its boot partition is not marked as active.
Should work with syslinux. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2019-03-21 at 15:18 +0100, Olaf Hering wrote:
A recent Tumbleweed snapshot removed master-boot-code. What is the replacement, has the replacement been tested?
The code in master-boot-record.rpm did just look for a primary, active partition and loads/runs the startup code from that partition. What I learned the hard was a couple of times is that Windows, after certain updates are installed, will not boot anymore unless its boot partition is marked as active in the partition table. I think sometimes it would refuse to install certain updates if its boot partition is not marked as active.
Olaf
According the information provided with the del req for master-boot- code (which, by the way was broken for a long time - see http://bugzilla.suse.com/show_bug.cgi?id=1125307 ) the replacement is to use /usr/share/syslinux/mbr.bin as provided by syslinux instead of the .mbr provided by m-b-c. Cheers Dominique
On Thu, Mar 21, 2019 at 3:26 PM Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
According the information provided with the del req for master-boot- code (which, by the way was broken for a long time - see http://bugzilla.suse.com/show_bug.cgi?id=1125307 )
the replacement is to use
/usr/share/syslinux/mbr.bin
as provided by syslinux instead of the .mbr provided by m-b-c.
What does this mean for the typical user? master-boot-code is indeed gone. My system boots okay. So I guess all is okay. It just sounds like an important thing. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 3/21/19 10:13 AM, Roger Oberholtzer wrote:
On Thu, Mar 21, 2019 at 3:26 PM Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
According the information provided with the del req for master-boot- code (which, by the way was broken for a long time - see http://bugzilla.suse.com/show_bug.cgi?id=1125307 )
the replacement is to use
/usr/share/syslinux/mbr.bin
as provided by syslinux instead of the .mbr provided by m-b-c.
What does this mean for the typical user? master-boot-code is indeed gone. My system boots okay. So I guess all is okay. It just sounds like an important thing.
The bug report shown above states that the deleted package has not been used for 5 years. You will not see any change, just as I have not, and I always boot from a partition, not the master boot record, which contains generic code. Also, the one system of mine that dual-boots Windows and Tumbleweed also works. Of course, it was necessary to install Windows first, but so far, no updates have broken it. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El jue., 21 mar. 2019 a las 11:18, Olaf Hering (<olaf@aepfle.de>) escribió:
A recent Tumbleweed snapshot removed master-boot-code. What is the replacement, has the replacement been tested?
The code in master-boot-record.rpm did just look for a primary, active partition and loads/runs the startup code from that partition. What I learned the hard was a couple of times is that Windows, after certain updates are installed, will not boot anymore unless its boot partition is marked as active in the partition table. I think sometimes it would refuse to install certain updates if its boot partition is not marked as active.
In the case of my pc, zypper asked me to place the installation DVD, to outdated the package master-boot-code. Other package with problems in the upgrade is pciutils-ids, which in case of upgrade, zypper will uninstall other packages, and to prevent this, I must to select to conserve the same version. Regards, Juan -- USA LINUX OPENSUSE QUE ES SOFTWARE LIBRE, NO NECESITAS PIRATEAR NADA Y NI TE VAS A PREOCUPAR MAS POR LOS VIRUS Y SPYWARES: http://www.opensuse.org/es/ Puedes visitar mi blog en: http://jerbes.blogspot.com.ar/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 21/03/2019 15.18, Olaf Hering wrote:
A recent Tumbleweed snapshot removed master-boot-code. What is the replacement, has the replacement been tested?
The code in master-boot-record.rpm did just look for a primary, active partition and loads/runs the startup code from that partition. What I learned the hard was a couple of times is that Windows, after certain updates are installed, will not boot anymore unless its boot partition is marked as active in the partition table. I think sometimes it would refuse to install certain updates if its boot partition is not marked as active.
Re the Windows part: Yes. Assuming non GPT disk. Yes, let the disk have a standard MBR, and mark the grub partition as bootable, then install grub there. When you need to update windows, change the boot mark to the Windows partition, when finished the update, undo boot mark with rescue disk. This is a nuisance. What I use is what Neil Rickert suggested time ago: <https://lists.opensuse.org/opensuse/2016-04/msg01023.html> The MBR is replaced with one that ignores the boot mark and always boots the one you want, that has grub. And, the Windows partition is marked bootable, but ignored. Windows is happy, boots from grub, and updates happily. I use that with my laptop that had W7 and now W10, so the thing works :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (7)
-
Andrei Borzenkov -
Carlos E. R. -
Dominique Leuenberger / DimStar -
Juan Erbes -
Larry Finger -
Olaf Hering -
Roger Oberholtzer