Driver compatibility for Dell Studio 14z (Successful OSX install!)

[glitchbit]

r1000 kext belongs inside another kext.. but here are the files I am using. Also GAOO inserted the r1000 kext into a kext package inside System/Library/Extensions, while that is fine, I copied that file and modified it under EE... whether or not that can be done with the wireless.. I am not sure actually. I see no reason why it would not work.

 

Here are my files.. you can probably move a lot of the files I have inside my SLE into the EE location. I had been experimenting a lot last week and did not get around to placing some of my files such as voodoobattery back into EE..

 

You really need to edit your own smbios.plist file though, because it may have hardware specific information in it and I am not sure what would happen if you were to use my smbios.plist!! I use Property List Editor for minor edits like the SMproductname

 

I would also suggest that at sometime or another, if you have not tried anyone elses dsdt file then try someone elses just to rule out my dsdt as creating the issue. Also if someone elses dsdt creates a KP or anything you can also boot up with DropSSDT=y I believe and it will ignore the dsdt file completely so you can revert back to a different one.

 

extra folder

http://www.mediafire.com/download.php?jty2mwiyedx

 

sle folder

http://www.mediafire.com/?jtfyjqy1wz4

 

Also a lot, maybe all of the color coded files that you see in my SLE folder that have not been mentioned in this thread anywhere could probably be skipped over.. it was part of my standard install disc (SnowOSX) so I am not certain if they are really needed or not. Sorry I had not got around to making sure they are needed or not..

[lancorp]

r1000 kext belongs inside another kext.. but here are the files I am using. Also GAOO inserted the r1000 kext into a kext package inside System/Library/Extensions, while that is fine, I copied that file and modified it under EE... whether or not that can be done with the wireless.. I am not sure actually. I see no reason why it would not work.

 

Here are my files.. you can probably move a lot of the files I have inside my SLE into the EE location. I had been experimenting a lot last week and did not get around to placing some of my files such as voodoobattery back into EE..

 

You really need to edit your own smbios.plist file though, because it may have hardware specific information in it and I am not sure what would happen if you were to use my smbios.plist!! I use Property List Editor for minor edits like the SMproductname

 

I would also suggest that at sometime or another, if you have not tried anyone elses dsdt file then try someone elses just to rule out my dsdt as creating the issue. Also if someone elses dsdt creates a KP or anything you can also boot up with DropSSDT=y I believe and it will ignore the dsdt file completely so you can revert back to a different one.

 

extra folder

http://www.mediafire.com/download.php?jty2mwiyedx

 

sle folder

http://www.mediafire.com/?jtfyjqy1wz4

 

Also a lot, maybe all of the color coded files that you see in my SLE folder that have not been mentioned in this thread anywhere could probably be skipped over.. it was part of my standard install disc (SnowOSX) so I am not certain if they are really needed or not. Sorry I had not got around to making sure they are needed or not..

 

My wireless works fine, it's just the wired ethernet. I'm not clear what you mean about R1000.kext (is that the same as Realtek1000.kext?) being inside of another kext. Sorry, I'm still learning. I also do not have an Extra/Extensions folder. Just Extra. Should there be an Extensions folder in there? All my kexts are in S/L/E. Why would I put some in Extra/Extensions instead?

 

I have the same problem as Bigdog1, back a few pages. I've sent him a PM to see if he ever got his Ethernet working.

 

I went ahead and did 10.2.6, and of course, sound and wifi didn't work afterwords, so I had to reapply some of the kexts that I just got finished doing! In any case I got both working again.

 

I think I'd like to modify the smbios.plist to gain the advantages others have discussed. I can probably figure it out, but what text string did you use to simulate a Macbook?

 

So, here's some quirky things that I still have a problem with on my 14z with 10.2.6:

 

• Sound works, but only after I adjust the volume twice.
  
• Ethernet detects when a cable is plugged in, but otherwise, does not work. No link speed, no packets, no IP.
  
• Fan runs a lot, and loudly. I have not heard anyone complain about this. Is my fan just noisier than others? If I'm doing anything, the fan starts running.
  

 

