@balaton

Just so we're on the same page, and it might amount to the same thing anyway, but on Sam460 the VGA is recognised and the whole boot process plays out on the screen connected to passthrough GPU but once the kickstart roms have been loaded and OS4 starts to boot we just get DMA errors reported in the qemu window and the screen stays on the kickstart load screen. I'm not saying qemu is throwing the errors, it may be the sam460, but something is not happy about DMA errors.

Hmm. I tested that before I realised DVI was the output that was being activated for OS4. Maybe i'll try that again now that I have the DVI port connected! But all the same, there are still the errors so it's probably still a non-worker.

I believe geennaam reported this some way back so this isn't new info at all. I'm just not sure if it got missed as there's a lot in this thread now.

@balaton

I mean, in pseudo-code terms, it goes something like this:


What I really meant by how far do I want to go, is do I pursue passing through more devices, or do I pursue real hardware. And independently of that, do I pursue furthering the Mac side of things.

Right now, I'm finding this extremely interesting so it's probably a mix of all three! If I pursue real hardware then that will have to be at the expense of this hardware as I simply don't have the room for a big box Amiga and a big box gaming PC.

@derfs

Ohhh. Thanks. That's interesting and gives me something to go back and look at on mine as I didn't check the values with / without rom file. OR, mine didn't add an extra region. I'm not sure which now. I keep calling them regions. They might be BARs. Frankly, at that point, to me, they're just numbers

@derfs
Hang on, that's just changed - there's a new entry there now! A 32bit memory region. Was the first one with romfile="" and the second one without? Or did something else change?

@derfs

Yes, and not only do I think that's worth trying, but I'd like you to give it a go as it is in between the 5450 and my RX580 so a good next step. Your figures look almost identical to mine so I should be able to send you something this evening. It won't be until 8 or 9 BST though.

[edit] Do you have a ROM entry listed? I don't need to know what's in it, but it does need to be there, it seems.

@Maijestro

Thank you.

It's not massively high-end hardware, but it's no slug either. I built it in June 2020. It has an AMD Ryzen7 3700X cpu 3.6Ghz, 8/16 cores, Boost to 4.4Ghz. I think the host OS is just running off an old 256GB sata ssd I had lying around because the main use of the machine is gaming so the main OS is on some super-fast NVMe drive. Host has 32GB of DDR4 3200 memory.

Main GPU is an RX6700, although that is completely invisible to OS4 and that's just seeing an old HD5450 I scored off eBay.

If qemu is only using a single core for the emulation then really, I'd consider the host to be mediocre in terms of modern PCs. For the record, none of the fans in the case ramp up when running the emulation so it is to all intents, silent.

@kas1e

First of all, my currently passed through GPU has no 3D support. That is a known thing, it's too old. 2D only as far as I know. I can download that demo tonight and try, but if it's really Quake3 then I imagine it will be a slide-show. Remember for now this is a Radeon HD5450 only.

As for changing the mapping then it might be just as easy if you post the output from the properties of the device in OpenFirmware and I can create the commands. Hmm... it's not what we really want but I'm sure I could create a utility to generate an OF patch script from the device output on Mac / Linux, far, far quicker than I could learn how to do it in Forth.

So, find your graphics card in OpenFirmware. It's going to be something like "/pci/display@2" - if you have more than one, make sure it's the right one.

Then, at the of prompt, type the following (this is from memory, apologies if there are errors):



Paste the output here. I'm particularly interested in the Reg property and the Assigned Addresses property.

Please note, people, that I'm not prepared to sit here and do it dozens of times. But I can do it once or twice before I write something to do it if it helps people with real hardware. I hadn't quite grasped that this effort was potentially benefitting physical Pegasos2 owners as well!

For now I have work to crack on with.

[edit] It's a shame you're not in the UK - I'm about to send a PCI-PCIe bridge back to Amazon as it's not what I need :D

@derfs

Well, that saves some effort I think I can just not pass that device through as they are mapped as independent devices I believe. I am reaching the point of just how far do I want to go with this now.

@balaton
Quote:
OK, understood. Obviously before all of this, Qemu was a bit of a black box to me. It's gradually opening up.

Quote:

That is something I will need to investigate. Morphos might tell me something there as well. I can probably access that quicker than I can get a linux guest setup. I'll take a look.

I also need to properly map the audio side of the card as well.

@balaton

Yes, and right now all I really know is that as soon as I try to transfer a file it only gets a packet or two in and freezes the transfer. If I then try to interact with a window the whole OS freezes and I have to kill the emulator.

At the end of the day, I was intending to look at writing a driver for the qemu card rather than using an emulated rtl8139 but that's months away if I can even get my head round it at all.

@balaton

