Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About dukzcry

  • Rank

Contact Methods

  • Website URL

Recent Profile Visitors

4,230 profile views
  1. iTCOWatchdog.kext

    Version 1.0.0


    Watchdog timer driver for boards with ICH southbridge Topic https://www.insanelymac.com/forum/topic/284657-watchdog-timer-driver-for-boards-with-ich-southbridge/
  2. SASMegaRAID.kext

  3. Driver for LSI MegaRAID SAS family

    That's wrong device. 8086 is intel, perhaps some device on your mobo. Correct one would be VEN_1000&DEV_0073: http://www.pcidatabase.com/search.php?device_search_str=0073&device_search=Search Here's a little utility to show devices id under OS X: http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/page-10?do=findComment&comment=2026275
  4. Driver for LSI MegaRAID SAS family

    Well, you should be able to load it after OS is booted without need of dev mode, since its added in permitted kexts list However it most likely won't work in case you try to boot OS X from the volume on a raid card. At least last time I've checked, the non-signed kext granting didn't work for kexts with early boot requirement: http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/page-14?do=findComment&comment=2134840 The 3rd party firmware is compatible if it at least exposes the same ABI as LSI fw does. Dell firmware works, for example.
  5. Driver for LSI MegaRAID SAS family

    justroach, > I swapped a known working card into the system and experienced the same results. I took the non-working 9260 out and put it into a known working system and everything worked. Oh weird... noradninj, Replied to your PM message instead. ElStuiterbal, If there is no output, that most likely means the kext doesn't match against your device. What PCI device ID do you have (you could look at using dspci/lspci or using another OS)? justroach, I remember you were successfully using H310 cards. Could you still look at DevIDs and FW revisions of your cards, so we could help ElStuiterbal to get running?
  6. Driver for LSI MegaRAID SAS family

    Open Terminal.app: # cp -r /Volumes/EFI/EFI/CLOVER/kexts/10.10/SASMegaRAID.kext /tmp; chown -R root:wheel /tmp/SASMegaRAID.kext; kextutil -v /tmp/SASMegaRAID.kext ... /tmp/SASMegaRAID.kext successfully loaded (or already loaded). # dmesg | grep SAS ... and post results here. You'd better to start with normal kext, not the debug one.
  7. Driver for LSI MegaRAID SAS family

    Hi. What confuses me is that > [SASMegaRAID] 3 of PDs present You have 3 physical disks attached to a raid card. > mfi0 Configuration: 1 arrays, 1 volumes, 0 spares > array 0 of 2 drives Only two of which are used in a raid array. Have you ever tried to disconnect non-involved one(s) from the card? > might this be an issue at all? as far as I understand, running the PERC 6/i in a PCIe 4x slot will just impact transfer rate Not likely. I'm more with your last sentence. You may also try io debug and full debug kexts and compare kernel buffer messages on when you use just that that old 100 gb drive and when you use 2x 2 tb drives (meanwhile, what about creating raid0 of single 2 tb drive or raid1 of both? Does it work?) to see where it stucks with your 4 tb raid volume. Am I right that it works fine on your side under another OS, like Windows?
  8. Driver for LSI MegaRAID SAS family

    Hi glotzer, Have you tried solutions for "device doesn't show up in profiler" and "contiguous drive enumeration" in FAQ? Does any of these change anything for you? You may also try to combine them if any single solution doesn't change the things. ElStuiterbal , > /tmp/SASMegaRAID.kext successfully loaded (or already loaded). Obviously this means that your kext was loaded :-) Please look at dmesg and Profiler after such successful load. Your dmesg buffer should have similar info messages akin to what glotzer posted. Next comes look at Profiler (Parallel SCSI section) and Disk Utility. You should see at least your controller in Profiler; and volume(s) in both utilities, if you have created any virtual disk in your controller bios. If you're stuck in the middle, try what was suggested to glotzer. Ah, and post things like your dmesg etc here so it will be more easy to figure what's going on. As for kext loading, glotzer made a great explanation. > I will try tomorrow to just install the kext in S/L/E No need, you already successfully loaded the kext ;-) Keep on testing like I described few paragraphs before. > However, could you explain why other kexts work if they are injected by Clover? > However, I would prefer to use Clover to inject the kext, to keep S/L/E as vanilla as possible. Probably because no other non-storage related kext require this: For me, kext injection worked fine prior to Apple introduced this kext validation bullsh*t. Anyway, you should finish manual testing prior to continuing with kext injection.
  9. Driver for LSI MegaRAID SAS family

    > File owner/permissions are incorrect (must be root:wheel, nonwritable by group/other) Please do cp -r /Volumes/EFI/EFI/CLOVER/kexts/10.10/SASMegaRAID.kext /tmp; chown -R root:wheel /tmp/SASMegaRAID.kext; kextutil -v /tmp/SASMegaRAID.kext
  10. Driver for LSI MegaRAID SAS family

    Hi, ElStuiterbal. Do you boot OS X with kext-dev-mode=1 kernel flag? Because you should! If this doesn't help you may also try to manually load it in booted system via 'kextutil -v /path/to/SASMegaRAID.kext'. This should print you what's going wrong.
  11. Driver for LSI MegaRAID SAS family

    flavo, > LSI 8008ELP 39 Can't google info about this card > 8708EM2 Mentioned few posts above your post http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/page-13 Requires fallback to the legacy interrupts (MSI doesn't work with it) by changing plist flag (see FAQ or mentioned posts). Not sure if there's any noticeable performance penalty with this. Instead of raid 0 or raid 0 + OS X raid you could just use an advanced raid level of a decent hardware raid card. However the latest trend for both speed and data safety was usage of a ZFS with RAIDZ. For this you don't need a hardware raid card but you need a good controller without bottlenecks. It could be either a separate pci controller supported by OS X or your mobo controller if it's good enough and has enough hdd connectors. See https://openzfsonosx.org/ project for this. They also have a good forum. You could ask a setup suggestion for your needs there. Also I hope you're more than satisfied with great feedback from jfive. Hi, justroach. > I recently came back to this thread for a new build and noticed that in the README that the IBM ServerRAID M1015 had been crossed out. I've been using one of these cards for a while with good results. I couldn't find a specific post that got the card killed, but... At least: http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/?p=2108649 http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/?p=1908246 If you could write the revision of your card, used firmware etc etc I think it could help people and after getting one more positive report on that card we may consider it a compatible card again > I'd like to give the sleep stuff a shot, but I don't see a Yosemite version with the sleep option available. Could someone post or PM that? I've just used an old kexts on Yosemite. There were no API changes in 10.10, so Mavericks kexts should just work for you too. Here's on how to bypass kext signature checking in Yosemite: http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/page-11?do=findComment&comment=2070470
  12. Driver for LSI MegaRAID SAS family

    Note that at least one person had an issues with RAID-5 setup using H310 card: http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/?p=2009371
  13. Driver for LSI MegaRAID SAS family

    Exactly you need to create a RAID array either from controller's BIOS or in Windows/Linux. (There is currently no capability to create/delete arrays from OS X when using this project But you can do monitoring operations with mfiutil console tool supplied with it) After that you can work with your virtual volumes like with usual HDDs, i.e. doing format, reading, writing, etc from any OS supporting your card. Yes, the one of benefits of a true hardware RAID is that they're OS independent solutions when you have drivers for all OSes you need.
  14. Driver for LSI MegaRAID SAS family

    Depends on a kext and a card. My driver doesn't currently support disk passthrough mode, so yes, OS X we'll see an array only as a single disk with any supported controller. And yes, this means that Parallels should work with such.
  15. Driver for LSI MegaRAID SAS family

    ElStuiterbal, yes this is possible with hardware RAID card and Parallels. Another way is where you find a VM software that could pass logical volume (like software RAID volume, not the underneath physical disks) to the ubuntu in it. Looks like Parallels can't do it such way. In final, I don't know how http://www.softraid.com/ solution works comparing to builtin OS X software RAID, but if it hides actual physical disks from OS X, than it will work even for Parallels. In these two options RAID array management is in the hands of OS X.