[Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service

2023-11-02 Thread Anaggh S
TL;DR Check if this fixes it for you. sudo apt install dptfxtract sudo systemctl restart thermald -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2038288 Title: Failed to start

[Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service

2023-11-02 Thread Anaggh S
Seems like I fixed the problem? References: * https://github.com/intel/thermal_daemon/issues/289 * https://github.com/intel/dptfxtract By default on Xubuntu 23.10, `/etc/thermald/thermal-conf.xml` does not exist. Run `sudo apt install dptfxtract` This creates

[Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service

2023-11-01 Thread Anaggh S
@koba sudo apt install autoconf autoconf-archive g++ libglib2.0-dev libdbus-1-dev libdbus-glib-1-dev libxml2-dev gtk-doc-tools libupower- glib-dev liblzma-dev libevdev-dev git clone https://github.com/intel/thermal_daemon.git cd thermal_daemon ./autogen.sh prefix=/ make # Stop Default

[Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service

2023-11-01 Thread Anaggh S
+1 Happening on fresh install. * Xubuntu 23.10 amd64 on every boot. * CPU Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz * Linux home 6.5.0-10-generic #10-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 13 13:49:38 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux * thermald 2.5.4-2 sudo systemctl status thermald ×

[Kernel-packages] [Bug 2035135] Re: Oracle Cloud systems not getting Jammy kernel updates

2023-09-16 Thread Anaggh S
Noticed this as well on Ubuntu 22.04 oracle arm64 (stuck at 5.15.0-1040) . No oracle kernel update since 2 months+? I decided to install latest generic hwe kernel instead and got rid of all oracle kernels. ``` sudo apt install linux-image-generic-hwe-22.04 reboot ``` ``` dpkg -l | grep -i

[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

2022-06-17 Thread Anaggh S
+1 Confirm. Adding "intel_iommu=off" to grub fixes the problem. Tested on * 5.17.6-051706-generic #202205090841 SMP PREEMPT Mon May 9 08:51:54 UTC 2022 x86_64 GNU/Linux * 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 GNU/Linux Like Tushar, the flickers I experienced are

[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)

2022-06-07 Thread Anaggh S
Thanks for confirming! This is great news. -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0

[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)

2022-06-07 Thread Anaggh S
Hi, following up on this https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/comments/26 I installed 5.18.2 today using mainline https://github.com/bkw777/mainline $ uname -a Linux home 5.18.2-051802-generic #202206060740 SMP PREEMPT_DYNAMIC Mon Jun 6 07:46:45 UTC 2022 x86_64 x86_64

[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)

2022-05-12 Thread Anaggh S
Hi, following up on this - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970426/comments/9 GRUB PARAM - `i915.enable_dc=0 intel_idle.max_cstate=2` has fixed the flicker for me. $ uname -a Linux home 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64

[Kernel-packages] [Bug 1970426] Re: [i915] screen suddenly starts flickering after update

2022-05-02 Thread Anaggh S
Affects Xubuntu 22.04 too on Lenovo Ideapad 330s (Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz) After about 11 days of using 22.04 release, it lead to major loss of productivity due to the flickering. Got headaches. This should have been a release blocker. I was curious if it affected Debian