mattyj2001 wrote:I have a BU40N that is _not_ working with firmware 1.01, but it seems to be some other weird kind of firmware, maybe? The Drive Information box in MakeMKV reports this (on a Mac):demon wrote: Wed Jan 30, 2019 2:43 am What OS are you on? For me, on Linux, this is what MakeMKV looked like after ripping a disc on my laptop:
https://owncloud.now.ai/index.php/s/UPb1hifvpgog22d
The "DEBUG: Code 03DF/..." line is what you should see if it's successfully able to rip from your drive. My BU40N worked fine with the 1.01 firmware (note the "Revision:" line in the box on the right; that's how the 1.01 firmware on this drive identifies itself).
And no, you don't need to redownload the app. The "Downloading latest SDF" and "Downloading latest HK" items in the log window are the app downloading the data it needs to do the rip. If you see "DEBUG: Code 01BE/...", as mike said, then your drive isn't cooperating. It looks like 1.00 is the latest firmware for that drive on the HLDS site, so it may just not work for a bit yet, but I'm sure mike is working on it.
Drive Information
OS device name: /dev/rdisk2
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE BU40N
Revision: 1.01
Serial number: KZPHCCG2136
Firmware date: 2117-12-22 12:21
Bus encryption flags: 1F
Highest AACS version: 66
But in the log window it reports:
"Optical drive "BD-RE HL-DT-ST BD-RE BU40N 1.01d" opened in OS access mode."
Firmware 1.01d? Whatever that is ... Also, confirmed I have the latest keys_hashed.txt in my data directory and I am attempting to rip a disk that is known to work (2001. I feel like we're all the same kind of sci-fi nerds.)
Not sure if it's possible/practical to downgrade/sidegrade the firmware.
We haven’t needed the txt file in some time now. It’s possible to downgrade/flash just like the other drives , but without knowing what’s not working it’s impossible for us to give any advice. Did you attempt to rip and get to the selection screen? Were errors present when attempting the rip?