But if I can get it working on bazzite that means I can switch away from fedora nobara since right n
But if I can get it working on bazzite that means I can switch away from fedora nobara since right now it's the only easy way for me to install it
VWhat are you looking to do with ROCM?
GGitHub
AI Inferencing at the Edge. A simple one-file way to run various GGML models with KoboldAI's UI with AMD ROCm offloading - GitHub - YellowRoseCx/koboldcpp-rocm: AI Inferencing at the Edge. ...
GSince so far, I have found that project to be one of the better ways to play with “ai” tech due to the easy interface and, wide module support that, and their backend API makes it possible to implement the output into other programs
GHowever, still waiting for ollama to merge this pull request https://github.com/jmorganca/ollama/pull/1146 since that would also be awesome, being able to run ollama on my gpu
GitHub
This change revamps the way ollama wires up llama.cpp for gguf to link directly via cgo instead
of running a subprocess. Within llama.cpp, a thin facade has been added to server.cpp (via included ...
of running a subprocess. Within llama.cpp, a thin facade has been added to server.cpp (via included ...
GBut the short version is I wanna play with cool ai tech locally
VI've used stable diffusion on Bazzite via distrobox using ROCM just fine
JWe should be putting ai workload shortcuts in justfiles
VI think it'd be a bit more work than it's worth, I kinda struggled to get it working because the landscape with ROCM and a lot of AI projects change quite often
GThank you I appreciate it since now I might be able to switch
VNo problem
VActually mentioning it, I want to try and get stable diffusion working on Deck
RIs there a way to download (as an archive) either specific bazzite root files (conf files of pipewire/pipewire-pulse/wireplumber from /usr/share) or all bazzite root files (if former only is not possible) from bazzite-deck:testing?
Jpodman pull it
Jpodman pull ghcr.io/ublue-os/bazzite:testingROK thank you!
Cout of curiosity, why does bazzite have at least 3 process trackers? NVtop, Btop, and Mission Center (and on Gnome, System Monitor).
Cit seems really excessive
VNVTop because Nvidia is weird, btop I think to match SteamOS? And Mission Center because it's a good GUI process tracker that a lot of us are just fans of, also good for people coming from Windows to have something familliar.
Hmission center isnt even part of the base bazzite install though? i dont have it at least
Hits optional
VI think it's a pre-installed flatpak
VMight just be on newly installed systems
H
V@cyber.glitterhoof
Jnvtop comes from the base images
CI know how to remove flatpaks
CI'm just saying 4 process trackers is too many
VAh, that makes sense
Jbtop is to match steamos, but those are cli
VAnd the GNOME/KDE ones come from the respective DE's
VWe could remove one but like, eh
Cespecially on non-steamdeck versions of bazzite
JI'll remove the gnome one in bluefin but I wanted to shake out mission control for a while and wanted to keep a backup so I haven't removed it yet
Juntil there's more reliable upstream ways to ensure flatpaks are installed I'm fine keeping backups on the image, I do hide the .desktop files though
VI mean, I guess removing the DE-specific process trackers would be ok but the others have their own justifications.
VCould maybe remove btop on nvidia, but it'd be creating a discrepancy between Bazzite and SteamOS which isn't the goal
TGNOME images preinstall it
Hah
VKDE too
VI'm fairly certain
Tit does not
TVHuh, I must have installed it then
TI did too on my KDE setup. Favorite system monitor application
VAlso, would adding Easy Effects to bazzite portal's music section be something anybody else is interested in?
VIt's a Pipewire EQ program.
TIt's in utilities iirc in the portal
VAh it is
Tshould it be in music? i think there's only music clients in there though