Lastly, I read that PC_EFI might help my Ethernet to be detected and work. I googled it, and it seems it's not an installer, just a file called "boot". Does anyone suggest using PC_EFI? What will I gain? How do I install it?

 

Sorry for all the questions! I promise to leave all of you in my will.

 

Thanks.

[glitchbit]

actually I meant to mention that if you update, which you already have, it will overwrite some of your modified files, and I apologize that I did not explain that you need to create an Extensions folder inside the Extra folder to avoid the system updates from overwriting your modified files. Don't worry about the update though, I have included the kext files you needed in my last post.

 

Basically what happens is that chameleon bootloader will load your EE kext files instead of the ones in SLE. It is also what allows some people to run a completely vanilla or close to vanilla system with no or fewer modded files in SLE. Unfortunately not every modded kext file in the SLE location can be placed in EE. It is mostly a trail and error process but most kext files can be placed in EE, I think is a safe assumption.

 

And yes when I said r1000.kext I was referring to realtek1000.kext, if you download my files and place them in Extra\Extensions and System\Library\Extensions you should be good. Also make sure you use the "Kext Utility" app to chown those directories after you modify them.. of course you can use the terminal but dragging and dropping those folders on to the kext utility app I find to be a lot nicer.

 

Also since you have an Extra folder it is fairly safe to assume, I think, that you already have a version of pc_efi and the chameleon bootloader installed. I wish I had explained that stuff earlier, but yes it threw me for a loop too awhile back because just about everyone around takes some of this stuff as common knowledge. It seems unless you keep yourself in the forums every 30 days you are likely to miss major developments and then everyone assumes you are up to speed.

[lancorp]

actually I meant to mention that if you update, which you already have, it will overwrite some of your modified files, and I apologize that I did not explain that you need to create an Extensions folder inside the Extra folder to avoid the system updates from overwriting your modified files. Don't worry about the update though, I have included the kext files you needed in my last post.

 

Basically what happens is that chameleon bootloader will load your EE kext files instead of the ones in SLE. It is also what allows some people to run a completely vanilla or close to vanilla system with no or fewer modded files in SLE. Unfortunately not every modded kext file in the SLE location can be placed in EE. It is mostly a trail and error process but most kext files can be placed in EE, I think is a safe assumption.

 

And yes when I said r1000.kext I was referring to realtek1000.kext, if you download my files and place them in Extra\Extensions and System\Library\Extensions you should be good. Also make sure you use the "Kext Utility" app to chown those directories after you modify them.. of course you can use the terminal but dragging and dropping those folders on to the kext utility app I find to be a lot nicer.

 

Also since you have an Extra folder it is fairly safe to assume, I think, that you already have a version of pc_efi and the chameleon bootloader installed. I wish I had explained that stuff earlier, but yes it threw me for a loop too awhile back because just about everyone around takes some of this stuff as common knowledge. It seems unless you keep yourself in the forums every 30 days you are likely to miss major developments and then everyone assumes you are up to speed.

 

Thanks again... I tried putting your kexts from your Extra's folder into mine (created the Extensions folder first!), and looked at your S/L/E folder and it looked like I had most of those already. Not sure what the color coding was for. So, I rebooted, and noticed my fans going crazy all the time. I looked at the activity monitor and it showed "kernal_task" running constantly at about 80%. On a hunch, I removed the cpui_snow kext and ran the kext utility app and rebooted and everything was back to normal. Normal being no Ethernet, still. I did not see a Realtek1000 kext in your files, though. Shouldn't you have one?

 

Anyways, I'm not sure what to do next...I cannot figure out why my Ethernet does not work!

 

If you have any other ideas, bring 'em on! Thanks.

[glitchbit]

Thanks again... I tried putting your kexts from your Extra's folder into mine (created the Extensions folder first!), and looked at your S/L/E folder and it looked like I had most of those already. Not sure what the color coding was for. So, I rebooted, and noticed my fans going crazy all the time. I looked at the activity monitor and it showed "kernal_task" running constantly at about 80%. On a hunch, I removed the cpui_snow kext and ran the kext utility app and rebooted and everything was back to normal. Normal being no Ethernet, still. I did not see a Realtek1000 kext in your files, though. Shouldn't you have one?

 

