Jump to content

[Guide] Dell Inspiron 6400/9400/1520/1720/E1405/E1505/E1705 Intel Core Duo

devilhood

By devilhood,
in Installation Guides

 Share
2,614 posts in this topic

Recommended Posts

rogabean
rogabean
Posted
Posted

Just to let you guys know (without saying anything that may or may not cause trouble here)... Another cat works great on the E1705/9400 with very few hacks with the exception of sleep and as a result lack of two cores... I could use some help from a few volunteers, but this would require you to have the needed files. PM me... If you have trouble keeping your Tiger going on this hardware or have never worked on fixing things yourself and found results... don't PM me please. I'm sorry but I'm going to be selective right now on who can help with this for obvious reasons.

Link to comment
Share on other sites
msh
msh
Posted
Posted

I have problem with Opera Browser.Is very slow in OS X.

In WinXP it's very fast,but in OS X is Struttering alot when i move side up and down.

Is this because of Titan driver?Or it can be something else that cause this problem?

I have almost everything working now,thats only problem i got now.

 

I use Opera browser because it can zoom very good.

Link to comment
Share on other sites
devilhood
devilhood
Posted
  • Author
Posted
I have problem with Opera Browser.Is very slow in OS X.

In WinXP it's very fast,but in OS X is Struttering alot when i move side up and down.

Is this because of Titan driver?Or it can be something else that cause this problem?

I have almost everything working now,thats only problem i got now.

 

I use Opera browser because it can zoom very good.

 

As I have stated many times before to other people, do not use Titan, use DiaboliK's Natit.

 

Also, try out Opera's new weekly release here: http://my.opera.com/desktopteam/blog/

 

Link to the Mac version is at the top of the page.

Link to comment
Share on other sites
msh
msh
Posted
Posted
As I have stated many times before to other people, do not use Titan, use DiaboliK's Natit.

 

Also, try out Opera's new weekly release here: http://my.opera.com/desktopteam/blog/

 

Link to the Mac version is at the top of the page.

 

Ok Where can i download Diabolik´s Natit?(Link Dosent work)

Can i just install that driver over titan?Or do i need to uninstall that first?If so,how to uninstall titan driver?

 

Tnx

Link to comment
Share on other sites
devilhood
devilhood
Posted
  • Author
Posted
How do i uninstall titan.kext?

What do you mean with rm the kext?

 

You'd have known what it meant if you read through my guide.

 

rm is the remove command via Terminal.

 

Simply open up terminal and type:

 

sudo -s (enter password when it asks)

rm -r /System/Library/Extensions/Titan.kext

 

then make sure you remove the extensions cache by typing:

 

rm -r /System/Library/Extensions.kextcache

rm -r /System/Library/Extensions.mkext

 

Voila! you can then install Natit via the installer.

 

If you want to install Natit manually, copy the kext into /System/Library/Extension and type in Terminal:

 

sudo -s

chmod -R 755 /System/Library/Extensions/Natit.kext

chown -R root:wheel /System/Library/Extensions/Natit.kext

Link to comment
Share on other sites
msh
msh
Posted
Posted

Ok i install Natit driver,I got problem with sleep,my display won´t wake up from sleep.So i install titan driver back,and Sleep mode is working again.So every who have problem with sleep mode,is because of Natit driver.

Link to comment
Share on other sites
jcbklyny
jcbklyny
Posted
Posted

I'll start out by saying I'm sorry for posting another question about this same old topic...

 

But I just reinstalled Uphucks 1.4 r3 release and I'm having a real problem with my video drivers. No matter what I do I can't seem to fix this dame color banding issue.

 

Devil, I did exactly what you said in your original post and in numerous replies to others. I only selected PowerManagement & Natit 0.2 on Install. No problem. Once in OSX I installed Mobility, LaptopDisplay and NvidiaEFI (I used the version of EFI you attached in one of your posts here). Reboot... and nothing changes. Same color banding issue.

 

I get a long slow fade to a full white screen before OSX kicks in and continues to load.

 

Is there another driver in the r3 release that needs to be removed? And yes, I am using cpus=1 to disable the second core.

 

 

 

 

