If you have freezes with Yes, try this hack, PatchWaitTOF that removes the hangs of apps, and total freeze if you're using that Synchronize with refresh flag in GUI prefs. (But do rather switch that off.)
Software developer for Amiga OS3 and OS4. Develops for OnyxSoft and the Amiga using E and C and occasionally C++
After having tried to make an RX 580 work in my X1000 and failed, I purchased an RX 560 and it work with the CFE hack.
Still some weid freezes in Emotion (video stops playing). I have installed Deniil's patch and reverted the INTERRUPTS to YES. We'll see how it comes along.
I don't see soft-reset as a definitive part of AmigaOS. It wasn't part of the original 68K AmigaOS. They only really became a thing with OS 4, because full reboots take so long.
One thing that was definitive of AmigaOS was the RAD drive. And Ramb0. Which OS4 people still used. You could do a soft reboot and it would survive. This doesn't happen with a cold reboot. Unless the firmware erases memory on reset I would consider this a bug. Because Exec always checked the memory for a existing ExecBase which a RAD would depend upon. If Exec isn't doing that but instead creating a new one every time it's not an Amiga Exec.
Quote:
I've also advocated for making the Early Startup Menu work without needing a reboot. That was met with pretty fierce resistance.
Hi, I have on my SAM460ex and a radeonHD (r7-250) a WB feeeze on startup. If I set (THX Spectre660) INTERRUPT=Yes and composition=OFF it loads WB ok and system runs ok.
Just found your comment. I have the same issue with my X1000 and R7 250. For me the issues started when I installed Update 2.
Did you have the same issue with Update 1? And is your issue confined to Update 2?
I noticed that the freezes are less (or disappear?) when the monitor driver in DEVS:Monitors has the correct name for the graphics card.
The Radeon R7 250 freezes almost immediately when plugged in if TOOL TYPES entry in the monitor driver is not changed accordingly. Once I put the name I could read in Ranger, I almost get no freezes. The 560 behaves similarly.
And the freezes that appear, only the gremlins know what is causing them. Since the Enhancer update the system has become more unstable for me.
I have nothing constructive to add to the discussion, as I'm still sporting R9 270 cards in my two X1000s. But I do want to thank you all for continuing to test and push ahead with the RX cards and drivers and patches and CFE workarounds. We may get there yet, with full speed, full resolution video and no hangups, and so at least one of my machines may get a new graphics card and some new capability to make me smile.
(Gigabyte R9 270X) CMPLENGHT=15 BOARDNAME=Radeon HD Oland
(Sapphire HD 7970) CMPLENGHT=21 BOARDTYPE=Radeon HD 7900 Series
In SYS:Storage/Monitors I have a monitor file for each of the above, I just remove the extension of the name and put it in DEVS:Monitors. e.g. from "NEC EA 224WMi.RX550" to "NEC EA 224WMi", and swap it with the one in DEVS:Monitors (which will be renamed accordingly).
Maybe I should try one single monitor file for each monitor and put all the tool types as above in one single "Monitor driver" per Display and disable the ones I don't need. That would remove sum clutter for sure.
I find it very confusing when the monitor files are named after the Graphics card which is inserted, which seems to be the default setting when installing AmigaOS 4.1FE.
Edited by Tuvok on 2023/8/20 12:23:24 Edited by Tuvok on 2023/8/20 12:24:32
I find it very confusing when the monitor files are named after the Graphics card which is inserted, which seems to be the default setting when installing AmigaOS 4.1FE.
The "monitor" files are gfx card files, only still called monitor files for historic reasons when there were no gfx cards yet but only the OCS/ECS/AGA chipsets and the monitor files were used for different resolutions (NTSC, PAL, A2024, etc.) on the same gfx hardware.
Perhaps more emphasis should be placed on usability. Making the system confusing just for the sake historical reasons seems abstruse to me.
Other changes have already been made to the system without taking into account the historical aspects, e.g. removing the utilities and WBStartup drawers.
And that was a good thing.
Apart from that, Commodore also made changes from AmigaOS 1.x to 2.x and 3.x and some were radical.
(Gigabyte R9 270X) CMPLENGHT=15 BOARDNAME=Radeon HD Oland
(Sapphire HD 7970) CMPLENGHT=21 BOARDTYPE=Radeon HD 7900 Series
It seems strange that you use the boardname "Radeon RX Polaris 12" for your ATI R9250, and the boardname "Radeon 9250" for your AMD RADEON RX550), but maybe that was just a typo when entering the info here?
But maybe more important:
You have CMPLENGTH=19 for both of the boardnames "Radeon RX Polaris 12" and "Radeon RX Polaris 11". Those names are 20 characters long each. So in effect you have created two monitor files which will be seen as one and the same, i.e. a random one will be picked, because the CMPLENGTH tells the distinguishing code to only compare as far as the 19th character, which means you have two monitors with the name "Radeon RX Polaris 1" (the "1" or "2" at the end are not seen in the comparison.
@nbache For the old ATIRadeon driver using CMPLENGTH=6 was required, for example on the AmigaOS 4.x CDs where you can't change it, to match all Radeon#? cards supported by it. For the Radeon HD and RX drivers using CMPLENGTH=9 should work the same way: You only need one monitor file for all HD cards, one for all RX cards and can keep them in DEVS:Monitors even if you (currently) don't have a supported gfx card installed. If you use it that way make sure you don't have the default monitor file for the old ATIRadeon driver in DEVS:Monitors as well since with CMPLENGTH=6 it will match Radeon HD and RX cards too and if the old ATIRadeon driver accesses a HD or RX gfx card that might cause some problems. If you need support for old cards using the ATIRadeon driver using something like "BOARDNAME=Radeon 9250" and "CMPLENGTH=8" instead will fix such possible problems.
Using more than one Radeon HD or RX monitor file without, or a longer CMPLENGTH, in DEVS:Monitors is only required if you want to use 2 HD or 2 RX cards at the same time, but that requires other changes as well, for example using PCIGraphics.card for the 2nd.
It seems strange that you use the boardname "Radeon RX Polaris 12" for your ATI R9250, and the boardname "Radeon 9250" for your AMD RADEON RX550), but maybe that was just a typo when entering the info here?
You are right, I typed it in on an Android phone and the site did not work properly, thanks for pointing that out, I will edit my previous post.
Quote:
But maybe more important:
You have CMPLENGTH=19 for both of the boardnames "Radeon RX Polaris 12" and "Radeon RX Polaris 11". Those names are 20 characters long each. So in effect you have created two monitor files which will be seen as one and the same, i.e. a random one will be picked, because the CMPLENGTH tells the distinguishing code to only compare as far as the 19th character, which means you have two monitors with the name "Radeon RX Polaris 1" (the "1" or "2" at the end are not seen in the comparison.
At least that's how I have understood it.
Well spotted. I checked on the AmigaOne and the name of the cards in Rangers is without the space between “Polaris” and the number. I wrote the post by memory without checking.
Up until now, I hadn’t read anywhere what you and Joerg explained, good to know about the workings of CMPLENGTH, I will make changes accordingly in my system.
Edit: edit Niels:
Are you one of the responsible persons for the wiki? Maybe it would be a good idea to edit and explain this. I’ll be glad to offer my help, maybe writing the text and you will only have to redact it, if you are short on time. Unless that is, that the wiki is not being edited for political reasons, to force some higher ups to collaborate to bake bread, instead of “competing” for the crumbs.
I checked again on the AmigaOS_Manual:_Workbench_Monitors wiki on amigaos.net and I could not find such information, neither did I find anything in the System Documentation drawer.
Btw, what is the correct tooltype name: "BOARDNAME" or "BOARDTYPE"?
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
Donate