Anyways, I'm not sure what to do next...I cannot figure out why my Ethernet does not work!

 

If you have any other ideas, bring 'em on! Thanks.

 

As I said before the realtek1000.kext is inside another kext file, IONetworkingFamily.kext I think is the name of the one it is in. As you can see in my EE folder. If that does not fix it for you then I suggest that you go look at your IONetworkingFamily.kext inside SLE and relocate it to another folder to make sure it is not loading in place of your EE file.. or after you relocate your original, just overwrite it with IONetworkingFamily.kext.

 

Also stop looking at the kext files as files, look at them as if they are folders or zip files, they have contents inside them that are easily read and modified by end users and sometimes contain multiple kext files for various hardware configurations.

 

Also I can not tell you much about your fans going crazy issue... I have the exact same laptop and dsdt obviously with BIOS A04 installed and had A01 and both times the cpui_snow.kext never caused my fans to go crazy for any reason.. cpui_snow.kext is specifically so that the cpu-i app can monitor speedstepping.

 

Only other thing I can think of is for you to check for a nullcpupowermanagement.kext in SLE and if you have it remove it.

[lancorp]

As I said before the realtek1000.kext is inside another kext file, IONetworkingFamily.kext I think is the name of the one it is in. As you can see in my EE folder. If that does not fix it for you then I suggest that you go look at your IONetworkingFamily.kext inside SLE and relocate it to another folder to make sure it is not loading in place of your EE file.. or after you relocate your original, just overwrite it with IONetworkingFamily.kext.

 

Also stop looking at the kext files as files, look at them as if they are folders or zip files, they have contents inside them that are easily read and modified by end users and sometimes contain multiple kext files for various hardware configurations.

 

Also I can not tell you much about your fans going crazy issue... I have the exact same laptop and dsdt obviously with BIOS A04 installed and had A01 and both times the cpui_snow.kext never caused my fans to go crazy for any reason.. cpui_snow.kext is specifically so that the cpu-i app can monitor speedstepping.

 

Only other thing I can think of is for you to check for a nullcpupowermanagement.kext in SLE and if you have it remove it.

 

I am trying what you suggested now, and will report back. No "nullcpupowermanagement.kext" in SLE.

 

Thanks for the clarification on kext files. I understand better now. If I spent more time in Mac-land I would probably know a lot more. My life and business are Windows-world, so....

 

Lastly, could you just give a brief overview of what I need to do to change the smbios.plist file so the OS thinks I have a real Mac?

 

Again, much thanks for spending the time! Hopefully, some of this info will be useful to others in the future who are just starting out!

 

 

 

UPDATE: Still no ethernet. Removed the IONetworkingFamily.kext from my SLE folder and put in the kext from yours instead,

and ran the kext utility to fix permissions and rebooted.

 

Same ol' thing...it senses I have a cable plugged in (or when I have it unplugged), but that's it. Just get the 169.254.173.158 self-assigned IP address.

 

Ughhh...this shouldn't be rocket science for cryin' out loud! Thank god for WiFi!

 

Can I troubleshoot this with console or terminal or some other app?

[glitchbit]

Well I had vaguely been remembering that another kext file inside IONetworkingFamily may need deleting and I just found the reference somewhere here.

 

"delete the realtek 8169 kext from within the plugins folder and then install this kext

http://psystar.com/realtek_r1000_driver.html"

 

the psystar link is broken and might not help you anyways.. and if you are using my networking kext file in either EE or SLE location then it ought to work because I already deleted 8169.. which I do not think anyone here mentioned to do but I searched the issue enough to find the answer awhile back.. so I am not sure what to tell you on your ethernet issue..

 

Only suggestion I can give is use the search here or use google. One trick I use often is I type in "site:insanelymac.com my issue here" into google without quotations and I almost always find my answers fairly quick. If I don't then I am probably not asking the right question or need to rephrase it and a lot of times after reading enough posts even if I am asking the wrong question I can usually find out what the right question is.

 

Only other question I have is if you are dual booting windows? I know if bluetooth is ever disabled inside windows then OSX will detect it but not activate it.. so maybe the same could apply to the ethernet port.. but if you never explicitly disabled it inside windows then I see no way for that to have happened.

[lancorp]

Well I had vaguely been remembering that another kext file inside IONetworkingFamily may need deleting and I just found the reference somewhere here.

 

"delete the realtek 8169 kext from within the plugins folder and then install this kext

http://psystar.com/realtek_r1000_driver.html"

 

the psystar link is broken and might not help you anyways.. and if you are using my networking kext file in either EE or SLE location then it ought to work because I already deleted 8169.. which I do not think anyone here mentioned to do but I searched the issue enough to find the answer awhile back.. so I am not sure what to tell you on your ethernet issue..

 

Only suggestion I can give is use the search here or use google. One trick I use often is I type in "site:insanelymac.com my issue here" into google without quotations and I almost always find my answers fairly quick. If I don't then I am probably not asking the right question or need to rephrase it and a lot of times after reading enough posts even if I am asking the wrong question I can usually find out what the right question is.

 

Only other question I have is if you are dual booting windows? I know if bluetooth is ever disabled inside windows then OSX will detect it but not activate it.. so maybe the same could apply to the ethernet port.. but if you never explicitly disabled it inside windows then I see no way for that to have happened.

 

No dual boot. Just SL 10.6.2.

 

OK, just to clarify everything, this is what I did. In SLE I removed the IONetworkingFamily and Realtek1000 kexts and ran the kext utility to fix things up. Then I put YOUR IONetworkingFamily.kext in EE folder and ran the kext utiity to fix up again. Rebooted. Upon reboot, double-checked that SLE did not have IONetworkingFamily or Realtek1000. Plugged in ethernet cable. Same thing. Shows cable connected, but then self-assigned IP. Now, though, I think I know what was causing my fans to go high speed all the time...plugging in the ethernet cable. I tried it a few times (rebooting between each), and everytime I plug in the ethernet cable, within a few seconds my fan starts going high speed. I check activity monitor, and kernel_task is 60-70%. Unplugging the ethernet does not resolve it. I have to reboot (which, for some reason now, when I shut down or reboot, I get a black screen but the system does not shut down or reboot. It's like in some hung state that requires I push and hold the power button).

 

Anyways, when I start up and use -v to start, I see a bunch of REALTEK stuff go by. Is there any way to pause or capture that and post it? Maybe you or someone can figure out what is not happening the way it should?

 

One other thing, what program do you use to monitor if speedstep is working? I thought it was cpu-i, but a google for it did not show anything in the first couple of pages of results. Do you have a link to download? I want to confirm that my CPU speed is not fixed at high speed all the time (since my fan does seem to abnormally go on/off a lot).

 

I'll celebrate the day I get this dam ethernet working!

[glitchbit]

cpu-i is not the easiest app to find I will try to link you later. Inthe mean time try booting up with -v -f, -f will help you to force osx to check/load your kext files.

[amartins02]

So I check back on here every now and then to check progress on this project. I can't really install OSX on my 14z unless its stable because I use it for school. The main thing I like is the battery life (5.5-6 hrs). What are you guys getting for uptime? Also, realistically, if I install OSX am I gonna have to tweak the thing everyday to try and fix something? I built a Mac Pro hackintosh desktop and have never had any issues and would like the same with the 14z.

 

Thanks

[glitchbit]

So I check back on here every now and then to check progress on this project. I can't really install OSX on my 14z unless its stable because I use it for school. The main thing I like is the battery life (5.5-6 hrs). What are you guys getting for uptime? Also, realistically, if I install OSX am I gonna have to tweak the thing everyday to try and fix something? I built a Mac Pro hackintosh desktop and have never had any issues and would like the same with the 14z.

 

Thanks

 

My response to your your question is that it is very stable, and why lancorp can't get his networking working is a mystery to me and probably the rest of us 14z users. Basically as long as the kext is placed inside the plugins folder of the IONetworkingFamily kext then it works.. But sadly that part I do not think was mentioned in this thread until I said something.. guess everyone thinks it is a common knowledge or something and then I end up forgetting about it, sorry =(.

 

Anyways as long as you read this entire thread and download the kext files I posted then I see no reason why you should have any issues with the install of OSX on it. As far as I can tell OSX runs just as good on this machine as it did on my gigabyte desktop which had a quad core 9300 I think it was and I just dismantled it, because I want to consolidate. I also use my hdmi out every day with my 25.5" and like I said the only 2 issues I have is with the secondary audio out port (primary one works fine though) and HDMI audio..

 

Everything else works perfectly and as far as the bugs that I posted regarding the mouse.. well that has gone away ever since I got rid of the sleepenabler kext (because I did not realize the nullcpupowermanagement kext was installed by my SnowOSX distro). The issues I had with my beachball freezing my computer upon boot up for about 1-2 minutes has gone away ever since I disabled firewire in my bios, I believe it works though from what others have said but since I rarely use firewire I will leave it disabled most of the time.

 

For some reason though in windows 7 my 8 cell battery gives me 4.5 hours and not 5.5-6hrs.. maybe I will contact dell. In OSX I get 4 hours though.. so I lose about 30 minutes or about 11% of my battery life.

[amartins02]

Ok. Thanks for the reply. Yea I have an 8 cell and the thing performs pretty well. If I lose a half hour thats not to bad. I'm not super worried about the 2nd audio out port because I only use one anyways. Not worried about the HDMI either. Aside from that if everything else is fine then I might give it a go and see how it does.

 

APPLE EVENT TOMORROW! Hope its a tablet or else it better be pretty impressive!

[lancorp]

Is anyone (which over the past week seems to only be glitchbit and amartins02) having issues with the trackpad?

 

Mine works, but I wanted to use tapping-as-click features so I enabled the track pref pane in System Preferences.

The thing is, my settings for tapping/clicking only work during a session. When I reboot or turn on, no tapping/clicking.

 

When I go into the Trackpad pref pane, it says that System Preferences must close and reopen to use the Trackpad Preferences Pane. Why? Also, why am I losing the tapping/clicking ability every time I reboot? Having to go into the Trackpad settings each time is getting tiring! (note that when I do go into the preferences, the settings are still enabled, they just don't work unless I toggle them off and back on.

 

Any ideas?

[GAOO]

Hey Glitchbit,

 

Nice to see that you have made a lot of progress for the Studio 14z

 

I'm thinking about replacing my current OSX install with Snow Leopard, and based on what I read:

- You recommend SnowOSX

- Brightness control works for you with Bios A04

- Speedstep works for you

- And many other things also works

 

I'm wondering, are you dual booting your SL install with a windows install? Also, how difficult was it to get everything working from SnowOSX? (After SnowOSX installation, is it just a matter of placing your DSDT and a few other Kexts?)

 

I currently dual boot Win7 and OSX 10.5.8. The only reason I'm thinking about replacing Leopard with SL is because the iPhone SDK for iPad requires Snow Leopard

 

 

Much appreciated if you could share any info.

 

Thanks,

GAOO

[glitchbit]

Is anyone (which over the past week seems to only be glitchbit and amartins02) having issues with the trackpad?

 

I rarely tap to click, but it is handy to know that toggling on and off fixes it for a bit.. I don't have any suggestions for that issue at the moment, but I am sure other users here in these forums probably have ran into the same issue on other laptops.

 

 

I'm thinking about replacing my current OSX install with Snow Leopard, and based on what I read:

- You recommend SnowOSX

- Brightness control works for you with Bios A04

- Speedstep works for you

- And many other things also works

 

I'm wondering, are you dual booting your SL install with a windows install? Also, how difficult was it to get everything working from SnowOSX? (After SnowOSX installation, is it just a matter of placing your DSDT and a few other Kexts?)

 

I recommend SnowOSX because it is the only one I tried.. I really dislike the idea of installing leopard and then having to turn around and install Snow Leopard off of some usb stick. I know some people are dead set against installing distros but so far I have downloaded 3 separate updates from Apple and while they did break my wireless once I simply copied my wireless kext back into SLE and was back up and running in no time. Also I did have to download a wireless kext someone posted which I guess now I have reposted in the page previous. Basically that wireless package you posted GAOO, I do not think is Snow Leopard compatible at least it was not for me.

 

Brightness controls work 90-95% of the time for me, and I do play with it almost every day. Rebooting always seems to fix it, although nullCPUPowermanagement could have caused the 5-10% of issues I had. Speedstepping does indeed work, and it would have worked for me a lot sooner had I realized that SnowOSX installs nullcpupowermanagement.kext which also kills sleep (so I had used sleepEnabler for awhile but it also creates issues with the mouse).

 

And the bluetooth definitely works well, bcc9 or whoever you (GAOO) got your bluetooth kext from has updated it and it works without scripting now. I did have to boot into W7 to enable bluetooth first however. (not important if you never disabled it )

 

Also I simply shrinked my W7 partition down and then I either formatted the space as ntfs or I used hiren's boot cd and used one of its partitioning tools to format it fat32 and then I installed SnowOSX like normal. I have not enabled any GUI for the bootup, so I just see your standard Darwin text and I can boot into W7 just fine (it has a 2 second delay which is fine by me). I also backed up W7 first, but did not need to use it. Dual booting has made me uneasy since the 10.4.8 days but it has improved a lot since then.

 

For newcomers SLE is short for System\Library\Extensions

EE is short for Extra\Extensions

 

On the kexts I posted earlier, these are the ones I use in SLE

(I placed these in there myself)

DellBluetoothHCI.kext -EE?

VoodooBattery.kext -This really ought to go in EE

IO80211Family.kext - I don't think this one works in EE..

BroadcomUSBBluetoothHCIController.kext - EE?

 

(The following SnowOSX will install for you)

AppleACPIPS2Nub.kext -unsure of its affects

LegacyAppleAHCIPort.kext -unsure

ApplePS2Controller.kext - I think I tried removing this one and it killed my trackpad..

LegacyIOAHCIBlockStorage.kext -unsure

PlatformUUID.kext -unsure

fakesmc.kext -unsure, I think this needed to boot up right =P DSMOS

IOATAFamily.kext -unsure

*nullCPUPowerManagement.kext (I did not include this with my post earlier, because it has to be deleted for sleep and speedstep to work)

 

I put unsure by those that I am unsure of their necessity, but I am running with them.

 

And for the EE folder this is what I currently have

CPUi_snow.kext * included earlier but not needed, but it lets me monitor speedstepping

HDAIDT.kext

EvOreboot.kext

IONetworkingFamily.kext

 

I guess the only other thing I would like to note is that SnowOSX installs an Atools folder in Applications which is very helpful with various tools and a kext utility to help with resetting permissions on specific folders via drag and drop. It also has a folder in there which has various kexts.

 

Its funny but I just read

NullCPUPowerManagement - attaches in place of the real AppleIntelCPUPowerManagement which doesn't work right on PCs (kernel panic, cpu running hot)

And that file actually CREATES the issue it is supposed to avoid! It caused my cpu to run hot, issues with the mouse and sleeping (probably brightness controls too).

[lancorp]

And that file actually CREATES the issue it is supposed to avoid! It caused my cpu to run hot, issues with the mouse and sleeping (probably brightness controls too).

 

Unclear...which one creates the issue--NullCPUPowerManagement or AppleIntelCPUPowerManagement ??

 

Your sentence made it unclear which one we should be using...

 

Also, could you give us details on how to make the "About this Mac" show the correct info (was it something with SMbios.plist)??

 

Thanks.

 

ps. I found a treasure at the Outlet this morning...a Studio 14z with 900p LCD, 8 cell, backlit KB, and BT (all the options I am currently missing) for $480 after coupon!!! What a steal!! When it arrives, hopefully, I can just move my 256GB SSD from my current 14z to the new 14z and have it work!

[glitchbit]

Unclear...which one creates the issue--NullCPUPowerManagement or AppleIntelCPUPowerManagement ??

 

Your sentence made it unclear which one we should be using...

 

Also, could you give us details on how to make the "About this Mac" show the correct info (was it something with SMbios.plist)??

 

Thanks.

 

ps. I found a treasure at the Outlet this morning...a Studio 14z with 900p LCD, 8 cell, backlit KB, and BT (all the options I am currently missing) for $480 after coupon!!! What a steal!! When it arrives, hopefully, I can just move my 256GB SSD from my current 14z to the new 14z and have it work!

 

dang!@#$! That was an extremely good deal, how much was it before coupon?!? You can't even buy the iPad for that money and you practically got a macbook pro! I paid $640 and after shipping and tax it came to $691.. still even at that price this laptop is a really good deal.

 

The context of my statement about the power management kext was that nullCPUPowerManagement was suppose to help keep the cpu running cool and prevent issues but instead on my 14z it created problems and a hotter cpu. So yes remove nullCPUPowerManagement!! Someone else in these thread I believe also says not to use it.

 

For smbios.plist just copy it to your desktop and open it in textedit and change iMac9,1 or whatever it says to MacBookPro5,5. That will make it appear like it is the newest 13" macbook pro. Some kexts though may perform better with different names set! I have not tried all the different combinations, but I do know that the MacPro names cause a KP on boot up, and iMac9,1 works (SnowOSX's default).

 

<key>SMproductname</key>

<string>iMac9,1</string>

 

Some people are using the hazardly release so I cannot say what it calls itself, look for SMproductname though. Once you have changed it then just drag and drop that file back to Extra. If you cannot boot up right then boot into safe mode using -x -v and rename the string back to whatever it was.

[glitchbit]

I removed everything that was not vanilla from SLE and I am only using these files in EE.

 

AppleACPIPS2Nub.kext

HDAIDT.kext

VoodooBattery.kext

ApplePS2Controller.kext

IO80211Family.kext

fakesmc.kext

CPUi_snow.kext

IONetworkingFamily.kext

EvOreboot.kext

PlatformUUID.kext

 

And I deleted the two Legacy kext files I posted earlier, for now anyways. Also I replaced IOATAFamily with an original and I put an original IO80211Family.kext in SLE as well. So far so good and as far as I can tell I am now running completely vanilla. It irritates me now to know that whoever made SnowOSX did not place these files in the Extra/Extensions folder to begin with.

 

http://www.mediafire.com/?mfjxa5mztxi

[glitchbit]

trying to work out a fix for usb not ejecting properly on sleep.. I forgot about that issue..

 

Seems our options are to either fix it in the dsdt which bcc9 found some good info on but it does not work for our model.. or we edit and recomple AppleUSBEHCI.kext inside the Plugins folder of the IOUSBFamily.kext.

http://www.insanelymac.com/forum/index.php...t&p=1097648

 

I have tried a lot of variations of the fix bcc9 mentioned for it earlier and have been unable to get it to work, I also renamed the _PWR method to an actual Name entry instead as well. I also put the fix both before and after, however I would like to put in the memory address of the usb ports as described here but I have ran out of time to try it tonight so please anyone give it a shot! http://www.insanelymac.com/forum/index.php...68014&st=20

 

In the meanwhile these two workarounds my suffice

http://vocaro.com/trevor/blog/2007/02/11/a...efore-sleeping/

http://www.macosxhints.com/article.php?sto...080329201951648

 

I would also really appreciate it if someone was to post a dsdt file belonging to the macbookpro5,5??

[lancorp]

dang!@#$! That was an extremely good deal, how much was it before coupon?!?

 

$569 - 15%. And, it's RED.

 

Thanks for the info on the SBMbios.plist stuff. Mine had MacPro3,1...I changed it to MacBookPro5,5 and rebooted OK.

Nothing seemed to change much though. How do I get the CPU to in the About this Mac to show the correct processor instead of Unknown?

 

Thanks for all your help. Wouldn't it be great if my new Red one actually had working Ethernet!

[Mark Downing]

For the 1600x900, HannibalX didn't need any of the display overrides, only the Natit.kext to get his display working.

 

Can you tell me which distribution you're using? And what version of OSX? BTW, try just the Natit.kext alone.

 

If Natit.kext doesn't work, I don't think bcc9's DSDT would work... but you can give it a try.

 

 

 

 

 

Please tell me how to use the kext file(s) for the Dell Studio 1555 Dell 1397 WLan wireless?

 

I am new to OSX and don't know how to use these kext files. I understood you to say that we can use the broadcom file? How so?

 

 

 

Respectfully

 

Mark Downing

[Mark Downing]

I don't have the Dell 1515 wireless. I chose wisely when I ordered :-)

 

430-2929 Dell Wireless 1397 802.11g Half Mini Card

 

It is working, but I had to edit AppleAirPortBrcm4311.kext to add pci14e4,4315.

 

If I could change it to mask itself as 4313 in the DSDT, it'd run with no edits.

 

 

How do you edit and install this fix? I am unfamiliar with .kext files. Where is this one located? Where did you edit it to put in your pci code?

 

I have the Dell Studio 1555 which has the same 1397 wireless lan mini card.

 

Help please.

 

 

 

Mark Downing

[GAOO]

Hey Glitchbit,

 

I appreciate your response and all the info you provided. I have finished downloading SnowOSX 3.6 so I'll be installing it soon, but if you don't mind, I would appreciate it if you can answer some more questions of mine. There are a lot of info lying around but it's hard to make sense of them since they are so scattered and there are a lot of links as well.

 

- What customization options did you choose or recommend when installing SnowOSX?

- What should we expect after installation? In other words, what works right off the bat when we boot SL after installing SnowOSX?

- Is this still the DSDT you recommend?

- For the things that don't work right off the bat, would you mind compiling a zip of the kexts needed to make them work? I think you linked to some here, but the links are invalid now.

 

Much appreciated if you can, thanks.

GAOO

P.S. - BTW, all drivers I posted on the front page only works for REGULAR Leopard (10.5.x). Sorry if there were any confusions.

[glitchbit]

Hey Glitchbit,

 

I appreciate your response and all the info you provided. I have finished downloading SnowOSX 3.6 so I'll be installing it soon, but if you don't mind, I would appreciate it if you can answer some more questions of mine. There are a lot of info lying around but it's hard to make sense of them since they are so scattered and there are a lot of links as well.

 

- What customization options did you choose or recommend when installing SnowOSX?

- What should we expect after installation? In other words, what works right off the bat when we boot SL after installing SnowOSX?

- Is this still the DSDT you recommend?

- For the things that don't work right off the bat, would you mind compiling a zip of the kexts needed to make them work? I think you linked to some here, but the links are invalid now.

 

Much appreciated if you can, thanks.

GAOO

P.S. - BTW, all drivers I posted on the front page only works for REGULAR Leopard (10.5.x). Sorry if there were any confusions.

 

I do not recall exactly what customizations if any that I made during the install of SnowOSX.. I am willing to connect an eSata drive tomorrow though to check it though. But basically I do not think you have full control over what kexts it will install into S/L/E. Any modified files it places in there will be color coded and easy to spot however.

 

Right off the bat I think the resolution is off, battery icon is missing, the system will not sleep, or fully restart without pressing down the button. It works just fine though to get the dsdt and extensions installed.

 

I recommend only using these files that I have zipped up here inside Extra\Extensions\

http://www.mediafire.com/?mfjxa5mztxi

 

I personally use kext utility inside the Atools folder which you will find in applications to reset the permissions on both the Extra Extensions folder the System/Library Extensions folder (after you delete the color coded files). Just drag and drop the two extension folders on it and you are done.

 

Make sure that you delete all the modified (color coded files from SLE after you setup the EE folder, you can reboot first to make sure EE is working if you want before deleting the files in SLE)

 

I also forgot to mention that I did have an error that prevented me from repairing permisions via disk utility, so immediately after you instal snowOSX v3.6 you want to open Disk Utility and try to repair permissions and if it gives you an error about "No installer packages" then run this off the disc or mounted iso "/Volumes/Mac OS X Install DVD/System/Installation/Packages/BSD.pkg"

 

Also remove AppleHDA, which is an original file I believe in SLE.

 

And yes this dsdt is the one that I still personally recommend

http://www.insanelymac.com/forum/index.php...st&id=64651

 

I have several variations of it that I am currently working on. I also resolved all warnings that my dsdt compiler was giving me, but it does not seem to make my system perform better nor do they resolve any real issues yet. I am particularly trying to resolve the USB sleep issue of it disconnecting drives on sleep at the moment. I was working on the audio issue but I get the feeling the usb issue will be easier to fix.

[glitchbit]

How do I get the CPU to in the About this Mac to show the correct processor instead of Unknown?

 

I wonder if having different cpu's affects the DSDT file? Mine is T6600, what is your model?