bobdamnit

Keep me posted. Its still working for me lol. LAN is going strong. Its been connected and on my network for days, doing some massive Linux DLs.

Actually, I'm listed as a MacBook5,1 in System Profiler. But if you look closely at a terminal, it also says I'm a Mac Pro. Pictures... If you look at the System Profiler.png picture, you'll see that the titlebar says MacBook, but directly under that on the left, it say's Bob Damnit's Mac Pro. Terminal says the normal stuff @ Mac Pro.... I think think think..... Thats the reason SpeedStep with CoolBook isn't working. I don't know how to fix it, and both of my 10.6.7 installs (Normal and Test) are this way.

Which would be why I absolutely CANNOT modify SMBIOS. Not even with Lizard.app. Makes sense. I've kind of made a mess of my tri-boot setup (OS X 10.6.7, OS X 10.6.7test, and Windows 7) so I'm going to format and restart from scratch.

Here's where I got my info from: http://www.insanelymac.com/forum/index.php?showtopic=237080&st=0&p=1584444entry1584444 Its working for me. Still working just fine for me.

Mine is formatted MacOS Extended (Journaled) Case Sensitive. No problems here, other than I had to rename com.apple.boot.plist in Extra/Extensions to "com.Apple.boot.plist" so I could boot. Although, on the same hard drive, I'm failing SMART tests in OS X, and passing them in Windows

Yeah, I got it working also. But it doesn't work if you don't have some form of SpeedStep control. Apple's, which runs WAY hot. Coolbook, which for some reason just doesn't work for me, or some other 3rd party kext. (EnhancedIntelSpeedStep.kext, VoodooPower.kext, or VoodooPowerMini.kext) VoodooPowerMini seems to be working alongside that package. I thought the two of them were breaking sleep. Sleep worked, and it woke up and even the screen woke up, but nothing was ever displayed. No login screen, nothing. I had forgotten that I installed something called "VoodooMonitor", and between the three, some odd things were happening. Removing that fixes sleep, and now I have full SpeedStep control. Like I said, VoodooPowerMini seems to be working. It just doesn't work from inside Extra/Extensions. (Dont know why, but doesn't load.)

Alright, the problem came back. On boot, whether on charger, or battery, CPU starts out at 1.6 Ghz. If I add/remove the charger, it will automatically drop to 996 Mhz. Coolbook is working properly, and will run through the CPU states. Getting frustrated, I removed Coolbook completely. (Kext in /S/L/E also.) I started looking into alternate SpeedStep solutions. I found VoodooPower.kext, EnhancedIntelSpeedStep.kext, and VoodooPowerMini.kext. EnhancedIntelSpeedStep.kext and VoodooPower.kext caused KP. VoodooPowerMini.kext when installed into /S/L/E functions as expected. PstateMenu is showing me that SpeedStep is working, and TempMonitorLite is showing me that CPU is at a cool 45*C. When running GeekBench, it immediately jumps up to 60+, but Pstate Menu is also showing me that CPU speeds have increased. Pstate Menu selections are working also. I can set my CPU to any state I want, or let VoodooPowerMini take over and step it down. Even without Pstate Menu, CPU temps are low, fan speeds are WAY down, and videos are no longer choppy when I yank the power cord out. So far, so good. I don't know if anyone has tried VPM.kext, but its working decently for me. (Seems to have broken sleep. Removing Pstate kext fixes it.)

I wouldn't use EDP to install. Do like you have been doing to install OS X, and update to 10.6.7. My build (D520) is similar to yours, with the GMA 950 and ICH7 chipset. Here is my /Extra/Extensions folder and you could drop it in there. I'd remove anything that doesn't pertain to you though, like BCM440x.kext, ApplePS2Controller.kext, and VoodooTSCSync.kext. Your wireless card won't work. The Intel cards aren't compatible with OS X. I'm not sure if you can change yours, but I'd swap it out for a broadcom if you can. After you get my /E/E, download EDP1.8 only to install Chameleon and to have it perform a new build with current kexts. (Option 1, followed by option "A"). Here are steps laid out: -Install OS X -Update -Use EDP to install Chameleon -Replace Extra/Extensions with mine, sans mentioned kexts -Use EDP to perform "new build with current kexts" (option 1, then option "A") -Reboot and test Extensions.zip

