Jump to content

Leopard on Pre-Series 7 NVIDIA nForce MCP + Intel CPU MOBOs


verdant
 Share

Survey of nForce chipset desktop MOBO Ownership  

386 members have voted

  1. 1. Which nForce chipset + CPU MOBO desktop system do you have?

    • Series 7 nForce chipset + Intel CPU MOBO?
      83
    • Series 6 nForce chipset + Intel CPU MOBO?
      222
    • Series 5 nForce chipset + Intel CPU MOBO?
      6
    • Series 4 nForce chipset + Intel CPU MOBO?
      6
    • Series 7 nForce chipset + AMD CPU MOBO?
      11
    • Series 6 nForce chipset + AMD CPU MOBO?
      16
    • Series 5 nForce chipset + AMD CPU MOBO?
      17
    • Series 4 nForce chipset + AMD CPU MOBO?
      20
    • I have a Series 600M nForce chipset + AMD S1 CPU laptop/notebook MOBO
      6
    • nForce chipset + CPU combo MOBO not listed above
      8
  2. 2. What is your nForce chipset desktop MOBO system CPU?

    • Intel Penryn (Wolfdale)
      9
    • Intel Penryn (Yorkdale)
      2
    • Intel Core 2 Extreme (Quad)
      14
    • Intel Core 2 Extreme (Dual)
      3
    • Intel Core 2 Quad
      112
    • Intel Core 2 Duo
      166
    • Intel Pentium D9xx
      4
    • Intel Pentium D8xx
      5
    • Intel Pentium 4
      7
    • Intel Celeron D
      2
    • AMD Phenom
      7
    • AMD Athlon 64 FX
      3
    • AMD Athlon 64 X2
      52
    • AMD Athlon 64
      6
    • AMP Sempron
      1


964 posts in this topic

Recommended Posts

Hey Guys, was reading the thread and thought you might be able to help. I'm working with iPC 10.5.6 and have it up and running to my satisfaction except for 2 elements to my knowledge.

1st. I have 3 sata drives in my Comp and for some reason OSx is not mounting the two formated NTFS with my windows installs. This isn't a major problem but i would like to be able to access them so as to be able to transfer files back and forth. Profiler can see them but it just doesn't seem to be mounting them for me to access.

2nd. My dvd drive seems to not be reading anything as i put in a cd or dvd and it asks what do do with blank dvd.

 

I am trying a few things but any help would be appreciated... Thanks ahead of time.

 

so it looks like your sata isn't installed yet :)

try this to install with easy kext installer and it should work fine !

http://forum.insanelymac.com/index.php?showtopic=35985

Link to comment
Share on other sites

Hi verdant.

 

As you asked, I put my memory clock to 667 MHz from 800 MHz.

My System Profiler still doesn´t recognizes my memory clock. It identifies it likes 0 Mhz.

 

[]´s

 

Has RAM speed reduction help with random freezes.......as for System Profiler, did you install an AppleSMBIOS hard-coded for 800MHz RAM?...........anyhow your RAM runs at the BIOS specified speed regardless of what System Profiler shows........

 

won't it work on the linksys?

 

AFIK it depends on the version (and I guess the chipset).......see here......

Link to comment
Share on other sites

You need to check and post the BIOS options under the Power Management sub-menu........see the last blue BIOS screen in your earlier post.....

 

Hi, verdant.

 

This message is only to tell you thanks for your efforts. I couldn't install in the computer so I have changed my mind with my computers and I will try in another with a G33 Intel chipset. I think it would be easy -_- but I'm not sure. As I have another chipset I will move to another thread, but thank you (one more time, and if you need more thanks tell me).

 

Best regards from Spain

Link to comment
Share on other sites

Hi, verdant.

 

This message is only to tell you thanks for your efforts. I couldn't install in the computer so I have changed my mind with my computers and I will try in another with a G33 Intel chipset. I think it would be easy ;) but I'm not sure. As I have another chipset I will move to another thread, but thank you (one more time, and if you need more thanks tell me).

 

Best regards from Spain

 

Hi jccguays

 

Thanks for taking the time to update me on your situation......I wish you success with the G33 Intel chipset......sorry I was not able to get you running on your 610i MOBO.....BTW I came across this on insanelymac:

 

