@MartinW

You describe the same behavior as I see with my 4850. But the hang at boot is caused by a crash of the RadeonHD driver after initialisation.

This doesn't happen with the Radeon RX driver and my RX 560.

@Hans
Quote:

You mean it can be done from boot loaders like amigaboot/bboot, etc ?

Quote:

I think any changes in the kernel is close to 0 chance that anything will be done, or ever will be released even if it will be done :)

Alternatively, we can disassemble pegasos2 kernel, find out the parts which do PCI tree parsing code, make a jump from assembler code to our new C based code, doing correct parsin, and at end jump back to the end of PCI scanning code (like viruses do). Then assemble whole thing back to working kernel code. That of course kind of hardcore, but can be done if nothing help.

At least i doing the same back in the past with the Cisco's firmwares when was in needs to update some parts and didn't have source code of it. And then makes .diff patch for.

Maybe that way will be also the solution and not _that_ hard (see futher in the post for more info).

@sailor
Quote:

Thanks, that the good one !

@All

So, from morphos, bridge definitely sees together with RadeonHD in it, check this out:

(click open images in new window for full sizes):

Bridge:



RadeonHD video part:



RadeonHD audio part:



What i can see from those screenshoots, is that everything on PCI0 except RadeonHD9250 in PCI1 (so AGP), but, the RadeonHD in the bridge (which on PCI0, and which OS4 kernel find), are on BUS#1 . Which mean that OS4 kernel, do read PCI0 and PCI1 lines, but scan (or read from firmware), no other BUS than 0.

Also, we can see, that RadeonHD both Video and Audio pars, sitting automatically on IRQ9 again (dunno if it's done by Morhos's kernel or by Firmware).

So either OS4 kernel didn't scan any other BUS than 0 on PCI0/1 lines (which probably the case), or, it internally scans it, but didn't see it on IRC9, and fail as well (Through i assume we should have errors from kernel logs).

I wrote mail to OS4-Beta about, so anyone with access to source code may check what actually the case there. Maybe Thomas can check it, but if not, as far as i know from the ones lurking around TonyW and Salas00 also have access to ExecSG code, so maybe they can confirm it..

@kas1eQuote:

From MorphOS I am using PCItool

@LiveForIt

Quote:
Yes, it certainly sounds like it. So, a possible workaround would be to flatten the node structure. Ugly, but it's either that, or someone has to fix the OS' openfirmware PCI tree parsing code...

Hans

@balaton

I've spent some time tonight looking at PCI Passthrough for 5450 GFX. BBoot 0.4, Qemu Master. I can't get it to work. Boot hangs before workbench even starts to load and leaves me with a grey sceen with the text "Workbench" in the top left in an old PAL-like resolution.

Hopefully I've not omitted any info. Let me know if I have.

I've compared bboot output from using pegasos rom with my manual forth patch:



To the same through bboot:



Unless you can spot anything, the only thing I could really see was that the command for bus 0:0.0 was 0 when using pegasos firmware and 7 with bboot. In addition, we know we are adding an empty assigned addresses property when there are no addresses.

I modified my bboot to match the command on PCI bus 0 but it didn't change anything:



I did also do a further test with the empty assigned addresses removed just in case this was confusing OS4 in some way. Again, no change.

At this point I'm not really sure where else to look!

@walkero

Yay!

What a great developer!! Only on an Amiga!! You fixed it
without even doing anything!

;D

PJS

@kas1e

Quote:

Sound like does not do it recurseivly, I think it only does it as if it was a simple list.

https://www.youtube.com/watch?v=j9yL30R6npk

@All

So tried to boot morphos with adapter and RadeonHD in, just enabled for their kernel logging of PCI , and that what i have in output:

for bridge:


And for RadeonHD inserted into the bridge (both display and audio):

Display:



Audio:



So Morphos's kernel surely can see RadeonHD as hardware in the log, pointing out that hardware related it ok. Bridge works, RadeonHD in it can be seen from other OS.

Now we need to understand : what problem OS4 kernel have to see it as hardware (i didn't mean working drivers or anything currently, just why it did see bridge, but didn't see what inside of bridge).

Maybe OS4 do see them, but failed to do something, and so we have no logging about ?

