Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: Looping login to OpenSuse Leap and booting to Windows 10 not working after installation of Leap

Hybrid View

  1. #1

    Default Looping login to OpenSuse Leap and booting to Windows 10 not working after installation of Leap

    After completing the installation of pre-installed Windows 10 on my computer (CI7 3.6 GHz, 256 GB SSD, 2 TB HDD, 16 GB RAM, NVIDIA GTX 750).
    Then I installed OpenSUSE Leap 42.1 from a bootable USB stick (created with ImageUSB/PassMark Software after downloading the .iso file with direct link).
    I partitioned my discs into '/' (BtrFS format) and 'swap' on the SSD drive and put the '/home' partition (XFS) on the HDD.
    I did not ask the installer to format the EFI boot partition because I was afraid it might jeopardize my system (correct?) but simply mounted the partition as '/boot/efi' (FAT format).
    The installation seems to have worked just fine since I did not get any error message.
    When I start my system I land in the boot manager offering to boot OpenSuse 42.1, Windows, ...etc.
    if I choose to start OpenSUSE, after a short message
    Code:
    0.21...] Ignoring BGRT: invalid status 0 (expected 1)
    and
    Code:
    kwm disabled by BIOS
    I arrived to the login menu but cannot log into OpenSUSE (looping login window).
    I can login in the console modus (ctrl+alt+F2) but do not know what to do from there...
    I cannot login as root because I did not create a root administrator account during the installation (my bad...) and therefore could not try to install a new NVIDIA driver.

    And if I choose to boot Windows, I get the message:
    Code:
    /EndEntire
    filepath: /ACPI(a0341d0,0)/PCI(2,1f)/Sata(0,ffff,0)
    /HD(2,190800,82000, ea..., 2,2)/File(\EFI\Microsoft\Boot)/File(bootmgfw.efi)
    /EndEntire
    error: Not supported image.
    I identified several threads with similar issues (https://forums.opensuse.org/showthre...nd-secure-boot, https://forums.opensuse.org/showthre...k-at-KDE-login) but I cannot solve my issue and am not even sure if it is the same problem.

    I would appreciate if anybody might be willing to give me some directions here.

    Should I re-install OpenSUSE freshly, taking care to create a separate root admin?
    Should I ask the installation program to reformat the existing EFI boot partition (FAT)?
    Does anybody see some obvious flag in my issue?

    Thank you

  2. #2

    Default Re: Looping login to OpenSuse Leap and booting to Windows 10 not working after installation of Leap

    Quote Originally Posted by yanfri View Post
    After completing the installation of pre-installed Windows 10 on my computer (CI7 3.6 GHz, 256 GB SSD, 2 TB HDD, 16 GB RAM, NVIDIA GTX 750).
    Then I installed OpenSUSE Leap 42.1 from a bootable USB stick (created with ImageUSB/PassMark Software after downloading the .iso file with direct link).
    I'd use a DVD. That way you can do a proper media check.

    Quote Originally Posted by yanfri View Post
    I partitioned my discs into '/' (BtrFS format) and 'swap' on the SSD drive and put the '/home' partition (XFS) on the HDD.
    I did not ask the installer to format the EFI boot partition because I was afraid it might jeopardize my system (correct?) but simply mounted the partition as '/boot/efi' (FAT format).
    Mounting your EFI partition as /boot/efi is 100% correct.

    Quote Originally Posted by yanfri View Post
    The installation seems to have worked just fine since I did not get any error message.
    When I start my system I land in the boot manager offering to boot OpenSuse 42.1, Windows, ...etc.
    if I choose to start OpenSUSE, after a short message
    Code:
    0.21...] Ignoring BGRT: invalid status 0 (expected 1)
    I'm 50% sure that line is highly ignorable.

    Quote Originally Posted by yanfri View Post
    and
    Code:
    kwm disabled by BIOS
    I'm 95% sure that that line is highly ignorable.

    Quote Originally Posted by yanfri View Post
    I arrived to the login menu but cannot log into OpenSUSE (looping login window).
    Sounds like a DE problem. Did you install KDE or GNOME?

    Quote Originally Posted by yanfri View Post
    I can login in the console modus (ctrl+alt+F2) but do not know what to do from there...
    I cannot login as root because I did not create a root administrator account during the installation (my bad...) and therefore could not try to install a new NVIDIA driver.
    You did create a root account because it's impossible to install GNU/Linux without one. The password is (almost certainly) the same as the one for the user account you created upon installation. But do not log into a desktop session as root. If you can connect your computer by RJ45 to an ethernet port to a DHCP-configured router/gateway, you're easiest option is to do so, log into a virtual console and enter:

    Code:
    sh-4.2$ su -
    sh-4.2# ping www.opensuse.org ; just to test connection: press Ctrl-C to halt.
    sh-4.2# zypper up
    sh-4.2# reboot
    Quote Originally Posted by yanfri View Post
    And if I choose to boot Windows, I get the message:
    Code:
    /EndEntire
    filepath: /ACPI(a0341d0,0)/PCI(2,1f)/Sata(0,ffff,0)
    /HD(2,190800,82000, ea..., 2,2)/File(\EFI\Microsoft\Boot)/File(bootmgfw.efi)
    /EndEntire
    error: Not supported image.
    Did you install Windows 10 and openSUSE Leap with secure boot enabled? If so, you will suffer from the same bug I've had to struggle with today. It still hasn't been corrected in the official repos but you will see can be corrected by reinstalling GRUB2-EFI from an unofficial one (see https://forums.opensuse.org/showthre...ure-boot/page4 ).

    Quote Originally Posted by yanfri View Post
    I identified several threads with similar issues (https://forums.opensuse.org/showthre...nd-secure-boot, https://forums.opensuse.org/showthre...k-at-KDE-login) but I cannot solve my issue and am not even sure if it is the same problem.
    If you're using secure boot, then (at least part of) your problem is the same.

    Quote Originally Posted by yanfri View Post
    I would appreciate if anybody might be willing to give me some directions here.

    Should I re-install OpenSUSE freshly, taking care to create a separate root admin?
    No. There's no such thing as a GNU/Linux installation without root.

    Quote Originally Posted by yanfri View Post
    Should I ask the installation program to reformat the existing EFI boot partition (FAT)?
    Definitely not! Unless you want to risk installing Windows 10 again!

    Quote Originally Posted by yanfri View Post
    Does anybody see some obvious flag in my issue?
    One step at a time. Did you enable secure boot and which DE did you install?

  3. #3
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,643
    Blog Entries
    3

    Default Re: Looping login to OpenSuse Leap and booting to Windows 10 not working after installation of Leap

    Quote Originally Posted by yanfri View Post
    I did not ask the installer to format the EFI boot partition because I was afraid it might jeopardize my system (correct?) but simply mounted the partition as '/boot/efi' (FAT format).
    Yes, that's correct. You did fine.

    Code:
    0.21...] Ignoring BGRT: invalid status 0 (expected 1)
    This seems unimportant. I found an ubuntu forum thread that gives a little information about this.

    Code:
    kwm disabled by BIOS
    I'm betting that was actually "kvm" rather than "kwm". There is likely a BIOS setting you can change if you need to actually use kvm. Otherwise, just ignore it.

    I arrived to the login menu but cannot log into OpenSUSE (looping login window).
    I can login in the console modus (ctrl+alt+F2) but do not know what to do from there...
    I cannot login as root because I did not create a root administrator account during the installation (my bad...) and therefore could not try to install a new NVIDIA driver.
    On the login window, select "Icewm" (instead of Plasma 5 or KDE or Gnome or whatever). See if you can login there. If you can, then you can install the nvidia driver from icewm.

    And if I choose to boot Windows, I get the message:
    Code:
    /EndEntire
    filepath: /ACPI(a0341d0,0)/PCI(2,1f)/Sata(0,ffff,0)
    /HD(2,190800,82000, ea..., 2,2)/File(\EFI\Microsoft\Boot)/File(bootmgfw.efi)
    /EndEntire
    error: Not supported image.
    That's bug 954126. There should be an update to fix this real soon now. In the meantime, you could turn off secure-boot in the BIOS as a temporary workaround.

    Otherwise, you are mostly in great shape, except for the need to install nvidia drivers.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  4. #4

    Default Re: Looping login to OpenSuse Leap and booting to Windows 10 not working after installation of Leap

    Thank you both flymail and nrickert for your help! Unfortunately my system is still not running perfectly as I expected.

    I installed KDE and I am not sure about the secure boot...
    Would you recommend to disable the secure boot?

    Here is what I did:
    In the meantime I re-installed OpenSUSE, taking care to create a separate root account. I formated my '/' partition as 'Ext4' (instead of 'BtrFS' as previously/as the installer automatically put it in response to the warning about BtrFS format for rookie users).
    I chose to install the LiLo and grub packages and I do not know which one booted after the installation but now the boot menu only gives me three choices instead of four and Windows starts perfectly now
    However, I still cannot boot OpenSUSE: I tried to login into IceWM - had to enter my password twice... - and managed to do so but I could not start any application from this environment and the OpenSUSE login bar was still apparent on my desktop #1 *??*.
    So I failed to open an internet browser to download the NVIDIA driver.

    Then I logged out and logged back in in the console mode.
    As advised, I ran:
    Code:
    su -
    ping www.opensuse.org; (stopped the process with ctrl+C)
    zypper up
    reboot
    Now, I still cannot start OpenSUSE.

    Is there a way to install a driver through the console command line?
    Where do I set the secure boot? I did not see it in the BIOS.

  5. #5

    Default Re: Looping login to OpenSuse Leap and booting to Windows 10 not working after installation of Leap

    I forgot to ask: is there a real benefit to install from a DVD instead of a USB stick? Is the image on both media not identical?
    Would you advise me to install OpenSUSE Leap with a DVD?

  6. #6
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,643
    Blog Entries
    3

    Default Re: Looping login to OpenSuse Leap and booting to Windows 10 not working after installation of Leap

    Quote Originally Posted by yanfri View Post
    I forgot to ask: is there a real benefit to install from a DVD instead of a USB stick? Is the image on both media not identical?
    Would you advise me to install OpenSUSE Leap with a DVD?
    I use a USB stick. There shouldn't be any difference, except perhaps in how the BIOS or UEFI firmware boots them. It's the same image iso file.

    There's an update out today that fixes the boot problem. So disable secure-boot until your system is fully updated.

    If you have a network connection, I think you are better off adding the nvidia driver from the nvidia community repo.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  7. #7

    Default Re: Looping login to OpenSuse Leap and booting to Windows 10 notworking after installation of Leap

    On 2016-01-06, yanfri <yanfri@no-mx.forums.microfocus.com> wrote:
    > Thank you both flymail and nrickert for your help! Unfortunately my
    > system is still not running perfectly as I expected.


    Keep trying. GNU/Linux is not free: you just pay with time rather than money.

    > I installed KDE and I am not sure about the secure boot...
    > Would you recommend to disable the secure boot?


    Thank you for confirming you use KDE. Whether secure boot is enabled is something you do need to know. You can find out
    in YaST->Bootloader. As suggested by nrickert, life might be easier for you if you disable secure boot.

    > Here is what I did:
    > In the meantime I re-installed OpenSUSE, taking care to create a
    > separate root account.


    As I said before every GNU/Linux install already has a root account.

    > I formated my '/' partition as 'Ext4' (instead of
    > 'BtrFS' as previously/as the installer automatically put it in response
    > to the warning about BtrFS format for rookie users).


    Whether you use BtrFS or ext4 shouldn't really make much of a difference of whether you can log into KDE.

    > I chose to install the LiLo and grub packages and I do not know which
    > one booted after the installation but now the boot menu only
    > gives me three choices instead of four and Windows starts perfectly now


    Well I suppose that's an advance. Usually, GNU/Linux installations use only one bootloader: e.g. LiLo or GRUB, but not
    both. Under YaST->Bootloader, you can see/set which boatloader is being used.

    > However, I still cannot boot OpenSUSE: I tried to login into IceWM - had
    > to enter my password twice... - and managed to do so but I could not
    > start any application from this environment and the OpenSUSE login bar
    > was still apparent on my desktop #1 *??*.


    In my experience, there should be no problem reaching openSUSE's KDE with Nvidia graphics cards with the default open
    source nouveau driver that comes preinstalled. I haven't tested this for openSUSE Leap 42.1 however. If you can't log
    into KDE/IceWM, and only command console then you can run YaST by logging into command console as root and typing `yast'
    and hitting `Enter'.

    > So I failed to open an internet browser to download the NVIDIA driver.


    In order to download the driver, you may make your life easier by installing a console internet browsert (such as links
    or lynx).

    > Then I logged out and logged back in in the console mode.
    > As advised, I ran: <SNIP> ping www.opensuse.org <SNIP> zypper up <SNIP>


    The `zypper up' command simply updates packages to the latest version and this can be useful in resolving numerous bug
    issues occuring after a fresh install. Sorry to ask a silly question, but did the ping actually confirm you were online?

    > Now, I still cannot start OpenSUSE.
    > Is there a way to install a driver through the console command line?


    Yes, but only if your internet connection is working from command console (or using much more long-winded methods using
    another computer).

    > Where do I set the secure boot? I did not see it in the BIOS.


    Yast->Bootloader should tell you.

  8. #8
    Join Date
    Sep 2012
    Posts
    5,145

    Default Re: Looping login to OpenSuse Leap and booting to Windows 10 notworking after installation of Leap

    Quote Originally Posted by flymail View Post

    > Where do I set the secure boot? I did not see it in the BIOS.


    Yast->Bootloader should tell you.
    No, it won't. It tells you whether bootloader is suitable for secure boot; it is independent of whether secure boot is actually enabled or not. Nor is it even possible to change secure boot state from within OS. Unfortunately each BIOS vendor has different GUI and OP did not even list motherboard vendor and BIOS version (then someone may have an idea) - and neither CPU speed, nor RAM size nor HDD nor video card help here.

  9. #9

    Default Re: Looping login to OpenSuse Leap and booting to Windows 10 notworking after installation of Leap

    On 2016-01-07, arvidjaar <arvidjaar@no-mx.forums.microfocus.com> wrote:
    >
    > flymail;2747249 Wrote:
    >>
    >> > Where do I set the secure boot? I did not see it in the BIOS.

    >>
    >> Yast->Bootloader should tell you.

    > No, it won't. It tells you whether bootloader is suitable for secure
    > boot; it is independent of whether secure boot is actually enabled or
    > not. Nor is it even possible to change secure boot state from within OS.


    That's terrible!... I didn't know that! What kind of implementation precludes OS knowledge of its own boot state?

    > Unfortunately each BIOS vendor has different GUI and OP did not even
    > list motherboard vendor and BIOS version (then someone may have an idea)
    > - and neither CPU speed, nor RAM size nor HDD nor video card help here.


    I guess that's very good reason to have secure boot disabled by default!

  10. #10
    Join Date
    Sep 2012
    Posts
    5,145

    Default Re: Looping login to OpenSuse Leap and booting to Windows 10 notworking after installation of Leap

    Quote Originally Posted by flymail View Post
    What kind of implementation precludes OS knowledge of its own boot state?
    You can check current state of secure boot using SecureBoot EFI variable; it is read-only as soon you leave firmware. I think current efibootmgr displays its value; you can also install efivar package that provides command to help manipulating EFI variables.

    And no, it is not OS state - it is firmware state. Strictly speaking it is of no concern to OS.

Page 1 of 2 12 LastLast

Posting Permissions

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