[Development]-Broadcom 4311 Fix

[blessani]

Goddamit, I just re-inserted the 3945 and its totally knackered it seems.....the orange light is just flickering faintly on the front of the machine - I have no idea why its doing it! And the CDROM drive doesn't work when its inserted - balls. Tried the obvious BIOS update just incase, but no avail - stupid laptop. The 4311 doesn't cause any issue, so I doubt its the PCI-E slot

[booger_sniffer5000]

I can't really help you there. Try searching the forums, you should be able to solve your CDROM driver. For the network card, try cleaning the slot and the card.

[blessani]

Tried cleaning it, its a hardware issue, it struggles posting with the card in - I'll take it to work and swap it for another Intel and see how it goes.

[booger_sniffer5000]

Bad news, after a reinstall of OS X, I realized that installing the PCIFamily,kext actually did nothing at all. My PCI E port is recognized with a fresh install and so is my card but it still doesnt work. And I also checked and IO80211Family.kext is loaded at startup and the only reason that it wasnt loading before is because of conflicting versions. So I was never onto anything.

[booger_sniffer5000]

Does anybody know of a wireless card that I could replace this one with? I am getting tired of my wireless card not working and if I can buy a new one then I will in a heartbeat. Thanks.

[booger_sniffer5000]

I noticed something. The output of ioreg -l for the pci card gives incorrect vender and revisions ids. So it looks like this card is being recognized incorrectly.

[booger_sniffer5000]

Can we get some help here?

[Laddie]

I have a Compaq Presario C571NR with the same issue as everyone else. I've uphuck's 10.4.9 and Kalyway's 10.4.10 and several of the howto's, the pin 20 hack and also starting windows to power the card and rebooting into OS X. This successfully powers up the card but it is still unrecognised as a wireless card. I beleive it is being recognized but incorrectly. The Airport drivers are in place and the vendor and device id's are listed for it but it is still not recognised. Looking at the output of "ioreg -l" this is what is listed for it, (is the byte order correct for the vendor and device id's?):

 

 

| | | +-o IOPCI2PCIBridge <class IOPCI2PCIBridge, registered, matched, active, busy 0, retain count 8>

| | | | {

| | | | "Power Management protected data" = "{ theNumberOfPowerStates = 3, version 1, power state 0 = { capabilityFlags 00000000, outputPowerCharacter 00000000, inputPowerRequirement 00000000, s$

| | | | "Bridge Memory Ranges" = (18446744073708503040,1048575)

| | | | "CFBundleIdentifier" = "com.apple.iokit.IOPCIFamily"

| | | | "IOClass" = "IOPCI2PCIBridge"

| | | | "IONameMatched" = "pci-bridge"

| | | | "IOProbeScore" = 18446744073709551516

| | | | "Power Management private data" = "{ this object = 023c4a00, interested driver = 023c4a00, driverDesire = 0, deviceDesire = 0, ourDesiredPowerState = 0, previousRequest = 0 }"

| | | | "IOMatchCategory" = "IODefaultMatchCategory"

| | | | "IONameMatch" = "pci-bridge"

| | | | "Bridge IO Ranges" = ()

| | | | "IOProviderClass" = "IOPCIDevice"

| | | | }

| | | |

| | | +-o PXS3@0 <class IOPCIDevice, registered, matched, active, busy 0, retain count 7>

| | | {

| | | "IODeviceMemory" = (({"address"=18446744072904245248,"length"=16384}))

| | | "device-id" = <11430000>

| | | "IOChildIndex" = 1

| | | "name" = "pci14e4,4311"

| | | "acpi-path" = "IOACPIPlane:/_SB/PCI0@0/RP03@1c0002/PXS3@0"

| | | "acpi-device" = "IOACPIPlatformDevice is not serializable"

| | | "vendor-id" = <e4140000>

| | | "revision-id" = <01000000>

| | | "IOName" = "pci14e4,4311"

| | | "IOPCIResourced" = Yes

| | | "subsystem-vendor-id" = <3c100000>

| | | "Power Management private data" = "{ this object = 023f6e00, interested driver = 023f6e00, driverDesire = 0, deviceDesire = 0, ourDesiredPowerState = 0, previousRequest = 0 }"

| | | "IOInterruptControllers" = ("io-apic-0","IOPCIMessagedInterruptController")

| | | "Power Management protected data" = "{ theNumberOfPowerStates = 3, version 1, power state 0 = { capabilityFlags 00000000, outputPowerCharacter 00000000, inputPowerRequirement 00000000,$

| | | "IOPCIExpressLinkStatus" = 4113

| | | "IOPCIExpressLinkCapabilities" = 222225

| | | "class-code" = <00800200>

| | | "compatible" = <"pci103c,1363","pci14e4,4311","pciclass,028000">

| | | "assigned-addresses" = <1000068200000000000000d00000000000400000>

| | | "subsystem-id" = <63130000>

| | | "reg" = <00000600000000000000000000000000000000001000060200000000000000000000000000400

00>

| | | "IOInterruptSpecifiers" = (<1200000007000000>,<0500000000000100>)

| | | }

