"Bus error" error with an ASUS BW-16D1HT (3.10-MK) drive in a Raidsonic IB-525-U3 (JMS567) case

[dtech]

First of all, the above drive+case combo works perfectly under Windows 10.
But I tried under OSMC (Vero 4K+) and LibreELEC-AML (multiple S905D, S912), on several Amlogic devices (armhf), but with the above combination I get this error:

Code: Select all

osmc@Vero4K-Plus:~$ makemkvcon --debug info disc:0
MakeMKV v1.17.6 linux(armhf-release) started
Debug logging enabled, log will be saved as file:///home/osmc/MakeMKV_log.txt
Profile parsing error: default profile missing, using builtin default
Bus error

Unfortunately, the log does not contain any useful information about the error:

Code: Select all

Debug log started at Tue Jan 23 12:23:45 2024 , written by MakeMKV v1.17.6 linux(armhf-release)
001005:0000 MakeMKV v1.17.6 linux(armhf-release) started
001004:0000 Debug logging enabled, log will be saved as file:///home/osmc/MakeMKV_log.txt
Using 262272KB for read cache.
001009:0000 Profile parsing error: default profile missing, using builtin default
Network access is ENABLED, CURL version 7.74.0/OpenSSL/1.1.1w/1.43.0 (arm-unknown-linux-gnueabihf) , proxy server not set.

I had no problems with any of the tested configurations with two other non-UHD drives (Samsung SE-506BB slim USB drive and LG BE06LU10 standard USB drive), even though they are USB 2.0.

However, I don't know if the drive (ASUS BW-16D1HT) or the external case (Raidsonic IB-525-U3) can be the culprit in the "Bus error". Does anyone have any ideas?

[dtech]

I think I got a bit closer to the problem, because the error only exists on systems that use a 64-bit (aarch64) kernel but have a 32-bit (armhf) userspace.

At the moment, I haven't been able to try it on native 64-bit. However, it was tested on native 32-bit with Amlogic S812 SoC, makemkvc does not give errors, but there is no hardware acceleration for H.265 for 10-bit HDR. (But it started with software playback, although it is quite a slideshow, but of course this is not the fault of makemkv.)

So the problem happens when try to call the 64-bit sg module with the armhf binary, but I have no idea how to debug this.

[dtech]

Today I was able to test it and it works properly with 64-bit kernel and 64-bit userspace as well.

Unfortunately, I have no idea how to make it work on an aarch64 kernel and a 32-bit (armhf) userspace. In most cases, this combination is still in use as a general standard.

The situation is the same on Raspberry Pi 4, not only on Amlogic boxes.