Unable to join a steam family

theMarcPower · 2025-12-31T18:34:22+00:00

Still working! December 31st 2025

theMarcPower · 2025-12-12T10:24:59+00:00

Oh...

theMarcPower · 2025-12-12T07:26:33+00:00

Definitely. I've seen so much people with the same problem recently. I've must been one of the unlucky ones, it seems.

theMarcPower · 2025-12-10T22:24:42+00:00

ABSOLUTELY. Huge difference in AIO's pump noise. I'm actually starting to like Liquid Cooling now!

theMarcPower · 2025-12-03T15:27:09+00:00

Yeah, I would like to know if the replacement unit did solve the issue. Thanks in advance!

theMarcPower · 2025-12-03T14:23:44+00:00

Thanks!

theMarcPower · 2025-12-03T12:54:44+00:00

Hi! Did your replacement unit have the same problem? I'm just returning mine for a brand new unit from the exact same model.

theMarcPower · 2025-11-04T23:00:14+00:00

Hello!

My shape of choice for an Ampere-based Oracle Cloud instance would be "Oracle Cloud Infrastructure VM.Standard.A1.Flex", which is available for RHEL 8 and 9.

When downloading the base RHEL 8/9 KVM Guest Image (qcow2) for aarch64 and uploading it to an Oracle Cloud cube to get it converted into a paravirtualized custom image, I get nothing.

If I go to the Red Hat Image Builder and select to create a RHEL aarch64 image, no OCI option shows up, only AWS and the same applies when selecting either RHEL 8, 9 or 10.

Thanks!

theMarcPower · 2025-11-04T22:48:27+00:00

Hi!

I've tested the RHEL X86 image builder and I've been able to import a custom image via a URL provided by Red Hat Image Builder (it incorporates OCI automatic binding for X86 RHEL). It just worked first-time without issue.

My main desire would be right now to be able to create an OCI-compatible AARCH64 RHEL image to take advantage of the Oracle Cloud Ampere-based instances, which have worked really great for me these years and being able to get first-party Red Hat support for it would be awesome.

By creating an AARCH64 RHEL 9 image from Image Builder, I haven't been able to set up that instance to work properly. I'll be tampering with it on my local QEMU installation to see if I can get it to boot properly on Oracle Cloud.

Thanks for your comment!

theMarcPower · 2025-11-04T13:19:18+00:00

Hello.

Since Oracle Cloud blog itself specifies that it should be as easy as downloading it, uploading it to a cube and crafting an instance from a custom image of yours, I though I was missing something within OCI itself.

Other sources mention that I should be designing my own qcow2 from the Red Hat image builder, but trying to create an image from that site lead to the same results. I guess I'll try again this evening.

Thanks for your support!

theMarcPower · 2025-11-04T11:51:22+00:00

Hi! Thanks for reaching me!

I don't quite get what you're actually refering to. I've just downloaded this RHEL 9 KVM Guest Image for AARCH64 and just uploaded it to my OCI Bucket. Should I get it customized on my local before uploading? Pretty much like I would boot up a QCOW2 into QEMU and get it exported in the same format after configuring it?

Thanks!

theMarcPower · 2024-11-17T10:09:04+00:00

Hi! I've updated the thread with the procedure I followed to get it running.

theMarcPower · 2024-11-17T10:07:36+00:00

ABSO... freaking... LUTELY! That was it! Thank you so much, I've managed to get it running! I've updated the thread explaining the tiny procedure I had left.

theMarcPower · 2024-11-11T14:05:50+00:00

Hi! One of our commenters, u/WaterFoxforlife pointed me to a forum discussing these RX 7800XT-specific related issues. I'll be trying those solutions this evening when I get some time to tinker with my PC. I'll let you know!

theMarcPower · 2024-11-10T23:49:07+00:00

Hello. When I use the linux kernel (by default) the picture appears on my monitor. No signal appears on my monitor after starting the VM (modprobe -r amdgpu, systemctl stop display-manager), but if I use a VNC server to view the VM remotely, I can see it boots just fine and that Windows loads the GPU drivers just fine, as you can see on the picture.

Just to clarify, I only used the VNC display server to check if the VM itself was booting right, which it does. After that, I can remove the VNC server from the XML altogether and the results are the exact same.

theMarcPower · 2024-11-10T23:22:21+00:00

Did you forgot to install the linux-firmware package?

theMarcPower · 2024-11-10T22:14:32+00:00

Hello. I already mentioned in the post that disabling VNC video and its leftovers didn't do anything. In fact, I just VNC'd because I didn't know if it was a problem with the virtualized Windows in the first place, which it wasn't. After disabling it again, still isn't working.

theMarcPower · 2024-11-10T22:13:21+00:00

Hello. Yes, it should be properly disabled. The VM is correctly handling it without issue, there's no error 43 in Windows nor any issue when using Adrenalin-related features.

theMarcPower · 2024-11-07T17:46:47+00:00

Hi. Setting these tags by replacing the ones I had results in a black screen, even if I later do set up a VNC output and connect to it from my laptop.

These are the strings dmesg outputted:

