@afxgroup
Nice!

@Tuvok
Thanks for tests !

So it looks like just my x1000 acts like this .. Maybe some power issues or so ..

My X1000 also act a bit strange : not always re-startup (i mean just to X1000 logo) after reset, and i should doing another one. Like it not fully initialized. I remember Raziel (user who were here some time ago) report same ..Do you have this kind of issue ? On serial when i can't boot i usually have:



And that all. Then again reboot (power off/poweron) and it starts. But that another problem anyway ..


Quote:
I do not have one either, all i know is that it was done, but have race condition bug : debug version works fine and can transfer gigabytes of data, but release version crash/freeze soon or later, so it was some race-condition bug which author weren't able to find and fix. Also it was (if i remember correctly, but can be very wrong, so don't take this for granted) a paid job for aeon, so you can imagine it all can ends up with nothing..

Anyway, because of that i trying to wrote open-source version now, and so far come to the point that i can ping myself, i can even connect via telnet to router outside (so basics works), but when i tried to load up welcome page from router is just end up loosing packets, etc.. so debug and one more debug.. There is for now:

(click open in new tab for fullsize):

@afxgroup
I know who should be next president ! Thumbs up ! What else except C-Media CM106 (0D8C:0102) 7.1 USB may be worth of testing ? (something up2date which can be find in shops, etc)

@Maijestro

All libraries are on OS4depot with clib4 version included

@maijestro

About the latest clib4, you can use the development branch, as others mentioned, and compile it yourself, or download the latest nightly build from https://github.com/AmigaLabs/clib4/releases/tag/nightly and copy the files inside the /opt/ppc-amigaos/ppc-amigaos/SDK folder

Thank you for using my docker images. I am glad that they are helpful.

@nbache

Quote:

He is using my docker images which still have the 54.16 SDK and not the updates coming with the update 3. Those will be included in a future update of my docker images.

I've been building a native USB Audio Class driver for AmigaOS 4 from scratch. It now supports stereo playback, 7.1 multichannel surround, recording with input switching, multi-device detection, and user-configurable device names. It's in beta

What works:

- Stereo and 7.1 multichannel playback
- Recording with Microphone, Line In, and SPDIF input switching
- Hardware volume control and input gain
- Multiple USB audio device detection and selection
- Glitch-free playback with triple-buffered isochronous transfers
- Clean start/stop without crashes
- Custom device names via prefs file
- Amiga Installer package for easy deployment

What to be aware of (beta caveats):

- Only USB Audio Class 1.0 devices are supported (covers most USB sound cards)
- Only 16-bit PCM format is currently handled
- The device must be connected before AHI initializes the driver
- Hot-plug/unplug while audio is playing will cause issues
- Not all USB audio devices have been tested — your mileage may vary
- Recording quality and input switching behavior depends on the specific USB chipsetIf you encounter problems, please capture the full serial debug log (all lines starting with [USBAudio]) and report the issue along with your device's VID:PID.

Read more here:

https://ko-fi.com/post/USBAudio-Bringi ... o-to-AmigaOS-4-B0B31VO9UN

And you can download it for free here: https://ko-fi.com/s/7f7d79b214

I'll add on os4 depot once it is stable enough

@kas1e

I tested, and the lights always start to flicker. On the router it is green when I connect to the internal ethernet port, while it is orange if I connect the cable to the Realtek 8139 ethernet card. The router senses automatically the connection speed. 1000Mbit = green 10/100Mbit = orange.

Test:

1. disconnect eth-cable from RLT8139
2. connected to internal X1000 ethernet port
-> internal LEDs of X1000 ethernet port flicker
3. pressed "reset" button on X1000 case
4. Waited for AmigaOS4.1 FEu3 to fully boot
-> internal LEDs of X1000 ethernet port flicker

New test:
1. Turned off X1000
2. waited 1 minute
3. verified ETH-cable connected to X1000 port
4. boot AmigaOS
-> LEDs flicker
5. reset of OS via software (Workbench menu)
6. Waited OS to fully boot
-> LEDs flicker
7. reset system via software (Workbench menu)
8. Waited for OS to fully boot
-> LEDs flicker
9. Pressed Reset button on case
10. Waited for OS to fully boot
-> Leds flicker.

Maybe it is because I have RTL-8139 card installed?

However, I am not a lucky one to have driver for the internal X1000 ethernet device. Never released to the public as far as I know.

So even if the lights flicker (modem and internal LEDs on X1000) I can not use the port. I tried to manually select pa6t_eth.device in internet wizard, but it can not open device. (error sound and does not let me "continue" set up wizard)

Hope this helps your quest.

@328gts

This is on my Sam460ex.
The X5000 is mainly used for USB testing and things requiring Warp3D Nova.

@All
Find out that on my x1000, when i connect router to the onboard NIC and then power on machine, then the leds both on router and on the NIC are green. All fine. Then, if i do "reset" by reset button on tower, they go to offline, and never come up even after OS4 loads up again. So , to make link again to work, i had to do exactly power off / power on.

Can somebody confirm if it only my x1000 acts like this, or all of them ?

Thanks!

@328gts



122595

@AmigaOldskooler

Thanks!

@AmigaOldskooler

Hi!

On February 19.02.26 there was also a release of
Infinite Icons 1.4 which also included an OS3.2 installer.

