[Kernel-packages] [Bug 1907421] Re: [UBUNTU 21.04] vfio: pass DMA availability information to userspace
The fix is currently prepared for focal based on LP 1913487 - "Focal update: v5.4.90 upstream stable release" https://bugs.launchpad.net/bugs/1913487 Hence aligning the status of the focal entry of this bug to LP1913487 and updating the status to In Progress. ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: ubuntu-z-systems Status: Confirmed => In Progress -- 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/1907421 Title: [UBUNTU 21.04] vfio: pass DMA availability information to userspace Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: Description: vfio: pass DMA availability information to userspace Symptom: vfio-pci device on s390 enters error state Problem: Commit 492855939bdb added a limit to the number of concurrent DMA requests for a vfio container. However, lazy unmapping in s390 can in fact cause quite a large number of outstanding DMA requests to build up prior to being purged, potentially the entire guest DMA space. This results in unexpected errors seen in qemu such as 'VFIO_MAP_DMA failed: No space left on device' Solution: The solution requires a change to both kernel and qemu - For the kernel, add the ability to provide the number of allowable DMA requests via the VFIO_IOMMU_GET_INFO ioctl. Reproduction: Put a vfio-pci device on s390 under I/O load Upstream-ID: a717072007e8aedd3f951726d8cf55454860b30d 7d6e1329652ed971d1b6e0e7bea66fba5044e271 Need also to be integrated into 20.10 and 20.04. OK, just to clarify we don't need to fix bionic for this one, but rather focal (20.04) and groovy (20.10). Furthermore, for 20.04, 20.10 and 21.04 ONLY commit 7d6e1329652ed971d1b6e0e7bea66fba5044e271 is needed, the other was a pre-req that is already present. __ SRU Justification: [Impact] * In case a vfio-pci device on s390x is under I/O load, vfio-pci device may end up in error state. * The commit 492855939bdb added a limit to the number of concurrent DMA requests for a vfio container. * However, lazy unmapping in s390x can in fact cause quite a large number of outstanding DMA requests to build up prior to being purged - potentially the entire guest DMA space. * This results in unexpected errors seen in qemu such as 'VFIO_MAP_DMA failed: No space left on device'. * The solution requires a change to both kernel and qemu. * The kernel side of things is addressed by this SRU. * The fix adds the ability to provide the number of allowable DMA requests via VFIO_IOMMU_GET_INFO ioctl. * The actual fix comes with commit 7d6e1329652e, but another fix ccd59dce1a21 is needed to get it cleanly applied. [Fix] * ccd59dce1a21f473518bf273bdf5b182bab955b3 ccd59dce1a21 "vfio/type1: Refactor vfio_iommu_type1_ioctl()" * 7d6e1329652ed971d1b6e0e7bea66fba5044e271 7d6e1329652e "vfio iommu: Add dma available capability" [Test Case] * IBM Z or LinuxONE hardware with Ubuntu Server 20.10 installed. * PCIe adapters in place that provide vfio, like RoCE Express 2. * A KVM host needs to be setup and a KVM guest (use again 20.10) that uses vfio. * Generate I/O that flows through the vf and watch out for error like 'VFIO_MAP_DMA failed: No space left on device' in the log. [Regression Potential] * The first patch ccd59dce1a21 modifies the common code file drivers/vfio/vfio_iommu_type1.c quity significantly. * But the reason is not that it introduces a lot of new things, it's a refactoring patch. * Nevertheless if done in a bad way it can significantly harm the IO memory management of virtual function adapters. * In worst case it may break them entirely, instead of 'just' exeeding the entire DMA space. * Things could also go wrong while doing the mapping and unmapping of DMA, that may even have an impact beyond vf adapters - harming other DMA devices. * The handling of dirty pages is also touched and the ioctl itself - which is important to keep the control of the devices. * But as said before, it re-factoring work, it's upstream accepted since 5.9 and the provenance shows that many engineers had an eye on these changes. * The second patch 7d6e1329652e - that inclides the needed fix - comes with far less modifications. * It also tounches drivers/vfio/vfio_iommu_type1.c but in a way that it mainly add one new function (vfio_iommu_dma_avail_build_caps) and an add. if statement in vfio_iommu_type1_get_info. * That allows to
[Kernel-packages] [Bug 1684240] Re: Lagging square around mouse pointer
I have this problem in Ubuntu Focal 20.4 installed on an iMac 21.5' mid-2010 with a Radeon ATI card. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1684240 Title: Lagging square around mouse pointer Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in plasma-workspace package in Ubuntu: Confirmed Bug description: (This can also be an nvidia related problem) Mouse pointer behaves as if it has an invisible square attached to it. This square covers some area next to the pointer, but it is not always clear exactly where (a link to a screenshot is shown below, please note the white square with some text from the previous webpage displayed in that window). This makes selecting text difficult, as one never knows where exactly the selection ends. Also, scrolling in some windows becomes problematic, as the pointer shadows a part of the scrollbar. When a text is being typed, one needs to make sure that the pointer is parked sufficiently far from the text (so, to make a long story short, this is very annoying). This behavior does not depend on the choice of the cursor theme. (A link to the screenshot: https://goo.gl/photos/92KKGyFs3AkdxYb79) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: plasma-workspace 4:5.9.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 19 10:41:58 2017 InstallationDate: Installed on 2015-06-05 (684 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: plasma-workspace UpgradeStatus: Upgraded to zesty on 2017-04-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1684240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857821] Re: External HDMI monitor audio always reported as "unplugged"
[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. https://bugs.launchpad.net/bugs/1857821 Title: External HDMI monitor audio always reported as "unplugged" Status in linux package in Ubuntu: Expired Bug description: Hello my Ubuntu friends, I can no longer play sound over my external HDMI connected TV. The image displays perfectly, but all the HDMI output devices are listed as "unplugged" I have spent a huge amount of time trying every solution that Internet searching will bring but this has changed nothing. I have tired all available video drivers, including Xorg and NVIDEA 396.26, 340.107, and 384.130. This failure is recent because in the past I could play both audio and video through the HDMI connector. The laptop is dual boot with Windows 10 and the HDMI works perfectly on that OS, although I rarely use it... I am wondering if upgrading my Xubuntu to the latest LTS could potentially solve this issue, but I fear such an update since I depend on this computer and an outage would be very hard for me... Any thoughts would be great. Thanks for making Linux great! Bob ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Dec 29 17:00:14 2019 InstallationDate: Installed on 2015-05-11 (1693 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891502] Re: tpm tpm0: Error (28) sending savestate before suspend
[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. https://bugs.launchpad.net/bugs/1891502 Title: tpm tpm0: Error (28) sending savestate before suspend Status in linux package in Ubuntu: Expired Bug description: Upon clicking suspend via Log Out... button in Xubuntu and also via systemctl suspend, the screen turns to black for 2 sec but then brings me back to log in screen instead of suspending. This was not an issue in 18.04. Currently on fresh install of 20.04.1. Aug 13 08:12:59 laptop kernel: [87528.628302] PM: suspend entry (s2idle) Aug 13 08:13:00 laptop kernel: [87529.250844] printk: Suspending console(s) (use no_console_suspend to debug) Aug 13 08:13:00 laptop kernel: [87529.250844] printk: Suspending console(s) (use no_console_suspend to debug) Aug 13 08:13:00 laptop kernel: [87529.555272] tpm tpm0: Error (28) sending savestate before suspend Aug 13 08:13:00 laptop kernel: [87529.555287] PM: __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x80 returns 28 Aug 13 08:13:00 laptop kernel: [87529.555292] PM: dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 28 Aug 13 08:13:00 laptop kernel: [87529.555296] PM: Device 00:01 failed to suspend: error 28 Aug 13 08:13:00 laptop kernel: [87529.929361] PM: Some devices failed to suspend, or early wake event detected Aug 13 08:13:01 laptop kernel: [87530.458095] PM: suspend exit Aug 13 08:13:01 laptop systemd[1]: systemd-suspend.service: Succeeded. 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 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: smrtalec 1174 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Aug 13 08:25:19 2020 InstallationDate: Installed on 2020-08-10 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Compaq 2510p Notebook PC PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=bf5ecda3-8bba-45a8-8f73-038836aa1952 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MSP Ver. F.30 dmi.board.name: 30C9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 75.28 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MSPVer.F.30:bd11/11/2011:svnHewlett-Packard:pnHPCompaq2510pNotebookPC:pvrF.30:rvnHewlett-Packard:rn30C9:rvrKBCVersion75.28:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP Compaq 2510p Notebook PC dmi.product.sku: KR918UT#ABA dmi.product.version: F.30 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907499] Re: Cheese says gives errors, cant use the webcam
[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. https://bugs.launchpad.net/bugs/1907499 Title: Cheese says gives errors, cant use the webcam Status in linux package in Ubuntu: Expired Bug description: webcam Creative NX pro is detected in lsusb but does not work. has worked in Ubuntu linux many years back. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 9 21:46:43 2020 InstallationDate: Installed on 2020-11-11 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUS All Series RelatedPackageVersions: cheese3.34.0-1ubuntu1 cheese-common 3.34.0-1ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2907 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2907:bd03/11/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-P:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914960] Re: no soundcard present with linux-image-5.8.0-43-generic
Please run `apport-collect 1914960` on the box as requested. `dmesg` & boot messages have not been supplied, at least not in a format allowing easy scannning. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1914960 Title: no soundcard present with linux-image-5.8.0-43-generic Status in linux package in Ubuntu: Incomplete Bug description: Beginning of February 2021 Ubuntu shipped a 3. time in a row (few months difference) a Kernel update that does not discover the onboard sound card. Same problem as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920 Booting back into linux-image-5.8.0-41-generic works. my on-board sound card & USB headset are well recognized! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869860] Re: Ubuntu mainline kernel v5.6 not supported by bcmwl-kernel-source
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with kernel version 5.6 or 5.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1869860 Title: Ubuntu mainline kernel v5.6 not supported by bcmwl-kernel-source Status in bcmwl package in Ubuntu: Confirmed Bug description: I am using Ubuntu 18.04 with kernel 4.15.0-91-generic and packet bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu5~18.04.1 from bionic-updates. Wifi BCM43228 802.11a/b/g/n [14e4:4359] is fine working. But working stops after installing ubuntu mainline kernel v5.6 (image, modules, headers-all, headers-amd64). While installing kernel there were error messages regarding dkms and no dkms-modul was built. bcmwl-kernel-source should support kernel v5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1869860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872908] Re: bcmwl kernel module does not build with kernel version 5.6 or 5.8
** Tags removed: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1872908 Title: bcmwl kernel module does not build with kernel version 5.6 or 5.8 Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Focal: Fix Released Bug description: After kernel update to 5.6.0-1007-oem wifi stopped working. Turned out dkms is unable to build the bcmwl module. The make log shows: ubuntu@ubuntu-inspiron-5482:~$ cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64) ons 15 apr 2020 09:19:05 CEST make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_reg_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ^~~ | ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: warning: returning ‘int’ from a function with return type ‘void *’ makes pointer from integer without a cast [-Wint-conversion] 949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size)); | ~^~~~ In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_set_auth_type’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5: warning: this statement may fall through [-Wimplicit-fallthrough=] 52 | if (wl_dbg_level & WL_DBG_DBG) { \ | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3: note: in expansion of macro ‘WL_DBG’ 816 | WL_DBG(("network eap\n")); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2: note: here 817 | default: | ^~~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_attach’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { |^~~ |ioremap_cache /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18: warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ)) == NULL) { | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_pci_probe’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 780 | if ((val & 0xff00) != 0) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 782 | bar1_size = pci_resource_len(pdev, 2); | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2), | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_reg_proc_entry’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58: error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type [-Werror=incompatible-pointer-types] 3376 | if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, _fops, wl)) == NULL) { | ^~~~ | | |
[Kernel-packages] [Bug 1914960] Re: no soundcard present with linux-image-5.8.0-43-generic
Apport as requested ** Attachment added: "apport with private information removed" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914960/+attachment/5461152/+files/apport.linux-headers-5.8.0-43-generic.61yjyl74.apport ** 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/1914960 Title: no soundcard present with linux-image-5.8.0-43-generic Status in linux package in Ubuntu: Confirmed Bug description: Beginning of February 2021 Ubuntu shipped a 3. time in a row (few months difference) a Kernel update that does not discover the onboard sound card. Same problem as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920 Booting back into linux-image-5.8.0-41-generic works. my on-board sound card & USB headset are well recognized! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910920] Re: no soundcard present with linux-image-5.8.0-37-generic
It happened again: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914960 -- 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/1910920 Title: no soundcard present with linux-image-5.8.0-37-generic Status in linux package in Ubuntu: Confirmed Bug description: With linux-image-5.8.0-34-generic, all on-board soundcards work flawlessly. After update of kernel to linux-image-5.8.0-37-generic durign this week no soundcards are detected. I am happy to provide more information. But I will not sent automatic apport reports because it includes private local data. !!DMI Information !!--- Manufacturer: LENOVO Product Name: 20BUS23M00 Product Version: ThinkPad T450 Firmware Version: JBET54WW (1.19 ) Board Vendor: LENOVO Board Name:20BUS23M00 !!Kernel Information !!-- Kernel release:5.8.0-34-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.8.0-34-generic Library version:1.2.3.2 Utilities version: 1.2.3 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xe123 irq 51 1 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe1234000 irq 52 !!PCI Soundcards installed in the system !!-- 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) Subsystem: Lenovo Broadwell-U Audio Controller [17aa:5034] 00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03) Subsystem: Lenovo Wildcat Point-LP High Definition Audio Controller [17aa:5034] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914949] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: focal -- 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/1914949 Title: Resume from suspend not working with i915 driver (linux 5.4 and 5.8) Status in linux package in Ubuntu: Confirmed Bug description: Using kernel 5.4.0-65, the system does not wake up anymore from suspend to ram (S3). The screen stays black, only the backlight comes on. Following the instructions in "wiki.ubuntu.com/DebuggingKernelSuspend", it shows that this PCI device is the problem: 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) This is a 1st gen Intel HD graphics (Ironlake) Testing various versions of kernels 5.4.0.x , I found that the problem seems to be introduced with 5.4.0-59 Versions after -59 don't wake up, and versions until 5.4.0-58 work fine. Testing 5.8.0-41, it doesn't wake up. Testing mainline 5.11.0-051100rc6-generic, it works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 HibernationDevice: RESUME=UUID=31673f7c-6b7f-4407-bc0b-e8f0652008be InstallationDate: Installed on 2018-09-11 (879 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=6de19ac7-7f66-4b39-a81f-3c955a60ae7a ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 Tags: ulyana Uname: Linux 5.4.0-65-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 05/25/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: HM55-HT dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd05/25/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM55-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914960] Missing required logs.
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 1914960 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: groovy -- 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/1914960 Title: no soundcard present with linux-image-5.8.0-43-generic Status in linux package in Ubuntu: Incomplete Bug description: Beginning of February 2021 Ubuntu shipped a 3. time in a row (few months difference) a Kernel update that does not discover the onboard sound card. Same problem as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920 Booting back into linux-image-5.8.0-41-generic works. my on-board sound card & USB headset are well recognized! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914960] [NEW] no soundcard present with linux-image-5.8.0-43-generic
Public bug reported: Beginning of February 2021 Ubuntu shipped a 3. time in a row (few months difference) a Kernel update that does not discover the onboard sound card. Same problem as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920 Booting back into linux-image-5.8.0-41-generic works. my on-board sound card & USB headset are well recognized! ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: groovy -- 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/1914960 Title: no soundcard present with linux-image-5.8.0-43-generic Status in linux package in Ubuntu: Incomplete Bug description: Beginning of February 2021 Ubuntu shipped a 3. time in a row (few months difference) a Kernel update that does not discover the onboard sound card. Same problem as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920 Booting back into linux-image-5.8.0-41-generic works. my on-board sound card & USB headset are well recognized! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914949] Re: Resume from S3 not working with i915 driver (linux 5.4 and 5.8)
** Package changed: ubuntu => linux (Ubuntu) ** Summary changed: - Resume from S3 not working with i915 driver (linux 5.4 and 5.8) + Resume from suspend not working with i915 driver (linux 5.4 and 5.8) -- 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/1914949 Title: Resume from suspend not working with i915 driver (linux 5.4 and 5.8) Status in linux package in Ubuntu: New Bug description: Using kernel 5.4.0-65, the system does not wake up anymore from suspend to ram (S3). The screen stays black, only the backlight comes on. Following the instructions in "wiki.ubuntu.com/DebuggingKernelSuspend", it shows that this PCI device is the problem: 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) This is a 1st gen Intel HD graphics (Ironlake) Testing various versions of kernels 5.4.0.x , I found that the problem seems to be introduced with 5.4.0-59 Versions after -59 don't wake up, and versions until 5.4.0-58 work fine. Testing 5.8.0-41, it doesn't wake up. Testing mainline 5.11.0-051100rc6-generic, it works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 HibernationDevice: RESUME=UUID=31673f7c-6b7f-4407-bc0b-e8f0652008be InstallationDate: Installed on 2018-09-11 (879 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=6de19ac7-7f66-4b39-a81f-3c955a60ae7a ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 Tags: ulyana Uname: Linux 5.4.0-65-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 05/25/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: HM55-HT dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd05/25/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM55-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914949] [NEW] Resume from S3 not working with i915 driver (linux 5.4 and 5.8)
You have been subscribed to a public bug: Using kernel 5.4.0-65, the system does not wake up anymore from suspend to ram (S3). The screen stays black, only the backlight comes on. Following the instructions in "wiki.ubuntu.com/DebuggingKernelSuspend", it shows that this PCI device is the problem: 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) This is a 1st gen Intel HD graphics (Ironlake) Testing various versions of kernels 5.4.0.x , I found that the problem seems to be introduced with 5.4.0-59 Versions after -59 don't wake up, and versions until 5.4.0-58 work fine. Testing 5.8.0-41, it doesn't wake up. Testing mainline 5.11.0-051100rc6-generic, it works fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 HibernationDevice: RESUME=UUID=31673f7c-6b7f-4407-bc0b-e8f0652008be InstallationDate: Installed on 2018-09-11 (879 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=6de19ac7-7f66-4b39-a81f-3c955a60ae7a ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 Tags: ulyana Uname: Linux 5.4.0-65-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 05/25/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: HM55-HT dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd05/25/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM55-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bot-comment ulyana -- Resume from S3 not working with i915 driver (linux 5.4 and 5.8) https://bugs.launchpad.net/bugs/1914949 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
I am having the same problem with an Apple Magic Trackpad 2, Ubuntu 20.04 and kernel 5.8.0-41-generic #46~20.04.1-Ubuntu SMP. [462154.113890] magicmouse 0005:004C:0265.00CE: unknown main item tag 0x0 [462154.114012] input: Apple Inc. Magic Trackpad 2 as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/bluetooth/hci0/hci0:768/0005:004C:0265.00CE/input/input253 [462154.114248] magicmouse 0005:004C:0265.00CE: input,hidraw2: BLUETOOTH HID v1.02 Mouse [André Brandão’s Trackpad] on 04:6c:59:0e:14:fa -- 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13
[Kernel-packages] [Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
I am having the same problem with an Apple Magic Trackpad 2, Ubuntu 20.04 and kernel 5.8.0-41-generic #46~20.04.1-Ubuntu SMP. -- 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/1385113 Title: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Message with Mouse Bluetooth [ 32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3344 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 24 05:22:54 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1385113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi Coiby To answer your question in message #359 > In hybrid mode, does external monitor work for you? The answer is yes, it works. I tested the hotplug of an HDMI external monitor, it was detected by Ubuntu 20.04 and worked by default as an extended desktop (both internal & external display used, not cloned). -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Update (based on #296) = The latest kernel tree (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) has the complete solution to fix this bug. So we can expect kernel v5.11 to fix this issue without any additional work. Before the release of v5.11, you are suggested to use #189 to save your touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd driver is built into the initramfs. So you have to rebuild the initramfs after replacing the old module with new one. On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs -u`. The complete solution is three patches, - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce filter setting in IRQ type setting") - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way to disable debounce filter") - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into account debounce settings") The first two patches has reached the stable tree. If the last one is also backported to LTS kernel, you won't need to install kernel 5.11. But I don't know when this will happen. Original bug report === Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10
[Kernel-packages] [Bug 1912928] Re: No network connectivity with kernel 5.8
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug is no longer a duplicate of bug 1912951 No network connectivity with kernel 5.8 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with kernel version 5.6 or 5.8 -- 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/1912928 Title: No network connectivity with kernel 5.8 Status in linux package in Ubuntu: Incomplete Bug description: Boot hangs temporarily, then there is no network connectivity after boot is complete. Problem occurs with all downstream versions of kernel 5.8. Loading older kernels at grub allows for a completely successful boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
#106 - please open a separate issue to debug this. The architecture for the WD19TB is very different than the TB16 and it shouldn't be conflated into this issue. The most interesting things to include in your issue - please first try this kernel: https://launchpad.net/ubuntu/+source /linux-oem-5.10. If it persists, can you please open an issue with 'ubuntu-bug linux-oem-5.10' which will attach all the logs to your 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I have a very similar issue with a WD19TB under Ubuntu 20.04 (Dell Latitude 5410) and desperately browsing the net, looking for solutions. Everything works fine until I resume from suspend. Then all USB devices connected to the dock start having failures (like missing key presses for the keyboard, mouse becoming sluggish until the device is disconnected, or sound becoming bad, also I suspect the ethernet port of the dock doesn't work well anymore). This is most likely *not* a thunderbolt authorization issue (I tried all the security modes: no security/user based/key based, all show the same behavior), which is a definite difference with many reports I found here and there (and makes it hard to find the same exact one as the one I have). The present issues description from the opener seems close enough, including dmesg output (although the opener had a Dell 16TB dock). -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[Kernel-packages] [Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
Thanks once again, @vicamo! Had to download additionally https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/plain/ath11k/QCA6390/hw2.0/board-2.bin and now finally detach my XPS 17 from the docking station and *still* have Internet!!! (3 months after getting it) I guess if the linux-firmware gets upgraded, I can again apply the instructions above and install linux-oem-20.04b, right? How can I "pin" linux-firmware? -- 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/1879633 Title: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux-firmware source package in Groovy: Won't Fix Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [SRU Justification: oem-5.6] [Impact] Qualcomm QCA6390 series not recognized due to the lack of ath11k and all its prerequisite drivers. $ lspci :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101] Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] [Fix] Tag ath11k-qca6390-bringup-202011301608 from ath tree (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git) marks first stable milestone on the platform/device under development since v5.6-rc1. Most of the commits under this tag, ~350 commits, have been in vanilla kernel v5.10-rc4 except those starting from commit 065c9528cc50 ("ath11k: add 64bit check before reading msi high addr"). While ath11k depends on MHI bus, qrtr and qmi helpers, changes falling in these components are also pulled. Besides, tx encapsulation https://lore.kernel.org/linux-wireless/20200908123702.88454-1-...@nbd.name/ and a couple more inclusive of 6 GHz capability, BSS Color were also pulled to satisfy API changes in mac80211/cfg80211. [Test Case] 1. Install firmwares & boot from patched kernel, 2. ath11k should be now up and running. Check with `sudo dmesg | grep ath11k` While this is going to bring massive changes to the kernel, as well as shared wireless stack that is not only used by ath11k but also many others, prebuilt kernel/firmware packages were deployed on platforms with and without ath11k for regression tests, and so far the results are positive. [Where problems could occur] ath11k and its relying parts have never been enabled in oem-5.6, so changes to them should have little effect on most platforms. For platforms equip QCA6390, this will be the first time they're probed and enabled, and as the driver is still under polishing, there can be regressions, performance lost, power consumption increase at this moment. Changes to wireless stack could also be an issue as this introduces interface changes to the API, so maybe DKMS packages in the wild will be affected. == SRU for U/OEM-5.10 == [SRU Justification: U/OEM-5.10] [Impact] Qualcomm QCA6390 series not recognized due to the lack of ath11k driver. $ lspci :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101] Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] [Fix] 25 additional fixes in ath tree (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git), tag ath11k-qca6390-bringup-202011301608 to resolve issues on TGL platforms, and firmware updates from mainline are required. [Test Case] 1. Install firmwares & boot from patched kernel, 2. ath11k should be now up and running. Check with `sudo dmesg | grep ath11k` [Where problems could occur] There has been a lot patches landed in kernel since 5.7 devel cycle. The last bits here has merge base with mainline at v5.10-rc4, and since then only patches for ath11k itself has been committed. == Original Bug Description == Qualcomm QCA6390 series not recognized due to the lack of ath11k driver. :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101] Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] Depending on bug 1891632 to fix Wi-Fi dead after resumed from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1842 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: #
[Kernel-packages] [Bug 1914848] Re: linux kernel 5.8 jammed
only linux kernel 5.4 is working linux kernel 5.8 is jammed -- 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/1914848 Title: linux kernel 5.8 jammed Status in linux package in Ubuntu: Confirmed Bug description: Computer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Pentium(R) CPU G3420 @ 3.20GHz CPU Family: 0x6 CPU Model: 0x3c CPU Stepping: 0x3 CPU Type: 0x0 Speed: 3200 Mhz 2 logical processors 2 physical processors HyperThreading: Unsupported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported AES: Unsupported AVX: Unsupported AVX2: Unsupported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Unsupported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: Ubuntu 20.04.2 LTS (64 bit) Kernel Name: Linux Kernel Version: 5.8.0-41-generic X Server Vendor: The X.Org Foundation X Server Release: 12009000 X Window Manager: GNOME Shell Steam Runtime Version: steam-runtime_0.20201203.1 Video Card: Driver: Intel Open Source Technology Center Mesa DRI Intel(R) HD Graphics (HSW GT1) Driver Version: 3.0 Mesa 20.2.6 OpenGL Version: 3.0 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 60 Hz VendorID: 0x8086 DeviceID: 0x402 Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1280 x 1024 Desktop Resolution: 1280 x 1024 Primary Display Size: 13.39" x 10.63" (17.09" diag) 34.0cm x 27.0cm (43.4cm diag) Primary VRAM Not Detected Sound card: Audio device: Intel Haswell HDMI Memory: RAM: 3798 Mb VR Hardware: VR Headset: None detected Miscellaneous: UI Language: English LANG: fi_FI.UTF-8 Total Hard Disk Space Available: 937366 Mb Largest Free Hard Disk Block: 878389 Mb The runtime information tool is preparing a report, please wait... have to restart again jammed again linux kernel 5.8 jammed this platform To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
This doesn't seem to be fixed with recent Ubuntu kernels. I have constant GPU hangs too. kernel: Linux luto 5.8.0-41-generic #46~20.04.1-Ubuntu SMP [ 20.503897] i915 :00:02.0: vgaarb: deactivate vga console [ 20.505641] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 20.525280] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [ 20.570726] fbcon: i915drmfb (fb0) is primary device [ 20.570858] i915 :00:02.0: fb0: i915drmfb frame buffer device [ 2252.688165] unhandled error in i915_error_to_vmf_fault: -22 [ 2252.688324] WARNING: CPU: 1 PID: 1455 at drivers/gpu/drm/i915/gem/i915_gem_mman.c:211 i915_error_to_vmf_fault+0x7a/0x90 [i915] [ 2252.688325] Modules linked in: nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_ice1712 snd_hda_codec snd_cs8427 snd_i2c snd_ice17xx_ak4xxx snd_ak4xxx_adda i915 snd_ac97_codec snd_hda_core snd_mpu401_uart snd_hwdep snd_seq_midi drm_kms_helper input_leds cec snd_seq_midi_event rc_core i2c_algo_bit snd_rawmidi fb_sys_fops snd_seq syscopyarea sysfillrect ac97_bus snd_pcm snd_seq_device snd_timer sysimgblt at24 snd soundcore serio_raw mac_hid sch_fq_codel w83627ehf hwmon_vid coretemp parport_pc ppdev lp drm parport ip_tables x_tables autofs4 uas usb_storage hid_generic usbhid hid gpio_ich i2c_i801 psmouse i2c_smbus pata_acpi lpc_ich r8169 realtek video [ 2252.688398] RIP: 0010:i915_error_to_vmf_fault+0x7a/0x90 [i915] [ 2252.688450] vm_fault_gtt+0x1d7/0x540 [i915] -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Released Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at
[Kernel-packages] [Bug 1914848] Re: linux kernel 5.8 jammed
trying completed ubuntu-bug evince trying send bug report linux kernel 5.8 is jammed and freeze -- 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/1914848 Title: linux kernel 5.8 jammed Status in linux package in Ubuntu: Confirmed Bug description: Computer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Pentium(R) CPU G3420 @ 3.20GHz CPU Family: 0x6 CPU Model: 0x3c CPU Stepping: 0x3 CPU Type: 0x0 Speed: 3200 Mhz 2 logical processors 2 physical processors HyperThreading: Unsupported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported AES: Unsupported AVX: Unsupported AVX2: Unsupported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Unsupported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: Ubuntu 20.04.2 LTS (64 bit) Kernel Name: Linux Kernel Version: 5.8.0-41-generic X Server Vendor: The X.Org Foundation X Server Release: 12009000 X Window Manager: GNOME Shell Steam Runtime Version: steam-runtime_0.20201203.1 Video Card: Driver: Intel Open Source Technology Center Mesa DRI Intel(R) HD Graphics (HSW GT1) Driver Version: 3.0 Mesa 20.2.6 OpenGL Version: 3.0 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 60 Hz VendorID: 0x8086 DeviceID: 0x402 Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1280 x 1024 Desktop Resolution: 1280 x 1024 Primary Display Size: 13.39" x 10.63" (17.09" diag) 34.0cm x 27.0cm (43.4cm diag) Primary VRAM Not Detected Sound card: Audio device: Intel Haswell HDMI Memory: RAM: 3798 Mb VR Hardware: VR Headset: None detected Miscellaneous: UI Language: English LANG: fi_FI.UTF-8 Total Hard Disk Space Available: 937366 Mb Largest Free Hard Disk Block: 878389 Mb The runtime information tool is preparing a report, please wait... have to restart again jammed again linux kernel 5.8 jammed this platform To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864871] Re: Failed to init Intel sound card in 20.04
After many months, I had the opportunity to put my hands on the computer that had these audio problems: (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/comments/31) ...and now the audio works without any workaround. Current Ubuntu version: 20.04.2 Kernel: 5.8.0-41 -- 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/1864871 Title: Failed to init Intel sound card in 20.04 Status in linux package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card there is no sound available because sound card not detected (only dummy output available in sound settings): $ alsamixer cannot open mixer: No such file or directory $ lspci -nnk |grep -A2 audio lspci: Unable to load libkmod resources: error -12 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] Subsystem: Lenovo Device [17aa:3816] Kernel driver in use: sof-audio-pci 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3] Subsystem: Lenovo Device [17aa:3819] $ pacmd list-cards 0 card(s) available. $ dmesg |grep sof [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB) [2.142149] systemd[1]: Mounting Mount unit for software-boutique, revision 54... [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 54. [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [2.817054] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 I've found similar bug reported here: https://bugs.archlinux.org/task/64720 As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot options and after that sound card successfully detected and started working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 26 19:22:05 2020 InstallationDate: Installed on 2020-02-25 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20RR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 195982] Re: Shift key (and caps lock) stop working when using VMWare
Wow, I did not expect this bug from 2008 to resurface in 2021! To quote myself in 2008: > As I'm using the free version of vmware, I can live with it until: > 1. They fix it > 2. VirtualBox becomes stable enough to use #2 happened many *many* years ago, so I can no longer test this issue, that was never really resolved beyond the sort-of-workaround with setxkbmap in over 12 years... -- 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/195982 Title: Shift key (and caps lock) stop working when using VMWare Status in Linux: Invalid Status in linux package in Ubuntu: Won't Fix Status in xkeyboard-config package in Ubuntu: Invalid Status in Gentoo Linux: New Bug description: [Problem] VMWare's keyboard mapping is imperfect, sometimes resulting in certain keys stopping functionality when running under VMWare, requiring the user to setup their configuration settings manually in VMWare. For a detailed explanation see the following article: http://www.vmware.com/support/ws55/doc/ws_devices_keymap_linux_longer.html [Original Report] After a day or so of running the shift key mysteriously stops working as does the cap lock. In other words I cannot enter shifted characters of any kind. The keyboard is connected to a KVM and all other systems respond to it properly. In additional any VMWare sessions I have open respond correctly. So I have the condition where all non-vmware applications in Ubuntu Hardy (all updates applied as of 2008-02-26 at 12:43 UTC) fail to recognize the shift key BUT applications within an active (a paused/restarted session also works) VMWare sessions running DO recognize the key. When this condition occurs ALL applications (except those within a VMWare session) are also unstable and will usually crash within a few keystrokes.If I continue to operate in this mode. I cannot pinpoint what, if any, application triggers this. It has always happened while working within terminal/browser/vmware sessions and NOT when opening a new application. It could be related to the KVM switch, but none of my other systems (2 Mandriva, 1 Windows) are affected by this. This bug has been present on my system for a number of days across daily updates and reboots (if the update requested it) and I think since I installed Hardy Alpha 1. A work around: log off and back on. A reboot/restart does not appear to be needed. Error logs show some unusual activity. --- MARK ... ... kernel ... rtc lost 7 interrupts ... --- MARK --- Plus some segfaults indicating which application crashed as I tried to type into it (mouse works fine). System: HP dv9743cl (which otherwise works lovely) Ubuntu: Hardy 8.04 (from lsb-release) TEST CASE: 1. Click inside the VM and 2. Hold any of the Ctrl, Alt and/or shift keys while releasing the keyboard/mouse to the host OS (which you obviously do when you press Crtl-Alt to revert back to windowed mode, as the cursor is then released from the VM). WORKAROUND: After this happens to recover your keyboard execute 'setxkbmap' in a terminal To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/195982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914919] [NEW] UC20 initrd misses modules to boot from USB disk
Public bug reported: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing console output it simply hangs indefinitely with a black screen https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914608). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen). + console output it simply hangs indefinitely with a black screen + LP#1914608 ). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen - LP#1914608 ). + console output it simply hangs indefinitely with a black screen #1914608 + ). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen #1914608 - ). + console output it simply hangs indefinitely with a black screen + https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914608). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1914919 Title: UC20 initrd misses modules to boot from USB disk Status in linux-raspi package in Ubuntu: New Bug description: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing console output it simply hangs indefinitely with a black screen https://bugs.launchpad.net/ubuntu/+source/linux- raspi/+bug/1914608). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
** Changed in: linux (Ubuntu) Assignee: Phan Thanh Long (phanlong2811) => (unassigned) -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Update (based on #296) = The latest kernel tree (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) has the complete solution to fix this bug. So we can expect kernel v5.11 to fix this issue without any additional work. Before the release of v5.11, you are suggested to use #189 to save your touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd driver is built into the initramfs. So you have to rebuild the initramfs after replacing the old module with new one. On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs -u`. The complete solution is three patches, - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce filter setting in IRQ type setting") - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way to disable debounce filter") - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into account debounce settings") The first two patches has reached the stable tree. If the last one is also backported to LTS kernel, you won't need to install kernel 5.11. But I don't know when this will happen. Original bug report === Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color