Hi Eurelien,
any chance you might write a simplet step by step toturial how to apply your
patch?
Thanks a lot.
Marius
--
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:
Hi All,
I'm sorry i didn't found time to send my work but now it's done.
Please find the ALC298 python scripts and the brightness management of the
Samsung galaxy book 12 on my github:
https://github.com/Teetoow/SamsungGalaxyBook12
I'm not sure it will solve problem for other ALC298 soundcards
Hi All,
Running the xiaomi notebook x15 pro here. Which comes with 4 speakers.
The front firing sound bad, like 25% and downward do not make any sound.
Anyone can help me out where to start?
hdajackretask does not work / save upon reboot. Kinda struggeling with
this one here...
@titou829 -
That would be great, thank you! As of now, I've used the script/verbs
from this link (I think that's where I got them):
https://github.com/thesofproject/linux/issues/4055 . And that managed
to get my sound working, but with the right side at lower volume, and I
believe ever lesser
Hi all,
I finally got time to work on the soundcard of the Galaxy Book 12 (SM-W720). I
finally found the solution in order to get it working under linux after a lot
of work on the verbs I got from qemu two years ago.
I already can have sound from a script I'll send to you this weekend.
I'm
Great news!!! Got the new machine. Avoided booting into windows, ever,
just in case. Executed your steps 1 through 8 (except for the
default.pa part... I wasn't sure if that was crucial, and figured I'd
save it until it seemed needed). Boot fresh machine, no sound. Apply
the verbs - The other
Yes, thank you for the brightness fix.
If it helps, I did remember the changes to make to the common.c file for
logging. In that bsd article you can ignore most of the text, but
somewhere in the middleish there is a hyper link that says something
like my hack. If you click on it, it shows you
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
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
Thank you for your latest script. I did a diff, crossing my fingers to
find a difference, but it was only your commented out line starting
pulse audio... so they're the same :/
And thanks for the pacmd output. At first when I compared yours and
mine, they were the same... except my sinks, etc.
Latest TO912.sh
** Attachment added: "TO912.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5630636/+files/TO912.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
That is odd. If its an option, you might consider a fresh install of
22.04 and then just the few steps. Its possible something else was
changed or didn't reset fully as expected, but I know a full reload can
be a ton of work and disruption. I don't know which script version they
had in the
Ok... So, I had previously done those steps 1 through 8. On top of those
however, since I had followed the instructions from that link
(https://forum.manjaro.org/t/howto-set-up-the-audio-card-in-samsung-galaxy-book/37090),
I had also added on top:
options snd slots=snd_soc_skl_hda_dsp
Thanks, I had tried a couple of things on the brightness, but it doesn't really
bother me that much and I kind of forgot about it. I will try your approach.
So full disclaimer, I am usually an Angular architect and not a linux
admin so try at your own risk, etc., etc., but here are my thoughts
Hi jhubuntu20,
First, hopefully I can do you a solid and tell you how I fixed my
brightness control at least (cause mine is a Galaxy Book2 Pro also, but
with the ARC graphics). What worked for me was:
-Created /etc/modprobe.d/i915.conf with
options i915 enable_dpcd_backlight=3
-
Hi Drew,
Since creating the TO912.sh script I have also upgraded to a GalaxyBook2
Pro (NP930XED) running 22.04 and the script was required (i.e. the
latest kernels don't automatically fix issue), but the script continues
to work fine for me on both headphones are speakers. Personally I would
Understood. I'd be super happy however if I could just get a manual
script to work at least, and then I could call it a day...anything to
just get any sound. But I've had no luck with that method, it seems to
have no effect. (Assuming we are talking about the TO912.sh script. I
tried to go
It's been a while. Since then I upgraded to Xubuntu 22.04 (not fresh
install), and I am running kernel 5.15.0, which is supposed to contains
my patch according to tags on
https://github.com/torvalds/linux/commit/8bcea6cb2cbc1f749e574954569323dec5e2920e.
So I expect the issue to be solved, but
FYI - I have the NP950XEE (GalaxyBook2 Pro w/ Intel ARC graphics), have
been struggling with the same problem and trying to fix for days now. I
have perfect sound in headphones, no sound on speakers. I've
implemented every fix discussed here, and haven't seen one single
effect. I'm running
@PowerKiki
I'm really sorry for the delay. My computer crashed and I needed to repair it..
I just finished...
After a year I reinstalled the latest kernel but the problem seems to persist.
Here is the result of the alsa-info.sh:
Thanks for the news. I've been listening to a muted mp3 for two years
now :-P
I am looking forward to Ubuntu 22.04 that should bring us the patched
kernel we need...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@PowerKiKi
The to912 script needs to be re-run after the audio sleeps. I have been running
it manually for two years. Yesterday, I wrote a script that runs automatically
after booting. It is much more convenient now. The script snippet:
LAST=0
while true; do
#pacmd list-sink-inputs | grep
Aurélien, first thing to do is probably `sudo alsa-info --upload` to get
and upload all your details. Then, we might compare it to mine: http
://alsa-project.org/db/?f=f13c46c58bba7ed21035e65230899b18419cd337
--
You received this bug notification because you are a member of Kernel
Packages,
Hi,
I have a Samsung galaxy book and encounter the same problem with my ALC298
sound card. I tried everything you did but it didn't work with mine. In fact I
even cannot hear something with the earphones.
I also tried to check the verbs used under windows (throught qemu) and it seems
they are
I will ping you guys also here, since it seems to be more popular bug
report. I've send a patch for speaker amp. You can find it here
https://bugzilla.kernel.org/show_bug.cgi?id=207423#c40 and test if you'd
like.
--
You received this bug notification because you are a member of Kernel
Packages,
** Also affects: linux
Importance: Undecided
Status: New
--
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
I don't know.
This is none Realtek AMP.
--
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,
Kailang, do you know how to power up the AMP?
--
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
Oh, one last thing, to hear the mettalic audio, simply launch a youtube
video in Chrome (not Firefox)
--
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,
And to fix that metallic sound with the mainline kernel, you will
probably need to perform steps 4 & 5 from my guide
(https://forum.manjaro.org/t/guide-how-to-set-up-the-audio-card-in-
samsung-galaxy-book/37090) and then reboot.
--
You received this bug notification because you are a member of
Yes, if you check alsa-info (here is my output:
http://alsa-project.org/db/?f=608b0585907cc0f959ebc2528e771f5260685382), you
will find it:
!!Loaded ALSA modules
!!---
snd_soc_skl_hda_dsp
snd_soc_skl_hda_dsp ALSAA module basically loads snd_sof_pci and that's why you
don't
@draamses
I am glad to hear it works on the flex. Thanks for the kind words, but
Mike Pozulp deserves most of the credit. He seems to have disappeared
here, but he had the key process for how to do it. For what its worth,
I don't recognize snd_soc_skl_hda_dsp (of course I am not using
@jhubuntu20
I am pretty sure this is caused by snd_hda_intel being loaded instead of
snd_soc_skl_hda_dsp
When I tested ubuntu kernel, the sound was clean and they all ladded
snd_soc_skl_hda_dsp, however any mainline kernel produced metallic sound and
those load snd_hda_intel
I have created a
@kaihengfeng
Yes, my model is included :
SND_PCI_QUIRK(0x144d, 0xc18a, "Samsung Galaxy Book Ion (NP930XCJ-
K01US)", ALC298_FIXUP_SAMSUNG_HEADPHONE_VERY_QUIET),
However, the quirk called "ALC298_FIXUP_SAMSUNG_HEADPHONE_VERY_QUIET" is
just the fix for the headphone jack only. So yes, that fix is
@draamses
I never encountered the metallic sound on my ion, so I am probably not
much help on that one. I do recall reading about it when I was
researching the speaker issue, so I do agree it is a separate issue. If
you google around a bit, it seems like there was a separate fix for
metallic
Yes, it is.
For some reason linux loads snd_hda_intel instead of snd_soc_skl_hda_dsp ALSA
module and this causes the metallic audio.
How can I get it to load snd_soc_skl_hda_dsp ALSA module?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Please check if your system id is included:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/pci/hda/patch_realtek.c#n7917
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
To answer my own question - I suppose the ubuntu kernels are more optimized and
have multiple fixes and drivers that the mainline/upstream kernels do not and
that's why I get the metallic audio...
I wonder what was fixed in Ubuntu's kernel to make this issue go away.
--
You received this bug
Decided to do more trial and error tests.
I tried multiple amd64 kerels from
https://kernel.ubuntu.com/~kernel-ppa/mainline/
It seems that all kernels I tried produce metallic audio, I believe you can
easily reproduce this by trying them.
Even the 5.4.52-050452.202007160732 kernel produced
Re: Metallic audio
Upgraded the kernel from 5.4.0-52 to 5.4.72 as I have on Manjaro.
Result: Metallic audio.
Booted again with 5.4.0-52
Result: Clean audio
Conclusion: quite likely a kernel issue.
How can we get this reported and fixed?
--
You received this bug notification because you are a
PLease disregard my last comment (#112). It happens in FF too, but on
other websites.
--
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,
One possibly important finding:
The metallic sound happens with Chrome but not with Firefox, running the same
youtube video.
I googled and found that chrome is using ALSA, while FF is using Pulseaudio.
Maybe that's the issue.
Got no idea how to solve this tho.
--
You received this bug
Re: Metallic sound
Forgot to mention - it seems to happen only on the speakers, not on the
headphones.
--
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,
Yeah, thanks a lot, it actually does work on the FLEX :)
I misread post #90 and tried only the verbs listed instead of the entire script.
Using the full attached script it works fine now, on MInt 20 (Kernel 5.4.0-52)
I tried the same verbs on the latest Manjaro, slightly newer Kernel 5.4.72. It
Just FYI for anyone interested, The daemon is now working again. Looks like
the last update of systemd caused the issue. Through another forum I found I
was able to fix it by just running "sudo apt reinstall systemd" (which also
fixed the broken battery indicator).
--
You received this bug
@draamses
I am surprised to hear it doesn't work, at least manually, on the flex.
I obviously don't work for samsung and don't know the hardware internal
details, but there is nothing in the script that is known to be
explicitly model specific. I am also just running a standard ubuntu
kernel now
@PowerKiKi
@terrymagnusdrever
@gannon1
I have the same problem on my Galaxy Book Flex 2020 (system id 0x144dc189).
The new kernel helped the earphone work, but there is still no sound from the
speakers, even when I am trying the verbs and daemon suggested here. I assume
these work for the ION,
@kaihengfeng
Can you describe what fix was implemented? I updated to kernel
5.4.0-52-generic in Ubuntu 20.04 and it is not fixed. I still must run
the script. Also, something has regressed with the latest updates
because now I have to manually run "pulseaudio --start" after booting to
get it
This issue should be fixed after 5.4.0-49.53.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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:
@duke-c
> It must be that a certain detail has not been handled properly. Do you
know what it is?
Nothing specific that I can think off, I'm running 5.8 kernel so there
might be that, depending what you are running.
> I have to put this line in /etc/modprobe.d/alsa-base.conf, without it,
the
@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
I still have the metallic sound issue, after did 3 steps you list in
#99. (No problem without pulseaudio.)
It must be that a certain detail has not been handled properly. Do you
know what it is?
I have to put this line in /etc/modprobe.d/alsa-base.conf, without it, the
sound card
@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,
duh, in step 2 /usr/share/alsa of course.
--
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
Just for reference to fix my remaining audio issues I did:
1. Compiled latest PulseAudio
(https://gitlab.freedesktop.org/pulseaudio/pulseaudio)
2. Copied latest ucm2 configs to /usr/share/local
(https://github.com/alsa-project/alsa-ucm-conf)
3. Enabled SOF driver
echo "options
@jhubuntu20
> The ION has the AKG smart amp and dolby what not
Same here actually, I believe Samsung used the same hardware.
> I think there may already be a fix out there for the metallic sound
issue
Yeah, my bad. I did quick test and start typing response, sorry. It is
PulseAudio that mess
@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
Also an idea for understanding what specific verbs are responsible for.
In Samsung Settings thingy there is a audio profile selection, we could
diff verbs set between those profiles.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I tested your script on my 930SBE. It sort of worked, I indeed got
output on speakers, but the quality was terrible, sound was metallic and
tiny. Generally looks like we are setting AMP coefficients and those
vary between models. I will set up and dump verbs for my machine when I
get some free
@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.
I got a chance to get the pro 9 back for a brief moment and run the CORB
script from @John, but that 0x20 block did not do it for this sub-model
(0x144dc169).
--
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
This new script also works for me, thanks.
However, with both versions of the script sound will stop working after
~30 seconds of inactivity. So it is not "sticky" in my case. An easy
workaround is to play an audio file on infinite loop with volume down to
zero. This will keep the speakers
@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
This is great news !
I just tried your script, while a song was already playing, and I
instantly got sound on my speakers (both left and right).
While the script is running I can hear each side coming on. First left,
then right.
I also noticed that if switching to my bluetooth headphones, the
@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
@John Hoff
> Namely, I followed the same procedure as before with the headphone
patch, but right before I made the new custom kernel I just added the
new candidate CORB values to the new patch_realtek.c file in my new
custom header... so basically just modified the samsung headphone very
quiet
@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
@John Hoff
> 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)?
Absolutely. I'll write a
@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
After changing alsa-base.config according to #6, headphones are working in
950XBE.
Attaching alsa-info with model=mono-speakers and headphones connected.
** Attachment added: "alsa-info in 950XBE"
I have similar problems in 950XBE.
I tried
$sudo hda-verb /dev/snd/hwC0D0 0x1a SET_PIN_WIDGET_CONTROL 0xc5
but there's still no sound from the headphone.
Are the pins different for Samsung Notebook 9 Always?
!!DMI Information
!!---
Manufacturer: SAMSUNG ELECTRONICS CO., LTD.
@John Hoff
> enable file...
Can you re-attach? I don't see it.
> Anyway, thoughts? Do you have any more clarity on how to replay the
CORB commands?
Take a look at this patch [1]. Use the CORB command recording to write a
similar patch. It will contain a 2034-entry long array of hda_verb
@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
@Mike, thanks for your help! I was able to submit the patch. Easier than
I thought :-)
FYI it ended up there: https://lkml.org/lkml/2020/8/24/977
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@PowerKiKi
Wondeful, thank you for clarifying. =)
> I'd love to submit the patch, but I've never done that before. I'll
see if I can figure it out later tonight...
That would be great - go for it! Nick Desaulniers has a good blog post
which describes how to submit a patch [1]. I read it and
@Mike Pozulp, it is correct that the model name referred in the merged
patch is incorrect. It refers to my model.
For future reference here is my alsa-info.sh: http://alsa-
project.org/db/?f=f13c46c58bba7ed21035e65230899b18419cd337
Where we can see:
Board Name:NT950XCJ-X716A
...
@John Hoff
John, great work!
> Now what? I am not sure what to do with any of this data
Now the hard part. Here's what I think is going on:
The windows driver running in the VM controls the audio codec. How?
According to section 4.4 of the Intel HDA Spec [1], the driver writes to
a
@John Hoff @PowerKiKi
Is "Samsung Galaxy Book Ion (NT950XCJ-X716A)" not a correct description
of John's laptop? If not, it doesn't matter to snd_hda_intel which only
looks at the subsystem id (0x144dc18a), but it's worth changing it for
the benefit of any humans who read the kernel code.
I use
@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
John, thank your for your help. I was able to build and run a patched
kernel. And even get the sound back, but only after a modification in
the patch. I noticed Mike created the patch for your machine, but named
it "Samsung Galaxy Book Ion (NT950XCJ-X716A)". This is incorrect because
@John Hoff
> Is there something I need to do to allow pass through of the
underlying hardware?
Yes. It's called vfio passthrough. Can you try doing what I did in
comment 15 [1]? It is based off of the instructions in the QemuHDADump
wiki [2].
[1]
@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
@John Hoff
I saw your were successful in applying the patch. I am trying to
reproduce here, but I struggled quite a bit with kernel
compile/installation. I am also a bit wary of breaking my entire system
as it is my daily driver.
On my latest attempt, I ended up with a running kernel 5.4.0-42,
@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
@John Hoff
The windows VM is the key. It's the top layer of the 3-layer cake. The
middle layer is linux and the bottom layer is the hardware. In linux we
record the windows driver communicating with the audio codec in the
hardware's firmware with the hope that we can play back the recording in
@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
@John Hoff
Woohoo!!! Way to go John! That's great news. I submitted a patch to LKML
(see attached). The content is the same as the patch that worked for
you; all I did was change the commit message. Hopefully it lands in your
favorite kernel distribution soon. :)
> Is there anything I can do to
1 - 100 of 121 matches
Mail list logo
