QUOTE(dhomi @ Jun 17 2008, 10:15 AM)

Thanks, your kext did help me recover my connection (although I still have to use the wizard to activate it each time I boot).
Further research and testing has brought me to the conclusion that installing the older 10.4.x Airport kexts in 10.5 is a bad move.
The dependancies are broken and this is a contributing factor to non-functional wireless adapters.You are far better off rebranding the device than you are installing those kexts, performance is superior and the device tends to be more compliant with the environment and the OS in general.
The bigger issue is knowing which chipset should bear which ID's.Having the wrong ID's is just as destructive as having the wrong kexts, wrong drivers are loaded and the potential for a panic increases.
I've played with Broadcom and Atheros cards, I've had very good luck rebranding cards and I'm careful to select ID's that closely match the device being modified to ensure the correct driver is being loaded.
The secret is knowing which chipset is contained in the device.
WMP300N (LinkSYS) I set subsys ID's to 0x106b,0x0087 (unfortunately you can't modify this card due to lack of software).
WMP54GS (LinkSYS) I set subsys ID's to 0x106b,0x004e (you can change this adapter).
All BCM4306 a/b/g miniPCI cards I set subsys ID's to 0x106b,0x004e (you can change this adapter).
All BCM4309 a/b/g miniPCI cards I set subsys ID's to 0x106b,0x004e (you can change this adapter).
All BCM4318 a/b/g miniPCI cards I set subsys ID's to 0x106b,0x004e (you can change this adapter).
Atheros AR5001 (b/g) I set subsys ID's to 0x168c,0x0024 (you can modify this card due to lack of software).
Atheros AR5001EX (a/b/g) I set subsys ID's to 0x106b,0x004e (you can modify this card due to lack of software).
Atheros AR5005 (b/g) I set subsys ID's to 0x168c,0x0024 (you can modify this card due to lack of software).
Atheros AR5005X (a/b/g) I set subsys ID's to 0x106b,0x004e (you can modify this card due to lack of software).
Atheros AR5006 (b/g) I set subsys ID's to 0x168c,0x0024 (you can modify this card due to lack of software).
Atheros AR5006XS (a/b/g) I set subsys ID's to 0x106b,0x004e (you can modify this card due to lack of software).
Atheros AR5008 (b/g/n) I set subsys ID's to 0x106b,0x0085 (unfortunately you can't modify this card due to lack of software).
Atheros AR5008X (a/b/g/n) I set subsys ID's to 0x106b,0x0086 (unfortunately you can't modify this card due to lack of software).
One drawback to this approach is that you need to modify the ID's in your Windows driver (the .inf) file for the device to have continued support in windows.
Fortunately I was blessed with drivers from Broadcom that are WHQL so I don't have any issues with Broadcom cards, Atheros on the otherhand, I have to search and find drivers that are WHQL and contain the generic PCI ID's to match the device or modify existing drivers and ignore the not WHQL messages.
Another little secret, HP Pavilion Elite 9080, if you have one or can get your hands on one and it came with an HP PCI-Express wireless adapter, borrow it and stick it in your hack, you'll be very impressed, I would beg, borrow or trade a card of similar functionality just to obtain that one.
QUOTE(mister5317 @ Jul 8 2008, 11:49 PM)

I have gone through the steps listed on page one with no problems. The only noticeable differences are when I do
CODE
ls -l
I get
CODE
drwxr-xr-x@ 3 root wheel 102 Jun 5 13:37 IO80211Family.kext
Notice the at sign. Is that a problem? I have never seen the at sign in permissions before, what does that mean?Second, when I run
CODE
kextload AirPortAtheros5424.kext
I get
CODE
kextload: extension AirPortAtheros5424.kext is already loaded
Also, I am running Kalaway 10.5.2.When I look in my Network Preferences I can see an AirPort connection listed but I cannot turn AirPort on. When I click the 'Turn AirPort On' button, nothing happens.Does anyone have any suggestions and or ideas?One last question, how do I determine my exact wireless card in OS X? Is there something similar to the Devices Hardware List on XP?
It sounds like you have one of the AR2412 cards and while you can get it recognized, there is no compatible driver in the Atheros kext and switching to the 10.4.x kext is a mistake despite what any one else tells you.
If you want to get your wifi working pm me your e-mail and I'll help you make it work.
Just understand that I'm not a patient person so resolving it quickly would be my goal, getting you to understand how or why doesn't even factor into the process otherwise your welcome to try and figure it out on your own.
I offer to help, you can accept or reject it, you can't reject now and expect to accept later, at that point I'd probably tell you "you should have accepted my offer when I made it" and that would be the end of it.
There are others on this forum who can tell you I have resolved their wireless issues, even by providing a driver for a device that none publicly seem to exist for.
It's up to you now.