A few thoughts...  Just based on my work before and the few people I
helped later, in my experience Samsung reuses as much as possible in
similar models and I don't think the laptops are that much different (if
any) with regard to sound.  So I don't think its option 1.  Option 2 is
a possibility and I would still consider a fresh install. I don't know
about spoofing, but if you know the quirk you think is missing you can
pretty easily just create a customized kernel that applies it.  I did
that originally on the Ion, again based on suggestions from Mike Polzup,
before I actually went down the qemu path.  It was needed back then just
to get the headphones working on the Ion, but I believe that issue is
now resolved in Ubunutu.  Also, for what its worth, your brightness fix
worked perfectly, so there is definitely some common aspects between
these machines.

Its been a couple of years, but basically my qemu approach was 
 -Install basic qemu
 -create a new windows virtual machine
 -Place a sound file on the desktop in the WM and ensure it played
 -Create the modified qemu version to get logging
 -Launch the previously verified VM 
 -Play the sound, noting where in the log it was playing
 -Record the logging
 -Translate the verb formats
 -Play back sections to find some sort of sound
 -Reduce the verbs as much as possible after getting a section that made noise

I never needed to install the windows realtek driver as a separate step, the 
qemu vms always had working sound just with a default install of windows.  It 
seemed like it would be easy once I got the modified qemu working, but it 
wasn't.  Honestly if we hadn't been on covid lockdown I probably would have not 
had the time to finish it.  I assumed, incorrectly, that if I just recorded the 
verbs during boot or the verbs up to the point where I heard sound on the VM it 
would be easy to just replay that bit and hear something, but that never really 
worked smoothly.  I just assumed I did it wrong and it didn't work, but later 
in desperation I started just taking chunks and trying them and I happened to 
hit a working segment. 
 I believe that was on Sept 12, thus the name of the script.  I never really 
figured out why the bigger chunks didn't work.

Mike gave me the basic concept and pointed me at these two approaches
for logging.  He seems to have dropped away right after that, but his
approach was absolutely correct.  Because I didn't think it was working
originally, I made both logging approaches work, but ultimately I used
the bsd style approach for the final work because i found the output
easier to work with as you can just copy and paste from stdout and the
verbs needed less modification:

https://jcs.org/2018/11/12/vfio

https://github.com/Conmanx360/QemuHDADump/wiki/Setup-and-usage-of-the-
program#start-of-content


If it helps, here are my very incomplete notes on making the modified qemu.  I 
didn't write down what I changed in common.c, but I believe it was inline with 
the article...


Manual Install Qemu
        
        sudo apt-get build-dep qemu
        
        Download source https://www.qemu.org/download/#source
        tar -xvf {insert-qemu-version-here}.tar.xz
        go into folder
        
        modify common.c in hw/vfio (to output the formatted tracing)
        
        In the qemu source, you'll need to edit 
                the file pci.c located in the hw/vfio folder. Edit the value: 
                
                DEFINE_PROP_UINT32("x-intx-mmap-timeout-ms", VFIOPCIDevice, 
intx.mmap_timeout, 1100)
                        From 1100 to 0 to prevent mmap'ing, and then also edit:
                DEFINE_PROP_BOOL("x-no-mmap", VFIOPCIDevice, vbasedev.no_mmap, 
false)
                        From false to true to prevent it completely.

        ./configure --enable-trace-backends=log --target-list=x86_64-softmmu
        make -j9
        
        sudo make install

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851518

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---------------

  Manufacturer:      SAMSUNG ELECTRONICS CO., LTD.
  Product Name:      950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:      SAMSUNG ELECTRONICS CO., LTD.
  Board Name:        NP950SBE-K01US

  
  !!Kernel Information
  !!------------------

  Kernel release:    5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:      x86_64
  Processor:         x86_64
  SMP Enabled:       Yes


  !!ALSA Version
  !!------------

  Driver version:     k5.3.0-19-generic
  Library version:    1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!-------------------

  snd_hda_intel

  
  !!Sound Servers on this system
  !!----------------------------

  Pulseaudio:
        Installed - Yes (/usr/bin/pulseaudio)
        Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-----------------------------

   0 [PCH            ]: HDA-Intel - HDA Intel PCH
                        HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--------------------------------------

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!-------------------------------------------------------

  00:1f.3 0401: 8086:9dc8 (rev 11)
          DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---------------------------
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
      rates [0x60]: 44100 48000
      bits [0xe]: 16 20 24
      formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
    Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
    Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
    IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
    IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
    IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
    IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
    IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
    IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
    IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
    IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
    Control: name="Headphone Playback Volume", index=0, device=0
      ControlAmp: chs=3, dir=Out, idx=0, ofs=0
    Device: name="ALC298 Analog", type="Audio", device=0
    Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
    Amp-Out vals:  [0x00 0x00]
    Converter: stream=1, channel=0
    PCM:
      rates [0x60]: 44100 48000
      bits [0xe]: 16 20 24
      formats [0x1]: PCM
    Power states:  D0 D1 D2 D3 EPSS
    Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
    Control: name="Speaker Playback Volume", index=0, device=0
      ControlAmp: chs=3, dir=Out, idx=0, ofs=0
    Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
    Amp-Out vals:  [0x7f 0x7f]
    Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  martin     1383 F.... pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 06:20:08 2019
  InstallationDate: Installed on 2019-11-03 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  martin     1383 F.... pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RES.075.190529.SP
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP950SBE-K01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9849A0Q-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RES.075.190529.SP:bd05/29/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn950SBE/951SBE:pvrP06RES:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP950SBE-K01US:rvrSGL9849A0Q-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 950SBE/951SBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PRES
  dmi.product.version: P06RES
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-11-05T23:13:55.854413

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1851518/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to