Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
8 user(s) are online (5 user(s) are browsing Forums)

Members: 1
Guests: 7

rjd324, more...

Support us!

Headlines

Forum Index


Board index » All Posts (derfs)




Re: RadeonRX.chip
Not too shy to talk
Not too shy to talk


Quote:
derfs wrote:
If you check the last tab in Updater it will show what software is linked to your account - look for Enhancer 2.2.


If you have not registered your copy of Enhancer yet then it will not allow you to download updates via updater. Register your copy at https://www.amisphere.com/register_product.php

Go to top


Re: RadeonRX.chip
Not too shy to talk
Not too shy to talk


@hotrodQuote:
hotrod wrote:Using "Updater" I get that RadeonRX.chip 2.12 is available for update and I got 2.11 installed. Choosing to download gives the message "RadeonRX.chip is not enabled for download on this AmiSphere account".

Why?


RadeonRX.chip 2.12 is available to download for Amisphere accounts that have Enhancer v2.x. If you check the last tab in Updater it will show what software is linked to your account - look for Enhancer 2.2.

Go to top


Re: Pegasos2 with RadeonHD/RX via bridge
Not too shy to talk
Not too shy to talk


Radeon RX580 on Win11.

Test failedYour graphics card drivers may be faulty.
WritePixelArray9499.648 MiB/(took 0.322000 seconds).
Test failedYour graphics card drivers may be faulty.
ReadPixelArray9500.283 MiB/(took 0.228000 seconds).

FillRect:
Size                Time (s)           Ops/s        MPixel/s
(1616)               1.124     2130674.377         520.184
(3232)               1.041     2134486.071        2084.459
(6464)               1.085     2047926.267        7999.712
(128128)             1.110     1811665.766       28307.278
(256256)             1.084      379595.018       23724.689
(512512)             1.109      308310.189       77077.547
(10241024)           1.096      184306.569      184306.569

BltBitMap
:
Size                Time (s)           Ops/s        MPixel/s
(1616)               1.072     2081001.866         508.057
(3232)               1.110     2061550.450        2013.233
(6464)               1.128     1969858.156        7694.758
(128128)             1.062     1743564.972       27243.203
(256256)             1.105      628393.665       39274.604
(512512)             1.114      158302.513       39575.628
(10241024)           1.109       39753.832       39753.832

OverlappedBltBitMap
:
Size                Time (s)           Ops/s        MPixel/s
(1616)               1.140      104230.702          25.447
(3232)               1.088      109799.632         107.226
(6464)               1.091      108912.007         425.438
(128128)             1.104       99146.739        1549.168
(256256)             1.106       79723.327        4982.708
(512512)             1.110       39639.640        9909.910
(10241024)           1.721       11621.150       11621.150

Composite
:
Size                Time (s)           Ops/s        MPixel/s
(1616)               1.109     2311533.814         564.339
(3232)               1.109     2290130.748        2236.456
(6464)               1.025     2167804.878        8467.988
(128128)             1.117     1915464.637       29929.135
(256256)             1.180      553838.136       34614.883
(512512)             1.040      148370.192       37092.548
(10241024)           1.124       34803.381       34803.381
NOTE
Compositing (or alpha blendingused premultiplied alpha mode.

CompositeSrcMask:
Size                Time (s)           Ops/s        MPixel/s
(1616)               1.024     1356201.172         331.104
(3232)               1.022     1358855.186        1327.007
(6464)               1.204     1318224.252        5149.313
(128128)             1.035     1192699.517       18635.930
(256256)             1.142      542591.068       33911.942
(512512)             1.063      141237.065       35309.266
(10241024)           1.119       33205.541       33205.541
NOTE
The source mask's alpha channel was multiplied by the source bitmap's alpha channel.
NOTEThe source bitmap's alpha channel was premultiplied.

Random:
Time (s)               Ops/s        MPixel/s
       1.642       48721.072       16296.230

------------------------------------------------------------
Some tests failed, so the result cannot be submitted to the results server

Go to top


Re: AHI and SB128 (CT4760)
Not too shy to talk
Not too shy to talk



Go to top


Re: Qemu + VFIO GPU RadeonRX 550 + AmigaOS4 extremely slow
Not too shy to talk
Not too shy to talk


@nikitas

Just to check - have you gone into Power prefs and changed the gfx card settings to fastest possible?

Go to top


Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
Not too shy to talk
Not too shy to talk


@MamePPCA1

Even if you boot from USB, the X5000 will use the boot details from a different partition if the "boot priority" of that partition is higher.

Boot from your USB, and check what the boot priority number is for all partitions, including the USB, and post them here.

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
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.

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
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.

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
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.

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
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.

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
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. = [execOpenDevice("sii3112ide.device",0,0x6793C610,0x00000000) = [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. = [execOpenDevice("input.device",0,0x66F7D1E0,0x00000000) = [123uS]
00009 : 
Mounter         :        [execCloseDevice("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. = [execOpenResource("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. = [execOpenLibrary("dos.library",39) [55uS]
00021 DH1/SmartFilesystem 1.293  o.k. = WaitPkt(0x00000000)
00022 DH1/SmartFilesystem 1.293  o.k. = [execOpenResource("newfilesystem.resource") [16uS]
00023 DH1/SmartFilesystem 1.293  o.k. = [execOpenLibrary("expansion.library",51) [26uS]
00024 DH1/SmartFilesystem 1.293  :        [execCloseLibrary("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  :        [execCloseLibrary("dos.library") [6uS]
00027 DH1/SmartFilesystem 1.293  : <----- PRIVATEInternalRunCommand(""ARG:"") = [103 (0x00000067)]
00028 : 
Mounter         FAIL DeviceProc("DH1:") [20169uS]
00029 : 
Mounter         o.k. = [execOpenDevice("input.device",0,0x66F7D0C0,0x00000000) = [115uS]
00030 Mounter         :        [execCloseDevice("input.device") [14uS]
00031 Mounter         :        [execCloseDevice("sii3112ide.device") [14uS]

Go to top


Re: Qemu Pegasos II interrupts issue
Not too shy to talk
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.

Go to top


Re: RadeonHD V.5 driver
Not too shy to talk
Not too shy to talk


@sailor

Its available from the Amigakit website

https://www.amigakit.com/radeonhd-driver-version-p-1107.html

Go to top


Re: Opening the 1st bootmenu automatically (X5000)
Not too shy to talk
Not too shy to talk


@Gregor

try looking at https://wiki.amigaos.net/wiki/UserDoc:BIOS to see if anything will help

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
Not too shy to talk


@balaton

I have always used the weilnetz builds on windows and have never had an issue.

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
Not too shy to talk


@All

QEMU 8.2.0 has been released and among the changes is the ability to use BBoot v0.5+ with the amigaone machine, removing the need for a u-boot bios image.

For Windows the downloadable installer is currently for 8.2.0-rc4, which will give you the same functionality apart from the bump in version number!

QEMU 8.2.0 source
QEMU Binaries for Windows (64 bit)
Instructions for Booting AmigaOS 4.1 on QEMU with BBoot

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
Not too shy to talk


@balaton

Compiled current qemu master for windows and Amigaone machine with bboot working as intended. Good job!

Go to top


Re: PCI virtio driver development
Not too shy to talk
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.

Go to top


Re: Running my OS4 games on QEmu
Not too shy to talk
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.

Go to top


Re: Command to see CFE/UBOOT variables
Not too shy to talk
Not too shy to talk


@rjd324

https://wiki.amigaos.net/wiki/UserDoc:BIOS

Quote:
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.

Go to top



TopTop
(1) 2 3 4 ... 13 »




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project