Ahm, i'm not sure what orientation the actual deck's display is. i never ran anything but steamos when i had it
VIt's a vertical display rotated in software
Vso i wanted to install bazzite on my desktop but when i try to boot from my usb (made with fedora media writer) it gives an error saying "image unsupported" and boots right back to windows
Aanyone see really slow network transfer speeds? everything says i'm connecting at 1Gbps+ wifi-wise, but i'm getting transfer speeds around 1Mbps, even to the lan (i'm on a lenovo legion go)
KNope, should be normal for you at least once everything is configured. Possible it's DeckHD related
VThat's what I was thinking
KCan always use a stock sb/Kinoite installer and then rebase
Hgo into the USB root and navigate to
that should fix the
EFI/fedora/grubx64.efiEFI/BOOT/grubx64.efiBOOTX64.EFIthat should fix the
image not supported@KyleGospo ^ thats also some workaround for you to add to your list of tricks too, as if they get that error, stock atomic fedora might also get the same issue
Ainteresting, it's working fine now. no reboot or anything. of note, this was behaving this way for all net traffic from my device, even from my server on my lan it was crawling. attended a work meeting and now i'm seeing 0.5Gbps. 
VIt was something stupid to fix tbh i just used legacy boot for the usb and it booted immediatly
Hyeah but from experience some installers will install the system in the mode the system was booted from
legacy --> bios/mbr install
uefi --> uefi install
legacy --> bios/mbr install
uefi --> uefi install
Hand lets not forget some laptops have legacy mode completely ripped out now
VI wanted to install efi mode but i couldn't for the life of it enter that efi partition on my usb
EDesktop images (sans NVIDIA, probably needs a rebuild) are updated. Deck images are not atm. Will take a closer look in about half an hour
E@KyleGospo removing kmods from an image might not be possible. We'd need something like cliwrap install-to-root but for removals (maybe it works both ways?)
KThat's fine, we can pull that out. I need to adjust which ones are installed against fsync anyway
ESounds good
Vwaydroid service nnot working
KDid you turn off SE linux?
Vset to permissive and rebooted
Vnvm it didnt change
BI want to say no. It's not something I've come across in use, or seen in a feature list.
VHow can I change the Res of waydroid/Weston?
K/etc/default
KThere's a Waydroid launcher file in thrre
KWhich holds the resolution
KAmong other things
VCool thanks :)
VWaydroid just needs a command iirc
KIt's because we also have to change the resolution of the wrapping Weston
KSo this handles that
KBetter than it being hard coded
KOr guessed from the current display config
VYeah I know, works fine tho.
VMaybe put that on the docs @nickname
VThat file already exists in the efi folder, the fedora folder however does not exist
IWhen I installed bazzite, my ntfs drives were populated automatically. In trying to fix something else, I removed the default mount point for one and set it as something else. Now I am having trouble figuring out where the initial mounting configuration is stored so I can/how to revert it to that. Where should I start looking?
KDE Partition Manager works with /etc/fstab, which doesn't seem to have anything for the initally configured drive.
Edit: Anyone finding this, if you're dealing with an ntfs volume with a windows installation, it will mount read-only if windows is hibernated. Shut down fully with Shutdown in windows.
Also, remove the line from /etc/fstab and mount with sudo mount path|guid mountpoint
KDE Partition Manager works with /etc/fstab, which doesn't seem to have anything for the initally configured drive.
Edit: Anyone finding this, if you're dealing with an ntfs volume with a windows installation, it will mount read-only if windows is hibernated. Shut down fully with Shutdown in windows.
Also, remove the line from /etc/fstab and mount with sudo mount path|guid mountpoint
Dhey I noticed that there has been some successful builds and some not successful, what would make some succede and others not
VUsually some components will fail
VThat's why broken images usually come in groups
Ve.g. all deck builds will fail
VAll nvidia builds
Vetc. etc.
VFor example, most recently the Deck and Nvidia images failed
VExcept for asus-deck apparently, probably a quirk of that image
DI've noticed this in the log of bazzite-deck:kinoite
DVWhich I'm assuming is how it know it failed?
VBut again, as said in the past
