There is nothing about what I was looking for.
Here is link if someone needs ROM FILE FOR K1000M
This is how to find that on the first page - takes 3 clicks to get to the post you linked.
There is nothing about what I was looking for.
Here is link if someone needs ROM FILE FOR K1000M
Now boot into Mojave, Catalina, Big Sur, Monterey or Ventura and report back if the internal and external displays are both still working?View attachment 2098390
Who has a wx7100 video card
I decided to add the command agdpmod=vit9696. Without connecting an external display, the backlight of the system works 10.13.6. Without this command, a black screen after loading 10.13.6, this requires an external display connection, which is inconvenient. Thanks to this command agdpmod=vit9696 works great!
Check out quickly the last ten posts to get an idea where to search and read.Hi Guys
I've also just discovered that one of my Thunderbolt ports (the one right next to the ethernet port) no longer works with my second monitor.
Any ideas what that might be?
Check out quickly the last ten posts to get an idea where to search and read.
3. Despite having 2 miniDisplayPort outputs, the 27" 2011 iMac will only output to one external display. There is currently no fix or workaround for this.
No, the only card I ever saw available was offered in Australia (ebay, maximum distance on this planet). The results will be most likely the same as with all other GCN 1-3 cards, it will not work properly in 2011 iMacs, but most likely fine in the 2009 and 2010 iMacs. Same speed and same benchmarks like the W6170M….Has anyone tried a AMD W6150M 4gb?
Good morning, I am new to this forum, I would like to update my imac 27 2011 with a nvidia k2100m 2gb I am about to perform the flash procedure, as for the operating system I have high sierra, I would like to update it at least to catalina (reason why I do this update) do I use open core? Are other systems stable? Thank you very much, I hope for your help
I'd recommend you update to Big Sur using OCLP (OpenCore Legacy Patcher) as that does still officially support your system with Big Sur, including the upgraded video card. That's my personal opinion.If you help me free i’m here, if you want money don't answer either
Good morning, I am new to this forum, I would like to update my imac 27 2011 with a nvidia k2100m 2gb I am about to perform the flash procedure, as for the operating system I have high sierra, I would like to update it at least to catalina (reason why I do this update) do I use open core? Are other systems stable? Thank you very much, I hope for your help
thank you very much I am undecided if big sur i catalina, in case I tried catalina I saw that you do not need opencore but also various fixes for the brightnessI'd recommend you update to Big Sur using OCLP (OpenCore Legacy Patcher) as that does still officially support your system with Big Sur, including the upgraded video card. That's my personal opinion.
For how to do the installation follow the advices from the first post of this thread and the OCLP documentation.
You cannot get it all. Catalina via @dosdude1 allows you to use the full spectrum of functionality including AirPlay, but the installation is a nightmare for inexperienced users. You can avoid these difficulties and use OCLP for all macOS versions starting with Mojave including the upcoming Ventura. It is your choice.thank you very much I am undecided if big sur i catalina, in case I tried catalina I saw that you do not need opencore but also various fixes for the brightness
The place in the VBIOS you found does not represent the PCI subvendor and subsystem ID but it is just reserved space. Those sub IDs are set by the EFI driver itself upon booting - and I've also seen that changing from boot to boot, without knowing how to fix it. All in all I don't care about Windows...@Ausdauersportler @nikey22 @internetzel
Test M5100 macOS window read vbios information is randomly different every time
Check the hardware ID inside the windows driver inf information and macOS inside match both (6281)
macOS display HD 7XXX corresponds to the windows R9 M2000X driver
macOS shows M5100 corresponds to windows is also matching M510 driver
Check vbios information hardware ID: 21 68 00 00 can be corrected to lock fixed loading driver so macOS windows is fixed will not show the error.
Check vbios information Dell driver ID 28 10 CC 15 and windows match the M5100 driver ID matches
Check the inf driver ID inside is 10 3C which is HP's ID, query vbios inside the information does not match, HP also has the original M5100 vbios
Check the inf driver list ID 6281 contains multiple models
AMD6821.1 = "AMD FirePro M5100"
AMD6821.2 = "AMD FirePro M5100"
AMD6821.3 = "AMD Radeon (TM) R9 M365X"
AMD6821.4 = "AMD Radeon R9 M200X Series"
AMD6821.5 = "AMD Radeon R9 (TM) M370X"
AMD6821.6 = "AMD Radeon (TM) R7 M380"
Match the loaded driver here
ID "%AMD6821.1%" = ati2mtag_R577, PCI\VEN_1002&DEV_6821&SUBSYS_2253103C&REV_00
"%AMD6821.2%" = ati2mtag_R577, PCI\VEN_1002&DEV_6821&SUBSYS_2254103C&REV_00
"%AMD6821.3%" = ati2mtag_R577, PCI\VEN_1002&DEV_6821&SUBSYS_B298174B&REV_87
"%AMD6821.4%" = ati2mtag_R577, PCI\VEN_1002&DEV_6821&REV_00
"%AMD6821.5%" = ati2mtag_R577, PCI\VEN_1002&DEV_6821&REV_83
"%AMD6821.6%" = ati2mtag_R577, PCI\VEN_1002&DEV_6821&REV_87
M5100 W5170M W7170M AMD GCN v1-3 GPU
Is it possible to correct the model display error caused by macOS windows driver matching error by fixing the blank ID: 00 00 inside vbios?
windows system by gpu-z check vbios version information are the same just load the driver is not the same.
Fix the blank ID 00 00 information inside the vbios to lock the fixed id information with the matching driver instead of loading the driver randomly each time resulting in display errors
Translated with www.DeepL.com/Translator (free version)
Can you fix the id in the efi driver to lock the fixed loaded driver?The place in the VBIOS you found does not represent the PCI subvendor and subsystem ID but it is just reserved space. Those sub IDs are set by the EFI driver itself upon booting - and I've also seen that changing from boot to boot, without knowing how to fix it. All in all I don't care about Windows...
The model name in macOS is purely cosmetic, OpenCore contains an updated name list database which will be used when the rebuild-device-tree property has been set in the config.plist (which should happen by default):Can you fix the id in the efi driver to lock the fixed loaded driver?
This will not only solve the driver loading problem in windows, but also solve the problem of macOS not displaying the correct model number?
You can try to add the reserved space ID 0000 to lock it.
I can help test macOS windows
<key>rebuild-device-tree</key>
<integer>1</integer>
m5100 id is 6821 w5170m id is 6820The model name in macOS is purely cosmetic, OpenCore contains an updated name list database which will be used when the rebuild-device-tree property has been set in the config.plist (which should happen by default):
Code:<key>rebuild-device-tree</key> <integer>1</integer>
Since most cards cannot be used without OpenCore properly just keep track of this particular entry. OCLP during it’s development tends to forget about this (cosmetic setting) and I do not interfere each time to get it back.
There is absolutely no technical reason to touch the vBIOS or the OC(LP) config or the EFI driver to have the same name showed up each time, it is a cosmetic issue within macOS.
M5100 and W5170M are different cards with different device-ID which may show up with different names when running macOS. And both cards may also load different Windows drives.
I don't know of any possibility to achieve that.Can you fix the id in the efi driver to lock the fixed loaded driver?
This will not only solve the driver loading problem in windows, but also solve the problem of macOS not displaying the correct model number?
You can try to add the reserved space ID 0000 to lock it.
I can help test macOS windows
Does the NVRAM issue cause a different id assigned to the efi driver to load each boot?I don't know of any possibility to achieve that.
In order to get the same ID on each boot you may have to always power off the machine before (cold) booting into Windows.
Maybe even an NVRAM reset is necessary on each boot...