On Wed, Feb 07, 2024 at 03:21:15AM +0300, Michael Tokarev wrote:
> 07.02.2024 02:17, Michael Tokarev пишет:
[...]
> > The binary in question is vgabios-stdvga.bin.
[...]
>"SMBIOS 2.1 table length 66822 exceeds 65535"
>
> Which wont help with 7.2 machine types (it changes defaults for 8.1+)
10.02.2024 22:09, Kevin O'Connor :
On Wed, Feb 07, 2024 at 03:21:15AM +0300, Michael Tokarev wrote:
07.02.2024 02:17, Michael Tokarev пишет:
[...]
The binary in question is vgabios-stdvga.bin.
[...]
"SMBIOS 2.1 table length 66822 exceeds 65535"
Which wont help with 7.2 machine types
So.. the difference is vgabios only, not seabios (vgabios-stdvga in this case).
And I can't get it to work with debugging vgabios, it always fails even with
DEBUG_LEVEL=2
(and level-1 logging isn't useful).
I was able to capture logs just for the non-working version, so there's nothing
to
comp
romfile_loadfile_g:
Based on romfile_loadfile but more flexible. User has to supply pointer
to a malloc function and the number of trailing padding bytes. Thus, any
memory region may be used.
romfile_loadfile:
It is now a wrapper around romfile_loadfile_g. Functionality is the same.
Signed-off-by
VGAROMs on MXM graphics cards need certain int15h functions present.
Tested on a HP EliteBook 8560w with coreboot and Quadro 2000M. A warning
is displayed for 30 seconds and performance is nerfed:
ERROR: Valid MXM Structure not found.
POST halted for 30 seconds, P-state limited to
Hi,
Dne 10. 02. 24 v 20:09 Kevin O'Connor napsal(a):
So it might not be a gcc issue really, but just a too large bios and
gcc-13 is able to produce more compact code which actually fits.
Ah, that makes sense. In the future, if you enable the seabios logs
it should help track these things down
11.02.2024 00:10, Rudolf Marek:
Hi,
Hello! Thank you for the reply!
Dne 10. 02. 24 v 20:09 Kevin O'Connor napsal(a):
So it might not be a gcc issue really, but just a too large bios and
gcc-13 is able to produce more compact code which actually fits.
Ah, that makes sense. In the future,
11.02.2024 09:49, Michael Tokarev wrote:
..
And the original bug report talks about windows, especially windows 10 -
just tried windows 7, and I don't see this behavior with it.
Probably should try with win11 - though this one is a bit more difficult
to install in bios mode.
So, win11 (in bio
