Slight correction, it’s available in Linux 6.7, and has to be enabled with the kernel parameter nouveau.config=NvGspRm=1. It may be enabled by default soon though (latest news I could find about that here).
- 0 Posts
- 5 Comments
Joined 1 year ago
Cake day: August 12th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
NVK itself is not dependent on anything proprietary, but it’s practically required to enable NVIDIA’s GSP firmware blob if you want to see actual performance since it’s what enables re-clocking (older post by Collabora here which touches on it).
2·9 months agoCheers, glad to hear you got it working. I don’t think there’s any problem on your end; all my flatpaks are user-installed as a Guix System user, so it didn’t cross my mind that a habitually-placed
--userflag would not work if something was installed system-wide!
Thanks for posting about this! I never thought to try this as an Akregator user, but it’s a great idea… I spent the past day getting this to work since I also use the Flatpaks; hope it helps.
As suggested by @progandy@feddit.de, one solution is to define a custom protocol where the URL gets passed to a script that opens Firefox Reader with the URL; here’s what I’ve done:
- Decide on a protocol name, which the URL will be prefixed with and passed to
xdg-opensince that should be available to the Flatpak. I usedfirefox-readeras the protocol, so I putxdg-open firefox-reader://%uas the custom command (so a command Akregator would run might look likexdg-open firefox-reader://https://example.com). - Define a desktop entry to support the custom protocol (you can see mine below).
~/.local/share/applicationsis the standard place to put these, as far as I’m aware. Since the custom protocol needs to be removed from the URL, I wrote a script (also below) to do this and then call Firefox withabout:reader?url=prefixed. The script can be anywhere in$PATH. - Add the desktop entry as a “default application” for opening URLs using this custom protocol. In my case, I ran
xdg-mime default org.mozilla.firefox.reader.desktop x-scheme-handler/firefox-reader(org.mozilla.firefox.reader.desktopis the name of my desktop entry file). - You also might have to update some mime/xdg database stuff. I had to run
update-desktop-database ~/.local/share/applicationssoxdg-openwould find the “Firefox Reader” desktop entry.
My Firefox Reader desktop entry
[Desktop Entry] Type=Application Name=Firefox Reader Exec=open-firefox-reader.sh %u StartupNotify=false MimeType=x-scheme-handler/firefox-reader;open-firefox-reader.sh script
#!/usr/bin/env bash flatpak run --user org.mozilla.firefox about:reader?url="${1#firefox-reader://}"If you have any other trouble or want to find more information about this since the desktop entry could probably be tweaked, here are the sources of note I used to figure this out (If I forgot a step or two writing this, they should also be present somewhere in there):
- Decide on a protocol name, which the URL will be prefixed with and passed to
You might be interested in git-annex (see the Bob use case).
It has file tracking so you can - for example - “ask” a repository at drive A where some file is, and git-annex can tell you it’s on drives C and D.
git-annex can also enforce rules like: “always have at least 3 copies of file X, and any drive will do”; “have one copy of every file at the drives in my house, and have another at the drives in my parents’ house”; or “if a file is really big, don’t store it on certain drives”.