Jump to content

Hervé

Administrators
  • Posts

    9911
  • Joined

  • Last visited

  • Days Won

    548

Everything posted by Hervé

  1. 'glad you found this site of assistance. The D630 nVidia is indeed a great C2D platform to run ML. My own one has an ultra crisp LCD with WSXGA+ resolution + SSD drive which makes for a superb oldish laptop to run Mac OS X (Ok, I'm a great fan of 13"-14" size laptops). I might replace my 11g wifi card by a 11n model to get improved internal network performance, especially with my Win-based server. Enjoy your latest Hackintosh!
  2. Hi Dragon, thanks for your contribution and feedback post DSDT table creation by Dinesh. Definitely a new system for integration into EDP.
  3. Do you have the Chameleon SATA module in /Extra/modules? Available here: http://forge.voodooprojects.org/p/chameleon/downloads/ BIOS HDD settings set to AHCI?
  4. Ok, we found that a kext had gone missing from the bootpack. it's been corrected. Re-download and re-apply the bootpack (re-run myHack -> install /Extra) and all will be in order, although it looks like you got there with that other /Extra folder which had the required kext!
  5. Because the bootpack is what it's called: a boot package. It's the basic stuff required to boot and get started (DSDT table + mandatory kexts and modules). It does not contain all the additional EDP stuff or whatever a user may add post-installation (eg: Chameleon themes) in /Extra.
  6. 1) http://argo.osxlatitude.com/edp/bootpack/ 2) https://osxlatitude.com/index.php?/topic/1868-bios-settings-d630/ 3) http://argo.osxlatitude.com/edp 4) http://argo.osxlatitude.com/edp/pre-installation/ 5) http://argo.osxlatitude.com/edp/installation/ 6) http://argo.osxlatitude.com/edp/post-installation/
  7. Did you try boot option: PciRoot=1 ? All usual Broadcom-based wireless cards will work: DW1390, DW1395, DW1490 to name some '11g' cards. You used the M4300 bootpack, right? If that didn't work to boot the M4300, note that it is quite similar hardware to D630 or D830, so you may reach some success with one of those bootpacks. Use the nVidia versions.
  8. That just applies to built-in LCD or ext. display in mirrored mode. The problem experienced above is only for ext. display in extended mode and that is only available post-boot.
  9. Try this in /S/L/E, but I would expect it to be ignored... IO80211Family.kext.zip 'ever tried to use the BCM43xx kexts instead of patched IO80211 for that DW1395?
  10. Out of interest, I've also done the same tests with my 20" widescreen 1680x1050 LCD. -> same sort of results: bottom of screen gets corrupted beyond 1280x800: 1) @1280x1024 2) @1680x1050 -> looks like any resolution starting from 1280x1024 and above gets corrupted.
  11. Ok, good, that's exactly what I experienced the other day. It's totally consistent and the black parts on the external screen are due to the widescreen ratio that is being maintained across both displays. You should still be able to select 1440x900 on the built-in LCD and another resolution on the external display; it'll then adjust with bars accordingly. Now, coming back to the issue you reported in extended mode, I have good news and bad news. The good news is that I can 100% reproduce the problem with my D620 GMA low res; the bad news is that there is indeed a problem! I hooked my D620 (GMA950) to a 19" 4:3 1280x1024 external LCD and booted SL 10.6.8. Internal display was @1280x800 as usual and external screen got automatically set by default @1152x864 (75Hz). No problem, external display looking nice enough. I then started to play with higher resolutions. 1) @1280x768 (60Hz), no problem, but graphics and text are a bit distorted/squeezed horizontally due to resolution. Not nice at all (doesn't show on screencopy). 2) @1280x960 (60Hz), no problem. Graphics and text look very much like @1152x864, there is just a bit more space available on the screen. 3) @1280x1024 (60Hz/75Hz), I too get the graphics corruption at the bottom. The issue is bad enough to even temporarily affect screen contents during moves. Conclusion: stick to 1152x864 or 1280x960!
  12. Yes, Wifi is always on, I never deactivate it. Both BT + Wifi run and wake concurrently. One last thing you could do, to match my laptop even more, is to copy my /S/L/E/IO80211Family kext to your /S/L/E, re-run myFix and try once more. -> PM
  13. No need to run myFix after changing DSDT file, just a straight reboot obviously to load that new table. The tests I ran the other day were in mirrored mode so I'll try again with extended mode, but no docking station/port replicator I'm afraid.
  14. By all means, try it; you may actually find another version of it there; I know I have one...
  15. No gain to be had with BIOS A18; in fact, it just adds signed firmware capabilities, nothing else. I just updated all my D630s for the sake of it, that's all.
  16. There are 2 LCD models for these laptops: 1) lo. res.: WSXGA (1280x800) 2) hi. res.: WSXGA+ (1440x900) By default, Mac OS X uses the highest res. supported by the display, so if you're not getting better than 1280x800, you're on a low res. model. You can confirm that through the BIOS system page where you'll see information about the laptop's hardware. You can only improve that by changing/swapping LCD (incl. inverter + cable, not just the glass panel) or by attaching a higher res. external display.
  17. Look here: https://osxlatitude.com/index.php?/topic/1827-slow-shutdown/page__st__20 Basically, delete AppleACPIPlatform.kext from /System/Library/Extensions (keep a backup just in case) and re-run myFix (full). Normally, EDP replaces that /S/L/E kext by the version from myHack in /Extra/Extensions (that was the EDP fix) but maybe there is regression following latest EDP update (up to r68 today).
  18. That issue had been fixed and fix incorporated to EDP (replacement of AppleACPIplatform kext from memory).
  19. Well, you plug your adapter in a USB port, the laptop sees it and reports what it reads out of the device. That's all. It's not activated, not usable because you need to install & load a kext (=a driver) for that new hardware, if such a kext exists (Google might be your friend). Once this is done, go to Network Preferences and you should get a popup message advising you that new hardware has been detected. At the bottom of the listed hardware, just above the lock, there are '+' and '-' clickable buttons. Click on '+', then open up the list of available network interfaces and select your newly installed equipment.
  20. Correct me if I'm wrong, but it sounds that you just want your laptop LCD to turn off/turn on (i.e. display sleep) when lid is closed/re-opened, right? Or do you just want to close the lid without anything happening at all, i.e. no display sleep, no computer sleep? Whatever it is, it differs from initial design, which is to sleep the computer when lid is closed. So you use 3rd party software (InsomniaX/Caffeine/Sleepless) to try and reach your goal. I don't know how it's done, but I guess those software somehow intercept the call for the code that puts computer to sleep. From your description, it also appears that those software do not put the display to sleep and that you have to use hot corner to do that, right? Or does closing the lid, with those software enabled, still put display to sleep but opening the lid failing to wake it? I'm failing to comprehend how a DSDT edit would help you here. I recently played around with hot corners on all my Latitudes. Works great, I can either put display to sleep or launch screensaver. With display sleep, I do not have to return to the specific hot corner to wake display, I simply press a key or move the mouse. If that does not work anymore once your 3rd party software is installed, I'd say the problem comes from them. Don't you agree?
  21. Try this one, renamed as DSDT.aml in /Extra. dsdt_d620_gma_1440x900.aml.zip
  22. It is best to use EDP on all the supported systems! It goes a long way beyond installing an audio driver (which is far from being the only thing missing after initial installation)...
  23. Hi, it's very simple: Intel cards are not (usually/longer) supported by Mac OS X, so you'll have to take that card out. Replace it with a supported model: - 'G' (54Mbps) Broadcom-based (BCM4311/4312) cards such as Dell DW1390, DW1395, DW1490, etc. - 'N' (270-300Mbps) Broadcom-based (BCM4321/4322/94321/94322) cards such as Dell MX846 (DW1505?), etc. - non Dell-branded (eg: HP, Asus, Apple) but nevertheless Broadcom-based cards - some Atheros cards (but I'm not familiar with those devices) You need a full-size mini PCIe card, not a half-size one (at least not without an adapter).
  24. I have the same (good) behaviour whether I use a BT350 or a BT360 adapter, so I rule out hardware/model-related issue. In your System Profiler, can you check your extensions for IO80211.kext? Which version does it show? I expect 1111, i.e. myHack. Provided you've run myFix (full) after that you copied "my" kext to /E/E, I would expect to find no 80211Family plugins (or empty plugins folder) in /S/L/E/myHack.kext. Can you check that out to establish if the "new" kext is indeed loaded? 2) open contents of myHack.kext and check plugins folder 2) you should find IO80211Family.kext 3) open that kext and check its plugins folder -> should be empty 4) open the version.plist file -> should show v3.1.2 You say your firmware at v4315 is higher than mine. Not exactly... After my tests, I said: - BT350 adapters -> firmware v2422 - BT360 adapters -> firmware v4315 so everything certainly looks Ok to me on that matter. I attach copy of the reported specs of the BT360 adapter as fitted to my D630 X3100 running Lion 10.7.5. You'll see that hardware is identical and software is different, presumably due to different versions of OS X.
  25. Well, if that existed, we need to update the bootpack page for the D620 GMA. It only shows one entry, clearly one for the low res model.
×
×
  • Create New...