AACS errors on Fedora FC 19 X64

[mike admin]

Apparently the kernel in Fedora 19 has an unknown bug that filters or damages raw SCSI commands sent by MakeMKV to the drive. As a result MakeMKV fails to open any blu-ray disc with an AACS error. So far the error was only reported on x64 kernel. The cause of the bug is not known, and there is no workaround short of using Ubuntu live cd or inside the VM. If you encounter AACS failures under linux, and are using the latest version of MakeMKV, please report your distro and kernel version in this thread.

UPDATE: The bugis in openssl library, and not in the kernel as previously thought. Please post the version of the openssl library as well if you encounter the issue.

UPDATE2: Kudos to nevergonnahappen4me for figuring out the bug and workaround. The workaround works for both F19 and F20.

In F20, you can run './configure' as usual, then edit the Makefile, adding ' -DOPENSSL_NO_EC' to the line that starts with 'CFLAGS='. Build and install normally after that.

[miracoolix]

Hi Mike,

I had that problem with fedora 19 and it's still there with after upgrading to fedora 20.

Code: Select all

uname -a
Linux berlin 3.11.10-301.fc20.x86_64 #1 SMP Thu Dec 5 14:01:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[miracoolix]

Mike,

I booted back to 3.11.8 kernel with the same result.

Sure that's a kernel problem? What about that aacs key story (key on disc made makemkv key invalid?)?

[Woodstock]

If the drive itself were the issue (AACS key revoked), why would it work in Windows with the same key? That is, some people are dual-booting (or running virtual machines) with Windows, and the Windows version works with the same hardware.

[tramal]

Same problem here. Playback of Blurays with VLC is also failing because of AACS key failure, even though I have the latest KEYDB.cfg in my ~/.config/aacs.

Running Fedora 20

Linux localhost.localdomain 3.11.10-301.fc20.x86_64 #1 SMP Thu Dec 5 14:01:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[tor123]

Still present kernel-3.12.5-302.fc20.x86_64. I have filed this bug https://bugzilla.redhat.com/show_bug.cgi?id=1042715 in bugzilla.

[miracoolix]

I've verified it works on the same machine with VMWare and Windows XP.

[tctc1]

Same issues here, no luck with any BD with Fedora 20 x86_64 and makemkv 1.8.7, please help.

[Linux@F20 ~]$ uname -a
Linux F20 3.12.5-301.fc20.x86_64 #1 SMP Fri Dec 13 22:33:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[MartinKG]

same behavior her on Fedora 20 x86_64 with makemkv from 1.8.1 to 1.8.7.
also when booting with a older kernel vmlinuz-3.11.7-200.fc19.x86_64 from Fedora 19.

uname -a
Linux fc20 3.12.5-302.fc20.x86_64 #1 SMP Tue Dec 17 20:42:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[nevergonnahappen4me]

I have tried 1.8.7 on Fedora 19 (x86_64) with the following kernels: 3.11.8, 3.11.10, 3.12.5, & 3.13.0-0.rc4.git3.1.vanilla.mainline. (That last one is a Vanilla kernel, no special patches/changes from the Fedora team.)

All ended with the same result, failure to open the disc. I do not have this issue when booted from a Ubuntu 13.10 LiveUSB (same machine and with the same disc in the drive).

[tor123]

HI

I am able to get makemkv to work with glibc-2.17-11.fc19.x86_64 and kernel-3.10.3-300.fc19.x86_64 in Fedora. I will now try to upgrade the kernel by not glibc.

[tor123]

I am able top open bluray disc with kernel-3.12.5-200.fc19.x86_64. and glibc glibc-2.17-11.fc19.x86_64 on system with X86_64.

[nevergonnahappen4me]

I am using kernel 3.12.5-200.fc19. I downgraded my glibc to 2.17-11.fc19 (I was using 2.17-20.fc19). I even recompiled/reinstalled the makemkv-oss component.

No change.

[unxfrek]

I can confirm that this happening with me also my blu-ray device is:

PIONEER BD-RW BDR-208D 1.10

I'm using F20 kernel-3.12.5-302.fc20.x86_64

I tried using MakeMKV with ubuntu live image ubuntu-13.10-desktop-amd64, it worked without any errors, with Fedora 20 I get:

Code: Select all

MMBD: Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT ESTABLISHED' occurred while issuing SCSI command AD010..080002400 to device 'SG:dev_11:0'
MMBD: Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION FAILURE' occurred while issuing SCSI command A30..00200740100720..09AAA85C36B435CDBDF16E94C22177BF878 to device 'SG:dev_11:0'
MMBD: Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT ESTABLISHED' occurred while issuing SCSI command AD010..080002400 to device 'SG:dev_11:0'

[unxfrek]

I also bumped up scsi debug logging to try and see what is going on.

Code: Select all

[43838.027681] sr 1:0:0:0: [sr0] Send: 
[43838.027686] 0xffff8805664e2900 
[43838.027690] sr 1:0:0:0: [sr0] CDB: 
[43838.027692] Test Unit Ready: 00 00 00 00 00 00
[43838.027698] buffer = 0x          (null), bufflen = 0, queuecommand 0xffffffff81446530
[43838.027703] leaving scsi_dispatch_cmnd()
[43838.027924] sr 1:0:0:0: [sr0] Done: 
[43838.027926] 0xffff8805664e2900 SUCCESS
[43838.027929] sr 1:0:0:0: [sr0]  
[43838.027932] Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[43838.027934] sr 1:0:0:0: [sr0] CDB: 
[43838.027935] Test Unit Ready: 00 00 00 00 00 00
[43838.027942] sr 1:0:0:0: [sr0] scsi host busy 1 failed 0
[43838.027945] sr 1:0:0:0: Notifying upper driver of completion (result 0)
[43838.027947] 0 sectors total, 0 bytes done.

This just repeats, the Send data seems to go through but then towards the end 'scsi host busy 1 failed 0' Notifying upper driver of completion (result 0) seems to fail. I get a Unknown status when I check the sense status.

Code: Select all

sg_decode_sense --status=4a 01 00 00 10 00 00 00 08 00
SCSI status: Unknown status
Probably uninitialized data.
  Try to view as SCSI-1 non-extended sense:
  AdValid=0  Error class=0  Error code=1

I'll have to try the same test's on a live ubuntu image later today.