Created attachment 306213
kernel-mute.log
(In reply to Tintin from comment #874)
> # . tas2781-2dev-on.sh 2
Sorry if this is a bit long, but trying to include info to help debug
the issue.
Well, it has finally happened again... It seems like the script hasn't
really helped... But I'll have to
# . tas2781-2dev-on.sh 2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019
Title:
[Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
sound at
(In reply to Tintin from comment #869)
> kindly run
> #i2cdetect -r 2
> and run following command during no sound issue
> dmesg -c > kernel-mute.log
Forgot to get the dmesg even though I did look at the dmesg output
(*facepalm*). There are no messages related to this in dmesg when this
occurs.
Save following as tas2781-2dev-on.sh
run ". tas2781-2dev-on.sh" in root mode during no sound, and check whether to
work?
Start###
#!/bin/sh
# echo Turn on log!
# set -x
clear
function clear_stdin()
(
old_tty_settings=`stty -g`
stty -icanon min 0 time 0
(In reply to dreamsyntax from comment #867)
> While audio working, and content is playing (actively outputting to device)
> Output is different:
> i2cset -y 2 0x38 0x00 0x00
> i2cset -y 2 0x38 0x7f 0x00
> i2cdump -y 2 0x38
> No size specified (using byte-data access)
> 0 1 2 3 4 5 6 7
To confirm... You want my dmesg output when there's no issue, but you
want me to clear it after reading it?
On 4/22/24 03:23, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> Tintin (shenghao-d...@ti.com) changed:
>
> What|Removed
kindly run
#i2cdetect -r 2
and run following command during no sound issue
dmesg -c > kernel-mute.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019
Title:
Unfortunately, my sound finally did fail again... But the symptoms seem
different. Audacious just hangs for a while before ultimately giving up
(and it stops hanging and stops trying to play).
But this is a new type of failure so perhaps this patch did make a bit of a
difference?
While audio working, and content is playing (actively outputting to device)
Output is different:
i2cset -y 2 0x38 0x00 0x00
i2cset -y 2 0x38 0x7f 0x00
i2cdump -y 2 0x38
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f0123456789abcdef
00: 00 00 00
(In reply to Gergo K from comment #865)
> Please try 0x38 instead of 0x70, and if still not found, try 0,1,2,4 instead
> of bus 3.
>
> If you still not found, please send your acpidump output.
# i2cset -y 1 0x38 0x7f 0x00
Error: Write failed
# i2cset -y 2 0x38 0x7f 0x00
# i2cset -y 2 0x38 0x00
> I never re-ran the above command.
The alsactl restores all audo controls after boot, including this one.
> Unfortunately, the result of the below command are as follows once audio
> breaks:
Please try 0x38 instead of 0x70, and if still not found, try 0,1,2,4
instead of bus 3.
If you still
A few things since I last posted:
After having done the below command...
`amixer -c 1 cset numid=3,name='Speaker Force Firmware Load' 1`
Every subsequent reboot the audio never broke. I had multiple 2+ hour
sessions with no issue.
I never re-ran the above command.
Adjusting the volume would have
Hi,
> there are a lot of entries, what exactly am I looking for?
Find the card with 'Speaker Force Firmware Load' control, then change
the -c and numid parameters accordingly.
> What is the expected result of the above?
It reloads the program of the amplifiers before powering up the
(In reply to Gergo K from comment #857)
> The firmware files have not changed.
>
> I think it's possible that this commit is the culprit:
> https://github.com/torvalds/linux/commit/
> bec7760a6c5fa59593dac264fa0c628e46815986
>
> Sorry about that, it works fine with tas2563, but I couldn't test
On 4/16/24 16:54, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #859 from Gergo K (so...@irl.hu) ---
> What else came to mind, the driver currently writes the calibration data to
> one
> of the wrong registers of tas2781, which can also
> Please try the following and report if it fixes the issue:
> amixer -c 1 cset numid=3,name='Speaker Force Firmware Load' 1
What is the expected result of the above?
> I had some time this morning to try and repeat the issue.. I couldn't
do it
I can reproduce in < 5 mins on average.
I played
What else came to mind, the driver currently writes the calibration data
to one of the wrong registers of tas2781, which can also cause problems.
If anyone wants to know what fixes the problem, please try this patch as
well:
https://lore.kernel.org/all/20240406132010.341-1-shenghao-d...@ti.com/
I had some time this morning to try and repeat the issue.. I couldn't do
it. So until I can find a way to repeat it, it's not worth testing other
kernel releases.
I will try Gergo's command once it happens again and report back.
--
You received this bug notification because you are a member of
The firmware files have not changed.
I think it's possible that this commit is the culprit:
https://github.com/torvalds/linux/commit/bec7760a6c5fa59593dac264fa0c628e46815986
Sorry about that, it works fine with tas2563, but I couldn't test it with
tas2781.
Something related to power management
I can try 6.7.9 and 6.7.12.
What you described vaguely sounds like the stuff I'm doing when it
breaks on me so I'll try that too!
I might have some time to do this tomorrow night.
I've wondered if this is a firmware issue as well. Here are my md5sums
for my files:
Hi, just confirming that on:
Lenovo Legion Pro 7i (Gen 8 / 2023) the no sound issue has regressed again on
6.8.5.
Last working version without any issues is 6.7.9 - which is odd
considering the original post lists this as not a regression?
alsamixer shows ALC287 under system info.
6.8.2-6.8.4
Created attachment 306161
attachment-31010-0.html
> ...it makes me think maybe our problems are symptoms of the same issue
I agree. I am using endeavour os, but I've also verified my scenario on
nobara (fedora based).
I found I can somewhat reliably get the audio to fail on 6.8.5 by leaving
the
(In reply to dreamsyntax from comment #853)
> Hi, just confirming that on:
> Lenovo Legion Pro 7i (Gen 8 / 2023) the no sound issue has regressed again
> on 6.8.5.
>
> Last working version without any issues is 6.7.9 - which is odd considering
> the original post lists this as not a regression?
>
(In reply to admin from comment #851)
> Can confirm on Endeavour 6.8.5 that my Legion Slim 7 16arha7 has working
> speakers now! yay! Lets hope they don't break again...
Does internal microphone work in your OS ?
--
You received this bug notification because you are a member of Ubuntu
Touch
Can confirm on Endeavour 6.8.5 that my Legion Slim 7 16arha7 has working
speakers now! yay! Lets hope they don't break again...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
(In reply to Linghui Ding from comment #848)
> After I upgrade to Linux 6.8.5, the speakers work well on my laptop. LOL,
> btw the machine can wake up from suspend, so this is also fixed. My laptop
> hardware model is Lenovo Legion R9000X ARHA7. Thanks everyone.
Confirm. Lenovo Legion 7 slim
After I upgrade to Linux 6.8.5, the speakers work well on my laptop.
LOL, btw the machine can wake up from suspend, so this is also fixed. My
laptop hardware model is Lenovo Legion R9000X ARHA7. Thanks everyone.
--
You received this bug notification because you are a member of Ubuntu
Touch
Working fine again for me in 6.8.5 :) Sorry for the spam!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019
Title:
[Lenovo Legion7 16ACHg6 82N6, Realtek ALC287,
Hm, I installed Ubuntu's 6.8.4 and the speakers work on my Legion 7
16achg6. But suspend doesn't wake up, so I'm back on 5.17.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
FYI, broken again in 6.8.4, 6.8.3 (not sure about 6.8.2).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019
Title:
[Lenovo Legion7 16ACHg6 82N6, Realtek ALC287,
I will share my experience maybe it can help. I am running this
configuration
CPU: 8-core AMD Ryzen 7 5800H with Radeon Graphics (-MT MCP-)
speed/min/max: 400/400/4463 MHz Kernel: 6.5.0-26-generic x86_64 Up: 10m
Mem: 3724.7/64145.7 MiB (5.8%) Storage: 2.75 TiB (59.2% used) Procs: 378
Shell: Bash
FYI, this looks to have been improved in Ubuntu's 6.8.1 mainline
(https://kernel.ubuntu.com/mainline/v6.8.1/).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019
I also tried the two changes above to 6.7.6, it took a bit for me to
work out how to compile a custom kernel in ubuntu (easy once you know).
Mine is a slightly different 14IRP8 device Yoga Pro rather than Slim Pro
(same underlying hardware).
Alsa-info -> https://alsa-
I don't know the reasons, but this code has been working in this way for
10+ years, so this type of collision can not be common.
I sent the ALC285_FIXUP_THINKPAD_HEADSET_JACK patch to the lists:
https://lore.kernel.org/all/7ffae10ebba58601d25fe2ff8381a6ae3a926e62.1708687813.git.so...@irl.hu/
And
(In reply to Cameron Berkenpas from comment #832)
> The strong beep suggests you might have the older firmware.
>
> If you have the old firmware, you might also notice your sound for your
> left and right speakers are swapped.
The speakers are not swapped but how can I check the current version
(In reply to Gergo K from comment #840)
> There is an ID collision.
>
> Your audio controller's PCI SSID (17aa:3802) is the same as the "Lenovo Yoga
> DuetITL 2021" Codec SSID. The snd_hda_pick_fixup() function searches the PCI
> SSID before the Codec SSID in the same table. So it picks the
>
(In reply to Gergo K from comment #840)
> There is an ID collision.
>
> Your audio controller's PCI SSID (17aa:3802) is the same as the "Lenovo Yoga
> DuetITL 2021" Codec SSID. The snd_hda_pick_fixup() function searches the PCI
> SSID before the Codec SSID in the same table. So it picks the
>
There is an ID collision.
Your audio controller's PCI SSID (17aa:3802) is the same as the "Lenovo
Yoga DuetITL 2021" Codec SSID. The snd_hda_pick_fixup() function
searches the PCI SSID before the Codec SSID in the same table. So it
picks the ALC287_FIXUP_YOGA7_14ITL_SPEAKERS fixup not the
(In reply to Gergo K from comment #836)
> Could you please comment out this line from patch_realtek.c and rebuild the
> kernel and start it without the module parameters?
>
> SND_PCI_QUIRK(0x17aa, 0x3802, "Lenovo Yoga DuetITL 2021",
> ALC287_FIXUP_YOGA7_14ITL_SPEAKERS),
Sounds like I should try this new firmware...
kernel-firmware... Is that the repo?
On 2/22/24 6:56 PM, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #837 from Willian (ker...@willian.wang) ---
> (In reply to Cameron Berkenpas from comment
(In reply to Cameron Berkenpas from comment #834)
> Then that's the latest firmware as far as I know (that's my server lol).
>
> Not sure why you're getting the beep then.
Oh, didn't know the server was yours, thank you lol. Unfortunately, the
firmwares are not up to date compared to
Could you please comment out this line from patch_realtek.c and rebuild
the kernel and start it without the module parameters?
SND_PCI_QUIRK(0x17aa, 0x3802, "Lenovo Yoga DuetITL 2021",
ALC287_FIXUP_YOGA7_14ITL_SPEAKERS),
--
You received this bug notification because you are a member of
The latest firmware is probably in the linux-firmware package.
Do you still hear a difference when you disable Dolby in Windows?
Do you hear the beep after hibernation also?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Then that's the latest firmware as far as I know (that's my server lol).
Not sure why you're getting the beep then.
On 2/22/24 13:31, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #833 from Willian (ker...@willian.wang) ---
> (In reply to
The strong beep suggests you might have the older firmware.
If you have the old firmware, you might also notice your sound for your
left and right speakers are swapped.
On 2/22/24 12:06, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #831
I don't know why it won't pick up your model.
Could you please run alsa-info after the patch and without the module parameter?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
=(In reply to Gergo K from comment #830)
> I don't know why it won't pick up your model.
> Could you please run alsa-info after the patch and without the module
> parameter?
Yeah, I have no idea, I decided to use specifically the model of my speaker
through trial and error.
(In reply to Gergo K from comment #828)
> Great to hear!
> I can create a patch, and it can be included in 6.6 and 6.7.
>
> Can you test whether the headset jack works also?
>
> And could you run alsa-info.sh? I think your model needs to be added to the
> patch_realtek.c to make it work without
Great to hear!
I can create a patch, and it can be included in 6.6 and 6.7.
Can you test whether the headset jack works also?
And could you run alsa-info.sh? I think your model needs to be added to
the patch_realtek.c to make it work without the module parameters.
--
You received this bug
(In reply to Gergo K from comment #826)
> Could someone please test if changing this fixup in the
> sound/pci/hda/patch_realtek.c fixes the volume control?
>
> [ALC287_FIXUP_TAS2781_I2C] = {
> .type = HDA_FIXUP_FUNC,
> .v.func = tas2781_fixup_i2c,
>
Could someone please test if changing this fixup in the
sound/pci/hda/patch_realtek.c fixes the volume control?
[ALC287_FIXUP_TAS2781_I2C] = {
.type = HDA_FIXUP_FUNC,
.v.func = tas2781_fixup_i2c,
.chained = true,
.chain_id =
I do now :) You're right the hda_model=17aa:38be definitely forces the
tas driver to load properly (it is in dmesg) and the firmware link
seemed to fix a NULL error when I first tried it.
[5.770034] snd_hda_codec_realtek ehdaudio0D0: bound i2c-TIAS2781:00
(ops tas2781_hda_comp_ops
** Bug watch added: github.com/PJungkamp/yoga9-linux/issues #11
https://github.com/PJungkamp/yoga9-linux/issues/11
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
(In reply to thornley.david from comment #819)
> I am running an 14IRP8 (Yoga Pro/Slim 9i), specifically this model
> (https://psref.lenovo.com/Detail/Yoga/Yoga_Pro_9_14IRP8?M=83BU0024AU).
>
> I have the laptop running Ubuntu 23.10 and I run mainline kernels from
> Ubuntu. I have tried almost
Could you share your acpidump output?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019
Title:
[Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal]
I noticed that patch is present in the kernel I am running...
"dmesg | grep 2781" yields nothing.
"lsmod" indicates snd_hda_scodec_tas2781_i2c is loaded.
I'm quite green with the audio subsystem in linux, so pretty overwhelmed
and suprised how complicated it is :) I'm not 100% sure, but it
(In reply to thornley.david from comment #819)
> I am running an 14IRP8 (Yoga Pro/Slim 9i), specifically this model
> (https://psref.lenovo.com/Detail/Yoga/Yoga_Pro_9_14IRP8?M=83BU0024AU).
Not sure what the cause of this is, but there is no specific mention of
"14IRP8" in any of the kernel code,
Based on alsa-info, its subsystem ID is: 0x17aa38be
It's here in the patch_realtek.c:
SND_PCI_QUIRK(0x17aa, 0x38be, "Yoga S980-14.5 proX YC Dual",
ALC287_FIXUP_TAS2781_I2C),
snd_hda_scodec_tas2781_i2c loaded.
Could you run this as well?
dmesg|grep 2781
--
You received this bug notification
I am running an 14IRP8 (Yoga Pro/Slim 9i), specifically this model
(https://psref.lenovo.com/Detail/Yoga/Yoga_Pro_9_14IRP8?M=83BU0024AU).
I have the laptop running Ubuntu 23.10 and I run mainline kernels from
Ubuntu. I have tried almost every recent kernel build up until 6.8-rc5
today (I had read
Legion Slim 7 16IRH8 quirk added with this commit:
https://github.com/torvalds/linux/commit/99af5b11c57d33c32d761797f6308b40936c22ed
This is in 6.7.1+.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
(In reply to Jacob Garby from comment #816)
> (In reply to Lukas from comment #814)
> > (In reply to Jacob Garby from comment #813)
> > > I have a "Lenovo Legion Slim 7i 16", and several days ago, out of
> nowhere,
> > > the speaker started working. I have no idea how -- I did not change
> >
(In reply to Lukas from comment #814)
> (In reply to Jacob Garby from comment #813)
> > I have a "Lenovo Legion Slim 7i 16", and several days ago, out of nowhere,
> > the speaker started working. I have no idea how -- I did not change
> anything
> > manually. I suspect it's a new kernel version
(In reply to Lukas from comment #814)
> (In reply to Jacob Garby from comment #813)
> > I have a "Lenovo Legion Slim 7i 16", and several days ago, out of nowhere,
> > the speaker started working. I have no idea how -- I did not change
> anything
> > manually. I suspect it's a new kernel version
(In reply to Jacob Garby from comment #813)
> I have a "Lenovo Legion Slim 7i 16", and several days ago, out of nowhere,
> the speaker started working. I have no idea how -- I did not change anything
> manually. I suspect it's a new kernel version that did it.
>
> I'm on Arch Linux, and I can't
I have a "Lenovo Legion Slim 7i 16", and several days ago, out of
nowhere, the speaker started working. I have no idea how -- I did not
change anything manually. I suspect it's a new kernel version that did
it.
I'm on Arch Linux, and I can't remember which kernel version I have
installed (but I
** Bug watch added:
github.com/milkovsky/Linux-on-Lenovo-Slim-7-Carbon-AMD/issues #2
https://github.com/milkovsky/Linux-on-Lenovo-Slim-7-Carbon-AMD/issues/2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in
I use a Lenovo Slim 7 Carbon with a ALC287 as well.
We have an issue page open for this device/issue as well, and I think we
nailed it down to the pin configurations.
https://github.com/milkovsky/Linux-on-Lenovo-Slim-7-Carbon-
AMD/issues/2#issuecomment-1615152518
I welcome your thoughts on
Don't mention it, I've already given up. At first, I thought maybe some
patches would "heal" this problem, then I believed the new kernel would
work, now I solved this problem by ignoring it and wearing my earphone.
--
You received this bug notification because you are a member of Ubuntu
Touch
Hey, I have a Lenovo Yoga 7 16IAP7 with Fedora Workstation 39 installed.
Kernel Verion: Linux 6.6.11-200.fc39.x86_64
alsa-lib version: alsa-lib-1.2.10-3.fc39.x86_64
I installed alsa-tools and went into hdajackretask to see what is going
on. Then I noticed that my System is telling me that I have
(In reply to Cameron Berkenpas from comment #805)
> I believe support for the 16ACHg6 was added quite a ways back.
>
> On 1/18/24 05:36, bugzilla-dae...@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=208555
> >
> > shenanig...@duck.com changed:
> >
> > What
Canonical occasionally breaks sound compatibility between kernel release
(but I yet to figure out why). However, the XanMod kernel quite rarely
breaks Lenovo sound compatibility, thus I suggest you give that kernel a
whirl: https://xanmod.org/ (It's quite easy to install and remove if
needed).
Probably time to bisect and then report back to Cirrus Logic.
On 1/18/24 16:53, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #806 from Howard Chu (h...@highlandsun.com) ---
> (In reply to Cameron Berkenpas from comment #805)
>> I believe
(In reply to Cameron Berkenpas from comment #805)
> I believe support for the 16ACHg6 was added quite a ways back.
Yes, it was added in 5.18. It is broken in 6.x. That's why I still only run
5.19 on my machine. The comment below says it actually stopped working in 6.6.
I can't confirm that it
I believe support for the 16ACHg6 was added quite a ways back.
On 1/18/24 05:36, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> shenanig...@duck.com changed:
>
> What|Removed |Added
>
(In reply to Howard Chu from comment #791)
> (In reply to Miggy from comment #790)
> > It seems the sound no longer works for the legion 7 16achg6 on kernel 6.6.
> > It's been working great for the last year on all kernels, but 6.6 just
> > doesn't work.
> >
> > I'm not sure if anyone else is
(In reply to August Wikerfors from comment #781)
> (In reply to Christian G. Semke from comment #780)
> > Here on my Lenovo Legion 7 Slim the audio never worked and the microphone
> > worked until 6.4, now in 6.5 nothing works anymore. Does anyone know how I
> > can resolve this? I'm a bit of a
```
aplay -l
...
card 2: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
```
According to laptop's specs:
https://psref.lenovo.com/Product/Legion_Slim_7_16APH8?tab=spec
Audio Chip
High Definition (HD) Audio, Realtek® ALC3306
Same no audio problem on this laptop: Legion Slim 7 16APH8
https://psref.lenovo.com/Detail/Legion/Legion_Slim_7_16APH8?M=82Y4001UMZ
OS: Fedora 39
Kernel: 6.6.9-200.fc39.x86_64
alsa-info.sh
http://alsa-project.org/db/?f=dc0275d1836faea7ddf81a990b07e4a86313bf9a
Bios:
Version: M1CN36WW
Release
Weirdly simple, but wow, this cannot be it. Hallelujah After a few
days reading and testing many things, I finally have audio! Apparently,
it was missing (some?) library required for pipewire. I have a Legion 7i
Pro running popOS on kernel 6.6.6-76060606-generic. Try running this
command:
(In reply to zacherytapp from comment #796)
> Hey it looks like Lenovo has released a new BIOS version for the Legion S7
> 16ARHA7 Slim model (the one I have that still has no sound). I'm curious if
> anyone has updated to this BIOS yet and if that's resolved any issues or if
> this would allow
(In reply to Andrew from comment #789)
> Created attachment 305523 [details]
> alsa-info.txt
>
> Thanks Cameron! Adding those files to /lib/firmware didn't work (I copied
> the files directly), so I'm probably out of luck for now. I've attached my
> alsa-info.txt in case it helps.
Hey, try to
(In reply to zacherytapp from comment #796)
> Hey it looks like Lenovo has released a new BIOS version for the Legion S7
> 16ARHA7 Slim model (the one I have that still has no sound). I'm curious if
> anyone has updated to this BIOS yet and if that's resolved any issues or if
> this would allow
Created attachment 305664
attachment-13865-0.html
I am currently out of the office on holiday I will be returning on
Tuesday January 2, I will not be checking email.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hey it looks like Lenovo has released a new BIOS version for the Legion
S7 16ARHA7 Slim model (the one I have that still has no sound). I'm
curious if anyone has updated to this BIOS yet and if that's resolved
any issues or if this would allow further development on the audio
issue.
--
You
(In reply to Gergo K from comment #794)
> (In reply to m from comment #792)
> > I'm on 6.6.4 on a Lenovo Yoga S940-14IIL
> >
> > cat /sys/class/sound/hwC1D0/subsystem_id 0x17aa3819
> >
> > Same subsystem_id as for Lenovo 13s Gen2 ITL
> >
(In reply to m from comment #792)
> I'm on 6.6.4 on a Lenovo Yoga S940-14IIL
>
> cat /sys/class/sound/hwC1D0/subsystem_id 0x17aa3819
>
> Same subsystem_id as for Lenovo 13s Gen2 ITL
> (https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_realtek.
> c#L10193)
>
> Sound works, but
For add info about the laptop
Legion S7 16ARHA7
( https://psref.lenovo.com/Detail/Legion/Legion_S7_16ARHA7?M=82UG0029SP )
cat /sys/class/sound/hwC1D0/subsystem_id
0xaa0100
Alsainfo in the comment 700
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I'm on 6.6.4 on a Lenovo Yoga S940-14IIL
cat /sys/class/sound/hwC1D0/subsystem_id 0x17aa3819
Same subsystem_id as for Lenovo 13s Gen2 ITL
(https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_realtek.c#L10193)
Sound works, but it is high-pitched since the base is missing.
--
You
(In reply to Miggy from comment #790)
> It seems the sound no longer works for the legion 7 16achg6 on kernel 6.6.
> It's been working great for the last year on all kernels, but 6.6 just
> doesn't work.
>
> I'm not sure if anyone else is having similar issues? Manjaro Linux here.
I had no luck
It seems the sound no longer works for the legion 7 16achg6 on kernel
6.6. It's been working great for the last year on all kernels, but 6.6
just doesn't work.
I'm not sure if anyone else is having similar issues? Manjaro Linux
here.
--
You received this bug notification because you are a
Created attachment 305523
alsa-info.txt
Thanks Cameron! Adding those files to /lib/firmware didn't work (I copied
the files directly), so I'm probably out of luck for now. I've attached my
alsa-info.txt in case it helps.
On Thu, Nov 30, 2023 at 10:45 AM wrote:
>
Andrew, the verb approach doesn't work here as smart amps are being
used.
The tas2781 smart amp is generally supported as of kernel 6.6... but now
it's a question of if firmware for your laptop is available.
Without your alsa-info, I can't tell if your laptop is supported...
But you can just
Is there some way I can help to get Realtek/tas working for the Lenovo
Slim Pro 9i (named Yoga Slim 9i outside of the US)?
On my Manjaro install, the top speakers work (although I don't think
they're amplified?) and the bottom subwoofers are off.
I've managed to get qemu working for sniffing
What about Lenovo Legion Slim 7 Gen 8 2023 ? does sound works ? i've
seen that work will be mainlined as said in the comment 774 but when ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
I was wondering how do I apply any patches? I'm on a legion 7i gen 7 and
was wondering how to add patches because I wanted to try out if any
patch works for my system, thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
(In reply to greg from comment #782)
> Looking at the patch this looks like a microphone quirk patch. It does not
> look like it patches the audio output side of things.
Correct, I should have made that more clear.
> Do you know of a patch or patch submission that is for audio out on the
>
Created attachment 305139
attachment-30610-0.html
I am currently out of the office on holiday I will be returning on
Tuesday September 26, I will not be checking email.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
(In reply to August Wikerfors from comment #781)
> (In reply to Christian G. Semke from comment #780)
> > Here on my Lenovo Legion 7 Slim the audio never worked and the microphone
> > worked until 6.4, now in 6.5 nothing works anymore. Does anyone know how I
> > can resolve this? I'm a bit of a
(In reply to Christian G. Semke from comment #780)
> Here on my Lenovo Legion 7 Slim the audio never worked and the microphone
> worked until 6.4, now in 6.5 nothing works anymore. Does anyone know how I
> can resolve this? I'm a bit of a beginner
>
> Alsa:
Here on my Lenovo Legion 7 Slim the audio never worked and the
microphone worked until 6.4, now in 6.5 nothing works anymore. Does
anyone know how I can resolve this? I'm a bit of a beginner
Alsa: http://alsa-project.org/db/?f=24e78ce46f588c8a681c092c24e05811a4f42f77
Kernel: 6.5.2-arch1-1
--
1 - 100 of 339 matches
Mail list logo
