Jump to content

Leopard on Series 7 NVIDIA nForce MCP + Intel CPU MOBOs

verdant

By verdant,
in OSx86 10.5 (Leopard)

 Share

Installer Packages for nForce chipset MOBOs  

143 members have voted

  1. 1. Would you be willing to donate an amount of your choosing to Mysticus C* to enable him to continue making and updating nForce chipset + Intel CPU MOBO-focussed Kernel/Drivers Installer packages, Combo Updater Packages......possibly even a DVD......?

    • Yes, before new and/or updated packages are released
      22
    • Yes, after new and/or updated packages are released
      18
    • Yes, but only after I have used the new and/or updated packages successfully on my system
      60
    • Unsure, I may donate after I have used the new and/or updated packages successfully on my system
      38
    • No
      5

  2. 2. Level of Demand for Installer Packages for nForce chipset MOBOs

    • Would you like it if new and/or updated installer packages for nForce chipset + Intel CPU MOBOs were to be developed by an OSx86 forum member?
      103
    • Would you be willing to donate an amount of your choosing to such a developer using an nForce chipset + Intel CPU nForce MOBO?
      68
    • Would you like it if new and/or updated installer packages for nForce chipset + AMD CPU MOBOs were to be developed by an OSx86 forum member?
      27
    • Would you be willing to donate an amount of your choosing to such a developer using an nForce chipset + AMD CPU nForce MOBO?
      20
    • Do you have a DESKTOP nForce chipset MOBO?
      109
    • Do you have a LAPTOP/NOTEBOOK nForce chipset MOBO?
      13

  3. 3. Nature of donations offered

    • Would you prefer to donate hardware (in good faith on the basis of trust) acceptable to the developer, to enable him/her to build a system on which to develop the installer packages?
      21
    • Would you prefer to donate cash (in good faith on the basis of trust) to the developer to defray his/her upfront cost of acquiring a system on which to develop the installer packages?
      122

1,138 posts in this topic

Recommended Posts

verdant
verdant
Posted
  • Author
Posted
@verdant

 

I saw a post of yours about GFX Strings, and had attempted trying them once, but as I know very little about GFX Strings, I had thought they were for Intel based mobos only (much like Vanilla Kernels). After seeing your post, I realized they were not. I decided to give GFX Strings a shot and I now have 1680x1050! Thanks!! This is great progress. It's amazing how going from 1024x768 to native resolution makes the machine much more usable.

 

A couple questions. I have the below in my Extensions folder:

 

GeForce.kext

GeForce2MXGLDriver.bundle

GeForce3GLDriver.bundle

GeForce7xxxGLDriver.bundle

GeForce8xxxGLDriver.bundle

GeForceFXGLDriver.bundle

GeForceGA.plugin

GeForceVADriver.bundle

 

NVDANV50Hal.kext

NVDANV40Hal.kext

NVDANV30Hal.kext

NVDANV20Hal.kext

NVDANV10Hal.kext

 

I removed the NVDAResman.kext file because it was still causing hangs with the loginwindow.

 

From my understanding, as for the NVDANV files, all I really need to pay attention to for my 8800 is the NVDANV50Hal.kext file. With GFX Strings, I am also assuming I still need to mod the info.plist files with my device id's??

 

Am I missing anything here??

 

No that is about it......I have my 8600GT running with an EFI GFX string in com.apple.Boot.plist and in Extensions folder I have

 

GeForce.kext

GeForce2MXGLDriver.bundle

GeForce3GLDriver.bundle

GeForce7xxxGLDriver.bundle

GeForce8xxxGLDriver.bundle

GeForceFXGLDriver.bundle

GeForceGA.plugin

GeForceVADriver.bundle

 

NVDANV50Hal.kext

NVDANV40Hal.kext

NVDANV30Hal.kext

NVDANV20Hal.kext

NVDANV10Hal.kext

 

so it is not immediately obvious why NVDAResman.kext is causing you problems...

Link to comment
Share on other sites
Metralha
Metralha
Posted
Posted

ok i need some lights here, i do lots of graphics and also games, and i need to put a new system together so i can test OSx86 on it and be able to also do the rest that i do.. i just need a good MOBO, im thinking of Asus striker II 790i ultra any advice welcome, ill still trying on my 780i tho :D so i can give any helpfull feedback :angel:

Link to comment
Share on other sites
icedtrip
icedtrip
Posted
Posted

@verdant

 

You mentioned in a previous post about IONDRVSupport.kext. What does this kext do? I have looked into it and found that some people use to recommend deleting this once all other video kexts are in place and ready to go. I have tried removing it, and leaving it in. Do I need to include my device ID in this as well? There is an IOPCIClassMatch in the info.plist, but is this an nvidia kext? Thanks.

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
@verdant

 

You mentioned in a previous post about IONDRVSupport.kext. What does this kext do? I have looked into it and found that some people use to recommend deleting this once all other video kexts are in place and ready to go. I have tried removing it, and leaving it in. Do I need to include my device ID in this as well? There is an IOPCIClassMatch in the info.plist, but is this an nvidia kext? Thanks.

 

