Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I have an issue flashing my geforce fx 6200 512mb with a rom made using the rom maker tools, i have tried various versions of nvflash 5.1x and all of them return me an error message saying:

Code:
Error: Unsupported code type: 0x1. FCode support deprecated.

i get this error even when trying to flash with roms i found online, is there any way around it? Do you have some nvflash versions i can try?
 
I have an issue flashing my geforce fx 6200 512mb with a rom made using the rom maker tools, i have tried various versions of nvflash 5.1x and all of them return me an error message saying:

Code:
Error: Unsupported code type: 0x1. FCode support deprecated.

i get this error even when trying to flash with roms i found online, is there any way around it? Do you have some nvflash versions i can try?
What is the output of nvflash --check?

I had an issue with the EVGA 512MB card needing the newer versions of nvflash to support the EEROM, but as you have found those versions won't flash FCode ROM's.

For me the work around was to combine the PC VBIOS and the FCode ROM into one rom image that works in both Macs and PCs.

NVFLASH only checks the half byte of the arch in the first ROM image. So we put the PC VBIOS first in the ROM image.

This only works if you EEROM is large enough to accommodate both ROM images, so we need the output of nvflash --check to see the size of the EEPROM on your card?
 
I have an issue flashing my geforce fx 6200 512mb with a rom made using the rom maker tools, i have tried various versions of nvflash 5.1x and all of them return me an error message saying:

Code:
Error: Unsupported code type: 0x1. FCode support deprecated.

i get this error even when trying to flash with roms i found online, is there any way around it? Do you have some nvflash versions i can try?
There you go, try

Code:
nv513 -4 -5 -6 -j <rom_file>

If not try one of the other ones in the archive, I definitely got it to work on the 6200 with one of them and I thought that it was 5.13

Cheers
 

Attachments

  • nvflash.zip
    1.4 MB · Views: 166
At the end i solved it on my own, it turns out i had a too recent copy of nvflash, so i grabbed the version 5.13 ( that i previously confused with version 5.136) from guru 3D and it worked, i was able to flash at least my geforce 6800 gt so it works in my g5, for the 6200 i will try getting it to work when i have some more time to spend on the project, for now i am happy with the geforce 6800 gt in my g5. BTW the 6200 gt will go in my firewire 800 g4 with dual cpus.
 
Last edited:
At the end i solved it on my own, it turns out i had a too recent copy of nvflash, so i grabbed the version 5.13 ( that i previously confused with version 5.136) from guru 3D and it worked, i was able to flash at least my geforce 6800 gt so it works in my g5, for the 6200 i will try getting it to work when i have some more time to spend on the project, for now i am happy with the geforce 6800 gt in my g5. BTW the 6200 gt will go in my firewire 800 g4 with dual cpus.
I doubt you'll be using a 6200 in a MDD, seems to be some incompatibility there. Likely it could be fixed, but it's going to take some more debugging.
 
I doubt you'll be using a 6200 in a MDD, seems to be some incompatibility there.

It should just need the 64k no sensor rom as far as i know, then it also needs taping pins 3 and 11 on the agp connector. i already did a similar mod to my geforce fx 5500 256mb, i am modding this 6200 gt as an upgrade from that really.
 
It should just need the 64k no sensor rom as far as i know, then it also needs taping pins 3 and 11 on the agp connector. i already did a similar mod to my geforce fx 5500 256mb, i am modding this 6200 gt as an upgrade from that really.
The 6200 ROMs at #1 are 64K, work with all versions of Open Firmware, and do not remove sensors or anything. We can remove the sensors code if that's a problem.
 
The 6200 ROMs at #1 are 64K, work with all versions of Open Firmware, and do not remove sensors or anything. We can remove the sensors code if that's a problem.
Well, I mean there is work and there is work.

The same ROM that I can load from a file on disk in my MDD for the EVGA 6200 512MB PCI doesn't work when flashed to the card in the MDD.

The card just doesn't show up on the PCI bus at all, so some issue with the ROM is causing the card to become invisible.

