This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1902162
Title:
Keyboard doesn't work after
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Hi team,
I upgrade Ubuntu from 20.04 to 20.10 and my keyboard doesn't work;
Computer model: ASUS X556UQK
Actual kernel 5.8.0-26-generic
I can't fix it yet; Do you know any solution to do?
Thanks
Regards
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package:
I would like to report back that on Ubuntu 20.04 with Intel AX200
network card (8087:0029), I resolved this issue by following @Hui Wang's
instruction
ibt-20-1-3.sfi and ibt-20-1-3.ddc from 20.10 driver
HSP/HSF was greyed out before but is now available and functioning after
powering off and on
We probably still need some information about the hardware. Please
either:
* Use a USB keyboard; or
* Use a kernel version that works
and then run:
apport-collect 1902156
** Summary changed:
- keyboard and touchpad don't work on kernel 5.8.0.26
+ keyboard and touchpad don't work on
I am running into the boot hang again, this time on xubuntu 20.10 and
only when `modprobe.blacklist=ath11k,ath11k_pci,btqca,hci_uart` is *not*
included.
** Attachment added: "output from journalctl on xps 13 9310 using
5.8.0-2026.27+lp1879633.2 and 5.9.0-2002.3+lp1879633.2"
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1902156
Title:
keyboard and touchpad don't work on kernel 5.8.0.26
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1902156
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
when I updated my system to ubuntu 20.10, the keyboard and mouse no
longer worked after a little investigation, I found out the kernel
causes this problem, downgrading to linux 5.4 or upgrading to linux
kernel 5.8.11 solved this issue, I also found that this problem is
*** This bug is a duplicate of bug 1902118 ***
https://bugs.launchpad.net/bugs/1902118
** This bug has been marked a duplicate of bug 1902118
ubuntu_ltp_syscalls: kill11 sub-test is always failing (timing out)
--
You received this bug notification because you are a member of Kernel
1) originally we use speaker-test to test HDMI/DP/Legacy, failed on
Ubuntu 20.10. with 5.9 official kernel, works fine.
2) now we change to another method to test audio, works well.
Summary:
Seems test tools has some issue.
5.9 official kernel support speaker-test, but in 5.8 (ubuntu 20.10),
Ah thanks, I was forgetting to install linux-modules-extra-* which is
what caused all the hardware to fail. I appreciate your assitance and
appolgize for the unrelated problem. Let me know if there are any other
pieces of information or things I can do to help further support
remediation of the
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1902154
Title:
Touchpad Not Detected
Status
Public bug reported:
I installed Ubuntu on my new laptop, but the touchpad isn't working so I
have to use a USB mouse.
The laptop is a Lenovo IdeaPad 3 15"
The model number is 81WE011UUS
I followed the instructions here but did not see any touchpad related devices
listed
@vicamo `sudo apt-get install linux-firmware linux-headers-5.8.0-2026
linux-modules-5.8.0-2026-generic linux-image-unsigned-5.8.0-2026-generic
linux-headers-5.9.0-2002-generic linux-modules-5.9.0-2002-generic linux-
image-unsigned-5.9.0-2002-generic` should be sufficient, no?
** Attachment
I have reinstalled with a fresh copy of Ubuntu 20.10 and tested both
5.8.0-2026.27+lp1879633.2 and 5.9.0-2002.3+lp1879633.2.
While I am no longer experiencing the boot hang I was previously
experiencing I am still running into the secondary issue where the
system fails to load any hardware
** Description changed:
- The patchset in
-
https://lore.kernel.org/lkml/20201006224702.12697-1-david.e@linux.intel.com/
- provides several critical fixes for intel_pmc_core driver, one is
- specific for Tiger Lake.
+ [Impact]
+ The power gating status is not correct and the slp_s0 value is
hi, you must install linux-modules-* as well. Or, you may fail to locate
your rootfs and get a emergency shell in initramfs stage. It's not a
boot hang.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
** No longer affects: linux (Ubuntu Focal)
** No longer affects: linux-oem-5.6 (Ubuntu Groovy)
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux-oem-5.6 (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1902110
Title:
Focal update: v5.4.71 upstream stable
Hi sorry, please ignore #28 as the test system I setup was booting from
an SD card. (I didn't want to re-partition or swap out my SSD) This
seemed to cause this new error since these kernels couldn't find the SD
card like the stock one could.
I will resetup my fresh test install on a brand new
Hi - commit 411a139d84bd34931e0e01d6ed5e48a718392e5d added
svm_xsaves_support, but AFAICT support for virtualizing the IA32_XSS MSR
on SVM was not merged back from upstream. Commit
864e2ab2b46db1ac266c46a7c9cefe6cc893029d added this support upstream and
was a parent of 411a13.
This means QEMU-KVM
I've also attached the system information. I will attempt booting again
this time with `5.9.0-2002.3+lp1879633.2` and share the results from
that with and without the modprobe.blacklist
** Attachment added: "System Information for the XPS 13 9310 from the "Help
Improve Ubuntu" prompt after
Initial test with a fresh install of Ubuntu 20.10
Added https://gist.github.com/maxried/796d1f3101b3a03ca153fa09d3af8a11
to sign kernel images for secureboot
Updated `/etc/default/grub` to include the kernel parameters mentioned
Added both ppa repos
Ran `sudo apt-get install linux-firmware
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1902150
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Hello,
I recently updated to Linux Mint Kernel 4.15.0-122 and now my machine
will not play sound out of headphones. It plays sound out of the built
in speakers. It recognizes that there is a headphone jack inputted into
the machine when there is one - but no sound emits.
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Public bug reported:
Issue occurred shortly after login without doing anything.
ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: linux-modules-5.8.0-26-generic 5.8.0-26.27
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion:
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1902141
Title:
package
In my case volume levels are good on both 20.10 and 20.04.
Consider that the alsa-ucm-conf parameters upstream for chtmax98090 are based
on my hardware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/1902096
Title:
Xenial update: v4.4.240 upstream stable
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/1902097
Title:
Xenial update: v4.4.241 upstream stable
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
er, autocorrection. It's:
modprobe.blacklist=ath11k,ath11k_pci,btqca,hci_uart
--
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/1879633
Title:
Killer 500s (QCA6390) WLAN/BT
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
I'll see if we happen to have one such model (XPS 13 9310) in the
convenient store nearby tomorrow. ;)
--
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/1879633
Title:
Killer 500s
It would be nice if you can boot with additional kernel parameters:
ath11k.debug_mask=0x debug ignore_loglevel log_buf_len=32M
You can dump system journal log of a previous boot with `journalctl -b
-1`, or `journalctl -b -2` for a even more earlier one, and so on.
Please attach the
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/1902095
Title:
Xenial update: v4.4.239 upstream stable
I installed 20.10 on my Dell Chromebook 3120 and then installed alsa-
ucm-conf from https://packages.debian.org/testing/alsa-ucm-conf and got
working sound. (Thanks for the tips @Gabirele)
The volume was very low initially and i had to use alsamixer to increase
it. But even after i increase the
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
I am using an XPS 13 9310, Core i7-1165g7 with 32GB of RAM. Initially I
tested on a fresh install of Ubuntu 20.04 and kernel
`5.6.0-2032.33+lp1879633.2` from your PPA, this caused the system to
hang on boot.
I then remove this and the firmware, upgraded to 20.10 and had the same
results with
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Patch backport to stable:
https://www.spinics.net/lists/stable/msg423555.html
** Changed in: curtin (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
No touchpad is showing Up after giving xinput list
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: wl
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1902107
Title:
xinput list Not showing any
** Description changed:
- When installing the 5.9 kernel with bcmwl6.30.223.271+bdcom package, the
- process fails to build the module.
-
+ When installing the 5.9 kernel with bcmwl6.30.223.271+bdcom package on
+ focal, the process fails to build the module.
Below is the build log:
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
With the above patch applied, we can see the culprit directories:
$ sudo find /sys/firmware/efi/vars/ -type d | grep \!
/sys/firmware/efi/vars/Pwr!Perf Profiles-7683c190-9523-4402-81ff-a11e93dc389c
/sys/firmware/efi/vars/Intel(R) VT for Directed I!O
(VT-d)-7683c190-9523-4402-81ff-a11e93dc389c
Public bug reported:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was
What platform/model were you testing? I didn't meet any boot hang during
the development. Logs available?
5.9.0-2002.3+lp1879633.2 is the one closest to ath-202010011934, so
probably that means there are some backport regressions introduced in
other versions, and thus need more regression tests
Like the last line suggested, that's harmless if your linux box has no
secureboot enabled currently. If so, you need to enroll your own key in
BIOS, and use it to sign your own build of kernel modules. See
https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS.
** Changed in: linux (Ubuntu)
Status:
--- Comment From mihaj...@de.ibm.com 2020-10-29 09:59 EDT---
With 2G, the crashkernel reservation will be 320K, which will not suffice to
unlock the LUKS volume when processing kdump. The installation was done using
2G.
Changing the VM size to 4+G will reserve 512K, and with this size
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1902083
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
make && sudo make install
Building v4l2-loopback driver...
make -C /lib/modules/`uname -r`/build
M=/home/rama/Downloads/VirtualWebcam/v4l2loopback modules
make[1]: Entering directory '/usr/src/linux-headers-5.8.0-25-generic'
make[1]: Leaving directory
I restarted forcing primer-select nvidia and the problem goes back. Attaching
journalctl of that boot here
I rebooted in recovery mode and run nvidia-smi again in text console and the
driver this time is there with no complaints as before (nvidia-smi
NVIDIA-SMI has failed because it couldn't
** Attachment added: "last reboot with the both cards recognized but no nvidia
in use"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901947/+attachment/5429000/+files/journalctl.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
I restarted with nvidia and the card is back but the drivers do not
work. Currently driver 455 is selected to be used but the primary
selection is intel (see below)
alvaro@alv-leno ~ % lspci -k | grep -EA3 'VGA|3D|Display'
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630
I think 512M for a 2GB system is a little too much to reserve. Can you
double check the details of that LUKS partition? Was it created during
an installation with a 2GB system? Or did you reduce the VM size after
installation?
Can you send the output of cryptsetup luksDump /dev/XXX?
Thanks.
The verification of the Stable Release Update for nvidia-graphics-
drivers-455 has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
I have updated the bios (used WinToUSB to install Win10 on an external
SSD, it works amazingly well). Unfortunately the error messages persist.
As the laptop does work (did not test 3D gaming yet, will do next week)
I suppose I should just ignore the messages.
--
You received this bug
Public bug reported:
perf support for Rocket Lake needs this series
https://lore.kernel.org/patchwork/patch/1322440/
which is targeted for 5.11
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Timo Aaltonen (tjaalton)
Status: Triaged
** Changed in: linux (Ubuntu)
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1902001
Title:
USB keyboard layout incorrect
Public bug reported:
Description:Ubuntu 20.04.1 LTS
Release:20.04
Kernel version: 5.4.0-52-generic (but problem began with 5.4.0-51-generic)
Keyboard: Bus 001 Device 018: ID 056e:1063 Elecom Co., Ltd ELECOM
TK-FCP097
Expected behaviour:
USB keyboard layout remains the same
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1901994
Title:
Touchpad not working
Status
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) =>
Public bug reported:
Hello,
I bought a new Lenovo Yoga Slim 7 and installed Ubuntu 20.04 on it.
Unfortunately my touchpad stopped working and is not even recognized as input
device (see attached device file). I would appreciate any hints as to how to
solve this issue.
Thank you!
Best regards,
The crash is random and not too often but if I turn off "wi-fi can be
turn off to power save": all wi-fi crash all time
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1897942
The problem persists with the newest image from the 27th...
--
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/1898808
Title:
[maas][focal]unable to deploy 20.04(focal) w/ default kernel
** Description changed:
[Impact]
Realtek 8821C Bluetooth controller may stop working after S3.
[Fix]
- Use the new firmware from Realtek.
+ Use the new firmware from Realtek (Release Version: 0xAA6C_A99E)
Link:
Jeff,
As we have already posted the patch set to upstream, so the target
upstream kernel version is the next upcoming kernel which is 5.11.
Yes we want you to back port this patch set into 5.4 kernel.
Thanks,
Sreekanth
--
You received this bug notification because you are a member of Kernel
83 matches
Mail list logo