AFIK the IONDRVSupport.kext is for very old graphic chipsets (circa 1997) but is important because it enables basic VGA so that you can still have working video when all other video driver kexts are missing and/or corrupted.......so if you do remove back it up so that if necessary you can reload it via single user mode back into S/L/Extensions......

Link to comment
Share on other sites
icedtrip
icedtrip
Posted
Posted

Here is the last system.log from my last failed boot trying to get QE/CI working. It is always hanging at this point now with the following kexts:

 

GeForce.kext

GeForce2MXGLDriver.bundle

GeForce3GLDriver.bundle

GeForce7xxxGLDriver.bundle

GeForce8xxxGLDriver.bundle

GeForceFXGLDriver.bundle

GeForceGA.plugin

GeForceVADriver.bundle

 

NVDANV10Hal.kext

NVDANV20Hal.kext

NVDANV30Hal.kext

NVDANV40Hal.kext

NVDANV50Hal.kext

NVDAResman.kext

 

Oct 13 19:55:50 localhost kernel[0]: npvhash=4095
Oct 13 19:55:49 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/chum.plist
Oct 13 19:55:49 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
Oct 13 19:55:49 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/pilotfish.plist
Oct 13 19:55:49 localhost com.apple.launchd[1] (com.apple.distccdConfigd): Unknown key: SHAuthorizationRight
Oct 13 19:55:49 localhost com.apple.launchd[1] (org.cups.cupsd): Unknown key: SHAuthorizationRight
Oct 13 19:55:49 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight
Oct 13 19:55:50 localhost DirectoryService[11]: Launched version 5.5 (v514.23)
Oct 13 19:55:50 localhost kernel[0]: hi mem tramps at 0xffe00000
Oct 13 19:55:50 localhost DirectoryService[11]: Improper shutdown detected
Oct 13 19:55:50 localhost kernel[0]: PAE enabled
Oct 13 19:55:50 localhost kernel[0]: 64 bit mode enabled
Oct 13 19:55:50 localhost kernel[0]: enabling INTEL features
Oct 13 19:55:50 localhost kernel[0]: Darwin Kernel Version 9.4.0: Fri Aug  1 21:34:49 EST 2008; ToH & StageXNU:xnu-1228.5.20/BUILD/obj/RELEASE_I386
Oct 13 19:55:50 localhost kernel[0]: standard timeslicing quantum is 10000 us
Oct 13 19:55:50 localhost kernel[0]: vm_page_bootstrap: 510198 free pages and 14090 wired pages
Oct 13 19:55:50 localhost kernel[0]: mig_table_max_displ = 79
Oct 13 19:55:50 localhost kernel[0]: ACPI CA 20051117 [debug level=0 layer=0]
Oct 13 19:55:50 localhost kernel[0]: Extension "com.apple.driver.AppleIntelCPUPowerManagement" has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style.
Oct 13 19:55:50 localhost kernel[0]: Class "AppleIntelCPUPowerManagement" is duplicate
Oct 13 19:55:50 localhost kernel[0]: Duplicate class
Oct 13 19:55:50 localhost kernel[0]: kmod_control/start failed for com.apple.driver.AppleIntelCPUPowerManagement; destroying kmod
Oct 13 19:55:50 localhost kernel[0]: ^[[33mFailed to load extension com.apple.driver.AppleIntelCPUPowerManagement.
Oct 13 19:55:50 localhost kernel[0]: ^[[0mAppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
Oct 13 19:55:50 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
Oct 13 19:55:50 localhost kernel[0]: AppleACPICPU: ProcessorApicId=2 LocalApicId=2 Disabled
Oct 13 19:55:50 localhost kernel[0]: AppleACPICPU: ProcessorApicId=3 LocalApicId=3 Disabled
Oct 13 19:55:50 localhost kernel[0]: Loading security extension com.apple.nke.applicationfirewall
Oct 13 19:55:50 localhost kernel[0]: Loading security extension com.apple.security.seatbelt
Oct 13 19:55:50 localhost kernel[0]: calling mpo_policy_init for mb
Oct 13 19:55:50 localhost kernel[0]: Seatbelt MACF policy initialized
Oct 13 19:55:50 localhost kernel[0]: Security policy loaded: Seatbelt Policy (mb)
Oct 13 19:55:50 localhost kernel[0]: Loading security extension com.apple.security.TMSafetyNet
Oct 13 19:55:50 localhost kernel[0]: calling mpo_policy_init for TMSafetyNet
Oct 13 19:55:50 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Oct 13 19:55:50 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Oct 13 19:55:50 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Oct 13 19:55:50 localhost kernel[0]: MAC Framework successfully initialized
Oct 13 19:55:50 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
Oct 13 19:55:50 localhost kernel[0]: IOAPIC: Version 0x11 Vectors 0:23
Oct 13 19:55:50 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Oct 13 19:55:50 localhost kernel[0]: Extension "com.apple.driver.ApplePCIConfigurator" has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style.mbinit: done
Oct 13 19:55:50 localhost kernel[0]: Security auditing service present
Oct 13 19:55:50 localhost kernel[0]: BSM auditing present
Oct 13 19:55:50 localhost kernel[0]: From path: "uuid", 
Oct 13 19:55:50 localhost kernel[0]: Waiting for boot volume with UUID 135FABED-795F-31AD-9833-E614485FB857
Oct 13 19:55:50 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: found 0 units.
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: found 2 units.
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: NVIDIA nForce MCP 51 by MeDevil (CMD 0x1f0, CTR 0x3f4, IRQ 14, BM 0xfd00)
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: sata phy reset done.
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: found 1 units.
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: NVIDIA nForce MCP 51 Serial ATA by MeDevil (CMD 0x9f0, CTR 0xbf0, IRQ 23, BM 0xf800)
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: sata phy reset done.
Oct 13 19:55:50 localhost kernel[0]: USBF:	0.493	Attempting to get EHCI Controller from BIOS
Oct 13 19:55:50 localhost kernel[0]: USBF:	0.494	USBLEGCTLSTS value e0040000
Oct 13 19:55:50 localhost kernel[0]: USBF:	0.495	EHCI - Ownership conflict - attempting soft reset ...
Oct 13 19:55:50 localhost kernel[0]: USBF:	0.496	EHCI - toggle OS Ownership to 0
Oct 13 19:55:50 localhost kernel[0]: USBF:	0.497	Found USBLEGSUP_ID - value 0x1 - writing OSOwned
Oct 13 19:55:50 localhost kernel[0]: USBF:	0.498	acquireOSOwnership done - value 0x1000001
Oct 13 19:55:50 localhost kernel[0]: USBF:	5.330	AppleUSBOHCI[0x4a58000]::CheckSleepCapability - OHCI controller will be unloaded across sleep
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: found 1 units.
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: NVIDIA nForce MCP 51 Serial ATA by MeDevil (CMD 0x970, CTR 0xb70, IRQ 23, BM 0xf808)
Oct 13 19:55:50 localhost kernel[0]: FireWire (OHCI) VendorID 1106 ID 3044 PCI now active, GUID 001e8c00013780d5; max speed s400.
Oct 13 19:55:50 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SAT1@E/AppleNForceATARoot/SEC0@1/AppleNForceATA/ATADeviceNub@0/AppleATADiskDriver/IOATABlockStorageDevice/IOBlockStorageDriver/ST3500630AS ST3500630AS/IOFDiskPartitionScheme/Untitled 1@1
Oct 13 19:55:50 localhost kernel[0]: BSD root: disk0s1, major 14, minor 1
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: warning: phy connection failed. status=0x00000000
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: found 0 units.
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: warning: phy connection failed. status=0x00000000
Oct 13 19:55:50 localhost kernel[0]: AppleNForceATA: found 0 units.
Oct 13 19:55:50 localhost kernel[0]: Jettisoning kernel linker.
Oct 13 19:55:50 localhost kernel[0]: Resetting IOCatalogue.
Oct 13 19:55:50 localhost kernel[0]: Matching service count = 2
Oct 13 19:55:50 localhost kernel[0]: Matching service count = 3
Oct 13 19:55:51: --- last message repeated 4 times ---
Oct 13 19:55:51 localhost kextd[10]: 409 cached, 0 uncached personalities to catalog
Oct 13 19:55:52 localhost kernel[0]: NVDANV50HAL loaded and registered.
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: Version 0.61.4alpha_osx initializing
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: setting optimization mode: cpu
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: Probing.
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: found nVidia MCP51 Ethernet Controller device 10de:0269 with flags 0x0000030b
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: Starting.
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: found power management capability at 68
Oct 13 19:55:52 localhost kernel[0]: Apple16X50ACPI1: Identified Serial Port on ACPI Device=UAR1
Oct 13 19:55:52 localhost kernel[0]: Apple16X50UARTSync1: Detected 16550AF/C/CF FIFO=16 MaxBaud=115200nForceLAN: PCI system 0x10DE:0x0269, subsystem 0x1043:0x8221 revision 0xA3 opened.
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: Mapped from 0xFE02B000 of length 4096.
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: Found nForce LAN with MAC: 00:1F:C6:7E:58:C3.
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: Taking PHY and NIC out of low power mode
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: Found PHY 0x1340:0x0034 at address 1.
Oct 13 19:55:52 localhost kernel[0]: ath_attach: devid 0x23
Oct 13 19:55:52 localhost kernel[0]: NVDA::probe(display)
Oct 13 19:55:52 localhost kernel[0]: NVDA::start(display) <1>
Oct 13 19:55:52 localhost kernel[0]: NVDA::start(display) <1> failed
Oct 13 19:55:52 localhost kernel[0]: ALCinject: Starting.
Oct 13 19:55:52 localhost kernel[0]: ALCinject: Setting built-in=<data not shown>
Oct 13 19:55:52 localhost kernel[0]: ALCinject: Setting layout-id=<data not shown>
Oct 13 19:55:52 localhost kernel[0]: dsmos: Initializing...
Oct 13 19:55:52 localhost kernel[0]: dsmos: Hook and decryption contexts set!
Oct 13 19:55:52 localhost kernel[0]: dsmos: Starting...
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: registerWithPolicyMaker: entering ...
Oct 13 19:55:52 localhost kernel[0]: nForceLAN: setPowerState: old state: 1, new state: 1
Oct 13 19:55:52 localhost kernel[0]: Override Target Powers. EEPROM Version is 14.2, Device Type 0
Oct 13 19:55:52 localhost kernel[0]: Override HT40 CTL Powers. EEPROM Version is 14.2, Device Type 0
Oct 13 19:55:53 localhost kernel[0]: mac 13.10 phy 8.1 radio 13.0
Oct 13 19:55:53 localhost mDNSResponder mDNSResponder-176.2 (Aug 15 2008 14:58:54)[35]: starting
Oct 13 19:55:53 localhost configd[14]: Error: No interface name for AirPort_Athr5424ab
Oct 13 19:55:53 localhost configd[14]: Error: ioPublishedDriverCallback() failed to initDeviceFromService()
Oct 13 19:55:53 wolfdale kernel[0]: nForceLAN: Ethernet address 00:1f:c6:7e:58:c3
Oct 13 19:55:53 wolfdale kernel[0]: AirPort_Athr5424ab: Ethernet address 00:1e:58:3b:16:9f
Oct 13 19:55:53 wolfdale kernel[0]: ATHR: unknown locale: 10
Oct 13 19:55:53 wolfdale configd[14]: setting hostname to "wolfdale.local"
Oct 13 19:55:53 wolfdale com.apple.SecurityServer[40]: src/CCIDDriver/specific/MacOSX/tools_mosx.c (63): Bundle InfoDic error: ifdReadTimeOut not found
Oct 13 19:55:53 wolfdale kernel[0]: nForceLAN: setBufSize/Apple wants 1500 bytes
Oct 13 19:55:53 wolfdale com.apple.launchd[1] (com.openssh.sshd): Unknown key: SHAuthorizationRight
Oct 13 19:55:53 wolfdale com.apple.SecurityServer[40]: src/CCIDDriver/USB/MacOSX/usbserial_mosx.c (1061): Captured device manufacturer is SCM Microsystems Inc.
Oct 13 19:55:53 wolfdale com.apple.SecurityServer[40]: src/CCIDDriver/USB/MacOSX/usbserial_mosx.c (1061): Captured device product name is SCR3310 USB Smart Card Reader
Oct 13 19:55:53 wolfdale com.apple.SecurityServer[40]: src/CCIDDriver/USB/MacOSX/usbserial_mosx.c (1061): Captured device serial number is 21120747245580
Oct 13 19:55:53 wolfdale com.apple.launchd[1] (com.apple.distccdConfigd[60]): Exited with exit code: 255
Oct 13 19:55:53 wolfdale kernel[0]: nForceLAN: setBufSize/We can give them 1500 bytes
Oct 13 19:55:53 wolfdale kernel[0]: nForceLAN: setBufSize/Setting with regards to mtu(1500) -- 1564 bytes
Oct 13 19:55:53 wolfdale fseventsd[56]: bumping event counter to: 0x32c18e (current 0x0) from log file '0000000000001cf3'
Oct 13 19:55:53 wolfdale kernel[0]: nForceLAN: Enabling... 1 2 3 4 5 6 7
Oct 13 19:55:53 wolfdale kernel[0]: nForceLAN: Starting transmit/receive engines
Oct 13 19:55:54 wolfdale kernel[0]: nForceLAN: Network link down.
Oct 13 19:55:54 wolfdale kernel[0]: nForceLAN: setMode (true, false)
Oct 13 19:55:54 wolfdale kernel[0]: nForceLAN: setMode (false, false)
Oct 13 19:55:54 wolfdale rpc.statd[47]: statd.notify - no notifications needed
Oct 13 19:55:54 wolfdale bootlog[64]: BOOT_TIME: 1223942142 0
Oct 13 19:55:55 wolfdale kernel[0]: NTFS driver 2.1 [Flags: R/O].
Oct 13 19:55:55 wolfdale kernel[0]: NTFS volume name , version 3.1.
Oct 13 19:55:55 wolfdale kernel[0]: nForceLAN: Link speed now 1000Mbps(full-duplex = 1), code 0x10032.
Oct 13 19:55:55 wolfdale kernel[0]: nForceLAN: setMode (true, false)
Oct 13 19:55:55 wolfdale kernel[0]: NTFS volume name icey_games, version 3.1.
Oct 13 19:55:55 wolfdale org.ntp.ntpd[44]: Error : nodename nor servname provided, or not known
Oct 13 19:55:55 wolfdale ntpdate[96]: can't find host time.apple.com
Oct 13 19:55:55 wolfdale ntpdate[96]: no servers can be used, exiting
Oct 13 19:55:55 wolfdale ntpd[44]: bind() fd 25, family 30, port 123, scope 4, addr fe80::21f:c6ff:fe7e:58c3, in6_is_addr_multicast=0 flags=17 fails: Can't assign requested address
Oct 13 19:55:56 wolfdale /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[51]: Login Window Application Started
Oct 13 19:55:56 wolfdale /usr/sbin/ocspd[99]: starting
Oct 13 19:55:57 wolfdale kernel[0]: ERROR: FireWire unable to determine security-mode; defaulting to full-secure.
Oct 13 19:56:02 wolfdale kextd[10]: writing kernel link data to /var/run/mach.sym

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
Here is the last system.log from my last failed boot trying to get QE/CI working. It is always hanging at this point now with the following kexts:

 

GeForce.kext

GeForce2MXGLDriver.bundle

GeForce3GLDriver.bundle

GeForce7xxxGLDriver.bundle

GeForce8xxxGLDriver.bundle

GeForceFXGLDriver.bundle

GeForceGA.plugin

GeForceVADriver.bundle

 

NVDANV10Hal.kext

NVDANV20Hal.kext

NVDANV30Hal.kext

NVDANV40Hal.kext

NVDANV50Hal.kext

NVDAResman.kext

 

EDIT: deleted quoted boot screen dump.....see original post this post is replying to....

 

Perhaps you are getting a conflict between onboard LAN and AirPort(Atheros).........as both are pulling an Ethernet address......but there are errors associated with Airport(Atheros).....you could try removing the NForceLAN and/or Atheros kexts via single user mode......you could also boot with -v debug=0x100 to get info on kernel panics.....

Link to comment
Share on other sites
icedtrip
icedtrip
Posted
Posted
Perhaps you are getting a conflict between onboard LAN and AirPort(Atheros).........as both are pulling an Ethernet address......but there are errors associated with Airport(Atheros).....you could try removing the NForceLAN and/or Atheros kexts via single user mode......you could also boot with -v debug=0x100 to get info on kernel panics.....

 

Just tried removing both kext's and got the same result. Same hanging at the same spot. I have attached my kext's. From what I have found, the only ones of real importance are:

 

GeForce.kext

NVDANV50Hal.kext

NVDAResman.kext

 

So I have only included those. Any ideas? Missing anything you can see?

 

EDIT: Upload didn't work. Can't get them uploaded.....looking into it.

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted

@icedtrip

 

Just tried removing both kext's and got the same result. Same hanging at the same spot. I have attached my kext's. From what I have found, the only ones of real importance are:

 

GeForce.kext

NVDANV50Hal.kext

NVDAResman.kext

 

So I have only included those. Any ideas? Missing anything you can see?

 

EDIT: Upload didn't work. Can't get them uploaded.....looking into it.

 

In trying to get full CI/QE and hence playing around with extensions, you may have some kext metakext "mismatches"......suggest you delete your extensions.mkext and extensions.kextcache files to see if that makes a difference......other kexts that can cause problems are

 

AppleEFIRuntime.kext

AppleInteCPUPowerManagement.kext

AppleHWSensor.kext

 

@ Galileo5

 

(Galileo5 @ Oct 14 2008, 09:42 AM) post_snapback.gifThanks for reply...

 

Thanks for reply to what.....?

Link to comment
Share on other sites
 Mysticus C*
 Mysticus C*
Posted
Posted

my best bet for getting the nvidia card working on an nforce mobo, is to first disable the on board network! (it is the most troublesome)

 

second add the correct class identification (of cource correct device id to correct driver as well) to nvd* gef* drivers... if you have seen my combo update package, and inspected with pacifist, there is an option for nvidia gfx drivers fix for nforce chipset... you need class identification on nforce mobo!!! (intel gfx drivers dont have problem bcoz they have the class identification... what is class identification? a driver should load for a correct type of device, e,g, vga driver should not load for network or chipset... get the idea?)

 

third check the nvinject website for suggestions regarding nvcap values for that specific models/ranges... i m sure there may be solutions...

 

good luck...

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
my best bet for getting the nvidia card working on an nforce mobo, is to first disable the on board network! (it is the most troublesome)

 

second add the correct class identification to nvd* gef* drivers... if you have seen my combo update package, and inspected with pacifist, there is an option for nvidia gfx drivers fix for nforce chipset... you need class identification on nforce mobo!!! (intel gfx drivers dont have problem bcoz they have the class identification... what is class identification? a driver should load for a correct type of device, e,g, vga driver should not load for network or chipset... get the idea?)

 

third check the nvinject website for suggestions regarding nvcap values for that specific models/ranges... i m sure there may be solutions...

 

good luck...

 

Hi Mysticus,

 

Thanks for the 3 helpful suggestions.......I would hope that readers would have disabled onboard LAN initially as my BIOS template recommends?......would those nForce MOBO owners having problems, especially with the "normally" posted solutions for 8800 GT or 8800 GTS GFX cards, be able to try just running your post 10.5.5 Combo updater package choosing correct NVinject with the correct RAM PLUS the nvidia gfx drivers fix.......i.e. without trying to update to 10.5.5 before their GFX card is working OK.....?

 

@ All readers

 

Eno has made much welcome progress with his nForceLAN driver kext for nForce MOBO onboard LAN e.g.

 

Known working physical devices:

Realtek 8211, 8211B, 8211C

Realtek/Cicada/Vitesse 8201

Marvel 88E1116, 88E3016

 

Supported PCI ids:

0x01c310de, 0x006610de, 0x00d610de, 0x008610de, 0x008c10de, 0x00e610de, 0x00df10de,

0x005610de, 0x005710de 0x003710de, 0x003810de, 0x026810de, 0x026910de, 0x037210de,

0x037310de, 0x03e510de, 0x03e610de, 0x03ee10de, 0x03ef10de, 0x045010de, 0x045110de,

0x045210de, 0x045310de, 0x054c10de, 0x054d10de, 0x054e10de, 0x054f10de, 0x07dc10de,

0x07dd10de, 0x07de10de, 0x07df10de, 0x076010de, 0x076110de, 0x076210de, 0x076310de,

0x0ab010de, 0x0ab110de, 0x0ab210de, 0x0ab310de

.....latest alpha version - [0.61.5alpha_osx] has fixed the multicast bug....... :)

 

But be aware it may not be fully stable for all nForce MOBO setups......some only get stable operation when running with the cpus=1 flag set at boot up or in com.apple.Boot.plist.....

Link to comment
Share on other sites
 Mysticus C*
 Mysticus C*
Posted
Posted

it would be hard to tell wheter nvidia gfx cards on an nforce mobo will work instantly before you fix the nvidia gfx drivers....

 

like i explained earlier... before making anything work on nforce mobo, you need to fix the nvidia gfx drivers even if you have ATI card...

 

the reason for that is on nforce mobo, you have lots of nvidia branded components so dev/ven ids...

 

nvidia drivers as original do not have class/type check... (like wheter the device that the driver is loading for is network card? gfx card? audio? chipset?)... this is causing big trouble...

 

intel chipsets with intel gfx drivers do not have this because intel gfx drivers has class type check before device id check!

 

so if you are on an nforce mobo, you need to add class check for nvidia drivers before doing anything else...

 

once classification is done, u need to check wheter your device id is in the drivers? also you need to make sure that your device is supported as well, you can know this info from other topics, or nvinject website or whatever other source that discusses this issue...

Link to comment
Share on other sites
icedtrip
icedtrip
Posted
Posted
...

 

so if you are on an nforce mobo, you need to add class check for nvidia drivers before doing anything else...

 

once classification is done, u need to check wheter your device id is in the drivers? also you need to make sure that your device is supported as well, you can know this info from other topics, or nvinject website or whatever other source that discusses this issue...

 

Class check? I think this is the first time I have seen that. Who knows, maybe I just missed it somewhere. OK. Here is what I have.

 

System Profiler

nVidia GeForce 8800 GTS:

 

Chipset Model: nVidia GeForce 8800 GTS

Type: Display

Bus: PCIe

PCIe Lane Width: x16

VRAM (Total): 512 MB

Vendor: NVIDIA (0x10de)

Device ID: 0x0600

Revision ID: 0x00a2

ROM Revision: nVidia GeForce 8800 GTS OpenGL Engine [EFI]

Displays:

Display:

Resolution: 1680 x 1050

Depth: 32-bit Color

Core Image: Software

Main Display: Yes

Mirror: Off

Online: Yes

Quartz Extreme: Not Supported

 

 

I am using EFI Strings as they are the only way I have been able to get native resolution.

 

I have the following kext's. The bolded ones are the ones I have researched are the ones required for my card.

 

GeForce.kext

GeForce2MXGLDriver.bundle

GeForce3GLDriver.bundle

GeForce7xxxGLDriver.bundle

GeForce8xxxGLDriver.bundle

GeForceFXGLDriver.bundle

GeForceGA.plugin

GeForceVADriver.bundle

NVDANV10Hal.kext

NVDANV20Hal.kext

NVDANV30Hal.kext

NVDANV40Hal.kext

NVDANV50Hal.kext

NVDAResman.kext

 

So, in the bolded kext's above, I have

 

GeForce.kext

- IOClass = NVKernel

- IOPCIMatch = 0x060010de

NVDANV50Hal.kext

- IOClass = NVDANV50HAL

- IOPCIPrimaryMatch = 0x060010de

NVDAResman.kext

- IOClass = NVDA

- IOPCIPrimaryMatch = 0x060010de

 

Up to this point, all I have changed has been the IOPCIMatch and IOPCIPrimaryMatch to match my device/vendor ID. Am I suppose to do something with the IOClass?

Link to comment
Share on other sites
 Mysticus C*
 Mysticus C*
Posted
Posted
Class check? I think this is the first time I have seen that. Who knows, maybe I just missed it somewhere. OK. Here is what I have.

 

System Profiler

nVidia GeForce 8800 GTS:

 

Chipset Model: nVidia GeForce 8800 GTS

Type: Display

Bus: PCIe

PCIe Lane Width: x16

VRAM (Total): 512 MB

Vendor: NVIDIA (0x10de)

Device ID: 0x0600

Revision ID: 0x00a2

ROM Revision: nVidia GeForce 8800 GTS OpenGL Engine [EFI]

Displays:

Display:

Resolution: 1680 x 1050

Depth: 32-bit Color

Core Image: Software

Main Display: Yes

Mirror: Off

Online: Yes

Quartz Extreme: Not Supported

 

 

I am using EFI Strings as they are the only way I have been able to get native resolution.

 

I have the following kext's. The bolded ones are the ones I have researched are the ones required for my card.

 

GeForce.kext

GeForce2MXGLDriver.bundle

GeForce3GLDriver.bundle

GeForce7xxxGLDriver.bundle

GeForce8xxxGLDriver.bundle

GeForceFXGLDriver.bundle

GeForceGA.plugin

GeForceVADriver.bundle

NVDANV10Hal.kext

NVDANV20Hal.kext

NVDANV30Hal.kext

NVDANV40Hal.kext

NVDANV50Hal.kext

NVDAResman.kext

 

So, in the bolded kext's above, I have

 

GeForce.kext

- IOClass = NVKernel

- IOPCIMatch = 0x060010de

NVDANV50Hal.kext

- IOClass = NVDANV50HAL

- IOPCIPrimaryMatch = 0x060010de

NVDAResman.kext

- IOClass = NVDA

- IOPCIPrimaryMatch = 0x060010de

 

Up to this point, all I have changed has been the IOPCIMatch and IOPCIPrimaryMatch to match my device/vendor ID. Am I suppose to do something with the IOClass?

 

all the nvidia related kexts should have the following line before the pci primary patch as seen below

 

<key>IOPCIClassMatch</key>
<string>0x03000000&0xff000000</string>
<key>IOPCIPrimaryMatch</key>

 

iopciclassmatch will ensure that the driver is going to load for a VIDEO CARD...

 

cheers...

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
all the nvidia related kexts should have the following line before the pci primary patch as seen below

 

<key>IOPCIClassMatch</key>
<string>0x03000000&0xff000000</string>
<key>IOPCIPrimaryMatch</key>

 

iopciclassmatch will ensure that the driver is going to load for a VIDEO CARD...

 

cheers...

 

Thanks Mysticus C* for this very helpful clarification for readers of this thread as to what to put below IOPCIClassMatch in their NV*.kext(s)....... :)

 

You are the only one has emphasised the importance of device class/type identification and checking when install nVidia GFX card drivers, especially for nForce MOBOs with multiple nvidia chipset devices.....even though by now I have scanned loads of video drive install guides/threads....... ;)

Link to comment
Share on other sites
 Mysticus C*
 Mysticus C*
Posted
Posted
Thanks Mysticus C* for this very helpful clarification for readers of this thread as to what to put below IOPCIClassMatch in their NV*.kext(s)....... :D

 

You are the only one has emphasised the importance of device class/type identification and checking when install nVidia GFX card drivers, especially for nForce MOBOs with multiple nvidia chipset devices.....even though by now I have scanned loads of video drive install guides/threads....... :)

 

 

