HP Victus Gaming Laptop 15-fb2082wm (A14MNUA)

Hardware: AMD Ryzen 5 8645HS Nvidia GTX4050 Realtek RTL8852BE 
BIOS: version F.07

Tested configuration:

Do not use an image writer like Ventoy (broken stage2 discovery). Use something else like Rufus or Fedora Media Writer which worked in my case.

Now that only leaves the hybrid GPU issues (display quirks under Xen: black screens, forced reboots etc…)

In GRUB, press the E key to add these boot parameters:

rd.driver.blacklist=nouveau nouveau.modeset=0 xdriver=amdgpu

Then press the Ctrl + X keyboard shortcut. After successful installation, make it permanent.

This only works for the stable official kernel and for some reason fails to load xsession/installer for the latest kernel.

Hope this could prove useful to other.

Additional info:
Hardware Overview*

  • Brand/Model: HP Victus 15 fb2082wm
  • CPU: AMD Ryzen 5 8645HS (6 cores / 12 threads, family 25, model 117, stepping 1) with integrated Radeon 760M Graphics
  • GPU:
    • Integrated: AMD Radeon 760M (Hawk Point, PCI 1002:1900, driver: amdgpu) → Used for dom0
    • Discrete: NVIDIA GeForce RTX 4050 Max-Q / Mobile (PCI 10de:28a1, rev a1, driver: nouveau loaded) → Available for PCI passthrough to VMs
  • Chipset: AMD Phoenix (Phoenix Data Fabric / Root Complex)
  • WiFi: Realtek RTL8852BE PCIe 802.11ax Wireless Network Controller
  • Ethernet: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
  • Storage: Sandisk SN5x NVMe SSD (driver: nvme)
  • Audio: Multiple (AMD Rembrandt/Strix HD Audio + Intel HDA + NVIDIA HDMI Audio)
  • Memory: 16GB
  • BIOS: F.07

Qubes OS Version & Installation

  • Qubes OS R4.3
  • Kernel in dom0: 6.12.59-1.qubes.fc41.x86_64
  • Xen version: 4.19.3 (xen-3.0-x86_64)
  • Installation notes:
    • Used Rufus/Fedora Media Writer to create bootable USB (Ventoy caused stage2 discovery timeouts / Anaconda aborts).
    • Custom boot parameters helped bypass early amdgpu init/power/ring failures and Anaconda memory pressure issues.
    • iGPU (amdgpu) works for dom0 after tweaks; NVIDIA dGPU hidden from dom0 and suitable for passthrough.

Virtualization Support

  • HVM: Yes (full support shown in xl info)
  • IOMMU (AMD-Vi): Yes – Fully enabled
    • “IOMMU 0 Enabled.”
    • Extended features present
    • Default domain type: Translated, lazy mode
    • DMA TLB invalidation policy: lazy mode
  • SLAT/EPT/RVI: Yes

Remarks
Suspend/resume and battery work perfectly fine.

4 Likes

It would be great if you could make a HCL report out of this:

1 Like

Is this using S3 or s0ix (s2idle) suspend? (this is present in /sys/power/mem_sleep)

(If s0ix) Did you have to apply any s0ix workarounds or did it work out of the box?

I also have a recent AMD laptop and it seems like it can never reach full deep s0ix suspend (hot laptop in the backpack).

1 Like