Ugh. Hopefully Laserboy comes back and gives me a report. The 630 doesn't have the BCM4401? Its almost identical...

Excellent, but before we do that, I'd like for it to be tested on other D520's or any other Latitude that has the BCM4401/BCM440x.kext. I'd hate to have EDP1.9 users flipping out because my addition to EDP is screwing up everyone elses setup lol.

I'm using BCM440x.kext from EDP1.8. Seems to be working flawlessly to me. No hardware issues to speak of, sleep still works, as well as LAN after multiple reboots.

Laserboy, can you do me a favor? (Or, anyone with the BCM440x LAN card?) Add this to your com.apple.boot.plist in /Extra/Extensions as a kernel flag: Ddd max_valid_dma_addr=1024 I think I have this nailed down, honestly. It seems as though Broadcom LAN cards have a problem with DMA mapping when RAM is over 1Gb. I was looking in Ubuntu at the buffer overflow bounce rate, and they allocate for it to be over 1Gb, which is why it works in Windows and Linux just fine. But when I looked at buffer overflows for Mac, I couldn't find anything. One way to stop it is to force OS X to believe you only have 1Gb of RAM, by using "maxmem=1024" as a kernel flag. Instead of doing that, I decided that I'd try limiting DMA mapping over 1Gb. This allows OS X and all the applications to use all of your RAM, however hardware cannot. (Graphics, Wireless, Audio, etc...) Seems to have worked for me. Typing this from an overnight Linux torrent session over LAN, and still going strong. No kernel panics, odd behavior, or random LAN drops. Dunno if you guys have heard about this, but it seems to be a working solution for me.

Mine only does 1024x768. I'm not too worried about the outside. Its just got sentimental value. It was my first ever laptop The Inspiron 1525 is running Backtrack 4 and Windows 7. Thats how I got it. I'm considering leaving BT4 on it, and throwing Slackware on it also just to mess around with the new Slackware. The D820 needs a LOT of work. 90% of the keys on the keyboard are missing, it has no battery or charger, and the media keys feel broken. It does run, though. I used my D520 charger to power the thing up, and it booted Windows XP just fine.

Replacing it with a D530 is out of the question. I love my D520 too much! I did acquire a D820 CoreDuo 2.17Ghz 4Gb RAM with a nVidia 512Mb card. Planning on dropping OS X on that just to see. If it works, it'll become my new HackBook Pro. Also acquired a Insprion 1525 that seems to be pretty compatible with OS X, but I'm thinking about making that a Linux machine.

I used the kext from EDP 1.5. in all of my testing. Same kext works in 10.6.0/10.6.3, however no longer works after that. Couldn't tell you why. Seems to load, LAN shows up in System Preferences, but gets a MAC address of 00:00:00:00:00:00. No way to change it to the legit MAC address that I can see.

I've had it work, in 10.6/10.6.3. Don't know what changed, but it stops working there. Also, it worked phenomenally in Leopard. I think it will work, however I'm not too bothered by it now that I've rebranded my Dell card.

Pull out BCM440X.kext from /Extra/Extensions. Run EDP and select option "1". At the "Kext Configuration" menu, select option "A" to "Rebuild using present config". Reboot. Then, put BCM440x.kext back in Extra/Extensions and perform the same steps in EDP. It should rebuild the kext cache and force the BCM440x.kext to reload. When you remove it from Extra and rebuild with EDP, it should remove the LAN from "Networking" in System Preferences.

