It's working!
On Sun, 22 Oct 2023 at 10:05, Launchpad Bug Tracker <
2027...@bugs.launchpad.net> wrote:
> [Expired for linux (Ubuntu) because there has been no activity for 60
> days.]
>
> ** Changed in: linux (Ubuntu)
>Status: Incomplete => Expired
>
> --
> You received this bug notificat
Please look into this.
On Fri, 14 Jul 2023 at 13:10, Daniel van Vugt <2027...@bugs.launchpad.net>
wrote:
> ** Changed in: linux (Ubuntu)
>Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs
Thanks for the tip!
now i can see the brightness bar but still its not working the
brightness is at 100 % only
On Fri, 14 Jul 2023 at 12:25, Daniel van Vugt <2027...@bugs.launchpad.net>
wrote:
> You might want to try kernel parameter 'acpi_backlight=vendor' which I was
> reminded of by:
> https:
I just checked all the bugs i didn't the solution could you please give the
the solution to fix this bug the brightness is stuck at full it's soo
irritating
On Thu, 13 Jul 2023 at 15:40, Daniel van Vugt <2027...@bugs.launchpad.net>
wrote:
> See also: bug 1899626, bug 1944094, bug 1995173
>
> ** S
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/2027645
Title:
[Lenovo Legion 5] Brightness option is not working and not sh
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Naresh (naresh-egsnrc)
--
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/1807406
Title:
hid-sensor-hub 001F:8086:22D8.0
We are still able to reproduce the issue with latest AMI BIOS FW with
the version "BIOS Date: 09/09/2019 16:06:39 Ver: 0ACKL028". The logs
attached in the previous comment are useful ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Thank you very much. Attached the dmesg log collected from the system.
May be it gives some hints on the freeze behavior. BTW it looks like we
are using a different BIOS version TX2-FW-Release-7.4-build_05 from the
logs. I will confirm the equivalent AMI BIOS version. If they are not
using the AM
Public bug reported:
UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system
left idle for ~22min it becomes unresponsive. The system will not take
any inputs like from UART, ping ..etc. The system will completely
freeze and we need to hard reset the system. It could be possible t
Linaro's test farm also notice this problem and reported internal bug on
dragonboard-410c device running 5.3.0-rc6 mainline kernel.
Bug 5460 - mainline: dragonboard-410c: WARNING at qcom_iommu.c:325
qcom_iommu_domain_free+0x74/0x88
https://bugs.linaro.org/show_bug.cgi?id=5460
dragonboard-410c b
10 matches
Mail list logo
