Tumbleweed Installation Freezes at 77%

As prominently noted at the download page: the live medias should not be used for installation or upgrade (for several reasons…).

If you have a wired connection you can use the LiveCD, installing with the liveCD is the same as the Network installation

A live media is not the same as the network installer. If this would be the case, one of them wouldn’t exist.

Better trust the openSUSE devs which prominently wrote, not to use the live media as installation or update source.

The LiveCD is used to try the DE without installing it by working on the Ramdisk. With the livecd you can navigate and do a lot of things. In the installation it behaves like a Net Install by downloading the software from the network. The network installation starts directly with the installation and you can’t do anything else. In the end the LiveCD is one more possibility, not one less, and you can try it since you can’t with the recommended DVD.

In Torrents you can find older versions http://tracker.opensuse.org:6969/stat

Thanks for responding.

I downloaded the DVD iso [openSUSE-Tumbleweed-DVD-x86_64-Snapshot20241206-Media.iso] and wrote it onto a flash (thumb)drive with “Disk Image Writer”. When the flashdrive boots, it goes into the openSUSE installer. [I am not flashing the mother board].

Thank for replying.

I am in the [extremely] slow process of doing an install from a live TW KDE boot to have the laptop internet connection live during the install. Will let you know.

Thanks @enziosavio.

This is what I chose to try since the DVD iso was going no where toward solving the immediate problem of getting things up and running. I will let you know.

Thanks for the input @hui

I see your point, but I am stuck trying to get the laptop up and running as it is 1/2 of my master-to-master replica for the mariadb databases I working on to help Indigenous people. I have also tried a year-old DVD iso and had the same problem before I chose to try the Live boot route.

I note that I can ensure internet access with the live boot and the installer has a sub asking we if I’ll choose to get up-to-date packages from the internet during the install. This was not an option with the DVD iso.

I will let you know what happens.

Thanks for sharing your experience. It seems though that this is not a secureboot issue and broadcom is not the problem. But I do feel the problem eminates from a lack of internet connection during installation. I will try a live boot and post what happens. Seems though, that the live boot will take a number of hours to inch its way through package installation.

Thanks

I feel lost right now with everything happening in the above posts about richard-caid’s installation problem. richard-caid could you please give the more hardware information about the laptop in question? Model number, information shown in BIOS about the machine?

When the installation freezes at 77% are there lights flashing which lights on the machine are flashing?

Could this a sort of kernel panic situation by chance?

So, my attempt at using a live boot to install failed at 77% installed as did my attempts to install from a DVD iso. When it freezes [or should I say hangs}, the cursor is a watch icon that I can move around. However, whether I wait for 4 hours or attempt to abort, nothings happens and I need to hold the power button down for a hard shutdown.

As for computer information:

  • Asus Vivobook 15 Model F512J, 20GB RAM, 1TB SSD, 2TB HDD
  • Screen shots of the bios are attached.

What other information can I give you when I cannot access the computer further than the bios?

Richard




I’ve got an idea:
/boot is inside an encrypted filesystem, from my side of view this won’t work.
For the kernel you should leave a small not encrypted partition.
After the kernel is loaded encryption should work well.
There is no EFI Partition configured.
Silly that the installer allows this…
Because of such things i let the installer configure my bootdrive himself and add my data drives then manualy.
I’m not sure if EFI is enough for encryption today, at least some time ago /boot must not be encrypted.

Greetings from germany.

Thanks for responding @Simonowski

