Hello everyone,
I had to fix my Laptop, and wasn’t able to use it for nearly four months because of that. Now, after returning and doing 10Gbs of updates, my laptop hasn’t been able to properly shut down for a few days now. No matter if I use shutdown, reboot, suspend or poweroff, it will always has some sort of issue.
Additionally, there is no audio anymore. I usually used PulseAudio, and the audio still works in other OSes.
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 17
Tile Size: 65472
User Name: actwo
Host Name: actwo
Server Name: pulseaudio
Server Version: 17.0
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: auto_null
Default Source: auto_null.monitor
Cookie: 6a3a:59e5
pactl list cards:
none
amixer:
Simple mixer control 'Master',0
Capabilities: pvolume pswitch pswitch-joined
Playback channels: Front Left - Front Right
Limits: Playback 0 - 65536
Mono:
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch cswitch-joined
Capture channels: Front Left - Front Right
Limits: Capture 0 - 65536
Front Left: Capture 65536 [100%] [on]
Front Right: Capture 65536 [100%] [on]
Please tell me if you need further information, I am currently using LTS 6.6.26-1
Exagerating you are - I believe - but impossible to provide any meaningful response.
Lack of audio doesn’t prevent usage - neither does it prevent shutdown.
Jugding from a part of the initial topic - you are using some kind of Lenovo hardware - that rarely causes any issues.
pulseaudio is - kind’a - a dying beast - pipewire to replace - giving no issues that I know of - at least not with the variety of hardware at my disposal.
Use amixer --card=0 to show ALSA mixer controls for onboard audio device
PulseAudio creates auto_null sink (Dummy Output) only if it cannot detect any audio playback devices
If PulseAudio is unable to detect onboard audio device it should be possible to play audio direct to onboard audio device in ALSA to confirm ALSA & hardware is working
If audio playback to ALSA device works as expected, remove PulseAudio user configuration databases and restart PulseAudio
Sadly, it isn’t fixed. After a successful reboot the audio is gone again, and just running those commands isn’t enough anymore. I can’t figure out how to get it to run again.
Well your system looked a little off to begin with.
So … please do what I suggested;
sudo pacman -Syu manjaro-pipewire
PS.
This would only start the service during that one session.
I could also give a comparison of my system here; pipewire.socket and pipewire-pulse.socket should both be enabled.
(pipewire.service and pipewire-pulse.service are disabled)
But maybe we should skip that manual service control stuff until you have the correct packages
Are bad aliens - no package exist in repos or AUR.
It is possible these are manually built packages.
But more than likely they are simply packages you should not have.
It is also notable that some of these have current replacements in the repos;
libsidplayfp podofo webkit2gtk
Are all available in the repos as current versions (note the lack of a trailing version in the package name itself).
In the case of systemd-fsck-silent I do not know if it is replacing regular systemd or what … but do make sure you have systemd.
It looks mostly like its doing what it should during shutdown.
There is that watchdog with a timeout of 10 minutes … and you probably dont need or want a watchdog anyways.
I know you noted it shutdown properly when sound was working … but we might try to get rid of the watchdog regardless;
To unload the module now:
sudo rmmod iTCO_wdt
To blacklist the module:
echo "blacklist iTCO_wdt" | sudo tee /etc/modprobe.d/blacklist-watchdog.conf
Theres also a guide on watchdogs of sorts:
I notice you have a number of redundant snaps.
(and as usual for snaps they are all mounted concurrently for no good reason …)
I also note that none of these are applications … they are things like mesa and gnome.
You arent running on these things are you? Like your desktop session is not using the SNAP mesa, is it?
My real suggestion is to remove all things snap in general.
But short of that you may wish to go cleaning it up. If only not to have multiple snapd and so on.
First off, I do need some of those tools - like NRF Connect.
The last time I was able to use my machine before it broke, end of December 2023, it all worked flawlessly. Just now after the updates it broke in that manner. The machine’s display broke, which led to me being unable to use it for months until I did Boardrepair on the PCB. I have removed the watchdog for now, and will see if rebooting still works.
Mesa should be there due to WINE, as i tried WINE/Proton quite some time ago.
My session shouldn’t be using gnome or MESA, no. I just removed gnome and some other stuff. I am going to reboot now to see what happens.
