@nbache
So I guess I'd better put it this way .
If all the programs included in ES2 are working properly after the UP3 update, don't install anything from ES2.
Also, don’t update using the “updater” from AEON. I hope no one is checking it or running it.
The version for A1222 already includes everything important from AEON... @Emeck, don’t check it unless there’s a program on the list that you need to update or you’ve bought something.

@emeck
Quote:
I don’t own an A1222, but the ES2 comes bundled with it. I think you bought an extra copy unnecessarily.
When you purchased the system, you received a USB drive containing the installation version of the system. It is highly recommended that you make a backup copy of this USB drive.
There have been instances where the contents of the USB drive were accidentally damaged.
The UP3 update for the A1222 itself doesn’t contain many (critical) fixes. The AOS4 system for the A1222 was slightly ahead of the version for other platforms. UP3 brings all system components up to the same version.

If you have the opportunity and need to make a backup—do not back up the system to the same drive/partition. If possible, buy a new similar drive and make a 1:1 copy.
If I remember correctly, you can also make a system backup using a program by @joerg (sorry, I don’t remember the name, I think it’s the AmiDVD player)... there’s a description somewhere on the forum.

EDIT:
One more important note. The system that comes with the A1222 already includes ES2 components.
Some of these components are included in versions other than the clean AOS4 system from Hyperion.
It is not recommended to install the entire ES2 package after updating to UP3. It will overwrite important system files in the “other” versions.

@kas1e
Quote:
I sent you a private message.
Thanks

@balaton
Ranger.
The ‘Gfx Boards’ tab shows total memory and free memory. You can calculate it.
I found it on the installation discs (I'm not sure if it's for all systems) in the ‘Extras’ folder or on os4depot.

@kas1e
Quote:
I have no idea, but I remembered one thing. I think there were two newer beta versions of the firmware for the PEG2.
A while back, a user on the MorphOS forum who had a PeG2 with that firmware wrote that it improved USB performance.

The PEG2 definitely has UHCI USB 1.1. Your post on the Hyperion and lspci forum
https://forum.hyperion-entertainment.com/viewtopic.php?t=5019

@kas1e
Peg2 only has a USB: v1.1 UHCI controller on the motherboard.
By adding this "-device pci-ohci" to the QEMU command line, you “add” an additional USB PCI controller to the motherboard.
It will only be recognized if the operating system supports it.
Just like in this video, where it’s paired with a real PEG2 (at 55 seconds)> https://youtu.be/oE42AX1F2LY?t=46
The video is pretty cool overall. It’s great to see that someone is still playing with a real PEG2 these days.

The PCI-OHCI driver for QEMU has received minor updates for QEMU-11
https://www.amigans.net/modules/newbb/ ... id=159592#forumpost159592

@joerg
Quote:
Most likely, the WinUAE driver would only work with AmigaOS PPC.
From what I can see, the author also wants it to work on both x86 and PPC, covering all systems.
You’ll surely point out that WinUAE uses QEMU to emulate the PPC CPU when running AmigaOS4 PPC on classic hardware (yes, WinUAE uses QEMU, in case anyone didn’t know). But that’s a very old version… very old. I think it comes from QEMU 3 if I remember correctly, and it was definitely stripped down to work properly with WinUAE under the CPU. I have no idea if it also emulates Voodoo.

This emulation QEMU voodoo has come in handy for me twice recently—even though it doesn’t work perfectly.

Example 1:
As you’re reading this thread, @balaton has released a new driver for QEMU (ATI).
I tested it under Sam460ex emulation. It didn’t work. Under QEMU (with PCI passthrough enabled), only the SM501/502 is available.
If I didn’t have the Voodoo driver for QEMU, the scope of troubleshooting potential issues would be very broad.
After verifying that the Voodoo driver for QEMU works on Sam460ex, a possible issue was u-boot. It checks if the connected card is ATI and configures various settings. It’s possible that QEMU (ati) doesn’t work correctly yet on Sam460ex after disabling this, but I think @balaton is already looking into that.

