@Templario

for sure it's all about having fun and trying different games you may have never played before or thought you wouldn't like for some reason then finding out hey this is pretty cool

@sacc-dude

My graphic card is an ATI Radeon RHD5450 as shown on a Morphos utilitie.

I would go to AmiWest with closed eyes,that could be a dream for me,but in reality I have little money

And another issue is that Fienix doesn't accept well my passwords and if I enter it is unusable

@AmigaOldskooler
The important thing is to participate.

@kas1e
Quote:C library printf(), at least the newlib one, is no "problem", but the OS printf() like functions (IDOS->Printf(), IUtility->SNPrintf(), IExec->DebugPrintF(), etc.) are more or less all based on IExec->RawDoFmt() which is replaced (SetMethod()) by locale.library when it's started with (something similar to) ILocale->FormatString() which uses a Hook for the putCharFunc and you should get a CallHookPkt() call for each char.

Quote:That's normal, debug output writes one char after another to the serial port, and if there are several tasks with debug output at the same time and task switches happen you get a mix of them.
Maybe using something like
in the patch and Forbid()/Permit() around the stack trace DebugPrintF() could help.
You still get a mix of different debug output, but at least complete lines for each task and not chars from different tasks in the same line.

@ktadd

It's always nice to read the first experiences on a new system... let us know how the baby goes...
and we're also interested to know how our MPlayer will runs!

Fair enough..

Knowing the graphics card is important.
Hummm, sound old? what is the number?

If it is a RadeonHD type will work better with CD install as it has driver for HD

If the card is RadeonRX, we have to make some changes.

So you are in the EU,

come to AmiWest for vacation! I'll still help you with getting your X5000 working well

Michael

EXTRA read Epsilon World setting up X5000
https://www.epsilonsworld.com/search?q=x5000

@balaton


Quote:

I have also observed this behavior compared to Qemu 8.1 to Qemu 9 it has become slightly slower, you know that I like to test it with Quake as a benchmark and here I get 29.2 FPS (Qemu 9) with 8.1 it was 31-32 FPS always tested with the fastest session which always leads to the same result in speed.

Which commit has slowed down Qemu 9 will be hard to check there have been too many changes and I don't want to find out because it's still very fast and I'm not arguing about 1-3 FPS I think what is really missing is a better FPU emulation.

@All
Yep, thanks, deal with now, soo !

There is the output of all CallHookPkts with their stacktraces, when i just run simple hello world (no CallHookPkt calling from test case, just hello world via casual printf() from libc):

https://kas1e.mikendezign.com/aos4/tra ... ace_single_run_printf.txt

And there is output when i run binary with pure usage of "empty" CallHookPkt() call:

https://kas1e.mikendezign.com/aos4/tra ... ingle_run_callhookpkt.txt

Almost no differences by amount of calls, +5-6 in case of CallHookPkt() test case.

And one more output i grab for 10 seconds when i do nothing few seconds, then clicking around by mouse, and collecting _all_ possible CallHookPkts() from system (and that include and processes, and tasks and whatever else FindTask() can find):

https://kas1e.mikendezign.com/aos4/tra ... s_of_all_callhookpkts.txt

(dunno how to catch interrupts as well ?)

What curious me seeing those outputs is:

1). Everywhere i see [LIBS:locale.library] Offset: 0. Wtf ? Involved but not used ? Broken "offset" entry for stacktrace ?

2). As i can see, offsets in the kernel, dos, and elf.library practically the same always for each stack trace, mean it's some very commonly used functions , is there a way to get a picture of what ones ?

Then for sake of compare how many pure varargs CallHook() functions is used, i add patch for CallHook() too, and there just collect all the task/whatever FindTask(NULL) find in, and can say that when one run simple test binaries from shell, no CallHook() involved by system. But if i let's say spawn in console new tab gadgets, i have that:



When i choose "open" volume via RMB menu on the volumes icons, then it also run CallHook() one time (just one time too):



So seems that at least CallHook() didn't used by system very often (a very little as far as i can see, but still).

Which is massively used, it's CallHookPkt() as expected, but what is unexpected, that OS4 have pure CallHook() in utility.library at all, and it wasn't very well documented everywhere, and more of it, before it was in amiga.lib in old times (so was a linker function) and now it still used in few bits of system, go figure why if almost everything is on CallHookPkt() already..


@Joerg
Btw, when i tried to use the same "signal" method but for all the tasks/process in the CallHookPkt, i.e. just like this:



