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.
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
You are most likely right. Just booting from "pegasos.rom" on Qemu is long - detecting devices/settings etc. Additionally, the boot settings need to be entered, as they are not saved during emilation. Bboot boots under Qemu with practically all the necessary settings.
Reading the threads on the forum you were sceptical about Qemu PPC/Qmiga. I hope you will change/change your mind
Yes I know. But the difference is similar - it boots almost twice as fast on bboot instead of via Amigaboot/pegasos.rom under Qemu.
Probably what Martin mean, that you miss the entry in the first answer about boot loading speed of amigaboot.of , so the answer was looking like you showing only speed of bboot to do a compare with the speed on real pegasos2 :)
As for whole speed: On real peg2 there it's all IDE, and through i do use Sata2IDE adapter it still IDE speed. Plus i also have set debug level, so it also takes few seconds.. I do have IDE2CF adapter as well, so may try for sake of interest how fast it will be from CF, but since it all ends with IDE, it can be same result.
What i am interesting most it when this damn PCI<->PCIE adapter arrive and i can test RadeonHD with :)
@Maijestro I plan to update my pegasos2 guide with BBoot instructions, I just haven't got to it yet.
No problem, I'll take care of it and send you the updated installation instructions by mail for comparison, I think you'll surely find one or the other error.
I am also not sure if BBoot works for the complete standard installation with the AmigaOs4.1 Pegasos 2 install CD. Since I'm on vacation right now, I'll test it over the next few days.
Edited by Maijestro on 2023/7/21 21:02:28 Edited by Maijestro on 2023/7/21 21:03:35
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Looking at the log from real PegasosII it looks like board firmware also leaves card at least on AGP bus with all ff values not only for interrupt but also for BARs. I'm not sure how that happens but if this works on real machine then BBoot should also not set these and leave them when they are set to all ff values. Currently in 0.2 these will be set and due to having wrong BAR values it results in 32 bit BARs set to 64 bit which maybe does not cause a problem if AmigaOS driver only needs the assigned-addresses property values and later reprograms the card based on that but I should probably need to fix this in a next version to get closer to real hardware.
To check if other values are the same with pegasos2.rom and bboot+VOF you could try booting with bboot both through bboot.fth with -bios pegasos2.rom (and maybe also running your script first) and without ROM just using -kernel bboot and post both logs and compare the values in those. BBoot prints the assigned-addresses property and other PCI values as it finds them and all chnages it made to them so this should help to find what's different when it works vs. when it doesn't. I think you got this just did not have time to test it but just saying it again to make sure I've explained it clearly enough.
@Maijestro I plan to update my pegasos2 guide with BBoot instructions, I just haven't got to it yet.
Finally after some failures I connected my AmigaOS 4.1 pendrive brought to me by Amedia France and it boots 2 times!!!
At this point is it recomendable to delete my AmigaOS4.1 partitions content and then copy USB content inside the AmigaOS4.1 partition?
Thanks
I will play MAME later again!!!
Amiga 500 1MB Chip RAM with ACA 500+ACA1232,CD32,Amiga 1300 030/50 Mhz,32MB (now on my hands at least)and Amiga One G3 XE PPC 800 Mhz,ATI Radeon 9250 128 MB,256 MB RAM,Seagate 200 GB HD,2 working DVD drives,X-Arcade double for MAME,Sil0680,4 USB ports,LG
@balaton So far sitting playing with peg2 for few hours booted from bboot 0.2 do not cause in os4 itself any differences in compassion with when i boot by amigaboot.of.
I am surprised myself that BBoot runs so well with AmigaOs4.1.
I can also confirm that the system continues to work stable without problems. Web browsing with YouTube streaming and sending files via FTP with ZitaFTP all no problem, even a good 30 minutes BreakHack play was possible until I had no more desire.
Fantastic work, tested under Qemu 8.1 RC0
Edit: Due to the new bootloader "BBoot" I am forced to completely revise my installation instructions concerning the installation of AmigaOs.4.1 under Qemu Pegasos 2. Maybe someone could also create an english manual? Otherwise you could translate my installation guide into English since it is written in German.
Edited by Maijestro on 2023/7/21 19:34:29 Edited by Maijestro on 2023/7/21 19:36:43
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
I got sector dumps from someone who destroyed an AmigaOS 4.x SFS partition by writing from MorphOS to it several years ago. Some of the sectors included invalid data which was definitely overwritten by the incompatible MorphOS SFS version.
Years ago i also destroyed OS4's SFS boot partition when wrote from Morphos to it (it wasn't like from the first write, but just after i do many write to). But other way around (from OS4's SFS to Morphos's SFS) works fine. So i just remember to not write from mos to os4's sfs anymore.
As for SFS reading from peg2's firmware, i do have on pegasos2's disk such partitions:
And when i do "ls" on them from peg's firmware, i can see ffs, morphos's sfs, but for our one have just "sfs-load: file "" not found ". So, yeah, it only read mos's sfs.
@All Interesting that on real pegasos2 , both Ethernets (and inbuilt one, and my PCI card one) sit on irq 0x09, together as many other things, but bridges (host bridge, isa bridge, etc) on 0x00 and IDE on 0x0E. But all others like audio, network, video, fireware, usb all indeed on 0x09. Just not IDE and bridges.
@balaton So far sitting playing with peg2 for few hours booted from bboot 0.2 do not cause in os4 itself any differences in compassion with when i boot by amigaboot.of.
Edited by kas1e on 2023/7/21 17:20:37 Edited by kas1e on 2023/7/21 17:34:54 Edited by kas1e on 2023/7/21 17:36:57
EDIT: By the way, i found that latest pegasos2 firmwares, not only support USB keyboards (i use USB keyboard there) , but also have ability to boot from SFS too. But i assume it's an ancient version of SFS
Maybe not (much) older, but it's for the incompatible MorphOS SFS port, which doesn't even seems to be compatible to SFS 1.84, let alone to the changes I did in my AmigaOS SFS versions, which aren't 100% compatible to SFS 1.84 anymore either, but of course using different changes.
I got sector dumps from someone who destroyed an AmigaOS 4.x SFS partition by writing from MorphOS to it several years ago. Some of the sectors included invalid data which was definitely overwritten by the incompatible MorphOS SFS version.
Read-only access, like in a boot loader, might work most of the time even when using incompatible SFS versions, but there is no guarantee.
Im getting the kickstart files to load, but before i get the pass-through gfx output on the 2nd screen my PC hard crashes!
My hard-crash issue seems to be a known issue with Ryzen cpus
Linux logs show it as a MCE hardware error, which - depending on what you read - either needs an update to the bios, or requires playing around with voltages in the bios.
Yeeehhhoooo my attempt to change the FTP client was the right decision.
Now I use Cyberduck, this FTP client is very simple like ZitaFTP under AmigaOs4.1.
@Hans it works perfectly, I didn't have to change anything else in my Qemu configuration.
I like this solution very much for the data dive between host and guest. I will buy this software.
Edit: The file transfer is stable, I tested it with a 100 MB+ file and it was transferred successfully.
@smarkusg
So I won the challenge because I found a very simple setup that works very well. Of course, their configuration is also possible, but I like it simple and straightforward, anyway thanks for the help buddy. It shows once more how usable Qemu with AmigaOs4.1 is at the moment.
Edited by Maijestro on 2023/7/21 17:36:18 Edited by Maijestro on 2023/7/21 19:01:04
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
BBoot is GPL v2, therefore it never can get any support for my AmigaOS SFS versions.
What kind of support you mean ? Is there needs for any support to add read-only support of any fs does not matter what, so to be able to read from to be able to load kickstart modules ?
But all that just theoretical and not important, loading kickstarts from FFS work fine as well for now, and more than enough to handle issues with RadeonHD/RX in meanwhile. With .zip file loading from FFS even faster than with unpacked modules on SFS2 (At least on pegasos2 and at least with the ~4mb zip archive).
EDIT: By the way, i found that latest pegasos2 firmwares, not only support USB keyboards (i use USB keyboard there) , but also have ability to boot from SFS too, but so far it looks like just from some ancient version of SFS (it can see morphos's SFS, but can't see amigaos4's SFS00).
Edited by kas1e on 2023/7/21 16:35:46 Edited by kas1e on 2023/7/21 16:51:35