• 0 Posts
  • 70 Comments
Joined 1 year ago
cake
Cake day: April 23rd, 2023

help-circle

  • Unfortunately I can’t even test Llama 3.1 in Alpaca because it refuses to download, showing some error message with the important bits cut off.

    That said, the Alpaca download interface seems much more robust, allowing me to select a model and then select any version of it for download, not just apparently picking whatever version it thinks I should use. That’s an improvement for sure. On GPT4All I basically have to download the model manually if I want one that’s not the default, and when I do that there’s a decent chance it doesn’t run on GPU.

    However, GPT4All allows me to plainly see how I can edit the system prompt and many other parameters the model is run with, and even configure multiple sets of parameters for the same model. That allows me to effectively pre-configure a model in much more creative ways, such as programming it to be a specific character with a specific background and mindset. I can get the Mistral model from earlier to act like anything from a very curt and emotionally neutral virtual intelligence named Jarvis to a grumpy fantasy monster whose behavior is transcribed by a narrator. GPT4All can even present an API endpoint to localhost for other programs to use.

    Alpaca seems to have some degree of model customization, but I can’t tell how well it compares, probably because I’m not familiar with using ollama and I don’t feel like tinkering with it since it doesn’t want to use my GPU. The one thing I can see that’s better in it is the use of multiple models at the same time; right now GPT4All will unload one model before it loads another.


  • I have a fairly substantial 16gb AMD GPU, and when I load in Llama 3.1 8B Instruct 128k (Q4_0), it gives me about 12 tokens per second. That’s reasonably fast enough for me, but only 50% faster than CPU (which I test by loading mlabonne’s abliterated Q4_K_M version, which runs on CPU in GPT4All, though I have no idea if that’s actually meant to be comparable in performance).

    Then I load in Nous Hermes 2 Mistral 7B DPO (also Q4_0) and it blazes through at 50+ tokens per second. So I don’t really know what’s going on there. Seems like performance varies a lot from model to model, but I don’t know enough to speculate why. I can’t even try Gemma2 models, GPT4All just crashes with them. I should probably test Alpaca to see if these perform any different there…





  • He did at the beginning, but he helped them get what they wanted in the end, and I think that counts for something.

    “We’re thankful that the Biden administration played the long game on sick days and stuck with us for months after Congress imposed our updated national agreement,” Russo said. “Without making a big show of it, Joe Biden and members of his administration in the Transportation and Labor departments have been working continuously to get guaranteed paid sick days for all railroad workers.

    “We know that many of our members weren’t happy with our original agreement,” Russo said, “but through it all, we had faith that our friends in the White House and Congress would keep up the pressure on our railroad employers to get us the sick day benefits we deserve. Until we negotiated these new individual agreements with these carriers, an IBEW member who called out sick was not compensated.”



  • Onihikage@beehaw.orgtoGaming@beehaw.org98% compatibility
    link
    fedilink
    English
    arrow-up
    9
    ·
    2 months ago

    You don’t need to add the exe of whatever mod tool to Steam, use Steam Tinker Launch. It lets you add an exe to run instead of the game, concurrent with the game, or injected after the game is up, and it will run in the same prefix that Proton uses for that game. It also has tools for installing and using several mod managers, and generally a ton of good features for tinkering with the game.

    The main issue I haven’t solved is getting something like the Nexus mods “open in manager” to work. My guess is I might have to install, run, and configure a web browser inside the prefix, but that sounds really annoying so I haven’t tried it.



  • The ELI5 for Fedora’s atomic desktops is that if Windows had an Atomic Desktop version, Program Files and most of the Windows folder would be read only, and each program you installed yourself would go into its own folder in your user directory. That’s the basic idea. It’s harder to screw up an Atomic system as long as you stick to containerized app formats like flatpak/appimage whenever possible. It makes it easier for everyone to diagnose problems, and easier for users to roll back if an update has problems. Even if you were to install it right now, you could use one simple command to “roll back” to any image from the last three months.

    The benefit of Bazzite is you have all of the above, plus a lot of gaming-related stuff preinstalled which, if you were to install them yourself in a normal Fedora environment, you’d likely have to spend a lot of time just learning how they’re supposed to be configured, how they interact, which versions have problems, and how to troubleshoot problems when an update to one app breaks a prerequisite for something else; eventually you end up in config hell instead of actually using your computer. With Bazzite, the image maintainers are the ones in config hell - they work out the kinks, app versioning, communicate with upstream to fix issues, all that, so your system should be in the most functional state that a Linux system can be, so you only have to think about using your apps.

    tl;dr

    • Atomic Desktops are more resilient to randomly breaking from updates or user error, and are easier to revert to a prior state if problems do arise
    • Bazzite is a custom Atomic image with lots of gaming stuff preinstalled and preconfigured to work properly out of the box
    • If you’re a gamer and wanting to try out Linux, Bazzite is going to be the least painful way to get your feet wet.
    • Immutable distros are excellent for daily driving. I daily drive one myself!




  • The biggest thing missing for me is good VR support at the OS level. Even with all the optimizations in Bazzite making regular games perform about equivalent to Windows, latency in VR is awful, and motion smoothing just plain isn’t supported in Linux yet, on any hardware. Those two pain points make the experience much worse than on Windows, I’d be motion sick in minutes if I tried to actually play something. Thankfully, normal gaming works just fine, and I don’t play VR as often as flat games, so I can just boot into Windows when I want to do that.

    The second thing is the poor state of music players. I’m used to the very extensive feature set in MusicBee, and not a single native player hits all the boxes that MusicBee does. It can be run in Bottles, but not very well, and as a newbie, it took me a lot of extra tinkering to get things working even sort of right - file permissions, dotnet stuff, font libraries, etc. I still haven’t quite gotten file permissions working right, and font rendering is pretty bad (and custom font selection is broken entirely), but maybe I’ll figure some of that out eventually so I can stop booting into Windows whenever I want to make changes to my library.


  • Bazzite, from Universal Blue, based on Fedora Atomic Desktops. Immutable-style distro which means critical OS files and folders are read-only and all system apps (the ones preinstalled) are updated together as a full image rather than piecemeal. Anything not preinstalled can be installed in a distrobox or as a flatpak/appimage/aur, or as a last resort, layered with rpm-ostree. Extremely user-friendly, everything a gamer needs is either installed and preconfigured out of the box or available as a flatpak. Bazzite’s the first time I had a good enough experience on Linux that I made it my daily driver; now Windows is the secondary OS I only go to when I really need that one thing that only works there.





  • Onihikage@beehaw.orgtoLinux@lemmy.mlCrapped my system
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    Atomic means the core OS packages are in an immutable container such that none of its individual components can be updated separately; instead the entire container is replaced with a newer version when the system is updated. This makes it much less likely for something to break during normal use, and easier to rollback updates if something does happen to break. The ideal use case is a containerized environment where each app you use is installed in its own container, like Docker, or is otherwise self-contained such as flatpak installers, and doesn’t rely on any of the system’s packages.