mrburns05 Dec 24 2007, 01:41 PM This should fix the mDNSresponder issues (I was having them also until i did this, now no trouble at all):

 

goto "System/Library/LaunchDaemons" and edit the two "com.apple/mDNSresponder......"files (forget the entire name but theres only two- youll see em)

 

in those files i hade to change this section:

<key>Label</key>

<string>com.apple.mDNSResponder</string>

<key>OnDemand</key>

<false/>

<key>ProgramArguments</key>

<array>

 

to this:

 

<key>Label</key>

<string>com.apple.mDNSResponder</string>

<key>Disabled</key>

<true/>

<key>ProgramArguments</key>

<array>

 

Then repaired disk permissions

 

but I do not know if it would have helped you......I see a sandbox error message similar to yours but [37] not [23] but it has no apparent effect on OS X booting up and operating smoothly......

 

Link to comment
Share on other sites

Hi everyone. I've been attempting to get OSx86 installed on my system for quite a while now, and near everything I've tried has not worked. My system specs are listed in my signature, but I'll expand on them a bit.

 

Motherboard: MSI P6N SLI Platinum

 

nForce Series 6: 650i

 

CPU: Intel Core 2 Quad Q6600 G0 Stepping. 4 Cores, 2.4GHz Stock and staying that way.

 

Do not currently have screenshots of my BIOS, will attempt to get some later on today.

 

DVD Drive: IDE, Only 1

 

Hard Drive: 2 SATA (1 320GB, 1 1TB), 1 IDE (320GB) (Main HDD is SATA). No RAID.

 

Partitioning: Main HDD is currently split between Windows XP SP3 and Linux, but will remove Linux for OSx86

 

Operating Systems: Windows XP Professional SP3 and Ubuntu 8.10

 

Graphics Card: XFX PVT84JUDD3 GeForce 8600GT XXX 256MB 128-bit GDDR3. Not in SLI.

 

PCI/PCI-E: The Graphics Card is PCI-Express, and no other cards

 

Onboard Devices: Audio Chipset|Realtek ALC888 LAN|Realtek 8211BL Firewire|1 Port USB|2.0, 6 Ports eSATA|1

OSx86 Status: Currently have attempted to install Kalyway 10.5.2, but unit will just hang at 'Still waiting for root device...', no matter what I try.

 

Install DVDs: Kalyway 10.5.2, but I can get any others that are needed

 

Problems: Like stated earlier, it will just hang at 'Still waiting for root device...' no matter what. I have followed this tutorial here as best I can (unable to locate BIOS v2.2, MSI's website only goes up to 1.6?) and I still get 'Still waiting for root device...'

 

I've almost given up at this point, but I really think I can get this working. Any help or tips or anything really at this point would be a HUGE help. Thanks in advance!

Link to comment
Share on other sites

@ DGNeo

 

Have you modded your BIOS? .......if you can only boot with cpus=1 you may have to.......see post #1 in this thread......

 

I have just done a quick Google search for MSI BIOS v2.2......it could be the driver here.......

Link to comment
Share on other sites

@ DGNeo

 

Have you modded your BIOS? .......if you can only boot with cpus=1 you may have to.......see post #1 in this thread......

 

I have just done a quick Google search for MSI BIOS v2.2......it could be the driver here.......

 

I have not modded my BIOS. I did download the modified BIOS that Kabyl made for my motherboard, I just have to figure out how to install it haha.

 

And I did see that BIOS, but the problem is, it's for the MSI P6N SLI-FI, which is a different motherboard than the one I'm using.

 

I'm not sure what you meant by boot either. I've tried the cpus=1 and everything, but no matter what it hangs on 'Still waiting for root device...'

Link to comment
Share on other sites

I have not modded my BIOS. I did download the modified BIOS that Kabyl made for my motherboard, I just have to figure out how to install it haha.

 

And I did see that BIOS, but the problem is, it's for the MSI P6N SLI-FI, which is a different motherboard than the one I'm using.

 

I'm not sure what you meant by boot either. I've tried the cpus=1 and everything, but no matter what it hangs on 'Still waiting for root device...'

 

Do you get the 'Still waiting for root device...' when booting from the DVD with -v cpus=1 maxmem=2048 platform=ACPI|86PC -legacy debug=0x100 ?

 

Have you checked your BIOS settings against the recommended 650i settings in post #1 and what about OSXCores......there are 10.5.5 modded BIOSs there for more than one variant of your MOBO....

 

(MS)-7383v52 P6N SLI Platinum

 

(MS)-7350v16 *(NMS) P6N SLI Platinum

Link to comment
Share on other sites

Do you get the 'Still waiting for root device...' when booting from the DVD with -v cpus=1 maxmem=2048 platform=ACPI|86PC -legacy debug=0x100 ?

 

Have you checked your BIOS settings against the recommended 650i settings in post #1 and what about OSXCores......there are 10.5.5 modded BIOSs there for more than one variant of your MOBO....

 

(MS)-7383v52 P6N SLI Platinum

 

(MS)-7350v16 *(NMS) P6N SLI Platinum

 

I just attempted it again, using those settings, and I still get the waiting for root device. I did notice that with this DVD I get the SAM Multimedia Read/Write Error, so I'm currently redownloading the Kalyway ISO and reburning it at a MUCH slower speed (I did max last time).

Link to comment
Share on other sites

Has RAM speed reduction help with random freezes.......as for System Profiler, did you install an AppleSMBIOS hard-coded for 800MHz RAM?...........anyhow your RAM runs at the BIOS specified speed regardless of what System Profiler shows........

 

Hi mate.

Sorry for the late response, but I´m working a lot these days because of carnival party here in Salvador, Bahia - Brazil. :wacko:

I didn´t have the time to check if reducing the RAM clock speed will help with the freeze, because as I´m using my machine a lot, I can´t put it to test while I´m working on it, because if it freezes, I loose all my job and this isn´t smart, right? ;)

 

