Hi everyone, I managed to create a Clover Legacy UEFI bootloader USB key with a patched DSDT and SSDT. It seems to be running just fine right now (as I am typing this). On the actual system volume, I am booting with Chameleon, so I am using the USB to test. I have the system running on a 2302 Patched Bios, and power management seems to be working as far as the Intel Power Gadget is showing me. Essentially, everything is working except for audio (no need, I have a wireless USB headset I use for that anyways).
I am having trouble trying to get it to work with just a UEFI bootloader, and not a legacy one. I would like to go to full UEFI mode if possible to streamline future updates and whatnot, and just to generally have a cleaner more vanilla install of the entire system. Whenever I boot using the Legacy USB i get a 'boot' message, then it shows '5' (that is the resolution profile it is selecting), and then it says 'welcome to clover' and proceeds to show the disk launcher screen where I can select my volume to boot from. Whenever I boot using the UEFI USB i get no message at all, it goes straight to a black screen with a FLASHING cursor on the top left.
I proceeded to copy CLOVERX64.EFI to the root of the EFI volume and rename it to SHELLX64.EFI as instructed by some guides on this specific mobo. When booting using that, I get a black screen with a SOLID cursor on the top left (and what seems like an odd resolution that it is being displayed at, as well). It never progresses from that point, and does not show the volume selection menu. I was wondering if it is at all possible to get the Asus P8P67 Deluxe Rev B3.0 @ 2302 patched bios (confirmed patched bios is working) with UEFI only. The 2302 bios does not have CSM or any option to do UEFI/Legacy Hybrid or UEFI only booting- so I cannot turn those off/change them. As far as I know you only have to install clover on your disk (efi), put all the extra kexts, drivers, dsdt and ssdt in the respective folders.
Random-things: Boot.efi X64 Patch For Mac Pro
Then boot to an efi shell find the folder in fsx where CLOVERX64.efi resides (not the one in the usb) then do: bcfg boot dump (return) bcfg boot add 0 CLOVERX64.efi 'osx' (return). Remove the usb pen and restart the pc. Install clover (efi) on the usb too. You are not going anywhere with a legacy pen. P8P67 is EFI capable. And to boot in the uefi pen simply hit F8 at boot and select uefi:yourpen. What do you mean by 'you are not going anywhere with a legacy pen'?
As I type this post, I currently booted from the legacy clover pen and I am in 10.10 right now, circumventing Chameleon what i was trying to explain was that 'hit f8 at boot and select uefi: yourpen' does not work. That is exactly what I'm doing.
It tries to read from the EFI partition on the USB key, but does not work. If I attempt to do it by selecting the legacy 'USB' partition that has an 'EFI' folder on it, it gets me here. Into OSX and allows me to use the system.
I'll try installing it onto the harddrive and see where that takes me. At least if it doesn't boot I can use this usb key to get back in here and configure stuff. EDIT: attempted to use 4.1.2 of this guide here: and it didn't add Clover to the bootloader and did not allow me to select the UEFI: harddrive partition that loads the mac drive that i have yosemite installed on. The P8P67 UEFI bios does not have a UEFI add/remove dialog where I can add things to the UEFI boot options. You have to install clover in the efi in the usb.
If it's not booting to clover as uefi then simply you haven't a uefi pen. Dude, i did that.
I tried it with 3 usb keys. That is why I am here asking questions. Do you understand the nature of a web community/forum? I don't think you're reading my posts. I followed the instructions on different guides. They all result in the same thing when running as UEFI. It gets stuck or does not load at all.
The bios even lists it as UEFI: usbkeyname in the boot options menu, and you're telling me i don't have a UEFI pen? It simply does not boot.
I am wondering how to get it to boot as a UEFI pen rather than a Legacy install. Thank you for your input, but your posts are not helpful. Ok but you said that the EFI folder is in a legacy partition. How did you format the pen?
I followed the instructions on the Clover USB boot guide. You format the pen creating a GUID partition table. Then in the clover installer, you select options to install in the ESP as UEFI, or install as Legacy (which creates an EFI folder in the USB partition on the drive instead of the EFI (ESP) partition). If I choose to create a drive and install Clover on the EFI partition, it does not boot. If I choose to create a drive and install Clover on the USB partiiton in an EFI folder, it does boot.
I am trying to boot it using the UEFI partition. Aside from all that, I am in the midst of repairing my Macintosh HD EFI partition and will be trying to do this via EFI partition on the HDD, as it seems to be corrupt. But that does not mean the EFI partition on the USB key should not boot.
It should still function. EDIT: repaired my EFI partition on my main harddrive that has Macintosh HD partition. Asus UEFI still won't pick up any of the files in there. Is there a way to remove all the UEFI entries and ask the ASUS bios to repopulate them all from scratch? So audio definitely does not work, as indicated.
It would be nice to say it is working- but to be honest I don't need it. I don't use HDMI or analog output on this computer. I have a Wireless Headset that I use all the time. I am attaching my boot log. If there is anything that looks out of the ordinary, please someone let me know.
For some reason, using ssdtPRgen and iMac12,2 SMBios Profile for the i2600k with the proper board ID, the SSDT is loaded, but the computer fails to boot. It hangs up on some apple80211receiver call or something, and then it doesnt even show the kernel panic, it just reboots.
I got it to boot once by changing some random things in clover options, but I only had P-states 16 and 38 within AppleIntelInfo.kext log. It would not go out of the 1600mhz state at all, so basically the 3800mhz Turbo state was non functional. With the iMac13,2 SMBios Profile, it boots extremely fast.
And it has 21 P-states. From 16, all the way up to 34, and an additional 35, 36, 37, 38 for Turbo mode. It's only missing P-state 17. And they are verified working within Intel Power Gadget app as well. But it works amazing, even with/without SSDT.
Everything works. Going to do some more testing and post Zip soon. Clover r4799 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation. Tested with unlocked Workstation 15 running OSX 10.9 -10.14 guest in Windows X64 host. Installation 1.
Download and unzip 'EFICloverr4799 for VMware.zip'. Mount Clover-v2.4k-4799-X64 by double clicking on it. Mount your VM's EFI System Partition eg in terminal sudo diskutil mount disk0s1 3. Copy EFI folder from step 1 into the EFI partition 4.
Shutdown the VM, add bios.bootDelay = '3000' to your VM's vmx file 5. Reboot your VM, press to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu. Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
Apologies for the lack of information (and for posting in the wrong place), but I can't even boot into Clover so screenshots of verbose mode aren't even possible. I've been running the beta of 10.14.2 for sometime (-using this excellent guide ) without any issues. When I tried to apply the new update for 10.14.2, my pc downloaded the update, shutdown but applied some updates then rebooted into a blank screen.
I've tried several things since then. Specifically:. Booting from the installation USB created using the above guide - same blank screen. Booting from an external HDD - successful launch of OS. From here I have tried different versions of Clover including the one on my HDD r4644 (all have been unsuccessful). I have also tried different memory management options osxaptiofix (1, 2 & 3) The only other information I can provide is in the screenshots below (including a brief of my drive configuration) Please let me know if and how I can get more information to help resolve the issue, or if I have to rebuild from scratch. Many thanks in advance.
Hi all, I hope someone can help me as I am struggling with this bloody installation.
As no one can help I'll try it a different way I've loaded up VirtualBox on the laptop and funnily enough I've not had much luck here either. Odd, but I don't even get through the install process. My desktop PC, although not perfect, does run OSX okay on VirtualBox so I'm seeing what happens if I copy the pre-made, pre-patched virtual machine over to the laptop. Would anyone care to rate my chances of 1) getting it running 2) transferring the virtual machine data to a real partition and dropping the need for VirtualBox Regards, Andy p.s.
Interestingly, I had a similar problem installing OSX on VirtualBox where it stalled after 'DSMOS has arrived' but this time a network card was mentioned as loaded and rebooting with 'GraphicsEnabler=Yes' did the trick. Step 2: Trying Bootloaders Again, after experimenting with various bootloaders, url='(basically Chameleon) seemed the most reliable. Others tended to need too many switches which gets a little boring after a few dozen install attempts. Tip: busratio=19 for i3-380M (if needed by your loader) Step 3: Retail Install Tip for modern machines: don't waste time with 10.6.0 and start with 10.6.3 retail DVD Took me about 6 installs to figure that one out. 10.6.3.seemed. to work much better but this time the webcam was broken, such a loss QQ Step 4: Combo Update Now the 10.6.7 combo patch went fine.
So on to url='This one had me stumped for a while: KP after combo/url='reboot due to Apple's CPU power management. Forgot to rebuild the caches. Although the NullCPUpowermanagement kext was in there the cache didn't know. Step 5: Booting with out url='CD This is where I'm up to.
I selected the 'easy' option in url='as I really have no idea about hardware in relation to OSX. Booting seems to stall half way. Verbose option reveals the hang is after 'DSMOS has arrived' which sorta points to some issue with graphics or networking maybe? I don't get any errors or warning messages up that point which is almost too perfect!
Tried -x option to no avail. Also tried GraphicsEnabler=Yes and No.
Single User at least got to a command line prompt but the keyboard was dead. Going back to a boot CD pretty much gave the same result albeit with warnings about the kexts from the boot CD overriding the ones attempting to load from the internal hard drive. I've noticed after a minute or so there is some drive activity but it's still stuck. Step 6: Give up?
Am I flogging a dead horse here or is there a chance this could work? I don't expect to get everything working perfectly but personally I would like to get it at least going with 10.6.7 booting from the internal drive without too many clever switches. Should I start looking into DSDT? Looks complicated. Is some piece of my hardware stalling 10.6.7? Like it really hates the Intel HD graphics? Some pointers would be appreciated Best Regards, Andy Hi Andy, I was trying to find out what motherboard you had.
Sometimes you can find Hackintosh support for the devices on the mobo rather than the computer model. Maybe your notebook is too new, I didn't find any howtos from people who've installed Hackintosh onto your computer. Hackintosh is very picky about the hardware it will support, basically what Apple used and supported with some exceptions.
I think you did well to get to 10.6.7 and it booted ok. I think the installation is rather generic and uses safe mode, -x drivers. That leaves you venturing into url='probably not knowing what you should choose. If after MB, you got kernel panic, KP, the likely cause is you installed the wrong kexts. It's possible to install conflicting kexts, for instance voodoohda.kext and alc889 used on my board. Try looking up your devices, like your lan/internet stuff, on google, +hackintosh Intel 82577LC Broadcom BCM4313 WiFi AppleIntelE1000e.kext 32/64 for 10.6 & 10.5.
This is based on Intel Wired Ethernet for Linux ( e1000.sourceforge.net ). As it uses ( almost as is ) Linux driver's source code, the license is GPL. The original one was based on 1.1.2 and 82566mm OSX driver ( 82566mm-osx-driver.googlecode.com ), however, I removed 82566mm stuff in 1.2.8. The base Linux driver is e100e-1.2.10 and can with Intel PCI Express ethernet chips like 82578 used with P55 chipset. ( I tested 82573 and 82578 only as I do not have other NICs. ) - I think the two most important things are graphics and internet. Sometimes you can get a hint about the right video driver by looking in Windows Device Manager.
The DSDT.aml is handy because it fixes some common problems. Most people get their DSDT from a database and there is also MaLd0n's DSDT auto-patcher. It is kind of hard to start off trying to generate a 'fixed' DSDT.aml by yourself. Kexts in /Extra/Extensions are read first, they supercede kexts in /System/Library/Extensions - the kexts in /S/L/E are often overwritten in an Update (10.6.7).
Another important file is com.apple.Boot.plist which help make devices work. I would add kexts rather slowly to your system, so you can identify which kext caused a KP. Probably the hardest device to get to work will be your video card. One large problem kext was sleepenabler.kext and the fix was booting with the flag pmVersion=0 but you seem to have avoided that. The -v switch is for verbose and shows where the panic occurs in the loading process. You need fakesmc.
For the update to 10.6.7, I had to use iousbfamily.kext rollback to 10.6.2 or lose peripheral usb devices like drives. Thanx for the reply! You may be on to something with the network drivers.
I did mention the 'DSMOS has arrived' stall and when run native no mention of my internal network card was made. Unlike when run under VirtualBox. I shall investigate this avenue further but I have a wedding to go to this weekend so not much time Refering to the motherboard: laptops are always tricky, especially so trying to shoe-horn OSX on but I guess it's Toshiba's take on the Intel HM55 chipset.
I get that my best option is going down the DSDT route but there are no mentions I can find of anyone even attempting to load OSX on the R630 let along kicking out a premade DSDT file Anyhoo, given the relative newness of this particular model - R630-156 - let me try and drum up some interest with a comparison to the 13' Macbook Pro. Thanx for the reply! You may be on to something with the network drivers. I did mention the 'DSMOS has arrived' stall and when run native no mention of my internal network card was made. Unlike when run under VirtualBox.
I shall investigate this avenue further but I have a wedding to go to this weekend so not much time Refering to the motherboard: laptops are always tricky, especially so trying to shoe-horn OSX on but I guess it's Toshiba's take on the Intel HM55 chipset. I get that my best option is going down the DSDT route but there are no mentions I can find of anyone even attempting to load OSX on the R630 let along kicking out a premade DSDT file Anyhoo, given the relative newness of this particular model - R630-156 - let me try and drum up some interest with a comparison to the 13' Macbook Pro.
I've played about enough with VirtualBox to learn a little more about OSX (I hope!) Back to installing on my laptop. I grabbed the latest modCD, now I knew a bit more about it, and tried to install the 10.6.3 Retail DVD again.
I did the 10.6.7 combo + url='but no luck on rebooting. Still hangs sometime between 'DSMOS has arrived' and the GUI starting. This time however, I managed to boot up using modCD and it was nice to see 10.6.7 in the 'About' box plus the correct CPU ID for my Core i3 So. I think I have two routes now: modify my Chameleon to mimic what modCD is doing to and/or get stuck into the black art of DSDT! I did try the network driver you mentioned and it shows up nicely on screen as AppleIntelE1000e with its MAC address, so thanks for that tip. I still think my problems are graphics related.
Given that the current Macbook Pros have Intel HD Graphics and the sleight-of-hand modCD does to guarantee some sort of GUI appears Probably a case of getting OSX to recognise my onboard graphics as something it likes. Back to DSDT it seems. Regards, Andy. I've played about enough with VirtualBox to learn a little more about OSX (I hope!) Back to installing on my laptop. I grabbed the latest modCD, now I knew a bit more about it, and tried to install the 10.6.3 Retail DVD again.
I did the 10.6.7 combo + url='but no luck on rebooting. Still hangs sometime between 'DSMOS has arrived' and the GUI starting. This time however, I managed to boot up using modCD and it was nice to see 10.6.7 in the 'About' box plus the correct CPU ID for my Core i3 So. I think I have two routes now: modify my Chameleon to mimic what modCD is doing to and/or get stuck into the black art of DSDT! I did try the network driver you mentioned and it shows up nicely on screen as AppleIntelE1000e with its MAC address, so thanks for that tip. I still think my problems are graphics related. Given that the current Macbook Pros have Intel HD Graphics and the sleight-of-hand modCD does to guarantee some sort of GUI appears Probably a case of getting OSX to recognize my onboard graphics as something it likes.
Back to DSDT it seems. Regards, Andy For Hackinstosh installs, graphics, audio and ethernet are very usually todo things after the initial installation. I think a generic video driver is used, nothing specific.x It's like when you install Windows, there is a generic video driver used to get you through the install. But then to get your devices to work, you have to usually use the dvd of drivers that came with the mobo. If you have onboard graphics, then that may be enough. But if you have a dedicated graphics card, then you need the install cd that came with it, or go to the manufacturer and download it.
So getting it to boot up is something, but not all that much because the kexts/drivers that deliver the full functionality to your devices haven't yet been installed. None of those boot cds will have the video driver you need on it. url='the kext install program, may have it. Of course you need to get to a completed boot screen to install the drivers still needed. And not all boot cds are created equal. But that's just to get one by, not the real McCoy Maybe you knew all this, but you weren't outlining your plan to agree with it when you wrote.
'modify my Chameleon to mimic what modCD is doing'. I think that will at most get you to the point where you can install more needed specific kexts. Chameleon, the bootloader, is found on url='cds. url='the default universal has some support for i3; url='Legacy For Unsupported CPUs & GPUs The new kexts come from url='when using the url='+ MB method. But the ModCD, rug sweeps, imo, ' Used the kernel blacklist code to disable graphics kexts when using the CD.
This way there won’t be issues anymore.' So this will boot up, but if you mimic it, you have no graphics kext and no full functionality for your video card. Well, if you can't find a driver for your Intel GMA, half a cake is better than letting them eat none, m.m. 'This is a new version of the modified Chameleon 2 RC4 bootloader, to get (wide) native resolution on most Intel GMA.
I tried to solve the common problems of the previous release. The behaviour of the bootloader has been modified as follows: 1. The desired resolution is read from “Graphics Mode” key in com.apple.Boot.plist 2. If the key is not present, the bootloader reads the default resolution of your LCD/Monitor from EDID 3. The first entry of vesa bios modetable is patched with the new resolution, so OSX can find it and boot correctly.The major improvement is that now you can specify your custom wide resolution. For example, on my Inspiron 1545, I was able to get 1280×720 instead of 1366×768. Obviously, the resolution must be supported by your monitor and graphics card, so first ensure of that using windows or linux.
The string format must be in the classical form example parameters: Graphics Mode 1280x720x32 Don’t forget to check for the existence of com.apple.Boot.plist in /Extra ' - Perhaps this will help with the resolution, but your transparency will suffer until the correct kext is discovered. QE = Quartz Extreme ^^^^ CI = Core Image This deviato idea is untested by me. Have you tried any graphics.kext yet? Chameleon is a good bootloader for Hackintosh because it reads /Extra and loads com.apple.Boot.plist (a config file) found in /Extra, and I don't think other bootloaders do. I'm currently looking at the DSDT for my R630. MaLd0n was kind enough to fix the errors in the DSDT section.
Unfortunately, this leads to another problem: Kernel Panic for the AppleACPIPlatform just after the kernel is loaded Seems to be a lot of mentions of this but I haven't turned up any clear solutions. A few people have had success dropping the new kext (1.3.5) to one from 10.6.3 (1.3.2) but that didn't work for me. Regards, Andy Play around with enabling or disabling one of these two kexts. You did enable HPET in Bios? Before you mentioned: AppleIntelCPUPowerManagement NullCPUpowermanagement Null.kext may contribute to the Kernel Panic AppleACPIPlatform I think you resolved this by removing NullCPUpowermanagement which surprised me a bit. It seems that your new DSDT.aml is rendering some kext superflous or even conflicting in your power management.
The next link is old but says some interesting things about the kexts that go into /Extra/Extensions. Mmm, no good Installed in that order and removed the Intel HD kexts but I still get the same AppleIntelCPUPowerManagement KP. I also tried adding the NullCPUPowerManagement kext back in and got KP on AppleACPIPlatform again. Trying some random things, I pulled the DSDT.dml file and added in the Extensions.mkext from modCD. And it booted!
Which is a first for my system without using some sort of boot CD. Obviously there's some magic involved in nawcom's Extensions (blacklisting of kexts is an obvious example) so I've just tried with a minimum FakeSMC and NullCPUPowerManagement (as I'm not using the DSDT.dml).
But no keyboard or mouse, just put that Voodoo PS/2 stuff back in. It boots betterer! Okay, some testing:. machkernel x32 boots fine. machkernel x64 KPs on ACPI like with the DSDT.aml.
nawcom's legacykernel for 10.7.0 is also fine as x32. legacykernel x64 doesn't KP but does stall waiting around for AppleIntelCPUPowerManagement So, 3 possibilities here:. I'm a noob and didn't try the arch=i386 a lot earlier (pure ignorance on my part). Killing the Intel HD kexts helped a lot.
The new Lion version of Chameleon helped (kewl new theme, thanx MaLd0n!) Or possibly a combination of all three The journey continues. Regards, Andy. Mmm, no good Installed in that order and removed the Intel HD kexts but I still get the same AppleIntelCPUPowerManagement KP. I also tried adding the NullCPUPowerManagement kext back in and got KP on AppleACPIPlatform again.
Trying some random things, I pulled the DSDT.dml file and added in the Extensions.mkext from modCD. And it booted!
Which is a first for my system without using some sort of boot CD. Obviously there's some magic involved in nawcom's Extensions (blacklisting of kexts is an obvious example) so I've just tried with a minimum FakeSMC and NullCPUPowerManagement (as I'm not using the DSDT.dml). But no keyboard or mouse, just put that Voodoo PS/2 stuff back in.
It boots betterer! Okay, some testing:. machkernel x32 boots fine. machkernel x64 KPs on ACPI like with the DSDT.aml. nawcom's legacykernel for 10.7.0 is also fine as x32.
legacykernel x64 doesn't KP but does stall waiting around for AppleIntelCPUPowerManagement So, 3 possibilities here:. I'm a noob and didn't try the arch=i386 a lot earlier (pure ignorance on my part). Killing the Intel HD kexts helped a lot. The new Lion version of Chameleon helped (kewl new theme, thanx MaLd0n!) Or possibly a combination of all three The journey continues.
Regards, Andy It sounds like you're ahead going down the homestretch, going to the whip. Chameleon reads /Extra/com.apple.Boot.plist and loads it during bootup.
This is what MaLd0n sent you, GenerateCStates Yes GeneratePStates Yes Kernel machkernel Kernel Flags arch=i386 arch=x8664 is correct for x64, I made a mistake once with just x64. Here is another c.a.B.plist, although on my system, it's empty. /Library/Preferences/SystemConfiguration/com.apple.Boot.plist Here are various notes/methods about getting your audio device to work: - alc269: VoodooHDA (32/64 bits), also could use LegacyAppleHDA - Audio HDA ALC269 Yes VoodooHDA 2.72, then replace the kext with the latest patched VoodooHDA.kext for ALC269 from KEXTS.C.M. (Internal speakers, Internal Mic and Analog I/O all work) - Audio Realtek ALC269 Yes Patched AppleHDA with DSDT section HDEF - Audio: Realtek ALC269 (works with VoodooHDA, but remove AppleHDA) - I have ALC889 and a dedicated kext, so I had to remove voodoohda.kext in order to get it to work. Perhaps your audio is working out of the box.
Very strange but no problem I read the link above, and this part made me think of Nawcom's modCD. 'Unfortunately, a 64-bit processor alone doesn’t suffice. Out of the box, boot.efi will not boot K64 even if you have a 64-bit processor and explicitly request K64 if at least one of the following is true. The machine has 32-bit EFI. The machine’s model is prohibited from booting K64 through a hardcoded list within the boot loader. (A cursory look suggests that the list excludes 'non-Pro' machines.)' The smbios.plist MaLd0n provided specified a MacBook Pro. I'm out of my depth: 'Good Night and Good Luck', another good movie, signing off.
My circumstantial evidence: I was reading Nawcom's blog, and this question was asked. Local says: December 8, 2010 at 4:31 am 'Thank you for the great release. Phenom 9550 up and working x32. Just one question. Your previous 10.6.5 kernel was 15.2 MB in size, while kernel on this cd is 7.5 MB, can you please share the differences?'
And Nawcom replied: ' nawcom says: December 8, 2010 at 12:47 pm 'It’s only compiled for i386, not i386 and x8664. That’s why it’s half the size. I would say that I keep it i386 only for compatibility with all known supported CPUS.' Mulcyber: That strikes me as having the potential for imposing a limitation.
Nawcom writes about his newest version of modCD, Feb14 2011: 'Fixes: Bootloader that’s installed, ICH10 AHCI/AppleIntelPIIXATA devid issue, JMicronATA causing an AppleAHCIPort kernel panic'. Okay, just so I've not gone completely mad I tried a standard boot CD + Retail install, combo then url='Then added 'arch=i386' and nope, same as in my first post. However, after a few more test installs it seems the AppleIntelHD. kexts were leading to the hang as before: either as a stall or at best switching to a blank grey screen.
Reading around I gather either my HD Graphics won't work at all or more likely be enabled by using a working DSDT.aml and/or hacking around the kexts. I shall leave the investigations of the graphics for a while and look into the other hardware. So far I have:. System updated to 10.6.7.
booting machkernel as x32 (but not x64). Wired Ethernet. Basic VESA graphic support. Accurate memory and processor description in 'About' Things that probably work but not fully tested:. Keyboard (some characters in wrong places but not really surprising in hackintosh!).
Trackpad (works but in theory could have multitouch). non-DSDT power support (SleepEnabler, VoodooBattery, etc.
Load but not looked at). USB devices (work most of the time but occasional KPs on insertion). DVD-Writer (OSX lists all the capabilities I'd expect).
Sound (need to find which kext best suits the ALC269) Not working but probably might:. Lid webcam (works in 10.6.0 retail, breaks from 10.6.3 on, related to above USB issues?) No idea on these at the moment:. Wifi (BCM4313). Bluetooth (BCM2070). Full graphics support. DSDT I have a theory on the BCM4313: posts on this usually finish with hacking around the vanilla IO80211Family.kext with focus on the BCM4311 kext. However, looking at the specs on Broadcom's site the 4311 and 4313 have nothing in common and I can't see any relation between them other than +2 Also in IO80211Family.kext is the BCM43224 which on paper is very similar to the BCM4313 but the former has a dual 2.4/5GHz transmitter - both are 'n' capable.
I shall be looking here More later! Regards, Andy. Sound (need to find which kext best suits the ALC269) EDIT: Re: ALC269 10ec:0269 & Nvidia 330m HDMI Larsen effect!!!
Close this topic! Solution is to edit VoodooHDA 2.7.2 plist: Change iGan from 90 to 0 Change iMix from 0 to 70 Add Mic entry with value 70 Now no Larsen effect, sound works, mic works (don't know what about HDMI). I see Lion is coming out soon. I've given up looking at the BCM4313, fortunately I had a Linksys USB adapter that works fine. Refering back to the work / doesn't work list, the biggest stumbling blocks I see for my laptop and quite a few others here are:. BroadCom BCM4313 - a very common budget N-series card, any hope there could be native support in Lion?. Intel HD graphics - a wide-reaching term that covers a lot of chipsets.
I believe my variant falls between being to new for standard Snow Leopard support and too old to be helped by the Sandy Bridge updates. Maybe I need to look again at getting at my DSDT.dml working! Everything else seems negotiable I will put this project on hold till Lion comes out.
If I can at least get my graphics working okay I'll consider swapping the BCM4313 for something Airport compatible. Thanks for all the help so far! Regards, Andy.
Hey together. I was just able, after trying Lion and Hazard's 10.6.6i (which both failed), to install 10.6.0 with the retail DVD and url='which i downloaded at tonymacx86. However i have some problems! Running the Combo Update 10.6.8 results in a Kernel Panic near the end of the installation ('Moving items to their destination.'
Can you please help me to explore what the issues might be?