• 20 Posts
  • 356 Comments
Joined 2 年前
cake
Cake day: 2023年6月12日

help-circle
  • If your primary usecase is going to be music (so a need for realtime capabilities for stuff like recording, VSTs and DAWs) then I do not reccomend immutable distros for a simple reason: you will probably/eventually need to hack something up to get it to work and at that moment, the immutability is just extra work.

    As far as I have tried fiddling with the music stack on Linux (which is not that much), the whole pipewire/JACK/carla stack is a bit messy.










  • taaz@biglemmowski.wintoLinux@lemmy.mllatest stats for fedora atomic spins
    link
    fedilink
    English
    arrow-up
    21
    arrow-down
    1
    ·
    edit-2
    29 天前

    Friend just hopped to Bazzite from Windows.
    I was hoping the atomocity would be a great boon - you kind of can’t break it right.

    Well, he wanted to configure RGB lighting on his mouse but the flatpak openrgb did not work, supposedly the udev rules included in bazzite by default, are not up to date or there was some other problem.
    As such we had to install openrgb the usual system-wide way, with rpm-ostree in terminal - something I was hoping he would never had to do.


  • Unless the vendor is rolling something super custom, for the communication TO the keyboard, it should use USB HID.

    Start Wireshark, filter for hid, connect the KB and the first message should be a HID descriptor of the KB, look for Output Reports (it’s meant from the POV of the usb master) or Feature Reports.
    Though, this will probably not yield much insight - vendors love to do the easy thing, reserve opaque 32x8 bytes as a “downlink” Output communication in the Vendor Usage Page and stuff their own protocol/encoding in there.

    On linux I can recommend hid-tools for working with this, in windows I believe your only solution is Wireshark.

    https://www.marcusfolkesson.se/blog/hid-report-descriptors/

    Happy Hacking!

    E: About the already reversed software, for logitech (and more) stuff, there is piper but you will want to look into the underlying daemon libratbag, there is also solaar








  • -S should not even try to refresh the database, that is what -Sy is for. And doing any variation of -Sy without also u (upgrade) is the unsupported partial “upgrade”, so it is possible that the time changes but only in the case of misuse.

    Also noticed you can just check the mtime of the directory itself, /var/lib/pacman/sync - directory mtime does not change when the files change content but pacman/alpm probably downloads the new databases to some temp files then moves them into the directory, changing it’s modify time (see stat, stat -c '%Y').