Fedora 44 KDE issues with Lenovo Slim 7i (sound & sleep)

Hi everybody,

Just got a new laptop and experiencing two issues with Fedora 44. Since this is a newer-generation model (Intel Ultra 7 355) could it simply be that some drivers have not been added to the kernel?

Secure boot is off, and could not find a fast boot option to turn off in the bios. Fastfetch screencap and sound screencap attached. This is the unit I got and here is its support page just in case. Win 11 works just fine.

Issues:

  1. F44 does not detect on-board sound chip, it’s Intel’s SST, and based on what I could find it should work. The funny part when I’m home the laptop find my ungrouped Sonos speakers and takes over the one in my office. Screenshot attached to show what KDE sees, and I plugged in headphones to make sure sound came out of somewhere

  2. Laptop never wakes from sleep mode, screen remains dark, and it’s 100% Intel no NVidia in this unit. After reading on the topic I disabled network boot pxe as it could be a factor (?) and no chages.

Any suggestions or advice? I really like the laptop, and am under a 30-day return window which I don’t think is needed for these issues.

Thanks in advance!


A couple of things I’d check before returning the laptop.

For the audio issue, Intel SST support can depend heavily on the exact Intel platform and kernel/SOF firmware version. Since this is a very new Ultra 7 355 system, Fedora 44 may simply not have complete support yet. I’d check inxi -A and lspci -nnk | grep -A3 -i audio to see whether the SST/audio controller is detected and which driver is being used. Also check dmesg for sof, snd, or audio errors.

For the sleep issue, that sounds more like a kernel/firmware/platform compatibility problem than PXE or network boot. I’d test both suspend modes with cat /sys/power/mem_sleep and see whether s2idle vs deep makes a difference. Checking journalctl -b -1 after a failed wake can also show whether the machine actually resumed and the display just failed to come back. I do have this issue too, with a NVIDIA/AMD hybrid laptop so I doubt it’s anything to do with any driver related to Intel, but it remains possible.

If you post the output of those commands (plus inxi -Fz), someone should be able to tell you pretty quickly whether the hardware is being detected correctly.

Hi Daniel,

First, thanks for your reply I really appreciate it.

The good news on the sleep issue is that it was solved between my post and your reply, a bunch of firmware updates were pushed and I suspect this did the trick.

On the sound issue, I agree, it should be a matter of time. And am keeping the laptop btw :slight_smile:

Here are the results of the commanded you suggested:
1- -inxi -A

Audio:
Device-1: Intel Core Ultra Processors HD Audio
driver: sof-audio-pci-intel-ptl
API: ALSA v: k7.1.8-200.fc44.x86_64 status: kernel-api
Server-1: PipeWire v: 1.6.8 status: active

2- lspci:

00:1f.3 Multimedia audio controller [0401]: Intel Corporation Core Ultra Processors (Series 3) HD Audio [8086:e428] (rev 01)
Subsystem: Lenovo Device [17aa:3839]
Kernel driver in use: sof-audio-pci-intel-ptl
Kernel modules: snd_sof_pci_intel_ptl, snd_hda_intel
00:1f.4 SMBus [0c05]: Intel Corporation Core Ultra Processors (Series 3) SMBus [8086:e422] (rev 01)
Subsystem: Lenovo Device [17aa:383a]

Looks like but feels like a Lego brick is missing which is coming.

Since the driver and firmware both look properly detected, I don’t think this is a KDE bug, it’s more likely PipeWire/ALSA just isn’t exposing a sink at all, which would explain why KDE shows nothing. My guess is a missing UCM/topology profile for this board. Can you run wpctl status and aplay -l and see if either shows a playback device?

Thanks - here are the outputs - aplay sees no soundcard same for wpctl

jp@Ideapad:~$ aplay -l
aplay: device_list:279: no soundcards found…

jp@Ideapad:~$ wpctl status
PipeWire ‘pipewire-0’ [1.6.8, jp@Ideapad, cookie:3691197148]
└─ Clients:
32. WirePlumber [1.6.8, jp@Ideapad, pid:1397]
36. pipewire [1.6.8, jp@Ideapad, pid:1398]
46. WirePlumber [export] [1.6.8, jp@Ideapad, pid:1397]
59. uresourced [1.6.8, jp@Ideapad, pid:1714]
60. kwin_wayland [1.6.8, jp@Ideapad, pid:1725]
61. libcanberra [1.6.8, jp@Ideapad, pid:1881]
66. [1.6.8, jp@Ideapad, pid:1881]
67. plasmashell [1.6.8, jp@Ideapad, pid:1908]
68. libcanberra [1.6.8, jp@Ideapad, pid:1908]
69. Brave input [1.6.8, jp@Ideapad, pid:378]
70. wpctl [1.6.8, jp@Ideapad, pid:5079]
75. xdg-desktop-portal [1.6.8, jp@Ideapad, pid:2265]
76. [1.6.8, jp@Ideapad, pid:1908]

Audio
├─ Devices:

├─ Sinks:
│ * 38. Dummy Output [vol: 0.20]

├─ Sources:

├─ Filters:

└─ Streams:

Video
├─ Devices:
│ 50. Integrated Camera [v4l2]
│ 51. Integrated Camera [v4l2]
│ 52. Integrated Camera [v4l2]
│ 53. Integrated Camera [v4l2]
│ 54. Integrated Camera: Integrated C [libcamera]
│ 55. Integrated Camera: Integrated I [libcamera]

├─ Sinks:

├─ Sources:
│ * 62. Integrated Camera (V4L2)
│ 64. Integrated Camera (V4L2)

├─ Filters:

└─ Streams:

Settings
└─ Default Configured Devices:
0. Audio/Sink alsa_output.pci-0000_00_1f.3.pro-output-3

Just rechecked everything, kernel 7.19 did not bring the hoped changes

With new hardware Linux (too) often has issues with power management, audio, WiFi, &/or BlueTooth, but there are now good inexpensive USB device for the last 3, and it is usually possible to get around power management issues if AC power is available (it does help that newer systems generally boot quickly).