Hervé

The bootup resolution is managed by optional parameter "Graphics Mode"="----x----x32". Best way to check and set or adjust this is with Chameleon Wizard once you're booted up: install Cham Wizard on your system (for instance, in Applications) and just double click on the Chameleon boot plist in /Extra. You'll see this optional parameter to the right side with a scroll-down menu from which you can choose various resolutions. Select 1440x900 if that's the one you want. For the persistent -f -v boot flags, as Mick said, press a key when you see the Chameleon delay bar at startup. You should then see the persistent boot flags and options at the botton of your screen. Delete everything, press Space then press Enter. That should take care of things.

Copying the kexts is not sufficient. You need to rebuild your cache and permissions with myFix or boot with -f.

You definitely need a new graphics card in the Optiplex: the on-board GMA 3100 is not supported by any OS X versions. But you'll find cards (such as the one I mentioned - fits all Optiplex models, including SFF ones) in the $30-50/25-40€ bracket, possibly cheaper on the 2nd hand market. For wifi, you should be able to get a USB dongle for pennies. nVidia 7300 SE is quite old and unsupported in ML (ok under SL and Lion though). Avoid it. The Quadro NVS 110M of the D620 is based on that 7300 chip. On the ATI front: the Radeon HD 5450 is a budget/entry-level card, capable to fit in low-profile desktops. It is supported in ML (OOB I think). Very cheap card. the Radeon HD 6450 is probably quite comparable to the nVidia GT610/620. Again, it's low-profile capable. It appears very problematic in ML... the Radeon HD 5670 is, I believe, more targetted for games. This is a full height card, so it won't fit into low-profile desktops such as the 755 SFF. It is supported in ML (may require kexts patching, depending on model/manufacturer).

I got hold of a Dell mini PCIe WWAN module for a D Series (Novatel Expedite EU870D, 7.2Mbps) and decided to give it a try. Not knowing if it'd be supported at all in OS X, I first gave it a shot in Win7 on my D630 nVidia. The module did not really show any indication of a model, so I just took a note of its PCI device ids and googled for it: Vendor id 0x413c and Device id 0x8137 came out as Dell DW5520. So I downloaded the driver for that module off Dell's web site D630 pages and, upon installation, I sure obtained a DW5520 3G modem in the device manager. I got a shortcut for a 3G modem app on the desktop too + a new little icon in the task bar. I took the battery out, inserted my 3G SFR-network SIM card and launched the app. It sure detected the SIM card on the SFR network and, chance would have it, there was an existing dial-up profile for SFR. I clicked on the connect button and off it went: 3G connection to the Internet. Great! I took the SFR SIM card out and tried my 3G Orange one. However, there was no existing Orange profile offered. So, I created one: 'called it "Orange World" and just specified APN "orange" as found on the Net. That sure was enough to be able to kick-off and establish a 3G connection. Brilliant! 'had to try it with OS X then. 'rebooted my D630 in Mountain Lion and checked the WWAN section of the System Report. Mmm, nothing. Quick look at USB: ha! it showed a "Novatel wireless HSDPA modem". Looking promising... However, no modem/new card/new interface in the Network Pref Pane. Ok, so the card was seen, but not registering as a WWAN module. A quick search on the Net revealed the use of 2 kexts + 1 script for WWAN: /S/L/E/IOSerialFamily.kext /SL/E/CellPhoneHelper.kext /L/Modem scripts/WWAN.ccl The IOSerialFamily kext contains a few plugins, 3 of them for WWAN: AppleWWANSupport + AppleWWANSupport1 + AppleWWANSupport2 (4th plugin is called AppleUSBIrDA). A quick look at the plugins showed entries for 0x413c vendor devices in AppleWWANsupport + AppleWWANSupport1. Things looked well covered from that point of view. The CellPhoneHelp kext's info plist was found to contain 2 entries for 0x413c vendor devices: one for device 0x8117, referenced as "Novatel Wireless EXPD CDMA (Dell 5700)" and one for device 0x8118, referenced as "Novatel Wireless HSDPA Modem (XU870)". Interesting, a possible/likely place for patching... The WWAN.ccl script showed many entries, including one for Novatel devices. All seemed in order on that front. I therefore decided to try and patch that CellPhoneHelper kext. I made a copy of it to the desktop and edited the info plist: I copied the entire 0x8118 HSDPA modem part and pasted/edited it as "0x413c/0x8137 Novatel Wireless HSDPA Modem (Dell DW5520)". At the bottom part of that section, I simply replaced the device id (in dec.) by 33079 (=0x8137 in hex.). After saving the plist file, I moved the modded kext to /E/E and ran myFix (full). On reboot, bingo!, I had a WWAN module reported. I opened up the Network Pref Pane and noticed a new 3G modem available to add. Once that was done, the card was listed on the left column and there was a default config to the right (auto-detected for Orange as it appeared). I checked the box to show modem status in the menu bar. Now I could see a nice new little icon on the menu bar, showing the well-known vertical bars of cellular networks signal... Clicking on it opened a little scroll-down menu with indication of network provider and a Connect option. On clicking Connect, I could see attempts to establish a connection but it would always fail. I remembered seeing the default profile with username Orange and a password in the Network Pref Pane, so I thought I'd edit that. What was in fact required was a proper profile for Orange. I opted to do the same thing as I had previously done in Windows: a new profile called "Orange World" and a simple mention of "orange" as APN data. Under Mac OS X however, the little bugger wanted a username and password! So, I decided to return to Windows and look for those credentials. None to be found in the profile I had created though; <_ i noticed could export my created profile. that resulted in an xml file which upon inspection a text editor revealed empty username and extremely long hexadecimal password. back mac os x simply copied this password the orange> Bingo! I was then able to establish a connection to the Orange 3G network. Once connected, the little vertical bars showing cellular signal strength become darker. Clicking on the icon allows to drop the connection when it's no longer required (and it could be better for your phone bill to remember to disconnect !!!), although there's an option to disconnect after a certain idle time (10min by default). The scroll-down menu also provides a direct link to the Network Pref Pane. When the 3G connection is in place, the Novatel tab will show details of IP addressing, connection duration and 3G traffic volume. Not that useful but nice to watch. I repeated the same process for Lion (10.7.5) and Snow Leopard (10.6.8) on my other D620/D630 laptops. It worked Ok in all cases but I noticed that, for Snow Leopard, there were 2 additional plugins in IOSerialFamily kext: InternalModemSupport + MotorolaSM56KUSB. They had to be removed for the WWAN module to be detected and work. I therefore made a modded copy of that kext to /E/E and re-ran myFix, rather than modify the original kext in /S/L/E. All was Ok on reboot. That's the only configuration difference for Snow Leopard. I also noticed that SL offered the ability to turn WWAN On and Off in the scroll-down menu, something not offered under Lion and ML. In a nutshell: for Lion & Mountain Lion: patched CellPhoneHelper kext in /E/E for Snow Leopard: patched CellPhoneHelper + modified plugin IOSerialFamily kexts in /E/E So, there you are, a nice little way to add 3G functionality to your Hackintosh if you possess a WWAN module and a 3G cell phone contract. This method was tested on the Latitude D Series, but should naturally be applicable to other models.

