Who's Online |
54 user(s) are online ( 36 user(s) are browsing Forums)
Members: 2
Guests: 52
Maijestro, trixie,
more...
|
|
|
|
|
Re: PCI virtio driver development
|
Posted on: 11/21 23:32
#1
|
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: 11/20 22:08
#2
|
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
|
|
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
|
|
Not too shy to talk
|
Good work Hans!
@kas1e
Is this using bboot?
|
|
|
|
|
|
Re: qemu emualtion of AmigaONE XE
|
|
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
|
|
Not too shy to talk
|
@Raziel
amiupdate.codebench.co.uk is down
|
|
|
|
|
|
Re: qemu emualtion of AmigaONE XE
|
|
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
|
|
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 ?
|
|
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 :)
|
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 7/20 21:51
#10
|
Not too shy to talk
|
@balatonQuote: balaton wrote:@derfs
If you see no Unknown RTAS token message then it's not using rtas to access nvram but reads it directly. I think I know what might be missing then but does this cause any issue other than the crash log? If not I probably won't fix until QEMU 8.2. The output you get with pegasos2 firmware does not seem meaningful anyway. The only issue i have is that some software (Sysmon) i use will always crash as it uses 'nvgetvar' to read all non-volatile variables, as a way to see what has been set in the bios. It does not affect using the OS at all so it can wait.
|
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 7/20 17:56
#11
|
Not too shy to talk
|
@balatonQuote: balaton wrote:@derfs
Does that crash cause any issue apart from the log? The emulated pegasos2 does not have nvram so even using the pegasos2.rom it would not be able to read anything but if it uses rtas then with VOF even the rtas calls are not implemented. I can look into that if it causes a problem but since there's nothing to return it does not matter if the result is only this log message but no other problems in AmigaOS.
If it's a problem with unimplemented rtas call you should see messages saying "Unknown RTAS token..." when using -d unimp QEMU option when the crash happens. That would confirm this is calling rtas and does not handle error from there (becuase on real firmware these are implemented). There are no unimplemented messages when the programs crash. If I use the pegasos firmware then nvgetvar produces output instead of crashing.
New Shell process 8
8.AmigaOS:> nvgetvar
peg2ide_xfer=FFFF
peg2ide_irq=1111
«Êþ«Êþ«Êþi
¢ài
¡Ài
¯Ði
¢Þ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ïi
¡ði
¡0i
¯Ði
¢°Þ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ïi
Ði
¢i
¯Ði
¢àÞ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ïÞ¾ï(goñ(
8.AmigaOS:>
The peg2ide commands are found in the kickstart file nvram.config *edit* noticed that AmigaOS has an extra error in the debug log for bboot, but not pegasos2.rom
Error adding SMI interrupt
|
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 7/20 16:30
#12
|
Not too shy to talk
|
@balaton Im ignoring the passthrough card first so that i can check things are running as they should. Running the same kicklayout which includes RadeonHD driver, but just using -device sm501. 1st bug is getting a crash in AmigaOS on module nvgetvar, which im assuming is because we are not using the pesasos firmware now.
Dump of context at 0xEFC6CBA0
Trap type: DSI exception
Machine State (raw): 0x0000D030
Machine State (verbose): [ExtInt on] [User] [IAT on] [DAT on]
Instruction pointer: 0x7FCD6BCC
Crashed process: nvgetvar (0x60C7D7C0)
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a load operation
0: 7FCD6124 5FB5FF40 ABADCAFE 00000000 5FB5FC69 5FCD8088 00000001 80808080
8: 02048A81 0000006F 02048A88 00000064 010D41B9 ABADCAFE 5FBF49B4 5FB60010
16: 02330000 EFC95F00 02330000 00010000 5FBF49B0 60773C40 01843848 60775A70
24: 6FF7E044 60F1F580 00000000 5FCE0000 00000000 6FF96300 02172C88 6FE69BA0
CR: 35955353 XER: ABA1CAFE CTR: 0000005D LR: 7FCD6158
DSISR: 40000000 DAR: 00000000
Kernel command line: os4_commandline serial munge debuglevel=3
Registers pointing to code:
r0 : _start()+0x104 (section 1 @ 0x100)
r5 : module nvgetvar at 0x5FCD8088 (section 5 @ 0x64)
r6 : module nvgetvar at 0x00000001 (section 0 @ 0xFFFFFFDC)
r8 : native kernel module nonvolatile.library.kmod+0x004c40c1
r10: native kernel module nonvolatile.library.kmod+0x004c40c8
r16: native kernel module radeonhd.chip+0x0072f420
r18: native kernel module radeonhd.chip+0x0072f420
r22: native kernel module kernel+0x00043848
r30: native kernel module kernel+0x00972c88
ip : module nvgetvar at 0x7FCD6BCC (section 4 @ 0xBA8)
lr : _start()+0x138 (section 1 @ 0x134)
ctr: unknown (0x0000005D)
Stack trace:
(0x5FB5FF40) module nvgetvar at 0x7FCD6BCC (section 4 @ 0xBA8)
(0x5FB5FF90) _start()+0x138 (section 1 @ 0x134)
(0x5FB5FFC0) native kernel module kernel+0x000436f0
(0x5FB5FFD0) native kernel module kernel+0x00043770
Disassembly of crash site:
7FCD6BBC: 98090000 stb r0,0(r9)
7FCD6BC0: 39290001 addi r9,r9,1
7FCD6BC4: 409EFFEC bne+ cr7,0x7FCD6BB0
7FCD6BC8: 4E800020 blr
>7FCD6BCC: 88030000 lbz r0,0(r3)
7FCD6BD0: 7C691B78 mr r9,r3
7FCD6BD4: 38600000 li r3,0
7FCD6BD8: 2F800000 cmpwi cr7,r0,0
7FCD6BDC: 4D9E0020 beqlr- cr7
7FCD6BE0: 7D234B78 mr r3,r9
Stack pointer (0x5FB5FF40) is inside bounds
Redzone is OK (4)
68k register dump
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Page information:
Page not found
|
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 7/20 16:17
#13
|
Not too shy to talk
|
@Maijestro I had some unexpected 'lowercase vs. uppercase' issues for the name of the zip file, as well as whats in the kickstartlayout file vs the names of the actual files. Im getting the kickstart files to load, but before i get the passthrough gfx output on the 2nd screen my pc hard crashes! Not sure what to try and check to be honest. *edit* also use
-append "os4_commandline serial munge debuglevel=3"
if you want debugoutput
|
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 7/18 23:55
#14
|
Not too shy to talk
|
@balatonQuote: balaton wrote:@MartinW
I don't know an easy way, maybe -trace enable="pci*" shows accesses to config regs and one can check there. Maybe it's not causing the IRQ issue with passed through cards but worths a try checking it anyway. Im getting constant output of the following lines after using -trace for pci*. There is so many that i had to freeze qemu to use the monitor as the output disappeared as soon as i pressed enter.
pci_route_irq IRQ 0 @/machine/peripheral-anon/device[0] -> IRQ 1 @root-complex
pci_route_irq IRQ 0 @/machine/peripheral-anon/device[0] -> IRQ 1 @root-complex
pci_route_irq IRQ 0 @/machine/peripheral-anon/device[0] -> IRQ 1 @root-complex
pci_route_irq IRQ 0 @/machine/peripheral-anon/device[0] -> IRQ 1 @root-complex
etc....
This is info qtree when i paused qemu
(qemu) info qtree
bus: main-system-bus
type System
dev: ps2-mouse, id ""
gpio-out "" 1
dev: ps2-kbd, id ""
gpio-out "" 1
dev: mv64361-pcihost, id ""
index = 1 (0x1)
x-config-reg-migration-enabled = true
bypass-iommu = false
bus: pci.1
type PCI
dev: rtl8139, id ""
mac = "52:54:00:12:34:56"
netdev = "net0"
addr = 03.0
romfile = "efi-rtl8139.rom"
romsize = 262144 (0x40000)
rombar = 1 (0x1)
multifunction = false
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class Ethernet controller, addr 00:03.0, pci id 10ec:8139 (sub 1af4:1100)
bar 0: i/o at 0x1200 [0x12ff]
bar 1: mem at 0xffffffffffffffff [0xfe]
bar 6: mem at 0xffffffffffffffff [0x3fffe]
dev: bochs-display, id ""
vgamem = 16777216 (16 MiB)
edid = true
xres = 1280 (0x500)
yres = 800 (0x320)
xmax = 0 (0x0)
ymax = 0 (0x0)
refresh_rate = 0 (0x0)
addr = 02.0
romfile = ""
romsize = 4294967295 (0xffffffff)
rombar = 1 (0x1)
multifunction = false
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class Display controller, addr 00:02.0, pci id 1234:1111 (sub 1af4:1100)
bar 0: mem at 0xffffffffffffffff [0xfffffe]
bar 2: mem at 0xffffffffffffffff [0xffe]
dev: vfio-pci, id ""
host = "0000:0b:00.0"
vf-token = "00000000-0000-0000-0000-000000000000"
sysfsdev = "/sys/bus/pci/devices/0000:0b:00.0"
x-pre-copy-dirty-page-tracking = "on"
display = "off"
xres = 0 (0x0)
yres = 0 (0x0)
x-intx-mmap-timeout-ms = 1100 (0x44c)
x-vga = true
x-req = true
x-igd-opregion = false
enable-migration = "auto"
x-no-mmap = false
x-balloon-allowed = false
x-no-kvm-intx = false
x-no-kvm-msi = false
x-no-kvm-msix = false
x-no-geforce-quirks = false
x-no-kvm-ioeventfd = false
x-no-vfio-ioeventfd = false
x-pci-vendor-id = 4098 (0x1002)
x-pci-device-id = 26641 (0x6811)
x-pci-sub-vendor-id = 4294967295 (0xffffffff)
x-pci-sub-device-id = 4294967295 (0xffffffff)
x-igd-gms = 0 (0x0)
x-nv-gpudirect-clique = 255 (0xff)
x-msix-relocation = "off"
addr = 01.0
romfile = ""
romsize = 4294967295 (0xffffffff)
rombar = 1 (0x1)
multifunction = true
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class VGA controller, addr 00:01.0, pci id 1002:6811 (sub 1462:3050)
bar 0: mem at 0x80000000 [0x8fffffff]
bar 2: mem at 0x90000000 [0x9003ffff]
bar 4: i/o at 0x1100 [0x11ff]
bar 6: mem at 0xffffffffffffffff [0x1fffe]
dev: via-mc97, id ""
addr = 0c.6
romfile = ""
romsize = 4294967295 (0xffffffff)
rombar = 1 (0x1)
multifunction = false
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class Class 0780, addr 00:0c.6, pci id 1106:3068 (sub 1af4:1100)
dev: via-ac97, id ""
audiodev = "none"
addr = 0c.5
romfile = ""
romsize = 4294967295 (0xffffffff)
rombar = 1 (0x1)
multifunction = false
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class Audio controller, addr 00:0c.5, pci id 1106:3058 (sub 1af4:1100)
bar 0: i/o at 0x1300 [0x13ff]
bar 1: i/o at 0x1030 [0x1033]
bar 2: i/o at 0x1034 [0x1037]
dev: vt8231-pm, id ""
addr = 0c.4
romfile = ""
romsize = 4294967295 (0xffffffff)
rombar = 1 (0x1)
multifunction = false
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class Bridge, addr 00:0c.4, pci id 1106:8235 (sub 1af4:1100)
bus: i2c
type i2c-bus
dev: smbus-eeprom, id ""
address = 87 (0x57)
dev: vt82c686b-usb-uhci, id ""
bandwidth = 1280 (0x500)
maxframes = 128 (0x80)
addr = 0c.3
romfile = ""
romsize = 4294967295 (0xffffffff)
rombar = 1 (0x1)
multifunction = false
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class USB controller, addr 00:0c.3, pci id 1106:3038 (sub 1af4:1100)
bar 4: i/o at 0x1060 [0x107f]
bus: usb-bus.1
type usb-bus
dev: vt82c686b-usb-uhci, id ""
bandwidth = 1280 (0x500)
maxframes = 128 (0x80)
addr = 0c.2
romfile = ""
romsize = 4294967295 (0xffffffff)
rombar = 1 (0x1)
multifunction = false
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class USB controller, addr 00:0c.2, pci id 1106:3038 (sub 1af4:1100)
bar 4: i/o at 0x1040 [0x105f]
bus: usb-bus.0
type usb-bus
dev: via-ide, id ""
gpio-in "" 2
gpio-out "isa-irq" 2
addr = 0c.1
romfile = ""
romsize = 4294967295 (0xffffffff)
rombar = 1 (0x1)
multifunction = false
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class IDE controller, addr 00:0c.1, pci id 1106:0571 (sub 1af4:1100)
bar 0: i/o at 0x1000 [0x1007]
bar 1: i/o at 0x100c [0x100f]
bar 2: i/o at 0x1010 [0x1017]
bar 3: i/o at 0x101c [0x101f]
bar 4: i/o at 0x1020 [0x102f]
bus: ide.1
type IDE
dev: ide-cd, id ""
drive = "ide1-cd0"
backend_defaults = "auto"
logical_block_size = 512 (512 B)
physical_block_size = 512 (512 B)
min_io_size = 0 (0 B)
opt_io_size = 0 (0 B)
discard_granularity = 512 (512 B)
write-cache = "auto"
share-rw = false
account-invalid = "auto"
account-failed = "auto"
rerror = "auto"
werror = "auto"
ver = "2.5+"
wwn = 0 (0x0)
serial = "QM00003"
model = ""
unit = 0 (0x0)
bus: ide.0
type IDE
dev: ide-hd, id ""
drive = "ide0-hd1"
backend_defaults = "auto"
logical_block_size = 512 (512 B)
physical_block_size = 512 (512 B)
min_io_size = 0 (0 B)
opt_io_size = 0 (0 B)
discard_granularity = 512 (512 B)
write-cache = "auto"
share-rw = false
account-invalid = "auto"
account-failed = "auto"
rerror = "auto"
werror = "auto"
ver = "2.5+"
wwn = 0 (0x0)
serial = "QM00002"
model = ""
cyls = 4063 (0xfdf)
heads = 16 (0x10)
secs = 63 (0x3f)
lcyls = 0 (0x0)
lheads = 0 (0x0)
lsecs = 0 (0x0)
bios-chs-trans = "lba"
rotation_rate = 0 (0x0)
unit = 1 (0x1)
dev: ide-hd, id ""
drive = "ide0-hd0"
backend_defaults = "auto"
logical_block_size = 512 (512 B)
physical_block_size = 512 (512 B)
min_io_size = 0 (0 B)
opt_io_size = 0 (0 B)
discard_granularity = 512 (512 B)
write-cache = "auto"
share-rw = false
account-invalid = "auto"
account-failed = "auto"
rerror = "auto"
werror = "auto"
ver = "2.5+"
wwn = 0 (0x0)
serial = "QM00001"
model = ""
cyls = 4161 (0x1041)
heads = 16 (0x10)
secs = 63 (0x3f)
lcyls = 0 (0x0)
lheads = 0 (0x0)
lsecs = 0 (0x0)
bios-chs-trans = "lba"
rotation_rate = 0 (0x0)
unit = 0 (0x0)
dev: vt8231-isa, id ""
gpio-in "pirq" 4
gpio-out "" 1
addr = 0c.0
romfile = ""
romsize = 4294967295 (0xffffffff)
rombar = 1 (0x1)
multifunction = true
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class ISA bridge, addr 00:0c.0, pci id 1106:8231 (sub 1af4:1100)
bus: isa.0
type ISA
dev: i8042, id ""
gpio-in "ps2-mouse-input-irq" 1
gpio-in "ps2-kbd-input-irq" 1
gpio-out "" 2
gpio-out "a20" 1
extended-state = true
kbd-throttle = false
kbd-irq = 1 (0x1)
mouse-irq = 12 (0xc)
dev: isa-fdc, id ""
iobase = 1008 (0x3f0)
irq = 6 (0x6)
dma = 2 (0x2)
fdtypeA = "auto"
fdtypeB = "auto"
fallback = "288"
bus: floppy-bus.0
type floppy-bus
dev: floppy, id ""
unit = 0 (0x0)
drive = "floppy0"
backend_defaults = "auto"
logical_block_size = 512 (512 B)
physical_block_size = 512 (512 B)
min_io_size = 0 (0 B)
opt_io_size = 0 (0 B)
discard_granularity = 4294967295 (4 GiB)
write-cache = "auto"
share-rw = false
account-invalid = "auto"
account-failed = "auto"
drive-type = "288"
dev: isa-serial, id ""
index = 0 (0x0)
iobase = 760 (0x2f8)
irq = 4 (0x4)
dev: isa-parallel, id ""
index = 0 (0x0)
iobase = 888 (0x378)
irq = 7 (0x7)
chardev = "parallel0"
dev: vt8231-superio, id ""
dev: mc146818rtc, id ""
gpio-out "" 1
base_year = 0 (0x0)
iobase = 112 (0x70)
irq = 8 (0x8)
lost_tick_policy = "discard"
dev: i8257, id ""
base = 192 (0xc0)
page-base = 136 (0x88)
pageh-base = -1 (0xffffffffffffffff)
dshift = 1 (0x1)
dev: i8257, id ""
base = 0 (0x0)
page-base = 128 (0x80)
pageh-base = -1 (0xffffffffffffffff)
dshift = 0 (0x0)
dev: isa-pit, id ""
gpio-in "" 1
gpio-out "" 1
iobase = 64 (0x40)
dev: isa-i8259, id ""
gpio-in "" 8
gpio-out "" 1
iobase = 160 (0xa0)
elcr_addr = 1233 (0x4d1)
elcr_mask = 222 (0xde)
master = false
dev: isa-i8259, id ""
gpio-in "" 8
gpio-out "" 1
iobase = 32 (0x20)
elcr_addr = 1232 (0x4d0)
elcr_mask = 248 (0xf8)
master = true
dev: mv64361-pcibridge, id ""
addr = 00.0
romfile = ""
romsize = 4294967295 (0xffffffff)
rombar = 1 (0x1)
multifunction = false
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class Host bridge, addr 00:00.0, pci id 11ab:6460 (sub 1af4:1100)
dev: mv64361-pcihost, id ""
index = 0 (0x0)
x-config-reg-migration-enabled = true
bypass-iommu = false
bus: pci.0
type PCI
dev: mv64361-pcibridge, id ""
addr = 00.0
romfile = ""
romsize = 4294967295 (0xffffffff)
rombar = 1 (0x1)
multifunction = false
x-pcie-lnksta-dllla = true
x-pcie-extcap-init = true
failover_pair_id = ""
acpi-index = 0 (0x0)
x-pcie-err-unc-mask = true
x-pcie-ari-nextfn-1 = false
class Host bridge, addr 00:00.0, pci id 11ab:6460 (sub 1af4:1100)
dev: mv64361, id ""
gpio-in "gpp" 32
gpio-out "sysbus-irq" 1
mmio ffffffffffffffff/0000000000010000
This starts as soon as the workbench appears - which is also when Amidock loads - and you can see/feel the slowness as stdio fills up with the messages. Are the 2 host bridges meant to have the same details? "Bus 0, device 0, function 0:" etc
(qemu) info pci
Bus 0, device 0, function 0:
Host bridge: PCI device 11ab:6460
PCI subsystem 1af4:1100
id ""
Bus 0, device 1, function 0:
VGA controller: PCI device 1002:6811
PCI subsystem 1462:3050
IRQ 9, pin A
BAR0: 64 bit prefetchable memory at 0x80000000 [0x8fffffff].
BAR2: 64 bit memory at 0x90000000 [0x9003ffff].
BAR4: I/O at 0x1100 [0x11ff].
BAR6: 32 bit memory at 0xffffffffffffffff [0x0001fffe].
id ""
Bus 0, device 2, function 0:
Display controller: PCI device 1234:1111
PCI subsystem 1af4:1100
BAR0: 32 bit prefetchable memory at 0xffffffffffffffff [0x00fffffe].
BAR2: 32 bit memory at 0xffffffffffffffff [0x00000ffe].
id ""
Bus 0, device 3, function 0:
Ethernet controller: PCI device 10ec:8139
PCI subsystem 1af4:1100
IRQ 9, pin A
BAR0: I/O at 0x1200 [0x12ff].
BAR1: 32 bit memory at 0xffffffffffffffff [0x000000fe].
BAR6: 32 bit memory at 0xffffffffffffffff [0x0003fffe].
id ""
Bus 0, device 12, function 0:
ISA bridge: PCI device 1106:8231
PCI subsystem 1af4:1100
id ""
Bus 0, device 12, function 1:
IDE controller: PCI device 1106:0571
PCI subsystem 1af4:1100
IRQ 14, pin A
BAR0: I/O at 0x1000 [0x1007].
BAR1: I/O at 0x100c [0x100f].
BAR2: I/O at 0x1010 [0x1017].
BAR3: I/O at 0x101c [0x101f].
BAR4: I/O at 0x1020 [0x102f].
id ""
Bus 0, device 12, function 2:
USB controller: PCI device 1106:3038
PCI subsystem 1af4:1100
IRQ 9, pin D
BAR4: I/O at 0x1040 [0x105f].
id ""
Bus 0, device 12, function 3:
USB controller: PCI device 1106:3038
PCI subsystem 1af4:1100
IRQ 9, pin D
BAR4: I/O at 0x1060 [0x107f].
id ""
Bus 0, device 12, function 4:
Bridge: PCI device 1106:8235
PCI subsystem 1af4:1100
id ""
Bus 0, device 12, function 5:
Audio controller: PCI device 1106:3058
PCI subsystem 1af4:1100
IRQ 9, pin C
BAR0: I/O at 0x1300 [0x13ff].
BAR1: I/O at 0x1030 [0x1033].
BAR2: I/O at 0x1034 [0x1037].
id ""
Bus 0, device 12, function 6:
Class 1920: PCI device 1106:3068
PCI subsystem 1af4:1100
IRQ 9, pin C
id ""
Bus 0, device 0, function 0:
Host bridge: PCI device 11ab:6460
PCI subsystem 1af4:1100
id ""
(qemu)
|
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 7/16 23:51
#15
|
Not too shy to talk
|
@MartinW Quote: MartinW wrote:
Radeon R9 270X may or may not have a usable solution right now. I think it is workable from a "does it function" point of view as long as you disable interrupts. This as Joerg pointed out is likely no good longer term. I'm a little confused on replies from Hans. I have a suspicion from the explanation of how the interrupt handlers should return 1 or 0, the v5 drivers might not work and the earlier ones would.
Radeon HD v5 drivers are not available for Pegasos2 machines, so we are limited to (max) version 3 drivers. Quote: From a practical point of view, the v5 driver is needed to control the fans on the R9 270X regardless of the interrupt situation and I've reached my spending limit, at least for this month so I'm not prepared to buy the newer driver to find out whether the interrupt code works or not. Maybe next month.
This is an issue that others have had with Radeon cards in real machines. I have never had this issue with a R270, R270x or RX580 in a X5000, or the R270 being used for passthrough.
|
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 7/15 21:56
#16
|
Not too shy to talk
|
Quote: MartinW wrote:
3. CMD Line as above. Current master plus OSDN patched master. INT's = Yes. Same as before can't get into workbench before the system hangs.
No. 3 works for me (OSDN repo + Interrupts on) however I do not see any difference between this and using the master repo with no patches. Is the version number different in the OSDN code? if it isnt, how can i tell that Im using the correct binary? My startup script is as follows
qemu-system-ppc \
-L pc-bios -M pegasos2 -bios pegasos2.rom -vga none \
-cpu 7457 -m 1024 \
-rtc base=localtime -serial mon:stdio -display sdl \
-drive media=disk,format=raw,file=hdf/peg2.img \
-drive media=disk,format=raw,file=hdf/apps.hdf \
-device vfio-pci,host=0b:00.0,multifunction=on,x-vga=on,bus=pci.1,addr=1 \
-device bochs-display,romfile="",bus=pci.1 \
-device rtl8139,netdev=net0,bus=pci.1 -netdev user,id=net0
|
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 7/14 22:33
#17
|
Not too shy to talk
|
@MartinWQuote:
@derfs - how did you get your R290 working? Did it have 2GB of video Ram? I would be interested in the values you ended up entering.
I have a 270 with 2Gb ram so the figures i entered are the ones you gave me.
|
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 7/11 22:57
#18
|
Not too shy to talk
|
@white
No one is willing to add voodoo3 emulation to qemu, and the only real benefit over sm501 would be using warp3d. sm501 emulation at least gets you 64mb of gfx memory.
|
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 7/11 15:35
#19
|
Not too shy to talk
|
@white Quote: white wrote:
@MartinW
I couldn't figure out if the answer was for me 
I guess so.
I have the ryzen 5800x so it doesn't have the integrated graphics card like the 5600x for example.
In the bios in addition to AMD V-T support
i also have this option i guess is for graphics card.
pci sub-system settings
if system has sr-iov capable pcie devices this option enable or disable single root io virtualization support.
But I wanted to know if you need a specific adapter etc.
To be able to insert one of the graphics cards you mentioned into the second slot.
Thank you. My 5600X does not have integrated graphics, so your setup will be very similar to mine. The main BIOS settings would be to make sure that SVM Mode is on as that turns on virtualization technology for Ryzen. You have 2 PCIe x16 slots on that motherboard, so you would put your main gfx card in the long silver x16 slot, and the gfx card you want to use for passthrough in the second x16 slot. Any PCIe card will fit, but from the ones that we have tested the 5450 and R9 270 are PCIe cards and will not need an adapter. If you want to use older gfx cards such as Voodoo3 or 9250 then you will need an adapter as these are most likely PCI cards. My setup is a Radeon RX 580 as main graphics card, and then the Radeon R9 270 in the second slot for passthrough.
|
|
|
|
|
|
Re: What the fastest possible x64 emulation way of OS4 today ?
|
Posted on: 7/10 20:56
#20
|
Not too shy to talk
|
@kas1e qemu (R9 270)
Cow3D_NoInfoBar
os4 - 80 fps
nova - 1130 fps
Ragemem (video only)
Video Bus
READ: 8 MB/Sec
WRITE: 151 MB/Sec
Shaderjoy (395x578)
yet_another_torus.frag - 57 fps
new_buffer.frag - 1380 fps
ring_twister.frag - 630 fps
X5000/20 (R9 270x)
Cow3D_NoInfoBar
os4 - 389 fps
nova - 1454 fps
Ragemem (video only)
Video Bus
READ: 36 MB/Sec
WRITE: 540 MB/Sec
Shaderjoy (395x578)
yet_another_torus.frag - 53 fps
new_buffer.frag - 1869 fps
ring_twister.frag - 672 fps
Its not the same gfx cards, but they are close.
|
|
|
|
|
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
