Jump to content

GeForce GTS 250M works 10% of the time in 10.8.2

Karol Trojanowski

By Karol Trojanowski,
in OSx86 10.8 (Mountain Lion)

 Share
12 posts in this topic

Recommended Posts

Karol Trojanowski
Karol Trojanowski
Posted
Posted

Hi all,

 

I'm writing this in pale hope because I'm positive I've tried almost everything.

 

I own a MSI GT 640 gaming series laptop with a GTS 250M (device id 0ca9), AKA GT215. I had a happy flawless install of Lion where it worked with GraphicsEnabler=Yes.

 

I installed Mountain Lion 10.8.2 using HackInstaller and now it boots fine until the login window is about to come up and 90% of the time the computer just hangs. Once every 8-10 boots it will bring up the login screen and from then on everything (Quartz, compositing, OpenGL games, sleep, AGPM) will work fine.

 

It also appears that I need to shuffle between Graphics Modes between reboots because it will not boot twice in the same graphics mode. In native resolution 1680x1050x32 set up in Chameleon 90% of the time I will get a RED SCREEN and lockup and every now and then a login screen. In all other VESA modes a most likely occurence will be a "You need to turn off your computer..." message.

 

Verbose mode doesn't change anything. debug=0x144 prints no information (it appears that the computer is really locked up).

 

Things I've tried:

  • switching bootloaders (I'm currently on Chameleon SVN r2054, best results so far)
  • PCIRootUID=1 gives a black screen, always
  • -x boots ok without Quartz obviously
  • nVidia kexts NVDANV50hal.kext and NVDAResman.kext from: DP1, DP2, DP3, DP4 (best) and new nVidia drivers (also work), Lion
  • editing kexts to include IOPCIMatch for my card (0ca9), no difference
  • switching Quartz.framework and QuartzCore.framework from Lion (fails to boot) and DP1 (no difference)
  • GraphicsEnabler=No ends up with a black (disabled) screen, but the card is detected (NVDANV50HAL loaded and registered)
  • custom EFI string, injected EFI string from Lion and once, when it booted fine, from Mountain Lion
  • npci=0x2000, npci=0x3000 make no difference
  • I use DSDT patched by HackInstaller, but DSDT=No makes no difference
  • probably any combination of boot flags possible...

Unfortunately there is no VBIOS for my card to download so I can't try POST-ing with Chameleon. Anyone knows how I can drop it from my card on Windows?

 

If anyone could possibly help me, I would be very greatful.

Link to comment
Share on other sites
eep357
eep357
Posted
Posted

VBIOS can be dumped for most cards in Windows using GPU-z, will get a bin file, that can be renamed to .rom. Have no clue what Hackinstaller does, or doesn't do to a DSDT, as is always the problem with click and go stuff. Clover is another alternate choice for bootloader. bdmesg may also have some more useful info in it.

Link to comment
Share on other sites
Karol Trojanowski
Karol Trojanowski
Posted
  • Author
Posted

Weird my GTS 250M seems to work better than ever with ML (10.8.2) just using graphicsenabler=yes in chameleon...

Maybe there are different GTS 250M models?

 

Maybe. Mine is manufactured by MSI according to lspci. Here's what I see in lspci -vvnn

 

01:00.0 VGA compatible controller [0300]: nVidia Corporation Unknown device [10de:0ca9] (rev a2) (prog-if 00 [VGA controller])
       Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:102f]
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
       Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
       Latency: 0
       Interrupt: pin A routed to IRQ 16
       Region 0: Memory at d2000000 (32-bit, non-prefetchable)
       Region 1: Memory at c0000000 (64-bit, prefetchable)
       Region 3: Memory at d0000000 (64-bit, prefetchable)
       Region 5: I/O ports at d000
       Capabilities: [60] Power Management version 3
               Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-
       Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
               Address: 00000000fee00000  Data: 4092
       Capabilities: [78] Express (v2) Endpoint, MSI 00
               DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
                       ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
               DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                       RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
                       MaxPayload 128 bytes, MaxReadReq 256 bytes
               DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
               LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <256ns, L1 <4us
                       ClockPM+ Suprise- LLActRep- BwNot-
               LnkCtl: ASPM L1 Enabled; RCB 128 bytes Disabled- Retrain- CommClk+
                       ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
               LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
       Capabilities: [b4] Vendor Specific Information <?>
       Capabilities: [100] #10de

 