I have been trying to approach my installation problem from the point of view of a comedy of errors.

  • There is no doubt that this started with attempting an upgrade with zypper dup that failed on a kernel. However, I disconnected the internet after updates were downloaded while they were installing. The installer froze in the terminal and C-c did not work in the command line to abort the install. Other programs were working on the computer and responding.
  • I then downloaded a DVD iso and attempted to install off-line . I used the same drive configuration with no changes (Btrfs was not included at this time) and there is a boot/efi on the SSD. This froze (the watch cursor could move but the install did not finish and attempting to click on abort had no effect.
  • I assumed I did something wrong and attempted a reinstall but this time used Btrfs for the Root OS system partition. A snapshot of that install was shared earlier in this stream. A boot issue from Btrfs being dropped into my root OS LVM partition could have started there. Last night I attempted to install from a 2021 DVD iso I had, the install froze while trying to install Boot Manager. (the installation shows what process it is on during installation).
  • Finally, Last night I went back to using ext4 for the operating system during the install and a DVD iso from Dec 8. but that did not work either (freezing at 77%). Here is a snapshot of that. Notice the boot/efi, on my SSD, although I do not know if the boot/efi is found during installation.

While I do not know what problems exist with the installation, I have a growing unease that various install attempts I have tried may have changed something, particularly when I have gone into bios to view functions/options. To ensure this is not a wild goose chase for people helping to solve this, I will go through some basics with the bios (which should have been set appropriately since TW has been the OS for around 3 years:

  • The last full install on the Asus Vivobook 15 was in May of 2023. Since that time, upgrades are doing infrequently through zypper dup. With those updates, there were custom issues with mariadb, emacs and vlc that required adjustments.
  • The initial installation of TW on the Vivobook 3 years was problematic with the previous OS system and the bios setup not favouring a scrub and installation of OpenSUSE (particularly seemed to block recognition of the SSD by openSUSE installer). However, those were worked through.
  • The bios is set as:
    • The SATA Mode Selection is switched to AHCI
    • hyper-threading is enabled
    • Intel Virtualization Technology is enabled
    • Intel AES-NI is enabled
    • VT-d is disabled
    • Fast boot is disabled
    • Secure boot is disabled (although I have tried installing with enabled and disabled and still fail to install).
  • After that, I am not proficient at setting up a bios and so am not certain if the boot has been altered. or what it should have in it.

I hope this gives some more background for solving this.

Thanks for the help

The Partition nvme0n1p1 is a FAT Partition mounted as /boot/efi.
You should be able to change the type from FAT to System/EFI.
The type is for BIOS, the mountpoint for the OS, BIOS looks for a partition with type EFI and ignores FAT, allthough EFI is FAT.
I still don’t understand for what reason root should be encrypted, there should not be any personal data.
I never used LVM, but for what reason someone should encrypt the container drive and the device inside too. PV of System is encrypted and Fast/Root too.
I would create an EFI an root partition without lvm and encryption. What you do with every other partition is on your side, allthough i tend to hold things simple and won’t use lvm.
lvm is usefull under certain circumstandes, but for me at homeuse there ist no plus.

I would prefer secureboot to be activated.
VT-d is the Intel naming for virtualization, and should be active, but under normal use conditions this doesn’t matter.
I am with you at the other points.

The problem remains,

Last night, I tried an install from the Dec 8 DVD iso for which I let the installer select the instal for me. The install was successful. Assuming then, that I might be the problem, I had someone give me a hand cleaning up my partition setup as I have not used Btrfs before [I did not know that Btrfs cannot be placed in an LVM.] He tried 2 attempts to get things installed, each one failing with a different error (one error was with network manager at 84% and another was with bootloader at 92%). He did not take a photo of those errors.

I used his build to run another attempt this morning and photoed the drive build and the error from the DVD iso installer at 77%.


Does anyone have ideas with this info??
Thanks Richard

Hi richard-caid, this is a good starting point > Recovering YaST logs after a failed installation attempt | Support | SUSE

Section > USB drive log recovery has helped me on one occasion.

-Thanks

By the way I do not believe this is correct information.

lsblk -fs
NAME                                      FSTYPE      FSVER    LABEL     UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda1                                                                                                                           
└─sda                                                                                                                          
system-root                               btrfs                          605560ad-fe93-4d09-8760-df0725b43ee1    652.7G    28% /var
│                                                                                                                              /usr/local
│                                                                                                                              /srv
│                                                                                                                              /root
│                                                                                                                              /opt
│                                                                                                                              /home
│                                                                                                                              /boot/grub2/x86_64-efi
│                                                                                                                              /boot/grub2/i386-pc
│                                                                                                                              /.snapshots
│                                                                                                                              /
└─Lenovo_M57p-openSUSE_Tumbleweed         LVM2_member LVM2 001           1yV15y-4YP2-Nekm-EWX2-eiId-uhEi-zxTcvc                
  └─sda2                                  crypto_LUKS 1                  d095bece-13e0-47ca-b2a9-f6119d3989fc                  
    └─sda                                                                                                                      
system-swap                               swap        1                  e736498b-60e5-4f99-99c2-8a6850a78ca9                  [SWAP]
└─Lenovo_M57p-openSUSE_Tumbleweed         LVM2_member LVM2 001           1yV15y-4YP2-Nekm-EWX2-eiId-uhEi-zxTcvc                
  └─sda2                                  crypto_LUKS 1                  d095bece-13e0-47ca-b2a9-f6119d3989fc                  
    └─sda