Help needed with a system recovery

Seasons Greeting to all looking for some help as my main PC decided to give up over Xmas, I think the motherboard died or something. Having tried most of the likely options & being unable to get into bios or have any keyboard, screen or mouse I was pretty stuck & gave up with it in the end.

Any way to get around this to try and avoid rebuilding all my settings & apps etc. I resorted to swapping out the SSD I used to run Opensuse Tumbleweed on a AMD based system with an Nvidia Graphics Card & plugged it into a little basic box I have that it Intel based with integrated graphics - so as Monty Python would have said now for something completely different.

Remarkably after a bit of playing around in the BIOS of that box I was able to set the old SSD as the first boot & remarkably as a belated Christmas present it actually booted into my old system as was & I am typing from it as we speak.

So the challenge is now to get it to recognise the new hardware so it can pick up the new graphics arrangement in the main as I’m stuck with a sub optimal 30hz at the moment. Please could I get any advice on scanning the system hardware and getting recommend software & drivers etc, for the new Intel based System? What do I need to show anyone who is kind enough to give some type to help?

Many thanks in advance & a Happy New Year.

System Details Report


Report details

  • Date generated: 2025-12-27 11:43:20

Hardware Information:

  • Hardware Model: AZW Green G3
  • Memory: 8.0 GiB
  • Processor: Intel® Celeron® N5095A Ă— 4
  • Graphics: Intel® UHD Graphics (JSL)
  • Disk Capacity: 1.3 TB

Software Information:

  • Firmware Version: JTKT001
  • OS Name: openSUSE Tumbleweed
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 49
  • Windowing System: Wayland
  • Kernel Version: Linux 6.18.2-1-default

If you were using proprietary NVidia drivers on the old, look in /etc/X11/ and /etc/X11/xorg.conf.d/ for *.conf files put there by the NVidia drivers. If found and removed, possibly nothing more will be needed except possibly to install Intel firmware kernel-firmware-intel and/or kernel-firmware-i915 and/or libdrm_intel1. Otherwise uninstalling the NVidia drivers may also be required. I have installed also:

intel-media-driver 
intel-vaapi-driver
libdrm_intel1
libvulkan_intel
ucode-intel
intel-gpu-tools
intel-hybrid-driver
intel-opencl 

Which are technically needed as a minimum I don’t know. Initrd(s) may also need regeneration:

# lsinitrd /boot/initrd | grep intel | wc -l
26
#

All the above is from Leap 15.6, but TW is similar. I’ve often swapped disks into other systems to work with little to no effort, but I’ve also never had NVidia proprietary drivers installed.

Thank you for taking the time out & sharing your intel details. I installed those & YAST also suggested some others see screenshot attached of the list. For some reason on the Native setting of my LG Widescreen 3840 x 2160 on seems to go up to 30hz for some reasons. Other options like 3440 x1440 offers 49.99hz while 2560 x 1080 offers 60hz.

Guess there maybe some kind of trade off going on, although I may have been able to do that before perhaps?

Haven’t tried the initrd regeneration or intraframs for that matter - not sure if I need to or if there are any other suggestions on that from?

Any thanks for now seem to be mostly up & running again - for the record here’s the screen shot of what got installed.

According to Intel, up to 4096x2160@60Hz is supported by your GPU, but note the note about max resolutions on that page. I don’t use Gnome or Wayland, so don’t know much to suggest about getting that display into 3840x2160@60Hz. Check in BIOS settup for a way to pre-allocate more memory to GPU use. If using an HDMI cable while DisplayPort output is available, try a DisplayPort cable. If you have a USB-C port, a USB-C to DisplayPort cable might also make a difference. 3840x2160@60Hz with HDMI requires a top quality cable, so if limited to HDMI, a better cable might help. The I/O from running command inxi -GSaz copied and pasted here using preformatted text tagging (</> icon, not another screenshot please) may provide us some clue.

