Anki Version: 2.1.15 (442df9d6) Qt 5.15.13 PyQt 5.15.10
Failed Attempts to Add FSRS:
1: Failed: Gear Icon for Any Deck Did Not Work: Launches Options but not option for FSRS
2: Failed: Code for FSRS Did Not Work: Anki Code used - 759844606
Perhaps the Anki version I have currently installed is not the latest making FSRS not possible for me to activate? Not sure? Any suggestions are truly appreciated. Many kind thanks.
That’s not accurate. Prior to being built-in functionality, FSRS could only be enabled through Custom Scheduling. The Helper add-on could be used with that, but it didn’t enable FSRS.
To be clear, I did use the recommended website ankiweb [as recommended by Kaiu] to select Linux (ARM) 2024+ which, in turn, downloaded Anki Version: 2.1.15 (442df9d6) Qt 5.15.13 PyQt 5.15.10; offering a packet with tar.zst file extension that landed in my local download folder. Is there another website location to find the latest version of Anki? Thanks everyone for your prompt reply
The file available at that link right now is anki-26.05-linux-aarch64.tar.zst – which should install version 26.05. You may have downloaded version 2.1.15 previously/from somewhere else and mixed it up with the more recent release.
Thank you very much for the last explanation…I think the older version may have spawned from the default software manager. Now I have the latest version 25.05, I did extract the tar.zst and used my terminal to complete installation. My terminal did say “complete” and to enter “anki” after changing directory using command “cd anki-linux” Period.
However, my terminal came back to me with this reply:
“bash: /usr/local/bin/anki: cannot execute binary file: Exec format error”
Does anyone have any idea what I action I should take?
Yes. You are right, the ARM version is not meant for me. I, instead, used anki-26.05-linux-x86_64.tar.zst, right click, select from menu “extract here” and placed extracted file on my desk top. Next I returned back to the desk top and double-clicked the executable file [icon with gear] and voila I now am able to have access to the latest version of Anki and most importantly, I can now see FSRS in the options menu. Brilliant !!! Thank you so much. Next: In the start menu, I had the Anki launch button but its launch function was turned off. So I then moved this Anki extracted folder off my desktop into a new folder [out of sight] to another location on my local drive. Then I returned back to the start menu, again, to scroll for the Ank launch button. Here, I right clicked, selected “properties” from the menu to display the “browse” button. Then I searched my local drive to find the new location for my Anki executable that is now stowed in its new safe location. Once found, I pressed “ok” and now my start menu Anki button is executable. Lastly, I saved this button to my panel. Thank you so much, Danika, for being patient with me. You have been a great help. I really appreciate you not giving up on me. A BIG THANK YOU.
Might be worth it to include a little command into the docs so that people can find out their architecture. E.g. uname -m[1] returns x86_64 in my case. So I know I have to use the x64 download.
But I’m not sure how easy this is going to be, due to the list of architectures being long and not the most obvious. For example, https://stackoverflow.com/questions/45125516/possible-values-for-uname-m shows a list of architectures starting with “ARM”. Those are arm arcitectures, but there is also e.g. aarch64, which doesn’t have “ARM” in it but is also an ARM achitecture.
I know way to little to know if all those architectures listed can be divided easily into arm, x64, x32 and possibly others. But it would be helpful to have a guide, especially for users that don’t know their architecture or how to find their architecture.
Edit: The anki website only shows “ARM”, but it really is “ARM64”. I assume “ARM32” would not be able to run that anki version. Should be added to the string in my opinion.
I had been toying with suggesting we mark the Windows ARM build as [rare] or [uncommon] or [less common] (because it is, right?). It seems unlikely that a typical Windows user would know the difference between an x64 chip and an ARM chip, unless they are using ARM. But I could see Windows 11 users looking at “Windows 10+” vs. “Windows 11” and grabbing the wrong build.
I don’t think so. At least if you consider that linux is installed on almost every non-consumer device.
But talking about laptops and desktops, I assume the cpu architectures are just as common / uncommon as with windows. Meaning x84_64 should be more common than ARM.
Not sure though if adding something like [uncommon] would help that much, though. I’d argue it’s better if the user knows how to check, so that the user downloads and installs the correct version from the get go. Though, arguably, one could just download the other anki version (e.g. ARM if they tried x84_64 first) if they notice that anki won’t run.
Yes, but that doesn’t work with every browser (especially with privacy settings enabled). E.g. for me some websites claim I use windows, though that certainly isn’t the case.
Having a command that runs on the users pc to identify architecture is much less error prone.
Maybe it makes sense to show platforms as tabs (with the detected platform selected) with some text instructions as used to be the case in the old website.
If I may add my input from a neophyte perspective, I agree with Danika, that is, to add (rare) to arch. Why? It would save time for those supporting this forum. Secondly, I would add a hyperlink on instruction on how to extract tsr.zst files. At first thought, it may seem so elementary to offer such instruction but remember more and more people are gravitating towards Linux. For such people, the terminal will likely be somewhat foreign. Also too, such instruction may decrease the odds of having pesky requests posted to this forum. BTW: Whoever invented Anki, is a genius. The internet is amazing and with Anki, one’s brain can also become amazing. Anki can really build a super sharp mind. Thanks again for your ongoing support.
Not really. It would increase support time for those that do not have x86_64. That’s why it’ important to give the users a way to find their cpu architecture (and maybe even try automatically determine the correct one as suggested above).
This is covered already in the installation instructions. They are linked in the downloads section:
When I switched to linux a few years ago the terminal was new to me, too. But it’s easy to learn. Especially if you have step by step instructions that are pretty fool safe, like those that the manual provides. I learned it, thousands of others learned it and so can new linux users.
But if they do not want to use the terminal, extracting archive files like .tar.xz can be done by most file managers by simply double clicking the file. Should be similar in windows, no?
Agreed, dae and the community build a great tool. And I’m glad the new leadership continues the great work (well, I dislike their corpo announcements, but the work on e.g. github is really good. Their announcements do a disservice to the actual great work that is being done in my opinion. But that’s off-topic here).