resolution for ally is 1080p right?
resolution for ally is 1080p right?
Hyep and landscape
Tok good
Tscaling shouldnt be an issue then
Twith anaconda
VTbh the fact scaling is bad at 800p landscape is kind of unacceptable on annaconda's part
VThat's not a crazy resolution
Jthe new installer will fix that
Hprobably crazy that someone would use 800p in 2020+ when it was made /s
im just happy we are getting a new installer soon
im just happy we are getting a new installer soon
VYeah I know... Still mad at them for making a bad installer
JI know haha
Jit's so bad
Jbut soon the pain will be over
VDoesn't effect my 1200p DeckHD screen, still feel bad for all of you poor people /s
RIs there any place where Gnome session/extension logs are stored? Quick look over Internet indicates that it should be .cache/gdm/session.log, but that file is absent.
Xsystemd journal
Jthanks for the suggestion
Jit appears to be working
Jso far its almost done with the installer
Jits "writing objects"
J@nickname I got the exact same error
Jwith an offline installer..
Jwth is going on?!?
J"The following error occurred while installing the payload. this is a fatal error and installation will be aborted"
The command 'ostree admin --sysroot=mnt/sysimage deploy --os=fedora fedora:fedora/39/x86_64/silverblue' exited witht the code 1
The command 'ostree admin --sysroot=mnt/sysimage deploy --os=fedora fedora:fedora/39/x86_64/silverblue' exited witht the code 1
JI'm clueless on what to do now, I'm just gonna cloud recover my rog ally and restart this entire process
Hhow are you setting up the partitions? ostree has some very strict requirements for how things are partitioned, or did you auto?
JI did automatic with 64gb of unallocated space for it to install to
Jthat should work right?
JI have bitlocker, secure boot, fast boot etc turned off
Hit should 
, i am not very familiar with all the quirks with the installs
, i am not very familiar with all the quirks with the installsJmaybe its an issue with a previous nobara installation I had before this...
Hah bitlocker might be problematic if the EFI partition is encrypted. never used bitlocker so i have no idea if it does that
JI just deleted the nobara paritions and tried installing to that
Jbitlocker is off
Jso it shouldn't do anything here
Jand nobara worked earlier this same day
Hoh i misread it my bad
Jits probably an issue caused by nobara being installed earlier
JI'll just cloud recover and start over
Him sorry i cant be of more help, havent been around long enough to know all the ins and out of the installer, other than its easier to install silverblue/kinoite and rebase if you have any issues.
no idea what causes your issue though since silverblue also fails
no idea what causes your issue though since silverblue also fails
MI’ve gone straight from nobara to Bazzite several times without issue so I doubt it’s that specifically. Are you using WiFi during setup and install or a USB-C dock with Ethernet attached? I’d highly recommend Ethernet just to rule out :latest network driver issues.
Jan issue in the efi parition?
JI've tried using an offline installer
Jand it still fails
JI uninstalled nobara improperly
Mhow did you flash the disk you used for installation? Also - have you tried seeing what happens if you reboot your Ally after it got most of the way through install and failed here 🎮bazzite
Mit’s not directly comparable, but there was a chimera issue in the past that would show a similar installation failed message after the entire process completed successfully, which you couldn’t know unless you rebooted without the install disk plugged in after it failed out at the end.
Jyou might be right.....
Jit showed a fedora installation in bios after everytime it failed
JI'm already pretty far into the cloud recovery process
Tthis is kind of what i meant by 🎮bazzite