At the moment I'm not blocking the ROM with romfile="" and qemu does spit out a lot of errors on boot. Further I have to type blind, either the failsafe command or just the boot command since everything else needs no intervention now. It gets there.

I just tried to boot with the rom blocked (romfile="") and OS4 cannot init the card, although there are enough manual steps here that I need to be sure I'm typing the correct thing each time. I think I did! :


Network is completely unusable with GPU passthrough. Seems fine without. So clearly there is more work needed here.

[EDIT] I should actually read what I post! Yes, the debug info clearly says it cannot find the ROM signature and so closes. So that begs the question, does it just need the signature to be somewhere, or does it need the actual ROM? If it's just the signature then that might be able to be supplied without actually loading it. Not that it's really a problem to load it, it just makes the boot process that bit more awkward.

OK, just to update, I think this is fully working using a Sapphire HD5450. I had to purchase Enhancer 2.2 for the drivers. Without them I could tell stuff was booted and running but I had no video, but now it seems good.

Resolution is 1920x1080@32bit, frame rates seem OK and Mace Demo fully works at a decent frame rate. This is the first time I've seen that game properly on OS4. I own it on Steam but under FE Classic emulation it was always missing sprites and stuff. Bear in mind, this is considered a low-end GPU.

I've had a couple of system freezes but each time it was when I was doing something network intensive. If I can work out how you do screenshots on OS4 I'll post some screenshots of the PCI resources as OS4 sees it.

There's still quite a bit I need to do. I haven't changed the mapping for the integrated audio. I don't know if that would work if I did and clearly this isn't an end-user friendly solution by any stretch of the imagination.

I would like to work out how to enable the HDMI output from the card, if that's possible because my DVI to HDMI isn't long enough and I've had to raise the machine up on blocks of wood for the cable to reach :D

I'll consider passing through a network card too if I have a supported one and see if that helps with the freezes I've been seeing. I will also see if I can get my RX580 passed through as well but I'm unsure what to do on the addressing for that as one of the memory regions is within 64bit. I need to read the documentation.

Leave this with me - I need to do some work on my OS4 install but it's looking promising!

So I'm battling with a number of different issues now, most of which lie with the potatoe pressing the keys on the keyboard!

So far, I haven't worked out how to get monitor output AND serial output. I mean, I can get monitor output but it's in a tiny window and any info command just scrolls off the screen. Maybe I can be specific about which PCI device I want info on. Hmmm.

I do currently have SM501 device as well but the guest isn't initialising it.

It would be a good idea now for me to throw my config in here in case I have something wrong as my brain is a bit fried right now.

@kas1e

Unfortunately, at this point it's not a script as such so not going to be a lot of use to anyone else, I've basically typed in forth commands at the Open Firmware prompt to get it to spit out the numbers, pasted them into a code editor, modified the relevant bits and then added Forth commands to push them back in in their modified form.

If this were to work then we can look at scripting it. But with my lack of Forth knowledge that's not going to happen overnight.

Anyway, without comments:



This is exactly the same but with all the raw numbers in comments

At the moment all I'm doing is attempting to address the 32 vs 64bit as mentioned here: #630

So with my script, I can now boot and I know the system is booted because I can see alsa errors where I would expect to hear sound if my alsa setup worked on this computer (something for another time), but as you can tell, I don't have a picture on the screen.

But I think this now looks reasonable:



Thats the same as before the script but with the 64bit flag not set.

@LiveForIt

Quote:

You can safely ignore the numbers there they are utterly meaningless, that was just me working out the forth syntax to modify the array which I've now done.

For the record, I'm really not convinced this is going to work, but sometime shortly we'll have the answer to that

[EDIT] Actually, looking at the numbers I have in front of me, I can see why we're at least testing it because on this older video card, even though the bars are being probed as 64bit all the numbers are within the first 32bit, so yeah, maybe. On my RX580, the ranges spanned the 32bit boundary and were actually 64bit numbers so in that instance I don't really see how it would physically work, I mean, the memory regions and the registers have to actually be where we're saying they are don't they?

But honestly, don't take my word for it.

OK, I guess I know how to add multiple address ranges (bars?) then.

@balaton
do I need to flip the 64bit entries in the reg too or just the assigned addresses?

This is still just a simple test

Before:


After:


What you're seeing here is, I've (manually) decoded the single entry in "assigned-addresses", modified the low 32bits to 0x84204111 instead of 0x84204000 and put it back in it's place.

So now I need to work out how to do it for multiple addresses and also the reg. Or at least I think I need to do the reg.

I don't know how to wrap it all up in a script just yet but given I didn't know anything about PCI or Forth until this week, one step at a time!!

[edit] And just to be clear, yes, I know those aren't the bits I'm meant to be flipping, I'm just messing right now.

Lol! Sorry, got to work too you know :D