[Kernel-packages] [Bug 1747273] Re: Can not control brightness on Thinkpad P51

2019-10-25 Thread blszyn
This still happens in a fresh install of 19.10 with discrete-only graphics (Nvidia enabled, Intel disabled in BIOS) and with the nvidia driver. Backlight control works when booting with the 19.10 live iso which the uses nouveau driver. -- You received this bug notification because you are a memb

[Kernel-packages] [Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

2018-04-13 Thread blszyn
Another ThinkPad P51 5.15.0-13-generic, Ubuntu 18.04 [0.00] ACPI: Core revision 20170831 [0.00] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210) [0.00] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/

[Kernel-packages] [Bug 1760876] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

2018-04-24 Thread blszyn
issue seems to persist in bionic linux-generic 4.15.0.19.20 amd64. $ sudo apt install --reinstall nvidia-dkms-390 Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to ge

[Kernel-packages] [Bug 1760876] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

2018-04-25 Thread blszyn
My Ubuntu 18.04 is no longer affected. I was able to get past "Cannot use CONFIG_STACK_VALIDATION=y" with some cleanup - removing all nvidia drivers, manually blacklisting nouveau, updating initramfs, and rebooting - before installing nvidia drivers and dkms again. -- You received this bug notif

[Kernel-packages] [Bug 2062412] [NEW] No input through internal microphone (Ryzen 6000)

2024-04-18 Thread blszyn
Public bug reported: The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This is a known problem and a patch may be included in kernel 6.8.3. Is it possible to backport this patch? Or is the plan to wait for a kernel

[Kernel-packages] [Bug 2062412] Re: No input through internal microphone (Ryzen 6000)

2024-04-18 Thread blszyn
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+attachment/5767654/+files/version.log -- 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/206

[Kernel-packages] [Bug 2062412] Re: No input through internal microphone (Ryzen 6000)

2024-04-19 Thread blszyn
Commit b44a34f581b0 applies to type 21J2 but Lenovo Thinkpad P14s (AMD) Gen 4 is type 21K5. Mario - you commented on a commit regarding type 21K5 here https://lore.kernel.org/lkml/cbf8ac6f-5e8d-4430-aba7-853cded5a...@michaelkloos.com/T/ Should 21K5 be included in the Quirks List? -- You receiv

[Kernel-packages] [Bug 2062412] Re: No input through internal microphone (Ryzen 6000)

2024-04-21 Thread blszyn
*** This bug is a duplicate of bug 2061254 *** https://bugs.launchpad.net/bugs/2061254 I tried mainline daily build 6.9.0-060900rc4daily20240420-generic. (Does it include commits that came a few hours before?) The microphone appears to be an acp63 device. Both snd_pci_acp6x and snd_pci_ps a

[Kernel-packages] [Bug 2062412] Re: No input through internal microphone (Ryzen 6000)

2024-04-21 Thread blszyn
*** This bug is a duplicate of bug 2061254 *** https://bugs.launchpad.net/bugs/2061254 The microphone is working in gnome desktop sessions with mainline daily build 6.9.0-060900rc4daily20240420-generic. -- You received this bug notification because you are a member of Kernel Packages, which

[Kernel-packages] [Bug 2108862] Re: Regression in NFS ro mount behavior

2025-05-22 Thread blszyn
I am seeing this in the most recent x86_64 kernels in both 24.04 and 25.04. It is not possible to remount NFS as read-write if another NFS volume is mounted read-only. Unmounting all NFS read-only volumes allows remounting as read-write. Is this the same bug? -- You received this bug notifica