The fix is included in Ubuntu-5.4.0-43.47 and later
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1882823
Title:
** Changed in: oem-priority
Importance: High => Critical
--
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/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default, until "max
hi reporter and any affected user,
I can not find any released image included
oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10
Same as #4 comment, the only iwlwifi dkms we provided is backport-
iwlwifi-dkms.
Could you please show me the `ubuntu-report show`? or bto.xml in the
re
Did you try to remove the kernel parameter "acpi_osi=linux"?
Please run "ls /sys/class/backlight/" to see what backlight interfaces
are available.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Please run "ls /sys/class/backlight/" to see what backlight interfaces
are available.
You may also want to try the kernel parameter for backlight such as
below
acpi_backlight= [HW,ACPI]
{ vendor | video | native | none }
If set to vendor, pr
For modifying / adding kernel parameters, please refer to
https://wiki.ubuntu.com/Kernel/KernelBootParameters
--
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/1894667
Title:
[HP 635] Radeo
Let's try manually whether backlight interfaces work.
cd /sys/class/backlight/radeon_bl0
# get max brightness
cat max_brightness
# get current brightness
cat brightness
# change current brightness, assuming max=12
echo 12 | sudo tee brightness
echo 6 | sudo tee brightness
Once done, d
got an error message during installation.
from a machine from certification pool 201903-26932
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
$ sudo apt-get install nvidia-driver-450
.
E: Co
This is kind of expected since it is common that systems from 2011 use
ACPI video interface. You can add the kernel into /etc/default/grub to
make it consist across boots.
I will compile a linux kernel with a workaround of
"acpi_backlight=video" for testing. If this work I can submit to linux
kern
Please try the kernel @
https://people.canonical.com/~alexhung/LP1894667/
1. remove kernel parameter "acpi_backlight=video"
2. download all deb
3. install kernel by "sudo dpkg -i *.deb"
4. reboot
This should be the same as "acpi_backlight=video"
1. run "ls /sys/class/backlight"
2. verify whet
It sounds weird to me that focal user will always get an error during
installing nvidia-driver-450 after this SRU be done.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/
A patch was sent to upstream for review
--
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/1894667
Title:
[HP 635] Radeon 6310 brightness control does not work
Status in linux package in Ub
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Sure I will update the information here.However, this will take a while,
i.e. patch review -> mainline kernel -> stable kernel -> Ubuntu focal
kernel.
It is the same as using the kernel parameter, and the patch will not
conflict with kernel parameter either.
--
You received this bug notification
The error messages are caused by BIOS bugs, and they cannot be fixed in
Ubuntu.
OC07 error in descriptions is declared but not defined in ACPI DSDT,
i.e. External (OC07, UnknownObj).
The OEMB in #6 has a checksum (i.e. one of OEMx) is a OEM-specific table and
that's probably used in Windows onl
#5 simply complains that ACPI BIOS can directly access I/O ports and
Linux kernel is not fond of it. The warnings are very often harmless.
--
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/189
You can try the following utilities to see whether CPUs are occupied
before and after USB devices are plugged in
1. top - check whether any processes is running
2. watch -n1 cat /proc/interrupts - check whether any interrupts are generated
at abnormal rates
3. powertop - more details of power an
dmesg shows nothing of ath10k_pci (wifi driver).
Please run "sudo modprobe -r ath10k_pci ; sudo modprobe ath10k_pci" to
check whether wifi driver can be re-initialized?
You may want to download and run live session of Ubuntu 20.04.1 ISO to
verify whether Qualcomm Atheros QCA9377 works.
** Summar
** Summary changed:
- cpu frequency stuck to max when pugging USB device
+ cpu frequency stuck to max when plugging USB device
** Summary changed:
- cpu frequency stuck to max when plugging USB device
+ cpu frequency stuck to max when plugging USB devices
--
You received this bug notification
@afsverissimo,
You may want to file another bug for your brightness problem which may
have different root cause and thus different required information.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kerne
same to #10, the issue is fixed. I verified the installation passed on
focal docker image.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1887674
Title:
Introduce the
The warning messages occurred between "ACPI: EC: interrupt blocked" and
"ACPI: EC: interrupt unblocked". Let's try to apply all (17) mainline
patches to ACPI EC to Ubuntu-5.4.0-47.51.
If this solves the problems we can then bi-select to identify which
patches are the solution and then backport to
** Also affects: oem-priority
Importance: Undecided
Status: New
--
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/1849947
Title:
Dell XPS 13 (7390) Display Flickering - 19.10
Sta
It is a good idea to send your patch to below kernel's mailing lists so
this can be reviewed by broader audiences to confirm it will work in all
scenario.
INTEL DRM DRIVERS (excluding Poulsbo, Moorestown and derivative chipsets)
M: Jani Nikula
M: Joonas Lahtinen
M: Rodrigo Vivi
L
@kaihengfeng yes both BT and Wifi stop working intermittently.
I found a fix that will bring both the BT and Wifi back if they go down,
however. By removing the BT-related modules from the kernel, issuing a
USB reset, and then loading the BT modules back into the kernel. BT will
work after that.
Thanks mfo for helping out how to disable secure boot and install kernel
I uploaded a test kernel @
https://people.canonical.com/~alexhung/LP1896482/0a8c35897f60b202/
There are 17 patches so it requires 4 times to identify the fixing
kernel patch. The included patches are listed in ec_bisect1.log
@jcline-physics,
Thanks for testing. The next is available @
https://people.canonical.com/~alexhung/LP1896482/31be3e3551d09f20/
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alex Hung (alexhung)
-
Next one is @
https://people.canonical.com/~alexhung/LP1896482/c271d18b523bb58e/
--
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/1896482
Title:
acpi event detection crashes
Status in lin
Next one:
https://people.canonical.com/~alexhung/LP1896482/937d1d5d752513b8/
--
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/1896482
Title:
acpi event detection crashes
Status in linux p
Bisecting points to the below commit. Ubuntu-5.4.0-47.51 requires more
than it without conflicting. Let me figure out which ones are also
required for SRU and I will build another kernel (and final one
hopefully) for testing
commit 03e9a0e05739cf872fee494b06c75c0469704a21
Author: Rafael J. Wysocki
A test kernel with target patches ready for SRU is available @
https://people.canonical.com/~alexhung/LP1896482/fixes/
The patch in #23 requires three precedent patches. See SRU.log file for
more details.
Note it is rebased Ubuntu-5.4.0-48.52 now.
--
You received this bug notification because y
@jcline-physics,
can you give kernel in #24 a try?
--
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/1896482
Title:
acpi event detection crashes
Status in linux package in Ubuntu:
In Pr
Information updates: the patch is now queued in 5.10.
--
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/1894667
Title:
[HP 635] Radeon 6310 brightness control does not work
Status in linux
That's great. Let's wait for the good 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/1895615
Title:
Backlight adjustment doesn't work on Google Pixel Slate
Status in linux package
** Description changed:
+ = SRU Justification =
+
+ [Impact]
+
+ The bug causes the EC driver to fail and ACPI events are no longer
+ handled by Linux kernel, i.e lid close no longer triggers suspends.
+
+ [Fix]
+
+ Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid
+ initiali
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alex Hung (alexhung)
--
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/1894667
Title:
[HP 635] Radeon 6310 brightness cont
Does the #10 target to 5.6.0.1019.16 for focal?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1844410
Title:
[TGL] Thunderbolt support (Tiger Lake)
Status in HWE Next:
New
St
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alex 1888 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Jul 3 16:00:55 2020
InstallationDate: Installed on 2020-07-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "F
resent on both versions.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
oDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alex 1888 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Jul 3 16:00:55 2020
InstallationDate: Installed on 2020-07-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal F
amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alex 1888 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Jul 3 16:00:55 2020
InstallationDate: Installed on 2020-07-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS &q
ecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alex 1888 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Jul 3 16:00:55 2020
InstallationDate: Installed on 2020-07-03 (0 days ago)
InstallationMedia: Ubuntu 20.0
age-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alex 1888 F pulseaudio
Ca
.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: alex 1888 F pulseaudio
CasperM
gnature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: alex 1888 F pulseaudio
CasperMD5CheckResult: skip
Curr
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMM
both versions.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USER
4
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alex 1888 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Jul 3 16:00:55 2020
InstallationDate: Installed on 2020-07-03 (0
** Changed in: linux (Ubuntu)
Status: In Progress => Won't Fix
--
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/1879082
Title:
Kernel reporting 100% battery, always
Status in linux
I have also a Qualcomm Atheros QCA6174 and can observe it fails from
time to time, not in focal only. More discussion can be found in
LP:1872351
While there aren't solution now, I use "sudo modprobe -r ath10k_pci ;
sudo modprobe ath10k_pci" to avoid rebooting the system.
--
You received this bug
It would be a great help to list which previous kernel version works,
too.
--
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/1886248
Title:
f6 Function key is not working
Status in linux p
Do you mean "F6" or the "hotkey" on your F6?
More information will be needed such as what F6 function key (hotkey) is
supposed to do and what laptop you have and so on. Running apport-
collect as in #1 will certainly helps.
Did you try Ubuntu 20.04 USB-live and verify whether this also happens
on
This is public in the Ubuntu CVE Tracker so making the bug public too.
** Information type changed from Private Security to Public Security
--
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/1
The log in description clearly points out "firmware crashed", and that
may be something we can forward to the hardware vendor.
--
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/1886588
Title:
@azimcuetcse01,
I believed vicamo meant the procedures in comment #2, such as
1. upload logs by running "apport-collect 1885671"
2. change bug status to "confirm"
Please update to latest packages and kernel (sudo apt update && sudo apt
upgrade -y && sudo reboot) and reproduce the bug before
Public bug reported:
> Laptop model directly from the sticker of the computer.
Lenovo T450 ThinkPad
> Manufacturer of the Touchpad.
> When the symptom first appeared.
Right after 18.04 => 20.04 upgrade. Touchpad never worked after upgrade.
Nor movements, neither clicks.
ProblemType: Bug
Distr
You can disable USB3 wakeup by modifying "/proc/acpi/wakeup"
1. list all wakeup sources - cat /proc/acpi/wakeup
2. enable or disable by echo device name - for example, my USB3 is XHC
- echo XHC | sudo tee /proc/acpi/wakeup
3. confirm changes - cat /proc/acpi/wakeup
--
You received this bug no
If this problem only occurs after you upgrade kernel, we may be able to
identify the regression patch by bisecting kernels if a passing kernel
version is shared.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
Invalid. I tested my laptop with 18.04 live image. The touchpad doesn't
work there. I guess, it's broken physically.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Description changed:
The Intel x710-TM4 is one of the latest 10GbE controllers from intel
using the i40e driver. This particular 4 port comes in a 2x2
- arrangement: 2x SFP+ and 2x RJ-45. This car is enabled in 5.4 via the
+ arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4
@bybeu,
USB Emulation: This allows USB devices (keyboard, mouse, USB drives) to
operate in BIOS / DOS.
USB Powershare: This allows USB ports to provide powers in sleep or
power-off, depends on hardware designs. This consumes some battery power
in sleep or power-off
USB Wake Support: This allows
after this patch, the issue can not be reproduced:
commit 24249e091ab3a935f6ea87b7f7355c689c045a80 (HEAD -> refs/heads/master)
Author: Luiz Augusto von Dentz
Date: Mon Apr 9 14:48:41 2018 +0300
shared/queue: Handle NULL as direct match on queue_remove_if
As with queue_find when fu
bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp
7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000]
** Affects: oem-priority
Importance: Critical
Assignee: Alex Tu (alextu)
Status: In Progress
** Affects: bluez (Ubuntu)
Importance: Undecided
S
this is the debdiff which applied the patch , and I also host the
modified code there :
https://code.launchpad.net/~alextu/ubuntu/+source/bluez/+git/bluez/+ref/lp1887910
-bluetoothd-segv-keyboard
** Patch added: "bluez_5.48-0ubuntu3.5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+b
@seb128, yes, I modified the description and the debdiff is there in #4.
** Description changed:
- steps:
+ [Impact]
+
+ * only impact Bionic machines because series after Bionic already
+ included this patch.
+
+ [Test Case]
+
1. pair bluetooth keyboard
2. see the dialog asking user in
** Description changed:
[Impact]
- * only impact Bionic machines because series after Bionic already
+ * only impact Bionic machines because series after Bionic already
included this patch.
[Test Case]
- 1. pair bluetooth keyboard
- 2. see the dialog asking user input the code f
Sorry,
the debugging and debdiff was done on the target machine so that the email ID
was missed.
This attached new debdiff also included the patch and lp number
information in the changelog.
And also updated the truncated description.
** Patch added: "bluez_5.48-0ubuntu3.5.debdiff"
https:/
** Description changed:
[Impact]
- * only impact Bionic machines because series after Bionic already
- included this patch.
+ This patch is for this issue:
+ steps:
+ 1. pair bluetooth keyboard
+ 2. see the dialog asking user input the code for pairing.
+ 3. press "esc" to cancel it.
+ 4
sorry for bad habit that I miss-understanded before.
I revised it and put detail information there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1887910
Title:
[bionic]blutoothd segfau
It shouldn't be long that Ubuntu 20.04 kernel gets it from upstream.
--
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/1882823
Title:
int3403 thermal INT3403:00
Status in linux package in
The patch was meraged to 5.4 stable 5 hours ago -
=
This is a note to let you know that I've just added the patch titled
thermal: int3403_thermal: Downgrade error message
to the 5.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux
Since the workaround involves amd's iommu and kernel 5.5, we may be able
to find a patch that fixes this by cherry-pikcy: git log --pretty=short
v5.4..v5.5 -- drivers/iommu/amd_iommu.c
commit 1daa56bcfd8b329447e0c1b1e91c3925d08489b7
Merge: a5255bc31673 9b3a713feef8
Author: Linus Torvalds
Mer
A test kernel, based on UBUNTU: Ubuntu-5.4.0-42.46, is available @
https://people.canonical.com/~alexhung/LP1887218/ver1/
If this solves this bug, we can keep bisecting. If not, we can try other
patches.
The following commits are excluded:
== merges ==
1daa56bcfd8b329447e0c1b1e91c3925d08489b7
99
** Tags added: originate-from-1888359 timbuktu
--
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/1872383
Title:
blk_update_request error when mount nvme partition
Status in OEM Priority Pr
PCI(e) is capable of correcting errors whenever possible. From your logs
all of the errors are corrected and therefore nothing to worry about.
If you see incorrectable errors you may observed device failures, or
system failures in some cases.
--
You received this bug notification because you are
When a PCIe AER error is captured, an error message will be output to
console. If it's a correctable error, it is output as a warning.
Otherwise, it is printed as an error. So users could choose different
log level to filter out correctable error messages.
==
** Changed in: bluez (Ubuntu Bionic)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1887910
Title:
[bionic]blutoothd segfault when you cancel the
It's seems not just one patch can fix this issue. I found another corner
case that still can trigger a blutoothd segmentation fault.
I pair one Bluetooth keyboard but cancel before input pairing keycode.
Before timeout of latest keyboard pairing, I pair another Bluetooth
keyboard and still cancel
The errors comes from physical layer so they likely comes from the root
port (00:1d.0) or the device attaches to it. Also, PCIe correctable
errors are handled by hardware, so one can turn off some hardware-
related features, such as apsm (pcie_aspm=off) or msi (pci=nomsi), to
verify whether there a
Please try mainline kernels (https://kernel.ubuntu.com/~kernel-
ppa/mainline/), for example, 5.8rc6.
If it works, please try 5.6 and then repeat bisecting.
This can help identify whether fixes are available and what fix is.
--
You received this bug notification because you are a member of Kerne
Thanks for reporting this, and your help is needed to identify the patch
that causes this regression.
There are 260 patches between 5.3.0-61 & 5.3.0-62, and it requires some
testing with bisects (see below).
$ git bisect start
$ git bisect good Ubuntu-5.3.0-61.55
$ git bisect bad Ubuntu-5.3.0-62.
Correction to #19. The kernel is available @
https://people.canonical.com/~alexhung/LP1888570/19357b3b0835/
--
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/1888570
Title:
poweroff not wor
Had the exact same error today. Was able to solve it via:
sudo ubuntu-drivers autoinstall
then rebooting.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
https://bugs.launchpad.net/bugs/1888617
Title
*** This bug is a duplicate of bug 1810183 ***
https://bugs.launchpad.net/bugs/1810183
You may need to report this to upstream or even to ASUS to support this
device. Vendor may decide to support it on Linux with enough request.
** This bug has been marked a duplicate of bug 1810183
numpad
@gneiss,
Thanks. Next one is
https://people.canonical.com/~alexhung/LP1888570/d37a638086c1/
--
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/1888570
Title:
poweroff not working after apt
It is odd that lspci shows you have a Qualcomm Atheros QCA9377 with
driver ath10k_pci, but dmesg shows nothing about ath10k as QCA9377 never
exists.
Can you run lspci -v to confirm QCA9377 and run "sudo modprobe -r
ath10k_pci ; sudo modprobe ath10k_pci" to unload and reload wifi driver.
Also run d
You can also update linux-firmware (from
http://security.ubuntu.com/ubuntu/pool/main/l/linux-firmware/) and / or
update system BIOS (do it with cautions).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Thanks. Next one is
https://people.canonical.com/~alexhung/LP1888570/0affe1fa22b2/
--
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/1888570
Title:
poweroff not working after apt upgrade
S
@gneisss,
I forgot to remove to *tool*.deb. They aren't needed.
next one: https://people.canonical.com/~alexhung/LP1888570/115f51d0fa11/
--
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/188
#19 and forward assume kernel 5.3.0-61 is good, according to bug
description; however, it may worthwhile to give it:
https://people.canonical.com/~alexhung/LP1888570/Ubuntu-5.3.0-61.55/
Especially, all tries were bad kind of worrying...
If it is good, the next one is
https://people.canonical.com/
Performance degrades can also related to power saving. Try kernel
parameter "pcie_aspm=off" to verify whether it improves
--
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/194
Title:
Qu
The ACPI's lid device "LID0" is not listed in /proc/acpi/wakeup, and it
can be the result of missing "_PRW" object in ACPI BIOS. It has only
_HID, _LID and _DSW objects such as below (extracted from acpidump.txt).
Device (LID0)
{
Name (_HID, EisaId ("PNP0C0D")
Method (_LID, 0,
This is a BIOS issue and a fix is required from OEM and is not from
Ubuntu.
--
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/1898949
Title:
ThinkBook 14-IIL can't wake from sleep by openin
Did you try "systemd-analyze time" or "systemd-analyze blame" to
identify the boot-time's bottleneck?
--
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/1898878
Title:
Ubuntu slow boot
Stat
_PRW requires knowledge of the hardware pin used for wake-up by lid, and
this is not available outside vendor themselves. We can, however, just
make a guess such as below
Method (_PRW, 3, NotSerialized)
{
Return (Package () {9, 3})
}
The attached is a patch for DSDT
You can force to use s2idle instead of deep (s3). This might force the
system as in #5.
command: $ echo s2idle | sudo tee /sys/power/mem_sleep
If this works for you, this is a better solution than patching DSDT.
--
You received this bug notification because you are a member of Kernel
Packages,
@azis-naufal,
#15 is where _PRW goes indeed, but my guess was wrong...
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
A post at Dell's forum has a workaround solution using a kernel
parameter "snd_hda_intel.dmic_detect=0".
https://www.dell.com/community/Linux-General/Freezing-boot-
Ubuntu-20-04-Dell-G3-3590/m-p/7667770/highlight/true#M17469
--
You received this bug notification because you are a member of Kerne
I don't think amdgpu's actual_brightness works in the first place.
Did you try any of the following kerenl parameters?
acpi_backlight= [HW,ACPI]
acpi_backlight=vendor
acpi_backlight=video
If set to vendor, prefer vendor specific driver
(e.g.
601 - 700 of 1851 matches
Mail list logo
