Jump to content
235 posts in this topic

Recommended Posts

The first question we need to ask is: why did we have to use the Darwin kext in the first place? What was different in the 10.4.1 kext on the DVD (version 3.5, 636k) compared to the Darwin kext (version 3.5, 452k)?

 

The 10.4.3 kext on the DVD is version 4.0.3 (684kb) and comes up with the following error:

 

taks-computer:/system/library/extensions root# kextload -t AppleAirport2.kext

can't add kernel extension AppleAirport2.kext (validation error) (run kextload on this kext with -t for diagnostic output)
kernel extension AppleAirport2.kext has problems:
Validation failures
{
"Executable file doesn't contain kernel extension code" = true
}

 

This is the same error we get if we load the 10.4.1 kext from the DVD in 10.4.1. It seems that these kexts aren't complete (or perhaps they are for PPC?).

 

The 10.4.3 kext's plist has added support for another wireless card, as I mentioned here

 

The Darwin driver needed a fix (additional functions that were missing) but worked great after adding them (as you all know).

The first question we need to ask is: why did we have to use the Darwin kext in the first place? What was different in the 10.4.1 kext on the DVD (version 3.5, 636k) compared to the Darwin kext (version 3.5, 452k)?

 

The 10.4.3 kext on the DVD is version 4.0.3 (684kb) and comes up with the following error:

 

taks-computer:/system/library/extensions root# kextload -t AppleAirport2.kext

can't add kernel extension AppleAirport2.kext (validation error) (run kextload on this kext with -t for diagnostic output)
kernel extension AppleAirport2.kext has problems:
Validation failures
{
"Executable file doesn't contain kernel extension code" = true
}

 

This is the same error we get if we load the 10.4.1 kext from the DVD in 10.4.1. It seems that these kexts aren't complete (or perhaps they are for PPC?).

 

The 10.4.3 kext's plist has added support for another wireless card, as I mentioned here

 

The Darwin driver needed a fix (additional functions that were missing) but worked great after adding them (as you all know).

 

i actually get a different error, but seeing as how im using a live cd to get online (i dont have wireless or wired working ;), i cant post it. )

well, i got bluetooth running, and am now using internet via my smartphone, albiet im only downloading at 5kps B). so here is the error i get when i try to load the kext from darwin:

 

extension /Users/fallingup/Desktop/osx/System/Library/Extensions/AppleAirPort2.kext/ appears to be valid

10AirPortPCI is not compatible with its superclass, 20IOEthernetController superclass changed?

kextload: a link/load error occured for kernel extension /Users/fallingup/Desktop/osx/System/Library/Extensions/AppleAirPort2.kext/

load failed for extension /Users/fallingup/Desktop/osx/System/Library/Extensions/AppleAirPort2.kext/

(run kextload with -t for diagnostic output)

would it be possible to make a kext for the card that simply passes all of the calls from the kernel to the old kext and use it similar to the way a dll works in windows? seeing as how the old kext sources only need to be recompiled and not actually modified....i would do this myself but i am unfamiliar with the way OS X works

I used Maxxuss' Patch +addon patch to install to the second partition of my notebook drive. During the installation process the Broadcom wirless worked fine but showed as an Ethernet device.

 

After first reboot (after making 2nd partition active) wirless stopped working. This tells me that there is a working config/driver on the DVD....

 

I get the same kext errors as above and was looking for info on using/editing the kext's when I checked back here for other's progress.

 

 

Thoughts?

I used Maxxuss' Patch +addon patch to install to the second partition of my notebook drive. During the installation process the Broadcom wirless worked fine but showed as an Ethernet device.

 

After first reboot (after making 2nd partition active) wirless stopped working. This tells me that there is a working config/driver on the DVD....

 

I get the same kext errors as above and was looking for info on using/editing the kext's when I checked back here for other's progress.

Thoughts?

 

Same thing happened to me. com.apple.driver.AppleAirPortBrcm4311 is loaded, but AppleAirPort2.kext doesn't load. The interface shows up in ifconfig, so I think this means the driver is operational, but theres no way to configure the card. I'm looking into what process the installation disk used to configure the interface that doesn't survive a reboot.

Same thing happened to me. com.apple.driver.AppleAirPortBrcm4311 is loaded, but AppleAirPort2.kext doesn't load. The interface shows up in ifconfig, so I think this means the driver is operational, but theres no way to configure the card. I'm looking into what process the installation disk used to configure the interface that doesn't survive a reboot.

 

 

10.4.3 Working Wireless (dell 600 with Broadcom 1400)

 

Use /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/airport to configure the card

 

