Public bug reported:
The brightness level works correctly, but when the system goes to sleep
mode and then I wake it up, I am not able to increase/decrease the
brightness level using the keyboard controls (Fn + F11/F12), it works as
a On/Off switch pretty much. When it wakes up, the brightness
Are there any updates on this issue?
--
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/1852084
Title:
Backlight brightness not working correctly after waking from Suspend
Mode
Status in
This issue also seems to be occurring when installing kernel version
5.19.10 from the Ubuntu Kernel repositories, so it is something related
to version >5.19.X (including 6.0rc and so on).
The default Ubuntu 22.10 kernel, which comes bundled with version 5.19,
simply won't boot at startup,
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616784/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616786/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616787/+files/Lspci.txt
--
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/1990068
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616788/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616785/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
When installing the daily build ISO fo Ubuntu Kinect Kudu, the system
will hang at boot, forcing a reboot and then going to Advanced Option
(on GRUB) and selection kernel 5.15.0.27.28, which comes preinstalled
when Ubuntu is installed, which then works as usual. Testing with
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616789/+files/Lsusb.txt
--
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/1990068
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616796/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616798/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616790/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616799/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616791/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616792/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616793/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
If there's a way to capture or produce a crash dump while the Kernel is
loading its initial ramdisk, it would be great to add here, but I'm not
sure of how to force it to generate a log.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616794/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616800/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616797/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1990068/+attachment/5616795/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I don't, it simply hangs on that screen, without even responding to a
press on NumLock, or Ctrl+Alt+Del. Interestingly, when I press on my
laptop's power button, it shuts down right after, like if it didn't even
moved passed the UEFI (even though I'm able to change the kernel with
which to start
After a lot of searching around, it seems that it is necessary to change
the "iommu=soft" command on GRUB to "amd_iommu=off" on kernel 5.19 or
higher. With that command, all kernels will boot fine afterwards.
--
You received this bug notification because you are a member of Kernel
Packages,
24 matches
Mail list logo