Then stacktrace massively overwrite other outputs (debugpritnf for name of task and amount of calls). Is it expected that it didn't work when different tasks involved, and not a single one like we did with signals ?

Quote:

Nice reading, tnx for the update. It is very useful for new a1222 users.

@TheMagicSNQuote:

Hvala na ažuriranju. Čekam Sin port...i naravno volio bih znati više o tim tajnim projektima :D

@joerg

EUAE has built in debuger, so if want to freeze a 68K program or something you can use EUAE for that. EUAE’s built in debugger is not unlike action replay.

@TheMagicSN
You can get similar debugging features on AmigaOS 3.x/m68k by installing and using about 10-20 debugging tools (Sushi, SegTacker, MuGuardianAngel, MemTrace, EatMem, etc.), but even with all available AmigaOS 3.x/m68k debugging tools installed you still get less information than on plain AmigaOS 4.x ("just" (Grim)Reaper) without using any additional debugging tools like GDB, Spotless, etc.

May 8, 2024 update of ktadd's Amiga NG Blog.
A1222 Plus up and running. What now?

@davec555

GrimReaper ;)

The stack trace is great also
that on most crashes it does
not just reboot. On 68k no
stacktrace and often instant reboot…

@davec555

Grim Reaper is good debugging tool, the stack trace feature is really useful
a rs232 serial cable is also useful, if game or program crash while doing intuition lock, or bitmap lock, or some other lockup.
Spotless is nice debuging tool as well.
DumpDebugBuffer command.

@white
C:BootLoader is only used on classic Amigas/WinUAE.

I'm not sure if a SWAP partition is usable on a QEmu Pegasos2 (with -m 2048) at all. Unless something radically changed in AmigaOS 4.x in the last 20 years only the first 2 GB of the 32 bit virtual address space are usable for RAM (incl. SWAP partition), the upper 2 GB are used for the PCI(e) address space.

A real Pegasos2 is AFAIK limited to 1 GB RAM and with a SWAP partition you can extent it to 2 GB.

On other systems more than 2 or 4 GB physical RAM can be used with the ExtMem feature, but from https://wiki.amigaos.net/wiki/Exec_Extended_Memory
Quote:

Quote:As long as you don't change anything in other partitions (moving, resizing, etc.) just deleting the SWAP partition is no problem.

What tools do you use to debug with on OS4?


@TheMagicSNQuote:

@joerg

typing error I meant:

C:BootLoader COMMANDLINE "NoDiskPager"

@Kas1e

Bits might not be so obvious, for some who has coded Javascript, or never learned anything about digital processing.

bits are in order: (highest) 31 to (lowest) 0, importent when want to shift bits right or left.

just like you have 1000's, 100's and 10's and 1's in the descimal system.
it's place in binrary number thats set to active or 1, 0 is not active.



bit 0, if 1 its on, 0 is off, if ON it has value 1 in decimal system
bit 1, if 1 its on, 0 is off, if ON it has value 2 in decimal system
bit 2, if 1 its on, 0 is off, if ON it has value 4 in decimal system
bit 3, if 1 its on, 0 is off, if ON it has value 8 in decimal system
bit 4, if 1 its on, 0 is off, if ON it has value 16 in decimal system
bit 5, if 1 its on, 0 is off, if ON it has value 32 in decimal system

And so on.. the combination gives you any decimal number.

So when we taking about the signal it has value, bit it has also location in binrary number, this is the bit.

if more than one signal is set, then more than one bit is set, this is why you are geting a different value, when you’re reading the state of the task.

Tested few games, with Sam 440ep Flex using Radeon HD 7750.
https://youtu.be/MWPsmwVkjsM


Cro-Mag Rally
https://youtu.be/AYT4jtwsY1Q

Otto Matic
https://youtu.be/l4z_l8uEXns

Steps to Required to make Radeon HD 7XXX work.

1. Update UBoot. UBoot 1.3.1g 04-Dec-2020 updater.
2. Get transparent PCI-PCIe bridge, with a P17C9X chip. It supports 66mhz bus.
3. Get PCIe x1 - PCIe x16 riser adapter.
4. Get compatible Radeon HD card.
5. Get A-EON's Enhancer Software 2.2 and install it.
6. Add text MODULE Kickstart/RadeonHD to SYS:Kickstart/kicklayout file, just after MODULE Kickstrat/PCIGraphics.card.
7. Install Hardware, it just should work now.

NOTE. Brige card with PEX 8111 chip worked without a problems. It said it shouldn't work with Flex. https://youtu.be/VqkGFlqje6o