On Sat, Apr 14, 2018 at 02:53:40PM -0400, Patrick Shanahan wrote:

* André Verwijs [04-14-18 14:21]:

...

The new GRUB2 boot-loader with Leap 15 an tumbleweed doesn't work for me anymore, so i guess I'll have to look for a new non-suse linux repo...

Leap and tumbleweed itself work without a hitch, only bootloader does not work... Back to the *old* one or add it as a second option....

weird no other user have this issue....

why would you look for a new non-suse linux repo when you admittedly have something wrong with *your* installation, ie: not onesuse related?

How can you be so sure about that? Just two days ago, my bsc#891678 was closed as WONTFIX because 13.1 is no longer supported - but I had exactly the same problem with 42.3 and I'm pretty sure it will be the same once I try again with 15.0 (or Tumbleweed).

you will have the same problems with *any* distro if your bork your system in the same manner.

Yeah, it's easy to call any slightly unusual disk setup "borked". On the other hand, I'm aware that my problem is generic problem of grub2 and I don't think changing the distribution would help. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Patrick Shanahan [04-14-18 21:49]:

* Michal Kubecek [04-14-18 20:52]:

...

On Sat, Apr 14, 2018 at 02:53:40PM -0400, Patrick Shanahan wrote:

...

* André Verwijs [04-14-18 14:21]:

...

The new GRUB2 boot-loader with Leap 15 an tumbleweed doesn't work for me anymore, so i guess I'll have to look for a new non-suse linux repo...

Leap and tumbleweed itself work without a hitch, only bootloader does not work... Back to the *old* one or add it as a second option....

weird no other user have this issue....

why would you look for a new non-suse linux repo when you admittedly have something wrong with *your* installation, ie: not onesuse related?

How can you be so sure about that? Just two days ago, my bsc#891678 was closed as WONTFIX because 13.1 is no longer supported - but I had exactly the same problem with 42.3 and I'm pretty sure it will be the same once I try again with 15.0 (or Tumbleweed).

so you reopened the bug and added 42.3 as having the same problem? and 15.0 if it does also?

...

...

you will have the same problems with *any* distro if your bork your system in the same manner.

Yeah, it's easy to call any slightly unusual disk setup "borked". On the other hand, I'm aware that my problem is generic problem of grub2 and I don't think changing the distribution would help.

