Jump to content

Darwin nForce4 ATA/SATA controller


Guest bikedude880
 Share

1,033 posts in this topic

Recommended Posts

Guest bikedude880
bikedude, do you think that your drivers for nForce4 will work for nForce 410/430 too??

Yes, it should work.

 

New beta (again). Same instructions as before. Not using Hamlo's source this time (too many errors in his code).

IOATAFamily_nVidia.zip

Link to comment
Share on other sites

Guest bikedude880
New version of driver doesn't see my SATA-drive :(

But SMART status of my IDE-drive is now enabled!! :)

Well, that's one step closer than I expected from this release. Now, is the PATA drive accelerated or not is the new question. Once PATA works fine, then it's onto the next chalenge... SATA! :(

 

Well, most recent BETA loads but it does not see my PATA drives or SATA drives.

Are you trying this on 10.4.8? It is critical that it is run under this version. Does dmesg show anything that says NVIDIA in it?

Link to comment
Share on other sites

With only my PATA connected, I now got:

 

Waiting for boot volume with UUID 67EF3022-3580-3722-BB72-E3FB0079860C

Waiting on <dict UD="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>

Couldn't alloc class "AppleIntelPIIXPATA"

Link to comment
Share on other sites

Guest bikedude880
On my second boot it doesn't see all my drives :P

and on boot it always writes smth like "couldn't alloc class "AppleIntelICH7XSATA"

 

Perfect. That's exactly what I need to know to fix this. I know exactly where that is in the code.

Link to comment
Share on other sites

Just as a question: Are you running 10.4.8? It is critical that this kext is installed under this version.

Sure I'm in 10.4.8

 

Kext is listed in the kextstat output and also in the System Profiler Extensions List.

Link to comment
Share on other sites

Guest bikedude880

Ok, new test. I do believe that this one will recognize the SATA ports properly.

 

EDIT: FOUND A BIG PROBLEM... WILL POST NEW VERION IN A FEW: 56 minutes after the hour.

EDIT2: This is the fixed version: On the hour - 4 minute fix: IOATAFamily_nVidia.zip

Link to comment
Share on other sites

Now I only get this:

 

Waiting for boot volume with UUID 67EF3022-3580-3722-BB72-E3FB0079860C

Waiting on <dict UD="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>

Still waiting for root device.

Link to comment
Share on other sites

Guest bikedude880

This is my world right now with this driver:

[17:25:37]<bikedude880> Well, my nForce kext now gets "Still waiting for root device"

[17:26:34] <Unnamed> well, that probably means it doesn't recognize your drives

[17:26:57] <Unnamed> at least you know it's loading/initializing without issue

[17:27:21] <bikedude880> That's true

[17:27:36] <bikedude880> Step in the right direction

[17:27:44] <bikedude880> And it recognizes the chipset

[17:28:09] <Unnamed> heh, I thought you didn't have an nForce4 board to test?

[17:28:17] <bikedude880> I don't

[17:28:33] <bikedude880> I have guinea pigs doing the testing

[17:28:54] <Unnamed> then I misunderstood "the chipset" :(

[17:29:11] <bikedude880> It recognizes that there is something there to talk to

[17:29:35] <bikedude880> It talks and finds out it's stupid and doesn't know that it's got a limb that wants to speak :P

[17:30:14] <Unnamed> haha, probably an accurate analogy..

Link to comment
Share on other sites

i appreciate your efforts bikedude, but possibly you're forgetting something, i don't know much about this kind of thing but is there something in AppleOnboardPCATA.kext/AppleVIAATA.kext that you are missing, coz with those we arent getting "waiting for root device", only with your driver, perhaps you're almost there just missing one last thing. thanks again, it must be really tricky not having the chipset either.

Link to comment
Share on other sites

dmesg if it helps:

0x43b7000 for hubNum 0
vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:f5:fb:8d
vmnet: Hub 0
vmnet: 	Port 0
vmnet: VMNetSetopt(8) called
vmnet: bridge-en0: got dev 0x43b1c04
vmnet: bridge-en0: up
vmnet: bridge-en0: attached
vmnet: VNetUserIfFree freeing userIf at 0x43a0100
vmnet: bridge-en0: interface en is sending notification 0xe
vmnet: bridge-en0: interface en is sending notification 0xe
vmnet: bridge-en0: interface en is sending notification 0xd
AppleYukon - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled
vmnet: bridge-en0: interface en is sending notification 0xe
bt8xx module has loaded!
bt8xx: kernel osrelease 8.8.1
bt8xx_init: failed to allocate a major number 1!
bt8xx_init: failed to allocate a major number 2!
bt8xx_init: failed to allocate a major number 3!
bt8xx_init: failed to allocate a major number 4!
bt8xx_init: failed to allocate a major number 5!
bt8xx_init: failed to allocate a major number 6!
bt8xx_init: failed to allocate a major number 7!
bt8xx_init: failed to allocate a major number 8!
bt8xx_init: failed to allocate a major number 9!
bt8xx_init: failed to allocate a major number 10!
bt8xx_init: registered with major number 11!
pciDevices(0x387b100) isValid(1)
probe_cards :ChipType vendorID(10de) deviceID(5c) revision(a2) subsystemID(0) subVendorID(0)
probe_cards :ChipType vendorID(1095) deviceID(3114) revision(2) subsystemID(7125) subVendorID(1462)
probe_cards :ChipType vendorID(109e) deviceID(878) revision(2) subsystemID(1) subVendorID(1461)
probe_cards :ChipType vendorID(109e) deviceID(36e) revision(2) subsystemID(1) subVendorID(1461)
bt8xx_attach: current_task(0x39eb010) kernel_task(0x3081da0)
bktr: ioRegisters at 0x2b745000
brooktree0: PCI bus latency is 32.
bt8xx_attach: func(36e109e) rev(2)
get_bktr_mem: size(32768) va(41f5f000) pa(12ab6000)
get_bktr_mem: size(32768) va(41f67000) pa(12abe000)
get_bktr_mem: size(65536) va(41f6f000) pa(12bd8000)
get_bktr_mem: size(1310720) va(41f7f000) pa(13fc4000)
get_bktr_mem: size(3555328) va(420bf000) pa(14104000)
bt8xx: buffer size 3555328, addr 0x14104000
bt8xx: GPIO is 0x00fff7c3
bt8xx: subsystem 0x1461 0x0001
checking msp3400c
any_i2c_devices = 1 remote = 0
bt8xx: AVer Media TV/FM, Philips FR1236 NTSC FM tuner.
probe_cards :ChipType vendorID(1102) deviceID(4001) revision(0) subsystemID(10) subVendorID(1102)
probe_cards :ChipType vendorID(1102) deviceID(7003) revision(3) subsystemID(40) subVendorID(1102)
probe_cards :ChipType vendorID(1102) deviceID(4) revision(3) subsystemID(51) subVendorID(1102)
probe_cards :ChipType vendorID(1814) deviceID(301) revision(0) subsystemID(55) subVendorID(1737)
probe_cards :ChipType vendorID(10de) deviceID(54) revision(f3) subsystemID(7125) subVendorID(1462)
probe_cards :ChipType vendorID(10de) deviceID(55) revision(f3) subsystemID(7125) subVendorID(1462)
probe_cards :ChipType vendorID(10de) deviceID(53) revision(f2) subsystemID(7125) subVendorID(1462)
probe_cards :ChipType vendorID(10de) deviceID(5d) revision(a3) subsystemID(0) subVendorID(0)
probe_cards :ChipType vendorID(10de) deviceID(141) revision(a2) subsystemID(0) subVendorID(0)
probe_cards :ChipType vendorID(10de) deviceID(5d) revision(a3) subsystemID(0) subVendorID(0)
probe_cards :ChipType vendorID(10de) deviceID(5d) revision(a3) subsystemID(0) subVendorID(0)
probe_cards :ChipType vendorID(11ab) deviceID(4362) revision(15) subsystemID(58c) subVendorID(1462)
probe_cards :ChipType vendorID(10de) deviceID(5d) revision(a3) subsystemID(0) subVendorID(0)
probe_cards :ChipType vendorID(10de) deviceID(52) revision(a2) subsystemID(7125) subVendorID(1462)
probe_cards :ChipType vendorID(10de) deviceID(50) revision(a3) subsystemID(7125) subVendorID(1462)
probe_cards :ChipType vendorID(10de) deviceID(5a) revision(a2) subsystemID(7125) subVendorID(1462)
probe_cards :ChipType vendorID(10de) deviceID(5b) revision(a3) subsystemID(7125) subVendorID(1462)
probe_cards :ChipType vendorID(10de) deviceID(59) revision(a2) subsystemID(7585) subVendorID(1462)
probe_cards :ChipType vendorID(10de) deviceID(5e) revision(a3) subsystemID(7125) subVendorID(1462)

Link to comment
Share on other sites

I've understood why this driver can't see our drives.

Sorry for my english, it's rather hard to explain, but I'll try to.

When we install IOATAFamily.kext with bikedude's script, system caches (Extensions.kextcache, Extensions.mkext) are removed.

So, at the first boot after installation of the kext, all extensions are need to be loaded. And the first boot is succesfull.

At the second boot all extensions don't need to be loaded cause Extensions.mkext and Extensions.kextcache are existing in system after the first boot.

And with these caches bikedude's driver can't see all drives.

I don't know why it is so, but it's the fact.

Link to comment
Share on other sites

bikedude, I tried your most recent driver with my notebook with nForce 430/410 SATA driver and got "Still Waitin for Root Device" message. . . but keep going with the good work! I feel that soon we will be abble to enjoy SATA on nForce controllers.

 

thank you for your efforts

Link to comment
Share on other sites

 Share

×
×
  • Create New...