well, i used to have nforce mobo :) not many people were aware of the problem, i knew it from the beginning, but didnt know exactly what was causing the issue... those nvidia gfx drivers were causing KP although i had the ATI card... it was easy to fix the problem in my case as i deleted all nvd* and gef*s... but later someone in another topic figured it out... we accidently read it.... :) it was not been too popular i guess...

 

since than (since the first gfx update 1.0 came out) i always made nvidia gfx drivers fixed for nforce chipsets...

 

like i said intel chipset with intel onboard cards dont have the issue, but if u check intel drivers, u ll see they have class check :) thats is how the solution i think found... :)

 

it is the basis in windows as well in different way, but similar, taht is how windows catologs everything in device manager...

 

now what is interesting is that new macs will have nvidia chipset? :) lets see how it will work out :P

Link to comment
Share on other sites
 Mysticus C*
 Mysticus C*
Posted
Posted
.....emphasised the importance of device class/type identification and checking when install nVidia GFX card drivers, especially for nForce MOBOs with multiple nvidia chipset devices....

 

for clarification, the device type identification is not for installing nvidia gfx card! The reason is to prevent nvidia gfx drivers from loading for different/wrong components (eg, chipset, network, memory controller etc...) of an NFORCE mobo!

 

If you read my explanation in previous post, I said I had ATI gfx card but with nforce mobo, those nvidia gfx drivers loaded up, and caused kernel panic...with the class identication they never load for wrong component anymore

 