My Setup:

E1705

Nvidia go7900 GS

2 Ghz Intel Core 2 Duo

2 Gigs of Ram

250 GB SATA 7200 RPM Hard Drive (Toshiba)

Link to comment
Share on other sites
devilhood
devilhood
Posted
  • Author
Posted
No it´s 8.9.1 Is 8.10.1 faster then 8.9.1?

 

If there is a speed difference, it will be negligible, but I'd stay with 10.4.9 until Apple release the source for the 10.4.10 kernel otherwise you wont have the same SpeedStep/ACPI support like with the current 8.9.1 kernel.

Link to comment
Share on other sites
tbcarey
tbcarey
Posted
Posted

It's as I suspected:  AppleHDAPatcher has hard-coded pin configurations it applies to AppleHDA,

irrespective of the actual values supplied through the codec dump. Essentially, AppleHDAPatcher

only scans the codec dump for codec ID and subsystem, and then makes assumptions about

the correct pin configurations, nodes, and pathmaps based upon this.  In other words, nearly

everything AppleHDAPatcher does for Dell STAC9200 variants is completely wrong.

 

I've fixed the pin configurations and the pathmaps manually, however. This just means when I

release the changes I've made, it will have to be as a full kext rather than a few files you can

apply to the results of your AppleHDAPatcher run. This is for the best anyway, as AppleHDAPatcher

also uses its own (older) versions of AppleHDA and AppleHDAController rather than patching

the files in your /System/Library/Extensions directory.

 

Here are the pin configuration values I am currently using, along with what they signify:

 

Port A: 0x0d - 0x0421101f - Jack on External Chassis / Right Side / Headphones / 1/8 inch Jack / Black Jack / Jack Detect Override / Pin Group 1 / Unique Sequence #F

Port D: 0x0e - 0x90170110 - Fixed in Internal Chassis / No Jack Location / Speaker / Analog Connection / No Jack Color / Misc 1 (Reserved) / Pin Group 1 / Unique Sequence #0

Port C: 0x0f - 0x408000f2 - No Connection on External Chassis / No Jack Location / Line In / No Connection Type / No Jack Color / Jack Detect Override / Pin Group F / Unique Sequence #2

Port B: 0x10 - 0x04a11020 - Jack on External Chassis / Right Side / Mic In / 1/8 inch Jack / Black Jack / Jack Detect Override / Pin Group 2 / Unique Sequence #0

Mono Out: 0x11 - 0x90170111 - Fixed in Internal Chassis / No Jack Location / Speaker / Analog Connection / No Jack Color / Misc 1 (Reserved) / Pin Group 1 / Unique Sequence #1

 

 

Theoretically, this should fix the jack detection muting problem -- AppleHDAPatcher was previously setting the pin configuration for Port D to

a 1/8 inch jack on the external chassis rather than an internal speaker device -- but unfortunately, it hasn't. Kind of tearing my hair out about

this, but I'm sure it will come together soon.

 

..and attached, a simplified widget node schematic for the STAC9200, in case anyone out there is doing similar work and happens to not be as slow as I am when it comes to fixing these problems!

post-93079-1187080362_thumb.png

Link to comment
Share on other sites
devilhood
devilhood
Posted
  • Author
Posted
It's as I suspected:  AppleHDAPatcher has hard-coded pin configurations it applies to AppleHDA,

irrespective of the actual values supplied through the codec dump. Essentially, AppleHDAPatcher

only scans the codec dump for codec ID and subsystem, and then makes assumptions about

the correct pin configurations, nodes, and pathmaps based upon this.  In other words, nearly

everything AppleHDAPatcher does for Dell STAC9200 variants is completely wrong.

 

I've fixed the pin configurations and the pathmaps manually, however. This just means when I

release the changes I've made, it will have to be as a full kext rather than a few files you can

apply to the results of your AppleHDAPatcher run. This is for the best anyway, as AppleHDAPatcher

also uses its own (older) versions of AppleHDA and AppleHDAController rather than patching

the files in your /System/Library/Extensions directory.

 

Here are the pin configuration values I am currently using, along with what they signify:

 