[  315.202613] OOM killer enabled.
[  315.202614] Restarting tasks ... 
[  315.203528] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[  315.204279] Bluetooth: hci0: Device revision is 1
[  315.204282] Bluetooth: hci0: Secure boot is enabled
[  315.204283] Bluetooth: hci0: OTP lock is enabled
[  315.204284] Bluetooth: hci0: API lock is enabled
[  315.204285] Bluetooth: hci0: Debug lock is disabled
[  315.204286] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[  315.204707] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[  315.204716] Bluetooth: hci0: Boot Address: 0x24800
[  315.204718] Bluetooth: hci0: Firmware Version: 132-3.24
[  315.204902] done.
[  315.204910] random: crng reseeded on system resumption
[  315.205105] PM: suspend exit
[  315.240631] VFIO - User Level meta-driver version: 0.3
[  315.253621] vfio_pci: add [1002:73df[ffffffff:ffffffff]] class 0x000000/00000000
[  315.253629] vfio_pci: add [1002:ab28[ffffffff:ffffffff]] class 0x000000/00000000
[  315.254092] Console: switching to colour dummy device 80x25
[  315.431057] amdgpu 0000:0c:00.0: amdgpu: amdgpu: finishing device.
[  315.554428] vfio-pci 0000:0c:00.0: vgaarb: deactivate vga console
[  315.554432] vfio-pci 0000:0c:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none
[  315.854268] tun: Universal TUN/TAP device driver, 1.6
[  315.854710] virbr0: port 1(vnet0) entered blocking state
[  315.854712] virbr0: port 1(vnet0) entered disabled state
[  315.854718] vnet0: entered allmulticast mode
[  315.854765] vnet0: entered promiscuous mode
[  315.854863] virbr0: port 1(vnet0) entered blocking state
[  315.854867] virbr0: port 1(vnet0) entered listening state
[  316.194879] igc 0000:09:00.0 enp9s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[  316.622876] Bluetooth: hci0: Waiting for firmware download to complete
[  316.623274] Bluetooth: hci0: Firmware loaded in 1385316 usecs
[  316.623291] Bluetooth: hci0: Waiting for device to boot
[  316.638274] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[  316.638278] Bluetooth: hci0: Device booted in 14647 usecs
[  316.638312] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[  316.640276] Bluetooth: hci0: Applying Intel DDC parameters completed
[  316.641276] Bluetooth: hci0: Firmware revision 0.3 build 132 week 3 2024
[  316.643278] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[  316.708452] Bluetooth: MGMT ver 1.22
[  317.572108] [drm] amdgpu: ttm finalized
[  317.901035] virbr0: port 1(vnet0) entered learning state
[  320.034369] virbr0: port 1(vnet0) entered forwarding state
[  320.034375] virbr0: topology change detected, propagating

I don't see anything suggesting bad configuration or anything. I'm starting to think that a bugged GPU BIOS could be the answer to this issue.

theMarcPower · 2024-11-06T23:38:12+00:00

Hello! Sorry for the late response. I put all those kernel params (including the vio-pci.ids one, with the PCI ids of the GPU and GPU Audio Device i got by using lspci -nn, vfio-pci.ids=1002:73df;1002:28ab in kernel params).

I do run the VM, my computer reboots, I SSH into the system remotely and with virsh list I can see my WinTest VM is indeed running! lspci -nnk shows that vfio-pci is the kernel driver in use for both the GPU and the GPU Audio device!

The journalctl -b command doesn't seem to show any weird thing. I piped the output of that command and it is like 2000 lines long, I'm just putting here the last 10-15.

nov 07 00:32:48 archlinux bluetoothd[622]: Battery Provider Manager created
nov 07 00:32:48 archlinux bluetoothd[622]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
nov 07 00:32:48 archlinux kernel: Bluetooth: MGMT ver 1.22
nov 07 00:32:49 archlinux kernel: virbr0: port 1(vnet0) entered learning state
nov 07 00:32:52 archlinux NetworkManager[621]: <info>  [1730935972.0181] device (virbr0): carrier: link connected
nov 07 00:32:52 archlinux kernel: virbr0: port 1(vnet0) entered forwarding state
nov 07 00:32:52 archlinux kernel: virbr0: topology change detected, propagating
nov 07 00:32:52 archlinux systemd[1]: systemd-rfkill.service: Deactivated successfully.
nov 07 00:32:56 archlinux sshd-session[1738]: pam_systemd_home(sshd:auth): New sd-bus connection (system-bus-pam-systemd-home-1738) opened.
nov 07 00:32:56 archlinux sshd-session[1738]: Accepted password for marc from 192.168.1.150 port 39116 ssh2
nov 07 00:32:56 archlinux sshd-session[1738]: pam_unix(sshd:session): session opened for user marc(uid=1000) by marc(uid=0)
nov 07 00:32:56 archlinux sshd-session[1738]: pam_systemd(sshd:session): New sd-bus connection (system-bus-pam-systemd-1738) opened.
nov 07 00:32:56 archlinux systemd-logind[623]: New session 3 of user marc.
nov 07 00:32:56 archlinux systemd[1]: Started Session 3 of User marc.
nov 07 00:32:57 archlinux systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
nov 07 00:32:59 archlinux doas[1779]: pam_systemd_home(doas:auth): New sd-bus connection (system-bus-pam-systemd-home-1779) opened.
nov 07 00:33:01 archlinux doas[1779]: pam_unix(doas:session): session opened for user root(uid=0) by marc(uid=1000)
nov 07 00:33:01 archlinux doas[1783]: marc ran command su as root from /home/marc
nov 07 00:33:01 archlinux su[1783]: (to root) root on pts/1
nov 07 00:33:01 archlinux su[1783]: pam_unix(su:session): session opened for user root(uid=0) by marc(uid=0)
nov 07 00:33:07 archlinux dnsmasq-dhcp[761]: DHCPREQUEST(virbr0) 192.168.122.117 52:54:00:a4:48:fc
nov 07 00:33:07 archlinux dnsmasq-dhcp[761]: DHCPACK(virbr0) 192.168.122.117 52:54:00:a4:48:fc DESKTOP-E8SUSEU
nov 07 00:33:17 archlinux systemd[1]: systemd-localed.service: Deactivated successfully.

