Jump to content

(Working) Tesla K40m in a 32Bit BAR Motherboard.

Poet129
By Poet129
in CPUs, Motherboards, and Memory
 Share
Go to solution Solved by Poet129,

@ShrimpBrime

Well, I've now figured out why the nvidia driver won't start on the modded v-bios... apparently they are signed however the signatures are stored in the v-bios itself not checked against a known good list. So running the modded K40c v-bios through KeplerBiosTweaker, and changing nothing just using it to resign it makes it all work... one year later wow so simple. So all that needs done is to get a variant of the card's v-bios that will work in your motherboard then mod it to allow it to be flashed to your card via nvflash (I only had to change one byte), then resign it with KeplerBiosTweaker and finally flash it using nvflash on Linux or a normally functional board. No need to reflash every reboot now. 🙂

Posted
18 minutes ago, Poet129 said:

Try using this.

Adapter: Tesla M40            (10DE,17FD,10DE,1171) H:--:NRM  S:00,B:01,D:00,F:00

WARNING: None of the firmware image compatible PCI Device ID's
match the PCI Device ID of the adapter.
  Adapter PCI Device ID:        17FD
  Firmware image PCI Device ID: 17C8
WARNING: Firmware image PCI Subsystem ID (196E.1511)
  does not match adapter PCI Subsystem ID (10DE.1171).
WARNING: None of the firmware image compatible Board ID's
match the Board ID of the adapter.
  Adapter Board ID:        EA06
  Firmware image Board ID: EA04

NOTE: Exception caught.
Nothing changed!

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
1 minute ago, ABIT-Wolf said:

Adapter: Tesla M40            (10DE,17FD,10DE,1171) H:--:NRM  S:00,B:01,D:00,F:00

WARNING: None of the firmware image compatible PCI Device ID's
match the PCI Device ID of the adapter.
  Adapter PCI Device ID:        17FD
  Firmware image PCI Device ID: 17C8
WARNING: Firmware image PCI Subsystem ID (196E.1511)
  does not match adapter PCI Subsystem ID (10DE.1171).
WARNING: None of the firmware image compatible Board ID's
match the Board ID of the adapter.
  Adapter Board ID:        EA06
  Firmware image Board ID: EA04

NOTE: Exception caught.
Nothing changed!

 

That's the V-Bios I gave you earlier? The link was for nvflash with checks bypassed?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
5 minutes ago, Poet129 said:

That's the V-Bios I gave you earlier? The link was for nvflash with checks bypassed?

I been there and tried every Linux version there and others.

I think if we could locate EA06 in the Titan.rom change to EA02 it may then work?

with the bios I mod.

 

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
Just now, ABIT-Wolf said:

I been there and tried every Linux version there and others.

I think if we could locate EA06 in the Titan.rom to EA02 it may then work?

 

 

That's what I did.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted (edited)
2 minutes ago, Poet129 said:

That's what I did.

Did you change the top line too? Let me have a look at the one you mod in HxD.

Edited by ABIT-Wolf
Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
Just now, ABIT-Wolf said:

Did you change the top line too?

The top line makes no difference as it can be overridden with the -6 parameter.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
8 minutes ago, Poet129 said:

The top line makes no difference as it can be overridden with the -6 parameter.

Well before I changed 32 to 71 I was getting 2 different errors in nvflash, so I thought it helped.

Only the EAxx error was left with that changed.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
13 hours ago, Poet129 said:

That's the V-Bios I gave you earlier? The link was for nvflash with checks bypassed?

./nvflash2 -i0 -6 GTXTitanXmod3.rom

NVIDIA Firmware Update Utility (Version 5.218)
Modified Version by Joe Dirt   


ERROR: No NVIDIA display adapters found

unless I over looked a version, that was the only Linux I could find there with checks bypass.

Some how I missed this post there, so looks there will be no more checks bypass versions or at least not released. page 50

 

Quote