Well, about the AppleSMBIOS hard-coded for 800MHz RAM, I believe I didn´t installed any file for that. If there´s a way to do so, please let me know. I´ll be glad to install it.

 

Hope to come here more often soon.

 

[]´s

Link to comment
Share on other sites

I just attempted it again, using those settings, and I still get the waiting for root device. I did notice that with this DVD I get the SAM Multimedia Read/Write Error, so I'm currently redownloading the Kalyway ISO and reburning it at a MUCH slower speed (I did max last time).

 

Yes, it is very important that you burn at a very slow speed........definitely ≤ x4........preferably x1 or x2........ :)

 

Hi mate.

Sorry for the late response, but I´m working a lot these days because of carnival party here in Salvador, Bahia - Brazil. :wacko:

I didn´t have the time to check if reducing the RAM clock speed will help with the freeze, because as I´m using my machine a lot, I can´t put it to test while I´m working on it, because if it freezes, I loose all my job and this isn´t smart, right? ;)

 

Well, about the AppleSMBIOS hard-coded for 800MHz RAM, I believe I didn´t installed any file for that. If there´s a way to do so, please let me know. I´ll be glad to install it.

 

Hope to come here more often soon.

 

[]´s

 

No problem....... :)

 

Many Install Distro's give an option of an AppleSMBIOS hard-coded for a specific RAM speed.....which if you had it installed may be a "problem" if you then drop the RAM speed in the BIOS, which is the speed the RAM will run at regardless of what the AppleSMBIOS "thinks" and shows......

Link to comment
Share on other sites

hi there,

 

okie, here we go, after sucessfull install and 99% running mac os x in my dell xps1330 now i'm trying to hack my desktop computer, sorry for me with an nForce MOBO, diving the forums i just reached this thread and the ray of light with it.

 

trying to install iAtkos 5i, if no options passed to darwin boot, just the apple screen appears and the machine reboots, a problem with ACPI, if i used the cpus=1 option, then i can get the boot to the "Still waiting for root device" stage, i suposse i need to make the trick with an IDE hd, but sad for me, i don't have got one :).

 

regarding BIOS, i can't change the SATA Mode, is disabled and permantly set to Raid, i have the raid disabled in the four sata channels, so i suppose the sata mode is AHCI or RAID depending on the state of each sata channel, enabled or disabled raid.

 

now, my machine specs, extracted from cpu-z and the hardware manager from Windows XP:

 

DMI

------------------------------------------------------------------------------

 

DMI BIOS

--------

vendor American Megatrends Inc.

version R01-B4

date 09/11/2008

 

 

DMI System Information

----------------------

manufacturer ACER

product Aspire M1641

version R01-B4

serial 91KNR7ZECB842009EF2900