Will be interesting to find an app kind of Randger/Sysmon for morphos, to see if from the OS side it see the RadeonHD from bridge too, and not just log the scanning pci bus details..

@sailor
Quote:

So it works as hardware, Radeon drivers even see hardware through that bridge, it just was issues with driver. But hardware were visibly then.

But maybe it was 8111 version of chip, and 8112 have new issue ?

@All

Got power-adapter riser today : tried and it change nothing. The same i can see card in OF, but kernel simple skip it. So this is not the power issue for sure.

Also tried to boot without AGP card in at all : no luck, it just comes to the time when driver should find a card, and "no graphics card found" from graphics.library or so.

So, while i waiting for another bridge to arrive (it will take another 10 days), i will try to boot from Morphos and Linux, so to see, how they see it (and if they at all). By that we will know at least if morphos or linux can see that RadeonHD card in, as OF see it.

Did anyone know what software on Morphos list all the devices like Ranger/Sysmon on os4 ?

@MartinW

That's not entirely true because I've got a request to support the X1000 as well from a X1000 owner. So apparently there was room for improvement.

@walkeroQuote:

I will try to break their result. We have to thank for this great game. I have no time now unfortunately I have to play BreakHack

@walkero

agreed

I agree to keep this competition for the whole of August. And to set the target a little bit higher, here is my score from today's game




Thank you all for playing Breakhack

@MartinW

You're a nice guy, I'll keep an eye on you

As soon as your x5000 has arrived and you have set up an AmigaOs4.1 system and all that entails I would appreciate if you could give some feedback on how things are going with this machine, it would be interesting to know.

@Maijestro

Quote:

When it works, it should work very well. I used to run all my Windows games in a Windows VM using GPU (and USB) passthrough. Ideally there will need to be ways to switch monitor inputs and keyboard / mouse (or pass them through too). It's all possible but obviously needs extra work.

Of course, I agree that OS4 drivers is also a nice way to go and I'd see the benefit there too on my laptop.

Quote:

I am part of a team that has created a sort of game engine but it was never completed. I intend to look to se if it could be brought to OS4 and maybe the goals re-aligned a bit so it could be completed. No public info yet and potentially may never be.

@MartinWQuote:

To be honest I don't think much of this GPU passthrough story under Qemu. Because this setup is very heavy and not user friendly. A suitable driver for this emulation would be far more effective.

However, the information was very helpful for real Pegasos 2 hardware where it might be possible in the future to use RadeonHD and RX cards across bridges, even if this hardware is very old they would be up to date.

You contributed a lot and did it really well and I know how much time testing alone takes, I've been dealing with the Qemu emulation and AmigaOs4.1 for a year when I started testing Qemu was on mine Machine completely unusable. No sound, no network, broken graphics etc.

Congratulations on the purchase of the x5000, maybe you will also develop some software for AmigaOs4.1 in the future. I can well imagine that with them....

@walkero

while playing today I go a DSI Grim Reaper which I PM'd to you so as not to clog this thread

@VooDoo

well we started late this month so to be fair to this great Rogue game we should play this for August too so you don't miss in on the fun

Unfortunately, at the moment Qemu is never going to work properly on my Mac Mini. The sound doesn't work with my USB Audi Interface and I don't want to route all the sound through the Mini's internal speaker to get round it. This is kind of a known thing. At one point Qemu couldn't even start a linux VM as it would kernel panic and shut off prior to login. Switch off the audio interface and it was OK. This was "UTM" but I believe it was Qemu behind the scenes.

Qemu is fine on my laptop for a bit of tinkering about but the GPU is the sticking factor there. And not the resolution, 1440x900(x2) is the native resolution of the screen but developing games is a non-starter.

So, the GPU passthrough stuff is a bit of fun to play about with but that will reach a pause when my X5000 arrives as I'll need the case the "passthrough machine" is in, not to mention the GPU.

@geennaam

Yes, I thought the one on Enhancer was for X1000. Let's face it, if that wasn't the case then there never would have been a reason to have yours

Well, whatever your reasons, I hope you're able to bring it back some day soon. I will keep the Audigy FX since it wasn't much money but in the meantime after speaking to Amigakit today I ordered a CMI8738 based card off Amazon.