Bug 1205100 - No sound from internal speakers [Samsung GBP360 aka NP930QDB]
Summary: No sound from internal speakers [Samsung GBP360 aka NP930QDB]
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Sound (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Takashi Iwai
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-05 14:40 UTC by jerome tako
Modified: 2025-06-18 01:13 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
alsa-tools.sh output (46.27 KB, text/plain)
2022-11-06 13:36 UTC, jerome tako
Details
dmesg output (81.20 KB, text/plain)
2022-11-06 13:40 UTC, jerome tako
Details
alsa-tools.sh output 14 nov (64.01 KB, text/plain)
2022-11-15 05:48 UTC, jerome tako
Details
alsa-info 21Nov (28.14 KB, application/x-shellscript)
2022-11-22 14:37 UTC, jerome tako
Details
alsa info output (72.10 KB, text/plain)
2022-11-22 15:01 UTC, jerome tako
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jerome tako 2022-11-05 14:40:43 UTC
Distro info : Gecko Linux Rolling KDE (based on openSUSE Tumbleweed).  Kernel is 6.0.6.1-default.  
Machine info : Samsung Galaxy Book Pro 360, 13", 2021.  Specific model NP930QBD-ke1US.  Hardware is intel 11th-gen tiger lake - not getting sound from the internal speakers to be a consistent issue across manufacturers using tiger lake chips.  I can't find the name of the sound card but I *think* it's a Realtek ALC298 (I think that's the one used in the 15" version of the same machine).

My internal microphone, sound via wired and bluetooth headphones/speakers are all WORKING.  The only thing that isn't is getting sound through my internal speakers. I've attempted several fixes that I'll link to below, but it just isn't working for me yet.  Below this post I'll also link all of the posts I've found around the net trying to research the issue.  Please note, I'm a novice linux user, typically I can only get around by copy/pasting solutions I find on forums, so please be specific in spelling out anything you'd like me to try.  

Some users report fixing the issue by installing these packages through YaST : 
intel-media-driver, libigdgmm12, libmfx-gen1_2, sof-firmware

I already have these installed but have no sound.  Removed and reinstalled through YaST but the issue persists.

Many other posts online link back to a tutorial that was posted on a Manjaro forum : https://forum.manjaro.org/t/howto-set-up-the-audio-card-in-samsung-galaxy-book/37090

I tried this method on Ubuntu Studio 22.04 but it did not resolve the issue, and I had gotten some more Ubuntu-specific guidance here (also didn't work) :
https://www.reddit.com/r/Ubuntu/comments/yikcnc/need_help_porting_a_manjaro_tutorial_for_a_ubuntu/

I can't really start that tutorial's method because I can't seem to install the package alsa-tools.
 https://software.opensuse.org/package/alsa-tools?search_term=alsa+tools

here are some of the terminal outputs I've seen requested in forums, hopefully they help.  

LSHW : 
*-multimedia
  description: Multimedia audio controller
  product: Tiger Lake-LP Smart Sound Technology Audio Controller
  endor: Intel Corporation
  physical id: 1f.3
  bus info: pci@0000:00:1f.3
  logical name: card0
  logical name: /dev/snd/controlC0
  logical name: /dev/snd/hwC0D0
  logical name: /dev/snd/hwC0D2
  logical name: /dev/snd/pcmC0D0c
  logical name: /dev/snd/pcmC0D0p
  logical name: /dev/snd/pcmC0D31p
  logical name: /dev/snd/pcmC0D3p
  logical name: /dev/snd/pcmC0D4p
  logical name: /dev/snd/pcmC0D5p
  logical name: /dev/snd/pcmC0D6c
  logical name: /dev/snd/pcmC0D7c
  version: 20   width: 64 bits   clock: 33MHz
             capabilities: pm msi bus_master cap_list
             configuration: driver=sof-audio-pci-intel-tgl latency=32
             resources: iomemory:600-5ff iomemory:600-5ff irq:173 memory:601d190000-601d193fff memory:601d000000-601d0fffff

  *-input:11
       product: sof-hda-dsp Mic
       physical id: d
       logical name: input25
       logical name: /dev/input/event15
  *-input:12
       product: sof-hda-dsp Headphone
       physical id: e
       logical name: input26
       logical name: /dev/input/event16
  *-input:13
       product: sof-hda-dsp HDMI/DP,pcm=3
       physical id: f
       logical name: input27
       logical name: /dev/input/event17
  *-input:14
       product: sof-hda-dsp HDMI/DP,pcm=4
       physical id: 10
       logical name: input28
       logical name: /dev/input/event18
  *-input:15
       product: sof-hda-dsp HDMI/DP,pcm=5
       physical id: 11
       logical name: input29
       logical name: /dev/input/event19
 
INXI -SMA
System:
  Host: koti Kernel: 6.0.6-1-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE
    Tumbleweed 20221103
Machine:
  Type: Convertible System: SAMSUNG product: 930QDB v: P06AKH serial: 4WNM9FGR602555
  Mobo: SAMSUNG model: NP930QDB-KE1US v: SGLA867A1X-C01-G001-S0002+10.0.19042
    serial: 123490EN400015 UEFI: American Megatrends LLC. v: P06AKH.019.210608.KS date: 06/08/2021
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: sof-audio-pci-intel-tgl
  Sound Server-1: ALSA v: k6.0.6-1-default running: yes
  Sound Server-2: PipeWire v: 0.3.59 running: yes




LSPCI -KVV
00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)
        DeviceName: Onboard - Sound
        Subsystem: Samsung Electronics Co Ltd Device c1a6
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 32, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 173
        IOMMU group: 12
        Region 0: Memory at 601d190000 (64-bit, non-prefetchable) [size=16K]
        Region 4: Memory at 601d000000 (64-bit, non-prefetchable) [size=1M]
        Capabilities: <access denied>
        Kernel driver in use: sof-audio-pci-intel-tgl
        Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl



FOUND ONLINE POSTS REGARDING THIS ISSUE
BUGS FOUND
    [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518

    {Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows) Bug #1850702 reported by Filipe Garrett on 2019-10-30
    https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702

    [930MBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers
    https://bugzilla.kernel.org/show_bug.cgi?id=207423

    [SOLVED] Bug 1204915 - No sound from Internal Speakers with Kernel 6.0.5
    https://bugzilla.opensuse.org/show_bug.cgi?id=1204915

SOLVED ISSUES
    [SOLVED] Samsung Galaxy Book Pro 360 - Speaker Issues ALC298
    https://bbs.archlinux.org/viewtopic.php?id=269385

    [HowTo] set up the audio card in Samsung Galaxy Book MANJARO FORUMS
    https://forum.manjaro.org/t/howto-set-up-the-audio-card-in-samsung-galaxy-book/37090

        SIMILAR RESPONSE (UBUNTU INSTRUCTIONS) TO MY REDDIT POST
        https://www.reddit.com/r/Ubuntu/comments/yikcnc/need_help_porting_a_manjaro_tutorial_for_a_ubuntu/

    Samsung Galaxy Book Pro 360 No Sound Ubuntu 21.10 - Reddit post with comments claiming solve
    https://www.reddit.com/r/Ubuntu/comments/rt4b05/samsung_galaxy_book_pro_360_no_sound_ubuntu_2110/
        LINKS TO THIS UBUNTU FORUMS THREAD
        https://ubuntuforums.org/showthread.php?t=2467804

    Bug 213953 - HP x360 Spectre speakers not working (Tigerlake, 15-eb1xxx/8811)
    https://bugzilla.kernel.org/show_bug.cgi?id=213953
        TIGERLAKE (11THGEN) CHIPS HAVE SPEAKER ISSUES ACROSS MANUFACTURERS.

    ARCHLINUX WIKI, LISTS GBP360 AS SOUND WORKING*
    https://wiki.archlinux.org/title/Laptop/Samsung
        LINKS TO ALSA WIKI PAGE
        https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture#ALSA_firmware

    SOUND CARD IS NOT WORKING (r/openSUSE)
    https://www.reddit.com/r/openSUSE/comments/t7127q/sound_card_is_not_being_detected/
        "Edit: My sound if finally fixed!!! I am just so dumb, after opening the yast software center it suggested me to download some packages. After downloading those and restarting my sound now works!!! I love opensuse!!!  These are the packages that were installed after opening yast software:
        intel-media-driver, libigdgmm12, libmfx-gen1_2, sof-firmware"
Comment 1 Takashi Iwai 2022-11-06 07:26:08 UTC
Could you give alsa-info.sh output?  Run the script with --no-upload option, and attach the output to Bugzilla.
Also, give the dmesg output from 6.0.6 kernel, too.
Comment 2 jerome tako 2022-11-06 13:36:12 UTC
Created attachment 862673 [details]
alsa-tools.sh output
Comment 3 jerome tako 2022-11-06 13:40:17 UTC
Created attachment 862674 [details]
dmesg output
Comment 4 jerome tako 2022-11-06 13:42:45 UTC
(In reply to Takashi Iwai from comment #1)

Attached both text files.  I did not have a file alsa-tools.sh already, so I ran this command found online : 
wget http://www.alsa-project.org/alsa-info.sh -O alsa-info.sh && bash alsa-info.sh

dmesg I just ran from my home directory as such. Thank you for the help, let me know if there's any other info you need.
Comment 5 Takashi Iwai 2022-11-06 15:40:35 UTC
alsa-info.sh must be included in the standard alsa-utils package (in /usr/sbin/alsa-info.sh).  I guess you looked at a wrong command name or path.

Through a quick glance, all logs look OK.  And since the problem is only about the speaker output, it must be some vendor-specific implementations of the speaker amp on this hardware, and that's not trivial to figure out.
You can try various model option for checking the existing quirks for other devices, at least.  The best would be to get the information / fix from the hardware vendor, of course.
Comment 6 jerome tako 2022-11-06 23:20:14 UTC
(In reply to Takashi Iwai from comment #5)
I will see if I can find any drivers from the vendor, though I suspect if anything it would end up being a windows driver hopefully someone has already ported.  It sounds like you're saying this might not be fixable?

If it's not too much trouble, since you're probably the most knowledgeable person I'm going to get to ask : Can you glance through that manjaro forums tutorial and let me know if it ought to work, or if there are any alterations I might expect to make (eg different packages/commands/file locations)?  (first link I included)
Comment 7 Takashi Iwai 2022-11-13 10:02:44 UTC
Well, the primary question is whether just running the majaro's script (TO912.sh) makes your speaker working or not.  It's not necessarily to be run at systemd unit, you could run at any time (but run as root).

If that's working, another thing to try it the following:
- Create /etc/modprobe.d/90-hda.conf containing the following two lines:

options snd-intel-dspcfg dsp_driver=1
options snd-hda-intel model=alc298-samsung-amp

Then reboot and retest.  This will switch the driver from SOF to the legacy HDA-Intel.  You'll lose the built-in mic capability by this, but it's only for testing the speaker.  After testing, you can remove this file again to restore to the original state.

If this makes working without anything else, I can create a test patch.
Comment 8 jerome tako 2022-11-13 14:37:47 UTC
1. cd /etc/modprobe.d
2. sudo nano 90-hda-intel.conf
3. Write lines in file:
options snd-intel-dspcfg dsp_driver=1
options snd-hda-intel model=alc298-samsung-amp

Then ctrl-O to save, Ctrl-X to exit.
4.  Restart  - Success!  Yes that got sound to come from the internal speakers.

//
I didn't get far attempting to do that manjaro tutorial because there aren't any available working packages for openSUSE for alsa-tools.  None of these worked for me, I could download the rpms and yums but the installations would fail because of dependency errors.  I asked around on some other forums (https://github.com/geckolinux/geckolinux-project/discussions/453) and someone pointed out that the only executable files in the alsa-tools debian package are 
    as10k1
    hda-verb
    hdajacksensetest
    sbiload
    us428control
(which I had already downloaded and installed through YaST).  

Here's as far as I had gotten following the Manjaro guide :
1. sof-firmware already installed (version 2.2.2-1.1.noarch)
2. I cannot find an installation candidate for alsa-tools.sh.
3. Go to the folder /etc/modprobe.d and create a file "blacklist.conf", then add this line : "options snd slots=snd_soc_skl_hda_dsp".
4. Also create a file called sof.conf in the same location, and add the line "options snd slots=snd_soc_skl_hda_dsp".
5. The Manjaro guide suggests renaming a file I don't have 
(/etc/modprobe.d/alsa-base.conf) simply to alsa-base.conf/backup.
Comment 9 jerome tako 2022-11-13 23:53:41 UTC
After restarting, I may have screwed something up.  I installed some audio programs (ardour, geekosdaw which has several dependencies), and then audio seemed basically broken again.  Now I have no sound through plugged-in speakers, and no internal speaker sound, the only thing working is bluetooth sound.  SHould I roll back to several hours ago when I last replied?

It's so confusing, I've been hoping to use SUSE to make some music, but it's such a fight just to play a midi instrument so far.
Comment 10 Takashi Iwai 2022-11-14 07:19:01 UTC
That's a good news.

Now I'm building a test kernel with the fix patch to apply the quirk for your device in OBS home:tiwai:bsc1205100.  Once when the kernel is built (it takes for an hour or so), the package will appear at
   http://download.opensuse.org/repositories/home:/tiwai:/bsc1205100/standard/

Please give it a later.  This should work as-is without the previous workaround.
Comment 11 jerome tako 2022-11-14 14:29:48 UTC
Thanks for making this patch!  But... how do I use it exactly?  I've never upgraded a kernel beyond running zypper upgrades.
Comment 12 Takashi Iwai 2022-11-14 15:28:04 UTC
* Download kernel-default-6.*.rpm from
  http://download.opensuse.org/repositories/home:/tiwai:/bsc1205100/standard/x86_64/kernel-default-6.0.8-1.1.ge5f6cc1.x86_64.rpm

* Install it via zypper
  % zypper in kernel-default-6.0.8*.rpm

zypper might warn you about the GPG or such, just accept it.
Comment 13 Takashi Iwai 2022-11-14 15:30:00 UTC
About zypper install: you might need to pass --oldpackage, depending on the package you've already installed.

Also, it'd be better to increase the number of installable kernels beforehand, too.  Just edit /etc/zypp/zypp.conf, and add more entries to the line defining "
multiversion.kernels = ...",
e.g.
  multiversion.kernels = latest,latest-1,latest-2,latest-3,running

This will allow the system keeping up to 3 old kernels.
Comment 14 jerome tako 2022-11-15 00:52:02 UTC
(In reply to Takashi Iwai from comment #13)
> About zypper install: you might need to pass --oldpackage, depending on the
> package you've already installed.
> 
> Also, it'd be better to increase the number of installable kernels
> beforehand, too.  Just edit /etc/zypp/zypp.conf, and add more entries to the
> line defining "
> multiversion.kernels = ...",
> e.g.
>   multiversion.kernels = latest,latest-1,latest-2,latest-3,running
> 
> This will allow the system keeping up to 3 old kernels.

can you give a more specific instruction on what to add for that line.  Like, should it read :
6.0.8-1-default, 6.0.8-1.ge5f6cc1-default
and should it actually say "running" at the end?

Also, after everything was working the last few days, I'm not sure what has happened but all my sound is gone again.  No speakers, headphones, or bluetooth functioning.  I think I did upgrade my tumbleweed install.  I also installed bitwig studio, which I know has many audio codecs, but audio was working fine after installing and running that program a little.  I also installed the brave broser, that was the last thing before I lost functionality.  I removed it and the repository & the one package that came with it, but that did not fix my sound.  Kernel is still the one you linked to.  I'll try re-installing that kernel to see if that works before I do any snapshot rollbacks.
Comment 15 jerome tako 2022-11-15 05:36:23 UTC
I booted into a few different snapshots but once again had no sound.  I am new to suse/btrfs though, so there's a chance I didn't understand how to properly use snapshots and rollbacks.  

But so I rolled back to right before I tried your kernel (when, previously, I *did* have sound simply after editing that modprobe.d file - which is still there).  6.0.8-1-default.  But now trying to install your kernel I get a download error : 
jerome@koti:~/System> sudo zypper install kernel-default-6.0.8-1.1.ge5f6cc1.x86_64.rpm
[sudo] password for root: 
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
  kernel-default-6.0.8-1.1.ge5f6cc1

The following package requires a system reboot:
  kernel-default-6.0.8-1.1.ge5f6cc1

1 new package to install.
Overall download size: 64.0 MiB. Already cached: 0 B. After the operation, additional 216.1 MiB will be used.

    Note: System reboot required.
Continue? [y/n/v/...? shows all options] (y): y
Retrieving package kernel-default-6.0.8-1.1.ge5f6cc1.x86_64                                                                       (1/1),  64.0 MiB (216.1 MiB unpacked)
kernel-default-6.0.8-1.1.ge5f6cc1.x86_64.rpm:
    Header V3 RSA/SHA256 Signature, key ID 4bf05f46f6e74bf5: NOKEY
    Payload SHA256 ALT digest: BAD (Expected c4f098f8c81c1e811dad99cd0c24b2e45f5360666e932e030e08a9a0398ef5f9 != 9d902dc294cac26f9ce21b711b05bbb3735b234e44e0f5b9b7907f7060d435bd)
    Payload SHA256 digest: BAD (Expected 348f323747eb191d798324c8abc20624487bc5f63e9db6cf4eef72a8a52d81cc != 9d902dc294cac26f9ce21b711b05bbb3735b234e44e0f5b9b7907f7060d435bd)
    V3 RSA/SHA256 Signature, key ID 4bf05f46f6e74bf5: BAD
    MD5 digest: BAD (Expected 9ebf01af1e34d9d7e301820277a9d51f != 554ff8f9cb92a4eca46688481116190e)

kernel-default-6.0.8-1.1.ge5f6cc1.x86_64 (Plain RPM files cache): Signature verification failed [2-Signature does not verify]



Trying through YaST gives a similar issue : Error: INVALID:kernel-default-6.0.8-1.1.ge5f6cc1.x86_64 (file-dae58073): Signature verification failed [4-Signatures public key is not available]
    Header V3 RSA/SHA256 Signature, key ID 4bf05f46f6e74bf5: NOKEY
    Header SHA256 digest: OK
    Header SHA1 digest: OK
    Payload SHA256 digest: OK
    V3 RSA/SHA256 Signature, key ID 4bf05f46f6e74bf5: NOKEY
    MD5 digest: OK



Sorry, I really don't know what I've done to break things.  It was working fine, then a reboot and now it's working less than when I started.
Comment 16 jerome tako 2022-11-15 05:48:56 UTC
Created attachment 862872 [details]
alsa-tools.sh output  14 nov
Comment 17 jerome tako 2022-11-15 05:58:51 UTC
when booting to previous versions in safe mode (eg 6.0.7 and earlier, I also have zero sound function.  I at least used to have bluetooth/headphone jack output. 

Again, my only guess not knowing much is that I must have installed something along with bitwig studio (an audio workstation) that may have broken something, but I don't know how to check for that.  I DID have working audio post-installation of bitwig though.
Comment 18 Takashi Iwai 2022-11-15 06:24:21 UTC
Did you try to remove the modprobe.d config you've added?  The config disables the mic input and something else might happen.
Comment 19 jerome tako 2022-11-15 14:14:04 UTC
(In reply to Takashi Iwai from comment #18)
> Did you try to remove the modprobe.d config you've added?  The config
> disables the mic input and something else might happen.

I commented out the two lines you had me post in 90-hda.conf, no change.  Here's the current list of that folder.

jerome@koti:/etc/modprobe.d> ls
50-broadcom-wl-blacklist.conf  90-hda.conf  blacklist.conf  sof.conf

The sof.conf file only has one line : "options snd slots=snd_soc_skl_hda_dsp"
Comment 20 jerome tako 2022-11-15 14:19:14 UTC
(to clarify, I also tried removing the file from the directory, no change.  I also tried commenting out the sof.conf file, no change).
Comment 21 Takashi Iwai 2022-11-15 17:11:59 UTC
I have no idea what went wrong.  The change in the kernel is very unlikely the culprit; you can try to boot with the previous working kernel for verification, too.

Some application or sound backend configuration might be broken by some reason.  You can try to clear the data / cache in ~/.config or ~/.local or whatever...

And, you can try to create a new user and check whether the audio is broken there as well.  If another user account works, it must be some user-specific setup.

In anyway, the fix patch has been submitted to the upstream and now pushed to stable branch.  It'll be included to TW kernel eventually later.
Comment 22 jerome tako 2022-11-15 19:10:21 UTC
(In reply to Takashi Iwai from comment #21)
> I have no idea what went wrong.  The change in the kernel is very unlikely
> the culprit; you can try to boot with the previous working kernel for
> verification, too.
> 
> Some application or sound backend configuration might be broken by some
> reason.  You can try to clear the data / cache in ~/.config or ~/.local or
> whatever...
> 
> And, you can try to create a new user and check whether the audio is broken
> there as well.  If another user account works, it must be some user-specific
> setup.
> 
> In anyway, the fix patch has been submitted to the upstream and now pushed
> to stable branch.  It'll be included to TW kernel eventually later.

Meaning, when it's kernel 6.0.9-1 or something similar, this patch will already be present and shouldn't require anything to be done on my end?  

Is it possible that I installed your kernel and broke it when running zypper up or zypper dup afterwards?

I'd like to try reinstalling that kernel you linked here, but is it no longer functional?
Comment 23 Takashi Iwai 2022-11-16 06:27:47 UTC
(In reply to jerome tako from comment #22)
> (In reply to Takashi Iwai from comment #21)
> > I have no idea what went wrong.  The change in the kernel is very unlikely
> > the culprit; you can try to boot with the previous working kernel for
> > verification, too.
> > 
> > Some application or sound backend configuration might be broken by some
> > reason.  You can try to clear the data / cache in ~/.config or ~/.local or
> > whatever...
> > 
> > And, you can try to create a new user and check whether the audio is broken
> > there as well.  If another user account works, it must be some user-specific
> > setup.
> > 
> > In anyway, the fix patch has been submitted to the upstream and now pushed
> > to stable branch.  It'll be included to TW kernel eventually later.
> 
> Meaning, when it's kernel 6.0.9-1 or something similar, this patch will
> already be present and shouldn't require anything to be done on my end?  

In theory yes.  Not sure which kernel version will be, but check the rpm changelog.

> Is it possible that I installed your kernel and broke it when running zypper
> up or zypper dup afterwards?

Possible, but I doubt it.  The instance itself appears, and the quirk should be only about the speaker.  I guess rather some mixer setup was screwed up or the application issue.
Comment 24 jerome tako 2022-11-16 06:59:33 UTC
Okay, so rollbacks didn't work (I may not have set them up right though).

Live USB, after running zypper up & zypper dup, and then also creating that 90-hda.conf file, sound was working through speakers and bluetooth but no internal speakers.

Creating a new user from the actual install though, I DID have working sound through the internal speakers again.  headphone and bluetooth sound worked, however the mic did not.   Current kernel is 6.0.8-1.ge5f6cc1-default, tumbleweed 20221114.

I'm leaning towards reinstalling, then going through these instructions, learning to take a proper snapshot, and then retrying bitwig one piece at a time to see what happens.  Is there anything you'd like me to try before doing that?

Given the issues I'm having, if I"m going to reinstall should I perhaps be considering Leap instead of Tumbleweed?
Comment 25 Takashi Iwai 2022-11-16 12:19:10 UTC
If you want to have rather a less frequently updated system, Leap 15.4 might be a good choice, indeed.  But better to verify whether the full hardware feature is supported beforehand with a live image or such.

I pushed the fixes to SLE15-SP4 git branch, so it'll be included in the next kernel update for Leap 15.4 (likely in the next month), too.
Comment 26 jerome tako 2022-11-16 22:33:24 UTC
So, just a waypoint update - reinstalled Gecko KDE Rolling (KDE Tumbleweed), ran "zypper update", and with that alone I have working sound on bluetooth and wired headphones, but no internal audio (as expected).  Kernel is 6.0.8-1-default, and tumbleweed release is 20221115.  I'm going to do some research on how to properly create and restore snapshots before I either replicate the 90-hda.conf file or try the patched kernel (which I may just wait for it to update with 6.0.9-1-default).
Comment 27 jerome tako 2022-11-22 01:03:15 UTC
Hi, I wanted to ask without creating a new bug issue - so, on openSUSE tumbleweed (no longer gecko linux, just standard), version 20221120 with kernel 6.0.8-1-default, I have had sound working just fine through headphones, speakers, and bluetooth, but I don't have a working mic anymore.  I've tried changing the audio settings in KDE's system settings and by using alsamixer, but no luck so far.  I haven't been able to get any mic signals detected at all, in audicty, zoom, or the KDE settings tests.  ANy ideas where to start with this?  Same machine as before, should I rerun alsatools or some other commands?
Comment 28 Takashi Iwai 2022-11-22 06:59:32 UTC
Make sure that you don't have any extra setup for modules.  And if it's really clean, please give alsa-info.sh output again.
Comment 29 jerome tako 2022-11-22 14:37:36 UTC
Created attachment 863043 [details]
alsa-info 21Nov
Comment 30 Takashi Iwai 2022-11-22 14:46:34 UTC
Erm, I asked about the *output* from alsa-info.sh.
Run the script with --no-upload option, and attach the output to Bugzilla.
Comment 31 jerome tako 2022-11-22 15:01:21 UTC
Created attachment 863045 [details]
alsa info output
Comment 32 Takashi Iwai 2022-11-22 15:06:42 UTC
You have this:

!!Modprobe options (Sound related)
!!--------------------------------

snd_intel_dspcfg: dsp_driver=1
snd_hda_intel: model=alc298-samsung-amp

... and that explains.  As already mentioned in comment 7, this makes the system switching to the legacy HD-audio driver, and the built-in mic capability is lost due to that.

Dropping those should bring the mic back, but the speaker might not work with the 6.0.8 kernel yet.  With 6.0.9 kernel, the speaker should work without those changes.
Comment 33 jerome tako 2022-11-22 15:42:15 UTC
(In reply to Takashi Iwai from comment #32)
> You have this:
> 
> !!Modprobe options (Sound related)
> !!--------------------------------
> 
> snd_intel_dspcfg: dsp_driver=1
> snd_hda_intel: model=alc298-samsung-amp
> 
> ... and that explains.  As already mentioned in comment 7, this makes the
> system switching to the legacy HD-audio driver, and the built-in mic
> capability is lost due to that.
> 
> Dropping those should bring the mic back, but the speaker might not work
> with the 6.0.8 kernel yet.  With 6.0.9 kernel, the speaker should work
> without those changes.

Ah, I didn't recall, thanks for your patience.  So, on the OS I'm currently using, I did make that 90-hda.conf file from comment 7, but I have NOT used your patched kernel yet, and I have NOT done any of the steps from the Manjaro tutorial like creating the TO912.sh script.  After reinstalling Tumbleweed I just made that 90-hda.conf file and sound (except mic) worked.

So, if I understand right, by kernel 6.0.9 (which is probably coming in an update or dup any day now), I shouldn't have to worry about manual configuration at all.   In the meantime, if I want to use my mic I should comment out those two lines of 90-hda.conf.  I could theoretically try other options to have everything working at once, like following the manjaro guide, or re-installing your patched kernel, but it sounds like for my experience level I'm better off just being patient for the kernel to update.
Comment 34 Takashi Iwai 2022-11-28 15:09:17 UTC
Yes, the fix should be included in the upcoming kernel.  Check rpm changelog in anyway whether it contains the relevant fix.

I close the bug for now.  If you still have a problem with the (upcoming) update kernel, feel free to reopen.
Comment 46 Swamp Workflow Management 2022-12-16 17:31:56 UTC
SUSE-SU-2022:4504-1: An update that solves 22 vulnerabilities, contains 7 features and has 26 fixes is now available.

Category: security (important)
Bug References: 1065729,1156395,1164051,1184350,1189297,1190256,1193629,1194869,1202341,1203183,1204631,1204636,1204693,1204810,1204850,1205007,1205100,1205111,1205128,1205130,1205149,1205153,1205220,1205331,1205428,1205473,1205514,1205617,1205653,1205744,1205764,1205796,1205882,1205993,1206035,1206036,1206037,1206046,1206047,1206051,1206056,1206057,1206113,1206114,1206147,1206149,1206207,1206273
CVE References: CVE-2022-2602,CVE-2022-3176,CVE-2022-3566,CVE-2022-3567,CVE-2022-3635,CVE-2022-3643,CVE-2022-3707,CVE-2022-3903,CVE-2022-4095,CVE-2022-4129,CVE-2022-4139,CVE-2022-41850,CVE-2022-41858,CVE-2022-42328,CVE-2022-42329,CVE-2022-42895,CVE-2022-42896,CVE-2022-4378,CVE-2022-43945,CVE-2022-45869,CVE-2022-45888,CVE-2022-45934
JIRA References: PED-1573,PED-1706,PED-1936,PED-2684,PED-611,PED-824,PED-849
Sources used:
openSUSE Leap 15.4 (src):    kernel-azure-5.14.21-150400.14.28.1, kernel-source-azure-5.14.21-150400.14.28.1, kernel-syms-azure-5.14.21-150400.14.28.1
SUSE Linux Enterprise Module for Public Cloud 15-SP4 (src):    kernel-azure-5.14.21-150400.14.28.1, kernel-source-azure-5.14.21-150400.14.28.1, kernel-syms-azure-5.14.21-150400.14.28.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
Comment 50 Swamp Workflow Management 2022-12-20 17:41:00 UTC
SUSE-SU-2022:4585-1: An update that solves 22 vulnerabilities, contains 7 features and has 52 fixes is now available.

Category: security (important)
Bug References: 1065729,1156395,1164051,1184350,1189297,1190256,1193629,1194869,1202341,1203183,1203391,1203511,1203960,1204228,1204405,1204414,1204631,1204636,1204693,1204780,1204810,1204850,1205007,1205100,1205111,1205113,1205128,1205130,1205149,1205153,1205220,1205264,1205282,1205331,1205332,1205427,1205428,1205473,1205507,1205514,1205521,1205567,1205616,1205617,1205653,1205671,1205679,1205683,1205700,1205705,1205709,1205711,1205744,1205764,1205796,1205882,1205993,1206035,1206036,1206037,1206045,1206046,1206047,1206048,1206049,1206050,1206051,1206056,1206057,1206113,1206114,1206147,1206149,1206207
CVE References: CVE-2022-2602,CVE-2022-3176,CVE-2022-3566,CVE-2022-3567,CVE-2022-3635,CVE-2022-3643,CVE-2022-3707,CVE-2022-3903,CVE-2022-4095,CVE-2022-4129,CVE-2022-4139,CVE-2022-41850,CVE-2022-41858,CVE-2022-42328,CVE-2022-42329,CVE-2022-42895,CVE-2022-42896,CVE-2022-4378,CVE-2022-43945,CVE-2022-45869,CVE-2022-45888,CVE-2022-45934
JIRA References: PED-1573,PED-1706,PED-1936,PED-2684,PED-611,PED-824,PED-849
Sources used:
openSUSE Leap Micro 5.3 (src):    kernel-default-5.14.21-150400.24.38.1, kernel-default-base-5.14.21-150400.24.38.1.150400.24.13.2
openSUSE Leap 15.4 (src):    dtb-aarch64-5.14.21-150400.24.38.1, kernel-64kb-5.14.21-150400.24.38.1, kernel-debug-5.14.21-150400.24.38.1, kernel-default-5.14.21-150400.24.38.1, kernel-default-base-5.14.21-150400.24.38.1.150400.24.13.2, kernel-docs-5.14.21-150400.24.38.1, kernel-kvmsmall-5.14.21-150400.24.38.1, kernel-obs-build-5.14.21-150400.24.38.1, kernel-obs-qa-5.14.21-150400.24.38.1, kernel-source-5.14.21-150400.24.38.1, kernel-syms-5.14.21-150400.24.38.1, kernel-zfcpdump-5.14.21-150400.24.38.1
SUSE Linux Enterprise Workstation Extension 15-SP4 (src):    kernel-default-5.14.21-150400.24.38.1
SUSE Linux Enterprise Module for Live Patching 15-SP4 (src):    kernel-default-5.14.21-150400.24.38.1, kernel-livepatch-SLE15-SP4_Update_6-1-150400.9.3.2
SUSE Linux Enterprise Module for Legacy Software 15-SP4 (src):    kernel-default-5.14.21-150400.24.38.1
SUSE Linux Enterprise Module for Development Tools 15-SP4 (src):    kernel-docs-5.14.21-150400.24.38.1, kernel-obs-build-5.14.21-150400.24.38.1, kernel-source-5.14.21-150400.24.38.1, kernel-syms-5.14.21-150400.24.38.1
SUSE Linux Enterprise Module for Basesystem 15-SP4 (src):    kernel-64kb-5.14.21-150400.24.38.1, kernel-default-5.14.21-150400.24.38.1, kernel-default-base-5.14.21-150400.24.38.1.150400.24.13.2, kernel-source-5.14.21-150400.24.38.1, kernel-zfcpdump-5.14.21-150400.24.38.1
SUSE Linux Enterprise Micro 5.3 (src):    kernel-default-5.14.21-150400.24.38.1, kernel-default-base-5.14.21-150400.24.38.1.150400.24.13.2
SUSE Linux Enterprise High Availability 15-SP4 (src):    kernel-default-5.14.21-150400.24.38.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
Comment 51 Swamp Workflow Management 2022-12-23 15:25:54 UTC
SUSE-SU-2022:4617-1: An update that solves 96 vulnerabilities, contains 50 features and has 246 fixes is now available.

Category: security (important)
Bug References: 1023051,1032323,1065729,1071995,1152472,1152489,1156395,1164051,1177471,1184350,1185032,1188238,1189297,1189999,1190256,1190497,1190969,1192968,1193629,1194023,1194592,1194869,1194904,1195480,1195917,1196018,1196444,1196616,1196632,1196867,1196869,1197158,1197391,1197659,1197755,1197756,1197757,1197763,1198189,1198410,1198577,1198702,1198971,1199086,1199364,1199515,1199670,1199904,1200015,1200058,1200268,1200288,1200301,1200313,1200431,1200465,1200494,1200544,1200567,1200622,1200644,1200651,1200692,1200788,1200845,1200868,1200869,1200870,1200871,1200872,1200873,1201019,1201308,1201309,1201310,1201361,1201427,1201442,1201455,1201489,1201610,1201675,1201725,1201726,1201768,1201865,1201940,1201941,1201948,1201954,1201956,1201958,1202095,1202096,1202097,1202113,1202131,1202154,1202187,1202262,1202265,1202312,1202341,1202346,1202347,1202385,1202393,1202447,1202471,1202558,1202623,1202636,1202672,1202681,1202685,1202686,1202700,1202710,1202711,1202712,1202713,1202715,1202716,1202757,1202758,1202759,1202761,1202762,1202763,1202764,1202765,1202766,1202767,1202768,1202769,1202770,1202771,1202773,1202774,1202775,1202776,1202778,1202779,1202780,1202781,1202782,1202783,1202822,1202823,1202824,1202860,1202867,1202872,1202874,1202898,1202914,1202960,1202989,1202992,1202993,1203002,1203008,1203036,1203039,1203041,1203063,1203066,1203067,1203098,1203101,1203107,1203116,1203117,1203138,1203139,1203159,1203183,1203197,1203208,1203229,1203263,1203290,1203338,1203360,1203361,1203389,1203391,1203410,1203435,1203505,1203511,1203514,1203552,1203606,1203664,1203693,1203699,1203767,1203769,1203770,1203794,1203798,1203802,1203829,1203893,1203902,1203906,1203908,1203922,1203935,1203939,1203960,1203969,1203987,1203992,1203994,1204017,1204051,1204059,1204060,1204092,1204125,1204132,1204142,1204166,1204168,1204170,1204171,1204183,1204228,1204241,1204289,1204290,1204291,1204292,1204353,1204354,1204355,1204402,1204405,1204413,1204414,1204415,1204417,1204424,1204428,1204431,1204432,1204439,1204470,1204479,1204486,1204498,1204533,1204569,1204574,1204575,1204576,1204619,1204624,1204631,1204635,1204636,1204637,1204646,1204647,1204650,1204653,1204693,1204705,1204719,1204728,1204745,1204753,1204780,1204810,1204850,1204868,1204926,1204933,1204934,1204947,1204957,1204963,1204970,1205007,1205100,1205111,1205113,1205128,1205130,1205149,1205153,1205220,1205257,1205264,1205282,1205313,1205331,1205332,1205427,1205428,1205473,1205496,1205507,1205514,1205521,1205567,1205616,1205617,1205653,1205671,1205679,1205683,1205700,1205705,1205709,1205711,1205744,1205764,1205796,1205882,1205993,1206035,1206036,1206037,1206045,1206046,1206047,1206048,1206049,1206050,1206051,1206056,1206057,1206113,1206114,1206147,1206149,1206207,1206273,1206391
CVE References: CVE-2016-3695,CVE-2020-16119,CVE-2020-36516,CVE-2021-33135,CVE-2021-4037,CVE-2022-1184,CVE-2022-1263,CVE-2022-1882,CVE-2022-20368,CVE-2022-20369,CVE-2022-2153,CVE-2022-2586,CVE-2022-2588,CVE-2022-2602,CVE-2022-26373,CVE-2022-2639,CVE-2022-2663,CVE-2022-28356,CVE-2022-28693,CVE-2022-2873,CVE-2022-28748,CVE-2022-2905,CVE-2022-2938,CVE-2022-2959,CVE-2022-2964,CVE-2022-2977,CVE-2022-2978,CVE-2022-3028,CVE-2022-3078,CVE-2022-3114,CVE-2022-3169,CVE-2022-3176,CVE-2022-3202,CVE-2022-32250,CVE-2022-32296,CVE-2022-3239,CVE-2022-3303,CVE-2022-33981,CVE-2022-3424,CVE-2022-3435,CVE-2022-3521,CVE-2022-3524,CVE-2022-3526,CVE-2022-3535,CVE-2022-3542,CVE-2022-3545,CVE-2022-3565,CVE-2022-3566,CVE-2022-3567,CVE-2022-3577,CVE-2022-3586,CVE-2022-3594,CVE-2022-3619,CVE-2022-3621,CVE-2022-3625,CVE-2022-3628,CVE-2022-3629,CVE-2022-3633,CVE-2022-3635,CVE-2022-3640,CVE-2022-3643,CVE-2022-3646,CVE-2022-3649,CVE-2022-36879,CVE-2022-36946,CVE-2022-3707,CVE-2022-3903,CVE-2022-39188,CVE-2022-39189,CVE-2022-39190,CVE-2022-40476,CVE-2022-40768,CVE-2022-4095,CVE-2022-41218,CVE-2022-4129,CVE-2022-4139,CVE-2022-41674,CVE-2022-41848,CVE-2022-41849,CVE-2022-41850,CVE-2022-41858,CVE-2022-42328,CVE-2022-42329,CVE-2022-42703,CVE-2022-42719,CVE-2022-42720,CVE-2022-42721,CVE-2022-42722,CVE-2022-42895,CVE-2022-42896,CVE-2022-43750,CVE-2022-4378,CVE-2022-43945,CVE-2022-45869,CVE-2022-45888,CVE-2022-45934
JIRA References: PED-1082,PED-1084,PED-1085,PED-1096,PED-1211,PED-1573,PED-1649,PED-1706,PED-1936,PED-2684,PED-387,PED-529,PED-611,PED-634,PED-652,PED-664,PED-676,PED-678,PED-679,PED-682,PED-688,PED-707,PED-720,PED-729,PED-732,PED-755,PED-763,PED-813,PED-817,PED-822,PED-824,PED-825,PED-833,PED-842,PED-846,PED-849,PED-850,PED-851,PED-856,PED-857,SLE-13847,SLE-18130,SLE-19359,SLE-19924,SLE-20183,SLE-23766,SLE-24572,SLE-24682,SLE-24814,SLE-9246
Sources used:
openSUSE Leap Micro 5.3 (src):    kernel-rt-5.14.21-150400.15.5.1
openSUSE Leap 15.4 (src):    kernel-rt-5.14.21-150400.15.5.1, kernel-rt_debug-5.14.21-150400.15.5.1, kernel-source-rt-5.14.21-150400.15.5.1, kernel-syms-rt-5.14.21-150400.15.5.1
SUSE Linux Enterprise Module for Realtime 15-SP4 (src):    kernel-rt-5.14.21-150400.15.5.1, kernel-rt_debug-5.14.21-150400.15.5.1, kernel-source-rt-5.14.21-150400.15.5.1, kernel-syms-rt-5.14.21-150400.15.5.1
SUSE Linux Enterprise Module for Live Patching 15-SP4 (src):    kernel-livepatch-SLE15-SP4-RT_Update_1-1-150400.1.3.1
SUSE Linux Enterprise Micro 5.3 (src):    kernel-rt-5.14.21-150400.15.5.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.