UUID 0021856B-31BB2008-10231209-54000000

 

 

DMI Baseboard

-------------

vendor ACER

model MCP73VE

revision NVIDIA MCP73

serial 000000000

 

 

Processors Information

------------------------------------------------------------------------------------

 

Processor 1 (ID = 0)

Number of cores 2 (max 2)

Number of threads 2 (max 2)

Name Intel Pentium E5200

Codename Wolfdale

Specification Pentium® Dual-Core CPU E5200 @ 2.50GHz

Package Socket 775 LGA (platform ID = 0h)

CPUID 6.7.6

Extended CPUID 6.17

Core Stepping M0

Technology 45 nm

Core Speed 1200.2 MHz (6.0 x 200.0 MHz)

Rated Bus speed 800.1 MHz

Stock frequency 2500 MHz

Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, EM64T

L1 Data cache 2 x 32 KBytes, 8-way set associative, 64-byte line size

L1 Instruction cache 2 x 32 KBytes, 8-way set associative, 64-byte line size

L2 cache 2048 KBytes, 8-way set associative, 64-byte line size

FID/VID Control yes

FID range 6.0x - 12.5x

max VID 1.225 V

Features XD

 

Chipset

------------------------------------------------------------------------------

 

Northbridge NVIDIA GeForce 7050 rev. A2

Southbridge NVIDIA nForce 620i rev. A2

Memory Type DDR2

Memory Size 4096 MBytes

Channels Single

Memory Frequency 333.4 MHz (3:5)

CAS# 5.0

RAS# to CAS# 4

RAS# Precharge 4

Cycle Time (tRAS) 14

Bank Cycle Time (tRC) 19

Command Rate 2T

 

Memory SPD

------------------------------------------------------------------------------

 

DIMM #1

 

General

Memory type DDR2

Module format Regular UDIMM

Manufacturer (ID) Apacer Technology (7F7A000000000000)

Size 2048 MBytes

Max bandwidth PC2-6400 (400 MHz)

Part number 75.A73AA.G03

Serial number 02308165

Manufacturing date Week 16/Year 08

 

Attributes

Number of banks 2

Data width 64 bits

Correction None

Nominal Voltage 1.80 Volts

EPP no

XMP no

 

Timings table

Frequency (MHz) 200 266 400

CAS# 3.0 4.0 5.0

RAS# to CAS# delay 3 4 5

RAS# Precharge 3 4 5

TRAS 9 12 18

TRC 12 16 23

 

DIMM #2

 

General

Memory type DDR2

Module format Regular UDIMM

Manufacturer (ID) Apacer Technology (7F7A000000000000)

Size 2048 MBytes

Max bandwidth PC2-6400 (400 MHz)

Part number 75.A73AA.G03

Serial number 02308165

Manufacturing date Week 16/Year 08

 

Attributes

Number of banks 2

Data width 64 bits

Correction None

Nominal Voltage 1.80 Volts

EPP no

XMP no

 

Timings table

Frequency (MHz) 200 266 400

CAS# 3.0 4.0 5.0

RAS# to CAS# delay 3 4 5

RAS# Precharge 3 4 5

TRAS 9 12 18

TRC 12 16 23

 

 

Graphic Card: PCI\VEN_10DE&DEV_07E5&SUBSYS_01371025&REV_A2\3&267A616A&0&80

DVD Drive: SCSI\CDROM&VEN_HL-DT-ST&PROD_DVDRAM_GH15F&REV_EG00\4&28799283&0&110

Lan: {1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV07DC\4&FD95245&0&00

Processor: ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_0

RAID Controller: Nvidia NForce ACPI\NVRAID20\3&267A616A&0

SATA Controller: Nvidia NForce PCI\VEN_10DE&DEV_07F8&SUBSYS_01371025&REV_A2\3&267A616A&0&70

Audio 0x01: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10250137&REV_1001\4&1171BB9A&0&0001

Audio 0x02: PCI\VEN_1102&DEV_0005&SUBSYS_00211102&REV_00\4&33E0692E&0&3050

 

 

thanks in advance for all the help.

 

regards from spain.

 

d.

Link to comment
Share on other sites

Many Install Distro's give an option of an AppleSMBIOS hard-coded for a specific RAM speed.....which if you had it installed may be a "problem" if you then drop the RAM speed in the BIOS, which is the speed the RAM will run at regardless of what the AppleSMBIOS "thinks" and shows......

 

So, as I didn´t installed the SMBIOS on RAM speed, I don´t have to do it, right?

 

It´s incredible how I don´t have problems when running 2 Gb. I run at the same time a lot of heavy programs as Photoshop, Illustrator, Adobe CS4 Bridge, iTunes and many others and get no KP, but the other day I was using 3 Gb RAM and when I closed iTunes and started VLC, freeze came.

 

[]´s

 

EDIT

 

Hi verdant. I´m editing this message to post some pics I got from a KP when I was working this afternoon.

Sorry for the poor image quality, but I had only my old cell phone to do it. :)

 

