This makes for more questions that answers, but lets brainstorm a bit to see if it produces a new idea:ġ) In the 1.9.3 image, what exactly is where the pointer points (I could get this myself by looking with a hex editor the ROM, but I’m a brick when it comes to understanding binary or code.
It goes against any logic and the only possible explanation is that the pointer is hard-coded in the hardware or in the VBIOS/GOP/driver. So we have the image from GOPupd 1.9.3 that has the original pointer, the microcode is relocated and thus impossible to be loaded, but the image still works then we have Image2, which changes the pointer, the microcode is removed and thus impossible to be loaded, but the image doesn’t work then we have the image from GOPupd 1.9.5 that changes the pointer, the microcode is relocated to that offset and thus available to be loaded, but the image doesn’t work. This meant that the microcode couldn’t be found by the loader, as if there wasn’t a microcode at all. Before 1.9.5, any present microcode was relocated because the GOP is simply too large to keep it at the same offset, but the pointer was unchanged. You’ve guessed it well, this was the reason of my confusion.
0 kommentar(er)