I took the plunge last night and fired up a Live Ubuntu CD and rebranded my BCM4312 card to an AirPort card. Results were amazing! I'm finally able to get Wireless N speeds without having the WLAN card drop out of working existence and not function until I reboot. If I had the router in "N" mode, I could surf the web for about 30 seconds on my BCM4312 card before it went stupid and stopped working. If I left it in "G" mode, I never had a problem. Problem I'm running into is that now in Backtrack 4, I can no longer use the b43 module to test wireless penetration. (Its cool. I have an Intel 2200/B/G/N card that works great for that!) Card works great for Windows though. No issues at all. Still detected as a BCM4321! But, having OS X pickup my wireless N router and achieve N speeds is going to make me completely forget about not having working LAN lol.

Probably not. I'm not too concerned with the LAN being broken. I rarely use it, honestly. But I'd like to have it working for others that have the BCM4401 and don't have a compatible wireless card, or do not have the means to get one. (They're destitue, cards are unavailable in their region, etc..) I did find that 10.6.3 was the last version of OS X Snow Leopard that would let me BCM4401 work properly. Anything past that, and the card becomes ignorant. (Also, anyone else notice that when you adjust the display brightness on their Latitude, the on-screen bezel doesn't display in OS X? Yet, when I push the "Pause" key, it attempts to adjust the display brightness and shows the bezel, however it doesn't actually adjust the brightness. It tries to increase the brightness, but wont. I haven't found a key for dim brightness lol.)

On the off-chance that this is right, I decided to image my setup and repartition for testing purposes. I now have 2 partitions, a flawlessly (sort of) working partition of OS X 10.6.7, and a very basic partition with OS X 10.6.0. I can confirm that LAN works in 10.6. However, somewhere in the update process, it stops working. In 10.6.7, my LAN doesn't work either. Tomorrow, I'm going to update to EVERY point, and figure out where it stops working. However, it doesn't make any sense to me. In my second partition running 10.6.0, I used the BCM440X.kext that is in EDP1.8, and LAN worked perfectly. It would auto assign an IP address via DHCP and allow me online with no issues. But in 10.6.7, using the SAME kext, it assigns me a loopback address, and NOTHING I do will change it. I just don't get it.

It works for us also, however in Snow Leopard you have to manually load the kext every time you wake from sleep, or shutdown/reboot. Its got something to do with the Sandbox, however I currently have no idea how to get around it. I'm sure Slice does, but CoolBook Controller works as it should, and keeps my D520 very cool. (Running 45*C right now. Cooler than it runs in Windows 7!!)

Try using my BCM440X.kext. Drop it into /Extra/Extensions, then when OS X asks you if you would like to copy/replace, say yes. Then fire up EDP and do selection 1, followed by a new build using current extensions. I believe the option is "A". Yup, after checking, its selection 1, followed by option "A". You'll see option "A" at the bottom of the EDP Terminal window. It says "Perform new build using existing kexts". If my BCM440X kext doesn't work, I'm not sure what else to try. I used to have this problem in Leopard, and sometimes reinstalling OS X would fix the issue. (I have no clue what ethernet card my D520 has, honestly.) AppleBCM440XEthernet.kext.zip

Cool. Glad to help out anyway I can. My machine is your machine, I'll just be doing the legwork

Actually, I did. I have a D520, and like I said in the email, I have a spare laptop. (Its a MacBook Pro. Hackintosh is more or less a hobby lol) So I'm not too concerned about destroying this laptop, and am completely willing to basically donate this machine to testing. If I could, I'd love to claim the D520 slot lol.

Chameleon rev 667 brings speedstep back. I lost battery meter, but I'm positive I can bring that back with EDP. I've been running for a whole day, in and out of sleep, and reboots galore and speedstep seems to be working all the time now. I know now why this happened. I installed EDP 1.8 but did not install the new version of Chameleon. While browsing EDP 1.8, I saw that you guys had packaged EDP with a new version of Chameleon. I figured it was alright to update, and that the bootloader wouldn't make that much of a difference. It never really did in Leopard. Perhaps support two bootloaders in EDP? Revision 667 as a guarantee and whatever you guys have been testing recently? I would certainly be willing to test bootloaders to see what benefits everyone the best. In fact, I might just do that anyway, and report back for you guys what worked best/worst for me.