./airport -s scans for SSIDs (or ./airport -sNAME scans for "hidden" SSIDs)

 

./airport -ANAME associates with the network (where NAME is your SSID of choice), and prompts you for the key/password for encrypted networks.

 

./airport -I shows the current status

 

 

This won't survive a reboot, but its better than nothing at all..

 

op

 

EDIT: I was initially stated I was using a Dell 1300, which is incorrect. I'm using a Dell 1400, BCM4309 based card.

I have an NC6000 notebook. There is an icon at the top of the screen for Broadcom, and the only option is to turn the card off (any cardbus card that gets plugged in shows up here anyway, just an OS feature). I get some Bootstrap_status 1102 error when I do what ohpossum mentions (manually load the airport file).

 

Using an older WPC54G card by Linksys that has a Broadcom chipset anyway.

 

I noticed compiling drivers is a bit different. What sort of errors are people getting when trying to compile the Airport2 from Darwin8.1?

i have the darwin 8.1 source from the cd, but for some reason i am not able to use gcc, i have installed it, but i get command not found when im in terminal. Just wondering if i should always boot with platform=ACPI, if that would help discover my card, seeing as how i dont have a battery moniter... (i havent tried booting with that option yet) Hope yall can get a driver compiled for this, otherwise for now im stuck on windows... ;)

 

I used Maxxuss' Patch +addon patch to install to the second partition of my notebook drive. During the installation process the Broadcom wirless worked fine but showed as an Ethernet device.

 

After first reboot (after making 2nd partition active) wirless stopped working. This tells me that there is a working config/driver on the DVD....

 

I get the same kext errors as above and was looking for info on using/editing the kext's when I checked back here for other's progress.

Thoughts?

 

how did you install, from 10.4.1 or booted from the dvd? when i installed the wireless didnt work, maybe we have a different build.

i have the darwin 8.1 source from the cd, but for some reason i am not able to use gcc, i have installed it, but i get command not found when im in terminal. Just wondering if i should always boot with platform=ACPI, if that would help discover my card, seeing as how i dont have a battery moniter... (i havent tried booting with that option yet) Hope yall can get a driver compiled for this, otherwise for now im stuck on windows... :(

how did you install, from 10.4.1 or booted from the dvd? when i installed the wireless didnt work, maybe we have a different build.

 

 

My thoughts:

 

It looks like AppleAirPort2 may not have x86 code in it at all. I suspect that wireless functionality has been moved from AppleAirPort2 to AppleAirPortBrcm4311.kext.

 

AppleAirPortBrcm4311.kext's Info.plist has device IDs for three cards:

 

<string>pci14e4,4311</string>

<string>pci14e4,4312</string>

<string>pci14e4,4324</string>

 

Someone with a 4320 (Dell truemobile 1300) could edit the plist, then reboot. You should see something like: AirPortPCI_MM: Ethernet address 00:90:4b:7b:xx:xx during boot (and in dmesg).

 

If that happens, you can use the airport command line to associate with a network.

Ok, update on my end.

 

I have to delete the AppleAirPort2 kext (it has my device ID in it though), and then edit the Info.plist for the AppleAirPortBrcm4311.kext to have my device ID of 4320 in it. Apparently you will probably want to leave the AirPort2 kext alone, as it errors in -v even on a working broadcom chipset.

 

So, kextstat now shows it being loaded, but if I attempt to manually run the airport program as noted earlier, I still get that bootstrap error.:( But just as a note, the AppleAirPortBrcm4311.kext shows as loaded with kextstat, but ifconfig -a doesn't list any adapters for me.

Ok, update on my end.

 

I have to delete the AppleAirPort2 kext (it has my device ID in it though), and then edit the Info.plist for the AppleAirPortBrcm4311.kext to have my device ID of 4320 in it. Apparently you will probably want to leave the AirPort2 kext alone, as it errors in -v even on a working broadcom chipset.

 

So, kextstat now shows it being loaded, but if I attempt to manually run the airport program as noted earlier, I still get that bootstrap error.:blink: But just as a note, the AppleAirPortBrcm4311.kext shows as loaded with kextstat, but ifconfig -a doesn't list any adapters for me.

same experience with mine, only i removed both appleairport kexts as not to interfere...no dice

In the same plugins directory where AppleAirPortBrcm4311.kext is located, are two executable files called wpa_supplicant and wpad. Google for these and you'll find some interesting info - we may be able to get WPA support with these.

 

http://hostap.epitest.fi/wpa_supplicant/

Guest
This topic is now closed to further replies.
×
×
  • Create New...