Arch Linux User Repository

This now depends on libavcodec.so so when it needs to be rebuilded against new ffmpeg version you are forced to uninstall first otherwise the update will be blocked

I can confirm that a manual sudo modprobe sg was necessary to get makepkg to detect my DVD drive.

Beta key:

• https://forum.makemkv.com/forum/viewtopic.php?f=5&t=1053
• https://cable.ayra.ch/makemkv/

In case this helps anyone, I had makemkv 1.18.3 hang whenever I started it, maxing out one CPU with a process 'makemkvcon' that had to be killed independent of the GUI.

To fix this I had to:

1. Download an old MakeMKV appimage for 1.17.6. I used this one, but it is at your own risk: https://github.com/uncle-ben-devel/makemkv-appimage/releases/tag/1.17.6
2. Make the AppImage file executable (chmod u+x ...), and run it
3. Insert DVD into drive and read the disk

MakeMKV then downloaded the latest keyfiles to ~/.MakeMKV, and dumped my drive firmware to that folder too as another file. This appears to be where the later versions of MakeMKV are getting stuck.

After that I could quit the AppImage and run the normal 1.18.3 and it worked. This appears to be a common problem.

@jedcooper the name can be found in the log.

I also have problems to use MakeMKV. I have cleanly uninstalled it and rebuild with yay. Module sg loaded. All no luck. I didn't enter the current month's key though, dunno where? And @red-lichtie how to find out the exact drives name? As mine contains spaces and maybe special chars as it seems.

I have found a way to get even the latest version (1.18.3) working.

Edit .MakeMKV/settings.conf and add your drives name to "sdf_Stop",

In my case it looks like this: sdf_Stop = "TEAC_BD-W26SS-B_2.02_{serial number}"

With that, the original functionality returns.

v1.17.9 fails to build but likely patches can be cherry picked from later version

This has nothing to do with OpenSource/Free Software

MakeMKV is not Free/Libre software, it is closed source with only the GUI/Frontend being open. It even costs money and needs a license key (There are time limits beta keys but they are exactly that)

The LibreDrive Firmware is not designed to make your drive Open, it doesn't, it's only there so your drive reads DRM stuff it otherwise wouldn't.

Nothing of this have to do with Richard Stallmann or the free software movement. If anything, RMS would want to help you getting rid of DRM, he hates it.

You may be fine with not being able to read new BluRay, but others want them and hence the software was changed to be able to read them.

I'm pretty sure there are older versions somewhere in the internet or you just ask the maker of the software itself

The AUR comment section is about comments for the PKGBUILD, not the actual software itself. This should be moved to the Archlinux or MakeMKV Forum if you have any further questions.

So @Vamp898, what you're saying is, it is better to not be able to ready ANY BluRays at all just because some modern ones might/can cause problems?

What do you mean with "without firmware refuses to do what MakeMKV wants"? It has been doing it for years, without any libredrive firmware.

It looks to me as though this breakage is wanted/desired by the MakeMKV developers, kinf of Stallman like "use LibreDrive or forget it".

If you install an old MakeMKV version, you won't be able to read any modern BluRay.

The LibreDrive Firmware is not an requirement of 1.18, every modern BluRay need that. Without LibreDrive, your Blu-ray player will refuse the commands from MakeMKV to read/circumvent the encryption.

If your Drive doesn't support LibreDrive, there is nothing you can do, an old MakeMKV version will not help. You drive has built in DRM and without firmware refuses to do what MakeMKV wants

@Mirto52: I tried that with 1.17.7 and the compile failed. I had to reinstall Arch so I don't have an old package about to simply reinstall.

My question: Did you get it to compile? If yes, how?

The latest versions of MakemKV breaks systems that don't/can't have some idealistic Libre firmware on their drive.

How can I make/compile/install a version (max 1.17.?) that actually compiles and installs?