Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
126 user(s) are online (83 user(s) are browsing Forums)

Members: 0
Guests: 126

more...

Support us!

Headlines

Forum Index


Board index » All Posts




Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


@joerg
Yes, i running on radeon9250 to see output. But then, i currently didn't try to load RadeonHD driver, i currently trying to find : why kernel didn't see device at all. So i didn't see it in ranger, and so on as hardware.

All this "BOARD=PIGraphics.card" stuff is probably for later stage, and more of hi-level, to have driver works, etc. But firstly, we need driver to know that there any hardware related , so driver can start at least talking with harware

Currently, it very much looks like that the kernel simple didn't see it and that all... If you check my debuglevel outputs, you can find that after that:

[_SetupCapabilitiesEnumerating capabilites of device 0x00:0x06.0x00 (@0x6FFFE80C)
[
_SetupCapabilitiescapOffs0x40  capID0x1 (Power Management)
[
_SetupCapabilitiescapOffs0x50  capID0x5 (Message Signaled Interrupts)
[
_SetupCapabilitiescapOffs0x60  capID0x10 (PCIe)


Nothing else happens in that terms. Kernel didn't tried to even talk with hardware, like there is none.

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Just can't stay away
Just can't stay away


@kas1e
Looks like you are using 2 Radeon cards.
Did you modify your DEVS:Monitors drivers for that? With a single one it should work automatically, but for using a 2nd one using something like a "BOARD=PCIGrapics.card" ToolTypes is required instead.
(Or something similar, I may be mixing things up and I never had such a setup, better ask Hans for details.)

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


@joergQuote:
joerg wrote:@Maijestro
Quote:
A reliable CPU task manager under AmigaOs4.1 does not exist at the moment
If all you need is something like top on Unix my "top" and Capehill's "tequila" should be reliable enough.


"Tequila" I have already used under AmigaOs4.1 it works well, but it is not perfect, but it does not have to be, because it is still being worked on.

"Top" I have not yet tried under AmigaOs4.1, thanks for the tip.

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


@Balaton
Running debug kernel of different levels with attached bridge and radeonHD in it, together with added RadeonHD.chip to kickstarts and kicklayout, so just in case it may try to loads someday.

As far as i see from logs, RadeonHD driver even didn't tries to loads up, like found nothing (that expected, as even Ranger didn't see card as hardware attached).

Anyway, it case it will be of any help:

full boot with bboot debug-level3:
https://kas1e.mikendezign.com/pegasos2 ... ot_bboot_debuglevel_3.txt

full boot with bboot debug-level5:
https://kas1e.mikendezign.com/pegasos2 ... ot_bboot_debuglevel_5.txt

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


@balaton

kas1e is testing on a real Pegasos 2. I am testing on QEMU with pass-through

Tried to pass-through the host bridge but that doesn't work. I cannot attach a VFIO kernel driver to the host bridge. So it looks like that you can only pass through endpoints. I do not have regular PCI slots in my system. So an External PCI to PCIe bridge like kas1e is using is also not possible for me.
And cascading bridges (pcie to pci + pci to pcie) is a bit too much.

If 64bit bars were the issue then he should have seen at least the two 32bit bars. Like I do on QEMU with amigaboot.of and no forth script.
Since he sees only the bridge within amigaos4, it looks like the first issue is a scanning issue. (or information is not passed on to amigaos4)

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


@Maijestro
Quote:
A reliable CPU task manager under AmigaOs4.1 does not exist at the moment
If all you need is something like top on Unix my "top" and Capehill's "tequila" should be reliable enough.

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


@balatonQuote:
balaton wrote:@Maijestro
Quote:
At least the numbers show that it is different, shouldn't it always be the same?

It should be about the same if the same thing has been run in the guest when you collect these statistics so if you always do the same and get the stats at the same point then difference shows something if they are from runs where different things happened since starting QEMU then they don't show anything.

PPC interrupt 8 is syscall when guest executes sc instruction which is done when something is calling AmigaOS services so maybe something is running in guest that does more stuff sometimes? Is there some task manager where you can check what task is using CPU time and compare that?


Thanks for the explanation, the test on both sessions always runs the same. I start Qemu Boote AmigaOs4.1 until Workbench is available and then I start Quake Timedemo1 and look at the benchmarks. Good session 32 FPS, bad session 16 FPS. So I can also determine which session with Qemu is bad and which is good. So I could assign IRQ and JIT info to the respective sessions.

A reliable CPU task manager under AmigaOs4.1 does not exist at the moment, but should not be necessary since both Qemu sessions run exactly the same.In the test nothing else is started like AmigaOs4.1 up to the Workbench and then directly Quake Timedemo1.

Edit: Believe me, I have tested this countless times. It's like when I noticed that the sound output under MacOs with Qemu and AmigaOs4.1 runs too fast, this error was also hard to reproduce until I recorded it on my handy

In a bad Qemu session I also notice that I can stream YouTube videos in 720p with MPlayer, but the FPS numbers collapse and the video plays slower, as if I had a good session with Qemu where Quake with 32 FP benchmark is available.

Since no one has tested it further, I'm not sure if it's only a MacOs problem. Or if it is due to the Mac M1 CPU which makes it sometimes faster and sometimes slower.Or maybe it is a problem of Qemu.


Edited by Maijestro on 2023/7/25 19:31:55
Edited by Maijestro on 2023/7/25 19:36:23
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


@balaton
Quote:
PPC interrupt 8 is syscall when guest executes sc instruction which is done when something is calling AmigaOS services so maybe something is running in guest that does more stuff sometimes?
AmigaOS doesn't use sc, nearly the whole OS is running in user mode.
(Of course not 100% of it, a few things need supervisor mode in AmigaOS as well, like changing MMU tables or anything else requiring supervisor mode, or even hypervisor mode on 64 bit/POWER CPUs, for some special PowerPC instructions, but that are very rare cases).

Go to top


Re: First user's report of new Intel HD Audio (Azalia) driver by geennaam
Not too shy to talk
Not too shy to talk


That’s a shame. I just ordered an Audigy Fx


Amiga x5040 ı 16GB ı RX580
GB-A1000 060@100,
A1200 PiStorm32-Lite CM4
Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


@Maijestro
Quote:
At least the numbers show that it is different, shouldn't it always be the same?

It should be about the same if the same thing has been run in the guest when you collect these statistics so if you always do the same and get the stats at the same point then difference shows something if they are from runs where different things happened since starting QEMU then they don't show anything.

PPC interrupt 8 is syscall when guest executes sc instruction which is done when something is calling AmigaOS services so maybe something is running in guest that does more stuff sometimes? Is there some task manager where you can check what task is using CPU time and compare that?

Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


@balaton
Ok will try increase debug level of kernel (i am currently on debug kernel level 1 always).

Quote:

Does the card connected to the bridge show up in Ranger just missing BARs?


If you mean real pegasos2, then it show no video card at all, be it running with bboot or with amigaboot.of

BTW, should to add , that i am not running any HD driver currently, all i do is via bridge connected RadeonHD card, and then boot pegasos2 over radeon9250 sitting on AGP, to see if Ranger see video card at all. So we even didn't reach a point that kernel see a hardware, so probabaly to early to worry about RadeonHD driver at all (just asking as may miss something)

@joerg
Did you aware of what kind of debug level for debug kernel i need to set, so to have some important bits from the kernel as of when it starts to scan devices, why it failed, etc. ? DebugLevel 3 should be enough imho ?

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


@geennaam
Quote:

On a real Pegasos2, a bridge in between is seen by the system. So if the kernel has an issue with scanning behind bridges then you are out of luck.


Does the card connected to the bridge show up in Ranger just missing BARs? If so it's probably a problem with 64 bit BARs. If it does not even show up then it's a problem with bridge. The AmigaOS log would give some more details on this with high enough log level. I've found the max you can go is 9, above that it would crash on bad debug code but maybe less is enough to get logs about device scanning as in higher levels memory management logs are too verbose and make too much noise. Experiment to find a level that doesn't have too much logs but still show [ScanDevice} messages.

Quote:

But let's not draw any conclusions until you have tried a power inserter and the pericom bridge.


It's unlikely to be a power problem if the Driver doesn't even talk to the card. One other thins that could cause problem if the card ROM needs to run and I'm not sure pegasos2 firmware does that for cards behind a bridge but I also don't know how to find that out. If you connect the card to QEMU with pass through and get errors from firmware when running BIOS then if you connect the same card on real pegasosII with briege I think you should see the same errors so that could confirm if the BIOS runs or not.

Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Just can't stay away
Just can't stay away


@geennaam
Quote:
So if the kernel has an issue with scanning behind bridges then you are out of luck.
I doubt it even tries to do anything like that, the kernel just uses whatever it gets from the firmware (U-Boot, CFE, SmartFirmware).

Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


@geennaam, @kas1e
You're trying to find problems with omitting important information so it's hard to debug this way. We now have BBoot and firmware output from real pegasos2 and found that pegasos2 firmware sees the card but we also know that pegaosos2 AmigaOS kernel won't see 64 bit bars so BBoot tries to change those to 32 bit BARs (this is when you get Truncared 64 bit BAR message). BBoot currently doesn't go down in the bridge so it won't do that for the card behind the brige, I'll need to find out how to do that. To see what AmigaOS sees from all this a debug log with kernel.debug and some higher loglevel where the [ScanDevice] or what it's called messages are logged could help to see where it fails.

@geennaam just posts way too little info to even follow what happens. I'm not even sure which cards he's testing and if they work or not so I'll just let you figure this out alone unless you can give more details. The difference in that case is if you boot with -kernel bboot then bboot will configure PCI devices so it will assign addresses and fix BARs itself and additionally it will also fix unset interrupts. All these fixes are logged in the BBoot output but since you haven't posted those I can't tell what it did. BBoot still could not handle a bridge in this config but since you're only passing through the card and not the bridge it also does not have to as the bridge is handled on the host. To get the same config as @kas1e one could pass through the bridge and use -bios pegasos2 firmware which would emulate what happens on real hardware more closely. Doing that and getting info mtree and info pci after AmigaOS boots might give some more info on what's set up and what may be missing.

I hope tha above makes sense, please read it multiple times if not clear for the first read as I don't have time to explain it in more detail. I'll look at extending BBoot to handle bridges but that would take a while.

Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


@kas1e

On QEMU, every VFIO device is passed through without any bridge that might be in the host system. So the VFIO GPU is directly attached to a host bridge within of the emulated Pegasos2 as you can see in the screenshot above.

On a real Pegasos2, a bridge in between is seen by the system. So if the kernel has an issue with scanning behind bridges then you are out of luck.

But let's not draw any conclusions until you have tried a power inserter and the pericom bridge.

Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


@kas1e

I was only talking about host bridges.

Everything starting with 00 is part of the PCI bus.

Everything starting with 02 is part of the AGP bus.

Somehow the AGP bus on QEMU starts with 01. But I guess this doesn't matter.

Here's a screenshot of Ranger on QEMU with the RX560 connected to the "AGP" bus.

Resized Image

Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


@geennaam
So, card detected by randger with both amigaboot.of and bboot.. What did it mean then .. That on real pegasos2 something else should be done about ?

Maybe that the result of differences to be "behind bridge" and "as it" ?

Btw, when you say:

Quote:

With the assumption that you already use the PCIe power inserter, it looks like the kernel is not able to scan behind your 8112.


Currently, i do not have power adapter (it will arrive tomorrow), but then, if it was power issue, it shouldn't be seen in OF too ? Or os4 kernel doing something like check if not enough power somewhere, then not add this device to the list of devices even if they work in OF" ?

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


@balatonQuote:
balaton wrote:@Maijestro
If in doubt read documentation: https://www.qemu.org/docs/master/system/monitor.html

Just type info jit or info irq in QEMU monitor. You can redirect the monitor to stdout with -monitor stdio in which case leave out -serial stdio or you can use -serial mon:stdio to multiplex both on the same window.


I did the test with info jit and info irq at a good and bad session.

Info Jit bad session:

(gemuinfo jit
Accelerator settings
:
one-insn-per-tboff
Translation buffer state
:
gen code size
121540068
/1073724416
TB count
186886
IE aug target size
23 max
=2048 butes
Th aug host size
313 butes 
(expansion ratio13.2)
cross page TB count 0 (0%)
directjump count
104199 
(55%) (2 jumps=87643 46%)
TH hash buckets
99012
/131072 (75.54head buckets used)
TB hash occupancy
34.17
avg chain occHistogram: (o,10Irdà rte rûärturdar
turtulE90
,1001%
TB hash avg chain
1.019 buckets
Histogram11rdêrûurâu13

Statistics
:
TB flush count
0
TB invalidate count 2775
TLB full flushes 0
TLB partial flushes 505722
TLB elided flushes 5143430
[TCG profiler not compiled]
(
qemu)


info irq bad session

(gemuinfo irq
IRQ statistics 
for 7447_01.1-powerpc-cpu:
24844
4
5081
7
37
8
3044952
10
70489
73
27
IRO statistics 
for isa-18259:
012
1
78
2
5556
9
2196
12
2096
14
2048
15
279 
(qemu)


good session info jit:

(gemuinfo jit
Accelerator settings
:
one-insn-per-tboff
Translation buffer state
:
gen code size
122601716
/1073724416
TB count
188792
TB avg target size
23 max
=2048 butes
TB avg host size
311 bytes 
(expansion ratio13.1)
cross page TB count 0 (0%)
directjump count
105220 
(55%) (2 jumps=88483 467)
TB hash buckets
99418
/131072 (75.85 head buckets used)
TB hash occupancy
34.45
avg chain occHistogram: (o,10Irdà rte rûärturdar
turtulE90
,1001%
TB hash aug chain
1.019 buckets
Histogram11 dêrûurâul3

Statistics
:
TB Flush count    0
TB invalidate count 3074
TLB full flushes
.  0
TLB partial flushes 491380
TLB elided flushes 5042828
[TCG profiler not compiled]
(
qemu)


good session info irq:

(gemuinfo ira
IRQ statistics 
for 7447_01.1-powerpc-cpu:
24850
4
4515
7
41
8
2184883
10
29055
73
30
IRO statistics 
for isa-18259:
011
1
70
2
5270
9
1503
12
3216
14
2032
15
144 
(qemu)


The value of irq 8 and 10 looks suspicious, because there are big differences here. But I don't know, that's just a guess. At least the numbers show that it is different, shouldn't it always be the same?


Edited by Maijestro on 2023/7/25 18:35:03
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Quite a regular
Quite a regular


@kas1e

amigaboot.of:
- RX 560 is detected by Ranger
- Only BAR4 and BAR5 are visible in Ranger.
- RadeonRX driver was removed from kicklayout because driver will fail due to missing BARs


bboot 0.4:
- RX 560 is detected by Ranger
- BAR0, BAR2, BAR4 and BAR5 are visible in Ranger.

Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Home away from home
Home away from home


@joerg
Quote:

Unless I understood something wrong the Marvell has no bridges, just 2 PCI busses.
The Articia-S (MAI Teron CX/PX/Mini PReP reference/evaluation boards, AmigaOne SE/XE/µA1, and Pegasos1) has 2 busses as well (first one, 0.0.0, directly connected to the onboard ethernet chip, the VIA southbridge incl. PATA, USB, etc. and the 3 PCI33 slots, 0.6.x-0.A.x), but the other one (0.1.0) uses an internal PCI-to-PCI bridge for the AGP and PCI66 slots (1.0.x + 1.1.x).


At least in Ranger on Peg2 i do have many labels as bridges (which can be just name-labeling of course). That how it looks like:

Resized Image

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top



TopTop
« 1 ... 376 377 378 (379) 380 381 382 ... 7270 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project