Port A: 0x0d - 0x0421101f - Jack on External Chassis / Right Side / Headphones / 1/8 inch Jack / Black Jack / Jack Detect Override / Pin Group 1 / Unique Sequence #F

Port D: 0x0e - 0x90170110 - Fixed in Internal Chassis / No Jack Location / Speaker / Analog Connection / No Jack Color / Misc 1 (Reserved) / Pin Group 1 / Unique Sequence #0

Port C: 0x0f - 0x408000f2 - No Connection on External Chassis / No Jack Location / Line In / No Connection Type / No Jack Color / Jack Detect Override / Pin Group F / Unique Sequence #2

Port B: 0x10 - 0x04a11020 - Jack on External Chassis / Right Side / Mic In / 1/8 inch Jack / Black Jack / Jack Detect Override / Pin Group 2 / Unique Sequence #0

Mono Out: 0x11 - 0x90170111 - Fixed in Internal Chassis / No Jack Location / Speaker / Analog Connection / No Jack Color / Misc 1 (Reserved) / Pin Group 1 / Unique Sequence #1

 

 

Theoretically, this should fix the jack detection muting problem -- AppleHDAPatcher was previously setting the pin configuration for Port D to

a 1/8 inch jack on the external chassis rather than an internal speaker device -- but unfortunately, it hasn't. Kind of tearing my hair out about

this, but I'm sure it will come together soon.

 

..and attached, a simplified widget node schematic for the STAC9200, in case anyone out there is doing similar work and happens to not be as slow as I am when it comes to fixing these problems!

 

I only wish I had the time to help you with this project, but from the looks of things it seems as though you are getting closer and closer to solving this.

 

PM me your PayPal and I'll donate a few bob if this turns out to be a success!

Link to comment
Share on other sites
Bourasque
Bourasque
Posted
Posted

I have seen a few posts about people not being able to mount/open DMG files after X or Y updates/changes. I had the same happen to me and the following fixed my problem.

 

sudo kextunload -c com.apple.AppleDiskImageController
sudo kextload -b com.apple.AppleDiskImageController

 

Though for some reasons, the problem comes back every now and then (haven't figured out what triggers it yet). I suggest you copy these two lines in a .txt or something for easier access the next time you happen to run in the problem again.

 

To tbcarey :

 

I am anxiously following your progress. PM me your paypal info for a donation if you are interested. I can't wait to listen music with my headphones on without realizing 5 minutes later that I have bothered everyone at work for the sake that I listen to hardcore music. Good times

 

/personal diary off.

 

Good day

Link to comment
Share on other sites
adude123
adude123
Posted
Posted
I'll start out by saying I'm sorry for posting another question about this same old topic...

 

But I just reinstalled Uphucks 1.4 r3 release and I'm having a real problem with my video drivers. No matter what I do I can't seem to fix this dame color banding issue.

 

Devil, I did exactly what you said in your original post and in numerous replies to others. I only selected PowerManagement & Natit 0.2 on Install. No problem. Once in OSX I installed Mobility, LaptopDisplay and NvidiaEFI (I used the version of EFI you attached in one of your posts here). Reboot... and nothing changes. Same color banding issue.

 

I get a long slow fade to a full white screen before OSX kicks in and continues to load.

 

Is there another driver in the r3 release that needs to be removed? And yes, I am using cpus=1 to disable the second core.

My Setup:

E1705

Nvidia go7900 GS

2 Ghz Intel Core 2 Duo

2 Gigs of Ram

250 GB SATA 7200 RPM Hard Drive (Toshiba)

 

I'll second that (I also posted in this thread before). I have the same NVidia (except Core 1 Duo and Uphuck 1.3). No matter how many times I've reinstalled with different kernels and versions and kexts, I still have a color-banding issue.

Link to comment
Share on other sites
adude123
adude123
Posted
Posted
Perhaps the colour banding issue can be related to differing LCD panels?

 

Is there any way to find out which one I have? In Vista under Device Manager, it simply says "Generic PnP Monitor," and I couldn't even find any drivers at support.dell.com. If it helps, I have the WUXGA Glossy screen.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...