»

[560SL]

Been trying to install my recently purchased Radeon 9250 card into the A4000T today, but without success. Installation procedure is kindof not-so-intuitive in my opinion, feels more like bringing order into a hippie- happening to get things working.

Anyway, followed the procedures as far up to the point where I am supposed to "click onto" the Radeon icon in Devs/Monitors. What happens then is I get a Software Failure, Program failed on Radeon.

The following has been installed:
- Picasso96 2.1b
- MM_CD_UP2.1

CVision3D in Devs/Monitors has been renamed to Radeon and tooltype set to Radeon. Radeon.card is in Libs:Picasso96. So it should kindof work now.....

I get the following log from SnoopDos before the program failure:
Count Process Name Action Target Name Options Res.
----- ------------ ------ ----------- ------- ----
1 WBL ChangeDir SystemA4k:P96Backup/Devs/Mo
2 WBL Load Radeon OK
3 WBL ChangeDir SYS:
4 Radeon ChangeDir SystemA4k:P96Backup/Devs/Mo
5 ramlib Load LIBSicasso96/rtg.library OK
6 Picasso96 Open ENV:Picasso96/AmigaVideo Read OK
7 Picasso96 Open ENV:Picasso96/Debug Read OK
8 Picasso96 Open ENV:Picasso96/BlackSwitchin Read OK
9 Picasso96 Open ENV:Picasso96/DirectColorMa Read OK
10 Picasso96 Open ENV:Picasso96/DoNotSetMMU Read OK
11 Picasso96 Open ENV:Picasso96/ShowModes Read OK
12 Picasso96 Open ENV:Picasso96/PlanarOnlyDIP Read OK
13 Picasso96 Open ENV:Picasso96/DisableAmigaB Read OK
14 Picasso96 Open ENV:Picasso96/PlanesToFast Read OK
15 Picasso96 Open ENV:Picasso96/Experimental Read OK
16 Picasso96 Open ENV:Picasso96/EnableBootVGA Read OK
17 ramlib Load LIBS:Picasso96/fastlayers.l OK
18 Radeon Open Radeon.info Read OK
19 Radeon ToolType QUIET Fail
20 Radeon ToolType BOARDTYPE OK
21 Radeon ToolType SETTINGSFILE OK
22 Radeon ToolType MEMORYCLOCK Fail
23 Radeon ToolType SOFTSPRITE Fail
24 Radeon ToolType BIGSPRITE Fail
25 Radeon ToolType BORDERBLANK Fail
26 Radeon ToolType DISPLAYCHAIN Fail
27 Radeon ToolType IGNOREMASK OK
28 Radeon ToolType NOPLANAR2CHUNKYBLITS Fail
29 Radeon ToolType NOBLITTER Fail
30 Radeon ToolType SYSTEM2SCREENBLITS Fail
31 Radeon ToolType QUIET Fail
32 Radeon ToolType OVERCLOCK Fail
33 Radeon ToolType GRANTDIRECTACCESS Fail
34 Radeon ToolType FAKENATIVEMODES Fail
35 Radeon Load LIBSicasso96/Radeon.card OK
36 Radeon Open ENV:Mediator/RadeonMem Read Fail
37 Radeon Open ENV:Mediator/RadeonInt Read Fail
38 ramlib Load LIBSci.library OK
39 ramlib Open ENVARC:Mediator/MMU Read OK
40 ramlib Open ENVARC:Mediator/NoCache Read Fail
41 ramlib Open ENVARC:Mediator/Warp3D Read OK
42 ramlib Open ENVARC:Mediator/Emulation Read Fail
43 ramlib Open ENVARC:Mediator/PatchInt Read Fail
44 ramlib Open ENVARC:Mediator/Buster Read Fail
45 ramlib Open S:Vendors.txt Read OK

pciinfo reports the following:
Pci Device 1:
VendorID: $1002
VendorName: ATI Technologies Inc. / Advanced Micro Devices, Inc.
DeviceID: $5960
DeviceName: RV280 Radeon 9200 Pro
ClassCode: $30000
RevisionID: $1
InterruptPin: 4
SubsystemVendorID: $1092
SubsystemID: $160
MemSpace0: $50000000 - $5fffffff
IOSpace1: $40c06000 - $40c060ff

Finally, the following line is in S:Vendors.txt:
5960 RV280 Radeon 9200 Pro

So I cant fully figure out what is happening when the Radeon icon is clicked, but it seems things start to go astray when the Vendors.txt has been read (I see it because a huge amount of memory is consumed), and this is the last log- entry that SnoopDos reports. One thing that worries me a bit is the possibility that there are debris left from the Voodoo installation, basically I just re- installed MM_CD_UP2.1 and followed the instructions in the RadeonGuide text file. Would be much nicer to install on a fresh system, but Id hate to do a complete system re- installation.

