Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iM 4,1-14,4 2011 iMac Graphics Card Upgrade
- Thread starter MichaelDT
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Console App -> try to fetch the panic report. Without it we have a „it does not work problem“ - noboday will be able to solve.
You have to adjust the opencore config completely. The boot-args are still different and I cannot support this 0.6.3 experiment.
Take both config files and a fitting xml editor or OC configurator and make the 0.6.3 look alike the 0.6.5 or you move over to 0.6.5 and try to find a solution for the brightness control there. I will not back port the Big Sur settings to 0.6.3 - this is ridiculous.
Hi,
sorry for being a little out of topic, but does anyone have any news about Nick [D]vB ? He is the author of many ROMs used here, and is a model of kindness.
I'm concerned because he hasn't posted anything here since may 2020, and just before he told me he was ill and has been hospitalized...
Does anyone have any news or a way to contact him ?
sorry for being a little out of topic, but does anyone have any news about Nick [D]vB ? He is the author of many ROMs used here, and is a model of kindness.
I'm concerned because he hasn't posted anything here since may 2020, and just before he told me he was ill and has been hospitalized...
Does anyone have any news or a way to contact him ?
I don’t have any problem to switch to 0.6.5, but I need to know where to look at to solve the brightness problem I have.
I don’t know all the variables in the config file, and what are the ones responsible for the brightness fix.
Without knowing the details you can compare both config files and only you can do tests. So please go ahead and learn to swim or to fly or both. I have no such system and cannot help and will not dig into the files...
Thanks for all. I'll stay at 0.6.3 for next weekend to have time to test and compare both configs.
If I find something, I will post here
There is no best card to use ... . While the iMac 2009 is more similar to 2010 than 2011, a GPU working in one doesn't necessarily mean it will work in another iMac series. If you just want to know what GPUs other users have reported working in iMac 2009, just read the 1st post on Graphic Card Performance. You can view results there in the Excel table and sort according to your iMac model year. I am sure more should have been successful without running the post-install benchmark nor posting there. And some users did upgrade to a few or more iMacs instead of one.
The problem is there are so many different variations even for the same GPU type, like the type of RAM chips and their preset or tolerable operating frequency. Even our Mac vBIOS developers can't catch them all. Moreover, we are talking about second hand market old GPUs. They might not function well as the components wear with time nor be available in each every place in an affordable price. Despite a user may report success, there could be many factors affecting your own, if you are lucky to get the same GPU into your hand. It is a self-discovery adventure and experiment on your own iMac. Only you would be the final trouble-shooter.
The 27" is a capable machine with room and power to spare, but I am biased to advise on an AMD WX4130 for its relatively cheap price and low power consumption without need of heatsink modification and good Metal performance and a "native" Bootscreen and Bootpicker with Opencore, which is a must at present to migrate from Catalina to Big Sur and also with full hardware video acceleration support without the graphic glitches of nVidia GPUs. However, all these rely on your acquiring one that can POST in your iMac 2009. In general the behaviours of AMD GPUs seem unpredictable in every Mac. Nevertheless, while I checked in the market not long ago, I could find only the Dell version of WX4130 which worked consistently in my iMac 2010. That's all I can say, again and again, with regard to this often asked question. Your budget, your required applications, the GPU availability and compatibility, and your technical savvy in doing troubleshooting on your own govern your choice. Read the 1st post for all the options and decide for yourself.
Last edited:
I was comparing 1st page and saw wx4130 performance gain at 130% whereas some Nvidia GPUs have beyond 200% gain. it seems I am missing some understanding.
The wx4130 allows you to have less problems if tou want to upgrade to Mojave, catalina or big sur.
For instance, if you try to use streaming services on safari, it won’t work on macos above high sierra with nvidia cards.
Yes, but let him read the first post himself. He was able to find the least important data (OpenGL performance) on his own.
Thanks, i suspected what you have affirmed.
I have ordered it with fingers crossed. Hope it works. If it does, it will be to all the team here.
Last edited:
How to kill a Radeon 6970M?
Today I bought another used (announced to be defective) 27 Mid 2011. After opening the system it I found out that the connector cable from logic board to power supply was not connected into the power supply. Reconnecting it and the system runs like a new one.
Now the interesting part. I booted Catalina (Valley did not run at all) and later High Sierra to make a Valley benchmark. Got 30.3 FPS and 1224 Score, compared to the AMD cards lame, but enough for browsing. I let the Valley run for not more than 30 minutes and got the temps as shown on the attached pictures.
It becomes crystal clear why such cards died in numbers so fast. ODD fan did not came up more than 1644 rpm but temps hit 90C very fast, heat sink at 77C - I never had such values with the 780M or RX480, especially after moving the ODD temp sensor onto the heat sink and using the very same Apple SMC software.
Not even my RX480 gets that hot during a 70W valley run.
Today I bought another used (announced to be defective) 27 Mid 2011. After opening the system it I found out that the connector cable from logic board to power supply was not connected into the power supply. Reconnecting it and the system runs like a new one.
Now the interesting part. I booted Catalina (Valley did not run at all) and later High Sierra to make a Valley benchmark. Got 30.3 FPS and 1224 Score, compared to the AMD cards lame, but enough for browsing. I let the Valley run for not more than 30 minutes and got the temps as shown on the attached pictures.
It becomes crystal clear why such cards died in numbers so fast. ODD fan did not came up more than 1644 rpm but temps hit 90C very fast, heat sink at 77C - I never had such values with the 780M or RX480, especially after moving the ODD temp sensor onto the heat sink and using the very same Apple SMC software.
Not even my RX480 gets that hot during a 70W valley run.
Attachments
Hello, everyone. First, thanks for everyone who contributed to this thread, specially OP, @Ausdauersportler (nice guides and tuts!), @nikey22 and @Nick [D]vB (I hope you are OK, someone posted you were hospitalized recently), @xanderon and @highvoltage12v.
I got an used K610M board recently (MXM A, it identifies itself as a GK208 board - IIRIC it was made for some HP notebook) and tried to install it on an iMac 21" mid-2011 (iMac12,1), but although I can flash the custom VBIOS and the board is detected, there is no video, as explained below.
Board info
Factual data:
1. The iMac was tested with a stock AMD card and it was working normally, I have installed Mavericks and upgraded to the latest High Sierra to make sure firmware/SMC are up-to-date
1. If the iMac is started with the K610M using the VBIOS that came with it or the version from #5750, neither the graphics card nor the LCD panel (obviously) are detected. Boot and clearing PRAM are as fast as normal, but it seems that macOS does not start at all, I can boot Linux only (without video).
2. After flashing the custom VBIOS, booting and clearing PRAM takes much longer, the LCD is detected, it turns on the backlight but no video at all. macOS starts loading but it restarts itself before finishing (I have set up automatic login and screen sharing for testing)
3. I can startup in Safe mode, but still no video (same as above). The board is identified with the custom VBIOS, but the display is shown with a weird resolution (1280 x 1024 IIRC) when I connect remotely via screen sharing
4. It seems that there is no external video in any case
5. I can flash the original and PC VBIOS from #5750, verification says it is fine, but when flashing the custom Mac VBIOS I get the same error shown in #4363, so I guess it is normal. Using the (much) newer nvflash for Linux does not seem to make any difference. For some reason, the board is shown on macOS with the custom VBIOS as being 1023MB.
The chip used in the board is N15M-Q2-B-A3 (not A1 as shown in the custom VBIOS post), it makes any difference?
I have searched all this thread for K610M and found nothing special. It seems that some boards do not work with some Macs, even tho they seem to be fine. I have seen many reports similar to mine in this YouTube video, so I guess K610M won't work all the times. Maybe there is some VBIOS configuration or version that would fix those, or at least find a way to avoid problematic boards.
If anyone knows if this can be fixed, please drop a line. If there is no fix, at least it will be here as a report to help others. I am not sure if the board is OK, so perhaps mine is just a faulty card.
Regards
I got an used K610M board recently (MXM A, it identifies itself as a GK208 board - IIRIC it was made for some HP notebook) and tried to install it on an iMac 21" mid-2011 (iMac12,1), but although I can flash the custom VBIOS and the board is detected, there is no video, as explained below.
Board info
Code:
Adapter: Quadro K610M (10DE,12B9,103C,2256) H:--:NRM S:00,B:01,D:00,F:00
EEPROM ID (EF,3012) : WBond W25X20A 2.7-3.6V 2048Kx1S, page
WARNING: Firmware image PCI Subsystem ID (106B.1026)
does not match adapter PCI Subsystem ID (103C.2256).
Please press 'y' to confirm override of PCI Subsystem ID's: y
Overriding PCI subsystem ID mismatch
Current - Version:80.28.54.00.02 ID:10DE:12B9:103C:2256
GK208 Board - 20390504 (Normal Board)
Replace with - Version:DE.AD.00.BE.EF ID:10DE:12B9:106B:1026
Quadro K610M by Nick[D]vB (Normal Board)Factual data:
1. The iMac was tested with a stock AMD card and it was working normally, I have installed Mavericks and upgraded to the latest High Sierra to make sure firmware/SMC are up-to-date
1. If the iMac is started with the K610M using the VBIOS that came with it or the version from #5750, neither the graphics card nor the LCD panel (obviously) are detected. Boot and clearing PRAM are as fast as normal, but it seems that macOS does not start at all, I can boot Linux only (without video).
2. After flashing the custom VBIOS, booting and clearing PRAM takes much longer, the LCD is detected, it turns on the backlight but no video at all. macOS starts loading but it restarts itself before finishing (I have set up automatic login and screen sharing for testing)
3. I can startup in Safe mode, but still no video (same as above). The board is identified with the custom VBIOS, but the display is shown with a weird resolution (1280 x 1024 IIRC) when I connect remotely via screen sharing
4. It seems that there is no external video in any case
5. I can flash the original and PC VBIOS from #5750, verification says it is fine, but when flashing the custom Mac VBIOS I get the same error shown in #4363, so I guess it is normal. Using the (much) newer nvflash for Linux does not seem to make any difference. For some reason, the board is shown on macOS with the custom VBIOS as being 1023MB.
The chip used in the board is N15M-Q2-B-A3 (not A1 as shown in the custom VBIOS post), it makes any difference?
I have searched all this thread for K610M and found nothing special. It seems that some boards do not work with some Macs, even tho they seem to be fine. I have seen many reports similar to mine in this YouTube video, so I guess K610M won't work all the times. Maybe there is some VBIOS configuration or version that would fix those, or at least find a way to avoid problematic boards.
If anyone knows if this can be fixed, please drop a line. If there is no fix, at least it will be here as a report to help others. I am not sure if the board is OK, so perhaps mine is just a faulty card.
Regards
Attachments
Last edited:
The K610M is a very weak card, and was more a proof of concept project really. Its only operates at 8x and has limited vram. I've never seen the -A3 variant.
Did you save the initial vbios that was on the card? VER:80.28.54.00.02
Send it to me, I will take a look at it. It could be a vram issue.
The K610M card that I used to develop the vbios used SAMSUNG ram, specifically: K4G20325FD-FC04.
I can make out that your card has hynix. So this will need to be looked at obviously.
Did you save the initial vbios that was on the card? VER:80.28.54.00.02
Send it to me, I will take a look at it. It could be a vram issue.
The K610M card that I used to develop the vbios used SAMSUNG ram, specifically: K4G20325FD-FC04.
I can make out that your card has hynix. So this will need to be looked at obviously.
Hey, @nikey22! Thanks for your reply. Yes, it seems that it uses hynix indeed (2 chips at both sides). Attached is the original VBIOS the card had in a ZIP file, it is much smaller than the one in the TechPowerup website.
Regards
Regards
Got the second shut down:
Anonymous UUID: 9FEDE1A4-44E4-3CB4-439E-3CED4DF5D9EF
Tue Jan 19 09:04:38 2021
*** Panic Report ***
panic(cpu 0 caller 0xffffff802558687f): Kernel trap at 0xffffff7fa655d4d7, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000018, CR3: 0x0000000028e93000, CR4: 0x00000000000626e0
RAX: 0x0000000000000000, RBX: 0xffffff80570a2cc0, RCX: 0x0000000000000000, RDX: 0xffffff9682bebd70
RSP: 0xffffff9682bebd50, RBP: 0xffffff9682bebd50, RSI: 0xffffff805a3f40b8, RDI: 0xffffff9682bebd68
R8: 0xffffff805a3f3f1c, R9: 0x0000000000000001, R10: 0x0000000000000000, R11: 0xffffff8034bdefc0
R12: 0xffffff805a3f40b8, R13: 0xffffff805a3f3d80, R14: 0xffffff8055856e00, R15: 0xffffff9682bebd68
RFL: 0x0000000000010246, RIP: 0xffffff7fa655d4d7, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0x0000000000000018, Error code: 0x0000000000000002, Fault CPU: 0x0, PL: 0, VF: 1
Backtrace (CPU 0), Frame : Return Address
0xffffff9682beb820 : 0xffffff802546ae76
0xffffff9682beb870 : 0xffffff8025594484
0xffffff9682beb8b0 : 0xffffff8025586654
0xffffff9682beb920 : 0xffffff802541ce60
0xffffff9682beb940 : 0xffffff802546a8ec
0xffffff9682beba70 : 0xffffff802546a6ac
0xffffff9682bebad0 : 0xffffff802558687f
0xffffff9682bebc40 : 0xffffff802541ce60
0xffffff9682bebc60 : 0xffffff7fa655d4d7
0xffffff9682bebd50 : 0xffffff7fa6559e22
0xffffff9682bebdc0 : 0xffffff7fa648a0fa
0xffffff9682bebde0 : 0xffffff7fa648c2f7
0xffffff9682bebe10 : 0xffffff7fa647a282
0xffffff9682bebe80 : 0xffffff7fa6500ba3
0xffffff9682bebea0 : 0xffffff7fa6476334
0xffffff9682bebed0 : 0xffffff8025a988a5
0xffffff9682bebf30 : 0xffffff8025a97012
0xffffff9682bebf70 : 0xffffff8025a9663c
0xffffff9682bebfa0 : 0xffffff802541c557
Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(378.28)[D342FE41-0457-3586-ABB0-38E8E3947C4F]@0xffffff7fa6449000->0xffffff7fa64e1fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A4F333D5-7EC0-332F-A23B-558A0AC169A8]@0xffffff7fa6414000
dependency: com.apple.iokit.IOSurface(211.15)[37BCC686-AF99-3381-AC4F-E54A347E0F40]@0xffffff7fa642e000
dependency: com.apple.iokit.IOPCIFamily(2.9)[F763C275-306F-358F-B6B0-0FD93486BD5F]@0xffffff7fa5c94000
dependency: com.apple.iokit.IOGraphicsFamily(519.23)[81D774E8-DD11-3866-B90A-E855215EDB60]@0xffffff7fa6004000
com.apple.GeForce(10.3.2)[E95E1C10-8F87-326C-A7CD-61D8440918CD]@0xffffff7fa64f2000->0xffffff7fa658dfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[F763C275-306F-358F-B6B0-0FD93486BD5F]@0xffffff7fa5c94000
dependency: com.apple.iokit.IONDRVSupport(519.21)[B9EB0174-55E4-3CB1-9802-E74BB1BD5EF0]@0xffffff7fa605a000
dependency: com.apple.nvidia.driver.NVDAResman(10.3.2)[6DE4BC26-EEC1-379B-AD41-532FB0A529CD]@0xffffff7fa6076000
dependency: com.apple.iokit.IOGraphicsFamily(519.23)[81D774E8-DD11-3866-B90A-E855215EDB60]@0xffffff7fa6004000
dependency: com.apple.iokit.IOAcceleratorFamily2(378.28)[D342FE41-0457-3586-ABB0-38E8E3947C4F]@0xffffff7fa6449000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
17G14042
Kernel version:
Darwin Kernel Version 17.7.0: Fri Oct 30 13:34:27 PDT 2020; root:xnu-4570.71.82.8~1/RELEASE_X86_64
Kernel UUID: 5E83A13A-32F5-3604-8591-50E2F2F70DC6
Kernel slide: 0x0000000025200000
Kernel text base: 0xffffff8025400000
__HIB text base: 0xffffff8025300000
System model name: iMac12,2 (Mac-942B59F58194171B)
System uptime in nanoseconds: 63253919459
last loaded kext at 6480727256: com.apple.driver.AudioAUUC 1.70 (addr 0xffffff7fa837c000, size 32768)
loaded kexts:
com.paceap.kext.pacesupport.snowleopard 5.9.1
com.apple.driver.AudioAUUC 1.70
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleMikeyHIDDriver 131
com.apple.driver.AppleTyMCEDriver 1.0.3d2
com.apple.driver.AGPM 110.23.37
com.apple.driver.ApplePolicyControl 3.20.18
com.apple.driver.AppleMikeyDriver 281.52
com.apple.driver.AppleGraphicsDevicePolicy 3.20.18
com.apple.driver.AppleHDAHardwareConfigDriver 281.52
com.apple.AGDCPluginDisplayMetrics 3.20.18
com.apple.driver.AppleUpstreamUserClient 3.6.5
com.apple.driver.AppleHDA 281.52
com.apple.driver.AppleHV 1
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.driver.AGDCBacklightControl 3.20.18
com.apple.driver.AppleIntelHD3000Graphics 10.0.4
com.apple.GeForce 10.3.2
com.apple.iokit.IOBluetoothSerialManager 6.0.7f22
com.apple.driver.pmtelemetry 1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.eficheck 1
com.apple.driver.AppleBacklight 170.12.6
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleLPC 3.1
com.apple.driver.AppleSMCLMU 211
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleFIVRDriver 4.1.0
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.driver.AppleThunderboltIP 3.1.1
com.apple.driver.AppleMCCSControl 1.5.5
com.apple.driver.AppleIntelSNBGraphicsFB 10.0.4
com.apple.nvidia.NVDAStartup 10.3.2
com.apple.iokit.IOBluetoothUSBDFU 6.0.7f22
com.apple.driver.AppleUSBStorageCoexistentDriver 439.70.3
com.apple.driver.AppleUSBCardReader 439.70.3
com.apple.driver.AppleIRController 353
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.filesystems.hfs.kext 407.50.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.BootCache 40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.AppleSystemPolicy 1.0
com.apple.iokit.SCSITaskUserClient 404.30.3
com.apple.filesystems.apfs 748.51.0
com.apple.iokit.AppleBCM5701Ethernet 10.3.1
com.apple.driver.AirPort.Atheros40 700.74.5
com.apple.driver.AppleFWOHCI 5.5.9
com.apple.driver.AppleAHCIPort 329.50.2
com.apple.driver.AppleACPIButtons 6.1
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 6.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 220.50.1
com.apple.nke.applicationfirewall 186
com.apple.security.TMSafetyNet 8
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 220.50.1
com.apple.kext.triggers 1.0
com.apple.driver.AppleGraphicsControl 3.20.18
com.apple.driver.DspFuncLib 281.52
com.apple.kext.OSvKernDSPLib 526
com.apple.iokit.IOAVBFamily 683.1
com.apple.plugin.IOgPTPPlugin 680.15
com.apple.driver.AppleSSE 1.0
com.apple.nvidia.driver.NVDAGK100Hal 10.3.2
com.apple.iokit.IOAcceleratorFamily2 378.28
com.apple.iokit.IOSurface 211.15
com.apple.nvidia.driver.NVDAResman 10.3.2
com.apple.iokit.IOSerialFamily 11
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.AppleGPUWrangler 3.20.18
com.apple.AppleGraphicsDeviceControl 3.20.18
com.apple.driver.AppleHDAController 281.52
com.apple.iokit.IOHDAFamily 281.52
com.apple.iokit.IOAudioFamily 206.5
com.apple.vecLib.kext 1.2.0
com.apple.iokit.IONDRVSupport 519.21
com.apple.driver.AppleSMBusPCI 1.0.14d1
com.apple.iokit.IOFireWireIP 2.2.9
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 6.0.0d8
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.driver.AppleThunderboltEDMSink 4.1.4
com.apple.driver.AppleSMBusController 1.0.18d1
com.apple.iokit.IOGraphicsFamily 519.23
com.apple.driver.AppleHIDKeyboard 205.1
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 6.0.7f22
com.apple.iokit.IOBluetoothHostControllerUSBTransport 6.0.7f22
com.apple.iokit.IOBluetoothHostControllerTransport 6.0.7f22
com.apple.iokit.IOBluetoothFamily 6.0.7f22
com.apple.iokit.IOUSBMassStorageClass 4.0.4
com.apple.driver.usb.IOUSBHostHIDDevice 1.2
com.apple.driver.usb.cdc 5.0.0
com.apple.driver.usb.networking 5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice 1.2
com.apple.driver.usb.AppleUSBHub 1.2
com.apple.filesystems.hfs.encodings.kext 1
com.apple.iokit.IOSCSIMultimediaCommandsDevice 404.30.3
com.apple.iokit.IOBDStorageFamily 1.8
com.apple.iokit.IODVDStorageFamily 1.8
com.apple.iokit.IOCDStorageFamily 1.8
com.apple.driver.AppleThunderboltDPOutAdapter 5.5.5
com.apple.driver.AppleThunderboltDPInAdapter 5.5.5
com.apple.driver.AppleThunderboltDPAdapterFamily 5.5.5
com.apple.driver.AppleThunderboltPCIDownAdapter 2.1.3
com.apple.driver.AppleXsanScheme 3
com.apple.iokit.IOAHCISerialATAPI 267.50.1
com.apple.iokit.IOAHCIBlockStorage 301.40.2
com.apple.driver.AppleThunderboltNHI 4.7.3
com.apple.iokit.IOThunderboltFamily 6.7.10
com.apple.iokit.IOEthernetAVBController 1.1.0
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.iokit.IO80211Family 1200.12.2
com.apple.driver.corecapture 1.0.4
com.apple.iokit.IOFireWireFamily 4.7.2
com.apple.driver.AppleUSBMergeNub 900.4.1
com.apple.iokit.IOAHCIFamily 288
com.apple.driver.usb.AppleUSBEHCIPCI 1.2
com.apple.driver.usb.AppleUSBUHCIPCI 1.2
com.apple.driver.usb.AppleUSBUHCI 1.2
com.apple.driver.usb.AppleUSBEHCI 1.2
com.apple.driver.usb.AppleUSBHostPacketFilter 1.0
com.apple.iokit.IOUSBFamily 900.4.1
com.apple.driver.AppleUSBHostMergeProperties 1.2
com.apple.driver.AppleEFINVRAM 2.1
com.apple.driver.AppleEFIRuntime 2.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 480.60.3
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleEffaceableStorage 1.0
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleUSBTDM 439.70.3
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.iokit.IOUSBMassStorageDriver 140.70.2
com.apple.iokit.IOSCSIBlockCommandsDevice 404.30.3
com.apple.iokit.IOSCSIArchitectureModelFamily 404.30.3
com.apple.iokit.IOStorageFamily 2.1
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.KernelRelayHost 1
com.apple.iokit.IOUSBHostFamily 1.2
com.apple.driver.usb.AppleUSBCommon 1.0
com.apple.driver.AppleBusPowerController 1.0
com.apple.driver.AppleSEPManager 1.0.1
com.apple.driver.IOSlaveProcessor 1
com.apple.iokit.IOReportFamily 31
com.apple.iokit.IOTimeSyncFamily 680.15
com.apple.iokit.IONetworkingFamily 3.4
com.apple.driver.AppleACPIPlatform 6.1
com.apple.driver.AppleSMC 3.1.9
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.Libm 1
com.apple.kec.corecrypto 1.0
EOF
Model: iMac12,2, BootROM 87.0.0.0.0, 4 processors, Intel Core i7, 3,4 GHz, 20 GB, SMC 1.72f2
Graphics: NVIDIA Quadro K3100M by nikey22, NVIDIA Quadro K3100M by nikey22, PCIe
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142314737335148302D4348392020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142314737335148302D4348392020
Memory Module: BANK 0/DIMM1, 2 GB, DDR3, 1067 MHz, 0x02FE, 0x45424A3230554638424353302D444A2D4620
Memory Module: BANK 1/DIMM1, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x9A), Atheros 9380: 4.0.74.0-P2P
Bluetooth: Version 6.0.7f22, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: ST2000DM001-1ER164, 2 TB
Serial ATA Device: Samsung SSD 860 EVO 500GB, 500,11 GB
Serial ATA Device: OPTIARC DVD RW AD-5690H
USB Device: USB 2.0 Bus
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: USB2.0 Hub
USB Device: Mad Catz R.A.T.3 Mouse
USB Device: IR Receiver
USB Device: Internal Memory Card Reader
Thunderbolt Bus: iMac, Apple Inc., 22.1
I posted the report.
Can anyone tell me what happened and how I can solve the issue?
I don't understand the reports and can't help myself, so any help is more than welcome.
All the best and thanks in advance
Ekki
Good morning Canada!
This becomes an ongoing issue, can you make a short list of memory supported currently with each NVIDIA card? I will add this to the table on post #1
The most important thing is that whether the GPU can POST in your iMac.
if it does, read the first post for the various options of vBIOS flashing.
My experience with the Dell WX4130 is that the Dell PC vBIOS (unflashed) can provide an external display image.
So, you can see the Linux flashing process on an external monitor connected to your iMac miniDS port.
If not, the ch341a may come into play. But I am not certain whether a non-POSTing GPU can be made to be POSTing by flashing. You have to try for yourself in such circumstances.
You can put such panic reports into
[SPOILER=„My really important panic report“]The long an winding report[/SPOILER]. It make posts more readable...Can you comment on (patched) extensions you have installed additionelly to the stock High Sierra?
No, if the GPU refuses to POST (i.e. let the system turn on and play the starting chime) than it does not help to flash another BIOS. We tried this some time before with empty BIOS files (only containing a valid header). No changes. I guess we have to look into the iMac firmware in that case.
That is also my experience. I have a non-POSTing Dell WX4150 and a HP WX4150, both of which can't be made to work despite my successful flashing with ch341a. But my experience is limited, unlike the more definitive findings of our developers