[Kernel-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
Tested with fresh installed focal on machine with Nvidia GPU. Enabled -proposed channel and install ubuntu-drivers-common 1:0.9.0~0.20.04.8. Execute command "sudo ubuntu-drivers install" and Nvidia driver 530 and related packages will be installed. Executed command "sudo ubuntu- drivers install nvidia:515-open" and Nvidia open driver 515 and related packages will be installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
Tested with fresh installed jammy on machine with Nvidia GPU. Enabled -proposed channel and install ubuntu-drivers-common 0.9.6.2~0.22.04.3. Execute command "sudo ubuntu-drivers install" and Nvidia driver 530 and related packages will be installed. Executed command "sudo ubuntu- drivers install nvidia:515-open" and Nvidia open driver 515 and related packages will be installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Tested on machine with FM350 installed, with oem 6.0.0-1006 kernel, modem manager 1.20.0-1~ubuntu22.04.1, libmbim-glib4 1.28.0-1~ubuntu20.04 and libqmi-glib5 1.32.0-1~ubuntu0.22.04.1. System can connect to 5g network. --- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: b429ecd3cf5b14431f765b3a415cda29db1d504b --- Hardware | manufacturer: generic | model: MBIM [14C3:4D75] | firmware revision: 81600..00.29.21.24_GC | D47 | h/w revision: V1.0.6 | supported: gsm-umts, lte, 5gnr |current: gsm-umts, lte, 5gnr | equipment id: 358198520003138 --- System| device: /sys/devices/pci:00/:00:1c.0/:71:00.0 |drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 | ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) --- Status| lock: sim-pin2 | unlock retries: sim-pin2 (3) | state: connected |power state: on |access tech: lte, 5gnr | signal quality: 64% (cached) --- Modes | supported: allowed: 3g; preferred: none | allowed: 4g; preferred: none | allowed: 3g, 4g; preferred: none | allowed: 5g; preferred: none | allowed: 3g, 5g; preferred: none | allowed: 4g, 5g; preferred: none | allowed: 3g, 4g, 5g; preferred: none |current: allowed: 3g, 4g, 5g; preferred: none --- IP| supported: ipv4, ipv6, ipv4v6 --- 3GPP | imei: 358198520003138 | enabled locks: fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached --- 3GPP EPS | ue mode of operation: csps-2 |initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 | initial bearer apn: internet | initial bearer ip type: ipv4v6 --- 3GPP 5GNR | mico mode: disabled --- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 (active) | slot 2: /org/freedesktop/ModemManager1/SIM/1 --- Bearer| paths: /org/freedesktop/ModemManager1/Bearer/1 ** 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Fix Committed Status in libqmi source package in Jammy: Fix Committed Status in linux source package in Jammy: New Status in modemmanager source package in Jammy: Fix Committed Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01)
[Kernel-packages] [Bug 1992435] Re: sof-hda-dsp Dmic0 not initial correctly
debdiff for jammy ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1992435/+attachment/5622937/+files/alsa-ucm-conf_1.2.6.3-1ubuntu2.debdiff ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Dirk Su (dirksu) ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1992435 Title: sof-hda-dsp Dmic0 not initial correctly Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Device use sof-hda-dsp driver will not able to initial the Dmic0 status correctly [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Dmic should be on and volume set to 70% [Where problems could occur] Only fix for Dmic0 control and upstream already merged the code. The risk will be low [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/132 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992435/+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 1992435] [NEW] sof-hda-dsp Dmic0 not initial correctly
Public bug reported:
[Impact]
Device use sof-hda-dsp driver will not able to initial the Dmic0 status
correctly
[Test Plan]
1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
3. reboot system
4. Dmic should be on and volume set to 70%
[Where problems could occur]
Only fix for Dmic0 control and upstream already merged the code. The risk will
be low
[Other Info]
Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/132
** Affects: oem-priority
Importance: Undecided
Assignee: Dirk Su (dirksu)
Status: Confirmed
** Affects: alsa-ucm-conf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1992435
Title:
sof-hda-dsp Dmic0 not initial correctly
Status in OEM Priority Project:
Confirmed
Status in alsa-ucm-conf package in Ubuntu:
New
Bug description:
[Impact]
Device use sof-hda-dsp driver will not able to initial the Dmic0 status
correctly
[Test Plan]
1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
3. reboot system
4. Dmic should be on and volume set to 70%
[Where problems could occur]
Only fix for Dmic0 control and upstream already merged the code. The risk
will be low
[Other Info]
Pull Request in upstream
https://github.com/alsa-project/alsa-ucm-conf/pull/132
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1992435/+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 1981525] Re: Add support for Raptor Lake CPUs
Tested on DPLVR-MTE-EVT-C1 (202206-30359) which has Raptor Lake. Enable -proposed channel and install thermald 2.4.9-1ubuntu0.1 from it. Check with systemctl, thermald works correctly. ** Attachment added: "thermald.log" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981525/+attachment/5611134/+files/thermald.log ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy ** Changed in: oem-priority Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Fix Committed Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+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 1983235] Re: ADL: Support for new thermal table
** Changed in: oem-priority Assignee: (unassigned) => Dirk Su (dirksu) ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1983235 Title: ADL: Support for new thermal table Status in OEM Priority Project: New Status in thermald package in Ubuntu: Invalid Status in thermald source package in Jammy: In Progress Bug description: [Impact] * Support the new thermal table on ADL. [Test Plan] * Use a machine with a ADL. * systemctl stop thermald.service and run thermald with --adaptive. * Check the log of thermald and the adaptive works. [Where problems could occur] * Becuase RPL is still a engineering sample, there's no any thermal rule from acpi, Need to check with the formal machine in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1983235/+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 1983235] Re: ADL: Support for new thermal table
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1983235 Title: ADL: Support for new thermal table Status in OEM Priority Project: New Status in thermald package in Ubuntu: Invalid Status in thermald source package in Jammy: In Progress Bug description: [Impact] * Support the new thermal table on ADL. [Test Plan] * Use a machine with a ADL. * systemctl stop thermald.service and run thermald with --adaptive. * Check the log of thermald and the adaptive works. [Where problems could occur] * Becuase RPL is still a engineering sample, there's no any thermal rule from acpi, Need to check with the formal machine in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1983235/+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 1981525] Re: Add support for Raptor Lake CPUs
upload debdiff for jammy ** Patch added: "thermald_2.4.9-1ubuntu0.1.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1981525/+attachment/5602780/+files/thermald_2.4.9-1ubuntu0.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: In Progress Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+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 1981525] [NEW] Add support for Raptor Lake CPUs
Public bug reported: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 ** Affects: oem-priority Importance: Critical Assignee: Dirk Su (dirksu) Status: Confirmed ** Affects: thermald (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Dirk Su (dirksu) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: New Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+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 1962731] Re: No SYS%LPI residency in suspend when ethernet is connected
** Tags added: oem-priority originate-from-1954400 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected Status in OEM Priority Project: New Status in linux-signed-oem-5.14 package in Ubuntu: New Bug description: Try the command # turbostat -S --show Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m mem -s 15 ... Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 9.78 0.25 0.86 6.21 4.37 0.00 67.53 67.67 0.00 There is no SYS%LPI residency. Unplug ethernet, the residency become Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 8.63 0.13 0.07 22.56 1.24 0.00 53.95 54.08 53.82 The ethernet controller is I219-LM. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1024-oem 5.14.0-1024.26 ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem 5.14.21 Uname: Linux 5.14.0-1024-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 2 05:24:51 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+fossa-pidgeot+X92 InstallationDate: Installed on 2021-11-03 (118 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962731/+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 1957094] Re: on-demand mode doesn't work with nvidia-390
Setup impish on 201606-22344 in cert pool, this system's GPU can supported both with nvidia-driver-390 and nvidia-driver-470. Installed ubuntu-drivers-common, nvidia-settings from impish-proposed repository. With nvidia-driver-390, try to setup on-demand mode with "prime-select on-demand", system will fall back to nvidia mode after reboot. With nvidia-driver-470, setup on-demand mode with "prime-select on-demand", system will change to on-demand mode after system reboot. The behaviour of nvidia-drivers-common and nvidia-settings in impish-proposed is as expected. ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-settings source package in Impish: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1957094] Re: on-demand mode doesn't work with nvidia-390
Setup focal on 201606-22344 in cert pool, this system's GPU can supported both with nvidia-driver-390 and nvidia-driver-470. Installed ubuntu-drivers-common, nvidia-settings from focal-proposed repository. With nvidia-driver-390, try to setup on-demand mode with "prime-select on-demand", system will fall back to nvidia mode after reboot. With nvidia-driver-470, setup on-demand mode with "prime-select on-demand", system will change to on-demand mode after system reboot. The behaviour of nvidia-drivers-common and nvidia-settings in focal-proposed is as expected. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-settings source package in Impish: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1942181] Re: Add support for AlderLake CPUs
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1942181 Title: Add support for AlderLake CPUs Status in OEM Priority Project: Fix Released Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Hirsute: New Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on AlderLake CPUs. [Test Plan] * Use a machine with a AlderLake CPUs * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware because the changes match on the CPU model ID. [Other Info] Supported added with: * https://github.com/intel/thermal_daemon/commit/ffb226c62d3bc052f47970be9802254e48799bf4 * https://github.com/intel/thermal_daemon/commit/d0c9e7fb5aea85b84841eba927feb8767765fda2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942181/+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 1942181] Re: Add support for AlderLake CPUs
** Tags added: originate-from-1929780 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1942181 Title: Add support for AlderLake CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: Fix Committed Status in thermald source package in Hirsute: New Status in thermald source package in Impish: In Progress Bug description: [Impact] * Support thermald on AlderLake CPUs. [Test Plan] * Use a machine with a AlderLake CPUs * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware because the changes match on the CPU model ID. [Other Info] Supported added with: * https://github.com/intel/thermal_daemon/commit/ffb226c62d3bc052f47970be9802254e48799bf4 * https://github.com/intel/thermal_daemon/commit/d0c9e7fb5aea85b84841eba927feb8767765fda2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942181/+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 1942181] Re: Add support for AlderLake CPUs
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Dirk Su (dirksu) ** Tags added: originate-from-1922863 somerville ** Tags added: oem-priority ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1942181 Title: Add support for AlderLake CPUs Status in OEM Priority Project: New Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: Fix Committed Status in thermald source package in Hirsute: New Status in thermald source package in Impish: In Progress Bug description: [Impact] * Support thermald on AlderLake CPUs. [Test Plan] * Use a machine with a AlderLake CPUs * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware because the changes match on the CPU model ID. [Other Info] Supported added with: * https://github.com/intel/thermal_daemon/commit/ffb226c62d3bc052f47970be9802254e48799bf4 * https://github.com/intel/thermal_daemon/commit/d0c9e7fb5aea85b84841eba927feb8767765fda2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942181/+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 1942181] Re: Add support for AlderLake CPUs
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1942181 Title: Add support for AlderLake CPUs Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: Fix Committed Status in thermald source package in Hirsute: New Status in thermald source package in Impish: In Progress Bug description: [Impact] * Support thermald on AlderLake CPUs. [Test Plan] * Use a machine with a AlderLake CPUs * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware because the changes match on the CPU model ID. [Other Info] Supported added with: * https://github.com/intel/thermal_daemon/commit/ffb226c62d3bc052f47970be9802254e48799bf4 * https://github.com/intel/thermal_daemon/commit/d0c9e7fb5aea85b84841eba927feb8767765fda2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1942181/+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 1942181] Re: Add support for AlderLake CPUs
Install 1.9.1-1ubuntu0.6 on focal and test on AlderLake CPU. Below is the output from thermald ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2021-09-02 05:11:50 EDT; 31s ago Main PID: 989 (thermald) Tasks: 4 (limit: 18702) Memory: 4.2M CGroup: /system.slice/thermald.service └─989 /usr/sbin/thermald --systemd --dbus-enable --adaptive Sep 02 05:11:50 u-Latitude-9430 systemd[1]: Starting Thermal Daemon Service... Sep 02 05:11:50 u-Latitude-9430 systemd[1]: Started Thermal Daemon Service. Sep 02 05:11:50 u-Latitude-9430 thermald[989]: 32 CPUID levels; family:model:stepping 0x6:9a:1 (6:154:1) Sep 02 05:11:50 u-Latitude-9430 thermald[989]: 32 CPUID levels; family:model:stepping 0x6:9a:1 (6:154:1) Sep 02 05:11:50 u-Latitude-9430 thermald[989]: Polling mode is enabled: 4 Sep 02 05:11:50 u-Latitude-9430 thermald[989]: sensor id 12 : No temp sysfs for reading raw temp Sep 02 05:11:50 u-Latitude-9430 thermald[989]: sensor id 12 : No temp sysfs for reading raw temp Sep 02 05:11:50 u-Latitude-9430 thermald[989]: sensor id 12 : No temp sysfs for reading raw temp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1942181 Title: Add support for AlderLake CPUs Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: Fix Committed Status in thermald source package in Hirsute: New Status in thermald source package in Impish: In Progress Bug description: [Impact] * Support thermald on AlderLake CPUs. [Test Plan] * Use a machine with a AlderLake CPUs * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware because the changes match on the CPU model ID. [Other Info] Supported added with: * https://github.com/intel/thermal_daemon/commit/ffb226c62d3bc052f47970be9802254e48799bf4 * https://github.com/intel/thermal_daemon/commit/d0c9e7fb5aea85b84841eba927feb8767765fda2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1942181/+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
