Unknown hash on IPL.bin

[Maverick Hunter X]

My own dumped GameCube BIOS which is DOL-001(EUR) / DOT-001P (PAL Revision 1.0) is not recognized in Dolphin (Dolphin 5.0-rc27)

These are the checksums for it:
crc 4f319f43
md5 0cdda509e2da83c85bfe423dd87346cc
sha1 f27c63e5394e2fd1606f70df004c4fc2d6027700

I've confirmed this dump on http://redump.org and it's a perfect match however Dolphin says otherwise.

I have named it IPL.bin and put it in the created EUR folder under Sys\GC as instructed.

The BIOS work after I click OK when it says that the hash is unknown and found in the EUR directory.

Is there something I have missed here or is something wrong? I thought verified dumps of the BIOS was supported?

[Shonumi]

FYI, Dolphin doesn't check the hash via CRC, MD5, or SHA-1. It uses Addler32 according to this line -> https://github.com/dolphin-emu/dolphin/blob/c6f72115e94b2ab26f7f5443435a15d50b734853/Source/Core/Core/Boot/Boot.cpp#L166

Since Dolphin can calculate MD5 hashes, perhaps it would be better to switch to that in the code.

EDIT - Or maybe the Addler32 hash for the PAL IPL is wrong. @Maverick Hunter X, can you check it out? I think something like HashCalc on Windows can tell you Addler32.

[Maverick Hunter X]

Thanks for your reply!

I'm going to check the Addler32 checksum out right now for my IPL.bin. Brb!


EDIT:

My Addler32 checksum is af912c43 exactly as shown in the picture I uploaded.
I have dumped and redumped the BIOS numerous times and I get the same result and it's a perfect match to the one on http://redump.org

So that probably means Dolphin has a wrong checksum for the DOL-001(EUR) / DOT-001P (PAL Revision 1.0) BIOS.

EDIT 2:

This is straight from redump.org's GameCube BIOS DAT listing all of the known verified GameCube BIOSes

game (
name "gc-ntsc-10"
description "DOL-001(USA) / DOL-001(JPN) / SL-GC10 (NTSC Revision 1.0)"
rom ( name gc-ntsc-10.bin size 2097152 crc 6dac1f2a md5 fc924a7c879b661abc37cec4f018fdf3 sha1 a1837968288253ed541f2b11440b68f5a9b33875 )
)

game (
name "gc-pal-10"
description "DOL-001(EUR) / DOT-001P (PAL Revision 1.0)"
rom ( name gc-pal-10.bin size 2097152 crc 4f319f43 md5 0cdda509e2da83c85bfe423dd87346cc sha1 f27c63e5394e2fd1606f70df004c4fc2d6027700 )
)

game (
name "gc-pal-12"
description "DOL-101(EUR) (PAL Revision 1.2)"
rom ( name gc-pal-12.bin size 2097152 crc ad1b7f16 md5 db92574caab77a7ec99d4605fd6f2450 sha1 80b8744ff5e43585392f55546bd03a673d11ef5f )
)

[Shonumi]

Dolphin might be using the PAL 1.2 hash. If you can get the Addler32 hash of the 1.2 IPL, that would help solve this mystery.

[Maverick Hunter X]

(09-11-2015, 03:24 AM)Shonumi Wrote: Dolphin might be using the PAL 1.2 hash. If you can get the Addler32 hash of the 1.2 IPL, that would help solve this mystery.

That could be a bit problematic as I don't own a PAL 1.2 GameCube.

But if there is a way to derive/calculate it from the checksums then maybe.

But would it be possible to just add the PAL 1.0 to the existing list?

[Shonumi]

(09-11-2015, 03:35 AM)Maverick Hunter X Wrote: But would it be possible to just add the PAL 1.0 to the existing list?

Yes, that's easy, but it would be best to find out where the current PAL hash came from before doing that. We need to make sure if we can keep it or toss it.

[Maverick Hunter X]

(09-11-2015, 03:39 AM)Shonumi Wrote:

(09-11-2015, 03:35 AM)Maverick Hunter X Wrote: But would it be possible to just add the PAL 1.0 to the existing list?

Yes, that's easy, but it would be best to find out where the current PAL hash came from before doing that. We need to make sure if we can keep it or toss it.

It's too bad that redump.org didn't include Adler32, then we would have known right away.

Where did the Dolphin team get the current Adler32 hashes originally? Wouldn't it be possible to ask the people who have submitted those values?
That way they can use HashCalc with their BIOSes to get the CRC, MD5 and SHA1 values that we can compare to redump.org's values to determine if it is the PAL 1.2 that Dolphin uses.

That's the best solution I can come up with.

[Maverick Hunter X]

I have investigated further and have found the answer to all this although I used an unmoral way in doing so but I needed to find out.

First let me be very very clear on one thing, that I did this for Dolphin and that it should contain accurate hashes matched to redump.org's

In "dolphin/Boot.cpp" one will find on line 157 this: const u32 PAL = 0xA0EA7341; where A0EA7341 is the Adler32 hash.
This PAL BIOS have the CRC dd8cab7c which does not match the ones from http://redump.org

This means Dolphin have a hash of either an unknown or bad dumped PAL BIOS.

I'm sorry to say the same goes with the JAP BIOS const u32 JAP = 0x87424396; where 87424396 is the Adler32 hash with a CRC of 8bdabbd4 which does not match.

And the USA BIOS const u32 USA = 0x1FCE3FD6; where the Adler32 hash is 1FCE3FD6 with a CRC of 6d740ae7 is also wrong.

I can't speak for the const u32 USA_v1_1 = 0x4D5935D1; as it's not listed anywhere.


The conclusion is that Dolphin have wrong hashes for all the BIOSes and that's why my dumped verified PAL 1.0 BIOS is not found and these warnings pop up.

As I said earlier I only own a PAL 1.0 GameCube and since I have verified my dump with redump.org it's safe to assume that the Adler32 hash of af912c43 is 100% correct.

You need to find people in this community with known BIOS dumps verified for JAP and USA and the PAL 1.2

[mbc07]

I still have the IPL dump from my old (and dead) GameCube and they don't trigger "Invalid hash" in Dolphin when I use them. I don't know what revision is it, but it's US version. Unfortunately I didn't verify my dump when I got it (a looooong time ago) but apparently it works fine in Dolphin...

[LPFaint99]

(09-11-2015, 06:40 AM)Maverick Hunter X Wrote: I can't speak for the const u32 USA_v1_1 = 0x4D5935D1; as it's not listed anywhere.

That was dumped from my personal gamecube, md5 019e39822a9ca3029124f74dd4d55ac4, crc d5e6feea
sha1 239eacd86527ff9a75aeb7282da65797baeef010

The list from redump.org only has 3 (2 pal, 1 US/NTSC-J [not even sure if that seems right])
so it is far from exhaustive,
heres another https://bugs.dolphin-emu.org/issues/7035#change-721322