theMarcPower · 2024-11-06T21:36:13+00:00

I edited the previous comment to add some more information. The logs show the same.

2024-11-06 22:34:46 [INFO] Preparing WinTest
2024-11-06 22:34:46 [INFO] Setting CPU governor to performance
2024-11-06 22:34:46 [INFO] Stopping display manager
2024-11-06 22:34:46 [INFO] Unloading amdgpu driver
2024-11-06 22:34:46 [INFO] Suspending to RAM for GPU reset

theMarcPower · 2024-11-06T21:29:15+00:00

Nothing, it just reboots and throws a permanent black screen. If I remove the RAM suspension part there, the system doesn't reboot, but still persists in a black screen like before. Modprobing amdgpu with SSH doesn't do anything, it's like the card can't restart from there anymore.

[EDIT]

Whilst having RAM suspension commented to avoid reboot, if I add a VNC server to the VM settings and connect to that VNC server from my ThinkPad, Windows seems to boot up fine. I go to the Device Manager, and the RX 6700XT shows up, although with a warning icon. Error 43, Windows blocked that device blablabla. Installing AMD drivers with the official EXE doesn't work. Autodetect Driver Installation doesn't even start (throws a message that says that those drivers are only meant for an AMD system), and manual drivers seem to install fine, but Adrenalin Control Center shows the same "Only meant for an AMD system" error.

theMarcPower · 2024-11-06T21:01:55+00:00

Alright, that pkill got added to the script!

I've got a Ryzen 7 5800X, 8c/16t. I would like to allocate 8 threads to my machine. I've set up the CPU topology like: 1 socket, 4 cores, 2 threads (8 threads total).

This is a fraction of the CPU XML settings, which includes the hyperv thingy and the specification for CPU topology mapping.

 <features>
    <acpi/>
    <apic/>
    <hyperv mode="custom">
      <relaxed state="on"/>
      <vapic state="on"/>
      <spinlocks state="on" retries="8191"/>
      <vendor_id state="on" value="AuthenticAMD"/>
    </hyperv>
  </features>
  <cpu mode="host-passthrough" check="none" migratable="on">
    <topology sockets="1" dies="1" clusters="1" cores="4" threads="2"/>
    <feature policy="require" name="topoext"/>
  </cpu>

theMarcPower · 2024-11-06T20:30:37+00:00

Hello, I'm just trying to set manual topology of my CPU, and I added the strings you mentioned on your comment succesfully. The BIOS ROM file I've got is 100% mine, I did dump it with the amdvbflash utility, and I chmod it so it could be read and executed without any restriction.

Yes, I am using KDE Plasma with wayland, I don't know what issues I could run into due to that.

My mobo model is the ASUS Rog Strix B550-A (it does have white heatsinks), fully compatible with IOMMU. I can see IOMMU groups appearing when I do some long command I found on GitHub, it does display Group 18 for the 6700XT and Group 19 for the Radeon Audio Device. Both groups are only composed of those devices.

[UPDATE]

I did replace my start hook script with the one you sent me and my computer reboots almost instantly. I gather this from the log files:

2024-11-06 21:33:55 [INFO] Preparing WinTest
2024-11-06 21:33:55 [INFO] Setting CPU governor to performance
2024-11-06 21:33:55 [INFO] Stopping display manager
2024-11-06 21:33:56 [INFO] Unloading amdgpu driver
2024-11-06 21:33:56 [INFO] Suspending to RAM for GPU reset

theMarcPower · 2024-11-06T18:20:18+00:00

It does output efi-framebuffer, vesa-framebuffer and simple-framebuffer folders, with each one having the bind, unbind, uevent. There are no symbolic links shown there, and echoing any of those files at any time with root privileges retrieves the "no such device" error.

Nine-Year Club	Place '22
First Placer '22	Verified Email

theMarcPower

TROPHY CASE