| | |

| | +-o USB1@1D <class IOPCIDevice, registered, matched, active, busy 0, retain count 9>

| | | | {

| | | | "USBBusNumber" = 29

| | | | "IODeviceMemory" = ({"offset"=6176,"parent"=({"address"=0,"length"=65536}),"length"=32})

| | | | "device-id" = <c8270000>

| | | | "name" = "pci8086,27c8"

[guilliamo]

I have a Compaq Presario C571NR with the same issue as everyone else. I've uphuck's 10.4.9 and Kalyway's 10.4.10 and several of the howto's, the pin 20 hack and also starting windows to power the card and rebooting into OS X. This successfully powers up the card but it is still unrecognised as a wireless card. I beleive it is being recognized but incorrectly. The Airport drivers are in place and the vendor and device id's are listed for it but it is still not recognised. Looking at the output of "ioreg -l" this is what is listed for it, (is the byte order correct for the vendor and device id's?):

end excerpt

 

I'm lucky in that my HP9230US recognized the DELL 1490 (Broadcom 4312) as Airport Extreme as soom as I got past HP's whitelist using Bluedragon1971's BIOS patch. It occurs to me that someone may be able to get useful info from MY "ioreg -l" listing for the working card in my HP:

 

Dell1490_in_HP9230US.rtf

 

G

 

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

HP Laptop DV9230US 1.66 GHz Core2Duo 2GB DDR2 RAM F27 BIOS w/Bluedragon1971 whitelist patch to allow booting with non-stock mini-PCIE wireless card

2X 250GB (2X 233GB Formatted) WD SATA WD2500BEVS Hard Drives (run quiet and cool)

Dell 1490 (Broadcom) mini-PCIE Wireless

Vista Ultimate on first HDD, formatted NTFS

OSX86 10.4.10 (Uphuck 10.4.9 1.4ir3 followed by KoolKal 10.4.10 updater) on second HDD, formatted HFS+ & MBR

Darwin Kernel 8.10.1: Wed May 23 16:33:00 PDT 2007; Sochi2014:VoteForUs/RELEASE_I386

EasyBCD BootLoader

 

XBench 1.3: 109.19

Working in OSX: Sleep; Dual widescreen monitors (Internal @ 1440 by 900 & external Dell 2405FPW 24" LCD DVI @ 1920 by 1200) both w/QE/CI/Rotation, iLife08, iWork08, Built-in speakers, Camera/PhotoBooth, Sonix WebCam Monitor, Wireless

Not working in OSX: Sound in/out other than built-in speakers (Conexant), card reader

[booger_sniffer5000]

Guilliamo, that info doesn't help. You have a different model wifi card and computer. Therefore, it is of no use to use. Thanks anyways.

[booger_sniffer5000]

Well, after typing into the terminal: "sudo kextload -t IO80211Family.kext", it told me that a bunch of other files were not the right ones to use with the IO80211Family.kext file that came with the Uphuck 10.4.9 dvd. I know the reason is because it is from 10.4.5, right now I am downloading the 10.4.9 Combo Update from Apple and I will use Pacifist to extract the IO80211Family.kext from it then install it and see what happens.And I should probably mention that the downlaod wont finish today because its 310 MB and I have satellite internet so I have a download limit of 200 MB and if I go over it, my internet speeds drop down to slower than dial-up-makes-you-want-to-kill-yourself kinda speeds.

[Laddie]

Kalyway 10.4.10 appears to be fine

 

kextload: extension IO80211Family.kext appears to be valid

kextload: IO80211Family.kext loaded successfully

new-host-6:/System/Library/Extensions root#

 

But OS X still doesn't properly see the broadcom 4311 though it is listed in the ioreg -l.

 

I came across this on another site, a blurb about HP and their BIOS locking out non-Intel cards? I don't understand, this card works fine on the C571NR under Vista. and a BIOS hack seems dangerous. Given that HP and Compaq are the same company could this be relevent? Has anyone tried this on their C300 or C500?

 

]http://forum.osx86scene.com/viewtopic.php?f=3&t=155&p=1581&hilit=4311#p1581

