In the General tab, look for a message at the bottom of the window stating “System software from developer DEVELOPER NAME was blocked.
This is just a partial answer.I managed to improve performance to around 19MB/s by doubling the clock rate.It seems that the timing spec below can be set to more interesting values, such as 'sd high-speed', but no luck for me so far.
I have troubles using both kext at the same time, so I revised the plist of both of them.They should work together now without problems and we should be able to use all of the Intel SATA and JMicron SATA ports at the same time with all of the JMicron PATA ports. Okay, so I've gone around and around on this bus and am going to post my findings here in hopes someone sees something I'm missing.I've got an ABit IP35-Pro motherboard:This motherboard has both the Intel ICH9R and the JMicron 363 controller on it, however currently I am only using the JMicron controller.
The reason for this is I have my everyday OS installed on the Intel controller and I have 2 different bios profiles for booting my trustworthy trouble free OS, and then my other OSes on an external HD. So I flip profiles, that shuts down the Intel controller completely to hide those drives from the other OSes, I flip on the power to my external HD and away I go on my quad boot setup. The JMicron on my board is used to control the 2 eSATA ports and the IDE channel just as a FYI. I'm not too concerned about the eSATA functionality, but would be happy just to boot again with AHCI mode enabled.Previously to this I had installed iATKOS v4.1 which worked with the JMicron IDE DVD drive I had fine, other distros required me to install from a SATA DVD drive and then once it was installed the JMicron driver worked fine and I was able to shut down the Intel controller again. When I used the iATKOS v4.1 I just made sure the JMicron controller was set to IDE and not AHCI, if AHCI was selected I'd have problems with the HD and long periods of no response from the installer.Now I've installed iATKOS v5 and updated to 10.5.6 via the combo update, no troubles with anything else except that if I try to put the JMicron controller in AHCI mode now I cannot get it to boot normally.
I either get a KP, IO read errors at boot and then a reboot, or the device isn't recognized.I follow what you're trying to do with the above steps, but it seems on my system it's not matching the class identifier or it just latches on to the first one and applies the driver to both device instances. This is the output from lspci in Ubuntu 8.10 with the JMicron controller in AHCI mode. (Everything works perfectly)I am unsure of how to get similar 'ioreg' output from Ubuntu to help troubleshoot the device and class ids, but the lspci information has everything that's needed to get that data so I hope that's enough for people to look at.Is there a way I can get 'ioreg' to run from within Terminal on the installer DVD? I noticed I have to do a little work even to get nano to work in that environment (fill the TERMINFO variable), but am not sure what all I would need to get ioreg to function. Everytime I goto a folder containing it, says something about no path or method available when I try to launch it.Anyone have any pointers for me with this?Also, I've been meaning to ask, in your second screenshot you're using a utility.
What is the name of that utility?! Did some more digging on this and found something odd. Even with the same match strings in the AppleAHCIPort.kext as your LegacyAppleAHCIPort.kext, it will not engage on the eSATA ports. I've tried to use your LegacyAppleAHCIPort.kext, but I get an error at bootup, I've included a picture of the screen at boot.Good news is, it looks like the JMicronATA driver is only trying to take the IDE ports, bad news is, it can't load the LegacyAppleAHCIPort.kext and either stalls there or starts getting read errors as well.
I find it strange if I remove the LegacyAppleAHCIPort.kext file that the AppleAHCIPort.kext, with the same match strings, doesn't appear in the startup at all.The startup screen was taken with the options '-v -f debug=0x100'. And here is what's in my /Extra/Extensions.mkext:drwxr-xr-x 3 root wheel 102 Jan 18 13:07 AppleACPIButtons.kextdrwxr-xr-x 3 root wheel 102 Jan 18 13:07 AppleACPIEC.kextdrwxr-xr-x 3 root wheel 102 Jan 18 13:07 AppleACPILPC.kextdrwxr-xr-x 3 root wheel 102 Jan 18 13:07 AppleACPIPCI.kextdrwxr-xr-x 3 root wheel 102 Jan 18 13:07 AppleACPIPlatform.kextdrwxr-xr-x 3 root wheel 102 Jan 18 13:07 AppleACPIPowerSource.kextdrwxr-xr-x 3 root wheel 102 Jan 18 13:07 AppleDecrypt.kextdrwxr-xr-x 3 root wheel 102 Jan 18 13:07 ApplePCIConfigurator.kextdrwxr-xr-x 3 root wheel 102 Jan 18 13:07 Disabler.kext. Here is a picture of the JMicron driver trying to take over all ports, and what it looks like when the AppleAHCIPort.kext kind of loads. I can tell it's loading in some fashion because it attempts to start up the system and starts tripping over IO errors, those errors eventually cause it to reboot, but when the drive isn't detected by any kext I just get the 'waiting for root device' over and over.
If you look in the LegacyAppleAHCIPort picture you can see the read errors at the bottom.I think I'm getting these read errors because the AppleAHCIPort.kext file doesn't know what to do with my eSATA ports or is not communicating with them correctly. Wish I would have saved the kexts I used before I moved to iATKOS v5. I have modified the JMicron 1.0 info.plist so that it matches my hardware so I don't need the legacy kext, and the legacy kext you provided didn't load so I modified the vanilla version myself to match class and device id.I really think it boils down to the AppleAHCIPort.kext not liking my eSATA ports on the JM363, wonder what can be done about that if in fact that's what's going on here.Also wanted to add, I noticed on the Ubuntu boot it not only recognizes that there are two separate devices for AHCI on the eSATA ports and IDE on the PATA port, it recognizes them on different IRQs. Ubuntu shows IRQ 16 & 17 being used while I am guessing that OSX is only showing the primary and secondary ports on the JMicronATA as being IRQ 17, not sure what the AppleAHCIPort driver is using for an interrupt.Just something I noticed, could be important, could mean nothing. Yes the AppleAHCIPort is completely silent on my system which makes things a little harder.
The screenshot of the JMicron driver trying to take over all the ports is with the JMicron driver as it sits with no class id filters. The latest version I believe does have those filters, but that screenshot was more to show what happens if it DOES try to take over the eSATA ports.If I remove the PATA device I cannot get OSX to load with just the hard drive connected to eSATA and the controller in AHCI mode. It seems no matter what I do, if I enable AHCI mode and get a kext to load, it isn't able to communicate with the controller properly.
Every time it appears a kext does attach to the eSATA controller in AHCI mode that the screen starts to fill with IO read errors and I can never get to the desktop. Normally once I start seeing those it's about 2-5 minutes of the OS trying to boot and then it just restarts.I've been digging on here for threads on eSATA ports based on the JMicron controller but haven't had any luck. I would expect to be able to boot from this port at least if I completely remove the PATA from the picture, but that doesn't seem to be the case. Looks like none of the kexts know how to communicate properly with the eSATA ports on my controller. Okay, I tried removing the JMicron kext, and rebooted, then the AppleVIAATA kext attached to it and it booted up fine. I removed the AppleVIAATA kext and upon reboot it sat at waiting for root device. I then went into the bios and enabled AHCI mode, upon boot it finds the HD, but the screen starts to fill with the IO read errors and eventually I get a reboot.To get it back to life I just booted off the CD and restored the JMicron kext from a backup location, and then went from AHCI to IDE.Wonder why this driver worked fine with 10.5.2-4 and now with 10.5.5-6 I'm having issues?
Well I got no more clues then.Just for testing I unplugged the hard drive from the ICH port and plugged it to the JMicron using a eSATA bracket and it booted up without any troubles. Granted is not a real eSATA device but it booted the same as it was plugged on the ICH ports.So your trouble could be:- Your system extensions are messed up somehow. Starting with a clean installation might fix it.- The eSATA ports on your mobo are somehow different.
It could be but I seriously doubt it, from what I know eSATA mostly differs to SATA in plugs, signaling and cabling, I dont think the controller cares where and how the device is plugged.- Your hard disk could be incompatible with Mac eSATA. I've read some reports that certain USB/1394/eSATA HD or enclosures have buggy bridge chipsets that dont get along well with Mac in eSATA mode. I got no clue which ones though. The eSATA ports on my controller might very well be 'unique', I noticed on their FTP they have two drivers listed for WinXP/Vista use:They have one for the controller, and then a special version for the eSATA version of their controller. I'm not sure what the differences are between the two as I haven't looked in depth, and windows doesn't seem to need their provided drivers to work correctly.I think I'm going to dig up my old iATKOS v4.1 disc and see if the hard drive is readable after booting from the DVD in AHCI mode. It's odd because I can start the install DVD in AHCI mode, but it still gives read errors and keeps spinning down the drive (Almost as if it's a sleep mode) and generally doesn't get very far. I believe before I was able to load the iATKOS v4.1i DVD with the controller in IDE or AHCI mode and it worked just fine.I'm thinking there's a new extension in here or something that's causing some issues with the AHCI side of things, just wish I knew how to get under the hood a little further and see if I could get some more verbose information on what's happening with the kexts/drivers and what information they're NOT telling me now.
Got it figured out. And it was the DUMBEST of things to overlook. I moved the external HD to the other eSATA connection (There are two, it was on bottom one). And it fired right up without any IO read errors!!!!I'm attaching my lspci and ioreg outputs if for nothing else to have them somewhere so I can look at them if need be in the future.Drives are orange, and that's fine with me, but I'd like to tweak the section that sees it as removeable. (It's in the ioreg report)Thanks again for your patience!! Thanks, I cant believe there is a typo in original Apple vanilla plist. I just copy and paste the generic ahci, I think it still works with that mistake or maybe not?
I remember seeing some generic AHCI controller but not sure if it was with this version. I've had great success with your 'AppleAHCIport plist-only kext for Intel ICHx SATA ports in AHCI/RAID mode' kext on my board. I've been running experiments the last few days with various methods of doing a vanilla install and have perfect results with the grub-dfe.iso.
I have multiple drives and partitions to play with what might work (and how it might work with other things ) with the minimum of tampering with the install. Previously I'd been trying several home brewed combinations and the ICH9 folder (4 kexts) download via OSX86Tools.Only thing - in System Profiler it's identified as 'ICH9R/ICH9DO/ICH9DH AHCI'. Is it possible to merely change this line in the info.plist to 'ICH9R AHCI'? Just visually it would seem more 'vanilla' to me.Unfortunately I'm also working with a Marvell 88SE6101 ATA controller that I've only had success with AppleVIAATA.kext. Any chance you can come up with a equally great replacement for that?Also, I can confirm that this works in 10.5.5 as well on my machine.Thanks for the great work.Edit: I think I've found a good solution to my ATA problem. Thanks for the quick response.The Marvell controller is ATA only:IDE interface 0101: Marvell Technology Group Ltd.
88SE6101 single-port PATA133 interface 11ab:6101 (rev b2)It's working perfectly with AppleVIAATA.kext: v0.2 from slashhack I'm only using your LegacyAppleAHCIPortIntelICHx.kext for AHCI recognition. It'll be a few days before I can test this in 10.5.6 but I'll edit the string to fix my little System Profiler report.I'll post back here with results but so far it's running far smoother with everything vanilla but the above 2 kexts and OpenHaltRestart.kext. Them.should work together now without problems and we should be able to use all of the Intel SATA and JMicron SATA ports at the same time with all of the JMicron PATA ports. If there is some mistake or I missed/mistaked some device ids please report and I'll try to fix it.Also, according to this it seems some newer ATI, NVIDIA, SiS, ULi and VIA chipsets are AHCI compliant. If you have such chipset and have a BIOS option to switch the controller to AHCI/RAID you might try using it with AppleAHCI kext. The vanilla kext has a generic personality for any AHCI controller class so it should pick it up if there is no other driver taking over it.Hi, you split up the legacy kext, one for intel one for jmicron:Does this mean that the disks on intel ahci ports can look as internal, and the jmicron esata disks can look as external at the same time? I dont know if that's posible, because the current SATA external icons fix does not change this kext, but the IOAHCIBlockStorage.kext, which is loaded for all AHCI-connected disks no matter which controller they are connected to.Maybe it could be posible to change the icons for a certain controller but I dont know of any way to change the ejectable/not ejectable property for Intel and JMicron separately.Well for me neither the orange icons, neither the orange icons nor the Eject menu bother me.I guess you are trying to make Intel ports look internal and JMicron external, right?
I had success with loading my JMicron drives as eSATA, in fact that was the only thing that made my system stable and resolved the 30 second HD pauses I would see now and again.Here's the post I made with changes I made to have the ports recognized as eSATA:Hopefully this helps you guys out in here, it just seems we don't have a 'template' plist to go off of that supports eSATA drives so I had to come up with this from strings that could be returned when running IOREG. Seems it was the fix I was looking for as I did test removing the 'ESATA' section from the plist and once again I could not mount and dismount my 1TB drive, and I got 30 second pauses again.Nice updates to the OP thorazine!
I think the dependency errors will appear in that case because it only looks for the dependencies inside the current directory/extensions.mkext.I just tried to remove the IOAHCI and IOPCI family dependencies entries from the plist and it seems to work the same way, maybe we dont need to put any dependencies in the plist-only kext, as the binary-kext will already load all the needed dependencies first.OSBundleLibrariescom.apple.iokit.IOAHCIFamily1.0.0com.apple.iokit.IOPCIFamily1.0.0com.apple.kpi.bsd8.0.0com.apple.kpi.iokit8.0.0com.apple.kpi.libkern8.0.0com.apple.kpi.mach8.0.0.