2560Ă—1080Ă—60 = 165,888 MHz
3440Ă—1440Ă—50 = 247,680 MHz
3840Ă—2160Ă—30 = 248,832 MHz
so apparently you hit the ceiling of your system’s circuitry and a better cable may or may not help. If Gnome Settings doesn’t offer more, maybe that’s it.

@jjis you don’t want the intel-hybrid-driver that is for old technology you do want the intel-media-driver installed.

30Hz is a hardware/cable issue… This LG is a television screen, correct?

Edit: is “HDMI ULTRA HD Deep Color setting set to ON”

Hi guys, thank you so much for taking the time to reply to my post - the Opensuse community really is the best & why I am so keen to hang onto my set up. That’s especially so here as you have correctly identified that is a cable / hardware capability issue rather than software as such. I also had a Chat with my imaginary friend GPT & although it is prone to making stuff up it also seemed to confirm that Intel Jasper Lake + HDMI + HDR = bandwidth limitations.

As requested I post the system details at the end, although I’m not sure why it lists 4 monitors when I have just the 2? Looking at that I’m aware that I still may need to do some tidying up as there is some Nvidia stuff still hanging around. Initially tried disabling the Nvidia Repo but on doing a DUP post that it switch me over to some Opensuse one when it complained that nothing provided them. Guess I need to look up the instructions for removing Nvidia or can I just leave those lurking around in the background with out doing any harm?

I’ll also look up & install the suggested intel-media-driver although as concluded above assume this won’t change the cable / bandwidth / resolution issue. Would any other outputs be useful?

Thanks again to all of you for taking the time, apologies for the delay in replying - time zones & being away from my PC etc. Have a great New Year celebration everyone.

inxi -GSaz 
System:
  Kernel: 6.18.2-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.18.2-1-default
    root=/dev/mapper/system-root fbdev=1 nvidia_drm.modeset=1 quiet splash
    mem_sleep_default=deep resume=UUID=f3862175-5313-44f6-850a-01c0fa3a188e
  Desktop: GNOME v: 49.2 tk: GTK v: 3.24.51 wm: gnome-shell
    tools: gsd-screensaver-proxy avail: xscreensaver dm: GDM v: 49.2
    Distro: openSUSE Tumbleweed 20251225