Same issue with the 256MB 6200 PCI. These cards work just fine( mostly ) in the Beige G3, G4 Quicksilver, and G5 systems.

Back in the day Rob Art Morgan( R.I.P ) had a similar issue with the 7800 GS AGP in MDD systems in his testing, while a flashed 6600 worked just fine in a MDD.


I seem to recall others having issues with 6200's and 7800's in MDDs.

So we have some work to do there.

I'd be happy to help debug it if you have some clue about the best way to go about it?
 
Well, I mean there is work and there is work.

The same ROM that I can load from a file on disk in my MDD for the EVGA 6200 512MB PCI doesn't work when flashed to the card in the MDD.

The card just doesn't show up on the PCI bus at all, so some issue with the ROM is causing the card to become invisible.

Same issue with the 256MB 6200 PCI. These cards work just fine( mostly ) in the Beige G3, G4 Quicksilver, and G5 systems.

Back in the day Rob Art Morgan( R.I.P ) had a similar issue with the 7800 GS AGP in MDD systems in his testing, while a flashed 6600 worked just fine in a MDD.


I seem to recall others having issues with 6200's and 7800's in MDDs.

So we have some work to do there.

I'd be happy to help debug it if you have some clue about the best way to go about it?
Did you provide any MDD 6200 testing info in the Beige G3 GPU thread?

I guess we need to know the difference between loading the rom from a file and loading the rom from the PCI card.

For each test, do dump-device-tree and also get Open Firmware lspci output. First we'll deal with the 256MB card which is known to work in Old World and New World Macs.

Tests:
1) Start with PC rom only. No fcode.
2) Then append a dummy FCode rom after the PC rom. Just make it set a single property such as device name.
3) Then add FCode debug 6200 rom (still with PC rom if it fits). The debug rom should output stuff. It would be best if you could get serial output working. I wonder if we can add " enet:telnet,192.168.0.123" io to nvramrc after install-console but before probe-all banner. This assumes that probe-all is not responsible for adding ethernet devices - you can tell by adding dev / ls after install-console but before probe-all
 
Back in the day Rob Art Morgan( R.I.P ) had a similar issue with the 7800 GS AGP in MDD systems in his testing, while a flashed 6600 worked just fine in a MDD.
Maybe we need to port the 6200/7800 to the fcode version of the 6600?
 
Did you provide any MDD 6200 testing info in the Beige G3 GPU thread?

I guess we need to know the difference between loading the rom from a file and loading the rom from the PCI card.

For each test, do dump-device-tree and also get Open Firmware lspci output. First we'll deal with the 256MB card which is known to work in Old World and New World Macs.

Tests:
1) Start with PC rom only. No fcode.
2) Then append a dummy FCode rom after the PC rom. Just make it set a single property such as device name.
3) Then add FCode debug 6200 rom (still with PC rom if it fits). The debug rom should output stuff. It would be best if you could get serial output working. I wonder if we can add " enet:telnet,192.168.0.123" io to nvramrc after install-console but before probe-all banner. This assumes that probe-all is not responsible for adding ethernet devices - you can tell by adding dev / ls after install-console but before probe-all
We normally leverage the nvramrc like this when we want to boot to telnet:

Code:
nvedit
: tnio " enet:telnet,10.1.2.3" io ; <press return>
<press ctrl+c to exit the nvramrc editor>
nvstore
setenv use-nvramrc? true
setenv boot-command tnio
reset-all
 
We normally leverage the nvramrc like this when we want to boot to telnet:

Code:
nvedit
: tnio " enet:telnet,10.1.2.3" io ; <press return>
<press ctrl+c to exit the nvramrc editor>
nvstore
setenv use-nvramrc? true
setenv boot-command tnio
reset-all
I think boot-command happens after probe-all. We want output before then.
 
Has anyone experienced difficulties using DVD player with a 6200 on leopard (with a B&W 600MHz G4)? The aspect ratio is all bungled up, menu text unreadable, but not with a 5200?!? Fine in Tiger though
Try using VLC, It has a drop down menu for changing the aspect ratio of video output. DVD Player is limited to that ability?

DOS:
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.