Hi,
I'm new to coreboot and this list, so please forgive and tell me if I'm doing something wrong.
I've successfully compile coreboot and flash it to a Lenovo x220. I tried seabios and tianocore as a payload and it works. So strange compile errors as I'm used to when I compile an opensource project. So, _bravo_.
What I need now is to be able to set the graphic preallocated memory. Usually in bios, it's "DVMT pre alloc" or something. I know it's possible on this platform because the unlocked bios can do it.
Could anyone point me in the direction ?
Thanks,
Jief
Mainboard : x220, i7-2640M@2.80GHz
Hi and welcome to coreboot,
First of all please use coreboot container: https://hub.docker.com/r/coreboot/coreboot-sdk/ You are guaranteed to have no errors during compilation.
DVMT... this terminology is so confusing. I think it refers to the UMA memory which is configured here for x220:
https://github.com/coreboot/coreboot/blob/master/src/northbridge/intel/sandy...
You can change that by changing the gfx_uma_size parameter in CMOS configuration utility - nvramcui. It is a payload that modifies the CMOS based runtime options.
Regards, Michał
On 9/25/19 11:15 AM, jief wrote:
Hi,
I'm new to coreboot and this list, so please forgive and tell me if I'm doing something wrong.
I've successfully compile coreboot and flash it to a Lenovo x220. I tried seabios and tianocore as a payload and it works. So strange compile errors as I'm used to when I compile an opensource project. So, _bravo_.
What I need now is to be able to set the graphic preallocated memory. Usually in bios, it's "DVMT pre alloc" or something. I know it's possible on this platform because the unlocked bios can do it.
Could anyone point me in the direction ?
Thanks,
Jief
Mainboard : x220, i7-2640M@2.80GHz
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
Dear Jief, dear Michał,
On 25.09.19 14:39, Michal Zygowski wrote:
[…]
DVMT... this terminology is so confusing. I think it refers to the UMA memory which is configured here for x220:
https://github.com/coreboot/coreboot/blob/master/src/northbridge/intel/sandy...
Also, see `cmos.layout` [1].
``` 11 0 32M 11 1 64M 11 2 96M 11 3 128M 11 4 160M 11 5 192M 11 6 224M ```
You can change that by changing the gfx_uma_size parameter in CMOS configuration utility - nvramcui. It is a payload that modifies the CMOS based runtime options.
There is also the utility `nvramtool` in the directory `utils` allowing you to read and set values from the operating system.
Print current value:
nvramtool -r gfx_uma_size
To print all possible values:
nvramtool -e gfx_uma_size
To set a value (I believe):
nvramtool -w gfx_uma_size=224M
Kind regards,
Paul
[1]: https://review.coreboot.org/cgit/coreboot.git/tree/src/mainboard/lenovo/x220...
Hi,
thanks for quick answer.
Sorry, it wasn't far away, but I missed it.
I tried and Windows report it. So it works.
But my point is to boot macOS. It boots, but graphic memory is still not right, even after having increased that memory. So maybe there other parameter for graphic memory. I'm sure. I tried to find documentation on Sandy Bridge.
The annoying thing is that the Lenovo bios does it (after having unlocked the advanced menu), but not perfectly. So I guess that the problem is : how a macbookpro8,1 initialize that sandy bridge...
On 25.09.19 15:23, Paul Menzel wrote:
Dear Jief, dear Michał,
On 25.09.19 14:39, Michal Zygowski wrote:
[…]
DVMT... this terminology is so confusing. I think it refers to the UMA memory which is configured here for x220:
https://github.com/coreboot/coreboot/blob/master/src/northbridge/intel/sandy...
Also, see `cmos.layout` [1].
11 0 32M 11 1 64M 11 2 96M 11 3 128M 11 4 160M 11 5 192M 11 6 224MYou can change that by changing the gfx_uma_size parameter in CMOS configuration utility - nvramcui. It is a payload that modifies the CMOS based runtime options.
There is also the utility `nvramtool` in the directory `utils` allowing you to read and set values from the operating system.
Print current value:
nvramtool -r gfx_uma_size
To print all possible values:
nvramtool -e gfx_uma_size
To set a value (I believe):
nvramtool -w gfx_uma_size=224M
Kind regards,
Paul
It may have tried initializing the graphics by itself, ignoring a setting of the unknown-to-it BIOS. You may consider running OS X in a virtual machine under Linux host.
On Wed, Sep 25, 2019 at 9:32 PM jief1.l@gmail.com wrote:
Hi,
thanks for quick answer.
Sorry, it wasn't far away, but I missed it.
I tried and Windows report it. So it works.
But my point is to boot macOS. It boots, but graphic memory is still not right, even after having increased that memory. So maybe there other parameter for graphic memory. I'm sure. I tried to find documentation on Sandy Bridge.
The annoying thing is that the Lenovo bios does it (after having unlocked the advanced menu), but not perfectly. So I guess that the problem is : how a macbookpro8,1 initialize that sandy bridge...
On 25.09.19 15:23, Paul Menzel wrote:
Dear Jief, dear Michał,
On 25.09.19 14:39, Michal Zygowski wrote:
[…]
DVMT... this terminology is so confusing. I think it refers to the UMA memory which is configured here for x220:
https://github.com/coreboot/coreboot/blob/master/src/northbridge/intel/sandy...
Also, see `cmos.layout` [1].
11 0 32M 11 1 64M 11 2 96M 11 3 128M 11 4 160M 11 5 192M 11 6 224MYou can change that by changing the gfx_uma_size parameter in CMOS configuration utility - nvramcui. It is a payload that modifies the CMOS based runtime options.
There is also the utility `nvramtool` in the directory `utils` allowing you to read and set values from the operating system.
Print current value:
nvramtool -r gfx_uma_sizeTo print all possible values:
nvramtool -e gfx_uma_sizeTo set a value (I believe):
nvramtool -w gfx_uma_size=224MKind regards,
Paul
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
-
jief -
jief1.l＠gmail.com
-
Michal Zygowski -
Mike Banon -
Paul Menzel