1)  I am so glad the brightness fix worked for you!  At least I can feel
like I've accomplished something ;)

2)  Thanks so much for your detailed qemu information.  I think I am
going to tackle that next, and it should help (especially since
compiling the pre-customized qemu was giving me trouble...your method
sounds better, cause I can download what should be the latest qemu, and
just patch it before compiling).


So, an update:  A bit of very good news and very bad news.  I was gearing up to 
do qemu last night, but decided to try "one last thing".  I came across this 
post here:
    https://bugzilla.kernel.org/show_bug.cgi?id=216023

In it, someone else with a 950QED had done the whole Qemu thing, and
came up with a different set of verbs.  Very long (3500 verbs), not cut
down very well.  So I decided to try them.  Boom, sound! Finally (It
scared the hell out of me, after all this trying and failing).  But:
Sound in the left speaker, in the right speaker extremely loud static.
Rebooted, same thing.  Then, while the static was playing, I went to
write myself a note about the results, and must have waited too long,
because in the meantime, I smelled something very faint coming from the
computer, then the static volume starts reducing slowly bit by bit to
nothing.  And from that point on, no sound in the right speaker in
linux.  In windows, even after shutdown, very faint volume from the
right (It's almost like a blew an amp or something?  ..maybe there is an
amplified speaker that linux is calling, that's dead, and windows is
calling the unamplified one, hence the quiet sound? ...but i don't know
how this stuff works.  Also, in certain configurations, I can in linux
only get that loud static on the right to pop in for 1sec before going
quiet again (by re-running the verbs)... so that cuts against the theory
that I blew something, even though windows sound is still permanently
affected, very weird)

So my computer is still within the return window for a few days, but I
don't wanna get a new one and just repeat the same mistake.  It's
possible it's not that anything blew, but just i'm still missing some
weird initialization/reset verbs or something?  Hence why I think I will
still see what happens on qemu, on a fresh windows install (and even
better that you say it will use a different generic sound driver, so i
can see what happens).  This whole thing has made me realize, as I boot
into linux/windows,reboot, etc., that the soundcard holds state between
reboots much more than I ever thought possible I.e., once the verbs are
sent, they don't need to be sent again unless I launch windows, or
shutdown completely.  And all this seems independent of whether I do
those other steps (alsa.conf, etc.) or not, it just seems about getting
those magic initialization verbs.

** Bug watch added: Linux Kernel Bug Tracker #216023
   https://bugzilla.kernel.org/show_bug.cgi?id=216023

-- 
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