Can be found here:
https://www.amikit.amiga.sk/infiniteicons

@kas1e
Quote:
It also freezes on Asahi Linux ARM64 (Fedora).
But it's a little different than RTL8139. Small packets still get through. On RTL8139, access is completely cut off.


Now my question, Roadshow (maybe a stupid one).
From what I've read, it works strangely even on real machines.
The INTERNET speed is poor. You can get some good values on the LAN.
Is there a problem there?
I don't currently know how packets are transmitted through QEMU. QEMU definitely emulates network cards, but what if a guest (AOS4 with an old TCP/IP stack) gets a “large packet” exceeding some limit (10Mb/100Mb/1Gb)? It will try to limit it, but it won't be able to handle it... will it crash?
I'm just writing theoretically - these are just my random thoughts and I may be talking nonsense.
One last thing: qemu-system-ppc and MacOS 9 PPC and Linux PPC work fine. There are no problems there.

@Maijestro

Quote:
If you had installed update 3, which was released last October, you should have had SDK 54.17.

Best regards,

Niels

@Maijestro

Clib4 dev version
https://github.com/AmigaLabs/clib4/tree/development

SDL 2.32.8
https://os4depot.net/?function=showfile&file=library/misc/sdl2.lha

@afxgroup

AmigaOS4 Build Environment
===================================

Compiler
--------
GCC 11.5.0 (adtools build)

SDK
---
AmigaOS4 SDK 54.16 (August 2022)
execsg SDK 54.31 (August 2022)
dos SDK 54.120 (March 2022)

Libraries
---------
clib4 2.0.0 (August 16, 2025)
SDL2 2.30.1 (August 2025)
SDL2_ttf 2.x (August 2025)
SDL2_image 2.x (August 2025)
SDL2_mixer 2.x (August 2025)
SDL2_net 2.x (August 2025)
SDL2_gfx 1.0 (August 2025)
SDL2_gl4es 2.30 (August 2025)
FreeType 26.2.20 (August 2025)



This is my complete development environment. The SDK seems to be a bit older, and I probably need to update it and bring it up to date? Or it could be an error in the AI version check.

In any case, I built ScummVM completely using Clib4, and it's already working very well. Thank you for the great work on Clib4.

The rtl8139 AmigaOS driver author has looked at it before and also checked the emulation in QEMU and could not find any problem in either of those so it could well be the issue is somewhere else. It could be in AmigaOS common SANAII code or network stack too. That it works on real machines does not mean the AmigaOS side does not have race conditions that do not happen as long as things are slow as on real machine but could break when replies come faster than expected (sometimes instantly) on emulation that may never happen on real machines. It could also be in QEMU's Windows version as that's less tested but since all network cards use the same netdev backends in QEMU and a lot of people use those it should not be completely broken so it's more likely to be either in rtl8139 emulation (which does not seem to be the case), pegasos2 emulation (you could try with other machines to check) or somewhere on the AmigaOS side but not in other parts of QEMU.

@kas1e
Quote:Should make next to no difference with old file systems like SFS as they can't take advantage of drivers supporting NCQ or similar (nearly all SCSI drivers, nvme.device, virtscsi.device, ...) as they are only doing a single device I/O and wait for completion before starting the next device I/O command.
Other file systems could be much faster on such devices, but I don't know if NGFS or filesysbox.library based file systems (NTFS-3G and several other FUSE file system ports) use multiple, parallel device I/O commands.

For booting AmigaOS from a 9PFS handler support for the 'e' protection bit isn't enough, additionally at least the 's' protection bit is required. Ideally all 16 AmigaOS protection bits should be supported, as well as the UID and GID numbers.
What you could do is using a small image file boot partition and put something likeat the beginng of the Startup-Sequence.
That way most of the OS is loaded from the 9PFS mounted directory.

@kas1e
No, that's the point. Image file is like a disk on which you have partitions and virtio-9p is like a network share that you mount. When the kernel boots it reads RDB from disks and looks for a boot partition which it can find with an image and virtio-scsi where the virtio-scsi driver is just like a disk driver otherwise everything is like on real machine with disks but what happens with a virio-9p driver? How does it know which share to mount and how does the kernel know it should boot from that when there's no RDB with partitions and a bootable flag anywhere? With Linux the 9p client is in kernel and there are options to tell it to mount and look for the root filesystem on a 9p share. But is there something similar in AmigaOS kernel or could just a virtio-9p driver provide that? A 9p driver may have an otion to tell it to mount a share but how do you tell the AmigaOS kernel that it should boot from that device if it has no RDB?

The difference between an emulated IDE and virtio-scsi is not in the image file, that's the same but emulated IDE goes through IO and interrupts which is slower than virtio that uses shared memory to communicate with QEMU with less emulation overhead.

@balaton
Quote:
I may talk bull, but as far as i see virtio-scsi its the same "img" file, just which i can see as real partition in the qemu. But what i want is to have just directory "System:" on windows, in which installed files of os4 can be seen as regular files (just like now in SHARED: with virtio-fs.handler).

ps. to be honest i not fully understand for now difference between having os4.img as it were done before, and scsi.img. Is is give any benefits ? I mean in both ways it's .img file which i need to partition and install on. Or i miss some major point ?