How do I get Warpd 3D SI and what are options for a Sam 440ep Flex with Radeon HD7750, Enhancer Plus installed?

@Sailor, have you tested these with Flex?

@All

Currently , when i want to control Sam460 via serial from the putty (i mean typing symbols on the terminal instead of on the SAM's keyboard), i should physically detach mouse and keyboard from. But, is there are some variable/environment which i can set, to avoid detaching of keyboard/mouse physically ?

For example, on pegasos2, when i want to have control over terminal and not over peg2's keyboard, i set "setenv output-device ttya", and then use putty without "flow control" to make it works. And to give control back to peg2's keyboard i set it back like "setenv output-device screen". But this is openfirmware, while sam460 is uboot based.

So, question is : is there any environment of this kind like on peg2, which when i set, i have control by terminal of my sam460, without detaching keyboard/mouse from them ?

Setting "stdout=serial" of course only mean to threw output to serial instead of screen, but not about ability to type from serial.

Thanks!

@joerg
Quote:

That explain all those "locale.library" string in the stack trace then, strange only why with offset:0 ?

Quote:

Yep, that better, but still not very readable as it still mix of different debug output. If use messages with all those processIDs is it possible to deal with ?

@Hypex
Thanks, will try it later

@MamePPCA1

Quote:

I imagine that's the case for everyone else who bought an X5000 as well.

@kas1e

Quote:

Just realised why. I was going to test it myself before rereading this. The TaskID and ProcessID are different.

The TaskID isn't exactly an ID and is simply the Task pointer. But because AmigaOS shares lots of pointers it uses it as an ID. The ProcessID, which is a newer addition, actually assigns an ID to a process. Maybe they tried to clean it up and make it more like a modern OS that does use a process ID.

Somehow, although it's obvious now, I had missed that. You've got it working again now. But for fixing that one, your ProcessIDMessage object will need TaskID as well, which is simply the Task or Process pointer. I did notice your ProcessIDMessage only had ULONG and that explains it. Whoops.


So global:


In Patched CallHookPkt:


Optional local fix avoiding allocation overheads:


Main routine is then:

@joerg

Nah... use mutex instead, around debug printf, mutex should be forbid() free..
at least that was what we were told.

Using forbid has no advantage,

imagine a different task that print half a line without using forbid, now your task invokes forbid() and DebugPrintF, and Permit(), the other task, will continue after permit(), and the text will look bad.

perhaps patching DebugPrintF so it uses a mutex can do the trick, then the lock becomes global.

Hey Mame,

Well that card is older, but it works on OS-4, Morph and Linux.
And it is compatible with the CD install.
this makes things (more) simple.


Try something and remove the hard drive to protect the info
Then just boot from the cd.
You can learn how to OS-4 from the cd boot (smile)


My response to your Fienix question is the same..get a hard drive and Make your life easier (But Since you can run it from the usb stick..even if it's really slow compared to a hard drive.

Just follow the excellent instructions (see Fienix page) that you got when you bought or downloaded the image. I bought the usb version.

BTW, did you look at Epsilon site (lots explained)

Save some cash (no lattes) and get that newer hard drive

Edit:Post moved to a separate thread

https://www.amigans.net/modules/newbb/viewtopic.php?topic_id=9542

@ktadd

Love it keep em coming Love the feelings you experience when setting up a new system (both good & bad) and that nice soothing feeling when you finally get it set up just the way you like it

How about we pick a mission in BOH and we can post our times to complete it with the fastest time taking the win.

BOH-RETREAM

@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:

Thanks for the update. I'm waiting for the Sin port...and of course I'd like to know more about those secret projects :D