Radeon RX cards on X1000

@ddni

I am trying to add a full step by step guide, but my system keeps freezing

@ddni (and all who like to try)

If you find mistakes, please shout

1) From a running system (RadeonHD based)
1.1) Adapt your monitor file (thanks to @Spectre660)


2) Reboot and enter CFE
2.1) from the prompt

(Make sure that ide0.0 is your Workbench boot partition or change it accordingly)

3) Turn off (plug off) the machine

4) Open the case
4.1) Set jumper GPIOLV10 (between the back ports and RAM sockets "2" and "3")
4.2) Switch the graphics board to the RX

5) Turn on the machine

NB: If you have a (working) PuTTY setup on a PC/Linux machine you can fix mistakes (as long as CFE stops during boot because of an error, otherwise you can only watch)
NB2: There is a way to fix little mistakes with PuTTY, you only need to disconnect your boot partition/hdd and CFE will error during init and throw you to a command prompt.

Steps to return to Radeon HD (works ONLY with a PuTTY connection or by clearing CMOS, the jumper next to GPIOLV10):
1) Turn off the machine
1.1) Remove the GPIOLV10 jumper
1.2) Switch the graphics board to the HD
1.3) Remove your boot hdd/ssd (unplug the power cord) - only do this if you got a working PuTTY serial connection to a Win/Linux system (see also NB2 above)

2) Turn on your machine
2.1) Have your PuTTY serial connection ready
2.2) When CFE errors out on finding the boot device, you can redo your STARTUP variable from the PuTTY connection (or redo the whole lot if you cleared CMOS before)

3) Turn off the machine again
3.1) Replug the power to your boot device/hdd

4) Reboot a last time and you should be back to RadeonHD

edit:
- added some more info
- rephrased some steps
- added INTERRUPT=No to the monitor file, since it seems to cure the random freezes

@Raziel

Yep, just did a test with SDL_benchmark...freezing the gfx board every time

Thanks are the characters surrounding the variable a ‘ or a “?
I was using “

@ddni

The whole command is encased in '
Within the command it's "

@Raziel

It is possible that the freezing is caused the GART stuff.
Doubt that the Radeon RX was ever tested on the X1000.

Mantis bug report time ..........

@Raziel

Thanks after changing the menu to auto, can CFE still be accessed in early boot with F?

@ddni

Nope, you need to save your settings, clear CMOS, redo your settings to get back to the F boot menu

@Spectre660

Probably...any way to turn it off?

Going back to Radeon HD...too flaky, too much freezes, not worth the hassle

@Raziel

Only by using a driver version before or up to 1.19 or so .
Worth reporting the issue though .
Hopefully we may also get some feedback from Goos and imagodespira later on too .

@Spectre660

And now RadeonHD.chip keeps crashing and i cannot reach WB anymore...yeah, why not? Never again...

Even from the installation CD??? Are you kidding me...

Ouch!!!

Think it might be wise to hold off with this hack for a while…
Perhaps AEON or Hans is reading this thread and would care to comment?

@ddni

Holy fucking shit, that was unnecessarily scary.


Not to self:
Don't ever fucking do that again...

...

for all of you who wants to try out

KEEP THIS IN MIND!!!

The RadeonHD.chip EXPLICITELY DOES !!! NOT !!! WANT to be booted forced serial!!

That means, if you go back to the RadeonHD driver, REMOVE THE GPIOLV10 JUMPER or you'll end up with a crashing driver!!!


YOU (and me) HAVE BEEN WARNED!!!

...

Lost a year or two there...

Ok, so you forgot to remove the jumper when you cleared cmos and went back RadeonHD? Sounds avoidable.

@Raziel
Quote:
Hence my post #2 I've been down those kind of roads before. Glad you got it working again.

@ddni

Nope, never cleared cmos, found a way to reset my settings without that step

You only have to disconnect your boot device (ide0.0), then cfe will error out on finding the boot device (doh) and with a PuTTY setup you can then redo your original "menu" STARTUP and are good to go.

@ddni

Quote:
Sorry, but I have no idea what's going on. I've never tried this myself, and my X1000 is in a different country.


Hans

@Hans

Thanks for replying.

So I just tried this with a PowerColor Red Devil RX590.
AmigaOS4 ESP2.2 boots and seems to work.
GPU fans running at full speed though?

Emotion VA plays Big Buck Bunny 1080 but I still get >60% CPU use.

Doom3 1.5.2 beta 1 loads, runs the timedemo and exits cleanly.
Reborn to Castle Wolfenstein runs with some purple speckles. 1080p fullscreen.

Further Testing.

@ddni
Va issues probably because of not correctly installed va libs (not only va.library should be installed, but also those rom-bios files). I do have 3% cpu loading with bunny on my x5000.

Purple issues in wolf maybe because of 16/32 bit differences with destop/game

@kas1e

rom bios files?
Do you mean Libs:VA/RadeonRX_drv_video.library ?