InfiniteMac OSx86

InfiniteMac OSx86 (http://infinitemac.com/forum.php)
-   10.X (http://infinitemac.com/forumdisplay.php?f=36)
-   -   nvidia gforce 310m (http://infinitemac.com/showthread.php?t=5962)

pbg4 04-22-2010 06:37 AM

Quote:

Originally Posted by bujbot (Post 47623)
Do you think it is worth it to revert back to 10.5. from Snow Leopard for the QI/CL? I have a sony vaio as well, and I thought my Graphics Card wasn't being read properly because I didn't I have QI/CL.

I like to stay with Snow since my laptop support 64bit, but can't seem to get this graphic
card to work. What knid of Vaio do you have and everything is working for you?

bujbot 04-22-2010 04:38 PM

Quote:

Originally Posted by pbg4 (Post 47629)
I like to stay with Snow since my laptop support 64bit, but can't seem to get this graphic
card to work. What knid of Vaio do you have and everything is working for you?

I have the CW series laptop. It's the g210m card though, and I'm running SL in 32-bit. So far everything's running fine except sound (working on it now), wireless (although I have it working with a USB adapter), and graphic acceleration. The system profiler is finding the right information for the card, but I have no QE/CI, can't change resolution outside of the boot.plist, and can't control brightness.

I'm curious to know more about this issue with the sony screens.

I'm dual booting with windows and there's obviously no issues with the screen there.

bujbot 04-25-2010 06:53 PM

Quote:

Originally Posted by pbg4 (Post 47629)
I like to stay with Snow since my laptop support 64bit, but can't seem to get this graphic
card to work. What knid of Vaio do you have and everything is working for you?


Any progress pbg4?

I've done some research into the vaio LCD issue and it seems like it is affecting quite a few people. There were rumours of people trying to resolve the issue but I haven't found an update in a while. ...

I have my sony running pretty well right now. Only issues come down to the graphics (that I've found so far).

I was happy enough with no acceleration for the time being, but I didn't realize that the openGL affected 'preview', 'iphoto', 'VLC' etc.

pbg4 04-29-2010 04:58 PM

Quote:

Originally Posted by bujbot (Post 47739)
Any progress pbg4?

I've done some research into the vaio LCD issue and it seems like it is affecting quite a few people. There were rumours of people trying to resolve the issue but I haven't found an update in a while. ...

I have my sony running pretty well right now. Only issues come down to the graphics (that I've found so far).

I was happy enough with no acceleration for the time being, but I didn't realize that the openGL affected 'preview', 'iphoto', 'VLC' etc.

Well, right now, my vaio boot into LCD with basic driver and one resolution. Hardware acceleration seem to work but no QE/CI, but when I've plug in my HDMI cable to an external display monitor, I've get better result, FrontRow work and Dashboard widgets, I get that ripple when adding a widget, but I can't seem to get that to work in my build-in LCD. I've used GraphicsEnabler=Yes with the new MacbookProUpdate. Oh!, the only way for me to get my build-in Display I have to use PCIRootUID=1 otherwise black screen and have to plug in HDMI cable. Well keep searching for solutions. Post your finding if you get anything.

bujbot 05-06-2010 03:50 PM

So newest update for me.

I reset everything video related to start again from scratch. I injected my device ID into NVDAHal50, NVDARESman, and Geforce kext's. I used ATY_init.kext ... although it is for ATI video cards, according to project osx86 wiki it should work. Put graphics enabled = n in the boot plist, and PCI root to 0.

This gave me a black screen on the laptop, but plugging an external monitor into the HDMI port revealed perfect graphics acceleration. Quartz and everything.

So now I'm trying to figure out why it's routing the screen to the hdmi instead of the LCD. If I remove the NVDAResman.kext I get the LCD back but no graphic acceleration. So I looked into its kext package and noticed different arrays and what looked like display routing (NVidiaRM and NvidiaRMTwinView). ATY_init.kext appears to inject to a Display-A and a Display-B, so I replaced the NVDA,NVMac with NVDA,Display-A ... then I just got blackness with the LCD and external.

... so I'm going to look into it more. I need to find out what each display is being called with ... NVDA,Parent, NVDA,NVMac, NVDA,Display-A etc.

Any thoughts?

pbg4 05-08-2010 09:45 PM

Quote:

Originally Posted by bujbot (Post 47989)
So newest update for me.

I reset everything video related to start again from scratch. I injected my device ID into NVDAHal50, NVDARESman, and Geforce kext's. I used ATY_init.kext ... although it is for ATI video cards, according to project osx86 wiki it should work. Put graphics enabled = n in the boot plist, and PCI root to 0.

This gave me a black screen on the laptop, but plugging an external monitor into the HDMI port revealed perfect graphics acceleration. Quartz and everything.

So now I'm trying to figure out why it's routing the screen to the hdmi instead of the LCD. If I remove the NVDAResman.kext I get the LCD back but no graphic acceleration. So I looked into its kext package and noticed different arrays and what looked like display routing (NVidiaRM and NvidiaRMTwinView). ATY_init.kext appears to inject to a Display-A and a Display-B, so I replaced the NVDA,NVMac with NVDA,Display-A ... then I just got blackness with the LCD and external.

... so I'm going to look into it more. I need to find out what each display is being called with ... NVDA,Parent, NVDA,NVMac, NVDA,Display-A etc.

Any thoughts?

Reinstalled Snow Leopard with the new Retail DVD v10.6.3. and apply the MacBookPro updates from Apple still get the same results. Just can't get the internal display to have QE/CI. Internal display show when I've added in device ID to NVDResman and NVDAHal50. Without adding my device ID to these two files, the internal display dosen't show and have to plug in HDMI cable. With device ID inserted ,my registry infos. show routing to Display B for internal display. Was looking into DSDT editing, but no luck. So nothing new for now. I'm going to try looking into NVCAP editing,maybe that might help.Well let you know how it's goes.Dose your Wi-Fi and sound works?

tbob18 08-07-2010 06:44 PM

I have the older Vaio Z with the 9300m GS and I have this same problem, after I install the drivers only video out (VGA/HDMI) works and QE/CI does work, but the internal monitor is not detected and stays blank.

The only way to get anything on the internal display is to remove the drivers. On the Intel it is possible to get the proper resolution using Chameleon and the Graphics Mode option but still no QE/CI, I have not figured out how to get the proper resolution on the nVidia at all.

There are proper drivers for both sides on Ubuntu using the Sony-VGN-Zseries-janitor script, but it still only supports cold switching (have to reboot to switch the GPU), maybe this could somehow be ported to OSX. :-/