A4000 with Radeon+Network Card on Mediator and lock ups.

[slaapliedje]

I have two different Radeons (just tried both of them again) one with 256MB (which the Amiga sees only 128MB, I think this is due to it acting like two different cards for the dual-head, but could be wrong) and one with 64MB that I bought from Elbox since I had bought the mediator before they had one of their deals..

The problem is that whenever I use a resolution that outputs through the Radeon card (I have an Indivision AGA connected to the VGA port and the Radeon connected through DVI on my 25" LCD.) it locks up after a short time.  Just freezes.

I can do the Control+A+A to reset it.  It seems to do this quicker when I'm in higher resolutions.  In fact I just tried saving it as 1920x1080 (which looks absolutely beautiful!) and it locks up before it even finishes loading up Amidock.

Any ideas?  It's running OS3.9, and I don't think I've done anything really custom on it besides a few things like installing the Mediator drivers.  

It's perfectly stable in the Amiga resolutions.

slaapliedje

[mechy]

Are the jumpers on the mediator bridge card set right?

Medconfig correct?  might try medication to take a look.

Mech

[Darrin]

off my Mediator on my A4000 with 256MB Radeon:

Swap Config:  Jumper off
Master:  Jumper On
WinSize:  Jumper On

[slaapliedje]

They are set up the same as Darrin's.

I one point I was thinking it was heat, but it does it even with the case off.

I have opened it up so many times, that if the Amiga were a real woman, I would have been arrested as Ted Bundy's Protoge.

slaapliedje

[mechy]

off my Mediator on my A4000 with 256MB Radeon:

Swap Config:  Jumper off
Master:  Jumper On
WinSize:  Jumper On

I think that triggered a memory... with 128MB and less cards i *think* winsize must be off also.

mech

[slaapliedje]

Tried both cards with it off and on.  The 256mb wouldn't boot with it off, and they both still lock up.

Though the strange thing is, if I save the resolution as being on the Radeon, it locks up almost right away (loads the icons on the desktop and the workbench bar, but locks up before Amidock).  On the other hand, if I'm in a normal Amiga resolution, then go into a Radeon resolution, it works for quite some time, then locks up.

Not sure if the Afa OS has anything to do with it, but I know when I try to enable that, it doesn't even get as far as showing any workbench, the screen just stays black.

I'm thinking more and more that it's some sort of memory conflict, but I would think I'd be getting an error instead of it just freezing.

slaapliedje

[Darrin]

Could it be a P96 issue?  I use v2.1c

[slaapliedje]

Ah, finally after digging around (I know I was on a quest to find the 2.1c before, but I think the download link at http://lilliput.amiga-projects.net/Picasso96.htm wasn't working or something) I managed to find that I must have been running an older version, 2.1b.  I'm going to install 2.1c now and then test and see if I have any luck in getting it to be more stable.

slaapliedje

[slaapliedje]

Ah, no such luck.  I was hopeful, because it didn't lock up when I was in the lower resolution and switched to 1920x1080 and ran a few things (usually locks up pretty quick) but as soon as I saved the resolution and rebooted, it locked solid again at the same spot.  Ctrl+A+A did reset it though.

[rkauer]

I promised myself to not post here any more. But just one question: how much memory you leave available in the Radeon tooltypes?

Remember that the Mediator needs some of the video card memory to act as a buffer for the rest of the busboard. So at least 1Mb must be left for the other cards in the system.

A 64Mb card must be set to a maximum of 63Mb. But the less, the best. Set the tooltype to 15Mb and the remaining memory will be added as FAST RAM (15Mb to video modes, 1Mb for the Mediator buffers, 48Mb for the system).

If you set all the card's memory to itself you'll have those lockups as soon as you choose a RTG resolution.

[slaapliedje]

You're referring to the sys:prefs/env-archive/mediator/RadeonMem file, correct?

It's set to 15.  I've played around with this a bit, as I said earlier, I have a Radeon that is technically a 256mb card, but I think it's one of the weird ones that think each video output is it's own video card, and divides the memory allocation to two different banks of memory (I looked in the... ah crap can't recall what the program is called now, but it displays all the PCI information..pciinfo?).

Even if I set the RadeonMem to 127, it still shows I have 128mb of memory.

Thanks for the input, sorry to make you post here again.

slaapliedje

[Darrin]

For what it is worth, mine is set at 63 and it allocates the remaining 192MB as system RAM.

I wonder if it might be the monitor setup in devs/monitors or perhaps your P96 custom screen modes.  My A4000 is under a table at the moment.  When I reconnect it I can email you my monitor driver and check my P96 preferences.  I don't know about you, but I had to build each and every P96 screen mode from scratch (doesn't take long once you've worked out what your display can handle).

[slaapliedje]

I actually found a perl script at one point that converts X.org screenmode lines into P96 configuration settings.  So with that I was able to get perfect resolutions filling up the screen for everything on the Radeon card.  Just wish I could find something similar for the Indivision utility.

I appreciate all the help!

slaapliedje

[freqmax]

@slaapliedje, Just do the display math