So if anyone have any idea what the problem could be? Like weird ENV/ARC settings or something like that? Any hints are welcome

[danbeaver]

You are correct, it is not intuitive. The install went wrong or you didn't reboot after each step. Yes, it is fine to rerun the install multiple times; it just copies files to the Libs directory and sets up some ENV/ENVARC settings. All are easy to find and delete. Run the install again and after each step try a fresh reboot.

This should work unless you have an incompatible 9250 card (not likely if it came from Elbox or Amigakit). You can ask Elbox for help if you registered the Mediator, but don't expect a reply.

[560SL]

Originally Posted by danbeaver

You can ask Elbox for help if you registered the Mediator, but don't expect a reply.

Thats all part of the not-so-intuitive installation process Alright, strongly considering a complete system re- installation.

[Bamiga2002]

Did you use MedConfig to configure Med+Radeon ?

You could also try going here http://www.pcidatabase.com/reports.p...=tab-delimeted and save the list as "S:Vendors.txt"

EDIT: corrected URL

[slaapliedje]

The information for my Devs/Monitors/Radeon file is;

(BorderBlank=System)
(MemoryClock=0)
BigSprite=NO
BoardType=Radeon
DisplayChain=Yes
FakeNativeModes=NO
FontsFix=NO
GrantDirectAccess=NO
IgnoreMask=Yes
NoBlitter=NO
NoPlanar2ChunkyBlits=NO
OverClock=NO
SettginsFile=SYS:Devs/Picasso96Settings
SoftSprite=NO
System2ScreenBlits=NO

Not sure why it amuses me that the NOs are all capitalized and the Yes, only has the Y as upper case...

Anyhow, that's that, my question would be, anyone know what all those options do and if one of those could be why AmiDOCK makes my system lock up? It seems that it's running pretty much fine without AmiDOCK loaded...

slaapliedje

[560SL]

Just made a new system installation this evening, from scratch 3.1->3.9+BB1+BB2. Then installing P96 2.1b and MM_CD_V2.1 and followed the RadeonGuide. Clicking on Devs/Monitors/Radeon now works without System Failure, but I cant get any board to attach to in P96 Prefs program.

I had exactly the same problem when installing the Voodoo card (attach to board/no board) but somehow I got it working then. I just cant remember how...

[slaapliedje]

Check Libs/Picasso96 to see if there is a Radeon.card file in there. I think that's where I had that issue as well.

slaapliedje

[Bamiga2002]

You could also try the beta 10 pci.library -> http://www.elbox.com/download/beta/pci.library

[560SL]

Thanks, will try the beta and see if this helps.

Would really help to understand what the P96Settings program is doing to find boards to attach to. Gonna see if Snoopdos can reveal anything.

[Bamiga2002]

What are your Picasso96 env-variables? Do you have MMU=Yes?
I haven't ever tried my Radeon separately, only together with a Voodoo3 and it required MMU=Yes. But this was on an A1200. Since then I've removed the Radeon because it's of no use since doesn't support Warp3D.

[Bamiga2002]

There's also a tad newer Picasso96-package available, get it here

[560SL]

Did some further testing this evening with no success. Reinstalled P96_2.1c (thanks for the info). Even reinstalled Mediator system files from CD + the 2.0 and 2.1 updates.

I noticed that I had previously missed to set BOARDTYPE to Radeon in the monitor file, but when set, I get the System Failure. Last thing Snoopdos says is that Radeon (monitor file) is doing OpenLib on Libs:Picasso96/Radeon.card. I did not try to use v10 of pci.library (yet).

In ENVARC:Picasso96 I have a variabe DoNotUseMMU which is set to No. ENVARC:Mediator has a variable called MMU, this is also set to No.

All thing is pointing to to install my Voodoo 5 5500 back again, as said, there are drivers to support Warp3D.

[Vanilla]

Originally Posted by 560SL

Anyway, followed the procedures as far up to the point where I am supposed to "click onto" the Radeon icon in Devs/Monitors. What happens then is I get a Software Failure, Program failed on Radeon

I can't believe they still make it so hard to install a driver. I thought with a fresh install it would be clean and take care of all the business. :-o

I first saw the installer a while back, and it all looked normal using a proper installer script, until you it wanted you to perform some manual manipulation and hack another monitor driver for its purpose!

I thought by now they would have cleaned all this up. But then again they also released updated USB drivers they expected you to copy manually into place that didn't work by themselves and needed configuration that happened to not be mentioned in the non existing readme file.

Is there any Amiga hardware anymore that can be installed by the average user? Or do you have to be a total Amiga tech head to install anything simple these days?

Anyway, what slot is the card in? IIRC it should be in the second slot form bottom?

[Bamiga2002]

Originally Posted by 560SL

... there are drivers to support Warp3D.

Where?! Gimme them now!! (OK AmigaOS 4.1 supports Radeon Warp3D)

Try the beta 10 pci.library if that helps...