I've no experience with the above cards but I would recommend you to check the wiki pages of InsanelyMac for a list of validated cards in the Components pages of each OS X version. Now, having very recently installed one, I can tell you that the nVidia GeForce GT610 works OOB in Lion and ML. There are various models of such cards (I used a Twintech 2GB DDR3 model). It's not a high-end card by any means, but it does quite a good job as an entry/mid-level card. It's cheap too. There are 1GB and 2GB versions. There's a good chance the GT620 would work just as well but can't say for sure, I've not tried it.

Perfect, especially if it has a higher res screen. There are 3 different 15.4" screen models: WXGA@1280x800, WSXGA+@1680x1050, WUXGA@1920x1200. The WXGA resolution is, in my opinion, too limited on a 15.4" display. That D830 will run ML very well with its T9300 CPU and 4GB of RAM.

I would recommend that you look at BIOS specialists site BIOS mods (http://www.bios-mods.com). You sure would be likely to get experts' advice there.

Isn't the E1505 the same as the 9400? That is listed in our compatibility chart. I would recommend you to redo a Vanilla installation with myHack + EDP. The problem with distros is that they're generic so you don't really know and control what they may or may not install...

Instead of modding the /S/L/E kexts, I would have made a copy to /E/E and modded those, then run myFix (full). This way, original /S/L/E kexts would have been left untouched. We would also recommend Chameleon, not chimera (chameleon, stolen and rebranded), but it's up to you in the end...

Re: "failed installation", read-up existing posts about it on the forum

Hey, good progress! Sleep and HDMI could need a DSDT patch; hopefully Dinesh can look into it. We'll get back to you.

Hi and welcome to this mad place! Look at the various OSXL web pages (EDP pages, including compatibility chart), not just the forum. You'll find a list of supported models there. Then post in support sections if you have any technical queries.

What are the PCI ids for your card? The Chameleon bootloader detects it but does not load a framebuffer per se, that's only done at Mac OS level. You probably need to check if your card device id is covered by the expected ATI/Radeon kext and FB. You may require patches, in which case, copy relevant kexts to /E/E.

Look in kextpacks for the ANV-Slice ALPS controller, it should be there. For Sleep, try with Sleepenabler kext.

No, there's no specific kexts for resolution, it's all covered by the kext that controls the display GPU and therefore knows its capabilities. Did you adjust the brightness at all in the display pref pane?

What you can do is install EDP, then grab the kexts off /Extra/Storage subfolders and copy them to /E/E. The kexts will be in various places, but we can help you with that. At minimum, that will get your keyboard/trackpad, audio, Ethernet working, possibly Sleep too. USB and HDMI probably require a DSDT. SD reader may not be supported at all. We're on the right track.

Oh well, if it's only 50quid, don't hesitate; it'll be an improvement. I can't really do with the WXGA to be honest, had the larger screen from the beginning and only got the LoRes version off work disposal, for testing purposes.

Replacing the WXGA LCD by a WXGA+ is totally feasible on the D620 and D630. You just need to make sure to get the cable with the LCD because they go together (cable for WXGA is different from cable for WXGA+). Your main problem would probably be to find one, and a cheap one too. You know, it's wouldn't be worth to spend $100 on a replacement screen of you could get a HiRes nVidia model for $200-250... But for what it's worth, I too have a D630 GMA LoRes and I must admit the screen is not great under Lion (I think it even looks nicer under SL!). It's much much better on my other D630 GMA HiRes. ML looks even better (improved graphics) on my other D630 HiRes, but that needs nVidia GPU...

Ok, so don't use the NullCPUPowerManagement at all then. Use the Generic /Extra (it's quite basic) to do your initial installation. Once you have ML installed and, hopefully, running, we can have a look at adding whatever kext might be required to get non-operational hardware.

