Vaio Z internal mic, no capture after sleep, works again after restart system

Hello,

My laptop internal mic seems to never not want to capture after sleep. It works after system restart, but never after sleep. It has always been in this way from the moment I freshly installed openSUSE for the first time until now and I’m not sure how to get it working. :sob:

My system:

  • Sony Vaio Z VJZ131
  • Tumbleweed 20240107
  • KDE Plasma 5.27.10
  • Kernel 6.6.9-1-default (64-bit)
  • no modprobe.d for sound being used:
% ls /etc/modprobe.d/
50-yast.conf

Testing with arecord -vv -f S16_LE -c 2 -D hw:0,0 new.wav and aplay new.wav.

Before sleep, internal mic works:

% arecord -l                                                    
**** List of CAPTURE Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC282 Analog [ALC282 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

After sleep (triggered by lid closed and later reopen), mic no longer captures:

% arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC282 Analog [ALC282 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Before and after, I see an “internal microphone” listed, and seems to have volume level set, but after sleep, there is no indication that it is capturing any level of sound.

Screenshot_20240116_061451

This may need a bug report to resolve. Does restarting pipewire and/or wireplumber resinstate the microphone capture?

systemctl --user restart pipewire wireplumber

Thanks, @deano_ferrari
Unfortunately that does not fix it or reinstate the microphone capture.

Worth a shot though. Does toggling the microphone mute make a difference? As I mentioned already, you may need to submit a bug report for this. Hardware details will be relevant here.

https://bugzilla.opensuse.org/index.cgi

If you need guidance about doing this, the following wiki page may be useful

https://en.opensuse.org/openSUSE:Submitting_bug_reports

1 Like

Thanks @deano_ferrari
I tried toggling and a few other things… even a reinstall (due to other unrelated issues), and still the condition is the same. I’ll follow your advice next chance I get.
Thanks again!