Page 4 of 7 FirstFirst ... 23456 ... LastLast
Results 31 to 40 of 70

Thread: How to have a custom UEFI grub menu for a multiboot system

  1. #31

    Default Re: How to have a custom UEFI grub menu for a multiboot system

    Quote Originally Posted by mrmazda View Post
    With the info provided it's hard to understand just what happened when, and the current state of things. If you can boot TW, get the script from https://github.com/arvidjaar/bootinfoscript and run it in a vtty or Konsole or XTerm, then do
    Code:
    susepaste -n Medin25 -e 40320 RESULTS.TXT
    so we can see what you have where and then suggest how to proceed. You may have to install susepaste first with zypper or yast. Also give us the exact model of your laptop so we can have an idea of its specifications. If you can install inxi with zypper or yast and provide output from
    Code:
    inxi -bGxx
    run from Konsole or an XTerm it would be even better. Alternatively, output from inxi can be redirected to a file and uploaded with susepaste just like with RESULTS.TXT.
    Maybe I wasn't really clear enough so I'll put it like this:

    Problem 1:

    1. Installation process of Tumbleweed
    2. Adding another EFI boot partition (as required) to the system even though already one exists as default (probably for windows 10)
    3. After installation openSUSE worked but Windows kept crashing and I couldn't get into it or boot it at all which I already mentioned
    4. Tried everything to fix it and thought that maybe Windows switched up some boot directories so that it couldn't find it's way to grub2. Maybe it has something to to with Legacy mode or UEFI, even though I tried all of it it kept failing.
    5. Had to reinstall openSUSE and Windows
    6. Installed Windows just fine but the system reserved of the previous one is still there so the crashed volume could still be accessed even though it can't boot
    7. I'm in a state where I want to install again Tumbleweed but don't know how to deal with the EFI boot partition which Linux requires and feel confused as a newbie for Linux systems and openSUSE

    Problem 2:

    My friend in the other hand installed it and it worked fine without needing an EFI boot partition, but he has problems with the software updates. It has to do something with the keybase that can't let the system provide the right tools to download files that need to be provided for the repositories from like multimedia and packman. He can't download basic things like vlc because it's missing it's codecs and files required for it to be installed.
    He refreshed the repositories, tried everything from the forums and sites, enabled all repositories except for the Leap 15.1 one that for some reason makes the whole update part not work at all. Strangely enough it says that everything is up to date in the console from the repositories. Maybe he is looking for the wrong thing, or those things are not that connected, but he tried everything and nothing worked.

    Thank you for the replies you gave me. Any other advice, help or solution to these problems?

  2. #32
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,743

    Default Re: How to have a custom UEFI grub menu for a multiboot system

    If an EFI boot partition exists there is no need for a second unless it is extremely small it just need to be mounted at /boot/efi

    You should NOT mix boot modes ie all OS must use EFI or MBR (legacy) booting never mix. This makes it impossible for grub to chain to the odd OS. You still should be able to boot to a EFI OS from the UEFI boot menu (BIOS) even if grub is in legacy mode

    As to problem two show the repos ( we can't look over your shoulder)

    zypper lr -d

    Also never mix repos from different OS versions ie only LEAP for Leap and only Tumbleweed for TW. Mixing will break things

  3. #33
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,690

    Default Re: How to have a custom UEFI grub menu for a multiboot system

    Quote Originally Posted by Medin25 View Post
    Any other advice, help or solution to these problems?
    Both problems belong in their own unique threads in which "everything" needs to be spelled out in detail. Neither is directly related to this thread's OP, or to each other.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  4. #34

    Unhappy Re: How to have a custom UEFI grub menu for a multiboot system

    Quote Originally Posted by gogalthorp View Post
    If an EFI boot partition exists there is no need for a second unless it is extremely small it just need to be mounted at /boot/efi

    You should NOT mix boot modes ie all OS must use EFI or MBR (legacy) booting never mix. This makes it impossible for grub to chain to the odd OS. You still should be able to boot to a EFI OS from the UEFI boot menu (BIOS) even if grub is in legacy mode

    As to problem two show the repos ( we can't look over your shoulder)

    zypper lr -d

    Also never mix repos from different OS versions ie only LEAP for Leap and only Tumbleweed for TW. Mixing will break things
    # | Alias | Name | Enabled | GPG Check | Refresh | Priority
    | Type | URI | Service
    ---+-------------------------------------+-----------------------------------------+---------+-----------+---------+---------
    -+--------+--------------------------------------------------------------------------------------+--------
    1 | Google-Chrome | Google-Chrome | Yes | (r ) Yes | No | 99
    | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 |
    2 | Packman | Packman | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://packman.jacobs-university.de/...USE_Leap_42.1/ |
    3 | dvd | dvd | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://opensuse-guide.org/repo/openSUSE_Leap_15.0/ |
    4 | http-download.opensuse.org-05f77fc4 | openSUSE.orgpenSUSE:Leap:42.3:Update | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/update/leap/42.3/oss/ |
    5 | http-download.opensuse.org-1f422a49 | multimedia:apps | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/reposit...USE_Leap_15.0/ |
    6 | http-download.opensuse.org-5e9c6fb8 | multimedia:libs | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/reposit...USE_Leap_15.0/ |
    7 | http-download.videolan.org-4d928b83 | SuSE | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.videolan.org/SuSE/Leap_42.3/ |
    8 | keybase | keybase | Yes | ( p) Yes | Yes | 99
    | rpm-md | http://prerelease.keybase.io/rpm/x86_64 |
    9 | openSUSE-Leap-15.0-1 | openSUSE-Leap-15.0-1 | No | ---- | ---- | 99
    | rpm-md | hd:///?device=/dev/disk/by-id/usb-JetFlash_Transcend_16GB_795DSIPTUNZ93RWR-0:0-part2 |
    10 | packman | packman | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://ftp.gwdg.de/pub/linux/misc/pa...USE_Leap_42.1/ |
    11 | repo-debug | openSUSE-Leap-15.0-Debug | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/debug/d...15.0/repo/oss/ |
    12 | repo-debug-non-oss | openSUSE-Leap-15.0-Debug-Non-Oss | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/debug/d.../repo/non-oss/ |
    13 | repo-debug-update | openSUSE-Leap-15.0-Update-Debug | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/debug/u...leap/15.0/oss/ |
    14 | repo-debug-update-non-oss | openSUSE-Leap-15.0-Update-Debug-Non-Oss | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/debug/u.../15.0/non-oss/ |
    15 | repo-non-oss | openSUSE-Leap-15.0-Non-Oss | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/distrib.../repo/non-oss/ |
    16 | repo-oss | openSUSE-Leap-15.0-Oss | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/distrib...15.0/repo/oss/ |
    17 | repo-source | openSUSE-Leap-15.0-Source | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/source/...15.0/repo/oss/ |
    18 | repo-source-non-oss | openSUSE-Leap-15.0-Source-Non-Oss | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/source/.../repo/non-oss/ |
    19 | repo-update | openSUSE-Leap-15.0-Update | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/update/leap/15.0/oss/ |
    20 | repo-update-non-oss | openSUSE-Leap-15.0-Update-Non-Oss | Yes | (r ) Yes | Yes | 99
    | rpm-md | http://download.opensuse.org/update/leap/15.0/non-oss/ |

  5. #35
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,845
    Blog Entries
    14

    Default Re: How to have a custom UEFI grub menu for a multiboot system

    That's what I call a mess. You have a mix of repos from various openSUSE versions, a guarantee for the issues you're seeing. My advice: a clean Leap 15 install.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  6. #36
    Join Date
    Jul 2018
    Location
    US
    Posts
    77

    Default Re: How to have a custom UEFI grub menu for a multiboot system

    When I this computer from my son, I formatted the 500GB SSD and installed Windows 10 first of course. Then I noticed it only create a /boot/efi partition that was only 128MB.

    Knowing that I would be installing several other Linux systems on here, I knew I had to have at least a 512MB /boot/efi partition. I found how I could make it 550MB.

    I've ran out of room before and found that deleting the dump files cured that problem.
    Intel Core i7-4770K, NVIDIA GeForce GTX 980 Ti, Mobo: ASUSTeK, model: Z87-K, Mem: 16GB, Sound Blaster Audigy Series, HD: Western Digital 1TB SSD, OCZ 500GB SSD and a Toshiba 2TB SATA HD

  7. #37
    Join Date
    Jul 2018
    Location
    US
    Posts
    77

    Default Re: How to have a custom UEFI grub menu for a multiboot system

    Quote Originally Posted by Medin25 View Post
    I'm new and I need a little help/advice on one thing. Since I already have an UEFI/EFI boot partition for Windows 10, I don't get it why Tumbleweed needs another one. The first time I just went with it and created two EFI partitions, but then Windows 10 crashed totally and couldn't recognize the right GPT partition in which it's EFI boot was held. I tried to convey all of it somehow to their right directories but it didn't work out at all. It pretty much killed my Windows system and my laptop, and that's why I had to reinstall everything. Now it again wants me to do the same and I don't feel safe doing it since I don't want to finish of the same. It is also important to point out that Tumbleweed and grub2 after that installation worked kind of strange compared to the last time I used it on my previous computer even though that wasn't that long ago and the main features felt buggy. Any help?
    Sorry, I'm a little late to this ballgame but, if you are willing to start from scratch, which it appears you need to do. Back up everything you want to save and start over by re-installing windows 10 first.

    Definitely watch this video about how to make the /boot/efi system partition as big as you want before you do.
    The video creates a 260MB EFI partition, which every system on your computer will use (Windows 10, Arch Linux, openSUSE and/or all the other systems you want or will ever want to install).

    You will want to make this at least 512MB or bigger. I made mine 550MB. You can see the 5 systems I have installed in my signature. You could make this 2GB and that would be fine if you have the room.

    This is probably the most important step there is during an initial install to a new or newly formatted partition. How to Resize EFI System Partition [Hackintosh]

    Doing this is easy for the guy in the video but, myself I never would have figured this out in a million years.

    BTW, I had to boot into Windows to retrieve that link.
    Intel Core i7-4770K, NVIDIA GeForce GTX 980 Ti, Mobo: ASUSTeK, model: Z87-K, Mem: 16GB, Sound Blaster Audigy Series, HD: Western Digital 1TB SSD, OCZ 500GB SSD and a Toshiba 2TB SATA HD

  8. #38
    Join Date
    Jul 2018
    Location
    US
    Posts
    77

    Default Re: How to have a custom UEFI grub menu for a multiboot system

    Then every time you install a Linux system .e.g. openSUSE Leap, just point it to the /boot/efi partition but, do not format it. Do the same with the swap partition.

    I re-installed Fedora 29 a couple of days ago and in order to get the /boot/efi and swap partition to be included I had to put a check by format this partition but, once it added it, I removed the check mark.

    I forget how it was when I installed openSUSE TW but, the idea is the same. You definitely do not ever want to format the /boot/efi partition and if you have more than one Linux system installed, you do not want to format the swap partition either.
    Intel Core i7-4770K, NVIDIA GeForce GTX 980 Ti, Mobo: ASUSTeK, model: Z87-K, Mem: 16GB, Sound Blaster Audigy Series, HD: Western Digital 1TB SSD, OCZ 500GB SSD and a Toshiba 2TB SATA HD

  9. #39
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,690

    Default Re: How to have a custom UEFI grub menu for a multiboot system

    Quote Originally Posted by Cavsfan View Post
    Back up everything you want to save and start over by re-installing windows 10 first.
    I haven't installed Windows first in nearly two decades, and that was probably a Windows-only installation. While it's perfectly reasonable to install Windows first, with proper understanding and planning, there's absolutely no compulsion to adhere to this too popular fairy tale of need. Strictly adhering to such logic, all operating systems would need reinstallation following each Windows reinstallation.

    Definitely watch this video about how to make the /boot/efi system partition as big as you want before you do.
    The video creates a 260MB EFI partition, which every system on your computer will use (Windows 10, Arch Linux, openSUSE and/or all the other systems you want or will ever want to install).
    260M is perfectly reasonable, probably the ideal recommendation for size on a virgin or freshly wiped disk.

    You will want to make this at least 512MB or bigger.
    Utter nonsense....

    I made mine 550MB. You can see the 5 systems I have installed in my signature.
    I have two UEFI systems with 6 or more installed operating systems. One has 6, with ESP partition using a mere 19M, which would be only 19% of a 100M partition. The other has 9, using 22M on ESP, which is probably about twice as much as needed due to in place backups/archives.

    There do exist circumstances that dictate a minimum ESP partition size of 260M. That is in the AFAIK as yet unsupported configuration of ESP partition living on a device with 4k logical sector size as well as physical sector size. Anyone else would be very hard pressed to install, much less maintain, enough operating systems to exhaust a 100M ESP partition's freespace.

    Those installers that claim that 100M or 128M is inadequate for ESP are quite simply broken.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  10. #40
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    977

    Default Drive Partition Rules (Windows Boot)

    Windows partition requirements:

    • System partition
      The device must contain a system partition. On GPT drives, this is known as the EFI System Partition, or the ESP. This partition is usually stored on the primary hard drive. The device boots to this partition.
      The minimum size of this partition is 100 MB, and must be formatted using the FAT32 file format.
      This partition is managed by the operating system, and should not contain any other files, including Windows RE tools.
      Note For Advanced Format 4K Native drives (4-KB-per-sector) drives, the minimum size is 260 MB, due to a limitation of the FAT32 file format. The minimum partition size of FAT32 drives is calculated as sector size (4KB) x 65527 = 256 MB.
      Advanced Format 512e drives are not affected by this limitation, because their emulated sector size is 512 bytes. 512 bytes x 65527 = 32 MB, which is less than the 100 MB minimum size for this partition.

      https://docs.microsoft.com/en-us/win...ive-partitions
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

Page 4 of 7 FirstFirst ... 23456 ... LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •