• 0 Posts
  • 28 Comments
Joined 2 years ago
Cake day: June 25th, 2023
  • azvasKvklenko@sh.itjust.workstoLinux@lemmy.ml•PS5 Controller Not Working - Linux MintEnglish
    3·
    2 months ago

    Hi there, having two dualsense and one ps4 controller, using them for ages on Linux and they mostly run great, but your issues doesn’t sound completely new either.

    It’s very important on how you installed Steam and whether it’s native package or Flatpak. For Flatpak you might need special udev rules to allow the controller inside sandbox, usually can be installed using steam-devices package.

    As others said, enable Playstation Controller support in Steam’s controller settings page.

    Check if Steam overlay is functioning. In-game, press Shift+Tab and you should see the overlay and then you should be able to get to controller settings. Try out both with Steam Input enabled and disabled - by default I guess it depends on the game, but mostly enabling it will make it work for games that have issues picking up ds natively.

    Test your controllers using something like jstest-gtk. Perhaps there is something else connected that acts as player 1 controller.

  • azvasKvklenko@sh.itjust.workstoLinux@lemmy.ml•So what the boink is Bazzite "cloud native" blah?English
    7·
    3 months ago

    Generally the industry shifted in a direction where it heavily relies on containers for running cloud applications. This solves many problems with traditional server systems where you’d be sticking to certain distro, so certain dependencies are in fixed versions, which brings some limitations. Container is an environment to run process in an isolated way so that it had its own root filesystem, its own view on what resources are available, sort of like it was separate machine, but it’s still running on the same machine natively using the same kernel as the host. You can then have multiple of such containers, all serving its narrow purpose and they all come with the complete fs and whatever distro release they are tested with. Nowadays cloud computing is all about containers and they come from images that are built in OCI format using Dockerfile syntax. After building an image, it is typically pushed into registry where it can be pulled from over network to be utilized across different nodes, which makes it pretty easy to scale and propagate changes in cloud environments.

    Now what that means to Bazzite/Universal Blue is that it uses similar tech to deploy the system, though the target here is your local machine. Of course some of the characteristics aren’t relevant in this scenario, but it solves some of the same problem - build predictable and reproducible environment that can be thoroughly tested before publishing. The general idea is similar to how devops build cloud apps: there is CI pipeline that runs the build using giant Dockerfile (or Containerfile, same thing) inside of which they include everything that the system needs (running traditional package manager and act as it was normal Linux distro during the build), which then results as image that’s being pushed to registry. Bazzite users then install updates by pulling new version of the image and ‘rebasing’ to it. It is called rebasing here, because rpm-ostree lets users add additional layers with more packages on top of that.

    EDIT: here’s the Containerfile I’ve been talking about: https://github.com/ublue-os/bazzite/blob/main/Containerfile Might give you some idea on how this works.