If you have nvidia gfx card on an nforce mobo, it is even more important to fix nvd* and gef* drivers...

 

I hope noone misunderstand what i said...

 

and correct problem solution is to add this code (missing 2 lines):

 

<key>IOPCIClassMatch</key>
<string>0x03000000&0xff000000</string>

 

before this code:

<key>IOPCIPrimaryMatch</key>

 

to NVD* GeF* .kexts (see list below)

 

=============

GeForce.kext

NVDAResman.kext

NVDANV50Hal.kext

NVDANV40Hal.kext

NVDANV30Hal.kext

NVDANV20Hal.kext

NVDANV10Hal.kext

=============

 

All of the drivers in the list above needs to be fixed for class type identification!!!

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
for clarification, the device type identification is not for installing nvidia gfx card! The reason is to prevent nvidia gfx drivers from loading for different/wrong components (eg, chipset, network, memory controller etc...) of an NFORCE mobo!

 

If you read my explanation in previous post, I said I had ATI gfx card but with nforce mobo, those nvidia gfx drivers loaded up, and caused kernel panic...with the class identication they never load for wrong component anymore

 

If you have nvidia gfx card on an nforce mobo, it is even more important to fix nvd* and gef* drivers...

 

I hope noone misunderstand what i said...

 

and correct problem solution is to add this code (missing 2 lines):

 

