pewe1263

So far for my hopes .... can't get the system to boot from the SSD only boot from usb and than select the SSD and it will boot to the SSD but that's not how it should be. What I've noticed as well is that the EFI partition on the SSD is not shown on the desktop when running the clover install package. I've already twice run thru the steps in the post installation but no success so far .... Any tips you might have ?

that was/is the trick, I just had to re-launch clover install package to get that EFI partition back and copied those two files et voila El Capitan is running ... Thank you for helping out, case closed. I hope, I still must do the post install. Happy new year to all of ye.

FYI I've got device id 0166 and revision id 0009 on my running mav whereas in the downloaded E6430 config.plist there are entries for dev/rev 0166 0004 could this cause the "hang" ? TIA, Peter

Following the tip from JakeLo followed the instructions in the linked posts. After a bit of misunderstanding the EFI stuff finally got it working, well the USB boot stick (I used a lexar 64 GB USB 2.0 version) so it boots into Clover V2 3330 then starts the screen with the apple on it (sometimes it goes into a panic but rebooting will convince the booter to continue) but it is at the apple screen at at apps 75% the screen goes blank and stays that way. Did I mention I do have a laptop with just 1344 x 756 resolution. Since there is only a E6430 download for 1600 x 900 resolution could that be the "I can't see anything on screen anymore" problem during the OS X installer ? How can I correct this ?

Thanks, for the tip, corrected my Bios to A12, and Mavericks is still running strong. But trying to upgrade to El Capitan just runs, wants a reboot and ... runs again into Mavericks ... I guess I will have to read some more on boot pack, clover and friends.

Anybody out there succeeded in running el capitan on a e6430 by upgrading from mavericks. Is this advisable ? Or should I start from scratch and try to setup El Capitan completely new ? Any links to successfull guides ? TIA

I gave up on this one, Linux just did exactly what was needed ... the mac mini has to wait ...

Hi There, is there a way to get the Wifi and the SD controller to work on an E6430 ??? My Wifi is reported in MS Windows as: Board = Dell Wireless 1540 802.11a/g/n (2.4GHz/5GHz) Rev 2.01 Chipset = BCM4359 / BCM92057000 In OSX 10.9.2 on the same HW: Broadcom BCM4310 USB Wifi Controller,,,: Name: AirPort Extreme Type: Wi-Fi Controller Driver Installed: No MSI: No Bus: PCI Slot: Slot-2 Vendor ID: 0x14e4 Device ID: 0x4359 Subsystem Vendor ID: 0x1028 Subsystem ID: 0x0014 Revision ID: 0x0000 Link Width: x1 Link Speed: 2.5 GT/s The build-in SD-Card reader: O2Micro OZ600F/OZ900F Integrated MMC/SD Controller: Name: pci1217,8221 Type: MMC/SD Controller Driver Installed: No MSI: No Bus: PCI Slot: Slot-6 Vendor ID: 0x1217 Device ID: 0x8221 Subsystem Vendor ID: 0x1028 Subsystem ID: 0x0534 Revision ID: 0x0005 Link Width: x1 Link Speed: 2.5 GT/s Any tips or ideas or links or just simple drivers ???

finally got my MB exchanged and guess what ... it worked ... however got no internet access only local intranet ??? ... seemed that with the mb a new mac address was coming along and I have my network all filtered by MAC addresses .... Typing this in from my first MellBook is very nice ... Thank you guys for all your help in this quest ... RESOLVED !!!

didn't go ... same failure with just 4 mins to go ... re-applying the fail method ... sorry for that guys ...

sorry for using another method, using the unifail from the other web resource and NOT sorry since it works ... Had to use boot options -x PCIRootUID=1 GraphicsEnabler=Yes during install of OSX 10.9.1 AND during boot from the mSata, this approach ran into a working OSX on the DC3217IYE. A little bit differently settings (like reporting 1.7 GHz and as a Mac something version x,y) but working .... Trying to re-install from the USB using the method taken from this side ... see if works as well with those options ... If successful, I'll try to get EDP on it to run ... tbc ...

Aha a partial succes .... Copied over the mach_kernel from USB boot to mSata root and rebooted .... Well, the mach_kernel message went away and the Apple boot screen was displayed, but just for a fraction of second and started to reboot by itself and promted for enter to continue and then a very brief moment to sow the Apple boot screen etc., etc., .... Actualy no real go .... What makes me wonder, does the BIOS version has a play in this. MH has 0020 and no issues, I have 0040 and a no go. If I look at MH's log there is pretty much no exception reported and mine just can't get enough of it..... Why do I get the hard cases having pretty much no knowledge of the matter and the people who do just get it Working without having issues, at least it looks like it ..... Anyway, does one of you guys have another idea how to get this going .... Much obliged, -PW

