EGL init fails on ubuntu 23.04 about martypc HOT 16 CLOSED

In case it's relevant, I built martypc with cargo build, I downloaded the 8088 GLABIOS rom, made an icon.png (it was complaining about this) in install/, and added a rom override to the toml:

rom_override = [
    { path = "./roms/GLABIOS_0.2.4_8T.ROM", address = 0xF0000, offset=0, org="Normal" },
]

from martypc.

In case it's relevant, I built martypc with cargo build, I downloaded the 8088 GLABIOS rom, made an icon.png (it was complaining about this) in install/, and added a rom override to the toml:

rom_override = [
    { path = "./roms/GLABIOS_0.2.4_8T.ROM", address = 0xF0000, offset=0, org="Normal" },
]

That is very relevant - I put the rom_override feature in mainly for rom developers so that they could force the emulator to use a specific rom, otherwise MartyPC is limited to the ROM hashes it knows about in its internal database ( I need to factor this out to an external definition file)

You were really close; you just need to load GLaBIOS at 0xFE000.

The intent I had for users was just to have them drop roms in the /roms/ folder and Marty would just figure out which one to use

from martypc.

You were really close; you just need to load GLaBIOS at 0xFE000.

And that did it! It's working well now. Thank you, I'll close.

from martypc.

Just another note - if you use the rom_override feature (which is fine, it lets you experiment with a bunch of ROMs I don't otherwise 'support') you are responsible for ALL the ROMs. So if you want to add a hard disk controller, you need to add another line and load the Xebec ROM there too, same for EGA and VGA.

from martypc.

The GLaBIOS download page:

https://github.com/640-KB/GLaBIOS/releases

Seems to suggest GLABIOS_0.2.4_8T.ROM (it's the first one they list), but roms.txt lists a GLaBIOS with a different checksum:

$ md5sum GLABIOS_0.2.4_8T.ROM 
cfcdd125e70d3f2343388c83ffabd6c7  GLABIOS_0.2.4_8T.ROM

from martypc.

The author of GLaBIOS was kind enough to create customized versions of GLaBIOS for MartyPC, those are included in the 0.1.2 binary release. They have special features.

Since GLaBIOS is under active development, I can't keep up with every version and change - I recommend using the two in the release archive.

from martypc.

Ah, I understand. I'll do that.

from martypc.

I notice that from your screenshot your render time is pretty high. at 7.3ms. It should be under 1ms. Would you be willing to install cargo flamegraph and take a measurement for me so I can see where that time is going?

https://github.com/flamegraph-rs/flamegraph

from martypc.

I'd expect it to be slow -- it's a cheap GPU running two 1440p screens and a fancy shell. I'll try flamegraph tomorrow.

from martypc.

The stuff in 'render time' actually runs on your CPU. I'm going to rename it to 'Framebuffer Time'

from martypc.

I had a go:

$ flamegraph -o x.svg -- ../target/debug/martypc

Then quit after a second or so.

http://www.rollthepotato.net/~john/x.svg

from martypc.

Thanks. For some reason the CGA device is taking 7x as much time to run as it should. Strange.

from martypc.

just a thought, when you build did you do 'cargo build' or 'cargo build -r' ? the former makes a debug build, which is very slow

from martypc.

Ahhhh yes I'm sure that's it. I didn't realize cargo defaulted to a debug build.

from martypc.

Youre not the first, it's a little frustrating that the default is a debug build. I've added a UI warning when MartyPC is built in debug mode, now you can't miss it!

from martypc.

Yeah, meson defaults to debug as well, it's caused quite a few libvips issues. I should add a warning like that.

from martypc.