963 replies to this topic

[verdant]

The  purpose of this thread, which will focus on attempts (successful,  partially successful, not successful yet.....with reasons why where  possible...... ) to install OSx86 10.5.x (Leopard) ONLY on NVIDIA nForce Series 5 and 6 MCP (570i, 590i, 610i, 630i, 650i  and 680i) chipsets + Intel CPU motherboard systems

is to

(i)     Complement the existing excellent Mysticus C* threads (A. and B. below)

A.    Nforce Chipsets: How to install Leo easy and fast with iAtkos v1.0i r3 - NForce Edition or Kalyway 10.5.2 DVD, Newbies Guide + Install Guide (Intel CPUs Only Guide) ....... now effectively static according to Mysticus C*.......he no longer runs a nForce chipset MOBO......

B. Mysticus C* Apple Delta/Combo Updates on nForce chipset + Intel CPU MOBOs - Currently updates to 10.5.6 - can be found here....

    
(ii)     Offer alternative support now that Mysticus C* is no longer supporting his nForce thread regularly, if at all.......

(iii)  To provide a focal point for the challenges associated with installing  OSx86 10.5.x....[and.....] on NVIDIA nForce Series 5 and 6 MCP (media and  communications processors) chipset-based Intel CPU MOBOs.

(iv)    To enable myself and other willing & helpful regular and guest contributers (volunteers  please.......?) to help many more owners of 570i, 590i, 630i, 650i and 680i chipset MOBOs than I and others can at present by answering  calls for help all over the place in isolated posts, PMs, and  threads......

A  number of forum posters have PM'd me wishing to make an unsolicited  entirely voluntary donation in appreciation for my freely given  assistance with their OSx86 problems......

Anyone wishing to donate (according to their personal circumstances and wishes) can now do so via PayPal......please remember to PM me your InsanelyMac Username AND Real Name so that I can link the two......and personally thank you....

A  donation is not required for my freely  given assistance....... donations are the gift of the giver NOT the  expectation of the receiver......

*************************************************************

POSTING REQUIREMENTS:

A. Full details of your system in your first post (and summary in your signature......following rules!)

1. Your MOBO brand and model: e.g. Asus P5N-32E SLI Plus 650i

2. Your nForce Series 5 or 6 chipset: i.e. 570i, 590i, 610i, 630i, 650i, or 680i

3. Your Intel CPU: Model, Core Quantity, Stock Speed and if Overclocked to what speed..... e.g. Intel Core 2 Quad CPU Q6600, 4 cores, 2.4GHz stock, 3.0GHz OCd

4. Screen shots of your current BIOS settings if at all possible (as very helpful and in some/many cases essential.....)

5. Your DVDRW(s): TYPE - SATA or PATA [IDE], QUANTITY

6. Your hard drive(s): TYPE - SATA or PATA [IDE], QUANTITY - and if set as RAID or not, SIZE (i.e. capacity in GB)......

7. Hard drive PARTITION/FORMATTING: - and if set up as single OS volume per HDD or multi-OS volume per HDD etc......

8. Current OS's installed: Full details i.e. not just Windows or Linux.... and whether or not you hope to dual boot or even triple boot....

9. Your graphics card(s): Brand, Model No., RAM, - if in SLI mode or not

10. PCI/PCI-E cards fitted:  e.g. USB, Firewire,NIC etc. and quantity of each...

11.  Onboard devices/functions: Audio chipset, LAN chipset, Firewire (number  of ports), USB 1.1 or 2.0 (number of ports), eSATA (number of ports),  etc.


B. Full details of your current OSx86 install status

1. Your available OSx86 Install DVD(s) - Name, Leopard version, Release version: e.g. iDeneb 10.5.4 v1.1
  
  2. Clear description of the problems you encountered when trying to  install....with boot screen images showing error messages  observed.......if at all possible (as very helpful and in some cases essential.....)

*************************************************************

BIOS SETTINGS TEMPLATE FOR 570i, 590i, 610i, 630i, 650i and 680i Ultra NVIDIA nForce Series 7 MCP chipset based Intel CPU MOBOs

This BIOS template (now V2 with some additions for 630i) does not claim to cover all the BIOS variations for all the different MOBOs that meet the above requirement........also apologies for any errors........It is a composite list so under 650i for example it has the settings for  different 650i MOBOs in the same column.......likewise for the other chipsets......it is not complete in terms of the number of different BIOS parameter layouts for the same chipset.......particularly for the 570i and 610i chipset MOBOs......

BUT readers should be able to see which ones of the  listed parameters match their particular BIOS parameters......

I did it this way because I am not able (due to time constraints and not having every MOBO manual etc.) to list all the relevant BIOS settings for each of the Pre-Series 7 nForce chipsets for all of the nForce chipset MOBO manufacturers!.....I hope you understand......

It is a preliminary guide to the most likely forms of the relevant BIOS parameters, their default settings, together with my recommended initial settings to enable OSx86 installation and stable operation (within the known limitations of nForce chipset MOBOs...... ).

The BIOS settings in italics are ones that you could change later if you so wish (assuming you have the appropriate kernel to install) to see if the system still runs OSx86 without any problems......

In the BIOS template I have got IEEE1394 Controller (i.e. Firewire) set as [Auto] or [Enabled], generally the default BIOS setting........BUT if when having it set as [Auto] or [Enabled] you cannot install OSx86 from DVD because your PC freezes during booting from the DVD, then set IEEE1394 Controller as [Disabled] and try rebooting from the DVD.......

If it makes no difference, the origin of the freeze lies elsewhere......if, however, you can now boot successfully from the DVD into the OS X Installer window, then after successfully installing and running OSx86 from the HDD, you can set it back to [Auto] or [Enabled]......if everything continues to work OK that is......

 Pre_Series7_nForce_Chipset_BIOS_SettingsV2.gif   175.29K   2272 downloads
 Pre_Series7_nForce_Chipset_BIOS_SettingsV2.pdf   63.52K   2733 downloads

*************************************************************

HELP FOR THOSE EXPERIENCING ACPI-APIC and/or BIOS PROBLEMS (e.g. always needing to use the cpus=1 boot flag)

