@sailor
Your latest article on overclocking the G3 is really good. Well done there. I am almost tempted to try to push mine a little bit.

@smarkusg
That initial post by @kas1e was written more than a year ago when AmigaOS did not run on QEMU pegaos2 yet (at least not in a usable way) and it does run slower on sam460ex due to some issues in PPC440 emulation. I've found the issues earlier this year when did profiling to try optimising it a bit but did not have time to try to fix it yet. But since then we've made aome progress with pegasos2 which is still not fully there but should be more usable now so it's more the background or view point changing than opinions.

Yes communicating in English with it not being native languege for most people can be difficult so just wanted to clear any misunderstandings.

And for Open Firmware fans "may the Forth be with you".

@kas1e
Hmm, then I'm puzzled how to actually access the AGP port on pegasos2. I think Linux just uses rtas for that, not sure if AmigaOS does the same. The openfirmware.resource in kernel mentions rtas but did not see calls from it so don't know what it actually does. At least one change now that BBoot will not try to write the wrong device (no ! value after ffffffff values) so it should be safer against breaking somehting but I'd still like to find out how this works as that may be the reason why pci.0 did not work with pass through. Any ideas anyone?

This is OT for this thread really so if this goes on for more than a couple of posts I'll start a new one.

Performance on the MacBook Air is poor. I mean, general opening windows, copying files, using the internet etc. is fine. Break Hack needs the sound to be disabled to get reasonable performance otherwise it's too slow to use really.

Interesting that you mention LiteXL. I discovered that the other day. At the moment I am experimenting with a number of machines:

- Intel i7 6700K with GPU passthrough. Purely testing.
- Mac Mini M1. This is my main machine.
- MacBook Air 13" Base model (7core GPU, 8GB Ram, M1 chip)

The MacBook air was bought for the winter months really where it's too cold to do much other than sit in the living room in front of the fire. Anyway, I digress.

I installed Lite XL on the MacBook air. It takes a while to open and when it opens it is just a grey screen. On the i7 machine with HD5450 card it works but screen refresh is too slow for it to be usable. The only machine that I have installed Enhancer 2.2 on is the i7 with GPU passthrough. The two Mac's are on FE Update 2. Maybe this has something to do with it?

On all of these machines I use SFS/00 for the boot / system partition. I've never had a problem booting from this and didn't know otherwise. I did just notice that the Work partition is DOS/07 whatever that is. I'll swap that out in a bit for SFS/02 and see if it improves performance.

Ultimately I intend to settle on an X5000 plus one Mac, probably the laptop, if it's good enough to do some development from the sofa.

@HansQuote:

If you use Qemu on Windows, there is also ready binary on https://qemu.weilnetz.de/w64/ Qemu 8.1 RC0 is already available there.

It may not change much that it is slow on your machine, but Qemu 8.1 includes some optimizations. Also the assignment of the correct CPU is omitted.

That Qemu Peg2 AmigaOs4.1 takes over a minute to boot on your machine is a bit unusual, compared to my machine which takes about 4-6 seconds to load AmigaOs4.1 and is fully usable after 10 seconds.

Such huge differences I would not have expected.

@MartinWQuote:

This is what my command line looks like for Qemu 8.1 RC0:



I have no compare how it runs on other machines except the videos from @White where it also seems to run fine.

@smarkusg uses Qemu on a MacMini M1 and it runs great on him too. Maybe it is also due to the correct setup of AmigaOs4.1, I installed AmigaOs4.1 the way the developers told me to. All partitions use SmartFileSystem and only my boot (kernel) partition uses FastFileSystem.

Also I can confirm that older SDL software cause problems. But this refers to SDL 1.x.x since SDL2.x these problems do not exist anymore.Some things have already been adapted by the Amiga community:

MilkyTracker, ScummVM, BreakHack, LiteXL, Mplayer, E-Uae

Of course everything that requires 3D acceleration and 32 bit windows does not work with Qemu AmigaOs4.1 Pegasos 2

Have you tried Qemu on your MacBook Air M1, it would be interesting to know how it runs.

@balaton

Quote:
Core i7-6700HQ @ 2.6 GHz. I've got 24 GB of RAM, so there should be no issues with running low on RAM.

Qemu 8.0.0.0 downloaded from the QEMU website.

Hans

@balaton
Quote:

There is output from bboot-test1:



All works as expected after boot

@balaton
Maybe you misunderstood something, or I misspelled something, or didn't share my thoughts....

@kas1e once wrote that he prefers WinUAE. He had some concerns about Qemu.
I hope those concerns are gone, WinUAE is also a very good emulation. I also use it occasionally.


