Tumbleweed Installer 08/05/2021 Hangs

Hello opensusers,

I am attempting to install the latest version of Tumbleweed on older hardware. The Live version boots fine from USB. When loading it it hangs on:

zram0: detected capacity change from 0 to #######

In place of the digits is a number.

I cannot even reach the installer.

I know it is not the installation media because it loads fine on another laptop.

How can I troubleshoot this?

Hello again everyone,

I was able to test-install via the Live USB: Tumbleweed KDE 20210805.

I will try the full installer later down the line.

I’m having a very strange problem regarding my set-up.

I’m either trying to test-upgrade from 15.2 to 15.3 or install KDE Tumbleweed to see if it plays nice with my hardware. The Tumbleweed I installed plays nice and actually better/faster than 15.2.

I am seriously considering moving to Tumbleweed because of the short EOL time-frames of Leap.

My question is why would OS KDE 15.3 Live/install Plasma not work on my system (other than through nomodeset) but KDE Tumbleweed does? It seems to be a bad combination of Plasma/KDE/kernel versions.

OS Gnome 15.3 Live works (as does the install).
OS XFCE 15.3 Live works.

OS KDE 15.3 hangs when loading Plasmashell/KDE/X. Hitting CTRL-ALT DOUBLE-BACK-SPACE drops the session back to an unresponsive login panel.

My graphics-card is NVIDIA G98M [GeForce G 105M]. The hardware is old hardware and I plan on upgrading in the future. However, it is not immediately feasible due to time and money.

I really don’t want to waste time endlessly troubleshooting, I have a version of Tumbleweed that works. But, some guidance on specific reasons why this is happening would be insightful.

Thanks for reading.

12 year old chip It is possible that it is no linger supported. M indicate a mobile setup. Does the CPU have a built in GPU?? If so try switching to that GPU in the BIOS I think this is pre Optimus machine???

Also with that age it may be short on memory

I have to think this must be a quirk of the Plasma live media. IME, old NVidia GPUs are well supported by the default Modesetting DIX driver, e.g. this one similar to yours:

# inxi -SGxyz
  Kernel: 5.3.18-59.16-default x86_64 bits: 64 compiler: gcc v: 7.5.0
  Desktop: Trinity R14.0.10 Distro: openSUSE **Leap 15.3**
  Device-1: **NVIDIA G98** [GeForce 8400 GS Rev. 2] vendor: PNY driver: nouveau
  v: kernel bus-ID: 0b:00.0
  Display: x11 server: **X.Org** 1.20.3 **driver: loaded: modesetting**
  unloaded: fbdev,vesa resolution: 1920x1200~60Hz
  OpenGL: renderer: NV98 v: 3.3 Mesa 20.2.4 direct render: Yes

Installation of 15.3 should be fine without need for nomodset on the installed system, though its possible it might be needed for the installer to work properly.

Thanks everyone for responding.
The computer is a laptop.

The issue centers around running OS 15.3 KDE Live & OS KDE 15.3 installed (on a old testing drive) & my graphics card.

On my 15.2 long working install (using the nouveau driver), I have not updated to KDE Plasma 5.18.6 which is the offending software (also in 15.3) methinks. I can only guess it’s a combination somewhere having to do with my graphics card and those versions of kde/plasma/qt/kernel.

I know how to peruse the logs but am unsure what I should specifically look for… Dropping to a tty and logging in and forcing the machine to shutdown/reboot causes SUSE to have to run a 1:30 job forcing the other session to close.

The most recent version of Tumbleweed plays very nicely with my old hardware. I don’t like all the EOL stuff so TW seems a good way forward.

OS 15.3 Gnome works (with Mesa 3D hardware acceleration, without it the computer goes a snail’s pace).
OS 15.3 XFCE Live works.

Sometimes the problem with Plasma is obvious or clued in ~/.xession-errors, or with the dm in /var/log/*dm.errors. Since Gnome works OK, try comparing the Xorg.0.log generated using it to the Xorg.0.log generated trying to use Plasma. Sometimes Xorg.0.log is found in ~/.local/share/xorg/, while its traditional location is /var/log/. Outright failures can be found in dmesg or journal by grepping, e.g.:

sudo journalctl -b | grep aile