Jump to content

10.4.3 broadcom wireless effort


  • This topic is locked This topic is locked
234 replies to this topic

#1
sportman

sportman

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 165 posts
Any thing to do with the topic, please post here. If anyone has the source to the hacked broadcom airport kext it would be greatly appreciated.

#2
suleiman

suleiman

    Your Anchorman

  • Retired
  • 640 posts
  • Gender:Male
  • Location:USA, UK, and CANADA :)
  • Interests:OS X
oh {censored}....so this doesn't work anymore in 10.4.3? Forget that man! I'm sticking to 10.4.1 in that case. I need a system with net.

No net = back in 1989.

#3
sportman

sportman

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 165 posts
im sure we will have it wokring soon enough, btw etherenet prolly should still work but wireless is n issue

#4
fallingup

fallingup

    InsanelyMac Protégé

  • Members
  • PipPip
  • 72 posts

im sure we will have it wokring soon enough, btw etherenet prolly should still work but wireless is n issue


thing is, my onboard ethernet didnt work in 10.4.1, i had to stick with wireless...

#5
Tak

Tak

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 113 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).

#6
fallingup

fallingup

    InsanelyMac Protégé

  • Members
  • PipPip
  • 72 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).


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. )

#7
fallingup

fallingup

    InsanelyMac Protégé

  • Members
  • PipPip
  • 72 posts
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)

#8
outoftheboxx10

outoftheboxx10

    InsanelyMac Protégé

  • Members
  • PipPip
  • 51 posts
  • Interests:mostly hardware
what if we were to take the old kextload app out of 10.4.1 and try to execute it on 10.4.3?
assuming nothing MAJOR has changed, should the os still be able to make the same calls to the kext?

#9
fallingup

fallingup

    InsanelyMac Protégé

  • Members
  • PipPip
  • 72 posts

what if we were to take the old kextload app out of 10.4.1 and try to execute it on 10.4.3?
assuming nothing MAJOR has changed, should the os still be able to make the same calls to the kext?


new kernel in .3, wont work...

#10
outoftheboxx10

outoftheboxx10

    InsanelyMac Protégé

  • Members
  • PipPip
  • 51 posts
  • Interests:mostly hardware
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

#11
Todd R.

Todd R.

    InsanelyMac Protégé

  • Members
  • Pip
  • 1 posts
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?

#12
ohpossum

ohpossum

    InsanelyMac Protégé

  • Members
  • PipPip
  • 73 posts

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.

#13
ohpossum

ohpossum

    InsanelyMac Protégé

  • Members
  • PipPip
  • 73 posts

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.

#14
cyrana

cyrana

    Prophetess of Doom

  • Retired
  • 1,462 posts
  • Gender:Female
  • Location:Somewhere out there
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?

#15
sportman

sportman

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 165 posts
no one has the source, want to give us it?

would be appreciated.

#16
cyrana

cyrana

    Prophetess of Doom

  • Retired
  • 1,462 posts
  • Gender:Female
  • Location:Somewhere out there
<snip>I was nonsensical</snip>

#17
sportman

sportman

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 165 posts
yea, wireless is the only way for me to get online, so hopefully someone can get the source compiled, i have talked to several people though and no one seems to be able to find the source, so any help would be greatly appreciated.

#18
fallingup

fallingup

    InsanelyMac Protégé

  • Members
  • PipPip
  • 72 posts
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.

#19
ohpossum

ohpossum

    InsanelyMac Protégé

  • Members
  • PipPip
  • 73 posts

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.

#20
Tak

Tak

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 113 posts
Nice findings. The AppleAirport2 kext in /Extensions has never loaded successfully on any x86 build so far. We had to rely on the Darwin kext of the same name.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy