Do I need to reinstall?
Hthanks, can we have logs with that?
I mean I can update the steam side of it
sec
Kthere's no such thing
H
Kgamemode and the desktop call the same updater
Klogs please
ty
R6.1.2 updated the breeze cursor so its no longer pixelated iirc
JThank you so much!
Jthinking of trying bazzite, if i dont partion my current ssd would an installation wipe it
PSo I decided I should get my Ally X replaced for free by Best Buy while I still can, because of this graphics bug. Happens every time I switch from Desktop to Gaming Mode, won't go away without sleeping/awakening the device, and I figure if it's a hardware issue it will only get worse over time.
Question - is there any problem just popping my 4TB SSD from this Ally X into the replacement device? Or should I start all over?
Question - is there any problem just popping my 4TB SSD from this Ally X into the replacement device? Or should I start all over?
MI’m not saying it’s impossible but that sounds more like software than a hardware issue to me
Meither in Gamescope or in the kernel driver
DIs it expected that bazzite on the ally x shows Ram size as 13.34?
ALower your vram in bios to 1gb
Kthen it'll show iirc 14.9
Kwhich is correct
Ksome amount of your RAM is VRAM at all times
ADon't you have like 30 days? Keep it for a few more days
ASound like software
Heveryone else answered everything else but yes you can move the ssd from 1 ally x to the other without issues
PI did a driver update via dnf update and mesa-dri drivers but still problem persists. It is intermittent, it will not bug out on every switch. What else can I try?
Kdnf isn't a thing here, we're atomic fedora
Krpm-ostree update updates the system, and we're currently running the same version of Mesa we've had for the last 2 weeks
PBest Buy says I have until 8/8. I’m going on a road trip starting 8/4 so really I’ve got another week tops
K@antheas has any other Ally X user reported these issues?
PIf it makes a difference I am using Bazzite in a dual boot setup. Not sure if this is related but the windows OS is constant BSOD right now and I’m waiting to get a 2nd usb drive to make a recovery drive for it
Kdid it BSOD before you dual booted?
Hdid you verify the sha256 of the iso? it should boot unless the iso is corrupt
PNo. Windows was fine but I only booted into windows like 2x before partitioning and installing bazzite. I decided to try booting to windows partition only after I started noticing the graphics bug. So I’ve never been able to boot to windows since installing bazzite
Keverything about your setup is sus
KI would start with reimaging and if you can still reproduce these issues, return it
Ksince you're the only one reporting them
Hof the ventoy iso? no I used the binary/tar.gz version
PI followed the dual boot guide on discourse and Aru’s YouTube video. By re-imaging do you mean reformat the drive, install windows again, then partition again and install bazzite?
KThe error you're getting in windows is a fundemental failure too, ACPI_BIOS_ERROR isn't something you can cause w/ partition or file changes
Hof the bazzite iso
Hventoy is working for you but the iso is not booting properly
Hwhere do I even find how to do that?
Him not seeing anything about a sha256 for bazzite
PThis is a 4TB Samsung 990 that I did cloud recovery on after swapping out the stock ssd. I did not run into any problems during install other than a) first having to turn off bitlocker and b) Bazzite did not boot due to secure boot being turned on in bios. After I turned off secure boot Bazzite loaded normally for the first time.
H
Hgives you a CHECKSUM file with the sha256 hash
PI guess I can repeat the process but not sure what difference it would make if I do the exact same thing again
