Jump to content

glotzer

Members
  • Content count

    3
  • Joined

  • Last visited

About glotzer

  • Rank
    InsanelyMac Protégé
  1. Driver for LSI MegaRAID SAS family

    Hi dukzcry, ElStuiterbal always wondered about that one, too and thanks to dukzcry's hint, this makes perfectly sense now - good one, me just didn't see the forest because of all those trees. @topic: 1.) booted with the "uncontiguous enumeration" kext --> device (adapter card) didn't even show up in profiler 2.) changed in Info.plist "PreferMSI" flag to false --> device (adapter card) is shown in profiler, still not showing any HDD devices or adapter card in "Disk Utility.app" noticable: If I connect an old 2.5 SATA 100GB HDD and configure it as RAID0 (single drive) --> adapter card shows up in profiler and all partitions on disk get recognized by "Disk Utility.app" If I configure those 2 WD BLACK drives the same way --> adapter card shows up in profiler, again nothing in "Disk Utility.app" (same as 2. above basically) suspicion: I'm running a dedicated GPU in the PCIe 16x slot. Using the (only remaining) slot with the PERC 6/i (needing PCIe 8x), wiring on the board might not support faster connection than PCIe 4x. next try for solution: Removing the dedicated GPU (thus loosing those fancy mini-display ports for my monitors) and moving the PERC 6/i in the no-occupied-by-GPU PCIe slot. Thought I could get around looking for cables/adapters in the basement - but hey, spring-time-clean-up comin' up anyway. question: 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 (meaning: not getting full SATA-speed - as transfer rate is again something different, if me reading through your errata on the unsafe settings kext got that right) will try to remove the dedicated GPU and report back with results - just give me a few days. Cheers glotzer
  2. Driver for LSI MegaRAID SAS family

    Hi ElStuiterbal, just a few points (always good to know) 1.) OSX (I think with 10.9) started to sign kext-files, so only "valid" drivers would be loaded during startup. That's why you should use the kernel-argument "kext-dev-mode=1" - because the kernel being in "developer-mode" will load kext-files even without a valid signature (which you will only get from Apple-certified software, I'd guess) 2.) OSX (I think with 10.7 or 10.8) started to use kernel-cache files. Essentially these files contain all your hardware's needs in regards to drivers (eg. kexts). Try to picture it this way: if you don't have certain kind of hardware in your box, there is no need to for the OS to provide kexts for (meaning loading the stuff into memory would be useless, because drivers will never be needed) - to make use of this concept, OSX builds a kernel-cache file with all drivers included to start up your individual hardware. That being said, consider this: a.) I'd use some kind of tool (kext-wizard always did me good) to "install" (which is just plain copy & chmod & chown "some.kext" into /S/L/E) b.) I'd use the same tool to repair permissions and REBUILD KERNEL CACHE (!!!) so OSX will pick up the new kext during next boot (this is essentially just some command-line-kung-fu too, but the novice is better off with some simple tool here) 3.) (more or less optional info, because your problem is explained / should be solvable with the above) OSX (and every other OS like Linux and Windows) is using FAT-formated EFI-partitions when GPT-formated. So technically, since FAT don't know about permissions and such (because it's not build into the filesystem like in HFS+, ext4, NTFS, etc.pp.), setting permissions on the kext on your EFI-partition is more or less useless (if you'r not running some kind of exotic boot-partition setup where you try to boot off of something other than a FAT partition) Placing the kext on your main HDD in "/System/Library/Extensions" you'd need to set permissions on the kext (e.g. "chown -Rv root:wheel ./some.kext && chmod 755 -Rv ./some.kext" - replace some.kext with your needs when in /S/L/E) and then REBUILD KERNEL CACHE (which I don't remember the command now - google should help you) to get the kext loaded on next startup. (loading kexts without booting is possible too, read through this thread, it's written down somewhere) hope to clear things up a little bit - happy hackintosh'ing Cheers glotzer
  3. Driver for LSI MegaRAID SAS family

    Hi dukzcry, first of all: thanks a lot for your work and effort put into this project - it is very much appreciated!!! and also a thanks to the rest of this community around here - been reading for years, never had to ask a question, thanks to the brave people asking for support here before I came to the hackintosh playground. Now I'm stuck with setting up a PERC 6/i Integrated on Yosemite 10.10.3 To be honest, this is the first time I'm messing around with raid-devices und such, so there might be a fundamental lack of knowledge regarding this subject on my side. Please forgive me, as I'm here to learn. I managed to get my hands on a PERC 6/i Integrated, which I prepared with some non-electrical tape (as mentioned in the first post - to get it to boot). I also managed to flash the bios of the card to the latest DELL version of the firmware (which can be found here: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=F96NR) After installing via the installer package provided by the link in the first post, I can successfully boot and the controller seems to be recognized: sudo dmesg | grep SAS [SASMegaRAID] [Helper] MSI IR line: 1 [SASMegaRAID] DMA: 64-bit, max commands: 1008, max SGE count: 33 [SASMegaRAID] 3 of PDs present [SASMegaRAID] Enabled options: Physical Drive Coercion Mode Auto Rebuild Battery Warning [SASMegaRAID] BBU type: BBU, status good, 99% charged running the mfiutil I get the following output: sudo mfiutil show adapter mfi0 Adapter: Product Name: PERC 6/i Integrated Serial Number: 1122334455667788 Firmware: 6.3.3.0002 RAID Levels: JBOD, RAID0, RAID1, RAID5, RAID6, RAID10, RAID50 Battery Backup: present NVRAM: 32K Onboard Memory: 256M Minimum Stripe: 8K Maximum Stripe: 1M Using the <Ctrl-R> utility during POST I configured one Disk-Vol-Group with a Virtual Disk being made up of two WD Black 2 TB drives in RAID0 mode. mfiutil seems to display that configuration correctly: sudo mfiutil show config mfi0 Configuration: 1 arrays, 1 volumes, 0 spares array 0 of 2 drives: drive 0 ( 1863G) ONLINE <WDC WD2003FZEX-0 1A01 serial=WD-WMC5C0D3R091> SATA drive 1 ( 1863G) ONLINE <WDC WD2003FZEX-0 1A01 serial=WD-WMC5C0D126J9> SATA volume mfid0 (3725G) RAID-0 64K OPTIMAL spans: array 0 this is the point where I get stuck in the setup process. OSx DiskUtil doesn't show the PERC 6/i controller, so I have no way to access the disks via the GUI. as I said before, this is the first time myself is messing with a RAID-setup. I have the feeling I'm missing something fundamental at this point. Unfortunately I don't even find the right phrases to feed google with. what am I missing here? is there any more information I can provide to solve this issue? as for my hardware-setup, I'm running the PERC 6/i on a Gigabyte Z77-DS3H booting via Osmozis Firmware any hints and help leading in the right direction would be much appreciated. thanks folks - and again big thumbs up, dukzcry cheers glotzer
×