Ah . . . well, I just based that number upon a fast look at what zypper was installing . . . knowing that it was the new 6.14 xxx kernel . . . .
So, I guess that puts me back on the standard TW install . . . . Topic has been the same topic for the entire thread . . . display does not revive from suspend, or intermittently does and doesn’t.
No hard feelings, but 181 lengthy posts in a lengthy thread are not going to bring much, we you see now. No one is going to read all that, so it is too hard to get any reliable picture of your system(s). In your case (AFAICS) I would even reintall TW
None taken, it seems like it’s complicated to get suspend function. But, miracles can happen . . . Deus Ex Machina . . . God could reach down into my machine and the problem would be gone . . . .
Right now I’m waiting to hear from the graphics card guy if there is a card that will move me into playing with the latest kernels and retro-act with my older OSX versions. It’s taken awhile for my other machines to catch up to TW’s kernels to compare the difference between having a graphics card or just using mobo graphics . . . .
But, I keep hoping as in the past, Takashi would suggest moving to the newest backport kernels to get out of this problem. This time it seems like locking in the old kernel is the answer. I did a fresh install of TW in another partition and that has the same issue as the older install of TW . . . . .
It sort of goes against the whole purpose of TW to run it on an “ancient” kernel . . . . If a change in graphics card doesn’t get it done, might be ye olde Nuke . . . followed by . . . Pave until I have a newer machine to play with.
You got it!
# fastfetch
,..., root@test
.,:lloooooc;. ----------------
,ool' oo,;oo: OS: openSUSE Tumbleweed x86_64
.lo' oo. oo: Host: 2447K70 (ThinkPad W530)
.oo. oo. oo: Kernel: Linux 6.14.0-1-default
:ol oo. 'oo Uptime: 6 hours, 21 mins
:oo .oo. .oo. Packages: 2395 (rpm)
.oooooooooooooo. .oo. Shell: bash 5.2.37
;oo. .oo. Display (LEN40B1): 1600x900 @ 60 Hz in 16" [Built-in]
'oo, .oo. Theme: Adwaita [GTK3]
"ooc,',,,,,,,,,,:ooc,,,,,,,,,,, Icons: Adwaita [GTK3]
':cooooooooooooooooooooooooool;. Cursor: Adwaita
.oo. .oo; Terminal: /dev/pts/2
.oo. .oo. CPU: Intel(R) Core(TM) i7-3740QM (8) @ 3.70 GHz
.oo. 'oooooooooo:ooo. GPU: Intel 3rd Gen Core processor Graphics Controller @ 1.30 GHz [Integrated]
.oo. 'oo. col Memory: 1.22 GiB / 31.17 GiB (4%)
.oo' 'oo col Swap: Disabled
coo 'oo oo' Disk (/): 83.60 GiB / 231.56 GiB (36%) - btrfs
coc 'oo .lo, Local IP (wlp3s0): 192.168.178.48/24
`oo, 'oo .:oo Battery (45N1011): 94% [AC Connected]
'ooooc,, ,:lol Locale: POSIX
`''"clc"'
#
Unattended upgrades are robust, low in CPU time and virtually never fail:
# journalctl -q -u transactional-update.service -g Consumed --no-hostname
Mar 17 04:56:38 systemd[1]: transactional-update.service: Consumed 2.585s CPU time.
Mar 18 00:00:39 systemd[1]: transactional-update.service: Consumed 2.578s CPU time.
Mar 19 00:00:39 systemd[1]: transactional-update.service: Consumed 2.692s CPU time.
Mar 19 05:43:16 systemd[1]: transactional-update.service: Consumed 53.797s CPU time.
Mar 20 00:00:26 systemd[1]: transactional-update.service: Consumed 2.707s CPU time.
Mar 21 00:04:01 systemd[1]: transactional-update.service: Consumed 1min 50.994s CPU time.
Mar 22 00:00:24 systemd[1]: transactional-update.service: Consumed 2.729s CPU time.
Mar 23 00:05:16 systemd[1]: transactional-update.service: Consumed 2min 56.007s CPU time.
Mar 24 00:00:32 systemd[1]: transactional-update.service: Consumed 2.689s CPU time.
Mar 25 00:00:32 systemd[1]: transactional-update.service: Consumed 2.662s CPU time.
Mar 26 00:01:00 systemd[1]: transactional-update.service: Consumed 24.730s CPU time.
Mar 27 00:00:07 systemd[1]: transactional-update.service: Consumed 6.194s CPU time.
Mar 28 00:02:15 systemd[1]: transactional-update.service: Consumed 37.928s CPU time.
Mar 29 00:06:43 systemd[1]: transactional-update.service: Consumed 2min 33.483s CPU time.
Mar 30 00:02:14 systemd[1]: transactional-update.service: Consumed 47.136s CPU time.
Mar 31 00:00:52 systemd[1]: transactional-update.service: Consumed 18.678s CPU time.
Apr 01 00:00:25 systemd[1]: transactional-update.service: Consumed 6.471s CPU time.
Apr 02 00:00:06 systemd[1]: transactional-update.service: Consumed 5.939s CPU time.
Apr 03 00:00:24 systemd[1]: transactional-update.service: Consumed 14.920s CPU time.
Apr 04 00:05:51 systemd[1]: transactional-update.service: Consumed 2min 18.448s CPU time.
Apr 05 00:04:31 systemd[1]: transactional-update.service: Consumed 1min 50.178s CPU time.
Apr 06 00:03:25 systemd[1]: transactional-update.service: Consumed 1min 22.324s CPU time.
Apr 07 00:00:11 systemd[1]: transactional-update.service: Consumed 6.270s CPU time.
Apr 08 00:01:43 systemd[1]: transactional-update.service: Consumed 1min 9.677s CPU time.
#Could you please stop pushing transactional-update to others? The devs do not support it on TW or Leap. Full stop here.
As the OP I am OK with getting information on ways that linux systems could be run and Karl provides that viewpoint. The purpose of a forum is sharing of information, and then it is up to the user to determine if it is something to try or not.
Personally, when I tried out his previous update script I discovered that it “wouldn’t work” for me because my machine is not running 24/7. I boot a system for the morning and then shut it down . . . so possibly shutting down in the middle of an upgrade, etc.
@karlmistelberger Thanks for the link to the Thinkpad information, that might have been your response to my DM?? I already have a newer laptop, Sys76 Gazelle . . . which I guess is a generic Taiwanese laptop badged as Sys76 which could possibly be a “rolling hardware” platform . . . it has an i7 10th gen cpu and combi Nvidia card with mobo graphics . . . which I have 3 linux distros installed on, now.
That is the schlep machine for work . . . still wondering about desktop machines that are a bit bigger and easier to get into than what the Mini-PC options look like . . . so that parts could be swapped in and out quick n dirty . . . ??? Laptops these days seem to involve many screws . . . doesn’t seem like the old PC days where the various components were under snap in lids for fast upgrades . . . . Fast is good. : - )
Do you actually think that a user is going to read a 186 post thread? IMNSHO this reduces the information value to …
The thread has had a lot of views in its lifespan. The OP is still looking for a solution to the issue presented in the long running thread, no need to start a new thread for the same problem until there is proof that no solution possible . . . . OR, until some pathway to tumbling forward with TW is discovered or provided here. TBD.
A post was split to a new topic: Resume issue after recent update
You may share output of inxi -Fmzy222.
The legacy w530 ThinkPads are readily serviceable: https://www.youtube.com/watch?v=gjIhWZKj-KQ Many newer laptops come with components soldered to the main board.
ATX is bulkier. Components are readily swapped in and out. Large cooling fans operate at low RPMs when removing 150 - 200 W thermal power. No CPU throttling occurs. Host 5700g has a PURE ROCK 2 cooler which is indeed silent.
sudo inxi -Fmzy222
System: Kernel: 6.12.10-76061203-generic arch: x86_64 bits: 64
Desktop: GNOME v: 46.0 Distro: Pop!_OS 24.04 LTS noble
Machine: Type: Laptop System: System76 product: Gazelle v: gaze15 serial: <filter>
Mobo: System76 model: Gazelle v: gaze15 serial: <filter> UEFI: coreboot v: 2023-09-08_42bf7a6 date: 09/08/2023
Battery: ID-1: BAT0 charge: 45.9 Wh (98.7%) condition: 46.5/48.0 Wh (96.7%)
Memory: System RAM: total: 16 GiB available: 15.49 GiB used: 3.92 GiB (25.3%) igpu: 64 MiB
Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
Device-1: Channel-0-DIMM-0 type: DDR4 size: 8 GiB speed: 2933 MT/s
Device-2: Channel-1-DIMM-0 type: DDR4 size: 8 GiB speed: 2933 MT/s
CPU: Info: 6-core model: Intel Core i7-10750H bits: 64 type: MT MCP cache: L2: 1.5 MiB
Speed (MHz): avg: 800 min/max: 800/5000 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
Graphics: Device-1: Intel CometLake-H GT2 [UHD Graphics] driver: i915 v: kernel
Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] driver: N/A
Device-3: Chicony USB2.0 Camera driver: uvcvideo type: USB
Display: server: X.Org v: 21.1.11 with: Xwayland v: 24.1.2 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~144Hz
API: EGL v: 1.5 drivers: iris,swrast platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.8-1ubuntu1~24.04.1 renderer: Mesa Intel UHD Graphics (CML GT2)
Audio: Device-1: Intel Comet Lake PCH cAVS driver: snd_hda_intel
Device-2: NVIDIA driver: snd_hda_intel
API: ALSA v: k6.12.10-76061203-generic status: kernel-api
Network: Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi
IF: wlp0s20f3 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet driver: r8169
IF: enp3s0f1 state: down mac: <filter>
Bluetooth: Device-1: Intel AX201 Bluetooth driver: btusb type: USB
Report: hciconfig ID: hci0 state: up address: <filter> bt-v: 5.2
Drives: Local Storage: total: 465.76 GiB used: 39.44 GiB (8.5%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G2B0C-00PXH0 size: 465.76 GiB
Partition: ID-1: / size: 47.76 GiB used: 14.18 GiB (29.7%) fs: ext4 dev: /dev/nvme0n1p3
ID-2: /boot/efi size: 511 MiB used: 215.3 MiB (42.1%) fs: vfat dev: /dev/nvme0n1p1
ID-3: /home size: 95.56 GiB used: 25.05 GiB (26.2%) fs: ext4 dev: /dev/nvme0n1p4
Swap: ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) dev: /dev/dm-0
ID-2: swap-2 type: zram size: 15.49 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors: System Temperatures: cpu: 45.0 C pch: 50.0 C mobo: N/A
Fan Speeds (rpm): cpu: 0
Info: Processes: 346 Uptime: 1h 48m Shell: Sudo inxi: 3.3.34
You may insert a 870 Evo or alike into the SATA slot and install from Tumbleweed Network Installation - x86_64
Alrighty, have yet to get under the hood on the Gazelle . . . it has an nvme drive, which I have partitioned and installed Sid & Gecko rolling. At the time I got that machine I was having a lot of issues w/ keeping TW running. But now when Gecko runs an upgrade there are a huge amount of time consuming “dracut” lines . . . . I was thinking about installing TW into the / partition, but wasn’t sure if the existing /home directory could be used, or if I would have to use a new one with the fresh install?? It’s Gecko rolling edition, which is TW . . . but with Packman already included . . . . It is more or less “the same” but then it is a “stack” . . . .
But, nice to know I could add another SATA drive into the mix, never enough drives.
In my case, the bug is reported and known:
https://bugs.kde.org/show_bug.cgi?id=483094
I suffered the black screen with mouse pointer thing, and after changing DM and try somethings, I discovered that this only happens in X11 sessions, not in Wayland ones with KDE and last NVIDIA proprietary drivers. And he said, and the last post of the bug conversation:
With 82% of telemetry-using Plasma users on Wayland, and KWin now split between Wayland and X11, X11 is going into formal maintenance-only mode now, so I’m downgrading the priority of this X11-only bug.
Sad for me. Say goodbye to KDE or change my remote access thing (meshcentral) that I have installed in lot of friends and family computers. So bye bye KDE 
Sad, indeed. There are still users of X11 . . . as Wayland still seems to be “buggy.” I just recently upgraded my Pop_OS! Gazelle which was stacked on jammy for several years, but in going to noble the DE was switched to their new offering Cosmic, which runs on Wayland only . . . . There were a number of problems with function, so I had to add the vanilla GNOME DE, which gave me the option for “GNOME on X11” . . . which I now use.
mmm I’m wondering if this is a plasma thing or only a kwin fail.
Maybe I can use KDE with another WM, losing the visual but keeping the functionality of KDE…
Someone?
Probably worth asking a question in the actual support categories. This is open chat, and it’s not likely going to get the visibility that asking a question that’s specifically asking for help with your issue would get.
I have same problem. Actually have had a long time. As far as I remember with this new upgrade I have had a year: Ryzen 5 7600x, B650 mobo and Nvidia 5080 or Nvidia 4070. Symptoms: after a sleep and wake up, the monitor stays dark, only mouse pointer visible and movable. When it is on sleep and when I move a mouse or press keyboard, some relay click on computer, so computer starts, but black display is on. Only the power off reset works.
I have done workaround that no sleep in suspend, only dimming the monitor after 5 minutes.
This is with X11 KDE as I can’t use Wayland. I have had drivers 550, 565 and the latest is 570.133.07. I suppose that I have used the range of kernels and I can’t remember that after a certain kernel, this kind of phenomenon appeared. But, there is alredy a bug report, so hopefully this is fixed some day.
@kinu So you said, “WM” . . . but do you really mean “DM”??? It is fairly easy in TW to add DEs, but then apparently they can’t be removed . . . . I added perhaps GNOME or KDE to get another DM option, but in my case the only one to work . . . after the apparent changes to SDDM were made . . . is LightDM.
As far as Plasma goes, there are other DE options, I have one distro running Plasma, but I never really liked it, because it is visually “too busy” . . . . I have MATE running on my TW install, and XFCE on my Leap 16.
@Tame Thanks for stopping by, this is more or less the exact problem that has been happening with my GTX 780 card . . . except I don’t get the mouse cursor, I just get the blackness. As far as the “bug report” goes, I filed one for this thread when it was on the help forum back in Jan, to very little fanfare . . . that is on the SUSE bugzilla site. The one post by Kinu . . . seems to be for KDE bug reports . . . don’t know if they all bubble up to the same place . . . . But, the only way to get action on a bug report is if numbers of folks report their problem on it . . . .
I noticed that there is already a thread for newer PCs, sorry for trolling…