This bug is awaiting verification that the linux-oem-6.14/6.14.0-1014.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-oem-6.14' to 'verification-done- noble-linux-oem-6.14'. If the problem still exists, change the tag 'verification-needed-noble-linux-oem-6.14' to 'verification-failed- noble-linux-oem-6.14'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-oem-6.14-v2 verification-needed-noble-linux-oem-6.14 -- 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/2124232 Title: Adjust fbcon console device detection for Dual GPU platform Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.14 package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem-6.14 source package in Noble: Fix Committed Status in linux source package in Plucky: New Status in linux-oem-6.14 source package in Plucky: New Bug description: [SRU Justification] [Impact] Some AMD platforms with additional NVIDIA GPU consume too much power than expected. For this kind of platforms with 2 GPUs that are not VGA devices, decided not to overload the VGA arbiter for non VGA devices. [Fix] Backport upstream patchset of https://lore.kernel.org/linux-pci/[email protected]/T/#m53c998f4946ae7eb99d2cbc329a968a0ed0daba0 . [Test Case] 1. Boot up the machines with 2 GPUs, like AMD platform GR-D(A+N) 2. Open Nvidia setting GUI, there is no “PRIME Profiles” option, and default use nvidia to render when check with command “#glxinfo -B“, even “prime-select query“ output in “on-demand“. 3. Monitor runtime status of NVIDIA by `cat /sys/bus/pci/devices/0000:xx:00.0/power/runtime_status` and make sure it's not always active. [Where problems could occur] Only work with user space utility for adjusting the boot_display attribute in sysfs. No regression expected at the current stage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2124232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