<key>IOPCIClassMatch</key>
<string>0x03000000&0xff000000</string>

 

before this code:

<key>IOPCIPrimaryMatch</key>

 

to NVD* GeF* .kexts (see list below)

 

=============

GeForce.kext

NVDAResman.kext

NVDANV50Hal.kext

NVDANV40Hal.kext

NVDANV30Hal.kext

NVDANV20Hal.kext

NVDANV10Hal.kext

=============

 

All of the drivers in the list above needs to be fixed for class type identification!!!

 

Hi Mysticus,

 

Thanks for that further helpful clarification........ :)

 

@ Thread Readers

 

Here are some threads to keep a watching eye on and to try the drivers on your OSx86 system........ :)

 

XDarwin's NVdarwin GFX card driver installer

 

eno's nForceLAN onboard LAN driver for nForce MOBOs

 

MercurySquad et al.'s Voodoo kernel

 

slashack's NForceATA Darwin ATA Drivers modifications to allow more than 2 gb of ram

Link to comment
Share on other sites
krypto
krypto
Posted
Posted

Am just wondering if all this will just work better once we get hold of Apples new MACBOOK which uses the new Nvidia CHIP.

Nvidia most often than not have a Unified driver for all thier chipsets, if thats the case then these new nvidia drivers in the new MACBOOK should work for existing nvidia chips,,,

 

I know its gonna be hard and a lot of work getting these but its a step forward now....

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
Verdant: I stop with my nforce topic :moil: From now on all nforce related subjects will be forwarded to your topic... ;) on your shoulders... good luck with :boxing: people :)

 

I don't remember volunteering to take over from you as the ;) point of call........ :stretcher:

 

Having pre-Series 7 NForce chipset MOBO posts in my Series 7 thread will make it "messy" so I will start another thread for pre-Series 7 NForce chipset MOBO posts......... :help: that you can point people to....

BUT posters that are rude/agressive :) or argumentative :laser:will not get replies......and neither will posters who are :offtopic: .........or who do not give enough of the clearly requested information..... :hammer: because I have my "real life" too......

I do not have loads of time to waste on :wallbash: or :moil: figuring out the problems for posters who are too lazy to do their own initial reading and research, especially on drivers for their non-standard and/or less-common MOBOs, components, peripheral devices e.g GFX cards, printers, scanners etc., which I have no experience of using myself......

 

If I get plagued by PMs or posts in my threads, in which posters demonstrate that they have not read all the useful posts in my threads, and in other relevant threads as well, and/or have not answered my necessary/relevant questions in earlier posts, and/or ignored sensible suggestions from myself and other experienced forum members etc. (Mysticus C*, you know exactly what I mean.... ;) ), then I will be justified in taking defensive action :angel: to protect my sanity, so that I do not :blowup: .......

 

