`Windows has stopped this device because it has reported problems (COde 43)`
Windows has stopped this device because it has reported problems (COde 43)
MOk well AMD Radeon(TM) graphics is showing up in device manager
Mbut
Hyou need to mask the VM (this is not the same as hiding the that its running on a VM) by supplying a vendor id
DSo I am guessing the 555 driver will make wayland way better on nvidia
Hyep no more flickering for starters
M?
Mhmmmm
SIs the timeline fixed? I had to stay on 18.1.4 or else the timeline just didn't show up
Hhttps://wiki.archlinux.org/title/PCI_passthrough_via_OVMF#Video_card_driver_virtualisation_detection
funny how the arch wiki has good documentation for a lot of stuff
funny how the arch wiki has good documentation for a lot of stuff
DI mainly went nvidia for vr
DBut after the announcement that windows will be recording your activities it made me want to duel boot and only use windows for vr
Hanyways i g2g
Mthat didn't change anything
DI am prob gonna wait until the 555 driver is stable and bazzite includes it
RIf you want to test it now, I recommend doing so in a clean fedora image rather than ublue
RAs ublue ships their own modifications, changing the driver could break updates
DNah just gonna wait till it is stable
DI don't like using beta drivers
RI usually don't either
RIt's just that I was so tired of waiting I couldn't help myself
R
RBut it's definitely wiser to wait for the stable version
I don't have much issues with the beta, but I also want a stable release so I can go back to ublue
I don't have much issues with the beta, but I also want a stable release so I can go back to ublue
HThanks. glad it is possible
HOk, having a major issue now. "The following error occurred while installing the payload. this is a fatal error and installation will be aborted. the command
ostree container image deploy --sysroot=/mnt/sysimage --image=/run/install/repo/bazzite-nvidia-stable --transport=oci --no-signature-verification exited with code 1Hthis happened after i wiped the previous installs partition through windows, and began a new install.
Mit saved me just the other day so I could get videos edited on davinci
Mtold me what I need to check for in the video and the command to use depending on that
Mthen I had a compatible video with davinci on linux
Pthis vfio stuff is a solved problem nowadays
Parch wiki would be pretty much what you need, ya
HWhat if i told you that you can find good gpu passthrough vm config settings in the vrchat wiki 
MLOL
Mbut nowhere else
Mjust in vrchat wiki
Mhaha
Pjust keep in mind that these are all hacky workarounds and you're probably trading one piece of nonworking software for another
Ponce you have things running stable and figure out a good config there's really not a lot of software that actually gives a shit tbh
Pand stuff that does try really hard to detect VMs is always going to be a bit fucky and you're better off keeping ur distance from them
AStuck in ostree hell
Pif you wipe the entire drive you're at ground zero and this shouldn't be an issue again
AFollow the dual boot guide and make the partitions by jand
AThen cross your fingers
RWhat's the reasoning behind removal of auto-power-profile GNOME extension from shipped ones? Just curious, since I thought it to be beneficial on laptops. Was it faulty?
HI might not dual boot at all.. if vga passthrough is working, i will just VM a windows for when i need to do Unity project builds
ANuke the drive then
Pwhat sort of hardware are you on?
HYup but we do not talk about the exact content of the vrchat wiki just that it has configs that might be useful 
Hme or Raltay?
Pyou