Nothing is impossible. Nvidia is just smarter than I was and nobody with real reverse engineering experience would step in. Not to mention I didn't want to brick my old 1080ti or will even remotely attempt on my 3090 with nobody wanting to help back me up on the cost of trashing an expensive card. Along with the constant "do this for me" messages, I walked away and let my homie Laithan take over the thread. And thank you Nvidia for not suing me.

 

 

 

 

 

Sorry, no more mods are being done. There is no point as we cannot flash an unsigned BIOS anyway.

 

page 52

 

Quote

edit:double

 

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
13 hours ago, ABIT-Wolf said:

Well before I changed 32 to 71 I was getting 2 different errors in nvflash, so I thought it helped.

Only the EAxx error was left with that changed.

This will still show up as an error but it can be overridden as I mentioned unless changed which isn't required as I didn't for the Tesla. The last V-Bios I modded fixed the EAxx error. But brought up the other error I thought was able to be fixed with the modded nvflash which is apparently too new to detect the older card.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
6 minutes ago, Poet129 said:

This will still show up as an error but it can be overridden as I mentioned unless changed which isn't required as I didn't for the Tesla. The last V-Bios I modded fixed the EAxx error. But brought up the other error I thought was able to be fixed with the modded nvflash which is apparently too new to detect the older card.

I have newer versions of Linux nvflash that see the card, but no check bypass.

Actually the version we used  for the K40m see it and works other than no bypas.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted (edited)
16 minutes ago, Poet129 said:

 The last V-Bios I modded fixed the EAxx error. But brought up the other error I thought was able to be fixed with the modded nvflash which is apparently too new to detect the older card.

If you would could you please post another link to the one you thought should fixed the problem.

I have edit & tested so many vbios last night I'm lost in the pile of vbios I have stored and I may

have even tried to mod that one, so it may no longer be any good..

Edit: I did mod quite a few and kept forgetting the step with MBT. Maybe its what the one you did needs?

Edited by ABIT-Wolf
add more info
Link to comment
Share on other sites
Link to post
Share on other sites
Posted
36 minutes ago, Poet129 said:

This is the one that should work, other than the certificate not working correctly. Which is why I was hoping to get a bypass for that. I already resigned it and everything though.

Thank You! I will give it a try soon. I wondered if the signing was part of the problem.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
4 hours ago, Poet129 said:

This is the one that should work, other than the certificate not working correctly. Which is why I was hoping to get a bypass for that. I already resigned it and everything though.

This is what I get with that rom. What about adding some padding like you said or would that help this?

The two file sizes are a good bit different. The Quadro M6000 12 GB BIOS is about 4k bigger.

 

(Version 5.227)
Simplified Version For OEM Only

Checking for matches between display adapter(s) and image(s)...

Adapter: Graphics Device      (10DE,17FD,10DE,1171) H:--:NRM S:00,B:01,PCI,D:00,F:00

WARNING: Firmware image PCI Subsystem ID (10DE.1132)
  does not match adapter PCI Subsystem ID (10DE.1171).

Please press 'y' to confirm override of PCI Subsystem ID's:  y
Overriding PCI subsystem ID mismatch
Current      - Version:84.00.56.00.02 ID:10DE:17FD:10DE:1171
               GM200 Board (Normal Board)
Replace with - Version:84.00.1F.00.01 ID:10DE:17FD:10DE:1132
               GM200 Board (Normal Board)

Update display adapter firmware?
Press 'y' to confirm (any other key to abort):  y
Command id:1000000E Command: NV_UCODE_CMD_COMMAND_VV failed
Command Status:NV_UCODE_CMD_STS_NEW
Error: NV_UCODE_ERR_CODE_CMD_VBIOS_VERIFY_BIOS_SIG_FAIL


ERROR: ERROR:BIOS Cert 2.0 Verification Error, Update aborted

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
36 minutes ago, ABIT-Wolf said:

This is what I get with that rom. What about adding some padding like you said or would that help this?

The two file sizes are a good bit different. The Quadro M6000 12 GB BIOS is about 4k bigger.

 

(Version 5.227)
Simplified Version For OEM Only

Checking for matches between display adapter(s) and image(s)...

