** Tags added: certified
** Tags removed: certified
** Tags added: ubuntu-certified
--
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/2002757
Title:
Dell precision 5560 screen can't back
I'm not sure this will get fixed for 5.17 at this point, we're already
planning to move to oem-6.1 and EOL 5.17 & 6.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
** Tags added: kern-5334
--
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/2002601
Title:
Wireless: Enable RTL8852BE wifi driver
Status in HWE Next:
New
Status in linux package
Public bug reported:
In OEMKernel wiki(https://wiki.ubuntu.com/Kernel/OEMKernel), How to install is
documented, but how to uninstall OEMKernel or back to the generic kernel?
It's not documented.
Maybe that's why this issue is fired:
https://ubuntuforums.org/showthread.php?t=2470860
And I also
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 2002757
and then change the status of the bug to 'Confirmed'.
If, due to the
@tjaalton: Added logs for 1 working and 2 non-working versions. It
seems like there has been quite a lot of churn in the amdgpu driver
between 5.17 and 6.0. Hope this helps narrow down the problem commits.
--
You received this bug notification because you are a member of Kernel
Packages, which
Log from booting 6.0.0-1010-oem - non-viable due to what appears to be
an instance of
https://bugs.launchpad.net/ubuntu/kinetic/+source/linux/+bug/1995956 or
a related bug. Errors start at line 1202. The 80 minutes which it took
for this bug to surface while using Slack is the longest this
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Log from booting 5.17.0-1026-oem - this is the kernel that blanks the
screen and is thus unusable. Note the amdgpu errors beginning at line
961 which do not appear in the 5.17.0-1025-oem log.
** Attachment added: "kern.log-5.17.0-1026-oem"
Log from booting 5.17.0-1025-oem - this is the kernel that works
correctly.
** Attachment added: "kern.log-5.17.0-1025-oem"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641119/+files/kern.log-5.17.0-1025-oem
--
You received this bug notification because
lspci -vvnn output
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641118/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen 3 blank laptop screen on bootup
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen 3 blank laptop screen on bootup
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in
Noticed that among the many tips of the day, LibO also suggests to use
Android or IPhone to remotely control an Impress presentation. The
"more info" page then excplicitly declares that the feature is cross
platform "GNU/Linux, Windows or macOS." either via Bluetooth or Wifi.
However to use the
** Tags added: originate-from-2000769 sutton
** Tags added: originate-from-2001905
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2002373
Title:
Mic Mute LED doesn't work on
*** This bug is a duplicate of bug 1968040 ***
https://bugs.launchpad.net/bugs/1968040
** This bug has been marked a duplicate of bug 1968040
Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument
invalide] [drmModeAtomicCommit: Invalid argument]
--
You received
Public bug reported:
The screen can't back on after suspend.
Here is the kernel log error:
[84090.414190] Asynchronous wait on fence :00:02.0:gnome-shell[2816]:1c469c
timed out (hin t:intel_atomic_commit_ready [i915])
[84090.414462] Asynchronous wait on fence
*** This bug is a duplicate of bug 1968040 ***
https://bugs.launchpad.net/bugs/1968040
I have a similar problem using an external HDMI monitor connected to a
laptop.
It happens with the blank screen after a period of inactivity (without
using the screen lock).
After the screen has gone
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1978986
Title:
[SRU][J/OEM-5.17][PATCH 0/1]
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1995041
Title:
Fix ath11k deadlock on
Gave up - came down to a decision between the machine and Linux. New
machine ordered, Linux staying :)
--
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/1914881
Title:
No sound from
Yes it is discussed in:
https://gitlab.freedesktop.org/drm/amd/-/issues/2135
--
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/1980831
Title:
GUI freezes randomly, kernel:
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1998224
Title:
pcie hotplug not working in linux-generic-hwe-18.04
As I already told in my case the issue is solved.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/1970074
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 2002748
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
d
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-kernel-source-525-open 525.60.11-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
Public bug reported:
Under heavy disk usage, such as backing up the disk to another drive, I
get the error:
[137133.774493] BUG: unable to handle page fault for address: 4164
[137133.774507] #PF: supervisor read access in kernel mode
[137133.774512] #PF: error_code(0x) -
Hi, any work around to this topic? I've also tried latest kernels, but no
improvement.
I have ROG Strix with Nvidia RTX3060 and AMD Radeon Rembrandt and I have the
same error with the exact same symptoms and that makes Linux unusable.
--
You received this bug notification because you are a
> I think the main use case is to bootstrap cloud images so that they
can then install other kernels as quickly as possible, right?
This is incorrect. the linux-kvm kernel is lightweight kernel meant for
minimal applications running in virtualized environments. The only image
it is present on
Public bug reported:
hf
ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: linux-generic-hwe-22.04 5.19.0.29.26
ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
Uname: Linux 5.19.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
** 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/2002353
Title:
Problem with Goodix i2c touch screen
Status in linux
Public bug reported:
SRU Justification:
[Impact]
This is a porting commit from
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1927253.
[Fix]
* N/A
[Test Case]
* Set DISPLAY_LEVEL to 1 in /dev/rshim0/misc and do 'cat /dev/rshim0/misc' from
external rshim driver.
The
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
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/1996071
Title:
[UBUNTU 20.04] boot: Add s390x secure
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
Public bug reported:
[ Impact ]
In order to use the same compiler as used for kinetic:linux (gcc-12) we have
made some changes to explicitly compile jammy:linux-hwe-5.19 with the same
compiler. These changes were mainly part of bug 1999750 and bug 1991664.
However, such changes are breaking
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
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
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
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
the same with -5.15.0-58-generic as 5.15.0-57-generic.
--
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/1998285
Title:
5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
Status in linux
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
Thank you for letting us know what's going and please do continue to
keep us posted.
Laurie
--
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/1988711
Title:
Update Broadcom Emulex FC HBA
Hi Ketan,
Thanks for this. I'm waiting on advice from the kernel team now.. I'm not
sure if I should send a PR based on the branch I patched using your patch
set, or if I should just send the patch set directly to the kernel team ML
for consideration. Indeed I was able to successfully apply all
Public bug reported:
Ubuntu 22.10 riscv64 image on lichee rv board with 3 HDDs attached, 2 in
a mirrored zpool, 1 standalone zpool, rsync copying data from single
pool to mirrored pool.
[Thu Nov 17 02:45:26 2022] Unable to handle kernel access to user memory
without uaccess routines at virtual
** Description changed:
Ubuntu 22.10 riscv64 image on lichee rv board with 3 HDDs attached, 2 in
a mirrored zpool, 1 standalone zpool, rsync copying data from single
pool to mirrored pool.
[Mon Nov 14 10:05:09 2022] Unable to handle kernel NULL pointer dereference
at virtual address
Public bug reported:
RM obsolete unsupported and no longer used v5.17 kernels
** Affects: linux-allwinner-5.17 (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: linux-meta-oem-5.17 (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: linux-oem-5.17
Public bug reported:
Ubuntu 22.10 riscv64 image on lichee rv board with 3 HDDs attached, 2 in
a mirrored zpool, 1 standalone zpool, rsync copying data from single
pool to mirrored pool. Source pool was using skein. Destination was
using the default.
[Tue Nov 15 15:04:51 2022]
Unable to handle
Our vendor told us that this is a generic problem with the following
supermicro board/system and many nvme ssd devices:
Board: H12SSW-NT
Servertype: Supermicro AS -1114S-WTRT
https://www.supermicro.com/Aplus/system/1U/1114/AS-1114S-WTRT.cfm
so it seems this is not kernel related, afaik.
--
** Description changed:
Ubuntu 22.10 riscv64 image on lichee rv board with 3 HDDs attached, 2 in
a mirrored zpool, 1 standalone zpool, rsync copying data from single
pool to mirrored pool.
[Sun Nov 13 06:41:10 2022] Unable to handle kernel NULL pointer dereference
at virtual address
** Summary changed:
- NULL pointer dereference
+ NULL pointer dereference in abd_copy_to_buf_off
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2002665
Title:
NULL pointer
Public bug reported:
Ubuntu 22.10 riscv64 image on lichee rv board with 3 HDDs attached, 2 in
a mirrored zpool, 1 standalone zpool, rsync copying data from single
pool to mirrored pool.
[Sun Nov 13 06:41:10 2022] Unable to handle kernel NULL pointer dereference at
virtual address
Public bug reported:
Ubuntu 22.10 riscv64 image on lichee rv board with 3 HDDs attached, 2 in
a mirrored zpool, 1 standalone zpool, rsync copying data from single
pool to mirrored pool.
[Mon Nov 14 10:05:09 2022] Unable to handle kernel NULL pointer dereference at
virtual address
Public bug reported:
SRU Justification
[Impact]
Support for Intel TDX guest driver is just now appearing upstream. This
patch set is a backport of the patches essential to enabling TDX guest
support on the Microsoft hypervisor.
Most of these patches are not yet upstream, but are considered
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5641006/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5641005/+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.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5640997/+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/2002353
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5641000/+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/2002353/+attachment/5641001/+files/ProcCpuinfoMinimal.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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5641003/+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/2002353/+attachment/5641004/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5641002/+files/ProcInterrupts.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-vt.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5640996/+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: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5640999/+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: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5640998/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5640995/+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/2002353
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5640994/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5640993/+files/CurrentDmesg.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: "CRDA.txt"
https://bugs.launchpad.net/bugs/2002353/+attachment/5640992/+files/CRDA.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/2002353
apport information
** Tags added: apport-collected focal
** Description changed:
I have no-name tablet with goodix touch screen which not work in any
version of Ubuntu. Currently I work with 20.04 LTS and kernel
5.15.0-56-lowlatency.
It reports into dmesg:
Goodix-TS
new debdiff for jammy (v2) with the proper changelog entry.
** Patch added: "bcmwl-support-5.19-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1981968/+attachment/5640985/+files/bcmwl-support-5.19-v2.debdiff
--
You received this bug notification because you are a member of
```
$ lspci -nnk | grep 0280 -A3
03:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723]
(rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
$ lsusb -d 8087:
Bus 001 Device 004:
Created attachment 303581
btmon -p 7 -i hci0 -w hcidump
This is BTSnoop file. Collected disconnection errors.
file hcidump
hcidump: BTSnoop version 1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 112 matches
Mail list logo
