installed new HD7950 & now my screen modes are messed up??-SOLVED again :-)

posted this on the fastest card thread but not getting enough exposure there so:

after successfully removing my old 6870 and installing 7950 all seemed ok except when I tried out Torx, Freespace2 & SuperTuxKart I was getting 'input not supported'?? so went back to WB screen & all fine.

for SuperTuxkart I changed screen mode in prefs and all is good but other games can't find prefs or where to change screen mode.

so how do I get all my screen modes back & working with my new card?

btw, my card: Gigabyte Radeon HD7950, 3GB Vram, full size, dual slot

@328gts

Hello,

I'm in the same situation, I installed a Radeon HD 7950 Power Color 3GB GDDR5, the workbench works perfectly, Cow3D too, but supertuxkart not work, the screen goes black and the X1000 is reset, Quake2 the same story, black screen and a reset, the same with Frogatto.
I have the latest drivers RadeonHD 2.10 and Warp3D SI v1.14 and AmigaOS Final Edition.

I have the same problems with some applications that i use mui and other screens for with every change of new card. So i have to change them. Im no expert so i dont really know but right now with 7750 im fine :) Ill probably keep it for a while. Its not the faster ones but silent.

@328gts:

If you dont find any prefs inside the game archives maybe they are saved somewhere in the envarc or its subdrawers ?. Maybe google if you havent done yet for the games.

I tried supertux for the first time on warp3D. Works ok. If i raise resolution some parts are damaged in the gfx. Fullscreen makes the screen just white.

@Fernecho

Check Frogatto/userdata/ maybe preferences.cfg or the save.cfg have the settings to the screenmode. Just rename them and copy over the original from the original archive.

@Fernecho

I get the black screen too but all I have to do is switch screens to get back to workbench with no issues and never does my system reset.
Did you try downloading the latest SuperTuxkart?


@Kicko

thanks will try digging up the individual prefs for each program

@all
Do you guys have custom monitor settings in DEVS:Monitors? If so, then what's probably happening is that those settings are in a monitor file specific to your old card, and the system is using the default settings (i.e., use DDC) for your new card. That way you end up with a different set of modes (with different modeids).

The easiest way to avoid this is to rename the monitor file to "Radeon," change the BOARDNAME tooltype to "Radeon" and the CMPLENGTH tooltype to 6.

If this doesn't make any difference, then I have no idea what's going on.

Hans

@Hans

thanks Hans! all solved now

Whats cmplength for ?. I had it to 21 but changed now to 6.

cmplength helps the system to associate the board with the monitor file by how many letters are in the name of the monitor file.

Radeon has 6 letters so cmplength needs to be 6

More precisely, it's the number of characters of the boardname which are used when comparing with the monitor filename. So you don't necessarily have to match the full length of both, but can use the first part for matching if it is enough, while still having a more informative longer name as your monitor filename.

(Or something like that )

Best regards,

Niels

hmm don't know what happened as all was working great but today any screen mode other than 1920x1280 gets me back to 'input not supported' black screen on my X1K ??

tried changing 'disablefakenativemoe and interrupt' in Tooltypes from yes to no but still no luck

@nbache

Ah, so the cmplength helps the system distinguish between two (or more) monitor files and pick the right one IF there is more than one monitor file or graphics card found?

@Raziel

Yes, partly, but I think the CMPLENGTH also has to be set correctly even if there's only one, for it to be accepted at all.

Best regards,

Niels

here's my tooltypes in Radeon monitor file:

CMPLENGTH=6
BOARDNAME=Radeon
VSYNCMIN=55
VSYNCMAX=75
HSYNCMIN=30000
HSYNCMAX=80000
(MODE=640x480@60)
(MODE=1280x720@60)
(MODE=800x600@60)
(MODE=1280x720@60)
(MODE=1024x768@60)
(MODE=1280x720@60)
(MODE=1920x1080@60)
(MODE=1280x1024@60)
DISABLEFAKENATIVE=No
INTERRUPT=Yes


hmmm strange thing just happened--as I went to copy the tooltypes to paste here I just noticed the CMPLength (thats seems to be a popular topic on this htread lol) changed to 7???? was always 6

@328gts

still having this issue so can someone post their too types here please

sooo messed with my tool types a few minutes ago and figured i'd remove the brackets from all the screen modes except the 1920x1080 since I know my WB is set to it.

well now I'm stuck with a quick 'input not supported error' and then the boot chingle and another black screen with the 'input not supported'???

genius that I am just got my bootable which was created with the old Radeon driver so now I'm totally stuck

figure I should be able to just put the new Radeon HD file onto the bootable DVD...

@328gts

what a mess.. the must be made a tool to uninstall present drivers/settings and reboot, install new drivers..reboot everything works

@328gts
Silly question, but why don't you just set it to ddc and let the monitor find it's best resolution? No need to mess with these settings manually.

@32gts

Just use:

CMPLENGTH=6
BOARDNAME=Radeon
DDCMODE=60Hz
DISABLEFAKENATIVE=Yes
INTERRUPT=Yes

That will get it working at least, you can tweak later but I doubt you will need to.

The tooltypes you posted will never work, all your screen modes are disabled because they have brackets round them and you have no DDCMODE setting. which can be 'All', 'Preferred' or '60Hz'

All means all, huge lists of screenmoces.
60Hz just gives the most common modes.
preferred just uses the native resolution of the monitor.

@Hans

Do you mind showing where I need to go (path) to modify those settings?

I can find and change the name of the old monitor name to Radeon, but where do I find the rest of parameters needed to be changed?

CMPLENGTH=6
BOARDNAME=Radeon
DDCMODE=60Hz
DISABLEFAKENATIVE=Yes
INTERRUPT=Yes

@all
Do you guys have custom monitor settings in DEVS:Monitors? If so, then what's probably happening is that those settings are in a monitor file specific to your old card, and the system is using the default settings (i.e., use DDC) for your new card. That way you end up with a different set of modes (with different modeids).

The easiest way to avoid this is to rename the monitor file to "Radeon," change the BOARDNAME tooltype to "Radeon" and the CMPLENGTH tooltype to 6.

If this doesn't make any difference, then I have no idea what's going on.

Hans

@AmigOS

Hey there... Those parameters are Tool Types stored in the icon. What you do is right click on the monitor icon in SYS:Devs and choose Information. Then click on the Icon tab and you can edit and save the parameters there. Happy hunting!