hi Nico and Peter, my friend wrote to Belkasoft and we just got a
reply (please scroll down to see it) which confirms that these dump
file offsets are not the physical addresses. We were already sure
about that : these addresses were different for each dump and a number
of "ghosts" was different;
Nico Huber wrote:
> > 0x42D3B3000 - working integrated graphics ROM !!!
> >
> > 0x42D305020 - working discrete graphics ROM (first working copy, the same)
> > 0x42E40DCD0 - working discrete graphics ROM (second working copy, the same)
>
> nice work! If these are physical addresses, dumping from
Hi,
On 07.07.2017 20:03, Mike Banon wrote:
> === ROM locations examples for 0x0 - 0x42F00 dump made while 16GB RAM:
>
> 0x000512000 - broken integrated graphics ROM, first "ghost"
> 0x3250D9020 - broken integrated graphics ROM, second "ghost"
> 0x3578FB000 - broken integrated graphics ROM,
This page from coreboot's official wiki - [1] - describes 5 ways to
extract VGABIOS. However, all these ways are either unsuitable for AMD
AtomBIOS extraction at all - or do not work for laptop's discrete AMD GPU
*** [1] https://www.coreboot.org/VGA_support#How_to_retrieve_a_good_video_bios
4 matches
Mail list logo