Adapter: Graphics Device      (10DE,17FD,10DE,1171) H:--:NRM S:00,B:01,PCI,D:00,F:00

WARNING: Firmware image PCI Subsystem ID (10DE.1132)
  does not match adapter PCI Subsystem ID (10DE.1171).

Please press 'y' to confirm override of PCI Subsystem ID's:  y
Overriding PCI subsystem ID mismatch
Current      - Version:84.00.56.00.02 ID:10DE:17FD:10DE:1171
               GM200 Board (Normal Board)
Replace with - Version:84.00.1F.00.01 ID:10DE:17FD:10DE:1132
               GM200 Board (Normal Board)

Update display adapter firmware?
Press 'y' to confirm (any other key to abort):  y
Command id:1000000E Command: NV_UCODE_CMD_COMMAND_VV failed
Command Status:NV_UCODE_CMD_STS_NEW
Error: NV_UCODE_ERR_CODE_CMD_VBIOS_VERIFY_BIOS_SIG_FAIL


ERROR: ERROR:BIOS Cert 2.0 Verification Error, Update aborted

 

If the cert is invalid for the card then padding won't help. This is likely the case. So the only work around would be to flash anyway with a cert check bypass version of nvflash. Which you said none of them found the card?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
14 minutes ago, Poet129 said:

If the cert is invalid for the card then padding won't help. This is likely the case. So the only work around would be to flash anyway with a cert check bypass version of nvflash. Which you said none of them found the card?

I only found 2 versions 5.218 & a older version for Linux with check byass and both couldn't see the card was installed when ran. I think they are both pre Maxwell.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
3 minutes ago, ABIT-Wolf said:

I only found 2 versions 5.218 & a older version for Linux with check byass and both couldn't see the card was installed when ran.

I doubt it is any different from the Tesla K40, but have you tried nvflash (specifically the check bypass versions) in Windows? I'm not a software dev so I won't be able to make a custom version of nvflash...

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
5 minutes ago, Poet129 said:

I doubt it is any different from the Tesla K40, but have you tried nvflash (specifically the check bypass versions) in Windows? I'm not a software dev so I won't be able to make a custom version of nvflash...

Yes I have tried in windows, but as you know all to well you get the code 12.

I tried at OC.net to get a mod of the 5.222 we been using I think it maybe the 1st Maxwell version.

But with no luck.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
1 minute ago, ABIT-Wolf said:

Yes I have tried in windows, but as you know all to well you get the code 12.

I tried at OC.net to get a mod of the 5.222 we been using I think it maybe the 1st Maxwell version.

But with no luck.

Did it even show in the list? I remember it did before it just said it couldn't be flashed.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
1 minute ago, Poet129 said:

Did it even show in the list? I remember it did before it just said it couldn't be flashed.

Yes it showed up but as unusable not enough res.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
Just now, ABIT-Wolf said:

Yes it showed up but as unusable not enough res.

What about in the check bypass version under Windows?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
4 minutes ago, Poet129 said:

What about in the check bypass version under Windows?

Same there it did show but as unusable.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
Just now, ABIT-Wolf said:

Same there it did show but as unusable.

So if we found a Linux version of that version of nvflash with the checks bypassed it would work I think. Or if you had temporary access to a working 64-Bit BAR motherboard.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
6 hours ago, Poet129 said:

So if we found a Linux version of that version of nvflash with the checks bypassed it would work I think. Or if you had temporary access to a working 64-Bit BAR motherboard.

Yes, sorry for the delay in replying having internet problems tonight.

I'm in windows now. let me run nvflaash.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

nvflash64_patched_5.590.0 --list
NVIDIA Firmware Update Utility patched by Vipeax
Copyright (C) 1993-2019, NVIDIA Corporation. All rights reserved.


NVIDIA display adapters present in system:
NOTE: Unconfigured display adapter found, device not accessible:
      Tesla M40            (10DE,17FD,10DE,1171) H:--:NRM  S:00,B:01,D:00,F:00

No NVIDIA display adapters found.
 

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing CPUs, Motherboards, and Memory

×