@PowerKiKi
PowerKiKi, I had to reload my pc for another project, and after
reloading I found that same lack of stickiness... Not wanting to go
backwards, I felt I had to chase down the full fix. This should fix
your issue (caused by pulse) if you want to skip the background audio
file...I also
@kasper93
That is great news, sounds like the same fix will work for multiple
models then!
--
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,
@kasper93
That is good to know. Makes sense that the CORB values might differ
somewhat. The ION has the AKG smart amp and dolby what not, so my CORB
sequence is likely tuned for that combination of items. It actually
sounds really good for a laptop. I think there may already be a fix out
@ironincoder
I highlighted the 0x20 block just to explain how the data is structured.
You need to run the full script (TO912.sh) with all 358 verbs to hear
sound.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@PowerKiKi
That is very odd, mine lasts for hours and hours.
I wouldn't think ubuntu and xbuntu would be that different with regard
to audio hardware mgmt, but one guess off the top of my head is that
before I found this thread I turned off power mgmt for snd_hda_intel to
try to get the
@PowerKiKi
@terrymagnusdrever
@gannon1
Just to document this for anyone else that might benefit, attached is
the final script I created. I reduced the previous list further from
788 to 358 verbs. There may be a few extra ones left, but probably not
many based on my testing, as removing more
@PowerKiKi
Yes, this is just a temporary step until I finish minimizing the verbs.
I was hoping it would be as easy as just finding the single command or
two in the group of 788, but it appears to be a longer combination of
sequences, so will take just a bit more tinkering to isolate. I will
get
@gannon1 @PowerKiKi
Mike, I never heard back from Jaroslav (I suspect he is pretty busy),
and my consulting work is very slow with the pandemic so I just
continued to work on it. Your concept is spot on. Thank you for all
the wisdom and thoughtful guidance. I am happy to report, after much
@gannon1
Sure. I found I am not getting the consistent output from the new
logging that I expected, so I want to try a couple of things this
weekend to understand it better. Then I will type up a brief summary
and post it in the other thread...
--
You received this bug notification because
@gannon1
Mike, after reading more on the patch links you sent me before, it
occurred to me I might have an easier way to test the 944 while you
create the proper patch. Namely, I followed the same procedure as
before with the headphone patch, but right before I made the new custom
kernel I just
conf file...
** Attachment added: "conf file"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5404851/+files/alc298-944-early-patch.conf
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@gannon1
Using the same steps we tried before, no luck with early patching.
Early patching didn't work on the Ion for headphones either, so could be
something with this laptop. Attached are the fw and conf files if any
else wants to try it... just change the id value to match your sound
@gannon1
Thanks. You are correct that HDA Verbs were not successful. Assuming I
did it correctly, I already wrote a script to produce a script that had
each of the 944 verbs and it did not turn on the sound. I tried that
yesterday, but failed to mention it.
If you find that a patch with the
@gannon1
Mike, depending on your answers to my many questions from today, if the
only way we know to proceed is to build and test a patch, could you help
with building the patch (or at least the basic framework of the patch so
I can just plug in the CORB values)? I used the attached spreadsheet
@gannon1
Some thoughts based on what I did today. I did make a recording (twice
to make sure I didn't do it poorly) of the VM boot process. So from the
time the VM initializes until you first see the win 10 desktop. To my
surprise there is only 1 single CORB command during that process. It is
@gannon1
I am also going to create a new recording today that is just the VM
booting. It seems to me that our problem may not be the audio device
itself, but the AKG smart amp not turning on. I am not confident that
the disable and re-enable I was doing of the realtek audio device in
windows
@gannon1
Not sure what happened to the enable file, here it is again...
Anyway, on your other comment, I assume the Verb ID and Payload you
mention would be the control and param values from my logging?
Do you know if that is a way to do this troubleshooting with the hda
verb approach as
@gannon1
disable file
** Attachment added: "Disable"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5404232/+files/Disable
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@gannon1
enable file...
--
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
@gannon1
I am tracking what your saying concept wise. Here is a summary of what
I did today, in part just to help me clarify my thoughts and in part so
you can maybe correct any gaps and save me troubleshooting time :).
- I have gone through all the documents in the wiki for QemuHDADump and
as
@gannon1
Mike, I didn't have luck with the exact steps in comment 15, but the
wiki written by Conner was very solid. I had to work through a couple
small differences on my system, but now I have a working QEMU VM where
the realtek hardware is recognized and the speakers actually work! I
worked
@PowerKiKi
Sure, it returns the following :
NP930XCJ-K01US
In the US, there are currently just two models of the Ion, my model and
the 15" model - NP950XCJ-K01US. The specs say both models have the same audio,
so you could probably include that model as well, unless you need someone to
@gannon1
Mike, I must be missing a step, but I installed qemu and virtual machine
manager successfully, then found a win 10 iso and installed and
activated windows in a new VM However, when I run that driver you
mentioned in comment 19, it runs without error, but my vm still doesn't
seem to
@PowerKiKi
I am happy to share the steps I took for information purposes, with the
understanding that I can't take any responsibility on whether they will
work for you or not. Performing anything like this on your daily
required PC is definitely a risk. Also, your on Xbuntu, so not sure if
that
@gannon1
I follow the concept. I tried first using vmware workstation, mostly
just cause I already had it installed for another purpose, but
unfortunately no luck there. Vmware abstracts the underlying hardware
and windows doesn't even see it as a realtek audio device. I also
shared the
@gannon1
I am still reading through all the links, but I think I get the basic
concept. Like you I don't readily have a working windows VM to trace,
but I will see if I can set something up. Ill let you know if I have
any luck
--
You received this bug notification because you are a member
@gannon1
OK, had some small struggles with grub on efi, but yes, once I made a
completely new kernel version with just this patch then it did work and
does survive reboots and source changes, etc. So at least until a new
kernel comes out I am set :)
Is there anything I can do to help with the
@gannon1
OK, so :
- downloaded kernel source
- applied patch
- ran make to create new debs
- activated new custom kernel
- added "options snd-hda-intel model=alc298-samsung-headphone" to
alsa-base.conf
- rebooted
- used "uname -r" to ensure the new custom kernel was
Yea, sorry. I was working off an apt-get version of the kernel source, then
after posting, I noticed you were using git. I have downloaded from the source
from git and applied the patch successfully. The new custom kernel is now in
the make process. I will update once it finishes and I can
@gannon1
I also tried :
patch -p1 < ~/Desktop/0001-ALSA-hda-realtek-Add-model-alc298-samsung-
headphone.patch
And received the same error...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
OK, While I would prefer to wait until the patch lands, for an ubuntu LTS that
can take a while, so I tried to do it manually. I downloaded the kernel src,
but I am having trouble applying the patch. I am using the command :
patch -i ~/Desktop/0001-ALSA-hda-realtek-Add-model-alc298-samsung-
@gannon1
Sure. I tried just that single character change first. No change after
reboot, i.e. still had to issue the manual command. If I use the manual
command with either 0x5 or 0xc5 it works perfectly in both cases. Just
for good measure I also tried adding back the model section too, but
@gannon1 Thanks for the reply. Perhaps I am missing something because
it seems like it should work, but I have not had any luck with the
method described by ironincoder. Just to be sure I did it again from
the start using the following steps (perhaps I just didn't understand
and missed a
I have the 13 inch Ion with the intel built in gpu. I am also running standard
Ubuntu and not Xbuntu. I have never had the system lock up or freeze on any
occasion and I use it for at least 10 hours a day. My keyboard lights have
also always worked perfectly from the start. In fact, the
I have the same computer and issue as PowerKiKi... the new Samsung Ion running
ubuntu 20.04.
I have found that I can make the headset jack work temporarily if I
issue this command :
sudo hda-verb /dev/snd/hwC0D0 0x1a SET_PIN_WIDGET_CONTROL 0x5
But it only lasts until the sound subsystem goes
35 matches
Mail list logo
