Douper2 commented 1 year ago

So at one point I got the Dummy Output issue and that was kinda fixable by just holding space on startup and selecting oldkern.conf but today I got the Dummy Output issue there aswell. I have pipewire installed. Now I know that the issue might be fixed by installing the pulseaudio package but i can't because of E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. I don't know what happend but what I know is that I was playing Hearts of Iron 4 and the screen froze, as usual I just shut down my pc using the power button. Maybe that's why. Please help. Also yes I did try to use the official audio troubleshooting guide but nothing worked.

My alsa-base.conf:

autoloader aliases"

install sound-slot-0 /sbin/modprobe snd-card-0 install sound-slot-1 /sbin/modprobe snd-card-1 install sound-slot-2 /sbin/modprobe snd-card-2 install sound-slot-3 /sbin/modprobe snd-card-3 install sound-slot-4 /sbin/modprobe snd-card-4 install sound-slot-5 /sbin/modprobe snd-card-5 install sound-slot-6 /sbin/modprobe snd-card-6 install sound-slot-7 /sbin/modprobe snd-card-7

Cause optional modules to be loaded above generic modules

install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet --use-blacklist snd-seq ; } #

Workaround at bug #499695 (reverted in Ubuntu see LP #319505)

install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; } install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; } install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet --use-blacklist snd-seq-oss ; : ; } # install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }

Cause optional modules to be loaded above sound card driver modules

install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; } install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq ; }

Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)

install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }

Prevent abnormal drivers from grabbing index 0

options bt87x index=-2 options cx88_alsa index=-2 options saa7134-alsa index=-2 options snd-atiixp-modem index=-2 options snd-intel8x0m index=-2 options snd-via82xx-modem index=-2 options snd-usb-audio index=-2 options snd-usb-caiaq index=-2 options snd-usb-ua101 index=-2 options snd-usb-us122l index=-2 options snd-usb-usx2y index=-2

Ubuntu #62691, enable MPU for snd-cmipci

options snd-cmipci mpu_port=0x330 fm_port=0x388

Keep snd-pcsp from being loaded as first soundcard

options snd-pcsp index=-2

Keep snd-usb-audio from beeing loaded as first soundcard

options snd-usb-audio index=-2

options snd-hda-intel single_cmd=1 options snd-hda-intel probe_mask=1 options snd-hda-intel model=basic "

And my aplay -l output:

"aplay: device_list:274: no soundcards found..."

Also here's my alsa-info link: http://alsa-project.org/db/?f=e5fb120fb16fa5eae9b20d94010f4108941aa16d

n3m0-22 commented 1 year ago

There have been multiple reports that Pipewire 0.3.70 fixes this issue. It would be best to try it if you haven't already. These instructions explain what you need to do. If that does not resolve the issue for you we can look into this further.

Douper2 commented 1 year ago

There have been multiple reports that Pipewire 0.3.70 fixes this issue. It would be best to try it if you haven't already. These instructions explain what you need to do. If that does not resolve the issue for you we can look into this further.

I tried pipewire 0.3.70 but it didn't work. Should I try a refresh install?

CABellamy commented 1 year ago

I've tried the fix above but I receive Err:17 http://apt.pop-os.org/staging/pipewire-0.3.70 jammy Release 404 Not Found [IP: 18.172.89.14 80] Reading package lists... Done I tried looking for the release on this github and can't find it anywhere it's not on apt either the above comes back as 404. Is there any update on this issue please? I can find 0.3.65 and I've tried reinstalling that to no avail.

leviport commented 1 year ago

@CABellamy That's because the PR was merged, like my instructions mentioned. Run the command I shared in that comment to remove the source and apply updates normally. This will give you the most recent version of Pipewire. You can confirm the version you have installed with apt policy pipewire