[Kernel-packages] [Bug 2062534] Re: GDM3 autologin might be racy on GCP resulting in inconsistent state of the wayland setup of seat0
** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2062534 Title: GDM3 autologin might be racy on GCP resulting in inconsistent state of the wayland setup of seat0 Status in gdm3 package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Bug description: This might not be a bug really about linux-gcp, but this is following the work on bug 2039732 and so far I could not reproduce that locally. Setup is 22.04 uptodate on GCP n2-standard instances, without GPU attached thus relying on vkms. I have reproduced locally a similar setup but on a KVM host. We rely on https://github.com/taskcluster/taskcluster/tree/main/workers/generic-worker#readme to run tasks on CI, and especially generic-worker will: - create a new task_XXX user - make it autologin in gdm3 config - generic-worker has code to probe for existence of the GNOME Wayland session before launching the task We relied on wl-clipboard package installed for verifying the status of wayland On top of that setup, here is the issue. We issue a TC task with payload: > export WAYLAND_DISPLAY=wayland-0 > export XDG_RUNTIME_DIR=/run/user/$(id -u) > wl-paste -l -p We expect that payload to report "No selection", but on GCP instances we mostly always end up with "This seat has no keyboard". There were also cases were the session would not be Wayland at all but rather X11. I think this suggests something around the availability of /dev/dri/card0, but forcing the gdm3 service to wait for its availability and adding extra waiting time after card0 is present would still not get us somewhere. We enabled gdm3 as well as mutter debugging but never found anything that would be a good lead on why it was not yet ready. At some point, the seat0 session of our user was shown as inactive and the active one was tied to gdm so we suspected this was the reason, but both forcing the session to be active and terminating the gdm session would still not unblock us. We also suspected the desktop to be locking itself so we disabled locking with the following, but iit did not help much: > cat > /etc/dconf/profile/user << EOF > user-db:user > system-db:local > EOF > > mkdir /etc/dconf/db/local.d/ > # dconf user settings > cat > /etc/dconf/db/local.d/00-tc-gnome-settings << EOF > # /org/gnome/desktop/session/idle-delay > [org/gnome/desktop/session] > idle-delay=uint32 0 > # /org/gnome/desktop/lockdown/disable-lock-screen > [org/gnome/desktop/lockdown] > disable-lock-screen=true > EOF > > sudo dconf update In the end, the only viable and reliable (verified over hundreds of runs now) fix that lasted was to add a "/bin/sleep 30" all to the gdm3 startup: > mkdir -p /etc/systemd/system/gdm.service.d/ > cat > /etc/systemd/system/gdm.service.d/gdm-wait.conf << EOF > [Unit] > Description=Extra 30s wait > [Service] > ExecStartPre=/bin/sleep 30 > EOF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2062534/+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 2059778] [NEW] package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: may be due to low disc space due to windows 10 update on dual boot system ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 06:24:31 2024 ErrorMessage: installed linux-image-6.5.0-26-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-21 (616 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059778 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: may be due to low disc space due to windows 10 update on dual boot system ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 06:24:31 2024 ErrorMessage: installed linux-image-6.5.0-26-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-21 (616 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059778/+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 2006557] Re: Enable rdma-sniffer for libpcap
** Changed in: libpcap (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006557 Title: Enable rdma-sniffer for libpcap Status in libpcap package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Invalid Status in libpcap package in Debian: Won't Fix Bug description: Hi, The request is to build and configure stock package libpcap with rdma-sniffer enabled. We'd like users of rdma devices to be able to sniff on them using stock tcpdump. Currently when using default tcpdump It does not list rdma devices. $ tcpdump -D |grep -i rdma $ when using locally build tcpdump (with rdma enabled) $ cd $ ./tcpdump -D |grep -i rdma 24.rocep4s0 (RDMA sniffer) 25.rocep7s0f0 (RDMA sniffer) 26.rocep7s0f1 (RDMA sniffer) 27.rocep10s0f0 (RDMA sniffer) 28.rocep10s0f1 (RDMA sniffer) 29.rocep33s0f0 (RDMA sniffer) 30.rocep33s0f1 (RDMA sniffer) 31.rocep36s0f0 (RDMA sniffer) 32.ibp36s0f1 (RDMA sniffer) Locally build steps: clone sources: $ mkdir tcpdumpbuild $ cd tcpdumpbuild/ $ git clone https://github.com/the-tcpdump-group/tcpdump.git $ git clone https://github.com/the-tcpdump-group/libpcap.git install required packages (including rdma packages so libpcap is built with rdma enabled): $ apt install flex bison librdmacm-dev librdmacm1 rdma-core rdmacm-utils configure and build $ cd libpcap $ ./autogen.sh $ ./configure --enable-rdma=yes $ make cd ../tcpdump/ ./autogen.sh ./configure $ make now ./tcpdump -D can show rdma devices. Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpcap/+bug/2006557/+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 2051672] Re: Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main)
** Summary changed: - Sync iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main) + Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/2051672 Title: Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main) Status in iproute2 package in Ubuntu: New Bug description: A few versions have been released and Ubuntu Noble still has the 6.1 version (6.1.0-1ubuntu2) from one year ago. Could it be possible to import the latest version from Debian unstable fixing a bunch of issues and supporting features from more recent kernels? Please note that Ubuntu Noble 24.04 will probably be shipped with the v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1 kernel, so missing the ones added to earlier versions. Switching to the v6.7 now should ease the upgrade to the v6.8 later. [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958 Upstream ChangeLog: - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/ - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/ - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/ - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/ - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/ - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/ (Previous changelog: https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22 ) ChangeLog from Debian: iproute2 (6.7.0-2) unstable; urgency=medium * Backport fix for 'ss' output -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + iproute2 (6.7.0-1) unstable; urgency=medium * Add Italian debconf translation (Closes: #1056582) * Update upstream source from tag 'upstream/6.7.0' * Bump copyright year ranges in d/copyright * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, merged upstream * Default config files moved from /usr/lib to /usr/share -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + iproute2 (6.6.0-1) unstable; urgency=medium * Update upstream source from tag 'upstream/6.6.0' * Backport patch to fix configuration installation * Remove handling of qt_atm.so, dropped upstream -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + iproute2 (6.5.0-5) unstable; urgency=medium * Use dh-sequence-movetousr -- Luca Boccassi <> Tue, 24 Oct 2023 15:24:01 +0100 iproute2 (6.5.0-4) unstable; urgency=medium * postinst: handle legacy config files only when upgrading from previous versions that shipped them * postinst: ensure that locally modified legacy config files are preserved as overrides on upgrade (Closes: #1051577) * Note configuration files location changes in NEWS -- Luca Boccassi <> Sat, 16 Sep 2023 18:58:51 +0100 iproute2 (6.5.0-3) unstable; urgency=medium * Remove further leftovers as part of upstream's move of config to /usr (Closes: #1051577) -- Luca Boccassi <> Mon, 11 Sep 2023 09:42:12 +0100 iproute2 (6.5.0-2) unstable; urgency=medium * Add maintscript to remove conffiles that upstream has moved to /usr (Closes: #1051577) -- Luca Boccassi <> Sun, 10 Sep 2023 21:28:28 +0100 iproute2 (6.5.0-1) unstable; urgency=medium [ Luca Boccassi ] * Use wildcard for Lintian overrides [ Peter Kvillegård ] * Add Swedish translation of debconf messages (Closes: #1050442) [ Luca Boccassi ] * Update upstream source from tag 'upstream/6.5.0' * Use cap_bpf instead of cap_sys_admin for ip vrf-exec * Package-provided config files are now shipped in /usr/iproute2 instead of /etc/iproute2 -- Luca Boccassi <> Sat, 09 Sep 2023 16:32:54 +0100 iproute2 (6.4.0-1) unstable; urgency=medium * Fix patch header Forwarded field * Enable ELF metadata stamping * Update upstream source from tag 'upstream/6.4.0' * Update Lintian overrides -- Luca Boccassi <> Fri, 30 Jun 2023 12:16:40 +0100 iproute2 (6.3.0-1) unstable; urgency=medium * Drop obsolete conflicts/replaces * Update upstream source from tag 'upstream/6.3.0' -- Luca Boccassi <> Tue, 13 Jun 2023 23:49:37 +0100 iproute2 (6.1.0-3) unstable; urgency=medium * Ensure 'ip mo' resolves to 'ip monitor' (Closes: #1036534) -- Luca Boccassi <> Mon, 22 May 2023 14:19:52 +0100 iproute2 (6.1.0-2) unstable; urgency=medium * Add Romanian language translation for debconf (Closes: #1031917) * Bump Standards-Version to 4.6.2, no changes * Bump d/copyright year range -- Luca Boccassi <> Sat, 25 Feb 2023
[Kernel-packages] [Bug 2003768] Re: iwlwifi Stuck
I wanted to let everyone know that I upgraded to 6.6.12-060612-generic about 16 hours ago, and have not had a single problem with my wifi. I used the debs downloaded from https://kernel.ubuntu.com/mainline/v6.6.12/ . So far, so good. -- 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/2003768 Title: iwlwifi Stuck Status in linux package in Ubuntu: Confirmed Bug description: [40234.924454] iwlwifi :00:14.3: Queue 5 is stuck 78 150 [40234.924775] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [40234.924916] iwlwifi :00:14.3: Start IWL Error Log Dump: [40234.924920] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [40234.924924] iwlwifi :00:14.3: Loaded firmware version: 71.058653f6.0 QuZ-a0-hr-b0-71.ucode [40234.924928] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [40234.924933] iwlwifi :00:14.3: 0xA210 | trm_hw_status0 [40234.924936] iwlwifi :00:14.3: 0x | trm_hw_status1 [40234.924939] iwlwifi :00:14.3: 0x004CBE06 | branchlink2 [40234.924942] iwlwifi :00:14.3: 0x004C257A | interruptlink1 [40234.924945] iwlwifi :00:14.3: 0x004C257A | interruptlink2 [40234.924948] iwlwifi :00:14.3: 0xB620 | data1 [40234.924951] iwlwifi :00:14.3: 0x0100 | data2 [40234.924953] iwlwifi :00:14.3: 0x | data3 [40234.924956] iwlwifi :00:14.3: 0x6100C1E4 | beacon time [40234.924959] iwlwifi :00:14.3: 0x0033EE36 | tsf low [40234.924962] iwlwifi :00:14.3: 0x0039 | tsf hi [40234.924965] iwlwifi :00:14.3: 0x | time gp1 [40234.924968] iwlwifi :00:14.3: 0x7F921B5F | time gp2 [40234.924971] iwlwifi :00:14.3: 0x0001 | uCode revision type [40234.924974] iwlwifi :00:14.3: 0x0047 | uCode version major [40234.924977] iwlwifi :00:14.3: 0x058653F6 | uCode version minor [40234.924979] iwlwifi :00:14.3: 0x0351 | hw version [40234.924982] iwlwifi :00:14.3: 0x00C89001 | board version [40234.924985] iwlwifi :00:14.3: 0x8007FC04 | hcmd [40234.924988] iwlwifi :00:14.3: 0x2402 | isr0 [40234.924991] iwlwifi :00:14.3: 0x | isr1 [40234.924994] iwlwifi :00:14.3: 0x08F2 | isr2 [40234.924996] iwlwifi :00:14.3: 0x00C3028C | isr3 [40234.924999] iwlwifi :00:14.3: 0x | isr4 [40234.925002] iwlwifi :00:14.3: 0x054C001C | last cmd Id [40234.925005] iwlwifi :00:14.3: 0xB620 | wait_event [40234.925008] iwlwifi :00:14.3: 0x00D4 | l2p_control [40234.925010] iwlwifi :00:14.3: 0x00010034 | l2p_duration [40234.925013] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid [40234.925016] iwlwifi :00:14.3: 0x | l2p_addr_match [40234.925019] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel [40234.925022] iwlwifi :00:14.3: 0x | timestamp [40234.925025] iwlwifi :00:14.3: 0x907C | flow_handler [40234.925470] iwlwifi :00:14.3: Start IWL Error Log Dump: [40234.925473] iwlwifi :00:14.3: Transport status: 0x004A, valid: 7 [40234.925478] iwlwifi :00:14.3: 0x2066 | NMI_INTERRUPT_HOST [40234.925482] iwlwifi :00:14.3: 0x | umac branchlink1 [40234.925484] iwlwifi :00:14.3: 0x80455B7C | umac branchlink2 [40234.925487] iwlwifi :00:14.3: 0x804721A2 | umac interruptlink1 [40234.925490] iwlwifi :00:14.3: 0x804721A2 | umac interruptlink2 [40234.925492] iwlwifi :00:14.3: 0x0100 | umac data1 [40234.925495] iwlwifi :00:14.3: 0x804721A2 | umac data2 [40234.925498] iwlwifi :00:14.3: 0x | umac data3 [40234.925500] iwlwifi :00:14.3: 0x0047 | umac major [40234.925503] iwlwifi :00:14.3: 0x058653F6 | umac minor [40234.925507] iwlwifi :00:14.3: 0x7F921B5C | frame pointer [40234.925510] iwlwifi :00:14.3: 0xC0886264 | stack pointer [40234.925515] iwlwifi :00:14.3: 0x0051019C | last host cmd [40234.925519] iwlwifi :00:14.3: 0x | isr status reg [40234.925634] iwlwifi :00:14.3: IML/ROM dump: [40234.925638] iwlwifi :00:14.3: 0x0003 | IML/ROM error/state [40234.925706] iwlwifi :00:14.3: 0x5603 | IML/ROM data1 [40234.925816] iwlwifi :00:14.3: 0x0080 | IML/ROM WFPM_AUTH_KEY_0 [40234.925836] iwlwifi :00:14.3: Fseq Registers: [40234.925879] iwlwifi :00:14.3: 0x6000 | FSEQ_ERROR_CODE [40234.925922] iwlwifi :00:14.3: 0x80290033 | FSEQ_TOP_INIT_VERSION [40234.925964] iwlwifi :00:14.3: 0x00090006 | FSEQ_CNVIO_INIT_VERSION [40234.926006] iwlwifi :00:14.3: 0xA482 | FSEQ_OTP_VERSION [40234.926049] iwlwifi :00:14.3: 0x0003 | FSEQ_TOP_CONTENT_VERSION [40234.926091] iwlwifi :00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN [40234.926134] iwlwifi :00:14.3: 0x2302 | FSEQ_CNVI_ID [40234.926177] iwlwifi :00:14.3: 0x01300504 | FSEQ_CNVR_ID
[Kernel-packages] [Bug 2047780] Re: BlueZ release 5.71
ell had an approved MIR but the only thing it was used for was iwd which is not currently in main. After the MIR is approved, something in main needs to depend on it (or add it to a main seed) and then the Archive Admins can promote it to main. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71 and merge from Debian
Simon, ell already has a recent approved MIR LP: #1971738 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 and merge from Debian Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
evolution-data-server still has uninstallable binaries on i386. You can ignore bluez for the binfmt-support issue. However, for bluez, Ubuntu uses --enable-phonebook-ebook . There are other phonebook options; maybe what Debian uses works for Debian. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
Simon, I think it would be better to get libphonenumber fixed correctly instead of working around it. https://launchpad.net/ubuntu/+source/libphonenumber/8.12.57+ds-4build1 https://ubuntu-archive-team.ubuntu.com/proposed- migration/noble_uninst.txt In other words, asking an Archive Admin to build binfmt-support on i386. I suspect that it would need to be special-cased something like this, because jarwrapper is arch:all https://code.launchpad.net/~jbicha/ubuntu-archive-tools/+git/ubuntu- archive-tools/+merge/457360 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
Daniel, systemd was updated today in noble-proposed. It includes changes as part of Debian's ongoing usrmerge work. In particular this commit: https://salsa.debian.org/systemd-team/systemd/-/commit/ee83b5721 Here is a Debian commit to adapt to the change: https://salsa.debian.org/bluetooth-team/bluez/-/commit/f4d76255cdfa Something like this could be simpler though: https://salsa.debian.org/DebianOnMobile-team/modemmanager/-/commit/367180c3 ** Tags added: update-excuse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Changed in: mutter (Ubuntu Mantic) Status: Fix Released => Triaged -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Triaged Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
I'm setting the importance to Critical per #6 at https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: mutter (Ubuntu Jammy) Importance: High => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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 2025568] Re: After update to 20230629.gitee91452d-0ubuntu1 no WiFi/WLAN with MT7921
Is Windows installed on this computer? -- 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/2025568 Title: After update to 20230629.gitee91452d-0ubuntu1 no WiFi/WLAN with MT7921 Status in linux-firmware package in Ubuntu: New Bug description: Notebook with "Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter" have no WiFi after upgrading firmware package # journalctl --since "2 days ago" | grep mt7921e Before Update: Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20230526130917a Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: WM Firmware Version: 01, Build Time: 20230526130958 Jul 02 16:27:58 hogwarts kernel: mt7921e :01:00.0 wlp1s0: renamed from wlan0 Jul 02 16:27:58 hogwarts NetworkManager[1333]: [1688308078.8625] rfkill3: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:01:00.0/ieee80211/phy0/rfkill3) (driver mt7921e) After Update: Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: enabling device ( -> 0002) Jul 02 16:55:52 hogwarts kernel: mt7921e :01:00.0: ASIC revision: 79610010 Jul 02 16:55:52 hogwarts kernel: mt7921e: probe of :01:00.0 failed with error -110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2025568/+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 2024985] Re: Bluetooth doesn't enable
If you want to try my fix, Secure Boot needs to be disabled, check in terminal> mokutil --sb Then in terminal sudo apt install git dkms git clone https://github.com/jeremyb31/bluetooth-5.19.git sudo dkms add ./bluetooth-5.19 sudo dkms install btusb/4.0 Then reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2024985 Title: Bluetooth doesn't enable Status in bluez package in Ubuntu: New Bug description: martin@studio-as6:~$ sudo dmesg | egrep -i 'blue|firm' [0.119642] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.278739] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.462372] [drm] Loading DMUB firmware via PSP: version=0x0422 [2.463264] [drm] Found VCN firmware Version ENC: 1.21 DEC: 2 VEP: 0 Revision: 10 [2.463267] amdgpu :e6:00.0: amdgpu: Will use PSP to load VCN firmware [4.073508] Bluetooth: Core ver 2.22 [4.074051] NET: Registered PF_BLUETOOTH protocol family [4.074053] Bluetooth: HCI device and connection manager initialized [4.074057] Bluetooth: HCI socket layer initialized [4.074059] Bluetooth: L2CAP socket layer initialized [4.074064] Bluetooth: SCO socket layer initialized [4.257367] mt7921e :03:00.0: WM Firmware Version: 00, Build Time: 20220908203253 [6.223611] Bluetooth: hci0: Opcode 0x c03 failed: -110 [7.328550] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.328553] Bluetooth: BNEP filters: protocol multicast [7.328556] Bluetooth: BNEP socket layer initialized Note the line: [6.223611] Bluetooth: hci0: Opcode 0x c03 failed: -110 UI carries on, but the error is fatal and no devices can be found. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.19.0-1017.18~22.04.1-lowlatency 5.19.17 Uname: Linux 5.19.0-1017-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jun 25 14:25:34 2023 InstallationDate: Installed on 2023-06-25 (0 days ago) InstallationMedia: Ubuntu-Studio 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230221) InterestingModules: bnep bluetooth MachineType: ASUSTeK COMPUTER INC. MINIPC PN53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-1017-lowlatency root=UUID=933611e5-18b7-4290-98f3-d60eb962bdad ro threadirqs quiet splash vt.handoff=1 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2023 dmi.bios.release: 2.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 20300 dmi.board.asset.tag: Default string dmi.board.name: PN53 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr20300:bd02/02/2023:br2.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN53:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPN53:rvrRev1.xx:cvnDefaultstring:ct35:cvrDefaultstring:skuSKU: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN53 dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: rfkill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2024985/+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 2024985] Re: Bluetooth doesn't enable
Looks like the kernel needs this patch from upstream https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/drivers/bluetooth/btusb.c?id=57117d7234dadfba2a83615b2a9369f6f2f9914f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2024985 Title: Bluetooth doesn't enable Status in bluez package in Ubuntu: New Bug description: martin@studio-as6:~$ sudo dmesg | egrep -i 'blue|firm' [0.119642] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.278739] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.462372] [drm] Loading DMUB firmware via PSP: version=0x0422 [2.463264] [drm] Found VCN firmware Version ENC: 1.21 DEC: 2 VEP: 0 Revision: 10 [2.463267] amdgpu :e6:00.0: amdgpu: Will use PSP to load VCN firmware [4.073508] Bluetooth: Core ver 2.22 [4.074051] NET: Registered PF_BLUETOOTH protocol family [4.074053] Bluetooth: HCI device and connection manager initialized [4.074057] Bluetooth: HCI socket layer initialized [4.074059] Bluetooth: L2CAP socket layer initialized [4.074064] Bluetooth: SCO socket layer initialized [4.257367] mt7921e :03:00.0: WM Firmware Version: 00, Build Time: 20220908203253 [6.223611] Bluetooth: hci0: Opcode 0x c03 failed: -110 [7.328550] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.328553] Bluetooth: BNEP filters: protocol multicast [7.328556] Bluetooth: BNEP socket layer initialized Note the line: [6.223611] Bluetooth: hci0: Opcode 0x c03 failed: -110 UI carries on, but the error is fatal and no devices can be found. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.19.0-1017.18~22.04.1-lowlatency 5.19.17 Uname: Linux 5.19.0-1017-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jun 25 14:25:34 2023 InstallationDate: Installed on 2023-06-25 (0 days ago) InstallationMedia: Ubuntu-Studio 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230221) InterestingModules: bnep bluetooth MachineType: ASUSTeK COMPUTER INC. MINIPC PN53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-1017-lowlatency root=UUID=933611e5-18b7-4290-98f3-d60eb962bdad ro threadirqs quiet splash vt.handoff=1 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2023 dmi.bios.release: 2.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 20300 dmi.board.asset.tag: Default string dmi.board.name: PN53 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr20300:bd02/02/2023:br2.3:svnASUSTeKCOMPUTERINC.:pnMINIPCPN53:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPN53:rvrRev1.xx:cvnDefaultstring:ct35:cvrDefaultstring:skuSKU: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN53 dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: rfkill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2024985/+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 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04
David, power off the laptop and remove battery and power cord, then press and hold power button for 30 seconds, install battery and power cord, then boot. If the battery isn't easy to access, just remove power cord and hold power button for 30 seconds -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2017790 Title: Intel Wi-Fi 6 AX201 failing in 23.04 Status in linux-lowlatency package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 23.04 the intel wifi driver is not loading, I am seeing the following in dmesg: [ 215.024382] Loading of unsigned module is rejected [ 262.051998] [ cut here ] [ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 genl_validate_ops+0x1cc/0x270 [ 262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 snd_intel_ sdw_acpi [ 262.052038] mii hid_plantronics hid_logitech_dj snd_usbmidi_lib snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel processor_thermal_device_pci_legacy cryptd cmdlinepart industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device hid_sensor_iio_common processor_thermal_rfim intel_cstate firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec processor_thermal_mbox soundcore rc_core mei ecdh_ generic [ 262.052068] processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal soc_button_array int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake [ 262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW O 6.2.0-1003-lowlatency #3-Ubuntu [ 262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 02/24/2023 [ 262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270 [ 262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d [ 262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206 [ 262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: [ 262.052106] RDX: RSI: RDI: [ 262.052106] RBP: a91bc7103b88 R08: R09: [ 262.052107] R10: R11: R12: 0001 [ 262.052107] R13: c1824780 R14: a91bc7103a88 R15: [ 262.052108] FS: 7fd67c380040() GS:8fcc7f68() knlGS: [ 262.052109] CS: 0010 DS: ES: CR0: 80050033 [ 262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 00770ee0 [ 262.052111] PKRU: 5554 [ 262.052112] Call Trace:
[Kernel-packages] [Bug 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04
David, is Windows installed also? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2017790 Title: Intel Wi-Fi 6 AX201 failing in 23.04 Status in linux-lowlatency package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 23.04 the intel wifi driver is not loading, I am seeing the following in dmesg: [ 215.024382] Loading of unsigned module is rejected [ 262.051998] [ cut here ] [ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 genl_validate_ops+0x1cc/0x270 [ 262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 snd_intel_ sdw_acpi [ 262.052038] mii hid_plantronics hid_logitech_dj snd_usbmidi_lib snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel processor_thermal_device_pci_legacy cryptd cmdlinepart industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device hid_sensor_iio_common processor_thermal_rfim intel_cstate firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec processor_thermal_mbox soundcore rc_core mei ecdh_ generic [ 262.052068] processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal soc_button_array int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake [ 262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW O 6.2.0-1003-lowlatency #3-Ubuntu [ 262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 02/24/2023 [ 262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270 [ 262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d [ 262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206 [ 262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: [ 262.052106] RDX: RSI: RDI: [ 262.052106] RBP: a91bc7103b88 R08: R09: [ 262.052107] R10: R11: R12: 0001 [ 262.052107] R13: c1824780 R14: a91bc7103a88 R15: [ 262.052108] FS: 7fd67c380040() GS:8fcc7f68() knlGS: [ 262.052109] CS: 0010 DS: ES: CR0: 80050033 [ 262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 00770ee0 [ 262.052111] PKRU: 5554 [ 262.052112] Call Trace: [ 262.052113] [ 262.052115] ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211] [ 262.052146] ? __pfx_nl80211_get_wiphy+0x10/0x10 [cfg80211] [ 262.052171] ? __pfx_nl80211_post_doit+0x10/0x10 [cfg80211] [
[Kernel-packages] [Bug 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04
Any results from terminal for dkms status It seems that the modules causing the issues are part of linux-modules- iwlwifi and I am not sure if that can be safely removed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2017790 Title: Intel Wi-Fi 6 AX201 failing in 23.04 Status in linux-lowlatency package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 23.04 the intel wifi driver is not loading, I am seeing the following in dmesg: [ 215.024382] Loading of unsigned module is rejected [ 262.051998] [ cut here ] [ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 genl_validate_ops+0x1cc/0x270 [ 262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 snd_intel_ sdw_acpi [ 262.052038] mii hid_plantronics hid_logitech_dj snd_usbmidi_lib snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel processor_thermal_device_pci_legacy cryptd cmdlinepart industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device hid_sensor_iio_common processor_thermal_rfim intel_cstate firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec processor_thermal_mbox soundcore rc_core mei ecdh_ generic [ 262.052068] processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal soc_button_array int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake [ 262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW O 6.2.0-1003-lowlatency #3-Ubuntu [ 262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 02/24/2023 [ 262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270 [ 262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d [ 262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206 [ 262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: [ 262.052106] RDX: RSI: RDI: [ 262.052106] RBP: a91bc7103b88 R08: R09: [ 262.052107] R10: R11: R12: 0001 [ 262.052107] R13: c1824780 R14: a91bc7103a88 R15: [ 262.052108] FS: 7fd67c380040() GS:8fcc7f68() knlGS: [ 262.052109] CS: 0010 DS: ES: CR0: 80050033 [ 262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 00770ee0 [ 262.052111] PKRU: 5554 [ 262.052112] Call Trace: [ 262.052113] [ 262.052115] ? __pfx_nl80211_pre_doit+0x10/0x10
[Kernel-packages] [Bug 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04
Remove the iwlwifi backports then -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2017790 Title: Intel Wi-Fi 6 AX201 failing in 23.04 Status in linux-lowlatency package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 23.04 the intel wifi driver is not loading, I am seeing the following in dmesg: [ 215.024382] Loading of unsigned module is rejected [ 262.051998] [ cut here ] [ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 genl_validate_ops+0x1cc/0x270 [ 262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 snd_intel_ sdw_acpi [ 262.052038] mii hid_plantronics hid_logitech_dj snd_usbmidi_lib snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel processor_thermal_device_pci_legacy cryptd cmdlinepart industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device hid_sensor_iio_common processor_thermal_rfim intel_cstate firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec processor_thermal_mbox soundcore rc_core mei ecdh_ generic [ 262.052068] processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal soc_button_array int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake [ 262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW O 6.2.0-1003-lowlatency #3-Ubuntu [ 262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 02/24/2023 [ 262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270 [ 262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d [ 262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206 [ 262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: [ 262.052106] RDX: RSI: RDI: [ 262.052106] RBP: a91bc7103b88 R08: R09: [ 262.052107] R10: R11: R12: 0001 [ 262.052107] R13: c1824780 R14: a91bc7103a88 R15: [ 262.052108] FS: 7fd67c380040() GS:8fcc7f68() knlGS: [ 262.052109] CS: 0010 DS: ES: CR0: 80050033 [ 262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 00770ee0 [ 262.052111] PKRU: 5554 [ 262.052112] Call Trace: [ 262.052113] [ 262.052115] ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211] [ 262.052146] ? __pfx_nl80211_get_wiphy+0x10/0x10 [cfg80211] [ 262.052171] ? __pfx_nl80211_post_doit+0x10/0x10 [cfg80211] [
[Kernel-packages] [Bug 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04
Try uninstalling the backport-iwlwifi-dkms and reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2017790 Title: Intel Wi-Fi 6 AX201 failing in 23.04 Status in linux-lowlatency package in Ubuntu: New Bug description: After upgrading from 22.04 to 23.04 the intel wifi driver is not loading, I am seeing the following in dmesg: [ 215.024382] Loading of unsigned module is rejected [ 262.051998] [ cut here ] [ 262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 genl_validate_ops+0x1cc/0x270 [ 262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 snd_intel_ sdw_acpi [ 262.052038] mii hid_plantronics hid_logitech_dj snd_usbmidi_lib snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel processor_thermal_device_pci_legacy cryptd cmdlinepart industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device hid_sensor_iio_common processor_thermal_rfim intel_cstate firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec processor_thermal_mbox soundcore rc_core mei ecdh_ generic [ 262.052068] processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal soc_button_array int340x_thermal_zone int3400_thermal intel_hid acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake [ 262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW O 6.2.0-1003-lowlatency #3-Ubuntu [ 262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 02/24/2023 [ 262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270 [ 262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d [ 262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206 [ 262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: [ 262.052106] RDX: RSI: RDI: [ 262.052106] RBP: a91bc7103b88 R08: R09: [ 262.052107] R10: R11: R12: 0001 [ 262.052107] R13: c1824780 R14: a91bc7103a88 R15: [ 262.052108] FS: 7fd67c380040() GS:8fcc7f68() knlGS: [ 262.052109] CS: 0010 DS: ES: CR0: 80050033 [ 262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 00770ee0 [ 262.052111] PKRU: 5554 [ 262.052112] Call Trace: [ 262.052113] [ 262.052115] ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211] [ 262.052146] ? __pfx_nl80211_get_wiphy+0x10/0x10 [cfg80211] [ 262.052171] ? __pfx_nl80211_post_doit+0x10/0x10
[Kernel-packages] [Bug 2007772] Re: 7392:c611 Edimax Technology Co., Ltd Edimax Bluetooth Adapter is not currently supported by the installed kernel (5.15)
Your dmesg shows an out of tree module called rtk_btusb. If you get rid of it the bluetooth may work with the btusb kernel module -- 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/2007772 Title: 7392:c611 Edimax Technology Co., Ltd EdimaxBluetooth Adapter is not currently supported by the installed kernel (5.15) Status in linux package in Ubuntu: Confirmed Bug description: Hi, I wanted to connect my bluetooth headset to my Ubuntu 22.04 LTS system. I purchased a Edimax usb bluetooth dongle (BT8500 with rtl8761b chipset) which has a ubuntu driver for a supportted kernal version of 2.6.32 – 5.3. (apparently) BT USB CHIPS rtl8761bu_fw BTCOEX_20190327-0202 FW_VER= 0x999646b BT UART CHIPS rtl8761b_fw BTCOEX_20190327-0202 FW_VER= 0xd99646b However This device 7392:c611 Edimax Technology Co., Ltd Edimax Bluetooth Adapter is not currently supported by the installed kernel (5.15), neither it is supported by the next 5.19 Ubuntu kernel. Support for this device has been added by this patch to Linux mainline. If you install a recent mainline kernel, the device should work. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/bluetooth/btusb.c?h=v6.1.12=c7577014b74c5369490715015db096182f1a2a23 systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-02-09 21:22:48 NZDT; 28min ago Docs: man:bluetoothd(8) Main PID: 1006 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.0M CPU: 133ms CGroup: /system.slice/bluetooth.service └─1006 /usr/lib/bluetooth/bluetoothd Feb 09 21:22:48 Edward bluetoothd[1006]: Starting SDP server Feb 09 21:22:48 Edward bluetoothd[1006]: Bluetooth management interface 1.21 initialized Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 [86619.755586] rtk_btcoex: Close BTCOEX [86619.755592] rtk_btcoex: -x [86619.857321] rtk_btusb: btusb_open start [86619.857326] rtk_btusb: btusb_open hdev->promisc ==0 [86619.857329] rtk_btusb: download_patch start [86619.857331] rtk_btusb: chip type value: 0x74 systemctl status bluetooth.service 13/02 ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2023-02-12 22:01:25 NZDT; 22h ago Docs: man:bluetoothd(8) Main PID: 1008 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.2M CPU: 180ms CGroup: /system.slice/bluetooth.service └─1008 /usr/lib/bluetooth/bluetoothd Feb 13 19:39:54 Edward bluetoothd[1008]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]:
[Kernel-packages] [Bug 2007654] Re: enable Rust support in the kernel
** Changed in: linux (Ubuntu Lunar) 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/2007654 Title: enable Rust support in the kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [Impact] Rust support has been merged starting with linux 6.1. This support allows to write external kernel modules using the Rust language. Modules written in this way are linked against the linux kernel and can be loaded/unloaded like any other .ko module. Main advantages of writing modules in Rust are: - memory safety: - no out of bounds accesses - no use after free - data race safety - strongly typed and statically typed - code extremely compact Roughly 70% of the security issues that the MSRC assigns a CVE to are memory safety issues: - Rust allows to write more secure and robust kernel code (reduce kernel CVEs) We should provide a Rust-enabled kernel so that people have the possibility to implement their own external kernel modules in Rust. [Test case] Build the following "hello world" test module: == hello_rust.rs == // SPDX-License-Identifier: GPL-2.0 //! Rust hello world example. use kernel::prelude::*; module! { type: HelloRust, name: "hello_rust", author: "Andrea Righi ", description: "Rust hello world example", license: "GPL", } struct HelloRust { } impl kernel::Module for HelloRust { fn init(_module: &'static ThisModule) -> Result { pr_info!("Hello from Rust\n"); Ok(HelloRust { }) } } impl Drop for HelloRust { fn drop( self) { pr_info!("Goodbye from Rust\n"); } } == Makefile == NAME=hello_rust ifndef KERNELRELEASE ifndef KDIR KDIR:=/lib/modules/`uname -r`/build endif PWD := $(shell pwd) all: $(MAKE) -C $(KDIR) M=$(PWD) modules install: $(MAKE) -C $(KDIR) M=$(PWD) modules_install clean: rm -f *.o *.ko *.mod* .*.cmd *.d Module.symvers modules.order rm -rf .tmp_versions else obj-m := $(NAME).o endif [Fix] Building the Rust support in the kernel requires specific versions of the Rust compiler and bindgen utility, same to build the external modules in Rust): - rustc 1.62.0 - bindgen 0.56.0 - clang/llvm (already required by BPF) Archive should provide these versions (ideally with a version suffix to avoid conflicting with the stock versions, e.g., rustc-1.62 and bindgen-0.56). In addition to that the kernel needs some packaging adjustments to use these special toolchain binaries and some special (not yet upstream) patches that would allow to enable mandatory features required in our generic kernel, such as: UBUNTU: SAUCE: allows to enable Rust with modversions UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion UBUNTU: SAUCE: scripts: Exclude Rust CUs with pahole UBUNTU: SAUCE: rust: allow to use INIT_STACK_ALL_ZERO With all of the above we can enable CONFIG_RUST in the kernel and provide support to build external modules (.ko) using Rust. [Regression potential] We may see build regressions due to the inavailability of the proper toolchain versions. Moreover these toolchain dependencies need to be maintained, making sure to be always aligned with upstream requirements, when stable updates are applied to the kernel. Moreover, hwe kernels require special attention, since this feature won't be available in old releases (unless the proper toolchain requirements are met). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007654/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
First, enable source code repositories, then fetch the source code with the following in terminal apt-get source linux-modules-extra-$(uname -r) Then navigate to the /drivers/media/usb/uvc directory and rename the uvcdriver.c to uvcdriver.old, choose open directory in terminal then wget https://raw.githubusercontent.com/Giuliano69/uvc_driver-for-Quanta- HD-User-Facing-0x0408-0x4035-/main/uvc_driver.c make -j4 -C /lib/modules/$(uname -r)/build M=$(pwd) modules sudo cp uvcvideo.ko /lib/modules/$(uname -r)/kernel/drivers/media/usb/uvc/ Then see if it works -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux
[Kernel-packages] [Bug 2000800] Re: Bluetooth is not being activated, I have updated with sudo apt-get update and installed the program and restarted and it does not turn on
Try installing a Nvidia driver from the Driver Manager and reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2000800 Title: Bluetooth is not being activated, I have updated with sudo apt-get update and installed the program and restarted and it does not turn on Status in bluez package in Ubuntu: New Bug description: Bluetooth is not being activated, I have updated with sudo apt-get update and installed the program and restarted and it does not turn on ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 22:34:07 2022 InstallationDate: Installed on 2022-12-30 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: bnep btusb bluetooth MachineType: LENOVO 82K2 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=UUID=94a2de4f-8565-4a45-8c72-872549f49fdb ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: H3CN32WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Gaming 3 15ACH6 dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrH3CN32WW(V2.02):bd02/23/2022:br1.32:efr1.32:svnLENOVO:pn82K2:pvrIdeaPadGaming315ACH6:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPadGaming315ACH6:skuLENOVO_MT_82K2_BU_idea_FM_IdeaPadGaming315ACH6: dmi.product.family: IdeaPad Gaming 3 15ACH6 dmi.product.name: 82K2 dmi.product.sku: LENOVO_MT_82K2_BU_idea_FM_IdeaPad Gaming 3 15ACH6 dmi.product.version: IdeaPad Gaming 3 15ACH6 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:7 acl:0 sco:0 events:1 errors:0 TX bytes:61 acl:0 sco:0 commands:1 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000800/+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 1997201] Re: BlueZ 5.66 release
I've uploaded this for you. I did notice that the "original" tarball you provided and is compatible with the Launchpad git tree doesn't match the original tarball used by Debian for 5.66. Not a problem here, but if we ever did get the bluez packaging closer in sync with Debian, it might be nice to use the same tarballs. ** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1997201 Title: BlueZ 5.66 release Status in bluez package in Ubuntu: Fix Committed Bug description: Release to Lunar: http://www.bluez.org/release-of-bluez-5-66/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+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 1996981] Re: package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.
** Summary changed: - package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1 [modified: usr/share/bash-completion/completions/bpftool usr/share/man/man1/cpupower-idle-info.1.gz usr/share/man/man1/cpupower-monitor.1.gz usr/share/man/man1/cpupower.1.gz usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/s hare/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf-script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf-version.1.gz usr/share/man/man1/perf.1.gz usr/share/man/man1/usbip.8.gz usr/share/man/man1/usbipd.8.gz usr/share/man/man8/bpftool-btf.8.gz usr/share/man/man8/bpftool-cgroup.8.gz usr/share/man/man8/bpftool-feature.8.gz usr/share/man/man8/bpftool-map.8.gz usr/share/man/man8/bpftool-net.8.gz usr/share/man/man8/bpftool-perf.8.gz usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz usr/share/man/man8/turbostat.8.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.4.0-131.147 + package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1996981 Title: package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04. Status in linux-intel-iotg-5.15 package in Ubuntu: New Bug description: package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1 [modified: usr/share/bash-completion/completions/bpftool usr/share/man/man1/cpupower-idle-info.1.gz usr/share/man/man1/cpupower-monitor.1.gz usr/share/man/man1/cpupower.1.gz usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf- bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf- report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf- script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf- top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf- version.1.gz usr/share/man/man1/perf.1.gz usr/share/man/man1/usbip.8.gz usr/share/man/man1/usbipd.8.gz usr/share/man/man8/bpftool-btf.8.gz usr/share/man/man8/bpftool- cgroup.8.gz usr/share/man/man8/bpftool-feature.8.gz usr/share/man/man8/bpftool-map.8.gz usr/share/man/man8/bpftool- net.8.gz usr/share/man/man8/bpftool-perf.8.gz usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz usr/share/man/man8/turbostat.8.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools- common 5.4.0-131.147 ProblemType: Package DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.14.0-1054.61-oem 5.14.21 Uname: Linux 5.14.0-1054-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 18 15:10:06 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package
[Kernel-packages] [Bug 1995798] Re: MT7921K high latency when bluetooth headset is used
** Bug watch added: Linux Kernel Bug Tracker #216668 https://bugzilla.kernel.org/show_bug.cgi?id=216668 ** Also affects: bluez via https://bugzilla.kernel.org/show_bug.cgi?id=216668 Importance: Unknown Status: Unknown ** Project changed: bluez => linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1995798 Title: MT7921K high latency when bluetooth headset is used Status in Linux: Unknown Status in bluez package in Ubuntu: New Bug description: When I use onboard WiFi and Bluetooth headset at the same time, the latency goes from ~30-50ms to 200-6500ms Motherboard: ASUS TUF GAMING X670E-PLUS WIFI BIOS: 0809 Kernels tested: Ubuntu 22.10 downstream kernel (5.19) and upstream 6.0.[135] $ lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 Also made upstream kernel bz: https://bugzilla.kernel.org/show_bug.cgi?id=216668 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 Uname: Linux 6.0.5-060005-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 15:44:14 2022 InstallationDate: Installed on 2022-10-15 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.5-060005-generic root=/dev/mapper/vg_system-lv_root_ubuntu ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2022 dmi.bios.release: 8.9 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0809 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X670E-PLUS WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0809:bd10/23/2022:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:6F:D9:DD:4A:B0 ACL MTU: 1021:6 SCO MTU: 240:8 UP RUNNING PSCAN RX bytes:23811976 acl:17760 sco:359584 events:24845 errors:0 TX bytes:22808883 acl:832 sco:352705 commands:4782 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1995798/+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 1988364] Re: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality
** Also affects: bluez (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu Jammy) Status: New => Triaged ** Changed in: bluez (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: Triaged Bug description: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+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 1986796] Re: amd64-microcode conflicts with linux-firmware
This was also detected by autopkgtests: https://autopkgtest.ubuntu.com/packages/v/vrms/kinetic/amd64 ** Changed in: amd64-microcode (Ubuntu) Importance: Undecided => High ** Changed in: amd64-microcode (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu) Status: New => Triaged ** Tags added: rls-kk-incoming update-excuse -- 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/1986796 Title: amd64-microcode conflicts with linux-firmware Status in amd64-microcode package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Triaged Bug description: Occurs on kubuntu, gnome and xfce versions of kinetic proposed -- most recent updates ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: amd64-microcode 3.20191218.1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Aug 17 08:07:09 2022 InstallationDate: Installed on 2022-06-10 (67 days ago) InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220610) SourcePackage: amd64-microcode UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1986796/+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 1738272] Re: microcode packages, like firmware packages, should be in main
By the way, Debian created a new component, non-free-firmware, last month. I don't believe any Debian packages have switched to it yet. Based on this bug history, I'm guessing we'd want to automatically import those packages to universe then (or main where we want it part of our Canonical-supported set). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1738272 Title: microcode packages, like firmware packages, should be in main Status in firmware-sof package in Ubuntu: New Status in intel-microcode package in Ubuntu: Fix Released Status in iucode-tool package in Ubuntu: Fix Released Bug description: The MIR for intel-microcode and iucode-tool in LP: #139 requested that these packages be shipped in restricted. The iucode-tool package is free software, and is shipped in restricted only because of the circular recommends with intel-microcode. The intel-microcode package contains non-free software (free redistribution, but no source code). However, this code is not part of the OS; it runs /under/ the OS on the CPU, and is analogous to linux-firmware, which we do include in main. The question of suitability for restricted vs. main in Ubuntu was not examined as part of the previous MIR, and the security team signed off on it for "restricted or main as appropriate"; so I think the decision to put it in restricted was not based on a thorough examination of the facts by an archive admin, and does not represent a precedent that needs to be examined further. I believe that these two packages should be promoted to main for consistency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1738272/+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 1982739] Re: BlueZ 5.65 release
I've uploaded this to kinetic-proposed and am unsubscribing ubuntu- sponsors. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1982739 Title: BlueZ 5.65 release Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.65 to kinetic: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+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 1982739] Re: BlueZ 5.65 release
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1982739 Title: BlueZ 5.65 release Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.65 to kinetic: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+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 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?
I tried to use my MSI laptop with and without external displays, with battery saver mode + wifi disabled (ethernet connection) + Bluetooth disabled; and the battery life I have from 60% to 10% is of 1h55min with external monitors and of 2h28min without. So no drastic difference, here are the outputs of `cat /sys/bus/pci/devices/:03:00.1/power_state` and `grep . /sys/bus/pci/devices/:03:00.1/power/*` without external displays: mustang@MSI:~/mnt/gwdg$ cat /sys/bus/pci/devices/:03:00.1/power_state D0 mustang@MSI:~/mnt/gwdg$ grep . /sys/bus/pci/devices/:03:00.1/power/* /sys/bus/pci/devices/:03:00.1/power/async:enabled /sys/bus/pci/devices/:03:00.1/power/autosuspend_delay_ms:0 /sys/bus/pci/devices/:03:00.1/power/control:auto /sys/bus/pci/devices/:03:00.1/power/runtime_active_kids:0 /sys/bus/pci/devices/:03:00.1/power/runtime_active_time:18655975 /sys/bus/pci/devices/:03:00.1/power/runtime_enabled:enabled /sys/bus/pci/devices/:03:00.1/power/runtime_status:active /sys/bus/pci/devices/:03:00.1/power/runtime_suspended_time:19568 /sys/bus/pci/devices/:03:00.1/power/runtime_usage:0 /sys/bus/pci/devices/:03:00.1/power/wakeup:disabled I can also do a test with my windows partition if you wish, but I know I have ~9 to 10h of battery life from a 100% charge with battery saver mode, I don't think we'll ever match what I get with ubuntu atm. It's really a shame that MSI does not work more closely with linux distributions for those new high end laptops... (btw the keyboard backlight cannot be turned off on ubuntu neither, I have (i) to boot on windows, (ii) disable keyboard backlight with MSI center tool and (iii) reboot on my ubuntu partition. I've already tried almost everything proposed on the web). -- 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.
[Kernel-packages] [Bug 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?
Yes, one to my dGPU and one to my integrated GPU, but the battery life is not so different with and without I think (when traveling, the battery life is also terrible compared to when I'm on my windows partition for which I can get ~9h of autonomy, but maybe it's just MSI and windows softwares that are very well optimized for my laptop, MSI really pushed forward the battery life on this model). I can still do a proper check though, I'll keep you in touch in the next week. -- 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor:
[Kernel-packages] [Bug 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?
(I ran out of battery so I had to reboot between the first `grep . /sys/bus/pci/devices/:03:00.1/power/*` and the 2nd one) -- 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+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.lau
[Kernel-packages] [Bug 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?
Here are the outputs: mustang@MSI:~$ cat /sys/bus/pci/devices/:03:00.1/power_state D0 mustang@MSI:~$ grep . /sys/bus/pci/devices/:03:00.1/power/* /sys/bus/pci/devices/:03:00.1/power/async:enabled /sys/bus/pci/devices/:03:00.1/power/autosuspend_delay_ms:0 /sys/bus/pci/devices/:03:00.1/power/control:auto /sys/bus/pci/devices/:03:00.1/power/runtime_active_kids:0 /sys/bus/pci/devices/:03:00.1/power/runtime_active_time:656490 /sys/bus/pci/devices/:03:00.1/power/runtime_enabled:enabled /sys/bus/pci/devices/:03:00.1/power/runtime_status:active /sys/bus/pci/devices/:03:00.1/power/runtime_suspended_time:11048 /sys/bus/pci/devices/:03:00.1/power/runtime_usage:0 /sys/bus/pci/devices/:03:00.1/power/wakeup:disabled -- 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternatio
[Kernel-packages] [Bug 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?
here is the output of: `grep . /sys/bus/pci/devices/:03:00.0/power/*` : /sys/bus/pci/devices/:03:00.0/power/async:enabled /sys/bus/pci/devices/:03:00.0/power/autosuspend_delay_ms:5000 /sys/bus/pci/devices/:03:00.0/power/control:auto /sys/bus/pci/devices/:03:00.0/power/runtime_active_kids:0 /sys/bus/pci/devices/:03:00.0/power/runtime_active_time:8029428 /sys/bus/pci/devices/:03:00.0/power/runtime_enabled:enabled /sys/bus/pci/devices/:03:00.0/power/runtime_status:active /sys/bus/pci/devices/:03:00.0/power/runtime_suspended_time:1519 /sys/bus/pci/devices/:03:00.0/power/runtime_usage:2 /sys/bus/pci/devices/:03:00.0/power/wakeup:disabled -- 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.
[Kernel-packages] [Bug 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?
Sure, here is the output of `cat /sys/bus/pci/devices/:03:00.0/power_state`: D0 -- 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+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 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
I have verified that gnome-remote-desktop 42.1.1-0ubuntu1 depends on fuse3 ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done 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/1970411 Title: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3) Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in gnome-remote-desktop source package in Jammy: Fix Committed Status in gnome-remote-desktop package in Debian: Fix Released Bug description: Impact == GNOME Remote desktop crashes if fuse3 package is not installed as it provides fusermount3, that fuse_session_mount() implicitly requires. Test Case = Verify that gnome-remote-desktop has a dependency on fuse3 What Could Go Wrong == This just adds a dependency. This bug should be very uncommon because a system without fuse3 also wouldn't have xdg-desktop-portal installed meaning Snaps don't work and wouldn't have ubuntu-desktop-minimal installed. Other Info = libfuse3 is currently suggesting fusermount3, I'm wondering if we should instead recommending it, given that one of the library function relies on that. It's possible for things to use the library without that function so that's why it's proposed to be only a Recommends and not a Depends. For Ubuntu 22.10, we should see if the kernel can support this natively without needing fusermount3 as suggested in comment 1. Stack trace: #0 g_log_structured_array (log_level=, fields=0x7f7859fefdd0, n_fields=3) at ../../../glib/gmessages.c:557 writer_func = writer_user_data = recursion = depth = __func__ = "g_log_structured_array" _g_boolean_var_ = #1 0x7f79092e2f99 in g_log_default_handler (log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE filesystem", unused_data=unused_data@entry=0x0) at ../../../glib/gmessages.c:3295 fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 0x7f790939a109, length = -1}, {key = 0x7f790932a09f "\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 140157821898257}} n_fields = #2 0x7f79092e43fa in g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR, format=, args=) at ../../../glib/gmessages.c:1387 domain = 0x0 data = 0x0 depth = log_func = 0x7f79092e2ee0 domain_fatal_mask = masquerade_fatal = 0 test_level = 6 was_fatal = was_recursion = buffer = msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE filesystem" msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE filesystem" i = 2 size = #3 0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 "[FUSE Clipboard] Failed to mount FUSE filesystem") at ../../../glib/gmessages.c:1456 args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7f7859ff, reg_save_area = 0x7f7859feff40}} #4 0x5605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at ../src/grd-rdp-fuse-clipboard.c:1321 rdp_fuse_clipboard = 0x5605ed301820 args = {argc = 1, argv = 0x7f7860001070, allocated = 1} argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"} result = Further details: - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970411/+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 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: fuse3 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: fuse3 (Ubuntu) ** No longer affects: fuse3 (Ubuntu Jammy) ** No longer affects: linux (Ubuntu Jammy) ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- 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/1970411 Title: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3) Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in gnome-remote-desktop source package in Jammy: In Progress Status in gnome-remote-desktop package in Debian: Fix Released Bug description: Impact == GNOME Remote desktop crashes if fuse3 package is not installed as it provides fusermount3, that fuse_session_mount() implicitly requires. Test Case = Verify that gnome-remote-desktop has a dependency on fuse3 What Could Go Wrong == This just adds a dependency. This bug should be very uncommon because a system without fuse3 also wouldn't have xdg-desktop-portal installed meaning Snaps don't work and wouldn't have ubuntu-desktop-minimal installed. Other Info = libfuse3 is currently suggesting fusermount3, I'm wondering if we should instead recommending it, given that one of the library function relies on that. It's possible for things to use the library without that function so that's why it's proposed to be only a Recommends and not a Depends. For Ubuntu 22.10, we should see if the kernel can support this natively without needing fusermount3 as suggested in comment 1. Stack trace: #0 g_log_structured_array (log_level=, fields=0x7f7859fefdd0, n_fields=3) at ../../../glib/gmessages.c:557 writer_func = writer_user_data = recursion = depth = __func__ = "g_log_structured_array" _g_boolean_var_ = #1 0x7f79092e2f99 in g_log_default_handler (log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE filesystem", unused_data=unused_data@entry=0x0) at ../../../glib/gmessages.c:3295 fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 0x7f790939a109, length = -1}, {key = 0x7f790932a09f "\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 140157821898257}} n_fields = #2 0x7f79092e43fa in g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR, format=, args=) at ../../../glib/gmessages.c:1387 domain = 0x0 data = 0x0 depth = log_func = 0x7f79092e2ee0 domain_fatal_mask = masquerade_fatal = 0 test_level = 6 was_fatal = was_recursion = buffer = msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE filesystem" msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE filesystem" i = 2 size = #3 0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 "[FUSE Clipboard] Failed to mount FUSE filesystem") at ../../../glib/gmessages.c:1456 args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7f7859ff, reg_save_area = 0x7f7859feff40}} #4 0x5605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at ../src/grd-rdp-fuse-clipboard.c:1321 rdp_fuse_clipboard = 0x5605ed301820 args = {argc = 1, argv = 0x7f7860001070, allocated = 1} argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"} result = Further details: - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970411/+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 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?
Yes as I said I ignored this error first (I did not even know what this meant). But then I experienced very low battery life on my ubuntu partition so I dug into that problem and learned that disabling my discrete graphic card could be an option. Doing so involves knowing the correct acpi_call to send it directly or via vga_switcheroo which I guess will send this same false call that the kernel is sending at boot. -- 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notificat
[Kernel-packages] [Bug 1973633] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590135/+files/ProcInterrupts.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590140/+files/WifiSyslog.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590138/+files/RfKill.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590136/+files/ProcModules.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590126/+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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590137/+files/PulseList.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590133/+files/ProcCpuinfoMinimal.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kerne
[Kernel-packages] [Bug 1973633] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590132/+files/ProcCpuinfo.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590131/+files/PaInfo.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590141/+files/acpidump.txt ** 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.la
[Kernel-packages] [Bug 1973633] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590139/+files/UdevDb.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590134/+files/ProcEnviron.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590130/+files/Lsusb-v.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590129/+files/Lsusb-t.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590128/+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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590127/+files/Lspci-vt.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590124/+files/CurrentDmesg.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590123/+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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https:
[Kernel-packages] [Bug 1973633] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590122/+files/AudioDevicesInUse.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kerne
[Kernel-packages] [Bug 1973633] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590125/+files/IwConfig.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-08 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/28/2021 dmi.bios.release: 1.5 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15CKAMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-15CK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: dmi.product.family: Delta dmi.product.name: Delta 15 A5EFK dmi.product.sku: 15CK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973633/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1973633] Re: wrong acpi_call sent at boot, how to disable discrete graphic card?
apport information ** Tags added: apport-collected jammy ** Description changed: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-05-08 (8 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: Micro-Star International Co., Ltd. Delta 15 A5EFK + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=78719e21-6069-4e4d-b5a1-a64916f89efe ro quiet splash acpi_backlight=vendor vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-27-generic N/A + linux-backports-modules-5.15.0-27-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3 + Tags: jammy + Uname: Linux 5.15.0-27-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/28/2021 + dmi.bios.release: 1.5 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: E15CKAMS.105 + dmi.board.asset.tag: Default string + dmi.board.name: MS-15CK + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: REV:1.0 + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 10 + dmi.chassis.vendor: Micro-Star International Co., Ltd. + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15CKAMS.105:bd10/28/2021:br1.5:svnMicro-StarInternationalCo.,Ltd.:pnDelta15A5EFK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15CK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku15CK.1: + dmi.product.family: Delta + dmi.product.name: Delta 15 A5EFK + dmi.product.sku: 15CK.1 + dmi.product.version: REV:1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1973633/+attachment/5590121/+files/AlsaInfo.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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Confirmed Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Rade
[Kernel-packages] [Bug 1973633] [NEW] wrong acpi_call sent at boot, how to disable discrete graphic card?
Public bug reported: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call? Adittional output asked by the doc: mustang@MSI:~$ sudo grep -i switcheroo /boot/config-* /boot/config-5.15.0-25-generic:CONFIG_VGA_SWITCHEROO=y /boot/config-5.15.0-27-generic:CONFIG_VGA_SWITCHEROO=y Thank you for you help, Best regards, Jeremy ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: acpi graphics grub hybrid ** Attachment added: "outputs of 'cat /proc/version_signature', 'sudo lspci -vnvn', 'less /boot/grub/grub.cfg', 'sudo apt list | grep -i gpu', 'sh get-acpi-info.sh' (see https://launchpad.net/~hybrid-graphics-linux)" https://bugs.launchpad.net/bugs/1973633/+attachment/5590120/+files/version_lscpi_grub.sfg_aptlist_get-acpi-info.zip -- 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/1973633 Title: wrong acpi_call sent at boot, how to disable discrete graphic card? Status in linux package in Ubuntu: Incomplete Bug description: Hi to the Ubuntu team, Key info: MSI Delta 15 A5EFK laptop dual boot Ubuntu 22.04 LTS/Windows 11 Ubuntu 5.15.0-27.28-generic 5.15.30 hybrid graphic cards: AMD RX6700M + AMD Radeon 8 Graphics Renoir (in AMD Ryzen 9 5900HX) open source amdgpu drivers I tried to combined one bug report with one related question hoping this is fine. -The bug- I've noticed the following error when booting on my ubuntu partition: [0.649628] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.GP17.MP2], AE_NOT_FOUND (20210730/psargs-330) [0.650162] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) /dev/nvme0n1p6: clean, 219896/6725632 files, 3948761/2688 blocks I did not really worried about that first. But then when I wanted to reduce my battery draining on my ubuntu partition (half of the battery life on my windows partition for similar usage) I've seen that disabling my discrete graphic card could be one thing to try to reduce power consumption. So I thought about using (i) acpi_call as stated or (ii) vga_switcheroo as stated in https://help.ubuntu.com/community/HybridGraphics . However, for (i) I need to know the correct calls to send to ACPI and my latptop is not listed here: https://hybrid-graphics- linux.tuxfamily.org/index.php?title=ACPI_calls and obviously the call that the kernel is trying to send at boot (for whatever reason) is also wrong. For (ii) I think that vga_switcheroo is also using acpi_call under the hood to disable the discrete graphic card. Which leads now to: -Question- Can I use vga_switcheroo knowing that my kernel is sending false acpi_call? I just want to be really sure about what I'm doing here because the doc states to modifiy the grub config and I'm really not confortable with dealing with the boot manager knowing the above bug. Is there a way to find the correct ACPI call?
[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
1, argv = 0x7f7860001070, allocated = 1} + argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"} + result = Further details: - - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f + - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f ** Changed in: gnome-remote-desktop (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-remote-desktop (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- 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/1970411 Title: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3) Status in fuse3 package in Ubuntu: Incomplete Status in gnome-remote-desktop package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in gnome-remote-desktop package in Debian: New Bug description: Impact == GNOME Remote desktop crashes if fuse3 package is not installed as it provides fusermount3, that fuse_session_mount() implicitly requires. Test Case = Verify that gnome-remote-desktop has a dependency on fuse3 What Could Go Wrong == This just adds a dependency. This bug should be very uncommon because a system without fuse3 also wouldn't have xdg-desktop-portal installed meaning Snaps don't work and wouldn't have ubuntu-desktop-minimal installed. Other Info = libfuse3 is currently suggesting fusermount3, I'm wondering if we should instead recommending it, given that one of the library function relies on that. It's possible for things to use the library without that function so that's why it's proposed to be only a Recommends and not a Depends. For Ubuntu 22.10, we should see if the kernel can support this natively without needing fusermount3 as suggested in comment 1. Stack trace: #0 g_log_structured_array (log_level=, fields=0x7f7859fefdd0, n_fields=3) at ../../../glib/gmessages.c:557 writer_func = writer_user_data = recursion = depth = __func__ = "g_log_structured_array" _g_boolean_var_ = #1 0x7f79092e2f99 in g_log_default_handler (log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE filesystem", unused_data=unused_data@entry=0x0) at ../../../glib/gmessages.c:3295 fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 0x7f790939a109, length = -1}, {key = 0x7f790932a09f "\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 140157821898257}} n_fields = #2 0x7f79092e43fa in g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR, format=, args=) at ../../../glib/gmessages.c:1387 domain = 0x0 data = 0x0 depth = log_func = 0x7f79092e2ee0 domain_fatal_mask = masquerade_fatal = 0 test_level = 6 was_fatal = was_recursion = buffer = msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE filesystem" msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE filesystem" i = 2 size = #3 0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 "[FUSE Clipboard] Failed to mount FUSE filesystem") at ../../../glib/gmessages.c:1456 args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7f7859ff, reg_save_area = 0x7f7859feff40}} #4 0x5605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at ../src/grd-rdp-fuse-clipboard.c:1321 rdp_fuse_clipboard = 0x5605ed301820 args = {argc = 1, argv = 0x7f7860001070, allocated = 1} argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"} result = Further details: - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1970411/+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 1970412] Re: [VROC] Ubuntu doesn't support 3rd SATA
** Package changed: bugzilla (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970412 Title: [VROC] Ubuntu doesn't support 3rd SATA Status in linux package in Ubuntu: Incomplete Bug description: An effort has been made to enable 3rd SATA support in kernel, but unfortunately the patch didn't make it to upstream (we are still working to make it happen). Without it certain utility programs cannot function properly when 3rd SATA is engaged. The patch itself adds Intel Emmitsburg PCH RAID PCI IDs to the list of supported controllers. Would you kindly apply this patch to 22.04 release? Patch to be applied: https://lore.kernel.org/linux- ide/20201119104318.79297-1-mika.westerb...@linux.intel.com/ Regards, Lukasz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970412/+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 1970117] Re: Atheros firmware missing in Ubuntu 22.04
Appears to be caused by https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux- firmware/commit/?h=jammy=dbcbb9a7d73fe21b2bae56df7f314af307a9708f -- 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/1970117 Title: Atheros firmware missing in Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: linux-firmware 20220329.git681281e4-0ubuntu1 used by Ubuntu 22.04 does not contain drivers for some Atheros WiFi/Bluetooth chipsets, which were included in the previous Ubuntu releases. The package is missing some files from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree, specifically: - ar3k (whole directory, was present in impish, missing in jammy) - ar*.fw - firmware for AR7010, AR9170 and AR9271 (can't find in the impish version) Because of that Bluetooth can't be enabled and WiFi is unstable on devices equipped with Atheros chipsets. In my case the following errors are reported by dmesg: [3.653613] usb 1-1.1: Direct firmware load for ar3k/AthrBT_0x1102.dfu failed with error -2 [3.653619] Bluetooth: Patch file not found ar3k/AthrBT_0x1102.dfu [3.653626] Bluetooth: Loading patch file failed [3.653631] ath3k: probe of 1-1.1:1.0 failed with error -2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: krzys 1642 F pulseaudio CasperMD5CheckResult: unknown Date: Sun Apr 24 17:32:11 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2018-11-06 (1265 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Aspire E1-571G PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ee6503b7-82f1-4ece-9e74-935ca46a08f4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-24 (0 days ago) dmi.bios.date: 12/25/2012 dmi.bios.release: 2.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:br2.11:efr0.0:svnAcer:pnAspireE1-571G:pvrV2.11:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11:skuAspireE1-571G_064C_V2.11: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571G dmi.product.sku: Aspire E1-571G_064C_V2.11 dmi.product.version: V2.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1970117/+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 1970117] Re: Atheros firmware missing in Ubuntu 22.04
Something is also wrong with the kernel source as these older Atheros wifi devices that used the ath9k wifi module had bluetooth devices that used the ath3k-1.fw firmware not the dfu files like the ath10k wifi/BT I would bet we need https://www.spinics.net/lists/stable/msg524224.html to fix this -- 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/1970117 Title: Atheros firmware missing in Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: linux-firmware 20220329.git681281e4-0ubuntu1 used by Ubuntu 22.04 does not contain drivers for some Atheros WiFi/Bluetooth chipsets, which were included in the previous Ubuntu releases. The package is missing some files from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree, specifically: - ar3k (whole directory, was present in impish, missing in jammy) - ar*.fw - firmware for AR7010, AR9170 and AR9271 (can't find in the impish version) Because of that Bluetooth can't be enabled and WiFi is unstable on devices equipped with Atheros chipsets. In my case the following errors are reported by dmesg: [3.653613] usb 1-1.1: Direct firmware load for ar3k/AthrBT_0x1102.dfu failed with error -2 [3.653619] Bluetooth: Patch file not found ar3k/AthrBT_0x1102.dfu [3.653626] Bluetooth: Loading patch file failed [3.653631] ath3k: probe of 1-1.1:1.0 failed with error -2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: krzys 1642 F pulseaudio CasperMD5CheckResult: unknown Date: Sun Apr 24 17:32:11 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2018-11-06 (1265 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Aspire E1-571G PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ee6503b7-82f1-4ece-9e74-935ca46a08f4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-24 (0 days ago) dmi.bios.date: 12/25/2012 dmi.bios.release: 2.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.11 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:br2.11:efr0.0:svnAcer:pnAspireE1-571G:pvrV2.11:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11:skuAspireE1-571G_064C_V2.11: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571G dmi.product.sku: Aspire E1-571G_064C_V2.11 dmi.product.version: V2.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1970117/+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 1909005] acpidump.txt
apport information 5.15 report sent. Same problem also with 5.17 and 5.18 kernels. Observations: entering suspend I see a plain orange screen with a big clock for just an instant before black out. Pressing a key will spin the fan for a few seconds but never show anything onscreen. Only way out I've found is power off & reboot. :( Dual boot machine. Wakes OK in Windows 10. ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578860/+files/acpidump.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578859/+files/WifiSyslog.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578857/+files/RfKill.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578858/+files/UdevDb.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578845/+files/IwConfig.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578856/+files/PulseList.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578855/+files/ProcModules.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578854/+files/ProcInterrupts.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578848/+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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578847/+files/Lspci-vt.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578853/+files/ProcCpuinfoMinimal.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578850/+files/Lsusb-v.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578852/+files/ProcCpuinfo.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578851/+files/PaInfo.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578846/+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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578849/+files/Lsusb-t.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578844/+files/CurrentDmesg.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578842/+files/AlsaInfo.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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1909005/+attachment/5578843/+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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1909005] Re: Ubuntu does not resume (wake up) from suspend
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeremy 2511 F pulseaudio /dev/snd/controlC0: jeremy 2511 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-19 (141 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Dell Inc. Inspiron 15-3565 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-lowlatency root=UUID=e7577721-a14d-4c90-aef5-4dd634cb9a96 ro threadirqs splash nomodeset vt.handoff=1 ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-lowlatency N/A linux-backports-modules-5.15.0-23-lowlatency N/A linux-firmware20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-23-lowlatency x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-07 (2 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/03/2018 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: Inspiron 15-3565 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd09/03/2018:br1.10:svnDellInc.:pnInspiron15-3565:pvr1.10.1:rvnDellInc.:rnInspiron15-3565:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:sku078E: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3565 dmi.product.sku: 078E dmi.product.version: 1.10.1 dmi.sys.vendor: Dell Inc. ** Tags added: apport-collected 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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sy
[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted
Same here. High pitched sound modulated by sine wave every 2 seconds. 48000 sampling rate doesn't work for me, either. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966066 Title: audio from external sound card is distorted Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: The sound card is a Focusrite Scarlett 2i2. The sound is distorted everywhere. Sound via HDMI works. Seen others having the same problem: (Edit because of previously wrong link here) https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card ubuntu release: Ubuntu 20.04.4 LTS package name involved in bug: linux-image-5.13.0-37-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:56:02 2022 InstallationDate: Installed on 2020-12-18 (459 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+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 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings
I closed the gnome-bluetooth part of this bug since this was apparently fixed in pulseaudio instead. ** Changed in: gnome-bluetooth (Ubuntu Xenial) Status: New => Invalid ** Changed in: gnome-bluetooth (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1283003 Title: Bluetooth headset/speakers listed but not selectable in Sound settings Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in blueman source package in Xenial: New Status in gnome-bluetooth source package in Xenial: Invalid Status in pulseaudio source package in Xenial: Fix Released Bug description: [Impact] Bluetooth headset/speakers are listed but not selectable in Sound settings (the correct device's options don't appear in the right pane). Hence no Bluetooth audio is unusable. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and try to select the device. Expected: The Bluetooth audio device is selectable (its options appear in the right pane when clicked and the selection stays on that device). [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+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 1949304] Re: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess retur
See https://askubuntu.com/a/1163018/300665 -- 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/1949304 Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: Tried to install on 20.04.3 Ubuntu Gnome andwill not load.Trying to get WiFi on Dell Optiplex 9020 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-3.5.0-30:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 31 12:38:49 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-10-30 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1949304/+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 1949304] Re: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess retur
You should be able to install the driver from the driver manager or by using this command in terminal with an ethernet connection sudo apt update && sudo apt install bcmwl-kernel-source -- 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/1949304 Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: Tried to install on 20.04.3 Ubuntu Gnome andwill not load.Trying to get WiFi on Dell Optiplex 9020 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-3.5.0-30:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 31 12:38:49 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-10-30 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1949304/+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 1949304] Re: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess retur
How are you trying to install? Did you download the bcmwl-kernel-source from a website? That version for bcmwl seems to be from 9 years ago -- 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/1949304 Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: Tried to install on 20.04.3 Ubuntu Gnome andwill not load.Trying to get WiFi on Dell Optiplex 9020 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-3.5.0-30:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 31 12:38:49 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-10-30 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1949304/+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 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
Same issue here on ubuntu 21.04, i was wondering why my power emptied overnight. ❯ sudo cat /sys/power/mem_sleep [s2idle] ❯ sudo dmesg | grep "suspend entry" [sudo] password for jeremy: [ 2739.515120] PM: suspend entry (s2idle) [22012.050938] PM: suspend entry (s2idle) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+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 1932303] Re: Dell XPS 17 9700 sound not working on linux-oem-5.10
** Summary changed: - Dell XPS 17 9700 wifi + Dell XPS 17 9700 sound not working on linux-oem-5.10 ** Summary changed: - Dell XPS 17 9700 sound not working on linux-oem-5.10 + Dell XPS 17 9700 microphone not working on linux-oem-5.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932303 Title: Dell XPS 17 9700 microphone not working on linux-oem-5.10 Status in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Bug description: Release: devops@devops-XPS-17-9700:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 devops@devops-XPS-17-9700:~$ Problem: Cannot get both wifi and sound working on a Dell XPS 17 9700 (i9 processor) at the same time. With the 5.10.0-1029-oem kernel wifi works, but sound (microphone) does not. With the 5.11.0-20-generic kernel, the microphone and sound works (thank you for fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632) but the wifi does not. With the 5.11.0-20-generic kernel and the linux-firmware (1.187.14) pkg installed (sound works but no wifi): Information with 5.11.0-20-generic kernel: devops@devops-XPS-17-9700:~$ sudo lspci -knn | grep Net -A3; rfkill list [sudo] password for devops: 04:00.0 Network controller [0280]: Qualcomm Device [17cb:1101] (rev 01) Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci 05:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 0: hci0: Bluetooth Soft blocked: no Hard blocked: no devops@devops-XPS-17-9700:~$ sudo lshw -C network *-network description: Network controller product: Qualcomm vendor: Qualcomm physical id: 0 bus info: pci@:04:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:195 memory:d210-d21f devops@devops-XPS-17-9700:~$ uname -sr Linux 5.11.0-20-generic devops@devops-XPS-17-9700:~$ sudo dmesg | grep ath11k [2.671864] ath11k_pci :04:00.0: WARNING: ath11k PCI support is experimental! [2.679263] ath11k_pci :04:00.0: BAR 0: assigned [mem 0xd210-0xd21f 64bit] [2.679309] ath11k_pci :04:00.0: enabling device ( -> 0002) devops@devops-XPS-17-9700:~$ sudo dpkg -l | grep firmware ii amd64-microcode 3.20191218.1ubuntu1 amd64Processor microcode firmware for AMD CPUs ii intel-microcode 3.20201110.0ubuntu0.20.04.2 amd64Processor microcode firmware for Intel CPUs ii linux-firmware 1.187.14 all Firmware for Linux kernel drivers devops@devops-XPS-17-9700:~$ sudo ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever devops@devops-XPS-17-9700:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1932303/+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 1932303] Re: Dell XPS 17 9700 wifi
** Changed in: linux-oem-5.10 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932303 Title: Dell XPS 17 9700 wifi Status in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Bug description: Release: devops@devops-XPS-17-9700:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 devops@devops-XPS-17-9700:~$ Problem: Cannot get both wifi and sound working on a Dell XPS 17 9700 (i9 processor) at the same time. With the 5.10.0-1029-oem kernel wifi works, but sound (microphone) does not. With the 5.11.0-20-generic kernel, the microphone and sound works (thank you for fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632) but the wifi does not. With the 5.11.0-20-generic kernel and the linux-firmware (1.187.14) pkg installed (sound works but no wifi): Information with 5.11.0-20-generic kernel: devops@devops-XPS-17-9700:~$ sudo lspci -knn | grep Net -A3; rfkill list [sudo] password for devops: 04:00.0 Network controller [0280]: Qualcomm Device [17cb:1101] (rev 01) Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci 05:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 0: hci0: Bluetooth Soft blocked: no Hard blocked: no devops@devops-XPS-17-9700:~$ sudo lshw -C network *-network description: Network controller product: Qualcomm vendor: Qualcomm physical id: 0 bus info: pci@:04:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:195 memory:d210-d21f devops@devops-XPS-17-9700:~$ uname -sr Linux 5.11.0-20-generic devops@devops-XPS-17-9700:~$ sudo dmesg | grep ath11k [2.671864] ath11k_pci :04:00.0: WARNING: ath11k PCI support is experimental! [2.679263] ath11k_pci :04:00.0: BAR 0: assigned [mem 0xd210-0xd21f 64bit] [2.679309] ath11k_pci :04:00.0: enabling device ( -> 0002) devops@devops-XPS-17-9700:~$ sudo dpkg -l | grep firmware ii amd64-microcode 3.20191218.1ubuntu1 amd64Processor microcode firmware for AMD CPUs ii intel-microcode 3.20201110.0ubuntu0.20.04.2 amd64Processor microcode firmware for Intel CPUs ii linux-firmware 1.187.14 all Firmware for Linux kernel drivers devops@devops-XPS-17-9700:~$ sudo ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever devops@devops-XPS-17-9700:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1932303/+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 1932303] Re: Dell XPS 17 9700 wifi
Unfortunately 5.11.0-20-generic does NOT fix the wifi. As you can see in the dmesg output above, the ath11k driver is present but doesn't seem to enable any interfaces. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932303 Title: Dell XPS 17 9700 wifi Status in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Incomplete Bug description: Release: devops@devops-XPS-17-9700:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 devops@devops-XPS-17-9700:~$ Problem: Cannot get both wifi and sound working on a Dell XPS 17 9700 (i9 processor) at the same time. With the 5.10.0-1029-oem kernel wifi works, but sound (microphone) does not. With the 5.11.0-20-generic kernel, the microphone and sound works (thank you for fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632) but the wifi does not. With the 5.11.0-20-generic kernel and the linux-firmware (1.187.14) pkg installed (sound works but no wifi): Information with 5.11.0-20-generic kernel: devops@devops-XPS-17-9700:~$ sudo lspci -knn | grep Net -A3; rfkill list [sudo] password for devops: 04:00.0 Network controller [0280]: Qualcomm Device [17cb:1101] (rev 01) Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci 05:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 0: hci0: Bluetooth Soft blocked: no Hard blocked: no devops@devops-XPS-17-9700:~$ sudo lshw -C network *-network description: Network controller product: Qualcomm vendor: Qualcomm physical id: 0 bus info: pci@:04:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:195 memory:d210-d21f devops@devops-XPS-17-9700:~$ uname -sr Linux 5.11.0-20-generic devops@devops-XPS-17-9700:~$ sudo dmesg | grep ath11k [2.671864] ath11k_pci :04:00.0: WARNING: ath11k PCI support is experimental! [2.679263] ath11k_pci :04:00.0: BAR 0: assigned [mem 0xd210-0xd21f 64bit] [2.679309] ath11k_pci :04:00.0: enabling device ( -> 0002) devops@devops-XPS-17-9700:~$ sudo dpkg -l | grep firmware ii amd64-microcode 3.20191218.1ubuntu1 amd64Processor microcode firmware for AMD CPUs ii intel-microcode 3.20201110.0ubuntu0.20.04.2 amd64Processor microcode firmware for Intel CPUs ii linux-firmware 1.187.14 all Firmware for Linux kernel drivers devops@devops-XPS-17-9700:~$ sudo ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever devops@devops-XPS-17-9700:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1932303/+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 1933274] [NEW] TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)"
Public bug reported: Tracing this back, I found the current Ubuntu 5.11 kernel has incorrect offsets for some platforms (TGL-H and ADL). I created an upstream bug at https://gitlab.freedesktop.org/drm/intel/-/issues/3662 and was directed to a commit, 5d0c938ec9cc, that ought to fix this issue. See the attached patch file for this commit applied to the current Ubuntu 5.11 kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Patch added: "i915-load-dram-from-pcode.patch" https://bugs.launchpad.net/bugs/1933274/+attachment/5506308/+files/i915-load-dram-from-pcode.patch -- 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/1933274 Title: TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)" Status in linux package in Ubuntu: New Bug description: Tracing this back, I found the current Ubuntu 5.11 kernel has incorrect offsets for some platforms (TGL-H and ADL). I created an upstream bug at https://gitlab.freedesktop.org/drm/intel/-/issues/3662 and was directed to a commit, 5d0c938ec9cc, that ought to fix this issue. See the attached patch file for this commit applied to the current Ubuntu 5.11 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933274/+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 1932303] Re: Dell XPS 17 9700 wifi
What I'd like to see is the sound fixes from 5.11.0-20-generic kernel make it into the OEM kernel so that both wifi and sound work on the Dell XPS 17 9700. ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932303 Title: Dell XPS 17 9700 wifi Status in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Bug description: Release: devops@devops-XPS-17-9700:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 devops@devops-XPS-17-9700:~$ Problem: Cannot get both wifi and sound working on a Dell XPS 17 9700 (i9 processor) at the same time. With the 5.10.0-1029-oem kernel wifi works, but sound (microphone) does not. With the 5.11.0-20-generic kernel, the microphone and sound works (thank you for fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632) but the wifi does not. With the 5.11.0-20-generic kernel and the linux-firmware (1.187.14) pkg installed (sound works but no wifi): Information with 5.11.0-20-generic kernel: devops@devops-XPS-17-9700:~$ sudo lspci -knn | grep Net -A3; rfkill list [sudo] password for devops: 04:00.0 Network controller [0280]: Qualcomm Device [17cb:1101] (rev 01) Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci 05:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 0: hci0: Bluetooth Soft blocked: no Hard blocked: no devops@devops-XPS-17-9700:~$ sudo lshw -C network *-network description: Network controller product: Qualcomm vendor: Qualcomm physical id: 0 bus info: pci@:04:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:195 memory:d210-d21f devops@devops-XPS-17-9700:~$ uname -sr Linux 5.11.0-20-generic devops@devops-XPS-17-9700:~$ sudo dmesg | grep ath11k [2.671864] ath11k_pci :04:00.0: WARNING: ath11k PCI support is experimental! [2.679263] ath11k_pci :04:00.0: BAR 0: assigned [mem 0xd210-0xd21f 64bit] [2.679309] ath11k_pci :04:00.0: enabling device ( -> 0002) devops@devops-XPS-17-9700:~$ sudo dpkg -l | grep firmware ii amd64-microcode 3.20191218.1ubuntu1 amd64Processor microcode firmware for AMD CPUs ii intel-microcode 3.20201110.0ubuntu0.20.04.2 amd64Processor microcode firmware for Intel CPUs ii linux-firmware 1.187.14 all Firmware for Linux kernel drivers devops@devops-XPS-17-9700:~$ sudo ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever devops@devops-XPS-17-9700:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1932303/+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 1932303] Re: Dell XPS 17 9700 wifi
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932303 Title: Dell XPS 17 9700 wifi Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Release: devops@devops-XPS-17-9700:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 devops@devops-XPS-17-9700:~$ Problem: Cannot get both wifi and sound working on a Dell XPS 17 9700 (i9 processor) at the same time. With the 5.10.0-1029-oem kernel wifi works, but sound (microphone) does not. With the 5.11.0-20-generic kernel, the microphone and sound works (thank you for fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632) but the wifi does not. With the 5.11.0-20-generic kernel and the linux-firmware (1.187.14) pkg installed (sound works but no wifi): Information with 5.11.0-20-generic kernel: devops@devops-XPS-17-9700:~$ sudo lspci -knn | grep Net -A3; rfkill list [sudo] password for devops: 04:00.0 Network controller [0280]: Qualcomm Device [17cb:1101] (rev 01) Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci 05:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 0: hci0: Bluetooth Soft blocked: no Hard blocked: no devops@devops-XPS-17-9700:~$ sudo lshw -C network *-network description: Network controller product: Qualcomm vendor: Qualcomm physical id: 0 bus info: pci@:04:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:195 memory:d210-d21f devops@devops-XPS-17-9700:~$ uname -sr Linux 5.11.0-20-generic devops@devops-XPS-17-9700:~$ sudo dmesg | grep ath11k [2.671864] ath11k_pci :04:00.0: WARNING: ath11k PCI support is experimental! [2.679263] ath11k_pci :04:00.0: BAR 0: assigned [mem 0xd210-0xd21f 64bit] [2.679309] ath11k_pci :04:00.0: enabling device ( -> 0002) devops@devops-XPS-17-9700:~$ sudo dpkg -l | grep firmware ii amd64-microcode 3.20191218.1ubuntu1 amd64Processor microcode firmware for AMD CPUs ii intel-microcode 3.20201110.0ubuntu0.20.04.2 amd64Processor microcode firmware for Intel CPUs ii linux-firmware 1.187.14 all Firmware for Linux kernel drivers devops@devops-XPS-17-9700:~$ sudo ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever devops@devops-XPS-17-9700:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1932303/+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 1927768] Re: No Bluetooth device found
You can try rtbth-dkms from https://launchpad.net/~blaze/+archive/ubuntu/rtbth-dkms I don't think the RT3290 ever had bluetooth support in the kernel -- 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/1927768 Title: No Bluetooth device found Status in linux package in Ubuntu: Confirmed Bug description: My laptop HP Probook 450 g0 has a bluetooth device. But my Ubuntu 20.04 can't find this device. I tried dmesg | grep -i blue -> No output I know my laptop has bluetooth device for sure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-72-generic 5.4.0-72.80 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vivek 3179 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 7 22:07:40 2021 HibernationDevice: RESUME=UUID=91721efb-c835-42a1-a739-b90f5b9e1c5d InstallationDate: Installed on 2017-05-22 (1445 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP ProBook 450 G0 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=c3fba244-e5d3-42d6-ab29-cbc5d705c6e9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-72-generic N/A linux-backports-modules-5.4.0-72-generic N/A linux-firmware1.187.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRF Ver. F.63 dmi.board.name: 1949 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.0F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRFVer.F.63:bd06/03/2016:svnHewlett-Packard:pnHPProBook450G0:pvrA2018CD200:rvnHewlett-Packard:rn1949:rvrKBCVersion90.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G0 dmi.product.sku: F9S12PA#ACJ dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927768/+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