Example 2:
As you know, I have QEMU PCI passthrough with a Radeon card. I also connected an NVMe drive to use as my main system drive.
The system using PCI passthrough is Pegasos2. Here, to start the PCI passthrough itself, you need to use bboot.
“pegasos2.rom” boots on its own, then bboot.fth is launched. It runs Kickstart.zip and boots the system.
This doesn’t happen automatically, so you have to bypass the restriction on booting the Pegasus2 emulation from ROM. Give it the commands… I’ll skip the rest of the details.
By accident, I added a “REM” for the RadeonHD driver in Kicklayout. The system wouldn’t boot. I didn’t have a modified version of Kicklayout where the SM501 driver would also be loaded.
I was in for a real ordeal. Connecting the monitor (My new monitor doesn't support resolutions lower than 800x600) to an X86_64 machine with PCI passthrough. Enabling the Intel card. Launching some X11/Wajland session and running QEMU without PCI passthrough from some system image to rebuild Kickstart.zip.
I hadn’t removed “MODULE Kickstart/3dfxVoodoo.chip” in Kicklayout, so the test was simple.
Booting the system with Voodoo via a remote “VNC" (Available as a QEMU video output option) session, correcting the entries in the running system in Kicklayout for RadeonHD, and rebuilding
Kickstart.zip.

Example 2 is very extreme, but it shows that the Voodoo driver can save your butt

I disagree that the author’s work on the Voodoo driver is unnecessary.
It’s not perfect, but it’s not a waste of time...
It comes in handy in everyday life (for me).

@balaton
Quote:
I corrected the post; it was translated incorrectly—my apologies. It’s not better; it’s actually worse—it’s slow and doesn’t have 3D yet, but it would make installation easier.

@balaton
Quote:
Yes. There is a problem with that. Some minor issues have already been fixed.
The driver isn't fast, but since it's probably the only one under the GPL license, it could be added (created) as a binary patch to the PEG2 and A1 installation discs. After purchasing the license,
you can download the ISO file, add the binary patch (Add monitor preferences), and boot the system.
Any System updates do not interfere with the operation of the system or the Voodoo3 driver.
Even if the Voodoo3 is slow, you could upgrade the system to U3 via updates and then install whatever you want.


One issue is the patch for QEMU. For now, the author is creating binary versions of QEMU (unofficial)
Time will tell how this plays out

@balaton
Quote:
I’ve been testing these options on a few ROMs I have for the RV100 and 7000. The newer u-boot doesn’t boot with `ati-vga` in QEMU-11.
I had a system image for the sam460ex to hand, so I gave it a go.
No one has reported any issues regarding this – perhaps no one ever will. I suspect few people use the QEMU sam460ex emulation.
You mentioned somewhere that the QEMU sam460ex emulation is to be removed. I won’t bother you with this matter.
It’s just worth noting that this issue occurs in QEMU-11 and ati-vga.

@balaton
I tested the ATI (QEMU) driver for sam460 in QEMU. It doesn't work.
Most likely, the newer version of u-boot is trying to initialize the ATI card for its own purposes.
It works with a custom u-boot (where Radeon initialization is disabled).
It also works with an older version of u-boot for QEMU.
But there are still major issues. WB has compositing disabled.
Sm501 and Voodoo3 work correctly.
Here’s a video—it’s easier for me to post a video than to write and post screenshots.
video- > https://youtu.be/IQSzCMMo9Q8

@balaton
I noticed one more small thing.
The memory usage for the ATI card (QEMU) always shows very low values. I think the maximum value was 7MB even when I had 64MB or 128MB allocated.
Even that early Voodoo driver always shows a maximum of 16MB.
The screenshot for the Sm502 also shows the usage.
Maybe this is a silly observation, but is there a lack of RAM for ATI (QEMU)? Maybe that’s why it chokes during “larger” tests.

P.S.
It’s also strange that the values shown by sysmon are in Mb instead of MB. The values themselves are correct, but “Mb” is misleading.

EDIT:
Edit: Here's a screenshot, @Maijestro—it's also max 7MB
https://ibb.co/rRnNMNrh

@balaton
Quote:
Here's a screenshot

@balaton
Quote:
It used to be available for free on os4dpot. Without going into detail as to why... it is currently available as part of the ‘zTools’ bundle in the AMIStore App Store (A-EON shop)
Several other programmes that were previously freely available, such as TuneNet, have suffered the same fate. At present, the situation is such that there are no new updates... just like everything else under A-EON’s control.

EDIT:
As far as I recall, only @joerg managed to update his program recently via AMIStore. The update had been available for several years, but it stopped working after the Up3 update. It is now working properly again

@derfs
I don’t think the AI fully understands what code it’s supposed to generate; here’s a quote from GitHub:
“MorphOS, Linux, AmigaOS 3.x: not yet bootable. The framework recognises their partition types and falls through to a ‘loader not implemented’ message; nothing will load.”
I think the AI is spitting out this status. AmigaOS 3?

@balaton
I ran it again just now for ATI (QEMU) 16-bit
Same Linux system, same guest OS (Peg2 AOS4FE U3), same command-line limit—only the `-display` option was changed.

udostępnij zdjęcie znajomym

The option I added, “vgamem_mb=128”, does not affect the test result. Without it, the result is the same.

@balaton
Quote:
Here are the results from QEMU-11 on Linux

But setting aside the ATI (QEMU) test—this is interesting https://hdrlab.org.nz/benchmark/gfxbench2d/os/amigaos/Result/3025
VirtIOGPU?

@Maijestro
There seems to be some other issue here besides the ATI driver for QEMU itself.
We found a bug that occurs in the latest version of QEMU as well as in older versions.
I checked a few things regarding how ATI (QEMU) works on versions < 11 and...
@balaton created patches for ati-vga, and they are available in QEMU-11, which ensure that the driver itself works fully correctly only in QEMU-11.
That’s why I understand why he’s pushing so hard to report bugs only on QEMU-11.
On older versions QEMU, you may encounter endianness issues with sdl1, crashes in native applications, etc.
The fully functional version works correctly only with the latest version of QEMU-11

@balaton
Quote:
This video should show exactly what I mean. Test with “guest_hwcursor=on”
video -> https://youtu.be/t2oYFogw-8A

On a black background/“boot logo,” you can also see it depending on the monitor. The square is gray and the entire background is black.
After restarting, you can see the mouse pointer instead of the square. It’s displayed correctly, but it shouldn’t be there.
As I mentioned, there’s nothing significant affecting how it works. It’s behaving strangely, which is why I let you know

@balaton
Quote:
The problem is that a square appears in the top-left corner. From what I’ve noticed, it’s the pointer/cursor. It isn’t rendered properly and a square appears instead.
It occurs on QEMU 11, Fedora 43, Linux Wayland. It is possible that this is not entirely a problem with the driver itself. It occurs in GTK and SDL displays. It does not occur with VNC.
It also occurs in older versions of QEMU on Linux with X11 and macOS.
You can easily check this by disabling ‘guest_hwcursor’. On the welcome screen with the ‘AmigaOS 4’ logo, move the mouse. You will see this square instead of the cursor. The colour may blend into the black background but is slightly lighter. It is very visible against a white background. I have such an AOS4 start-up logo on one installation.
The mouse pointer should not appear at all at this point (before the system has fully loaded). It should be hidden/masked/invisible. The problem does not disappear when you click in the window or switch the ‘QEMU’ window to the active one.
This is not a major issue. Some people might not even notice it.

edit:
The video I recorded yesterday was actually from a Fedora 43 Linux system and QEMU 11

edit2:
There’s another way to open it. Restart AmigaOS using the option in the main menu.
On the start-up screen, you’ll see the correct mouse pointer in the top-left corner, which was a square on the first boot.