On Tue, 20 Feb 2024 14:41:50 -0500
Kevin O'Connor wrote:
> On Sat, Feb 10, 2024 at 11:17:54PM +0300, Michael Tokarev wrote:
> > 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
>
On Sat, Feb 10, 2024 at 11:17:54PM +0300, Michael Tokarev wrote:
> 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
On Sun, Feb 11, 2024 at 09:49:21AM +0300, Michael Tokarev wrote:
> Hello! Thank you for the reply!
>
> > Just a random idea, maybe there is something wrong with windows failing to
> > emulate stuff?
> > (the vgafixup.py)
>
> Well.
>
> Windows might fail to emulate something. The prob with
On Mon, Feb 12, 2024 at 01:06:34PM +0100, Fiona Ebner wrote:
> Am 10.02.24 um 21:17 schrieb Michael Tokarev:
> > 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
Am 10.02.24 um 21:17 schrieb Michael Tokarev:
> 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
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
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,
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
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
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
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
11 matches
Mail list logo
