AmigaOne as qemu target

@all

Got just AmigaOne up on qemu. How to set up audio part, as there is some missing parts on real HW?

Thanks.

@Mlehto
The audio parts are present on QEMU so sound should work the same as on pegasos2 but maybe AmigaOS does not select the audio output automatically on amigaone. You should be able to set it in Prefs AHI/Audio/Sound or whatever that is called then select via-ac97 (or you can add -device ES1370 and use with SB128 driver instead). There was something about Units. I think the default Unit should stay at audio.device or something like that and only select via-ac97 or other hardware drivers for the other 4 units. This was discussed on this forum before and if I remember correctly audio.device allows more apps to use output simultaneosly so you only want to select sound card for the hardware units. Sorry for the approximate info but I don't remember exactly but hope this gives some directions. If you have pegasos2 running easiest is to check what is set there in AHI Prefs and set the same on amigaone.

@balaton

True, thanks :)

How about peg2 target, didnt dig it more, but memory as 2gb didnt work?

@Mlehto
See: https://qmiga.codeberg.page/aos_problems.html
2GB works with -kernel bboot on pegasos2 but SmartFirmware cannot detect SIMMs bigger than 1GB. This could be fixed but I did not bother as it works with -kernel bboot which is probably the most used config.

Ok, thanks. Im mixed things again it seems.

Looks like 2b2, 2b3 newest OF differ from 2b5, wich works with 2gb. All differs from latest public though.

Hopefully thinking… bboot on real 2b2 probably doesnt change this…

Anyway I think that there may be something on 2b2/2b3 boards itself, wich prevent 2 gb functioning correctly.

@Mlehto
The 2bX are not firmware but board revisions I think. Each may have a minimum required firmware version but I only know about two firmware versions available on-line and the last from bPlan does not seem to support 2GB. I think there's a newer maybe on MorphOS storage but I don't know if that's any better. In any case if there's a hardware issue that causes instability with more than 1GB RAM BBoot (or even the firmware) can't fix that. Even if it's a firmware issue not detecting bigger than 1GB SIMM, BBoot on real machine running from firmware can't do anything about that as at that point the firmware has already detected RAM and set up the memory controller at boot which can't be changed later. You'd need a newer firmware probably. I think there was a thread about 2GB on pegasos somewhere that may have some info, maybe on morph.zone?

@balaton
From what I remember reading about PEG2, you had to use a very specific type of memory module for it to work with 2 GB of memory on real machines.

@smarkusg
Yes but it's unclear what are the limitations. Is it some hardware issue or a firmware issue not recognising newer SIMMs or SIMMs with different number of banks or something like that. It's most likely to work with the oldest 1GB modules that were available at the time the firmware was written and least likely to work with newer and larger SIMMs. And maybe not even all of the older ones work but the ones that were tested. It was probably not common to have such large SIMMs back then.