Who's Online |
217 user(s) are online ( 122 user(s) are browsing Forums)
Members: 1
Guests: 216
kas1e,
more...
|
|
Headlines |
-
mce.lha - game/utility
Apr 23, 2024
-
theme_list.lha - utility/misc
Apr 23, 2024
-
faac.lha - audio/convert
Apr 22, 2024
-
faad2.lha - audio/convert
Apr 22, 2024
-
seq.lha - audio/misc
Apr 22, 2024
-
libfaac.lha - development/library/audio
Apr 22, 2024
-
libfaad.lha - development/library/audio
Apr 22, 2024
-
image2pdf.lha - utility/text/convert
Apr 22, 2024
-
libharfbuzz.lha - development/library/graphics
Apr 20, 2024
-
libpng.lha - development/library/graphics
Apr 20, 2024
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
|
Not too shy to talk
|
@balaton
patch works with SFS v1.290 which means that the SFS version on the AOS4.1FE iso can be used to create and format SFS partitions for new installations.
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
|
Not too shy to talk
|
@joerg
Sorry, I mentioned the different SFS versions to show that it is less likely an issue with SFS, but more to do with the OS4 function call SFS is using that fails the check for the PCI bridge.
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
|
Not too shy to talk
|
@joerg Quote: joerg wrote:
@balaton Quote:I assume that version should work on real hardware if it comes with the sam460 install CD. Depends on the version of the install CD: - The SFS versions (I don't remember which versions of SFS were included on which versions of the AmigaOS 4.x CDs) included until Amiga OS 4.1 Update 5 or 6, the last AmigaOS 4.x distribution for which Hyperion had the permission to include my SFS versions as free contribution on the CDs, should work. - Pirate copies of my software, for example the SFS version included by Hyperion despite explicit prohibition to continue using any of my AmigaOS 4.x software on their AmigaOS 4.1 CDs, for example AmigaOS 4.1 Update 7/"Final Edition" or anything later, should fail. It's not limited to SFS, most of my AmigaOS 4.x software illegally distributed on such AmigaOS 4.1 CDs, for example AmiDVD and several others should fail as well. No matter if real hardware or emulated. SFS v1.277 PPC on aminet (and v1.293 in enhancer) has the same issue as v1.290 on the AOS4.1FE iso as far as I can tell, where-as SFS v1.277 68k works.
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
|
Not too shy to talk
|
@joerg
beats me.. its a basic 4.1FE upd2 install for QEMU-sam460 with 512Mb, and I had snoopy and mounter open with almost 400Mb ram free.
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
|
Not too shy to talk
|
@balaton Here is my output when using mounter to try and mount DH1: in QEMU. DH1: is a SFS partition on the same drive as the FFS boot partition. Hopefully this can add extra data to point people to the issue.
00001 : Mounter : o.k. = [exec] OpenDevice("sii3112ide.device",0,0x6793C610,0x00000000) = 0 [203uS]
00002 : Mounter : o.k. = LockDosList(DEVICE|READ)
00003 : Mounter : o.k. = FindDosEntry(,"DH0",DEVICE) = "DH0" [20uS]
00004 : Mounter : o.k. = FindDosEntry(,"DH1",DEVICE) = "DH1" [36uS]
00005 : Mounter : o.k. = FindDosEntry(,"DH2",DEVICE) = "DH2" [32uS]
00006 : Mounter : UnLockDosList(DEVICE|READ)
00007 : Mounter : o.k. = DismountDevice("DH1:",0x00000006,0)
00008 : Mounter : o.k. = [exec] OpenDevice("input.device",0,0x66F7D1E0,0x00000000) = 0 [123uS]
00009 : Mounter : [exec] CloseDevice("input.device") [9uS]
00010 : Mounter : o.k. = LockDosList(DEVICE|READ)
00011 : Mounter : FAIL = FindDosEntry(,"DH1",DEVICE) = "" [34uS]
00012 : Mounter : UnLockDosList(DEVICE|READ)
00013 : Mounter : o.k. = MakeDosEntry("DH1",0)
00014 : Mounter : o.k. = [exec] OpenResource("FileSystem.resource") [22uS]
00015 : Mounter : o.k. = AddDosEntry("DH1")
00016 : DH1/SmartFilesystem 1.293 : -----> PRIVATEInternalRunCommand("", ARG:"")
00017 : DH1/SmartFilesystem 1.293 : 1 = GetSegListInfo(0x00702659 [""], ) [16uS]
00018 : DH1/SmartFilesystem 1.293 : 0 = FindSegmentStackSize("") [55uS]
00019 : DH1/SmartFilesystem 1.293 : 1 = GetSegListInfo(0x00702659 [""], ) [13uS]
00020 : DH1/SmartFilesystem 1.293 : o.k. = [exec] OpenLibrary("dos.library",39) [55uS]
00021 : DH1/SmartFilesystem 1.293 : o.k. = WaitPkt(0x00000000)
00022 : DH1/SmartFilesystem 1.293 : o.k. = [exec] OpenResource("newfilesystem.resource") [16uS]
00023 : DH1/SmartFilesystem 1.293 : o.k. = [exec] OpenLibrary("expansion.library",51) [26uS]
00024 : DH1/SmartFilesystem 1.293 : [exec] CloseLibrary("expansion.library") [6uS]
00025 : DH1/SmartFilesystem 1.293 : o.k. = ReplyPkt(0x676B5054,R1=0,R2=103) [ACTION_STARTUP 0] [23uS]
00026 : DH1/SmartFilesystem 1.293 : [exec] CloseLibrary("dos.library") [6uS]
00027 : DH1/SmartFilesystem 1.293 : <----- PRIVATEInternalRunCommand("", ARG:"") = [103 (0x00000067)]
00028 : Mounter : FAIL = DeviceProc("DH1:") [20169uS]
00029 : Mounter : o.k. = [exec] OpenDevice("input.device",0,0x66F7D0C0,0x00000000) = 0 [115uS]
00030 : Mounter : [exec] CloseDevice("input.device") [14uS]
00031 : Mounter : [exec] CloseDevice("sii3112ide.device") [14uS]
|
|
|
|
Re: Qemu Pegasos II interrupts issue
|
|
Not too shy to talk
|
@Hans
Im using my build of v9.0.0-rc0 on windows, and I have tried peg2, amigaone and sam460 in qemu and have not seen the same issue.
what version is your qemu build, as some irq updates balaton wrote for the southbridge were commited at the end of November 2023.
|
|
|
|
Re: RadeonHD V.5 driver
|
|
Not too shy to talk
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 12/21 20:49
#9
|
Not too shy to talk
|
@balaton
I have always used the weilnetz builds on windows and have never had an issue.
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 12/3 16:09
#11
|
Not too shy to talk
|
@balaton
Compiled current qemu master for windows and Amigaone machine with bboot working as intended. Good job!
|
|
|
|
Re: PCI virtio driver development
|
Posted on: 2023/11/21 23:32
#12
|
Not too shy to talk
|
@smarkusgQuote: smarkusg wrote:@kas1eQuote:If they simply upload it on os4depot for everyone's usage: then that will be very good and correct way : everyone who will be in needs can use it. All good.
But it wasn't like this with classes, and surely will not happen with this library too (i hope to be wrong). Those developers who will be in interest to use this library, will be forced to wait when Mattew will find a time to answer with putting a restriction usage on top of it :)
Do you think they can upload it to os4depot in the end for everyone's usage ? I didn't believe in, but hope to be wrong :)
You have made me curious. As I understood it. E.g. an ordinary person who would like to do something with VAAPI for AOS4 has to ask @ for an API, register somewhere, sign something ? VAAPI is only for A-EON products ? Im assuming they are talking about the Enhancer Software Core 2 pack ( link here) as that requires an Amisphere login to download the pack for free. My own opinion is it doesnt matter what website you get it from, as its still free and Matthew will still have the same limited time to do things. There are much better things to spend time on.
|
|
|
|
Re: Running my OS4 games on QEmu
|
Posted on: 2023/11/20 22:08
#13
|
Not too shy to talk
|
@balaton Quote: balaton wrote:@TheMagicSN Quote: As to the SDL crash, anyone ever tried to insert debug output into the SDL compile to find out where inside SDL it crashes ?
It does not crash just produces garbled graphics with some SDL1 apps. What's strange is this only happens on pegasos2 not on amigaone but these two machines are very much the same on the QEMU side so there must be some difference on the guest side. When booting pegasos2 kernel with debuglevel=7 I've noticed these logs:
gfx AltiVec/VMX enabled
gfx PPC74xx optimizations enabled
which are the first things printed after kernel starts so probably part of graphics.library or siliconmotion502.chip as the logs from the SM502 driver follow immediately. This looks like it could have something to do with the issue (as it goes away when using -cpu g3) but don't know where these logs are coming from or if they are present on amigaone. Maybe this is something that somebody interested to find this out could start from. Anybody knows more about what these logs are and where they are coming from? These lines also appear when using amigaone in qemu.
|
|
|
|
Re: Command to see CFE/UBOOT variables
|
Posted on: 2023/9/10 23:10
#14
|
Not too shy to talk
|
@rjd324 https://wiki.amigaos.net/wiki/UserDoc:BIOSQuote: Once AmigaOS has been installed you can obtain a complete unsorted list by typing NVGetVar from a Shell to display all of the UBoot environment variables. Typing NVGetVar >RAM:varlist will output the list to a file on the RAM Disk which you can print off for reference if required. I dont have a X1000 so cant check if this is correct.
|
|
|
|
Re: Pegasos2 with RadeonHD/RX via bridge
|
Posted on: 2023/8/24 22:30
#15
|
Not too shy to talk
|
Good work Hans!
@kas1e
Is this using bboot?
|
|
|
|
Re: qemu emualtion of AmigaONE XE
|
Posted on: 2023/8/13 0:19
#16
|
Not too shy to talk
|
@balaton
Using the ES1370 device on Pegasos2 and AmigaOne has the same distortion. I do not notice distortion using the ES1370 device on Sam460.
|
|
|
|
Re: Problems with AmiUpdate
|
Posted on: 2023/8/11 16:52
#17
|
Not too shy to talk
|
@Raziel
amiupdate.codebench.co.uk is down
|
|
|
|
Re: qemu emualtion of AmigaONE XE
|
Posted on: 2023/8/7 0:35
#18
|
Not too shy to talk
|
@balaton
I have successfully installed the AmigaOne-qemu version, and I will try and describe any issues I had.
(Compiled and run on Ubuntu, Ryzen 5600x.)
Note - There are 3 windows in use * - serial window for debug messages * - VGA BIOS window for uboot * - SM50x window for AmigaOS
- Besides adding the siliconmotion502.chip file to the install CD, I also added the SmartFilesystem file (from enhancer package) so that I could install to and boot from SFS/02
- The ide/CD speed seems slow when loading the kickstart files from it. The speed seems fine when installing onto HD.
- When the OS installation finished and rebooted, the SM50x window looked like it froze, but the VGA BIOS window had reset and was waiting at the uboot menu. Once I set it to boot from HD it worked (my HD boot priority was already set to 10 to make sure the CD didn't boot instead).
- The HD boot worked after I removed the a1floppy.device.kmod entry in the Kicklayout, as that is what is stopping the OS from loading.
- Using the es1370 device for sound is not perfect as sounds crackle and/or get distorted as they go on. changing bitrate and other settings don't make a difference. I didn't notice this issue when using this sound card with sam460-qemu
Summary - The only issue I have is the sound. Other than that I would say its speed is on par with Peg2-qemu.
|
|
|
|
Re: QEMU, e500 and Linux
|
Posted on: 2023/7/27 23:31
#19
|
Not too shy to talk
|
@afxgroup You can add a device to do this, and you can get the full list of valid devices using the following line.
./qemu-system-ppc -device help
Here is the list of valid storage devices
Storage devices:
name "am53c974", bus PCI, desc "AMD Am53c974 PCscsi-PCI SCSI adapter"
name "dc390", bus PCI, desc "Tekram DC-390 SCSI adapter"
name "floppy", bus floppy-bus, desc "virtual floppy drive"
name "ich9-ahci", bus PCI, alias "ahci"
name "ide-cd", bus IDE, desc "virtual IDE CD-ROM"
name "ide-cf", bus IDE, desc "virtual CompactFlash card"
name "ide-hd", bus IDE, desc "virtual IDE disk"
name "isa-fdc", bus ISA, desc "virtual floppy controller"
name "isa-ide", bus ISA
name "lsi53c810", bus PCI
name "lsi53c895a", bus PCI, alias "lsi"
name "megasas", bus PCI, desc "LSI MegaRAID SAS 1078"
name "megasas-gen2", bus PCI, desc "LSI MegaRAID SAS 2108"
name "mptsas1068", bus PCI, desc "LSI SAS 1068"
name "nvme", bus PCI, desc "Non-Volatile Memory Express"
name "nvme-ns", bus nvme-bus, desc "Virtual NVMe namespace"
name "nvme-subsys", desc "Virtual NVMe subsystem"
name "pvscsi", bus PCI
name "scsi-cd", bus SCSI, desc "virtual SCSI CD-ROM"
name "scsi-hd", bus SCSI, desc "virtual SCSI disk"
name "sd-card", bus sd-bus
name "sdhci-pci", bus PCI
name "sii3112", bus PCI, desc "SiI3112A SATA controller"
name "usb-bot", bus usb-bus
name "usb-storage", bus usb-bus
name "usb-uas", bus usb-bus
name "virtio-blk-device", bus virtio-bus
name "virtio-blk-pci", bus PCI, alias "virtio-blk"
name "virtio-blk-pci-non-transitional", bus PCI
name "virtio-blk-pci-transitional", bus PCI
name "virtio-scsi-device", bus virtio-bus
name "virtio-scsi-pci", bus PCI, alias "virtio-scsi"
name "virtio-scsi-pci-non-transitional", bus PCI
name "virtio-scsi-pci-transitional", bus PCI
For scsi you could add a new device of 'virtio-scsi-pci', and then add a scsi-hd image and attach it to scsi.0
-device virtio-scsi-pci -drive if=none,id=hda,file=linux.hdf,format=raw -device scsi-hd,drive=hda,bus=scsi.0
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 2023/7/21 16:36
#20
|
Not too shy to talk
|
@derfsQuote: 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. Basically its nothing to do with qemu :)
|
|
|
|