[booger_sniffer5000]

It would load fine on 10.4.10, it loads fine on 10.4.9 but it doesn't stay loaded and if you type in kextload IO80211Family.kext and it tells you that it loaded successfully, it means it was not already loaded and therefore 10.4.10 has the same problems as 10.4.9 (unless you unloaded the kext manually before running that kextload command). The reason it works on vista is because there is a specific driver written for those cards. In os x, there are no drivers made for the card on this computer because obviously, its a pc and not a mac. Its impossible to do a bios hack in os x because there are no programs written to do it because macs use firmware and not a bios. So there wouldn't be a program to do it. And that wouldn't solve our problem because we are trying to get this card working and not replace it. Given that, I wouldn't hack my bios. And each bios is different so I wouldn't use one way to do it on one computer on another. Sorry for the huge reply.Oh yeah, and AppleAirPort.kext and AppleAirPort2.kext both refuse to load. So that might have something to do with it.

[booger_sniffer5000]

well after using Pacifist to extract and install IO80211Family.kext, IOPCIFamily.kext, and IONetworkingFamily.kext from the 10.4.9 update, I finally got IO80211Family.kext to load at startup. But, the wireless card still doesn't work.

[booger_sniffer5000]

Oh, I forgot to mention that after installing these kexts, a kernel panic occurs in the process of shutting down no big deal but just thought i would mention it.

[booger_sniffer5000]

well after looking through an output of ioreg -l, if found this:

+-o ApplePCISlotPM <class ApplePCISlotPM, !registered, !matched, active, busy 0, retain count 7>

| | {

| | "Power Management protected data" = "{ theNumberOfPowerStates = 3, version 1, power state 0 = { capabilityFlags 00000000, outputPowerCharacter 00000000, inputPowerRequirement 00000000, staticPower$

| | "Power Management private data" = "{ this object = 0215c180, interested driver = 0215c180, driverDesire = 0, deviceDesire = 0, ourDesiredPowerState = 2, previousRequest = 2 }"

| | }

which pretty much means its a problem with the pci-e slot and the power management. So, thats why the card doesnt turn on.

[Achilleus]

I see....

 

I wonder how the Linux guys got around this?

[olinboy1]

I have just upgraded my dv5220us to Leopard and am overall happy with how the machine is running it. Am I correct in assuming that the "pin 20 trick" would not help this situation as it is more based on the mini pcie than it is the wifi power button on the laptop itself? I am willing to try it, but if someone else can already confirm it won't help anything, I'll leave well enough alone.

 

Any more new info boogersniffer? I can't say I understand most of the details you write about, but I am appreciative of your efforts! Hopefully this problem can be overcome like so many others have. Let me know if there is anything I can do or test to help out.

[booger_sniffer5000]

Well, I am sorry to say guys but I am out of the osx86 project untill after like December 1st. OS X had a kernel panic after trying to fix my wireless and I am in the midst of writing a term paper. So, once my term paper is handed in, I can help again. Im just afraid that os x would panic on me again if I installed it and then end up losing my work. So right now Im using Vista. So, I can't help until after December 1st. Sorry guys :censored2: blame my english teacher .

[booger_sniffer5000]

I have a question, what is ICH7? Does is have anything to do with the wireless bus or is it something else? Thanks.

[Achilleus]

I wish I knew =\

 

I'm getting an iMac on the fifteenth but it would be awesome if I could have osx on both computers. This wireless card problem seems pretty difficult to tackle

[olinboy1]

I have a question, what is ICH7? Does is have anything to do with the wireless bus or is it something else? Thanks.

 

Judging from Intel's 848 page pdf http://download.intel.com/design/chipsets/...ts/30701303.pdf I think that ICH7 does have a lot to do with not only the wireless (or more specifically the pci-e, mini or otherwise), but everything else on the board as well. I don't exactly know how it impacts our search, but I'd be willing to bet money on the fact that it is part of the "problem."

 

I believe my HP (dv5220us) is an 945GM "Calistoga" which is a ICH7-M chipset.

[booger_sniffer5000]

This weekend ill hookup my old hard drive and install osx86 and work on a fix. Hopefully i can get something worked out.

[Achilleus]

Thanks boogersniffer!

[jubjubrsx]

ugh i sure hope this problem can get fixed...heck who knows maybe people should get a pot of like 5-10$ to the person who comes up with a good fix for it......

 

i just ended up getting a usb wifi which works but the internal one would be awesome if anyone could get it working properly