If your System Hangs after Boot Screen Message:

"Mac framework successfully initialized
Using XXXX buffer headers and 4096 cluster IO buffer headers"

where XXXX may be 16384, 14805, 10485, 5242 typically......

XXXX Number Explanation:

16384 is reported to indicate ≥ 4GB RAM
14805 is reported to indicate 2GB RAM

The Error Cause may be:

ACPIPlatform.kext and/or AppleAPIC.kext  and/or IOACPIFamily.kext

The Error Solution may be:

Replace ACPIPlatform.kext and/or AppleAPIC.kext and/or IOACPIFamily.kext with compatible version(s); generally found in older distros...…or as an "ACPI Fix"  or "ACPI-APIC Old" or similar  in recent distros.....

HOWEVER, if different versions of these kexts do not resolve the error, then you may need a modified-DSDT BIOS……this is because the DSDT is a part of the ACPI subsystem.  

ACPI is the acronym for Advanced Configuration & Power Interface. The ACPI interface has been around since 1999 and used on the majority of i386 and x86_64 systems since then.

ACPI is an abstraction level that is interfaced between the OS and the platform firmware and hardware. This abstraction layer's, i.e. ACPI's purpose is to hide differences in the platform firmware and/or hardware from most of the operating system kernel codebase, in order that most of the kernel codebase does not have to be changed for the OS to run on systems with different hardware and/or firmware. Thus, OS and the platform can evolve independently so that a new OS should be able to run on old hardware, while an older OS should be able to run on new hardware.DSDT is an acronym for Differentiated System Description Table.  The DSDT contains the Differentiated Definition Block, which supplies the information and configuration information about the base system. It is always incorporated in the ACPI Namespace by the OS at bootup. However, it is sad fact that a number of MOBO manufacturers do not seem able to provide fully functional DSDTs as part of their MOBOs' BIOS.

For example, MSI MOBOs often need a DSDT string-modded BIOS.....read this thread.....and see here......Kabyl may be able to help you.....BUT also see OriginalMACNUT's OSXCORES......e.g. MSI P7N nForce 750i SLI Platinum......also see fassl's DSDT Patcher.......using mackerintel's Chameleon with DSDT Override bootloader......as well as koalala's ACPI (DSDT) Patcher for BIOS and AML, CPU Cores, HPET, RTC, TM, GFX......

*************************************************************

IF YOU ARE USING PATA (IDE) DEVICES e.g. IDE HDD(s) and IDE DVDRW or DVDROM (and/or CDROM/CDRW) THEN PLEASE READ:

CORRECT IDE (PATA) DEVICE JUMPER SETTING AND CABLE CONNECTING

1.  The modern 40-pin Ultra DMA 80-wire cable can be made  connector-specific by jumpering CS (Cable Select) on HDD and jumpering  CSEL (Cable Select) on the DVDROM, because the cable connectors are  usually color-coded as follows:

Blue connector to the host i.e. MOBO,
Black  connector to the chosen primary device, i.e. device cable-selected as  Master (usually i.e.should be the END connector of the cable)
Grey connector to the chosen secondary device, i.e. device cable-selected as Slave (usually i.e. should the MIDDLE connector of the cable)

BUT not always.........

With such a cable, if  you jumper the DVDROM as Master and the HDD as Slave, or vice versa,  then the Slave device is usually connected to the middle connector and  the Master device to the end connector (with the Blue connector as always connected to the MOBO IDE connector)

2.  If you have the older 40-pin 40-wire Cable Select cable, then the  Master Connector is the MIDDLE connector of the cable, and the Slave  connector is the END connector of the cable(with the Blue connector as always connected to the MOBO IDE connector).

3. If you have the older 40-pin 40-wire Regular (non-Cable Select) then the function of the MIDDLE and END connectors on the cable 40-pin 40-wire (with the Blue  connector as always connected to the MOBO IDE connector) are determined  by the jumper settings on the devices connected to each (i.e. Master or  Slave). With such a cable, if you set both devices as Cable Select,  each will configure itself as Master, causing a signal conflict.

4.  If you have the very rare situation of one device having to be jumpered  on Cable Select and the other jumpered as Master or as Slave (i.e. no  CS or CSEL option), then Cable Select mode is invoked, configuring the  MIDDLE connector of the cable as Master on older 40-pin 40-wire Cable Select cable, and on modern 40-pin Ultra DMA 80-wire cable, configuring the END connector of the cable as Master (with in either case, the Blue connector connected to the MOBO IDE connector).

Confusing or what.........  ide8040pin.jpg   15.75K   218 downloads

If  your MOBO has two separate IDE channels, i.e. two IDE connectos on the  MOBO.......typically the blue MOBO connector is IDE Channel 0 and the  black MOBO connector is IDE Channel 1.......then I recommend that you  get two 80 wire IDE cables and try connecting your IDE DVDROM to the  blue MOBO connector as Master and your IDE HDD to the black MOBO  connector as Master if other IDE arrangements do not work........

*************************************************************

Partitioning and Formatting a Hard Drive (HDD) for OS X

OS X Disk Utility does not recognize unallocated space on a hard drive, and so the space cannot be used to create a new partition.

You can only either reformat a pre-existing partitioned volume, or re-partition the entire hard drive space.....

When setting up partitions on a hard drive using Windows, just create primary partitions formatted as either simple FAT32 or NTFS volumes depending on your version of Windows......FAT32 and NTFS volumes are recognised by OS  X.....so you can then use Disk Utility to either re-partition and/or re-format the volumes using the partition/formatting schemes you want for OS X.......e.g. MBR/HFS+ or GPT/HFS+.......

Should you be in the ideal position of being able to and wanting to install OS X on its own hard drive, I  recommend for general PC use (i.e. rather than as a server) that you partition the hard drive as Master Boot Record (MBR) via the Partition menu tab in OS X Disk Utility and format it as Mac OS Extended (Journaled) volumes, into a minimum of 4 volumes (depending on your HDD capacity) as follows:

1st volume at the start of HDD is a small 10GB volume (choose a name without spaces e.g. Leopard_Boot or OS_X_Boot etc) to use as a OS X boot volume with ONLY a basic fully working OS X install from your chosen OS X Install DVD (which enables you to use its Disk Utility functions on the other OS X volumes), together with:

Kext Helper b7
OSx86Tools
PC EFI v9 Chameleon Bootloader Installer
Chameleon 2.0RC1 Bootloader Installer

and any other Utiliy software you find very useful for OS X system installation/maintenace/repair etc., to enable you to modify/test OS X updates on the Main and Backup OS X volumes without ever risking not being able to boot into OS X on this HDD.......

The 2nd and 3rd volumes are equal size volumes, which for use as the OS X Main and Backup (or Test) systems, respectively.......suggest you use a size of  at least 40GB for each.....

The 4th volume is a OS X Data Archive volume with all your archived OS X and OS x86 software, documents files, image files, music files, or whatever you wish to archive and keep safe......

*************************************************************

Mysticus C* device class/type identification IOPCIClassMatch modification when installing nVidia GFX card drivers, especially for nForce MOBOs with multiple nVidia chipset devices....    

Note the device type identification is not for installing the nVidia GFX card driver kexts themselves!
  
  The  problem arises because nVidia graphics kexts do not have an internal  check process to see whether they are loading for an nVidia graphics  card or not, which means that they can/may load for any nVidia/nForce  chipset device in the MOBO/system with a IOPCIClassMatch listing nVidia  as vendor....
  
The  purpose of the modification is to prevent the nVidia GFX driver kexts  from loading as drivers for the wrong i.e. different MOBO components  (eg, chipset, network, memory controller etc...) on an nForce  MOBO......!

Without  the device class/type identification present in the NVD* and GeF*  kexts, nVidia GFX card drivers load up on a NForce MOBO even when a ATI  GFX card is installed, causing kernel panics..... If you have nVidia  GFX card on an nForce chipset MOBO, it is even more important to fix  the NVD* and GeF* drivers......
  
  Furthermore,  Mysticus C* and myself, working together, recently isolated the origin  of the frequent freezing during OS X system updates employing Apple  MacOSXUpdCombo10.5.x.pkg Installers on nForce chipset MOBOs and/or  MOBOs with nVidia graphics card(s) fitted....see the section "FOR  SERIOUS STUDENTS OF OS X on a x86 PC SYSTEM" in my write-up here......
  

The solution is to add these 2 lines of code (if found to be missing)

CODE

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

before this code:

CODE

<key>IOPCIPrimaryMatch</key>

in the NVD*.kexts and

before this code

CODE

<key>IOPCIMatch</key>

in the GeForce.kext (see list below)  

=============
GeForce.kext
NVDAResman.kext
NVDANV50Hal.kext
NVDANV40Hal.kext
NVDANV30Hal.kext
NVDANV20Hal.kext
NVDANV10Hal.kext
=============

in the Info.plist file of each of the above kexts.

To get to Info.plist file in each kext:

1. Navigate to /System/Library/Extensions
2.  Find each kext one at a time, then right-click on kext icon, choosing  "Show Package Contents", then open Contents folder to find Info.plist.
3.  Open Info.plist file via Terminal using sudo nano etc., or right-click,  choosing "Open With", and selecting your preferred Text Editor app;  e.g.Text Edit, TextMate, TextWrangler, Property List Editor, or  PlistEdit Pro etc.
4. Make changes to Info.plist and save modified file.

All of the NVDANVxxHal.kexts  in the list above are recommended to be fixed for class type  identification, in case more than one NVDANVxxHal.kext is loaded and  registered.....

*************************************************************

Mysticus C* nForce chipset MOBO "friendly"
Combo Updates / ISOs......

UPDATE May 2009 :

Mysticus C* has shown his willingness to develop nForce chipset MOBO "friendly" OS X Installer Packages and EVEN MORE.... WHEN SUPPORTED (Remember he is not in the Forbes 500 Rich List AND neither am I ).....and wishes to continue doing so....as the Snow Leopard approaches....

You can make a PayPal USD donation (according to your personal circumstances and wishes) to Mysticus C* to support his continued work on nForce chipset "friendly" software...

BUT NOW you can also donate a nForce chipset laptop/desktop should you wish to......

===================================================================
Hardware 3 = TEST PC Components  (For nForce Mobo Owners)
===================================================================
Various (cheap/expensive depending on the demand and Donation collected) nForce Mobos+Intel Cpu to test Combo Updates / ISOs for future use... This is highly needed as I dont have huge bandwidth and do not have many knowdledged users around either. If i have test hardwares (well i only need specific nForce mobos deemed problematic + a cheap intel c2d cpu) it will be easier to release updates/isos for nforce mobo owners. If you would like to donate your laptop/desktop for this cause your welcome to do so as well.
Price: ₤ Variable
Current Poll: ₤ 0

Login to become a donator member.....


UPDATE March 2009 :

Mysticus C* Apple Delta/Combo Updates on nForce chipset + Intel CPU MOBOs - Currently updates to 10.5.6 - can be found here....


ARCHIVE Mysticus C* SOFTWARE :

10.5.5 Updater Packages:

The Mysticus C* nForce Drivers Installer v1.2 and 10.5.5 Combo Update Patches v1.2.0 are BOTH now available here.....   

At my request Mysticus C* has produced a standalone installer, primarily for nForce chipset + Intel CPU MOBO owners (although other users may benefit from it too....see installer options ) for the following advances of particular benefit to nForce chipset MOBOs: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 (enables more than 2GB or 3GB of RAM to be used)

incorporating Mysticus C*'s USB mount and controller fixes too

that will allow a post-OSx86 install on OSx86 10.5.2 and later........ALTHOUGH the installer is optimised for 10.5.5.....

In his current version nForce Drivers Installer (v1.2), Mysticus C* has updated the current 0.62.3n beta version of eno's nForceLAN kext with the 0372-3 device IDs and provided it in two variants......one with the OptimizationMode set to 0 (for throughput-load optimization) andthe other set to 1 (for CPU-load optimization).......  

I have successfully run version 1.0 of Mysticus C*'s nForce Drivers installer on

(i) Kalyway 10.5.2 OSx86 Test System ( on an external USB2.0 [2 x 250GB SATA HDD] RAID enclosure running in BIG mode),
(ii) iDeneb v1.1 10.5.4 system, and
(iii) JaS 10.5.4 updated to 10.5.5 using Mysticus C*'s 10.5.5 Combo Updater Packages.Both (ii) and (iii) are OSx86 Test Systems on an external eSATA [750GB SATA HDD] enclosure.

The installer runs successfully on my Asus P5N32-E SLI Plus (650i nForce chipset) MOBO with Intel Core2 Quad Q6600 G0 Version CPU OC'd to 3.0GHz, Gigabyte NVidia GeForce 8600GT GFX card, 6GB 667MHza DDR2 RAM, 3xSATA HDDs, PATA DVDRW, 2 x onboard nForce MCP55/Marvell 88E1116 LAN controller/chipset, and Netgear GA311 RTL8169 chipset NIC.....

The installer options in version v1.2 are:
  

 nForce_Drivers_V1.2.gif   33.21K   1344 downloads

BUT this does not mean that all of the installable kexts & kernel will run without error on your PC OSx86 system........

*************************************************************

KERNEL & KEXT & SYSTEM UPDATES

1.    slashack's AppleNForceATA.kext for nForce MOBOs

There is continuing good progress using the slashack AppleNForceATA kext to access RAM ≥ 3GB......

The AppleNForceATA.kext v0.1 is working very well for most users; although some may have issues with DVD drives and others may have issues with the Voodoo kernel........see slashack's thread.....


2.    eno's nForceLAN.kext for nForce MOBOs

There is continuing good progress using the eno nForceLAN kext......

eno's latest nForceLAN onboard LAN driver ([0.62.13n] Code/dependency cleanup. Moved link timer to separate event source (testing). Invalid MAC is replaced by a pseudo-random number instead of a random one (should fix any iTunes issues).) allows HPET to remain enabled in BIOS since disabling HPET in BIOS may be an issue for users who dual boot Vista and OS X as HPET is recommended for Vista multimedia applications......see here.


3. Slice's USB2.0 kexts for Leopard (with Sleep support)

There is continuing good news regarding Slice's USB2.0 kexts.......

There is a new compilation by Slice from 10.5.7 sources, with a version change to 3.4.4 This version includes all previous fixes, new DeviceIDs and forced sleep capabilities even if it is not really supported (as discussed with Hafnium). All files tested in 10.5.5 so it compatible with old systems (Leopard only!). Download the kexts from his thread here.....

Download attachments to desktop
Double click to unzip
Enter Terminal
sudo -s
mkdir ~/Desktop/Off
cp -r -v ~/Desktop/*USB*.kext /S*/L*/E*/IOUSB*/C*/P*/
chown -R root:wheel /S*/L*/E*/IOUSB*/C*/P*/
rm -v /S*/L*/E*.mke*
diskutil repairpermissions /
reboot


4.    Vanilla kernels and Voodoo kernels

My 650i MOBO does not like the 9.5.1 vanilla kernel.......while it does not always hang during the booting process......it comes up with messages like ".......disk not supported." and on one occasion when it reached the Desktop, moving the mouse away from the Hardware Monitor File tab just generated the Apple "spinning rainbow wheel".....but I did have the eno nForceLAN kext installed.... However, I did not have the eno nForceLAN kext installed the last time I installed the 9.5.1 vanilla kernel.....but on booting my system bootup screen froze after the following last four error lines appeared:

ERROR: Firewire unable to determine......     AppleNForceATA: found 0 units.     AppleNForceATA::free( 0x98a9600)

I waited for over 10 minutes but no further boot progress beyond this point......

The first error line was repeated 10's of time before last appearance and disk3s5 is the HDD volume I was booting from: disk3s5: loctl (_IOW,'d',31,32) is unsupported.

9.5.1 vanilla is reported to also cause the loctl error on an Asus Striker II Extreme (790i chipset)...and reported not to work on a XFX 780i MOBO either.....

Same is likely to be true with the Vanilla 9.6.0 kernel......confirmed as I was able to boot Vanilla 9.6.0 only once without a KP at least for a few minutes........

USE VOODOO 9.5.0 RELEASE VERSION v1.0 kernel........Voodoo 9.6.0 under development.......see here........


5. Leopard OS X 10.5.6

Successful clean system installation and subsequent operation of Leopard 10.5.6 on External eSATA HDD OS X volume partitioned as MBR connected to my  system ......see my Sunday 28th December blog entry in my blog.....Asus P5N32-E SLI Plus (nForce 650i) + Q6600 running full CI/QE, USB 2.0, audio, networking (RTL8169 NIC), eSATA, and Firewire 400 (IEEE1394a) operation...... with subsequent manual installation of slashack's AppleNForceATA.kext for 6GB RAM operation.....  

This success bodes well for  Mysticus C* next surprise for nForce chipset + Intel CPU MOBOS.....

*************************************************************

Kernel and/or Kext Testing [left]

On my JaS 10.5.5 test system, I have run HighLoad v1.9.8 memtest on 5020MB to test out the 6GB RAM as regards causing kernel panics with Voodoo Beta 2C kernel and slashack's nForceATA.kext.......all tests passed without any kernel panics!..... for Voodoo Beta 2C kernel and slashack's nForceATA kext.

 6GB_Slashack_NForceATA_MEMTEST.png   60.5K   218 downloads

Voodoo Beta 2C now successfully replaced by Voodoo Release Version 1.0 Rev_A

LATEST TESTING NEWS

A. VoodooHDA.kext version 0.2.2 released.....see here......

Mute is now working.........autoswitching between speakers (unknown) on rear port and headphones on front port is still not working....

 Sound_Output_VoodooHDA_v2.2.tiff   47.49K   97 downloads  Sound_Input_VoodooHDAv2.2.tiff   47.75K   42 downloads  Audio_MIDI_Setup_VoodooHDAv2.2.tiff   60.63K   31 downloads

B. Experimental Source for VoodooHDA released.........see here and here.......

If you are unwilling to learn by doing.......jump  to Step 5. to find my already compiled VoodooHDA.kext.......otherwise, continue learning by reading and doing.......

1. Download and install Xcode 3.1.2 if not already installed and download the VoodooHDA read-only source using Terminal:

CODE

sudo svn checkout http://voodoohda.googlecode.com/svn/trunk/ voodoohda-read-only

which will generate a file list:

A    voodoohda-read-only/PCMBlitterLib.h
A    voodoohda-read-only/VoodooHDADevice.cpp
A    voodoohda-read-only/PCMBlitterLibX86.cpp
A    voodoohda-read-only/Info.plist
A    voodoohda-read-only/getdump.c
A    voodoohda-read-only/VoodooHDADevice.h
A    voodoohda-read-only/helper.sh
A    voodoohda-read-only/VoodooHDAEngine.cpp
A    voodoohda-read-only/AudioClip.cpp
A    voodoohda-read-only/Tables.c
A    voodoohda-read-only/Shared.h
A    voodoohda-read-only/Registers.h
A    voodoohda-read-only/VoodooHDAEngine.h
A    voodoohda-read-only/OssCompat.h
A    voodoohda-read-only/Tables.h
A    voodoohda-read-only/Private.h
A    voodoohda-read-only/VoodooHDAUserClient.cpp
A    voodoohda-read-only/PCMBlitterLibDispatch.h
A    voodoohda-read-only/VoodooHDAUserClient.h
A    voodoohda-read-only/Verbs.h
A    voodoohda-read-only/License.h
A    voodoohda-read-only/Models.h
A    voodoohda-read-only/Readme.txt
A    voodoohda-read-only/PCMBlitterLib.cpp
A    voodoohda-read-only/Parser.cpp
A    voodoohda-read-only/English.lproj
A    voodoohda-read-only/English.lproj/InfoPlist.strings
A    voodoohda-read-only/Common.h
A    voodoohda-read-only/VoodooHDA.xcodeproj
A    voodoohda-read-only/VoodooHDA.xcodeproj/user.pbxuser
A    voodoohda-read-only/VoodooHDA.xcodeproj/project.pbxproj
A    voodoohda-read-only/VoodooHDA.xcodeproj/TemplateIcon.tiff
A    voodoohda-read-only/VoodooHDA.xcodeproj/user.mode1v3
Checked out revision 2.

and the "voodoohda-read-only" folder in /Users/"Logged-In User"/.....

2. In Terminal type

CODE

cd /Users/"Logged-In User"/voodoohda-read-only
          sudo su

3. At sh-3.2# prompt, type

CODE

./helper.sh build

In the "voodoohda-read-only" folder, there will now be a "build" folder containing a "Debug" and "VoodooHDA.build" folder.......inside the "Debug" folder is the compiled VoodooHDA.kext.....

4. In Terminal, rename AppleHDA......

CODE

cd /System/Library/Extensions/
          sudo mv AppleHDA.kext AppleHDA.kext.back
          exit

5. Use Kext Helper b7 to install the now compiled VoodooHDA.kext OR my already compiled VoodooHDA.kext....

6. Reboot with -v -f......You should hopefully hear an audio "crackle" during booting......

What I find on my Asus P5N32-E SLI Plus MOBO with Asus SupremeFX Audio Card (with AD1988b audio codec) is as follows:

 SysProfilerVoodooHDA.tiff   8.3K   76 downloads
 Sound_Output_1.tiff   55.79K   57 downloads
 Sound_Output_2.tiff   56.54K   18 downloads
 Sound_Output_3.tiff   57.8K   13 downloads
 Sound_Output_4.tiff   55.76K   11 downloads
 Sound_Output_5.tiff   55.58K   13 downloads
 Sound_Input_1.tiff   59.85K   15 downloads
 Sound_Input_2.tiff   60.41K   10 downloads
 Audio_MIDI_Setup.tiff   63.19K   18 downloads

Rear sound-out ports working on Analog PCM #0: and Front sound-out ports working on Analog PCM #1:.......volume adjusted via Master or PCM.......autoswitching between ports is not working....

Sound Input ports and Digital PCM #2: have not been tested.......


C. Now available THe KiNG's fix for the AD1998b audio codec on my Asus P5N32-E SLI Plus MOBO with Asus SupremeFX Audio Card....it now enables Line in and Mute....unlike the Taruga_AD1988b_Rev3 / Rev4 installer......

 IntelHDA.png   36.59K   72 downloads  Sound_Output.png   44.02K   59 downloads  Sound_Input.png   43.43K   49 downloads

His Leopard HDAEnabler.kext and the AD1988b.HDA.FIX.kext, plus the necessary original 10.5.6 AppleHDA.kext can be got here......install all three kexts simultaneously using Kext Helper b7.......

[nz_mitch]

EDIT: RESOLVED - THANKS VERDANT! Check below for a link to instructions.

Here we go!

Moved this from a seperate thread - cheers Verdant.

1. XFX nForce 680i LT
2. 680i
3. Intel Core 2 Duo E8200 2.4 GHz stock OC'd to 3.0 GHz
4. Let me know what you want / need!
5. DVDRW Pioneer SATA currently installed, have an IDE if neccessary
6-7. 1x 320 GB SATA Seagate HDD, 4 partitions (Windows, Data, Apps, potentially MacOSX86), 1x 300GB Seagate IDE, 2 partitions (Data, potentially MacOSX86) [I've tried installing to both which is why there's two mac partitions - ultimately only want one!)
8. Windows Server 2008, hope to dual boot into MacOS - probably using BCD.
9. 2x XFX 9600 GT 512 MB DDR3 Super Clocked (I understand I won't be able to run these in SLi?)
10. 1x Firewire (400?), about 8 USD 2.0 ports (it's a Silverstone SST-TJ04 case). On board sound I think, but I've always used a USB headset.

EDIT: RESOLVED - CHECK HERE FOR A RUNDOWN ON INSTALLING WITH THIS HARDWARE.

Currently I've just got iDeneb 10.5.5 v 1.3 (I need 10.5.5 for the 9600GT). I'm happy to try other releases if need be.

When I try and install with -v I get as attached: ultimately the "cannot find root device" error.

I have tried using an IDE DVD drive which leads to the same problem. Next I tried removing the SATA DVD and HDD and using only an IDE DVD and HDD and I was, after a bit of tinkering in disk manager, to get OSX to install however when I came back (after the install, I guess it had rebooted) it was on the grey screen with the cross-symbol on it. I rebooted with -v and ultimately ended up with "cannot find root device" again.

If you need any more information please let me know - otherwise any help would be much appreciated!

Cheers

Attached Files

•  compressed.jpg   367.84K   253 downloads

[verdant]

nz_mitch, on Oct 23 2008, 10:30 AM, said:

Here we go!

Moved this from a seperate thread - cheers Verdant.

1. XFX nForce 680i LT
2. 680i
3. Intel Core 2 Duo E8200 2.4 GHz stock OC'd to 3.0 GHz
4. Let me know what you want / need!
5. DVDRW Pioneer SATA currently installed, have an IDE if neccessary
6-7. 1x 320 GB SATA Seagate HDD, 4 partitions (Windows, Data, Apps, potentially MacOSX86), 1x 300GB Seagate IDE, 2 partitions (Data, potentially MacOSX86) [I've tried installing to both which is why there's two mac partitions - ultimately only want one!)
8. Windows Server 2008, hope to dual boot into MacOS - probably using BCD.
9. 2x XFX 9600 GT 512 MB DDR3 Super Clocked (I understand I won't be able to run these in SLi?)
10. 1x Firewire (400?), about 8 USD 2.0 ports (it's a Silverstone SST-TJ04 case). On board sound I think, but I've always used a USB headset.

Currently I've just got iDeneb 10.5.5 v 1.3 (I need 10.5.5 for the 9600GT). I'm happy to try other releases if need be.

When I try and install with -v I get as attached: ultimately the "cannot find root device" error.

I have tried using an IDE DVD drive which leads to the same problem. Next I tried removing the SATA DVD and HDD and using only an IDE DVD and HDD and I was, after a bit of tinkering in disk manager, to get OSX to install however when I came back (after the install, I guess it had rebooted) it was on the grey screen with the cross-symbol on it. I rebooted with -v and ultimately ended up with "cannot find root device" again.

If you need any more information please let me know - otherwise any help would be much appreciated!

Cheers

Hi there,

1) To run OS X on x86 installed via current kernels / DVD installers, you cannot have two nVidia GFX cards installed......you need to physically remove one of the cards.....

I am happy to be proven wrong on this......but if you check out the GFX card options for Apple Mac Pro, you can install up to 4 x ATI Radeon HD 2600 XT 256MB GFX cards but only 1 x NVIDIA GeForce 8800 GT 512MB, or 1 x NVIDIA Quadro FX 5600 1.5GB GFX card.....

2) Is your BIOS is updated to version P08?

3) Check your BIOS settings against the Bios template in my Series 7 topic post #1......I have not had time to do a similar template for pre-Series 7 MOBOs yet......but I suspect the BIOS parameters and their options will match up sufficiently with those in the template to serve a useful double-check.....

This will be our starting point.......

[SilverSix311]

Working:
Kalyway 10.5.2
Sata seems to gimme alot of freezing for some reason.. If anyone knows the answer lemme know.

Current Project:
I am trying to either Update from 10.5.2 Kalyway to 10.5.5 Combo Update. Doesnt seem to like me as last two times my compy froze for some reason... OR i am goin to try and install iDeneb 10.5.5 with Nforce Patch as soon as the ISO finishes D/Ling

Specs:
MoBo: EVGA nForce 680i SE SLI
CPU: Intel Core 2 Quad 2.4ghz
DVD: Samsung DVD Burner PATA
HDD: 180gig Maxtor PATA, 250gig WD SATA, 500gig Maxtor SATA
GFX: XFX GeForce 8800 GTS Extreme 640MB
Ethernet: Apple USB to Ethernet Adapter
RAM: OCZ Nvidia SLI 2gig DUAL Channel RAM 800mhz

I think that pretty Much sums everything up.

Will the voodoo kernels RUN a 680i Motherboard or do you have to use the Nforce kernel only? I havent ever tried anything other than the Nforce and ive only used Kalyway 10.5.2....

Hit me up on AIM: SilverSix311

[verdant]

SilverSix311, on Oct 24 2008, 08:06 AM, said:

Working:
Kalyway 10.5.2
Sata seems to gimme alot of freezing for some reason.. If anyone knows the answer lemme know.

Current Project:
I am trying to either Update from 10.5.2 Kalyway to 10.5.5 Combo Update. Doesnt seem to like me as last two times my compy froze for some reason... OR i am goin to try and install iDeneb 10.5.5 with Nforce Patch as soon as the ISO finishes D/Ling

Specs:
MoBo: EVGA nForce 680i SE SLI
CPU: Intel Core 2 Quad 2.4ghz
DVD: Samsung DVD Burner PATA
HDD: 180gig Maxtor PATA, 250gig WD SATA, 500gig Maxtor SATA
GFX: XFX GeForce 8800 GTS Extreme 640MB
Ethernet: Apple USB to Ethernet Adapter
RAM: OCZ Nvidia SLI 2gig DUAL Channel RAM 800mhz

I think that pretty Much sums everything up.

Will the voodoo kernels RUN a 680i Motherboard or do you have to use the Nforce kernel only? I havent ever tried anything other than the Nforce and ive only used Kalyway 10.5.2....

Hit me up on AIM: SilverSix311

Hi there,

The Voodoo Beta 2C kernel and slashack's nForceATA kext both are working very well on my 650i MOBO.......

Are you running Kalyway 10.5.2 currently? Please let me know so that I can guide on what to do next.....

[nz_mitch]

Hi verdant,

Thanks for your suggestions - I've tried everything as described but I still get "still waiting for root device" when I run the installation with -v (that's with just a SATA HDD and SATA DVDRW connected).

So the bios is definitely P08 and I've mirrored the bios functions wherever possible as described - it seems that the problem is with the nForce SATA drivers not picking up the HDD.. is that about right?

Not sure where to go from here..

[verdant]

nz_mitch, on Oct 24 2008, 11:40 PM, said:

Hi verdant,

Thanks for your suggestions - I've tried everything as described but I still get "still waiting for root device" when I run the installation with -v (that's with just a SATA HDD and SATA DVDRW connected).

So the bios is definitely P08 and I've mirrored the bios functions wherever possible as described - it seems that the problem is with the nForce SATA drivers not picking up the HDD.. is that about right?

Not sure where to go from here..

I will PM you.......With the Mysticus C* 10.5.5 Combo Updater packages, you will be able to update any install to 10.5.5 from 10.5.0 upwards........

[nz_mitch]

Hi verdant.

Thanks for the PM! While I was AFK I tried installing again using cpus=1 and with the IDE DVD instead of the SATA DVD and the install went without a hitch!

When I came to reboot however it crashes.

I get to the bootloader (and can select to boot into Windows or add different boot switches such as -x, -v etc) but after about 5 seconds of booting or a bit longer in verbose mode when (at least from what I can see from the split second before it crashes and reboots) it falls over right when it starts to actually boot MacOS X.

I've disabled the onboard NIC and have removed one of the 9600GTs (currently there's one in the top PCI-e slot, closest to the CPU) so not sure what could be causing it.

During the iDeneb installation I checked the following options:

1. Vanilla kernel
2. NVInject 512MB
3. cpu=1 fix

I think those were the only things I changed - I'm guessing I could try without the cpu=1 fix but if there's any other changes to the iDeneb installation you'd recommend let me know.

Thanks again!

[verdant]

nz_mitch, on Oct 25 2008, 01:29 AM, said:

Hi verdant.

Thanks for the PM! While I was AFK I tried installing again using cpus=1 and with the IDE DVD instead of the SATA DVD and the install went without a hitch!

When I came to reboot however it crashes.

I get to the bootloader (and can select to boot into Windows or add different boot switches such as -x, -v etc) but after about 5 seconds of booting or a bit longer in verbose mode when (at least from what I can see from the split second before it crashes and reboots) it falls over right when it starts to actually boot MacOS X.

I've disabled the onboard NIC and have removed one of the 9600GTs (currently there's one in the top PCI-e slot, closest to the CPU) so not sure what could be causing it.

During the iDeneb installation I checked the following options:

1. Vanilla kernel
2. NVInject 512MB
3. cpu=1 fix

I think those were the only things I changed - I'm guessing I could try without the cpu=1 fix but if there's any other changes to the iDeneb installation you'd recommend let me know.

Thanks again!

NForce MOBOs cannot use a vanilla kernel.....you must used a modified kernel and you should not need the cpu=1 fix......check out my blog entry on my iDeneb v1.1 10.5.4 installation guide.......

[nz_mitch]

Thanks verdant.

Followed your instructions from your blog and used all of the same except for NVInject I went with 512mb.

Here's where I get now when booting:

 compressed2.jpg   335.27K   187 downloads

Looking at that and reviewing the instructions I'm now not 100% sure if I selected a NIC driver (although my onboard NIC is disabled in bios and currently there's no PCI NIC), but I think this might be my imagination/frustration getting the better of me!

If I boot in -x I get the same, as with booting with cpus=1 maxmem=2048 etc.

If I boot in standard mode it just gets to a GSoD as I believe they're called, prompting me to restart.

At least we're making some progress though!

[verdant]

nz_mitch, on Oct 25 2008, 06:09 AM, said:

Thanks verdant.

Followed your instructions from your blog and used all of the same except for NVInject I went with 512mb.

Here's where I get now when booting:

compressed2.jpg

Looking at that and reviewing the instructions I'm now not 100% sure if I selected a NIC driver (although my onboard NIC is disabled in bios and currently there's no PCI NIC), but I think this might be my imagination/frustration getting the better of me!

If I boot in -x I get the same, as with booting with cpus=1 maxmem=2048 etc.

If I boot in standard mode it just gets to a GSoD as I believe they're called, prompting me to restart.

At least we're making some progress though!

If you had selected a Ethernet PCI NIC kext during installation, the kext will be loaded but there is no PCI NIC physically present for an internet connection to be established......

Until you get a PCI NIC installed suggest that you do the installation without selecting any network options in the installation Customize menu as per my guide.......the correct Ethernet kext can be installed later once you have your PCI NIC.......I recommend a NIC with the RealTek RTL8169 chipset........

[ Mysticus C*]

good luck with some serious problems... when you tell people not to do something, they will usually do the opposite and try to test your patience... 1-2-3 samples are fine, but when you get it very often that is very good test for nerves

[geiman]

Just thought I'd share my success;

My system:

MOBO
BFG Tech nforce 680i SLI

Chipset
NVIDIA nForce 680i SLI MCP

OnBoard Functions
8-Channel HD Azalia Audio
2-Gigabit Nvidia Ethernet Ports
6 USB 2.0 Ports
2 Firewire Ports

CPU
Intel Core 2 Duo 4300, Stock Speed: 1.83GHZ; OverClocked to: 2.13GHZ

Graphics Card
MSI NX8800GTS 512MB (G92) (no SLI)

RAM
2GB Corsair

WLAN
Netgear wg111v2 with Realtek 8187L drivers

DVD
1 x LITE-ON DVDRW SHM-165H6S:  IDE drive used with IDE-SATA converter to use with SATA

HardDrive (no raid)
1 x 320GB IDE drive (install drive)
1 x 320GB IDE drive used with IDE-SATA converter
1 x 40GB SATA drive

Partitioning
One OS, OS X 10.5.5, on 320GB SATA converted drive; Windows & Linux on 40GB SATA drive
OS'S Currently In Use
Windows Vista(not used much)
Ubuntu Ultimate 1.9
iDeneb v1.3 10.5.5

Install Status
Leopard: iDeneb 10.5.5 v1.3   Did not use available nForce ppf Patch, not sure if it would help or hurt install

iDeneb installed relatively easy; I had a minor problem where once in a while the DVD would not boot:  it would just hang without giving any errors.  So I just rebooted, reinserted the disc, and it would work fine.  Also, if  I had to reboot and try again, it seemed to work best if I took out the disc, and re-inserted it; it may have something to do with reading from the SATA dvd drive, but I'm not sure.

Other than that, the install ran very smooth.  I setup one MBR based partition to install OS X too, and installed with the 9.5.4 XNU kernel, Azalia Audio patch, NVInject 0.2.1 512MB, and the OLD AppleNforceATA.kext package.  This gave me full acceleration of graphics, audio, and both cores working on first boot, however my SATA dvd drive did not work; it was recognized but would not read any discs.  I then installed the 8187L drivers for my WLAN card, and manually installed the new TEST AppleNforceATA package, which fixed the problem with my SATA DVD drive, and GREATLY improved the read/write speeds for my harddrive.  I tried installing with the new TEST AppleNforceATA.kext package during the install instead of the old version, but whenever I went to boot my install, it would hang, and not startup without giving any errors.  This may have been due to some other error on my part, but the above method worked for me and that's what I stuck with.  As for audio, the AzaliaAudioOut patch worked great for me, but with only having audio out I tried using the Apple HDA Patcher with a realtek ALC885 codec dump, which only still gave me audio out.  It says it recognizes two inputs and a few outputs, but no inputs actually work.

Everything seems to be working great, it seems to be very stable as I haven't had it crash/KP once.  I tried the Nforce lan kext but it makes my system hang within ~4 or 5 seconds after booting.  This is the first Leopard disc that has worked for me since the original 10.5 TOH RC2 Leopard disc when Leopard was first out.

I hope I included everything you wanted, I don't have any problems, just thought I'd share my success.  If you would like any further details don't hesitate to ask.


~Geiman

[verdant]

@ Mysticus

Thanks.......if my emails, PMs and posts to you start sounding like gibberish......then I will either be before being  
Or have   and gone on a rampage   .........

@ Geiman

Thanks for the writeup......it will increase readers' confidence that OS X can be successfully installed on nForce chipset = Intel CPU MOBOs.......

[SilverSix311]

@verdant
Curently i have 10.5.2 working great other than not being able to write to SATA drives it will freeze if i do it. DUnno why... I was using the MeDevil SATA kexts. But i dunno really. And if you have AIM that would be the best way to help me out as i have 2 compys either that or i can try IRC on my dad's laptop. Anyway im ready to start trying to upgrade i just Made a time machine for my 10.5.2 install so i dont have to wait a year everytime i mess it up. Thank you for your help!

[ Mysticus C*]

verdant: i was not talking about pms or emails, i was talking about posts in this topic what i ment was good luck with the samples (people who do things totally opposite than what they are told) if you read the first couple posts here, u ll understand what i ment

[SilverSix311]

@Geiman
Since you have a 680i motherboard what BIOS settings did you use? I can get iDeneb to boot but getting past the screen telling you all the crap its doin it either freezes at Disk Read errors with i think might be my media they were a lil scratched when i burnt them, or it sits at some "Mac OSX version: Not yet" screen. So i could use a BIOS setting Sheet for 680i. Also you can contact me on Gshoe311 AIM for my cell phone.

[verdant]

 Mysticus C*, on Oct 25 2008, 07:28 PM, said:

verdant: i was not talking about pms or emails, i was talking about posts in this topic what i ment was good luck with the samples (people who do things totally opposite than what they are told) if you read the first couple posts here, u ll understand what i ment

Hi Mysticus,

I know what to you meant!.....my reference to PMs or emails was the rubbish I may end up writing in my PMs or emails to you if and when some posters send me crazy........

Cheers
verdant

SilverSix311, on Oct 25 2008, 07:41 PM, said:

@Geiman
Since you have a 680i motherboard what BIOS settings did you use? I can get iDeneb to boot but getting past the screen telling you all the crap its doin it either freezes at Disk Read errors with i think might be my media they were a lil scratched when i burnt them, or it sits at some "Mac OSX version: Not yet" screen. So i could use a BIOS setting Sheet for 680i. Also you can contact me on Gshoe311 AIM for my cell phone.

@ SilverSix311

Check your BIOS settings against the BIOS template in my Series 7 topic post #1......I have not had time to do a similar template for pre-Series 7 MOBOs yet......but I suspect the BIOS parameters and their options will match up sufficiently with those in the template to serve a useful double-check....

SilverSix311, on Oct 25 2008, 07:00 PM, said:

@verdant
Curently i have 10.5.2 working great other than not being able to write to SATA drives it will freeze if i do it. DUnno why... I was using the MeDevil SATA kexts. But i dunno really. And if you have AIM that would be the best way to help me out as i have 2 compys either that or i can try IRC on my dad's laptop. Anyway im ready to start trying to upgrade i just Made a time machine for my 10.5.2 install so i dont have to wait a year everytime i mess it up. Thank you for your help!

I  assume you tried both the AppleNForceATA.kext and AppleNForceATA-TEST.kext by MeDevil....

After you have sorted out your BIOS settings, I suggest you use Mysticus C*'s nForce Drivers package to install Voodoo Beta C2 kernel and slashack's nForceATA kext...... If you look at this post you can use Mysticus C*'s 10.5.5 Combo Updater packages to update to 10.5.5 in the same operation....

[geiman]

I'll get some pics of my BIOS settings up ASAP, but until then:

I honestly can't think of anything I had to change in the BIOS.  Everything is pretty much stock settings except for overclocking, fans, and the like.  But I'll get the pics up soon.

[geiman]

Here are some shots of my bios:

 IMG_2003.jpg   680.42K   236 downloads
 IMG_2004.jpg   727.58K   143 downloads
 IMG_2005.jpg   746.96K   113 downloads
 IMG_2006.jpg   661.22K   101 downloads
 IMG_2007.jpg   730.22K   96 downloads
 IMG_2008.jpg   715.37K   91 downloads
 IMG_2009.jpg   715.31K   117 downloads

If there is something I didn't get, or if there is anything else you need, just let me know!