In my case, there seems to be an issue with pipewire using too many file
descriptors:
systemctl status --user pipewire
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset:
enabled)
Active: active (running) since Fri 20
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 tr
(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. B
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
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?
https://bugzilla
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 cause
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 U
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:
af5adf85ef96839ae1aa79bc916f1
(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?
>
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
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 C
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 f
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 su
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
> --
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 try
Then sounds like your laptop is supported by my patch:
https://bugzilla.kernel.org/show_bug.cgi?id=216194
This patch will never make it into the kernel. But if you are able to
apply the patch and build your own kernel... This will get you sound.
(In reply to Linghui Ding from comment #775)
> Her
Depends on which laptop you have. It will work if you have the Legion 7i
Gen 7, but not for the Gen 8 (but there is work to get the Gen 8 working
that will be mainlined).
Share a link to your alsa-info.
(In reply to Linghui Ding from comment #773)
> So, this patch can solve the sound problem, ri
This is probably the same as an Nvidia driver issue that I've had... Or
similar... I had the same issue with the Gen 6, and gave up hibernating
completely with the gen7/8.
I could hibernate & resume 1-2 times, and then when resuming... the
laptop would hang, eventually my desktop session would
I haven't been able to get this working properly. I was able to get
sound with this approach a few months ago, but I was getting "AMP short"
errors, which I'm sure can't be good.
On 6/5/23 06:45, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comme
Alas, you are correct. The good news is that this is being worked on for
the Legion... But it seems to be for the latest model of the Legion
(which does haven't Cirrus Logic, it has TI smart amps IIRC). I have the
2nd to latest (which I think came out less than a year ago).
Hopefully from there
Here's a thread where people are expressing their dissatisfaction with Lenovo's
support of Linux on their Legion series laptops. Maybe if enough people chime
in, they'll take us seriously and we'll get somewhere. I personally don't
need/want formalized Linux support... I just want the hardware t
Looking more closely at your alsa-info... You have:
/sys/bus/acpi/devices/CLSA0102:00/status
I didn't even know the CLSA0102 existed! Just the CLSA0100 and the
CLSA0101. I don't think that's supported at all at this point. You might
try reaching out to Cirrus Logic. I think that's your best bet
See https://bugzilla.kernel.org/show_bug.cgi?id=216194 for a new patch.
Currently the latest is lenovo-7i-gen7-sound-6.2.0-rc3-0.0.5b-002.patch
This latest patch theoretically has support for Blake Lee's machine.
A new revision of the 16IAX7.
oppsig's Yoga Slim 7 Carbon 14ACN6
Pierre Hébert,
The name doesn't matter, just the numeric ID. If I had a patch worth
submitting, I would fix the names but otherwise they don't matter.
Please share the following outputs with me:
uname -a
And mostly I need this:
dmesg | egrep -i '(csc3551|cs35l41|reset_gpio|short|adev|speaker)'
On 2/28/23 23:4
Created attachment 303815
attachment-24448-0.html
Uploaded lenovo-7i-gen7-sound-6.2.0-rc3-0.0.5b.patch to
https://bugzilla.kernel.org/show_bug.cgi?id=216194
Although I forgot to update it in the patch name... This patch is
against 6.2.1
I put a disclaimer that this is a use-at-your-own-risk as
You have the slim? I don't think I added slim support to the patch. I
think someone else did and it worked.
It's not that hard to do. The numeric ID you need can be found in your
alsa-info.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
As the 6.1.x kernel worked, likely something else isn't quite right.
Are you sure you're running your patched kernel? Which patch did you
apply?
On 2/28/23 06:00, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #739 from Pierre Hébert (pier..
For details around why this doesn't work as well as a use at your own
risk patch (which SO FAR has proven safe), look here:
https://bugzilla.kernel.org/show_bug.cgi?id=216194
The short short version is that Lenovo has zero interest in adding
entries in a BIOS update that would allow sound to wor
No, only the 16IAX7 is covered.
You could a quirk for your laptop model... But I have to wonder how
different the speakers are for a slim model, which would concern me.
On 12/30/22 16:17, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #731
New patch for Lenovo Legion 7i Gen7 (16IAX7)
lenovo-7i-gen7-sound-6.2.0-rc1-0.0.3.patch posted:
https://bugzilla.kernel.org/show_bug.cgi?id=216194
This is still very much a use-at-your-own-risk sort of thing... However,
I have it on good word that someone who's been using this virtually
everyday
I think none of the Gen 7 Legions have support.
Basically, all Lenovo needs to do is add some info to the ACPI _DSD
tables which will allow the cs35l41 drivers to know how to configure the
amp chips in our laptops. Lenovo so far has been unwilling to do this.
Maybe the AMD based Gen 7 does, but
https://wiki.archlinux.org/title/DSDT#Using_modified_code:
We should be able to override it. From here, using early patching should
allow you to specify using a quirk to support CSC3551.
From there's a question of using safe values in your override.
Also, you won't have suspend/resume for the
(In reply to Blake Lee from comment #719)
> Hi Cameron,
>
> I got my Legion Slim 7 Gen 7 AMD version yesterday and when I excitedly
> installed Fedora, I found the audio did not work. I would like to throw my
> weight behind this to get it fixed, but I don't know what to say to support
> exactly
Hello,
I'll follow up with you guys probably tomorrow (but possibly as soon as
later today). I've just been having an eventful holiday weekend.
As tomorrow is a normal weekday that I have off, I'll finally reach out
to Lenovo again tomorrow myself.
Doing a quick search, I don't think anyone ha
None. Whenever I picked up their calls, it would hang up, so the ticket
would close. I'm going to try their support chat when I have time...
Whenever that will be.
On 11/4/22 12:41, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #714 from d
The Intel based Legion 7i Gen 7 definitely has this problem as I have
one.
On 10/27/22 09:16, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #712 from antide...@gmail.com ---
> Does anyone know if both the intel and amd versions of legion gen
It does not, which is unfortunate, as the 6th gen model recently finally
got support.
The gen 7 uses the CSC3551 and the gen 7 is missing the properties in
the _DSD tables.
Do you already have the Gen 7? Try submitting a Lenovo support ticket
asking them to add the properties. I have a ticket
(In reply to toyeisfree from comment #708)
> i'm a normal user and i can be super wrong but... why we say that the bios
> is missing something and in Windows work perfectly without that ?
Because the windows drivers from Lenovo have those values hardcoded into
them.
Seems that Cirrus Logic genera
(In reply to antidense from comment #705)
> Here are the dmesg errors:
> [ 35.177946] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: error -EINVAL:
> Platform not supported
> [ 35.179512] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: error -EINVAL:
> Platform not supported
>
> [2.331045] ACPI: \_SB
(In reply to toyeisfree from comment #701)
> Created attachment 302941 [details]
> dmesg for Legion S7 16ARHA7-82UG
>
> dmesg for this laptop (
> https://psref.lenovo.com/Detail/Legion/Legion_S7_16ARHA7?M=82UG0029SP )
Because your ACPI table is missing the _DSD entries just like mine:
[6.1110
You could share your dmesg.
The other possibility is that the kernel doesn't include the
configuration (arch IIRC?).
On 10/1/22 04:48, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #698 from jochemp...@gmail.com ---
> (In reply to Cameron
Created attachment 301907
attachment-12523-0.html
Almost certainly your laptop doesn't have the _DSD entries needed to
properly get sound working.
Check dmesg for either of these messages:
dmesg | grep -i "Platform not supported -EINVAL"
or
dmesg | grep -i "Error: ACPI _DSD Properties are missin
The Lenovo Legion 7i Gen 7 (2022) model is now available in the USA:
https://www.lenovo.com/us/en/p/laptops/legion-laptops/legion-7-series/legion-7i-gen-7-(16-inch-intel)/len101g0018
If you have one of these laptops, please share your alsa-info here. I
strongly suspect it has Cirrus Logic cs35l41
Songine,
Can you provide more info about your specific model? You should be able
to get that from running "lshw".
For the top of my output, I get:
version: Legion 7 16ITHg6
On 6/4/22 17:46, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #6
Great!
Some probably silly questions:
1) Do both speakers work? Do you get left channel sound out of the left
speaker and right channel sound out of the right speaker?
2) After resuming from suspend/hibernate, does your sound still work?
3) What if you insert headphones and remove them? Does so
Did you test this yourself?
On 6/3/22 00:11, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> Songine (donglingluoy...@gmail.com) changed:
>
> What|Removed |Added
> ---
Looking at your alsa-info, you don't have the CLS0100 amplifier chips,
which is what those modules would enable support for. Your laptop is not
supported by those modules and likely aren't supported at all.
(In reply to cris223 from comment #620)
>
> Hi everyone, with a thanks of your support!
>
Appears that these kernels are including these drivers. You might have
to figure out how to build your own kernel while enabling the necessary
kernel options yourself after all.
On 5/24/22 01:46, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comme
It seems the path to endian.h may have changed from
/usr/include/sys/endian.h to /usr/include/endian.h.
In the failing file(s), try changing it from:
#include
To:
#include
On 5/24/22 05:37, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment
I would try try 5.17. 5.18 only came out yesterday, and therefore
doesn't even have any point releases so chances are reasonably high
you'll run into bugs.
Additionally, I don't have the ACHg6. It's possible you'll need to
specify which modules to load. In the likely event that 5.17 doesn't
work,
Your error message shows you're 5.13, which definitely doesn't have
support.
On 5/23/22 08:46, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #614 from she...@liang.at (she...@liang.at) ---
> The first two modprobe commands returned
> `
> mo
There's no patch for your laptop yet.
Assuming your sound bar is initialized through verbs (I suspect it is),
you'll need to find the verb sequence yourself:
https://github.com/thiagotei/linux-realtek-alc287/tree/cameron
Once there's a working verb sequence, a patch can be created.
On 5/23/22 0
Seems like this is the best way to do it (but if someone knows of a better way
for Ubuntu, let us know):
https://sleeplessbeastie.eu/2021/11/01/how-to-install-mainline-linux-kernel-on-ubuntu-based-distribution/
Seems this gets you a tool that allows you to manage and install
mainline kernels. You
According to your alsa-info, you have the already supported 16ACHg6
which is supported in the latest versions of the kernel.
There should be a repo you can add on your system to be able to pull the
latest mainline kernels. I don't have it handy at the moment as I've
been building/installing ker
Created attachment 300990
attachment-14829-0.html
From your alsa-info (thanks!), I see that your subsystem id is 0x3822
compared to the 0x1813 of the 15IMHG05.
In the root of the linux source folder/directory, open the file:
sound/pci/hda/patch_realtek.c
Find this line:
SND_PCI_QUIRK(0x17aa, 0
Looking at the model number, there's a chance it's compatible with the
verbs of the 15IMHG05, or another model from around that time.
Do you know how to build and run your own kernel?
Also, please provide a URL to your alsa-info.
On 5/15/2022 12:12 PM, bugzilla-dae...@kernel.org wrote:
> https:
The issue appears to be that the Nvidia kernel module is failing to
build and therefore you do not have working Nvidia support with this
kernel. I'm not sure how you configured your kernel so I suspect you
have one OR both of the following issues:
1. Nvidia's drivers do not yet support 5.18-rc1. E
Sounds like https://github.com/ibus/ibus/pull/2394 might fix the issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1965673
Title:
Object 0x... of type IBusText has been f
So I can confirm that copying /usr/share/pipewire/media-session.conf to
/etc/pipewire/media-session.d/media-session.conf and deleting these lines fixes
the issue:
$ diff /etc/pipewire/media-session.d/media-session.conf
/usr/share/pipewire/media-session.d/media-session.conf
94a95,116
> with-a
Probably the models of laptop each need their own set of verbs.
On 2/14/22 05:34, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #552 from Jürg Lempen (i...@jlempen.com) ---
> Hi all,
>
> Good news for Lenovo Yoga Duet 7 13IML05 owners!
>
> T
Lucas,
Do the CS35L5* chips require firmware to operate? It seems the
CS35L41/2's do not.
And out of curiosity, does the CLSA0101 have the CS35L51?
On 2/7/22 00:36, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #549 from Lucas Tanure (tan
Whoops, just checked the latest xenial systemd source package and
mistakenly thought I saw the patch had already been pulled. Please pull
this.
** Changed in: systemd (Ubuntu)
Status: Fix Released => New
** Description changed:
- Please backport this patch to 16.04, which should improve r
** Tags added: patch patch-accepted-upstream
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1659676
Title
Public bug reported:
performed apt-get updated followed by apt-get autoremove
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: humanity-icon-theme 0.6.10
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architec
LGTM
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cgroup-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1668724
Title:
fails to mount cgroupfs inside containers running on 16.04
Status in cgroup-lite package in Ubuntu:
I'm happy to provide a patch, but if the root cause of my issue is in lxc
it may be easier to patch that than worrying about backwards compatibility
for cgroups on older distro releases.
On Mar 3, 2017 20:11, "Serge Hallyn" <1668...@bugs.launchpad.net> wrote:
> This bug incidentally also affects
Hm, I found a bug in my last version of this patch. Freshly booted machines
which had not mounted the cgroupfs had all the hierarchies as 0, causing all
cgroups to get mounted onto a single directory. I can work around this by
detecting this scenario.
However, I wonder if I am actually seeing a
Edit: re: the systemd hierarchy, it's actually not mentioned in
/proc/cgroups, it's /proc/self/cgroups
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cgroup-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1668724
Title:
fa
Also, is there a reason the name=systemd cgroup controller gets mounted
at /sys/fs/cgroup/systemd instead of /sys/fs/cgroup/name=systemd in
newer versions of cgroups-mount? It means my applications have to
special-case stripping off the name= when they try to work with cgroups
based upon /proc/cgro
Whoops, didn't notice I changed that part in my local copy. Should have
been more careful with my patch.
** Patch removed: "cgroup-lite_1.1.5.patch"
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+attachment/4828546/+files/cgroup-lite_1.1.5.patch
** Patch removed: "cgroup-
Patch for 1.12
** Patch added: "cgroup-lite_1.12.patch"
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+attachment/4828590/+files/cgroup-lite_1.12.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Patch for 1.1.5
** Patch added: "cgroup-lite_1.1.5.patch"
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+attachment/4828588/+files/cgroup-lite_1.1.5.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
It looks like there were fixes in the latest version of cgroup-lite that
would still be applicable/useful for earlier ubuntu releases, but I
tried to minimize the diffs to have the functionality that I need. Let
me know if you need a patch for trusty as well.
--
You received this bug notification
Patch for 1.12
** Patch added: "cgroup-lite_1.12.patch"
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+attachment/4828547/+files/cgroup-lite_1.12.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Patch for cgroup-lite 1.1.5
** Patch added: "cgroup-lite_1.1.5.patch"
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+attachment/4828546/+files/cgroup-lite_1.1.5.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
and have noticed that the cgroups-mount script for mounting the cgroups
inside the containers has stopped working. This is because systemd now
comounts multiple controllers on a single hierarchy, which prev
Public bug reported:
Please backport this patch to 16.04, which should improve reliability of
timesyncd updates to the RTC:
https://github.com/systemd/systemd/commit/5f36e3d30375cf04292bbc1bf3f4d7512cf80139
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Descript
Nathan: How many interfaces or IP's are you bringing up? That error
message makes it sound like there could be a lot of contention on the
lock. Could you also get the output of `pstree | grep -B3 lockfile`
while a VM is coming up? (You'll need to attach to a free virtual
terminal using the kvm con
I can confirm I've been running this in production and have not seen any
further issues.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
htt
** Description changed:
- We're seeing a race between if-up.d/ntpdate and the ntp startup script.
+ [Impact]
+ * Hardware clocks are not stepped at boot, which can prevent NTP from ever
+ syncing the clock.
+ Incorrect clocks can cause serious issues in distributed systems.
- 1) if-up.d/nt
In case it wasn't clear, my patch is supposed to be for the
debian/ntpdate.if-up file. Also, I think the priority of this bug should
be higher, it was assigned 'low' when there was no clear problem caused
by the race. Systems booting with uncorrectable clock skew can be a
serious problem.
--
You
I think a common cause for this issue could be stuck buttons. I was
seeing a similar symptom today where the left button on my usb mouse
attached to my closed laptop wasn't working. Opening the lid and tapping
the mouse buttons by my touchpad fixed the issue.
--
You received this bug notification
82 matches
Mail list logo
