#61
Posted 02 January 2008 - 07:00 PM
i'm wondering if this is the same one as that in you post:
" 4318, Broadcom BCM4318 [AirForce One 54g] 802.11g Wireless LAN (confirmed)" ?
many thanks
#62
Posted 12 January 2008 - 11:07 AM
This is what my script is for. Actually this is the only thing it does: it just adds some PCI-IDs.I have to put my hardware PCI id in AppleAirPortBrcm4311's Info.plist file:-
/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AppleAirPortBrcm4311.kext/Contents/Info.plist
Yeah, I might add Leopard support later. For now only Tiger is supported.With Tiger Works great
With Leopard: Kernel Panic!!!
Yes it's the same one. This is actually just the name of the chipset shown by "lspci" under Linux.my card is Broadcom BCM4318 802.11b/g Wireless Network Adapter
i'm wondering if this is the same one as that in you post:
" 4318, Broadcom BCM4318 [AirForce One 54g] 802.11g Wireless LAN (confirmed)" ?
many thanks
regards,
mcsmart
#63
Posted 25 January 2008 - 03:32 AM
http://forum.insanel...showtopic=83428
#64
Posted 26 January 2008 - 11:00 PM
If I use the Airport utility, it finds nothing. I click on the Airport icon at the top, Airport: Not Configured. If I go to network preferences, click "Assist Me..." and go through the motions, it finds my router and allows me to enter the password. However, next screen it says "cannot connect to internet." So, I close the assistant window and look at network preferences... Connected, with an assigned IP address. All is good.
If I go to system profiler, then down to Airport card, it says "AirPort is currently turned off" when I am clearly connected.
Still quite odd that Airport is not seeing it correctly.
It would be cool if somebody had any ideas as to how to get Airport to be seen as "enabled." Any thoughts?
#65
Posted 26 January 2008 - 11:15 PM
It seems after running the assistant, and then trying to initialize the card, it works. Did for me, anyways.
#66
Posted 27 January 2008 - 04:17 AM
Thanks for the tip though, I'll remember that.
#67
Posted 27 January 2008 - 10:08 AM
Thanks for the hintI would add this model to the first post, for the sake of forum Newbies
Good to hear. Did you do a reboot in the first place?Well, oddly enough, I rebooted and now its working perfectly. Huh, thats weird. Works absolutely great now. It even automatically connected to my network, with other options.
#68
Posted 30 January 2008 - 12:35 AM
Using deadmoo 10.4.1 image
EDIT: Found it on a spare Leopard install disc. Somebody should post it in case someone doesn't have it.
#69
Posted 01 February 2008 - 06:48 AM
One odd bit -- before running the script, 'Built in Ethernet' in the network panel was dithered out. After running the script, it is available and I can set configuration options for it. I plugged into a wired network w/ dhcp, but it didn't seem to detect it.
Is is possible that, since I don't have a driver yet for my wired ethernet, it is looking at the first ethernet adapter it finds (the wireless, in this case) and assuming it's the 'built in ethernet'?
How could I correct this?
#70
Posted 01 February 2008 - 03:14 PM
#71
Posted 01 February 2008 - 04:55 PM
Is is possible that, since I don't have a driver yet for my wired ethernet, it is looking at the first ethernet adapter it finds (the wireless, in this case) and assuming it's the 'built in ethernet'?
How could I correct this?
It looks like that's exactly what's happening. Digging around, I found in the Network Utility the Info section. There, for interface en0, it lists Vendor as "Apple", model as "Wireless Network Adapter".
I'm still trying to get my Yukon 8036 adapter working, but until then, what do I need to do to get the broadcom adapter recognized / configured as an airport card, rather than as en0 ?
#72
Posted 01 February 2008 - 08:31 PM
/Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
(after modifying the kext)
<key>IOInterfaceUnit</key> <integer>0</integer>
This did the trick for me and i could configure the card with Airport. Earlier it was like a simple ethernet device..
#73
Posted 01 February 2008 - 10:28 PM
Now, off to try and figure out how to get some sound.
#74
Posted 02 February 2008 - 10:32 AM
If you got a modified kext, your script will make it unusable because it just writes the string section and the rest disappears.
Maybe you also could add my earlier post (link)
to the FAQ on the first page. I see thats exactly whats causing many people trouble
#75
Posted 03 February 2008 - 01:12 PM
What do you mean by modified kext? It is recommended to install Apple's AirPort-Update before running the script... Then you should get a vanilla-kext.@mcsmart:
If you got a modified kext, your script will make it unusable because it just writes the string section and the rest disappears.
Thanks for that hint.Maybe you also could add my earlier post (link)
to the FAQ on the first page. I see thats exactly whats causing many people trouble
Regards,
mcsmart
#76
Posted 03 February 2008 - 01:34 PM
What do you mean by modified kext? It is recommended to install Apple's AirPort-Update before running the script... Then you should get a vanilla-kext.
Thanks for that hint.
Regards,
mcsmart
Some days ago i experimented with the .kext from tubgirl's v10.4.10 . Seems the AirPort Update is already integrated.
Anyway the kext already contained the IDs of additional wireless adapters and as i ran your script the .kext was a completely mess
#77
Posted 04 February 2008 - 08:55 PM
#78
Posted 05 February 2008 - 02:07 PM
Is it a USB card or PCMCIA? With PCMCIA you probably won't have any luck. USB could work: plug it in and see what happens. Especially the output of "sudo dmesg" should be interesting.I got a motorola wn825g wireless card that has a broadcom chipset in it but I dont know how to configure it. I already have the AppleAirPortBrcm4311.kext with the pcid 4320 in it. All help to configure the card would be much appreciated.
mcsmart
#79
Posted 06 February 2008 - 04:33 AM
#80
Posted 07 February 2008 - 10:16 AM
Yeah, see: PCMCIA is sort of a problem. You should first be sure that your PCMCIA controller is working, and only very few chipsets are supported by OSX86. You can try to attach the output of dmesg to one of your posts.Thanks for a quick reply. It is a PCMCIA card not USB. I ran the command 'sudo dmesg' and it displayed a lot of information which i dont understand which included something about the ethernet. (I have my ethernet working).
But trust me: just get a new USB wireless card (check the forum for recommended cards) and life will be a whole lot easier for you
regards,
mcsmart
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users



Sign In
Create Account