I would be interested in a standalone combo installer for these:

 

XDarwin's NVdarwin GFX card driver installer

 

eno's nForceLAN onboard LAN driver for nForce MOBOs

 

MercurySquad et al.'s Voodoo kernel

 

slashack's NForceATA Darwin ATA Drivers modifications to allow more than 2 gb of ram

 

that will allow a post-OSx86 install on OSx86 10.5.2 and later........ ;)

Link to comment
Share on other sites
 Mysticus C*
 Mysticus C*
Posted
Posted

ok i ll deal with those installers... no worry... but i had given enough support to nforce owners :thumbsup_anim: put lotsa effort and information in the topic and some people refuses to read them and/or search them... also i dont have nforce mobo anymore so i cant really test much... therefore i cant help efficiently... plus i m fed up with dealing too many noobs (not newbies) who cant read a single line in first posts and jumping last pages, and no idea about what they are doing with their 2-3 days experiences....

Link to comment
Share on other sites
 Mysticus C*
 Mysticus C*
Posted
Posted

I have not finished it yet but it will look like this :)

 

NVdarwin is a mess from the link you sent me, there is no proper information regarding custom nvdarwin package installation... Luckily i know which drivers needs to be removed before the update takes place, and if you know what i mean, you will see the mess people make by installing nvdarwin without removing the nvkush-natit-titan-nvinject drivers... the installer provided has custom packages/drivers etc and it is quite a mess and expecting people to understand without single information :P i figured out all but the custom part which includes edid.command, and nvdarwin package alone (which i think for manually editing the memory and/or output nvcap values? but doesnt say anything about how edid will be used or how nvcap will be edited so i will keep the packages in the desktop most likely in case it is needed to be edited by people...

 

nforceyx8.png

 

i will finish it up tomorrow...

 

anything else u wanna add?

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
I have not finished it yet but it will look like this :)

 

NVdarwin is a mess from the link you sent me, there is no proper information regarding custom nvdarwin package installation... Luckily i know which drivers needs to be removed before the update takes place, and if you know what i mean, you will see the mess people make by installing nvdarwin without removing the nvkush-natit-titan-nvinject drivers... the installer provided has custom packages/drivers etc and it is quite a mess and expecting people to understand without single information :P i figured out all but the custom part which includes edid.command, and nvdarwin package alone (which i think for manually editing the memory and/or output nvcap values? but doesnt say anything about how edid will be used or how nvcap will be edited so i will keep the packages in the desktop most likely in case it is needed to be edited by people...

 

nforceyx8.png

 

i will finish it up tomorrow...

 

anything else u wanna add?

 

IT is looking good!......thanks........ :)

 

Only if you agree.....but I thought it might be useful to add your very latest USB fix as many people still seem to come unstuck with USB problems judging by LioNEXT's thread postings.....

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