sorry, didn't go .... after the fail message waited a bit and booted from the mSata drive but it still came back to use the USB. So powered down, removed the USB and booted again but the system found no bootable device. So fired up with GRUB 2, listed all the devices and partitions and it included in the list the partition of the mSata, multiple. Booted via the USB again and installed Chameleon via the myHack tool. Now the mSata booted but didn't get far ... started to complain about /mach_kernel not found and repeated that every time I hit a key ... too bad ... but was worth a shot. Oh, by the way did insert a Intel WiFi + BT card, no effects noted sofar (Dual band wireless AC 7260 2x2 AC+BT) This is a basic 10.8.5 install ... no extras at all Next tip for me to try ??

Hi MH, well, that's what the OSX Installer is reporting. I've saved the OSX Installer packages to my network so I can easily use the dmg(s) over and over again. Now SL 10.6.3 on DVD crashes immediately, so I guess that version won't work. Of course I tried the latest OSX I've got and that's 10.9.1. That seems to install but reports with only 5 or 4 minutes to go a nice OSX Install failed. I've tried multiple times but all the same. After have read through your log, I noticed it was performed using 10.8. So I purchased ML as well via the apple store, got only 10.8.5. So the following I performed from my E6430 OSX 10.9.1: Got a new USB stick (8GB) Lauched myHack 3.3.1 Create OSX 10.8 install USB using the saved ML DMG Waited for the process to complete and ejected the USB Got over to my DC3217IYE Booted from the USB Stick Still got the msg 128MB not supported for the HD4000, continued that, no special boot options entered. At the language screen selected the english one (the first in the list) Got the OSX Continue to Install screen Used DiskUtility to erase and partition the mSata for GUID and took the journal option it has to be noted that at the first aid screen the verify options are greyed out After completion back to the OSX Install screen and continued What surprised me as well is, that when ressing the customized install, an complete empty window is displayed. After agreement etc, the installation continued counting down from 21 minutes, it feels like it takes more though. With 5 minutes to go the screen turns completely white and the mouse freezes ??? Never had that before. Just to see if keyboard reacts, I hit num lock and the install screen came back and the install continued .... .... for a little while and then the window with OSX Install Failed with some text that I should contact the SW provider or try again .... .... don't know if apple would play along though .... .... tried again and the white screen came earlier now with ten minutes to go but the fail came at the same 5 or 4 minutes to go ... Powered off the DC3217IYE by using the installer option, that worked quit good and fast, happened within seconds. Got back to my Mav E6430 and installed the generic extras. After that went through back to the DC3217IYE and tried again ... .... booting the usb, erase & partitioned the mSata, installed OSX .... same behavior failed at 4 minutes to go ... Back to the E6430 again and installed the 10.8. boot pack extras as downloaded from the web. Booted the DC3217IYE again. The nice OSX Latitude boot screen came, counting down in seconds, no option taken, verbose mode executed, but I didn't even get to the OSX Install, panic crash .... that's the same, at least the behavior, as with the 10.9.1 version. .... getting rather dissappointed in OSX ... this is almost as worse as the seatlle based OS .... Talking about it and to rule out some real HW flaws and looking for at least some succes .... I choose to tyr my luck with the other OS 8.1 After killing all partitions during that installation, it just installed and after installation of JRiver MCE it directly performed as expected. At least that worked .... so I could sleep with the feeling that if al fails there is still an alternative to OSX .... although, not really .... What can I provide or perform myself to let you guys have a closer look at the problem with this DC3217IYE ???? @MH, Can you let me know your BIOS settings so I can match ??? Anything I can do to help in this quest ??? Thanks anyway for your time and thoughts !!!! Greetings, -PW

Just installed the generic extra on the USB using myHack, but crashes as well. Pretty much at the same spot breaks off the installation after the language selection by showing the installation screen where the log can be viewed, saved, and various different options. Of which the disk manager is one and this time my mSata is properly reported as a Kingston SMS200S360G with a Total of 59GB. But it is here were the install stops ..... Bummer .... Any further tips or hints how to solve this ??? Would be greatly apriciated !!!

Hi MH, can you let me know the HW you use for the internal mSata ? I think my 8GB reported kingston 1600 CL11 RAM will not be the cause for this unexpected behavior. Do you use a WLAN/BT card, if so can let me know what you use as well. Since in my boot log, one of the first non-expected messages is concerning some BT (I assume it stands for bluetooth) issue. Furthermore I figured out where the SandForce mentioned device in my list is for. It's for the mSata having a SandForce chip, but it beats me why DiskUtility can't partition it at all. All, or pretty much all fields in the partition pane are greyed out ????? And the reported size of 33MB is a little bit surprising ???? Thanks for your time and help in this. Cheers, -PW