0502091525ye1.th.jpg 0502091524ym7.th.jpg 0502091523fa4.th.jpg 0502091522gw1.th.jpg 0502091521ex2.th.jpg

 

When you can, take a look at this and tell me if there´s a solution.

 

[]´s

Link to comment
Share on other sites

@ breakingbad

 

Suggest you upgrade from Voodoo Beta 2C kernel to Voodoo Release v1.0 Rev_A by running the installer from here......then report what happens......

 

@ el.......rostro

 

It would be helpful if you can explain what you mean by "i can't change the SATA Mode, is disabled and permantly set to Raid"........is the Sata Mode Select option set as [RAID] and greyed out? What other SATA / IDE parameter setting options do you have in your BIOS......?

 

I do not know if you could use the Linux R01-B3-Linux BIOS instead of the R01-B4-Windows BIOS from here......

 

Do you get the 'Still waiting for root device...' when booting from the DVD with -v cpus=1 maxmem=2048 platform=ACPI|86PC -legacy debug=0x100 ?

 

Also check your BIOS settings against recommended settings for 610i and/or 630i in post #1 of this thread.......

Link to comment
Share on other sites

Yes, it is very important that you burn at a very slow speed........definitely ≤ x4........preferably x1 or x2........ :)

 

So I just reburned the DVD at 2x speeds, and I'm still getting the SAM Multimedia Read/Write Error. My DVD's are pretty good quality (older Verbatim DVD-R's) and it still didn't work. Any other options?

Link to comment
Share on other sites

@ breakingbad

 

Suggest you upgrade from Voodoo Beta 2C kernel to Voodoo Release v1.0 Rev_A by running the installer from here......then report what happens......

 

Hi mate.

 

Already upgraded for the new Voodoo kernel. Let´s see how the system will behave. Thanx for the help.

 

[ ]´s

Link to comment
Share on other sites

So I just reburned the DVD at 2x speeds, and I'm still getting the SAM Multimedia Read/Write Error. My DVD's are pretty good quality (older Verbatim DVD-R's) and it still didn't work. Any other options?

 

Have you installed Kabyl's modded BIOS yet........if not, breakingbad has exactly the same MOBO as you AFIK......perhaps he can guide you by posting in this thread a HOW TO on installing the Kabyl BIOS as he has already done so?

 

Hi mate.

 

Already upgraded for the new Voodoo kernel. Let´s see how the system will behave. Thanx for the help.

 

[ ]´s

 

OK........BTW would you be willing to post a HOW TO in this thread on installing Kabyl's modded BIOS on your MOBO model?.......it may help DGNeo.......

Link to comment
Share on other sites

OK........BTW would you be willing to post a HOW TO in this thread on installing Kabyl's modded BIOS on your MOBO model?.......it may help DGNeo.......

 

Hi mate.

I can try to do it. In fact is very simple. You may need some basic knowledge in MS-DOS commands since you may need to boot with some Win98 Boot Disc.

 

I´ll do a little guide and post it here in a later moment because right now I´m quite busy.

 

[]´s

Link to comment
Share on other sites

@ el.......rostro

 

It would be helpful if you can explain what you mean by "i can't change the SATA Mode, is disabled and permantly set to Raid"........is the Sata Mode Select option set as [RAID] and greyed out? What other SATA / IDE parameter setting options do you have in your BIOS......?

 

yeah, the Sata mode option is not changeable and is greyed, i can enable or disable each raid channel in anotherr bios screen.

 

I do not know if you could use the Linux R01-B3-Linux BIOS instead of the R01-B4-Windows BIOS from here......

 

i will try to reflash computerr this weekend, i suposse i will be able to use this bios file.

 

Do you get the 'Still waiting for root device...' when booting from the DVD with -v cpus=1 maxmem=2048 platform=ACPI|86PC -legacy debug=0x100 ?

 

yes, still the same message, now i have a ide PATA disc in the unique ide channel in the computer, the bios and windows xp recognizes the hard disk, but i suposse osx not.

 

Also check your BIOS settings against recommended settings for 610i and/or 630i in post #1 of this thread.......

 

okie, i will do asap.

 

thanks for the help.

 

regards, d.

Link to comment
Share on other sites

Hi verdant, I just found this and I think it's MUST HAVE for every NForce user. No more "IOKitWaitQuiet() timed out waiting to write kernel symbols"; it makes boot really faster. Credits goes to the autor.

 

Thanks for the info......I will test it out and assuming all is OK will add link to my post #1...... ;)

 

EDIT: Update......I have tested the 10.5.6 version of the ar4er modified IOATAFamily.kext (following the idea of coolyou of modifying the timeout setting) on my eSATA HDD OS X volume......it boots OK and removes the delay "IOKitWaitQuiet() timed out waiting to write kernel symbols".......HOWEVER in my case at least, when I put OS X to sleep and then wake OS X from sleep all the HDD volumes (i.e. both eSATA external and SATA internal HDD volume icons) appear on the Desktop......but I then get the "Device Removal" warning message appearing

 

Device Removal

The device you removed was not properly put away. Data might have been lost or destroyed. Before you unplug your device, you must first select its icon in the Finder and choose Eject from the File view.

 

and just afterwards the SATA internal HDD volume icons begin disappearing from the Desktop until all have disappeared........

 

The reason for this becomes apparent when the function of IOKitWaitQuiet is seen in IOATAController.cpp :

for( int i = 0; [color="#ff0000"]i < 3100[/color]; i++)
{

// read the status register - helps deal with devices which errantly
// set interrupt pending states during resets. Reset operations are not
// supposed to generate interrupts, but some devices do anyway.
// interrupt handlers should be prepared to deal with errant interrupts on ATA busses.
OSSynchronizeIO();
UInt8 status = *_tfStatusCmdReg;

// when drive is ready, break the loop
if( ( status & readyMask )== readyOn)
{
// device reset completed in time
resetFailed = false;
break;
}

IOSleep( 10 ); // sleep thread for another 10 ms

}


if( resetFailed )
{
// it is likely that this hardware is broken.
// There's no recovery action if the drive fails
// to reset.
DLOG("IOATA device failed to reset.\n");
result = kATATimeoutErr;
}

DLOG("IOATA reset complete.\n");

return result;

}


/*---------------------------------------------------------------------------
*
* Subclasses should take necessary action to create DMA channel programs,
* for the current memory descriptor in _currentCommand and activate the
* the DMA hardware
---------------------------------------------------------------------------*/
IOReturn
IOATAController::startDMA( void )
{


DLOG("IOATA Bus controllers that offer DMA must provide implementation/n");

return kATAModeNotSupported;
}




/*---------------------------------------------------------------------------
* Subclasses should take all actions necesary to safely shutdown DMA engines
* in any state of activity, whether finished, pending or stopped. Calling
* this function must be harmless reguardless of the state of the engine.
*
---------------------------------------------------------------------------*/
IOReturn
IOATAController::stopDMA( void )
{

DLOG("IOATA Bus controllers that offer DMA must provide implementation/n");

return kATAModeNotSupported;
}


/*---------------------------------------------------------------------------
// WaitForU8Status
// Will wait up to one millisecond for the value in the altStatus register & mask to equal the value
// passed in. Note that I always use the altStatus register so as not to have the side affect of clearing
// the interrupt if there is one.
---------------------------------------------------------------------------*/
bool
IOATAController::waitForU8Status (UInt8 mask, UInt8 value)
{
int i;

// we will read the status from the alt status register so as not
// to clear the interrupt accidentally

for (i=0; i < kStatusDelayLoopMS; i++)
{
OSSynchronizeIO();

if ((*_tfAltSDevCReg & mask) == value)
{
return true;
}

IODelay( kStatusDelayTime );
}
return false; // time's up
}

/*----------------------------------------------------------------------------------------------------
** Routine ATAPISlaveExists
**
** Purpose: Determines whether an ATAPI device seen as a "slave" of a master ATAPI device
** is actually present, or the product of the master shadowing a not-present slave's registers
** Call this function when the master device shows EBh 14h, and the slave also shows the ATAPI
** protocol signature.
** Returns: False if a device is ruled out. True if a device is verified. Leaves device in a ready state,
** But no longer showing signatures.

NOTE: Device 1 (slave) is assumed already selected.
*/


bool
IOATAController::ATAPISlaveExists( void )
{
UInt8 scratchByte;
UInt16 scratchWord;
UInt32 dataCounter;
UInt32 loopCounter;

// The only option is to issue a command and see what happens.
OSSynchronizeIO();
*_tfAltSDevCReg = 0x02; // disable interrupts

//issue INDENTIFY PACKET DEVICE
OSSynchronizeIO();
*_tfStatusCmdReg = 0xA1;

// reading and disreguarding a register provides the required 400ns delay time.
OSSynchronizeIO();
scratchByte = *_tfAltSDevCReg;

OSSynchronizeIO();
scratchByte = *_tfAltSDevCReg;

// if the device returns status 00h, we declare it not present. A real device would probably be
// status BSY (80h) now. An incredibly fast device might be ready to move data and show DRQ.
// However, by ATA standards, a not present device is required to return 00h.
// Lucky break, no device and we figured it out in a hurry.

if( (scratchByte == 0x00) )
{
// enable device interrupt
*_tfAltSDevCReg = 0x00;
OSSynchronizeIO();
return false;
}

// OK we probably have a device now. We have to wait for drive to send data, and read it and clear it.
// It is possible that the a misbehaving master has decided to respond to the command. So, we'll
// break on error bit and say it's not a real slave should that happen.

// take a leisurely approach, this will take a while.

// give the device up to 10 seconds to respond with data.
for( loopCounter = 0; loopCounter < 10000; loopCounter++)
{
OSSynchronizeIO();
scratchByte = *_tfAltSDevCReg;

// If drive sets error, clear status and return false. It's probably a misbehaving master
if( scratchByte & 0x01 )
break;

// this means the drive is really there. Clear the data and return true.
if( (scratchByte & 0x58) == 0x58) // RDY=1 DRQ=1
{
OSSynchronizeIO();
scratchByte = *_tfStatusCmdReg; // clear pending interrupt state

for( dataCounter = 0; dataCounter < 256; dataCounter++ )
{
OSSynchronizeIO();
scratchWord = *_tfDataReg;
}
// enable device interrupt
*_tfAltSDevCReg = 0x00;
OSSynchronizeIO();
return true;
}

// OK, sleep for 10 ms and try again.
IOSleep(10);
}

// In the ugly case, a drive set BSY, and didn't respond within 10 seconds with data.
// Otherwise, this is the for loop terminating on seeing the error bit.
// We'll read status and return false.

OSSynchronizeIO();
scratchByte = *_tfStatusCmdReg; // clear pending interrupt state

// enable device interrupt
*_tfAltSDevCReg = 0x00;
OSSynchronizeIO();

return false;

}



/*---------------------------------------------------------------------------
* scan the bus to see if devices are attached. The assumption is that the
* devices are in a cleanly-reset state, showing their protocol signatures,
* and the bus is properly wired with a pull down resistor on DD:7.
* If your bus controller does not meet these conditions, you should override
* and supply your own function which meets your specific hardware needs.
* Your controller may or may not require a reset, or it may require more
* thorough scanning, or additional configuration prior to looking for drives,
* or it may aquire information from firmware indicating the devices attached.
* This function should be self contained and not rely upon work loop or
* or anything other than the register pointers being setup and enabled for access
---------------------------------------------------------------------------*/

UInt32
IOATAController::scanForDrives( void )
{
UInt32 unitsFound = 0;
UInt8 status = 0x00;
// [color="#ff0000"]count total time spent searching max time allowed = 31 secs[/color]
// it RARELY takes this long.
UInt32 milsSpent = 0;

// wait for a not busy bus
// should be ready, but some devices may be slow to wake or spin up.
for( int loopMils = 0; [color="#ff0000"]milsSpent < 3100[/color]; loopMils++ )
{
OSSynchronizeIO();
status = *_tfStatusCmdReg;
if( (status & mATABusy) == 0x00 )
break;

IOSleep( 10 );
milsSpent++;
}

// spun on BSY for too long, declare bus empty
if( ! ([color="#ff0000"]milsSpent < 3100[/color]) )
goto AllDone;


// select each possible device on the bus, wait for BSY-
// then check for protocol signatures.

for( int unit = 0; unit < 2; unit++ )
{

// wait for a not busy bus
for( int loopMils = 0; [color="#ff0000"]milsSpent < 3100[/color]; loopMils++ )
{
// write the selection bit
OSSynchronizeIO();
*_tfSDHReg = ( unit << 4 );
IODelay( 10 );
// typically, devices respond quickly to selection
// but we'll give it a chance in case it is slow for some reason.
status = *_tfStatusCmdReg;
if( (status & mATABusy) == 0x00 )
{
break;
}

IOSleep( 10 );
milsSpent++;
}

// spun on BSY too long, probably bad device
if( ! ([color="#ff0000"]milsSpent < 3100[/color]) )
goto AllDone;

// check for ATAPI device signature first
if ( ( *_tfCylLoReg == 0x14) && ( *_tfCylHiReg == 0xEB) )
{
if( (unit == 1 )
&& ( _devInfo[0].type == kATAPIDeviceType ) )
{

// OK we've met the condition for an indeterminate bus, master is atapi and we see a slave atapi
// signature. This is legal ATA, though we are fortunate enough that most devices don't do this.

if( ATAPISlaveExists( ) != true )
{
_devInfo[unit].type = kUnknownATADeviceType;
goto AllDone;

}

}

_devInfo[unit].type = kATAPIDeviceType;
_devInfo[unit].packetSend = kATAPIDRQFast; // this is the safest default setting
unitsFound++;

} // check for ATA signature, including status RDY=1 and ERR=0
else if ( (*_tfCylLoReg == 0x00) && (*_tfCylHiReg == 0x00) &&
(*_tfSCountReg == 0x01) && (*_tfSectorNReg == 0x01) &&
( (*_tfAltSDevCReg & 0x51) == 0x50) )
{

_devInfo[unit].type = kATADeviceType;
_devInfo[unit].packetSend = kATAPIUnknown;
unitsFound++;

}else{

_devInfo[unit].type = kUnknownATADeviceType;
_devInfo[unit].packetSend = kATAPIUnknown;
}

}

 

where i < 3100 has been changed to i < 100, and all occurrences of milsSpent < 3100 have been changed to milsSpent < 100......perhaps less of a change, e.g. to <1000 may solve this issue......

Link to comment
Share on other sites

Hi mate.

 

Even upgrading the kernel solved my freezing problem.

It still freezing even in low usage of memory and processor. Don´t know why it happens.

 

I´ll try to start system using the 4 Gb RAM to see if freezes as fast as using 3Gb.

When using 3Gb RAM don´t take to long to freeze.

 

When using only 2Gb I can run OS X for days without restarting or freeze.

 

[]´s

 

P.S. - I´ll try to help our other mate about flashing his BIOS. ; )

Link to comment
Share on other sites

Hi mate.

 

Even upgrading the kernel solved my freezing problem.

It still freezing even in low usage of memory and processor. Don´t know why it happens.

 

I´ll try to start system using the 4 Gb RAM to see if freezes as fast as using 3Gb.

When using 3Gb RAM don´t take to long to freeze.

 

When using only 2Gb I can run OS X for days without restarting or freeze.

 

[]´s

 

P.S. - I´ll try to help our other mate about flashing his BIOS. ; )

 

I am beginning to wonder if there is some incompatibility between your Kabyl modded BIOS/MOBO/800MHz DDR2 RAM that OS X patched kernels are sensitive to......

Link to comment
Share on other sites

I am beginning to wonder if there is some incompatibility between your Kabyl modded BIOS/MOBO/800MHz DDR2 RAM that OS X patched kernels are sensitive to......

 

That´s sound bad to me. : (

 

I asked Kabyl´s to mod my newest BIOS version, but he didn´t answered my request yet.

If I send you my modded BIOS you can check to see if there´s something wrong? If yes, let me know so I can send you.

 

In fact, when my BIOS was modded by Kabyl, the only issue till that time was about the cores of my CPU, I don´t know if he fixed any other issue related to BIOS fixing for MSI mobo´s.

 

[]´s

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...