and fwiw, the OP said nothing about a "slightly unusual disk setup", just that it worked previously and not now. and his conversation blamed the opensuse distro. -- (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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Sat, Apr 14, 2018 at 09:47:41PM -0400, Patrick Shanahan wrote:

* Michal Kubecek [04-14-18 20:52]:

...

How can you be so sure about that? Just two days ago, my bsc#891678 was closed as WONTFIX because 13.1 is no longer supported - but I had exactly the same problem with 42.3 and I'm pretty sure it will be the same once I try again with 15.0 (or Tumbleweed).

so you reopened the bug and added 42.3 as having the same problem? and 15.0 if it does also?

Not yet, first I'm going to make sure grub2 in 15.0 doesn't handle this setup (which was created with YaST partitioner and YaST bootloader module didn't say a word about it being wrong, neither for LILO nor for old grub) either. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 04/14/2018 12:14 PM, Knurpht @ openSUSE wrote:

Op zaterdag 14 april 2018 20:18:43 CEST schreef André Verwijs:

...

The new GRUB2 boot-loader with Leap 15 an tumbleweed doesn't work for me anymore, so i guess I'll have to look for a new non-suse linux repo...

Leap and tumbleweed itself work without a hitch, only bootloader does not work... Back to the *old* one or add it as a second option....

weird no other user have this issue....

Sorry, but almost every post of yours is like this. No information, none other than 'does not work'. Anything anybody could say on this would be a wild guess. My 2 cents

On 04/14/2018 01:37 PM, Wayne Patton wrote:>> I installed Tumbleweed snapshot 20180410 yesterday. It worked just fine

...

on my system with EFI and GPT partitions.

Unless you provide more info about what's happening it's going to be hard for anyone to help you, therfore your post seems more complaining than anything.

... doesn't work for me anymore ... What in the world does that mean? In English, that phrase often means "it doesn't turn me on anymore" or "I don't get a thrill out of it, anymore." Is that what you mean? As Knurpht and Wayne Patton point out, above, your complaint is meaningless as provided. -- -Gerry Makaro openSUSE Member openSUSE Forum Moderator openSUSE Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 04/15/2018 12:36 AM, Per Jessen wrote:

Come on, it's not that difficult. It means "has ceased to work for me".

Oh, Come On, yourself! I have an Acer laptop downstairs with openSUSE installed on it. It has ceased to work for me. Must be openSUSE's fault. How do I fix it, or should I file a bug report? -- -Gerry Makaro openSUSE Member openSUSE Forum Moderator openSUSE Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

with GPT partition(s)and leap 15/TW Grub2 is NOT loading, for some reason the "boot code" (MBR) is not written so will not boot.. more info here: https://en.wikipedia.org/wiki/GUID_Partition_Table I'm working on leap 15/TW installation logs (latest build) and i will put them online for sharing.... André Op 16-4-2018 om 15:34 schreef Carlos E. R.:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Content-ID:

On Sunday, 2018-04-15 at 13:03 -0700, Fraser_Bell wrote:

...

On 04/15/2018 12:36 AM, Per Jessen wrote:

...

 Come on, it's not that difficult.  It means "has ceased to work for me".

Oh, Come On, yourself!

I have an Acer laptop downstairs with openSUSE installed on it.

It has ceased to work for me.

Must be openSUSE's fault.

How do I fix it, or should I file a bug report?

Per is only commenting that the phrase "doesn't work for me anymore" has a clear meaning. It does not mean, as you said, "it doesn't turn me on anymore" or "I don't get a thrill out of it, anymore."

Per did not say that the OP is clear enough to know what the problem is.

- -- Cheers,        Carlos E. R.        (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2

iEYEARECAAYFAlrUpkwACgkQtTMYHG2NR9UamACfX+QeJpmECFrvOXixeZxpaQ+d cmoAoJRCh7b51DfN5ZokXPFtxL80bGY+ =roDv -----END PGP SIGNATURE-----

-- ______________________________________________________________________________________ My Twitter Page: twitter.com OpenSimFan http://twitter.com/OpenSimFan My Instagram page: instagram.com dutchglory http://instagram.com/dutchglory My Facebook page: facebook.com André Verwijs http://www.facebook.com/andre.verwijs My Google+ page: André Verwijs - Google+ https://plus.google.com/111310545842863442992 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Fraser_Bell wrote:

On 04/15/2018 12:36 AM, Per Jessen wrote:

...

Come on, it's not that difficult. It means "has ceased to work for me".

Oh, Come On, yourself!

Please behave. -- Per Jessen, Zürich (12.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Knurpht @ openSUSE wrote:

Op zondag 15 april 2018 09:36:41 CEST schreef Per Jessen:

...

Fraser_Bell wrote:

...

On 04/14/2018 01:37 PM, Wayne Patton wrote:>> I installed Tumbleweed snapshot 20180410 yesterday. It worked just fine

...

...

on my system with EFI and GPT partitions.

Unless you provide more info about what's happening it's going to be hard for anyone to help you, therfore your post seems more complaining than anything.

... doesn't work for me anymore ...

What in the world does that mean? In English, that phrase often means "it doesn't turn me on anymore" or "I don't get a thrill out of it, anymore."

Come on, it's not that difficult. It means "has ceased to work for me".

Per, this is not what it's about. AFAICS Fraser_Bell's point also is that the OP is meaningless, due to lacking any kind of real info.

You don't say ... We can all see that, no need to repeat it. AFAICT, Fraser was (needlessly) having a go at the English used, which is what I responded to. How about we all start behaving like adults? -- Per Jessen, Zürich (12.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2018-04-16 21:29, Fraser_Bell wrote:

On 04/16/2018 12:12 PM, Per Jessen wrote:

...

How about we all start behaving like adults?

Good idea, Per.

Perhaps you can start by setting the example? ;-)

It is you who has to set the example, IMHO. But you started the absurdities. This is not something that I expected from a candidate to the board. -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 15.0, at Minas-Anor) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Not sure if this post is off-topic or not, but: OPEN APOLOGY TO PER JESSEN: Per, I am sorry for my earlier reply. Just because you fired the first shot, it is not an excuse for me to fire back. I do respect you and all the work you do for openSUSE. -- -Gerry Makaro openSUSE Member openSUSE Forum Moderator openSUSE Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Tue, 17 Apr 2018 12:20:59 -0500 Neil Rickert wrote:

For my tests with GPT partitioning and a bios_boot partition, I put the bios_boot partition at sectors 34-2047. That way it uses space otherwise wasted. The installer does not like that, and wants to create a larger bios_boot partition. But I persisted with that, and it worked just fine. It works fine that way with "btrfs" file system. So if the objection to a bios_boot partition is the disk space wasted, you can put that partition in sectors 34-2047 so that no useful disk space is actually wasted.

That's interesting and worth knowing. Thanks! I guess it only needs the first 512 bytes for a boot sector, so a 2MB partition is plenty. - -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEeNZxWlZYyNg7I0pvkm4MJhv0VBYFAlrWMG4ACgkQkm4MJhv0 VBYyShAAkWVxOLmmncQ8jeuKmzEtfgQzoeYf1HMdM4CNYDFWUSiEFVhxYNUFs11a 9RST5ECJztDHRHsSnM+dOl9lhpBRQOMoIZRzV5QRbrruzb0cG2igEvJn869PhU+M x+lGeYcVsWyyLiurLEvLfHK9SGrFB21EARqAA3H4qCfd+tpIUmpVjkxx2gWP8Hc2 axk2EyCD59pohYqeH51t5HFtTCiHQc+amYKzwohxCh5QNYKEx/lSGuESDF30kaWa ky9vgHMw48Svxte0nOBWJPwIR4PjIq5bZn/U+QtiSyexG5vrBMpYnZUo0jK+LXXp 7T8gZCGUmTYEAHWhH9RZwzcf7cV36Eo5kNLQH9fleDUvi1IA0X2hw3/hUX/pSDTl igB0rui2uR4QUqILkHfLyxSifBI01rd4AdFQzYmFcU0+n/ux1Tspg2gDv21KO8IQ KsAN4qKTyM5mjWdLdbQlLWkDZ5qVFqvhzi/5fwmG6etTsI+B82IpNXpgao9DyMIC YYJ3qHy4r+zTe1232G9kZVv5WKrdAgiifu1cGVnPqHmXQ8t/JnKWqYnisLlh35Ts 17EMcIxHNU8tNn2LZq2ch2FoHLWy/00qiYMbRrx6cucWrDF/2xFB4FaMIIJpdUOW HcWevcwkdq9aU4fy+1wSV6c/8v3HPu/sXmXus6NG3mCb6NktpHc= =FEtm -----END PGP SIGNATURE-----

17.04.2018 21:40, Neil Rickert пишет:

On 04/17/2018 12:35 PM, Liam Proven wrote:

...

I guess it only needs the first 512 bytes for a boot sector, so a 2MB partition is plenty.

I think it needs more that 512 bytes. The bulk of the grub code is in "/boot/grub2/i386-pc/core.img". It needs enough to be able to locate that code.

Wrong. core.img is exactly *the* code that locates /boot/grub2 which contains bulk of grub2. It is effectively copy of what is written into bios_boot or other location where you chose to install grub2. 512 bytes sector contains code that reads core.img using absolute disk location(s).

And "btrfs" makes that more complex, because there can be multiple versions of "core.img" in different snapshots.

No. /boot/grub2/i386-pc is subvolume and so exempt from (root) snapshots. There is always only one bootloader which is overwritten on update.

On 04/17/2018 05:04 PM, André Verwijs wrote:

question: does a PC BIOS/disk controller has to support GPT partitions?

That should not matter in most cases. The disk controller only needs to be able to access the disk. It should not care about content. The BIOS does look for an MBR. The GPT format begins with a "protective MBR" which should satisfy the BIOS. I have used a GPT partitioned disk in an older computer. If you don't like GPT partitioning, then use the expert partitioner for Leap 15.0 (or for Tumbleweed). Click on "/dev/sda" in the left column (or whatever disk you are using). It has to be the full disk, not a partition. Then there should be an "Expert" button near bottom right of the screen. Click that and there is an option to create a new partition table. And you should be able to select either GPT or MS-DOS. Use MS-DOS for older style partitioning. Note that doing this will erase the disk (with a warning). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Liam Proven wrote:

The legacy BIOS does not contain support for GPT*, but GPT contains an emulated MBR so that a legacy BIOS should be able to read a GPT disk and possibly even boot from it if you're lucky. :-)

I tried this only just the other week - no luck here. Legacy BIOS with 2 x 3Tb harddrives. I had to let it boot over PXE. -- Per Jessen, Zürich (18.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

17.04.2018 20:35, Liam Proven пишет:

On Tue, 17 Apr 2018 12:20:59 -0500 Neil Rickert wrote:

...

For my tests with GPT partitioning and a bios_boot partition, I put the bios_boot partition at sectors 34-2047. That way it uses space otherwise wasted. The installer does not like that, and wants to create a larger bios_boot partition. But I persisted with that, and it worked just fine. It works fine that way with "btrfs" file system. So if the objection to a bios_boot partition is the disk space wasted, you can put that partition in sectors 34-2047 so that no useful disk space is actually wasted.

That's interesting and worth knowing. Thanks!

I guess it only needs the first 512 bytes for a boot sector, so a 2MB partition is plenty.

What "it" do you mean here? bios_boot partition contains grub2 core.img which (for btrfs on BIOS) is about 40K. Still fits into 2M space but no more into legacy 63 post-MBR sectors.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/17/2018 01:35 PM, Andrei Borzenkov wrote:

Should work with Syslinux gptmbr and grub2 installed on partition; whether YaST is prepared to setup it I do not know.

Thanks. I wondered about that case. At one stage, the installer didn't support it (maybe that was opensuse 13.2), even though the "btrfs" file system reserves space for this use. So I tried it. And it worked without a problem. Using expert partitioner, with GPT: No bios_boot partition. Just swap and "/" as the only two partitions, with "btrfs" for "/". The installer then set it to boot from the partition containing "/boot" (i.e. the root partition), and set the active flag for this partition (legacy_boot flag), and install generic boot code in the partition. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJa1nH3AAoJEGSXLIzRJwiFZ8kIAJGXjVdcvxP5fAECt8ibT5Wl KBd0JcAYG7K2dDeXP8/pJElRotpMy6mjDtWV4puWKajqfoSHHB0mt/S4lgmoUV2l xu2dfN+4c4KBA1VG1NJlrWZOm6/nJDp7sNtJkwhebvXVdnZ0D/qDBFo/l2v5aXNk 0MDiXPusFB7ELcw2lxMfoSe6qEtm7JhTfEMr4Kr8cp3pNM6K5jvfL4DTK6cl6S4Z ZkyuOLz29xuuF6B3+V5cD3iiDPgZJZkf1r7UGVA0MBMkMPOADB7EVncpG7X+gZ4Q gI7okLtPOlWoAbQ/JqoorPslMBvI42MzUSz/eZMT7IA/FXXN7LUH78OUpM8nEyc= =4h9c -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org