@Kai-Chuan Hsieh I have downloaded libpciaccess 0.17-3ubuntu0.24.04.3~oem1 shared by you and tested on my system. I can confirm, that the regression https://bugs.launchpad.net/bugs/2115574 which I have observed when trying 0.17-3ubuntu0.24.04.1 is not seen on my system with the new version you shared. Some details of my system you can find at https://bugs.launchpad.net/bugs/2115605.
Package tested: libpciaccess0_0.17-3ubuntu0.24.04.3~oem1_amd64.deb Testing performed: Rebooting the system after installing the package Result: System behaves correctly Please note I have only tested the package for the regression https://bugs.launchpad.net/bugs/2115574. I am not impacted by https://bugs.launchpad.net/bugs/2111684 that you work on here, so I cannot comment whether the package you shared fixes the issue you are trying to fix. The only difference in behaviour I have observed between the libpciaccess0_0.17-3build1_amd64.deb which I was using originally and 0.17-3ubuntu0.24.04.3~oem1 is that with the older package in the syslog I can see the following messages during boot (few times during entire boot process): kernel: nouveau 0000:01:00.0: bus: MMIO write of 00870fb0 FAULT at 100c10 [ PRIVRING ] while with the new package you shared the log says: kernel: nouveau 0000:01:00.0: bus: MMIO write of 008699b0 FAULT at 100c10 [ PRIVRING ] i.e. instead of writing 00870fb0 the write (which fails) is now of 008699b0. I cannot see any functional impact of the old log and I cannot see any impact from the new log either, providing this information here just in case it may be useful in any way. PS Just a friendly advice - I was not subscribed to this bug and only noticed your message because you posted it first on 2115574, but that message is now deleted. In future in such situations you may prefer to contact people with direct message or ask them in the bug you've seen them to look into some other bug (not sure what is considered more proper on launchpad). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/2111684 Title: [SRU] Xorg AMD platform A + N config selected wrong primary GPU Status in OEM Priority Project: New Status in libpciaccess package in Ubuntu: Fix Released Status in libpciaccess source package in Noble: Triaged Status in libpciaccess source package in Oracular: Won't Fix Status in libpciaccess source package in Plucky: Triaged Status in libpciaccess source package in Questing: Fix Released Bug description: [ Impact ] * On AMD platform with Nvidia dGPU, if the iGPU is not VGA compatible. and pci order is later than NV * The system will select Nvidia as the primary GPU, which is wrong on AMD platform. [ Test Plan ] * On AMD (StrixPoint or KrakanPoint) platform with Nvidia dGPU * Check the renderer by $ xrandr -display <display name> --listproviders * Provider 0 should be AMD graphic [ Where problems could occur ] * If Nvidia dGPU is VGA compatible and the boot_vga is set, the system still select Nvidia as the primary GPU. * If the platform AMD graphic card acpi companion is not configured in the BIOS, the system still select Nvidia as the primary GPU. [ Other Info ] * Upstream MP: https://gitlab.freedesktop.org/xorg/lib/libpciaccess/-/merge_requests/37 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2111684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