Used myHack to make just the OSX MAV 10.9.1 boot USB. Didn't even bother the restart myHack to put the generic extras on just left it as is. Went over to my little DC3217IYE and started from the USB. I still got the message about that 128 MB is not valid for a HD4000 only 96, 64 or 32 and had to press some key to continue ... so I did. Now the nice language picker screen came and after selecting english for a change ... it gave me some log screen and that the installation couldn't be finished or so. Well I saved the log and attached for you hopefully can read more out of it since for me it could be almost chinese that's something I can't deceiver as well. In the process I found out that my internal Kingston SMS200S3/60G SSD was kind a gone, only 33 MB total space (this is not a typo) listed in the DiskUtility and not partitions and have a very strange name like Sand-something with a magical number behind it between curly brackets. This is brand new hw, just a couple of days old. The SSD should be 60 GB in size .... Any tips are more than welcome ... Installer Log 26-Feb-2014.txt

Hi MH, thank you for mentioning IT does work .... BIOS is the 0040 of 03/25/2013, the system is mfged november 2013. got no idea why it doesn't work for me .... that with SL boot didn't work as well some direct panic message. I'll make a new generic USB MAV boot USB and report back ....

Well, I used my E6430 boot usb and got stuck while the usb drive was corrupt as noted on screen. What was noted that the apply boot screen started pretty much directly and the circling thing went on for a while and the top of the apple got a nice square with a forbidden sign in it, like in traffic a red circle with a kind of backslash through it. What surprised me as well was that when booting in verbose mode all the reported message were displayed a lot faster than with NUC USB boot, exceptionally faster ... although the USB drives are both 2.0 as is the NUC's USB port .... Next try is performing a SL 10.6.3 install see if that works ...

copied over the kext and performed a quick myfix. Tried it again on the DC3217IYE and .... well at least I got a different version stamp on the kext when getting the panic ..... See screen for hopefully readable result: Strange that it doesn't get booted at least. I simply followed the EDP instructions from the EDP pages when making a boot USB. 1. Fire up my E6430, yep the one with the nasty screen 2. Used myHack 3.3.1 to make an install USB 3. Started myHack again to install my own extras pointing to the downloaded bootpack from the EDP compatibility page 4. Put the USB in the NUC and booted .... However my NUC hardware is from 23 November, 2013. Maybe Intel changed something after all ..... But still no luck ... yet ... I think I'm gonna try just booting from E6430 USB and see how far it gets ...

I'm very sorry but I've got no idea how to make a patched kext ??

Just got me a nice Intel NUC DC3217IYE and found your bootpack. Made a brand new boot USB for 10.9.1 and applied your bootpack by second run of myHack 3.3.1 and installed the extras. Booting from that USB for the NUC got me a message that the BIOS setting for the video should be 96, 64, 32 MB whereas mine was set to it lowest possible value of 128 MB, can't go lower in the NUC's BIOS. Just below the message it mentioned to press a key to continue, so I did ... With the boot package it ended in a panic and some errors .... stopped at System uptime in nanaseconds and some number ... Made a second USB Boot for now 10.8.5 and without the boot pack. Same 128 MB video message but after hitting a key the white apple screen came with the circling wheel and after that the usual stuff as normal when you install OSX. Format the harddrive and installed on the harddrive. The system continued very slowly with installing whatever it needs to install but at another couple of minutes to go it ran into some unexpected error and the whole install failed. So I installed the extras folder again this time for 10.8 of course and did the exercise again. Now it gave an OSX Latitude boot screen with a slowly decreasing time to put in any options. Let that run through and the system continued with a verbose boot ending in the below picture, hope you can read it. For what it's worth, no network connected. Just power, usb, big telly through HDMI connector. Internals: RAM = Kingston KVR16S11/8 = 8GB 1600 CL11 SODIMM SSD = Kingston SMS200S3/60G = 60GB mSata Hope one of you can help !!!!!

sorry .... not an option .... tops I could check the faulty laptop for bad connections or the likes but nothing more ...

however windows does not seem to have a problem, but osx does. Strange though Snow Leopard did work OK, no artifacts. Only with the mavericks updates came the artifacts .... maybe a stupid timing issue caused by a not perfectly fitted connection located beneath the keyboard 'cause every keystroke turns into an artifact change as does f.e. software loading .... like you have a bad shielded cable laying nearby your microwave .... so maybe it is a condensator not doing it's decoupling from whatever and causes some interferance .... who knows, with these frequencies going thru the mainboard it's easy to generate some very hard to detect interferences, at least the component causing it .....

oui, used the laptop internal lcd of 1366*768 14" and on battery with wifi off and all but the internal DVD attached. We match the bios version and all bios settings.