One of the old "amigans.net" forum members recently wrote me a thought (I won't quote who because he may not want me to).

"...amigans.net is such a peaceful haven in the Amiga world compared to other Amiga forums...".
I have no intention of changing that.

So, have a nice day, a peaceful weekend, good health and for the StarWars fans "may the force be with you"...

@Hans
I think designing a common virtio.library to support the communication method basics that can be shared could be rally helpful. The virtio headers are BSD licensed so such library could also be inder a BSD license and thu free to be used in commercial projects as well but keeping the virtio.library open could help different driver writers to share and improve it together. I've considered writing such library before but did not get very far so I can't help much with it but coming up with a standard shared way for this in a shared library would be useful in my opinion.

@Hans
What core i7 version is that and what EQMU version are you using? Is QEMU from a binary or compiled yourself?

@kas1e
Could you please try this new version on real PegasosII?
http://zero.eik.bme.hu/~balaton/amiga/bboot/bboot-test1.xz
It should fix access to AGP card which was showing with all ff values before which also means that this is probably broken in QEMU now so maybe that's why @MartinW could not get a card work with bus=pci.0 so use the default bus for pci pass through for now.

(This is now a pre-release testing version, nothing new for using on QEMU in it and I plan to add more to this for an actual release so everybody else can ignore this, for them it's identical to last released version but will get all ff on QEMU for pci.0 devices, opposite of what's in real hardware I think but that's what should be tested.)

@all
Thanks for the suggestions. Of course it's going to be a trade-off. Especially with budget restrictions.

I don't need the world's fastest AmigaOS on qemu setup, though. Something a good step up from my current Core i7 laptop's performance would be welcome. Booting takes just over 1.5 minutes (from pushing enter on the bootloader menu), and everything feels sluggish.

Hans

@Maijestro

Great to hear you've got a working setup. I'm going to take a peek at Filezilla's source-code because it's the default option for a lot of people.

Quote:
Almost missed this. I suggest anyone considering writing virtio drivers contact me. All virtio drivers have a common method of communicating with the virtual hardware. So, we could potentially share code.

Hans

I just killed a fairy. Wasn't entirely sure I was meant to kill a fairy but it dropped a lot of platinum so what can you do?

(114.62g)




[EDIT]

324.28 gold

@smarkusg


I probably misdescribe what I use.
I use kali on real partition on SSD with dedicated partition that's all.

dual boot with windows.

so simply
ssh (sshd) OpenSSH server
and then qemu with Pegasos2
with AmiCygnix.

that's all

@Maijestro, @smarkusg
Don't understand what you want to convince @kas1e about. He's been helping a lot so far and I think he uses both emulation and real hadware so no need to take sides or fight about anything or try to convince anybody that one way is better than any other. There's enough space for everybody here I hope so just be cool.

My primary goal for writing BBoot was to avoid the need for the non-free firmware for booting AmigaOS on QEMU but I realised that this could be useful for other things as well, such as allowing using so far unsupported gfx cards either via pass-through with QEMU or via bridges on real hardware or also to just boot faster even on real PegasosII so those are also usages I'm happy to support and glad to see if BBoot is useful beyond its original goal to boot AmigaOS without pegasos2.rom. I still want to keep it simple and small so maybe don't want to put in too many features but its usage is certainly not limited to QEMU and I've considered real hardware usage as well when writing it.

@Maijestro

What's your current full command line for Qemu on your Mac? I have a MacBook Air (base M1) just for sitting on the sofa playing about and it's not great. I have a feeling that a lot of your success is simply down to the pure power of your M1 Max CPU?

At the moment we need to drop back to G3 cpu because any of the others have problems with SDL rendering (and an awful lot of stuff seems to be written against SDL). Not complaining here by any means, just wanted to check we're doing the same thing. For me anything GPU related is very poor and not really do-able without real hardware.

@kas1e

You should remember that this is not about improving the Pegasos 2 hardware, it's about the Qemu Pegasos 2 emulation, that it works with real hardware is the result of Qemu, as they mentioned back then that if they ported SuperTux they wouldn't support emulation.

I understand your thinking of course, since everything 3D accelerated runs better under real hardware, but never say never. You just benefit from the Qemu Pegasos 2 emulation and should be open to support it.

Of course the information how things work on real hardware is important to make the Qemu emulation better and if this works on real hardware too.

We should all work together and everyone ultimately benefits. It's not a criticism, just my personal opinion.

@white

>Would you like to try it?

To be honest, I'm appalled by the configuration you describe.
You're running Windows, plus WSL Linux Kali. Plus probably VMware and Qemu.

I'll also be honest with you - I have no intention of installing AmiCygnix for the time being. I hope you can understand that.

I'm keeping my fingers crossed for you and hope you get through it.