• 1 Post
  • 28 Comments
Joined 9 months ago
cake
Cake day: January 5th, 2024

help-circle





  • The headphones you have don’t have any actual surround sound capabilities. The only thing they do is have a software driver that maps a set of channels from 7.1 surround sound to the binaural sound mapping of the headphones.

    The pipewire sound server can do the same thing as iCue with filter chains and specific plugins. See this post for some pointers and guidance if you wish to set it up for yourself.

    Do note that unless you have content built with actual 5.1 or 7.1 surround sound, there won’t be much actual benefit to using virtual surround sound on headphones in the first place.





  • https://librewolf.net/

    A summary from its site and known technical details:

    • no telemetry by default
    • includes uBlock Origin
    • has sane privacy-respecting defaults
    • prepackages arkenfox user.js
    • relatively well-maintained fork of Firefox that keeps up with upstream
    • No major controversies AFAIK

    As for Windows 7, nobody should really need to install Librewolf anyway on such a device. No device running Windows 7 should have access to the internet at this point. If you are asking about compatibility intending this use case, you have bigger problems to worry about than your choice of browser. If you just need to view HTML files graphically, even Internet Explorer or an older firefox ESR will do.


  • We are well beyond the point of a majority of common hardware having built-in kernel drivers and userland software for extra stuff like RGB control that the best advice is rather avoiding Linux, to instead avoid the trash hardware (NVidia for the time being, GoXLR, Broadcom, etc.). My GPU, audio hardware, network interfaces are both popular products and have worked out of the box for years now.


  • Assuming you are installing your Steam library on your ext4 partition rather than ntfs one for your Windows install, BeamNG will likely be the easier game to diagnose for your game crashes on launch. The log file to find for BeamNG is located by default in steamapps/compatdata/284160/pfx/drive_c/users/steamuser/AppData/Local/BeamNG.drive/0.32/ as beamng.log. By default in a standard Steam install, your steam library is located at ~/.steam/root/. I am unsure if Bazzite installs Steam as a Flatpak. If it does, the default Steam library should be at ~/.var/app/com.valvesoftware.Steam/data/Steam/. If you chose a custom location for your Steam library, it will be wherever you chose it to be.









  • jrgd@lemm.eetolinuxmemes@lemmy.worldonly as in free beer
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 months ago

    If that is the case, the developer should have likely noted otherwise before closing the issue as the final piece of discussion. That is good to know that your experience hasn’t dropped the OS into base Windows 11. If as you say is true, the developer should also really spend some time cleaning up the README and clarify that base Tiny11 can actually be updated in-OS. I will still test in a VM later today to confirm that Tiny11 doesn’t actually erode or degrade on update for myself.


  • jrgd@lemm.eetolinuxmemes@lemmy.worldonly as in free beer
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    4 months ago

    From the Github README:

    Also, for the very first time, introducing tiny11 core builder! A more powerful script, designed for a quick and dirty development testbed. Just the bare minimun, none of the fluff. This script generates a significantly reduced Windows 11 image. However, it’s not suitable for regular use due to its lack of serviceability - you can’t add languages, updates, or features post-creation. tiny11 Core is not a full Windows 11 substitute but a rapid testing or development tool, potentially useful for VM environments.

    It literally says that it cannot be updated from a built OS install. You need to reinstall tiny11 by rebuilding the install image with a newer Windows 11 base image. Obviously it would be best to do this every time there is a security patch release for Windows 11.

    EDIT: Rereading further, the bigger Tiny11 image might be able to be updated in-OS. I’m going to dig through the ps1 scripts to see if the README holds up to that un-noted capability.

    EDIT2: I don’t see any registry edits that knock Windows Updater offline. I’ll test it in a VM to see if things work (from prebuilt when it eventually downloads). Though I am unsure at this moment if such an image’s changes will survive a Windows update at all.

    EDIT3: VM not tested yet, but an issue on the GitHub seems to corroborate my initial assumption.

    EDIT4: VM tested. Things claimed to be patched out (Edge) came back with one of the cumulative updates applied shortly after install. Other cumulative updates are being blocked (error instantly on attempt to install after download) (perhaps unintentionally). Image downloaded claimed to be for 23H2, but Windows 11 22H2 was installed, seemingly with no way to actually upgrade. I think my point stands.