Graphics:
  Device-1: Intel JasperLake [UHD Graphics] driver: i915 v: kernel
    arch: Gen-11 process: Intel 10nm built: 2019-21 ports:
    active: HDMI-A-1,HDMI-A-3 empty: DP-1,HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:4e55 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.8
    compositor: gnome-shell driver: X: loaded: nvidia unloaded: modesetting,vesa
    alternate: fbdev,nouveau,nv gpu: i915 display-ID: 0
  Monitor-1: HDMI-1 model: GSM LG HDR WQHD res: mode: 3440x1440 hz: 50
    scale: 100% (1) dpi: 109 size: 800x340mm (31.5x13.39") diag: 869mm (34.22")
    modes: N/A
  Monitor-2: HDMI-3 model: HKC 27E6CA res: mode: 1920x1080 hz: 60
    scale: 100% (1) dpi: 81 size: 600x330mm (23.62x12.99") diag: 685mm (26.96")
    modes: N/A
  Monitor-3: HDMI-A-1 model: LG (GoldStar) HDR WQHD serial: <filter>
    built: 2023 res: 3440x1440 dpi: 109 gamma: 1.2 size: 800x335mm (31.5x13.19")
    diag: 867mm (34.1") modes: max: 3840x2160 min: 640x480
  Monitor-4: HDMI-A-3 model: 27E6CA serial: <filter> built: 2024
    res: 1920x1080 dpi: 81 gamma: 1.2 size: 597x336mm (23.5x13.23")
    diag: 685mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.3.1 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel UHD Graphics (JSL)
    device-ID: 8086:4e55 memory: 7.36 GiB unified: yes display-ID: :0.0
  API: Vulkan v: 1.4.335 layers: 3 device: 0 type: integrated-gpu name: Intel
    UHD Graphics (JSL) driver: mesa intel v: 25.3.1 device-ID: 8086:4e55
    surfaces: N/A device: 1 type: cpu name: llvmpipe (LLVM 21.1.7 128 bits)
    driver: mesa llvmpipe v: 25.3.1 (LLVM 21.1.7) device-ID: 10005:0000
    surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo gpu: gputop,
    intel_gpu_top, lsgpu, nvidia-settings wl: wayland-info,wdisplays
    x11: xprop,xrandr

my first thought is maybe the power supply died. Do you have a multi-meter that you can check it with?

@jjis Two things, have you checked the system specifications, AFAIK HDMI-2.0 gpu capabilities and HDMI-2.0 specification cables are required for 4K?

There are also some mutter experimental tweaks you could try via dconf-editor and search for mutter, then in the experimental section, enable variable-refresh-rate and xwayland-native-scaling maybe even scale-monitor-framebuffer and likewise kms-modifiers. Reboot and test.

Thanks for taking the time to comment. Don’t have a multi meter, but had only recently replaced the PSU as the old one failed. Case Fan, CPU fans & Nvidia Fans were all powering up but I got not screen output or peripherals like mouse & keyboard from multiple usb ports & could not even get into BIOS. Tried removing & reseating RAM & power connectors etc. So my guess in the end was the motherboard had failed - SSD still works in another PC too now. Had been getting EFI 0*80000 warnings for a while prior to that too. Bit annoying as it is only 3 years old, never had a PC fail so quickly - but guess they don’t make things like they used to?

@jjis you need to remove the above and suggest adding another, so;

update-bootloader --del-option fbdev=1
update-bootloader --del-option nvidia_drm.modeset=1
update-bootloader --add-option intel_iommu=on
update-bootloader

A reboot is required, then check inxi -GSaz output.

Edit: Oh, and also remove monitors.xml file may help, rm ~/.config/monitors.xml*

1 Like

Season Greetings to you Malcom & thanks for those suggestions. I tried running those commands but I’m not sure they had any effect looking at the GSaz output. Maybe I need to edit the Grub in a text file if I can remember how to do that. Output below:

System:
  Kernel: 6.18.2-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.18.2-1-default
    root=/dev/mapper/system-root fbdev=1 nvidia_drm.modeset=1 quiet splash
    mem_sleep_default=deep resume=UUID=f3862175-5313-44f6-850a-01c0fa3a188e
    intel_iommu=on
  Desktop: GNOME v: 49.2 tk: GTK v: 3.24.51 wm: gnome-shell
    tools: gsd-screensaver-proxy avail: xscreensaver dm: GDM v: 49.2
    Distro: openSUSE Tumbleweed 20251227
Graphics:
  Device-1: Intel JasperLake [UHD Graphics] driver: i915 v: kernel
    arch: Gen-11 process: Intel 10nm built: 2019-21 ports:
    active: HDMI-A-1,HDMI-A-3 empty: DP-1,HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:4e55 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.8
    compositor: gnome-shell driver: X: loaded: nvidia unloaded: modesetting,vesa
    alternate: fbdev,nouveau,nv gpu: i915 display-ID: 0
  Monitor-1: HDMI-1 model: GSM LG HDR WQHD res: mode: 3440x1440 hz: 50
    scale: 100% (1) dpi: 109 size: 800x340mm (31.5x13.39") diag: 869mm (34.22")
    modes: N/A
  Monitor-2: HDMI-3 model: HKC 27E6CA res: mode: 1920x1080 hz: 60
    scale: 100% (1) dpi: 81 size: 600x330mm (23.62x12.99") diag: 685mm (26.96")
    modes: N/A
  Monitor-3: HDMI-A-1 model: LG (GoldStar) HDR WQHD serial: <filter>
    built: 2023 res: 3440x1440 dpi: 109 gamma: 1.2 size: 800x335mm (31.5x13.19")
    diag: 867mm (34.1") modes: max: 3840x2160 min: 640x480
  Monitor-4: HDMI-A-3 model: 27E6CA serial: <filter> built: 2024
    res: 1920x1080 dpi: 81 gamma: 1.2 size: 597x336mm (23.5x13.23")
    diag: 685mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.3.1 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel UHD Graphics (JSL)
    device-ID: 8086:4e55 memory: 7.36 GiB unified: yes display-ID: :0.0
  API: Vulkan v: 1.4.335 layers: 3 device: 0 type: integrated-gpu name: Intel
    UHD Graphics (JSL) driver: mesa intel v: 25.3.1 device-ID: 8086:4e55
    surfaces: N/A device: 1 type: cpu name: llvmpipe (LLVM 21.1.7 128 bits)
    driver: mesa llvmpipe v: 25.3.1 (LLVM 21.1.7) device-ID: 10005:0000
    surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo gpu: gputop,
    intel_gpu_top, lsgpu, nvidia-settings wl: wayland-info,wdisplays
    x11: xprop,xrandr

@jjis Then there must be something lurking somewhere related to nvidia, maybe a dracut -f --regenerate-all may clean it up.

Thanks I got that cleared out now. The main annoyance I’m facing now is that I’m unable to launch Evolution on the new set up - just crashes at launch - core dump type of thing. I did mention this on another recent thread on here where someone else had been seeing that too. Not sure if it is a general bug or related to the limited RAM / resources of the machine I’m using now?

Evolution doesn’t appear to be resource-hungry here, but may depend on setup.
You are not alone apparently: bug 1252751
I personally met something like evolution/-/issues/3152 recently on Tumbleweed.
Starting Evolution for a fresh user might show if there is something wrong with the user config or if there is a general problem; if the fresh user is ok, maybe backup and rename /home/<your username>/.cache/evolution so that e.g. /home/<username>/.cache/evolution/mail/<account ID>/folders.db are recreated.
PLEASE BACKUP everything especially if you are using POP accounts that download and store locally your messages; IMAP accounts should keep messages on the server, but better safe than sorry :wink:

Hi thanks for taking the time to reply. Good to know it may not be a resource issue. I wonder if it could be a security thing as I swapped the drive it is in to another Computer so maybe something isn’t mapped correctly perhaps or the OATH2 thing for Outlook? Not sure which version I’m on, although the TW system is pretty up to date. Can’t check it as the Gnome Software centre that launches if I try to see App details also crashes all the time just after it loads. Gnome does seem a bit ropey recently with all the upgrades.

Any way not sure how I can try it with a fresh user as I can’t even get Evolution to launch. Guess I could try uninstalling & reinstalling as my accounts are all IMAP, but not sure if that will leave old folder details in place or wipe those. Managed to get the old Thunderbird to fly in the meantime as an alternative for now.

If any one has any thoughts or ideas on this, that would be greatly appreciated. Seasons Greetings to all.

@jjis So you just swapped the storage device from the old system to the new system? I have a similar device a Beelink Mini PC (16GB of RAM) it’s Gen 12 Alder Lake currently running Leap 16.0 but did have Tumbleweed on it and also Aeon running without issues. I don’t use Evolution though, I use Claws-Mail as it covers usenet as well…

Yes that right Malcolm, I was a bit surprised it worked as it was from a AMD/Nvidia system to a lower powered Intel based system, that you have kindly helped me tidy up. My mini only has 8gb RAM so wasn’t sure if that is the issue or because of the drive being swapped over maybe?

@jjis 8GB should be fine. There could just be cruft left over, as suggested by @OrsoBruno create a test user and see what happens… As in GNOME Software etc…

Edit: Can you please post the latest output from inxi -GSaz

Add new user (Gnome Settings > System > Users > Add User , you may need to “unlock” by providing the root password) and if it fails YaST2-Users still works in Tumbleweed.
At login, choosing the Gnome Session should provide Evolution for the new user, with no configured account but it should still launch.
The same should happen for Gnome Software. There might still be something in the caches etc. trying to use Vulkan with the Nvidia GPU or the like, so rebuilding the caches or starting fresh looks as worth a shot.

1 Like