You made your myHack installer with Generic /Extra, right? Or did you use your own /Extra as provided above? Do you have NullCPUPowerManagement in /Extra/Extensions at all? If not, try to put it there and re-run myFix (full) on the media and retry.

Both tables do differ... Now, I'm far from a DSDT expert (quite the contrary) but I can make the following comments: I see this part of DVI table (under 'Device (PEG0)') not included in the VGA table: Device (PEGP) { Name (_ADR, 0xFFFF) Method (_PRW, 0, NotSerialized) { Return (GPRW (0x09, 0x04)) } } Device (VID) { Name (_ADR, Zero) } Also, I note that in DVI table you have: Method (_DSM, 4, NotSerialized) { Store (Package (0x22) { "rom-revision", Buffer (0x10) { "OSXLatitude.com" }, "@0,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0F) { "NVDA,Display-A" }, "@0,built-in", Buffer (One) { 0x01 }, "@0,pwm-info", Buffer (0x14) { /* 0000 */ 0x01, 0x14, 0x00, 0x64, 0xA8, 0x61, 0x00, 0x00, /* 0008 */ 0x08, 0x52, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, /* 0010 */ 0x00, 0x04, 0x00, 0x00 }, whereas in the VGA table, you have: Method (_DSM, 4, NotSerialized) { Store (Package (0x1C) { "@0,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0F) { "NVDA,Display-A" }, "@0,built-in", Buffer (One) { 0x01 }, "@0,pwm-info", Buffer (0x14) { /* 0000 */ 0x01, 0x14, 0x00, 0x64, 0xA8, 0x61, 0x00, 0x00, /* 0008 */ 0x08, 0x52, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, /* 0010 */ 0x00, 0x04, 0x00, 0x00 }, and what follows, related to "@1, [...]" looks the same in both tables.... Try and copy/replace the part from DVI to VGA or vice versa.

Yes, kind of... I tried briefly on my D630 GMA, but quickly stopped when I met problem booting the DP1 kernel; there's just no point at all.

Those who use ML know that Apple removed the ability to have the quick resolution switching/monitors dectection facility in the Finder's bar, as existed in previous versions. By default, ML users now have to go to the display pref pane and press Alt key to detect monitors or select 'scale' resolution to get a list and be able to manually select one. There are 2 little tools available to get that functionality back: Display Menu, which is available for free on App Store QuickRes, available from http://www.quickresapp.com Display Menu works great and is extremely well presented; this is the tool I would recommend. QuickRes is nice too, but I found it to be a little flawed. For instance, when testing it on a D830 WXGA (1280x800), I noticed it allowed to select a WUXGA (1920x1080) resolution that sets the laptop LCD to a sort of interlaced mode at what appears the said resolution. One may think "Great! I can get a much much larger resolution than normally expected!" when in fact it's bugged: the mouse cannot move to the very top and very bottom of the screen (stops at about 1/2 an inch)... As such, the mouse has to be set to about a 1/2 inch from the place where you want to click for items at top and bottom of screen, whilst it seemed to be Ok for things in the middle of the screen. So, careful ! There's no problem when correct/supported resolutions are used though. NB: for the above picture, in order to select the 'Resolutions' option, the mouse had to be placed right under the 'Quit' option of the QuickRes popup menu...

The message is probably a "failed installation" actually. I wouldn't call that "normal" per se, but yes, it's a known false alarm since 1st ML release... It's been mentioned in the following threads: https://osxlatitude.com/index.php?/topic/2258-1083-update/ https://osxlatitude.com/index.php?/topic/1852-1082-update/ https://osxlatitude.com/index.php?/topic/1621-installed-108-on-d630-nvidia/

Arguably, it is somehow easier to update your BIOS from within Windows, so yes, update it before you install OS X.