Smartsound Plymouth

[Luciana]

HiI had posted a plymouth-git issue relating to the boot issues we've been having recently (I'm currently booting without the splash param). It's possible that the plymouth-git issue is related to the nvidia dkms drivers as I seem to recall this boot issue happening after switching to the nvidia driver.

Today, I received a response to my plymouth-git issue suggesting to have modsetting enabled. I haven't gotten clarification but, in digging, it seems that the modsetting could be referring to the drivers for intel video chips and not nvidia. I worry that I'm going to bork my install if I install/enable modsetting. What's the general thoughts here on modsetting? Unrelated to the issue or a possibility?

Thanks,

KB

Actually integrated graphics is provided by your CPU. and you are right I looked up your CPU online and it seems that Intel Core i7-4930K doesn't have integrated graphics.

Seems like waiting it is for plymouth-git and nivida drivers to work it out with each other.

The plymouth team suggested that I add nvidia_drm.modeset=1 to my kernel params to see if it fixes the issue. Worth testing before I take the latest update or nah? If it's useful for the Garuda team, I'll be happy to try.

I migrated to pipewire and pipewire-pulse from pulseaudio for audio, and I use wireplumber as the session manager for pipewire. Unfortunately, there has been many issues with audio, especially for the speakers. Sometimes, the speakers outputs the same volume and the volume cannot be changed by volume buttons (Applies to every configuration of built in audio except for Pro Audio). Sometimes, only the front left/ front right speakers work and the other don't output any sound. Sometimes, when I check pavucontrol in the output devices for the built in analog stereo, the speaker was unavailable and the headphone jack was plugged in for no reason. And finally, the speakers are available but simply doesn't produce any sound, and there is no sound that was displayed in pavucontrol. I tried to switch back to pulseaudio and pipewire-media-session, but the same issue occurs, forcing me to stay with pipewire and wireplumber.

I tried to switch back to pulseaudio and pipewire-media-session, but as I mentioned earlier, it didn't fix the issue. I tried to look at other posts that is somewhat relating to the issue. Some of them might've worked temporarily, but when an issue I had got fixed, I still had the other problems, especially for the unchanging volume which I could never find a solution to. I moved all the config files of pipewire, alsa, and wireplumber from /usr/share/ into /etc/ but that didn't do anything (note that I didn't look into the config files yet). I checked the status of the sessions pipewire, pipewire-pulse, and wireplumber and they all output at least one error. The sessions pipewire-pulse and wireplumber both showed input / output errors and I don't know why it's like that.

I did have pipewire-pulse installed with pipewire to begin with. I remember installing pulseaudio before to see if the issue would be solved and then replacing it back with pipewire-pulse. I reran the command for fuser and I didn't see pulseaudio and pulseaudio-bluetooth anywhere. I looked for pulseaudio services and sockets and I didn't see them. Just in case, I removed the config files for pulseaudio.

After the reboot, the audio gets cuts out like usual and then comes back and then cuts out after a period of time, so I had to switch between ports to get the audio back. The analog stereo output still cannot change the actual volume from volume buttons but Pro Audio could, as usual. I checked the status of the sessions and the errors are the same. As of right now I only see the input output error for Capture. There are mod.protocol-pulse i/o errors for pipewire-pulse but now it's from Plasma PA so maybe that's the culprit. I will repost the status of the sessions and the fuser output

I don't remember setting "dmic_detect=0" and I couldn't find that option in /etc/modprobe.d/, except for putting "options snd-hda-intel model=generic" in /etc/modprobe.d/alsa-base.conf so pipewire could detect the audio cards I have. I tried to find it in /etc/ using grep but there's no output so I think there isn't. I checked in the entire drive where I use arch on, and there are some matches, but I don't think they are important because it's about firefox

I commented the line of code "options snd-hda-intel model=generic" and rebooted. No speaker cards were used as expected. However, the issues with pipewire and pipewire-pulse is gone, except for wireplumber. The reason I added that line in modprobe before so the speaker cards were detected. I checked the sound cards in my system now and the cards looked different.

Edit:

When I configure the audio, there are only two options: analog stereo input and pro audio. I can get the sound back by switching to Pro Audio, but I need to have analog stereo duplex to be an available option so I can both use the mic and the speaker. When I select Pro Audio, both front speakers work without any issue

Also I tried to reinstall sof-firmware, and I found that there was an error during the installation of sof-firmware as it said that the "command failed the execute correctly". Not sure if that is related though

I realized I was dumb and I didn't install plymouth and installed it and I can finally reinstall sof-firmware. There was no output from the other command even after rebooting. Also would my analog stereo output profile get detected if sof-firmware is used? My speakers are currently working and it's just that they are just called "Line Out" and "Headphones" and they aren't in a profile.

When I did the "options snd-hda-intel model=generic" configuration in /etc/modprobe.d/alsa-base.conf, the ports contained speakers, so I doubt it's a cosmetic issue. Currently, I don't have an issue with audio, just an inconvenience. I'm going to mark this solved and I'll apologize for going off topic and wasting time.

You didn't waste anyones time because it was necessary to get of the "generic" assignment and this frankly isn't anywhere near solved.

You put the "generic" there, so you got generic labels - and control issues, because it's a bad "solution" for the initial problem.

3a8082e126