Maybe you could dump your injection string so I could try it? This is the command:

ioreg -lw 0 -p IODeviceTree | grep device-prop

 

I have the 1GB RAM version.

 

I installed Clover, but as of now I can't make sense of how it handles graphics. With default settings it just reboots where the login screen is supposed to appear. For now I'm back to Chameleon.

Link to comment
Share on other sites
mtek
mtek
Posted
Posted

Done! Hope it helps...

 

 

| |   "device-properties" = <500300000100000002000000050300001100000002010c00d041030a000000000101060000030101060000007fff04002e000000400030002c004100410050004c002c0062006f006f0074002d0064006900730070006c0061007900000008000000010000001c000000400030002c006200750069006c0074002d0069006e000000050000000120000000400030002c0063006f006d00700061007400690062006c00650000000f0000004e5644412c4e564d61630022000000400030002c006400650076006900630065005f00740079007000650000000c000000646973706c61790014000000400030002c006e0061006d0065000000130000004e5644412c446973706c61792d410020000000400031002c0063006f006d00700061007400690062006c00650000000f0000004e5644412c4e564d61630022000000400031002c006400650076006900630065005f00740079007000650000000c000000646973706c61790014000000400031002c006e0061006d0065000000130000004e5644412c446973706c61792d42001c0000006400650076006900630065005f0074007900700065000000100000004e5644412c506172656e7400220000004100410050004c002c0073006c006f0074002d006e0061006d00650000000a000000536c6f742d31100000004e0056004300410050000000180000000400000000000100fe0000000000000a000000000e0000004e00560050004d0000002000000001000000000000000000000000000000000000000000000000000000220000005600520041004d002c0074006f00740061006c00730069007a00650000000800000000000040100000006d006f00640065006c000000150000004765466f72636520475453203235304d001e00000072006f006d002d007200650076006900730069006f006e0000001300000037302e31352e31352e30302e30360022000000400030002c0064006900730070006c00610079002d006300660067000000080000000301030022000000400031002c0064006900730070006c00610079002d00630066006700000008000000ffff00013f0000000100000002010c00d041030a0000000001010600061c0101060000007fff0400160000006200750069006c0074002d0069006e0000000500000001>
   | |   "device-properties" = {"PinConfigurations"=<00>,"layout-id"=<0c000000>,"hda-gfx"=<"onboard-1">,"model"=<"Conexant Cx20583">,"built-in"=<00>,"subsystem-vendor-id"=<79110000>,"codec-id"=<6750f114>,"device_type"=<506562626c652048534600000000000000000000000000>,"subsystem-id"=<50ff0000>}

  • Like 1
Link to comment
Share on other sites
mtek
mtek
Posted
Posted

 

 

Mine is identical. I guess I'm just out of luck. Thanks for the effort though :)

 

Did you a try a clean ML install? I had some strange issues when I upgraded from Lion in the first place, although not as far as I noticed related to the graphic card.

With a clean ML install everything worked out smoothly oob.

Link to comment
Share on other sites
Karol Trojanowski
Karol Trojanowski
Posted
  • Author
Posted

Did you a try a clean ML install? I had some strange issues when I upgraded from Lion in the first place, although not as far as I noticed related to the graphic card.

With a clean ML install everything worked out smoothly oob.

 

Yes it's a clean install. I tried ###### first, in fact, and the result was identical. I ran the process from the beginning 3 times already.

 

Edit: Oh well, I got censored :) I first used, you know, the OTHER installer :)

Link to comment
Share on other sites
  • 2 weeks later...
C.Frio
C.Frio
Posted
Posted

Hi...

 

as you did a lot ...boot with a external monitor connected...

 

did you try to use all the files from hackinstaller(as it booted ok for installation), instead a chameleon alone, and then adjust with ML working?

 

c.frio

Link to comment
Share on other sites
Karol Trojanowski
Karol Trojanowski
Posted
  • Author
Posted

Hi...

 

as you did a lot ...boot with a external monitor connected...

 

did you try to use all the files from hackinstaller(as it booted ok for installation), instead a chameleon alone, and then adjust with ML working?

 

c.frio

 

Hi, thanks for the reply. I tried booting with an external display, it did nothing (no signal). As for HackInstaller, I did not point out that I removed the NVDA* kexts from S/L/E on the install media because the result was identical.

 

Cheers.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...