Broadcom Wireless issue on HP Pavilion G4 1100tx

hi everyone, about a month ago i bought a new HP pavilion G4 110tx notebook which i using windows 7 ultimate as the Operating system, everything goes fine till now. i have a problem with my broadcom 4313 802.11 b/g/n which the link speed is unstable, sometimes it can reach to 65 Mbps but then it can goes down till 5 Mbps. i have installed the lates driver for that broadcom, but it doesnt give me any good news, the problem still occured "i'm using task manager -> Networking to see the link speed" any of you that have a same problem? thanks

Hi Hspasta,
Hspasta wrote:
You are forgetting the pipe
>>
in your wpa_passphrase call. It shoud look like this:
# wpa_passphrase "rsamurti" "9342184386" >> /etc/wpa_supplicant.conf
I corrected as you mentioned above. Still the same problem continues.
Anand

Similar Messages

E430 - Windows 8.1 x64 broadcom wireless driver issue

Hi,
I have a E430 running windows 8.1:
Driver info: PCI\VEN_14E4&DEV_4727&SUBSYS_060814E4&REV_01\4&1BEFDF2B&0&00E1
My wifi connection is just not working properlly. When I was running with windows 8, it works fine.
Has anyone have a updated driver for this , for Windows 8.1? The current one available from Lenovo website is not working for me.
Thanks in advance.

Did you try deleting the Broadcom wireless device in the Device Manager (including deleting drivers if prompted) and rebooting? I just did a fresh re-install of Win 8.1 (not "Refrsh - I mean format and install from scratch) and it works fine with the driver Windows 8.1 installed automatically. If possible, connected via a LAN cable after you reboot and then try to install the driver using Winodws Update.
I think that version is actually newer than the one listd in Lenovo System Update so I've just been using the one Windows installed automatically. For me, up thru Winows 8 this device driver was not available through Windows update and had to first be installed manually.

Hp pavillion dv9502au notebook pc broadcom wireless adpater not shown in device manager

Problem: hp pavillion dv9502au notebook pc broadcom wireless adpater not shown in device manager
System Type
hp pavillion dv9502au notebook pc
Windows editon
Windows 7 Ultimate
System
Processor       AMD Turion(tm) 64 X2 Moblie Technology TL-56 1.80GHz
Installed Memory   1.00 GB (895 MB usable)
System type              32-bit Operating System
Wirless TECH
Broadcom Wireless
Problem
1. I have a switch at front left of laptop which can be slided to switch on Wireless Connections
2. IT turns red when switched off and blue when switched on as normal
3. But only thing that turns up is Bluetooth connection and no broadcom wireless connection
4. No adapter is shown in the devmgmt.msc( device manager)
5. I tried installing broadcom drivers to reslove the problem, and restarted many times for install.
6. I tried the "reset thing" after removing the battery that experts said about.
7. I was atlast forced to use Wired conneciton using ethernet( i hate it because, i can't be mobile around the house)
8. Please Help
Windows 7 Ultimate
System
Processor       AMD Turion(tm) 64 X2 Moblie Technology TL-56 1.80GHz
Installed Memory   1.00 GB (895 MB usable)
System type       32-bit Operating System
Wirless TECH
Broadcom Wireless
Problem
1. I have a switch at front left of laptop which can be slided to switch on Wireless Connections
2. IT turns red when switched off and blue when switched on as normal
3. But only thing that turns up is Bluetooth connection and no broadcom wireless connection
4. No adapter is shown in the devmgmt.msc( device manager) (network adpaters shown are
                                     NVIDIA geforce adapter, bluetooth adpaters)
5. I tried installing many broadcom drivers to reslove the problem, and restarted many times for install.
6. I tried the "reset thing" after removing the battery that experts said about.
7. I was atlast forced to use Wired conneciton using ethernet( i hate it because, i can't be mobile around the house)
Please help

Your wireless adapter is defective.
Please mark the post that solves your issue as "Accept as Solution".
If my answer was helpful click the “Thumbs Up" on the left to say “Thanks”!
I am not a HP employee.

Tried every way to install my broadcom wireless card and failed

Hello.. i asked this in the newbie section but didn't get any replies.. i really need help and i don't know where else to go.
i have an hp dv2500 laptop with a Broadcom wireless card.. here is the output of lspci | grep -i net
08:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)
at first, i tried getting it to work with the broadcom-wl driver from AUR as suggested by this wiki page: http://wiki.archlinux.org/index.php/Broadcom_BCM4312
i followed all the steps.. however, i did get an error when i tried to exucute this line:
insmod /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/wl.ko
and the error was:
error inserting 'wl.ko': -1 File exists ...
i continued despite this error and when i was done, i couldn't detect the card with iwconfig or wicd.. the modules named "wl" and "lib80211" are loaded but i still can't detect it..
i uninstalled, re-installed and i got the same behaviour..
so then i tried the BCM43xx driver as described here: http://wiki.archlinux.org/index.php/Wir … up#BCM43XX
i unpacked the firmware and restarted but i still couldn't detect it.. and i couldn't load the bcm43xx module because arch says was not found..
then i tried the driver after that "b43".. followed the steps on the wiki, restarted, and i still couldn't detect the card with iwconfig or wicd..
i have been trying to get this to work for 3 days now.. i appreciate your time and help in this issue..
thanks

thanks for the reply tomk..
so at least we limited the problem to using broadcom-wl..
here is dmesg after modprobe -r wl
Bluetooth: Generic Bluetooth USB driver ver 0.5
usbcore: registered new interface driver btusb
Adding 1895660k swap on /dev/sda4. Priority:-1 extents:1 across:1895660k
forcedeth 0000:00:0a.0: irq 27 for MSI/MSI-X
Clocksource tsc unstable (delta = 4398045793691 ns)
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
eth0: no IPv6 routers present
lib80211_crypt: unregistered algorithm 'NULL'
and after modprobe wl:
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
i'm not that good with gnu/linux, so i'm not sure if something is wrong from these messages... do they point to anything?

Bad Driver for Model J6N60AV - Broadcom Wireless, bluetooth, SP68429

I recently purchased this HP700qe. I always make sure that I have all drivers for a machine archived away before doing anything with the machine.
I have downloaded the file SP69429.EXE
When attempting to extract the contents, it asks for the destination folder. After selecting to extract to the default folder, the gauge appears and starts to populate, then the app crashes. No documents appear in the default directory
C:\SWSETUP\SP68429
I have searched a great deal but can not find seem to source the driver from any other location. Broadcomm states to go to the vendor.
I found no other way to report this issue than the public member support forums. This is a poor situation. It reflects badly upon HP as a corporate entity selling to the public.
I hope to see two things. 1) A driver that extracts correctly. 2) a better method for communications between new customers with real issues and support.
I know, keep dreaming.
Below is the information from the download page:
DescriptionThis package provides the Broadcom Wireless Local Area Network (WLAN) Driver in the supported desktop models and operating systems.
Release details
Released:
2014-07-24
File name:
sp68429.exe [1/1, 36.32M]
Version
6.30.223.245 B
Compatibility:
Microsoft Windows 8.1 (32-bit)
Microsoft Windows 8.1 (64-bit)
Microsoft Windows Embedded 8.1 Industry (32-bit)
Microsoft Windows Embedded 8.1 Industry (64-bit)
Fix/EnhancementInitial release Windows 8 driver for Broadcom 802.11n Wireless LAN Device.

Hi:
Since you are aware that this is a peer to peer forum, no one from HP will respond on behalf of the company.
I do not work for or represent HP, but I have reported this problem through the forum administrators to please contact the department responsible for releasing drivers.
I tried by various other means to extract the contents from the file, and it absolutely will not work.
If there is a pressing reason you need a driver for that card right away, you should be able to use this slightly older one...
http://h20565.www2.hp.com/hpsc/swd/public/detail?swItemId=cp_133536_1
HP does have support for PC's under warranty, and you can contact HP technical support for the country you live in at the link below...where you could have reported the problem as well, rather than presuming that HP lacks a method for communications between new customers with real issues and support.
http://www8.hp.com/us/en/contact-hp/ww-contact-us.html

New MacBook Pro 13 i5 Wireless Issues.

I got the new MacBook Pro i5 2.3 the day it came out. So maybe a week and half ago.
I`m having intermittent wireless issues. I have done some testing and even replaced my older AirPort Base Station with the new Dual-Band one, but still seeing a drops from the network. I have a ping going to my router and to the ABSE. I tried changing the channel and using 5GHZ or 2.4GHZ. I also have a AirPort express and seen similar results. I tried reseting the PRAM, repairing permission, I did not reinstall the OS but I dont see how this would help. I think there is a hardware issue with the wireless card/antenna.
I did upgrade RAM and HDD was changed to SSD (intel G2 SSD). There are no other issues, machine is fast, no lock ups. Other devices on the network do not seem to drop any connections (ATV, ATV2, iPhone4, iPad etc..)
The network drop outs are short but are noticeable and if a ping is going I can see the drops
*-- 192.168.1.1 ping statistics ---*
*1527 packets transmitted, 1505 packets received, 1.4% packet loss*
*round-trip min/avg/max/stddev = 0.779/12.203/396.084/42.274 ms*
Any help is appreciated as I`m really frustrated but this issue.

Here are some of the pings.
+*64 bytes from 192.168.1.3: icmp_seq=2190 ttl=255 time=1.138 ms*+
+*Request timeout for icmp_seq 2191*+
+*Request timeout for icmp_seq 2192*+
+*64 bytes from 192.168.1.3: icmp_seq=2193 ttl=255 time=1.701 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2194 ttl=255 time=1.653 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2195 ttl=255 time=1.723 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2196 ttl=255 time=1.470 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2197 ttl=255 time=1.435 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2198 ttl=255 time=1.217 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2199 ttl=255 time=1.115 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2200 ttl=255 time=1.433 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2201 ttl=255 time=1.002 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2202 ttl=255 time=1.057 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2203 ttl=255 time=1.222 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2204 ttl=255 time=0.769 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2205 ttl=255 time=0.821 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2206 ttl=255 time=0.723 ms*+
+*Request timeout for icmp_seq 2207*+
+*64 bytes from 192.168.1.3: icmp_seq=2208 ttl=255 time=54.892 ms*+
+*Request timeout for icmp_seq 2209*+
+*Request timeout for icmp_seq 2210*+
+*64 bytes from 192.168.1.3: icmp_seq=2211 ttl=255 time=1.313 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2212 ttl=255 time=0.936 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2213 ttl=255 time=1.839 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2214 ttl=255 time=0.879 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2215 ttl=255 time=63.446 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2216 ttl=255 time=24.384 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2217 ttl=255 time=105.923 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2218 ttl=255 time=41.322 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2219 ttl=255 time=1.853 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2220 ttl=255 time=0.811 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2221 ttl=255 time=0.721 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2222 ttl=255 time=0.791 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2223 ttl=255 time=3.816 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2224 ttl=255 time=1.052 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2225 ttl=255 time=0.688 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2226 ttl=255 time=89.272 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2227 ttl=255 time=49.459 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2228 ttl=255 time=15.891 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2229 ttl=255 time=0.745 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2230 ttl=255 time=0.724 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2231 ttl=255 time=0.680 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2232 ttl=255 time=1.950 ms*+
+*64 bytes from 192.168.1.3: icmp_seq=2233 ttl=255 time=0.600 ms*+
+*Request timeout for icmp_seq 2234*+
+*64 bytes from 192.168.1.3: icmp_seq=2235 ttl=255 time=0.725 ms*+

If you have a Blue Screen / Error due to Wireless issues (B110a), fix in here.

For the original thread created by somebody else, please see here:
http://h30434.www3.hp.com/t5/Printer-All-in-One-Install-and/B110a-network-connection-problem/m-p/319...
Here's a youtube video of what happened to me: http://www.youtube.com/watch?v=adE1kq36ld4
I'm reposting it here so it can hopefully help some of you guys if anybody else stumbles across this. In short, my printer was fresh out of the box and I attempted to connect it to the wireless network. It would throw a blue screen on the LCD with an error of B8126AD6.
I narrowed it down to an issue with DHCP. For some reason the printer connects to the wireless access point but as soon as it tries to get an IP address from the DHCP server it crashes with that blue screen and the error code in the first post above. This look like a massive bug in the printers firmware! For reference my router is a Billion 7401VGPR3 which is acting as my default gateway and DHCP server. I have a Linksys WRT54G as my Access Point for the house.
To solve it, I turned DHCP off on my router and then tried connecting the printer to the wireless network. This time it connects fine but you still can't talk to it because it doesn't have a proper IP address. If it still doesn't connect properly, try turning WPA/WPA2/WEP off on your Access Point. Leave it completely open for a moment until you can reach the web interface (as below).
To fix the IP issue, I then went into the Settings menu on the printer and printed the "HP Network Configuration Page". Note that under the Wireless menu option there are a couple of different "Print Network Test Page" options. I believe it's the 2nd one that I selected. You'll know you have the right one when it prints out the page with the following info:
IPv4 IP Address
Subnet Mask
Hostname
Default Gateway
Primary DNS
etc, etc.
Take note of the IP Address from the printout above and the Subnet Mask. My IP was 169.254.73.5 and subnet mask 255.255.0.0. Now I manually configured my computers IP address to be similar (within the same subnet): 169.254.73.10 with the same subnet mask.
Now you can load up the web interface of the printer using http://169.254.73.5 in my case. (You should also be able to ping the printer at this point too). In here you have a Network tab where you can now manually set the IP Address of the printer. Set the address you want it to be in your network (in my case 192.168.0.3 with a subnet mask of 255.255.255.0 and default gateway 192.168.0.1 and dns server 192.168.0.1).
Once I clicked OK I changed my PC's IP back to normal, and I can now reach the printer on its IP address set above. YAY!
The great thing is, in the web interface you get a million more options to play with. You can manually set the IP address, gateway, DNS, wireless settings such as WPA1/WPA2 AES/TKIP Encryption, WPA Passkey, etc. So if you had to set the Access Point to completely Open, setup the encryption again and put the passkey in here. When I did this I had to go back into the Settings menu on the printer LCD and select "Disable Wireless" then "Enable Wireless" to force it to re-join the network.
Finally I went into the Settings menu again and Updated the software on the printer. I don't know if the new software fixes the bug or not - I haven't tested it (can't be bothered!).
Hopefully this will help some of you guys out there too!
EDIT: I've just stumbled across another couple of posts with similar results to mine:
- http://h30434.www3.hp.com/t5/Printer-networking-and-wireless/How-to-install-Photosmart-B109n-z-on-a-...
- http://forums.techguy.org/networking/627989-hp-6980-printer-wireless-problem.html

Many thanks to gardz for an exhaustive overview on this critical problem with the B110a printer!
I am happy to report that I have managed to set the printer to a static IP and am now able to connect to it wirelessly from my home computers, and also able to use the web apps and ePrint features on the printer. The printer shows the IP address and I am able to use the EWS (Embedded Web Server) to connect to its IP address from my PC's internet browser. The Wireless Network Test Report also showed no problems. I have also completed the Product Update on the printer, and there are no more pending updates now.
However, the core wireless problem is still not satisfactorily resolved.
I get the BSOD and blinking-lights error ("Please turn off printer and then on"), only if I start the printer when Wireless is enabled on the printer. If wireless is disabled prior to printer boot, there is no error.
The workaround I have adopted for now, is to always switch off the printer's wireless, before switching off the printer, and enabling the wireless setting only when I need to print/scan.
Is this happening with anyone else? Why would the printer crash if it boots with wireless enabled? If it is already set to a static IP, why would it still conflict with the DHCP on the router?
My router is perfectly working, it is in the same room as the printer, so the signal strength is good. The printer itself is quite stable except for this crash-after-boot-if-wireless-was-enabled issue on the printer.
I made the mistake of connecting the USB cable to my primary computer before installing the printer drivers, so even the USB option is not working (Windows recognizes the printer as an unknown USB device). If anyone can point me to the printer drivers (inf files), I would be grateful. The CD does not have the driver files in a convenient location. It seems to be embedded within the setup package somewhere.
Gardz and PrintDoc, I hope you can help us out on this one. I know many B110a users are struggling with the wireless issues, so HP needs to release a firmware fix and driver update soon. Wireless ought to work out-of-the-box, as this product is aimed at the SOHO users.

Is anyone else having email problems such as apps exiting in the middle of an email? It may be a wireless issue. I use First Class for work and yahoo email for personal. I will be in the middle of typing a long email and the app just quits, all data lost.

Is anyone else having email problems such as apps exiting in the middle of an email? It may be a wireless issue. I use First Class for work and yahoo email for personal. I will be in the middle of typing a long email and the app just quits, all data lost.

Have you tried restarting or resetting your iPad?
Restart: Press On/Off button until the Slide to Power Off slider appears, select Slide to Power Off and, after the iPad shuts down, then press the On/Off button until the Apple logo appears.
Reset: Press the Home and On/Off buttons at the same time and hold them until the Apple logo appears (about 10 seconds). Ignore the "Slide to power off"

I have had wireless issues sense Leapord, any fixes yet? its a shame that my wife has to sit in front of our 27 inch imac on a $300 Windows computer to use the web effectively. I have tried all fixes and some work while others don't but all temporary

This Lion wireless issue has become more than just an irritation, so much so, my wife has resorted to sitting in front of a 27 inch imac with a 300 dollar Walmart Windows computer to get the bills paid and use the web. And yes, there is not a fix out there I haven't tried over the last year or so, some worked and some didn't, but all were temporary at best. Same issue with my Macair, I wonder if its a hardware issue, like the video card in my 2006 MBP, it went out after the warrenty and then I found out there was a calss action suit going on over it, unfortunately Apple wouldn't cover it and wanted 7oo bucks to fix it, sold that as parts.
While i really like me Macs, I own three, I may have to bow out and stick with LINUX, that has yet to let me down, anyone know if Mountain will fix this issue? or are we all just waiting for defective WiFi cards to fail at our own expense, PS, got three Macs for sale.

Sounds like you're getting kernel panics, which are usually, but not always, caused by hardware problems, with memory being one of the regular culprits.
First thing I would do is to get our your original OS X disks, insert the first one (should say 'AHT version x.x' in small print on the label - if not, find the one that does), and reboot holding the Alt key down. Choose the Apple hardware test, and when prompted, choose the extended test. If you have either of the TechTool programs, they can do similar testing. Does that identify any hardware issues?
Next, I'd download rember from http://www.kelleycomputing.net/rember/ . This is a memory testing program that you can set to run overnight. Does it come up with any errors? If so, try resetting your memory card(s) by removing and putting back into the computer. Rerun memory test.
This FAQ will provide other details: http://www.thexlab.com/faqs/kernelpanics.html

This is a workaround for the MBP wireless issue

There have been many topics on the MBP wireless issues already, but I thought some people might find this workaround helpful.
Firstly, my system is a 2.2Ghz MBP, running 10.4.10, and also airport extreme update 2007-04. I am using an airport express base station. My previous Powerbook never had any wireless problems, so I really couldn't blame the basestation for the MBPs poor wireless.
Warning - The workaround requires a little bit of work in the terminal. A little bit of understanding of how networks work is assumed here as well. So it is probably not for everyone ...
What I have observed - whenever the MBP loses connection, the airport basestation IP and MAC addresses are missing from the ARP table.
- To view the ARP table, type (in a terminal window) arp -a.
So, when the MBP wireless hangs, open up the terminal and type that in.
Do a Cntrl-C if the arp command is hanging and not returning anything.
In normal situations, a list of IP addresses and MAC addresses will show up.
As others have already noted, clicking on the airport icon in the menubar, will magically bring the wireless back to life. When this happens, the ARP table also gets magically populated correctly. Coincidence? I think not!
So, the workaround is to store a PERMANENT entry in the ARP table for the airport basestation IP and MAC address. In my case, I can use the Airport Utility software to confirm what the basestation IP and MAC addresses are (note MAC address = Airport ID in Airport Utility). I found the basestation IP=10.0.1.1 and the MAC=0:11:24:07:d7:f
To create a permanent ARP table entry for my airport basestation, I opened up a terminal window, and did the following -
1) login to my administrator account
2) type in the following command sudo arp -s 10.0.1.1 0:11:24:7:d7:f
3) type in my administrator password to authorise the change
4) type in (to confirm the changes have been made) arp -a
5) logout of my administrator account (from the terminal)
Ever since I did this, my MBP wireless performance has been flawless.
Note, if you shutdown or restart your computer, the arp entry disappears. This is ok for me as I hardly ever power down my MBP. As insurance I have added an account startup item to remind me to do the arp table entry.
This workaround is great for me because I don't have a need to use multiple wireless networks. It might not be practical for people who roam around onto different networks.
Give it a go and see if it works for you.
Message was edited by: michael louey

OK, after some further experimenting, I changed the multicast rate on my airport express. It was set at 6Mbps, and I changed it to 2Mbps.
I have read that the default multicast rate for previous 802.11g versions of Airport basestations is actually 2mbps. Excellent results so far !! I have set up a terminal command to continuously ping my airport router address every 15 sec, and there have been virtually no dropped packets so far over many hours.
ping -i 15 10.0.1.1
Interestingly, in Apple's Airport Admin software in my MBP there is no option to set the rate at less than 6Mbps (!!!!), so I had to use the Windows XP version of Airport admin software to make this change using a windows machine. Using the XP software you can set the muticast rate as low as 1Mbps.
If you are using Apples airport admin software (Tiger and Leopard) and you commit any sort of change in settings, the multicast rate will be re-set at a minimum of 6Mbps. My understanding of the multicast rate is that setting it too high is similar to shrinking the coverage area of the basestation, and limiting access only to clients who can transmit at the required multicast rate.
So my new theory is that the dropouts are caused by the MBP dropping off the airport due to not being able to achieve the set multicast rate. (this could be due to factors such as low signal strength, excessive interference or noise).
If you are using Apples more recent Airport admin software, you are having a minimum 6mbps muticast rate set, and this might be too high for your particular environment.
Just a theory.
(oh yeah, I enabled interference robustness on the MBP and the basestation just for good measure)

Macbook Pro (Late 2008) - Windows 7 64-bit, Bootcamp 3.1 - Wireless Issue

Hi Everyone,
I have a Macbook Pro (15-inch, Late 2008) model with Snow Leopard and Windows 7 64-bit dual boot. I have done a search and cannot find any reference to this problem on my hardware.
I have had no issues in Windows 7 when using Bootcamp v3.0. In the last week I have upgraded to Bootcamp v3.1. (completed twice, rolled back in between to prove that the issues was related to the Apple Update)
After I update to v3.1, I have issues with my wireless network. The network cannot resolve the name for any internet address. I can connect to wireless networks (tried multiple networks), all the DHCP settings seem to be retrieved correctly (Gateway, DNS etc) and I can ping local and machines outside my network without an issue provided I use the IP address. (Skype works - which uses direct IPs rather than names I have found over time)
As soon as I use a name for a destination for Web traffic, Mail, pinging (any application), my Macbook Pro cannot resolve the address and just bombs out.
If I connect to a wired network, the machine works perfectly and name resolution on that interface works. If I rollback (using Windows 7 rollback capability) to before the v3.1 Bootcamp is installed, the wireless networking also works perfectly.
I noticed this in the support area at apple:
http://support.apple.com/kb/TS3196
But this refers to wireless issues in Bootcamp drivers prior to v3.1 and on 13 inch Macbook. Wonder if this is a similar issue or related?
Anyone else seen this or point me in the direction of a fix?
Thanks,
Thommo

I'm looking into running Windows 7 64bit on the exact same MBP you have, so I'm curious as to whether or not you've found a solution yet outside of the forums.
Do you think it might be that the bootcamp 3.1 update is only for Windows 7 32bit and not for the 64bit version?

MacBook wireless issue (ongoing) & DIY airport card replacement

Hello,
With reference to the ongoing MacBook/OSX (10.5.3) Leopard intermittent wireless issues discussed in this forum has anybody gone ahead and taken matters into their own hands and purchased and installed a new Airport card for their MacBook from www.ifixit.com?
Further details at: http://www.ifixit.com/MacBook-Parts/MacBook-Core-2-Duo-Santa-Rosa-Penryn-802-11n -Airport-Extreme-Card/IF186-062
If so, did it resolve your intermittent Airport issues?
It seems to me that when the MacBook is running on battery power only the Airport card does not realise that the MacBook has come out of sleep sometimes and therefore does not always function correctly. Maybe the Airport card does not receive sufficient power when the MacBook comes out of sleep mode whilst running on batteries only?
Typically when I run the MacBook connected to power the intermittent wireless problem does not occur.
This issue has been a recurring problem for me for 6 months now and unfortunately I have not seen Apple address this issue.
My MacBook is 6-months old and is a black MacBook using a 2.2GHz processor running Leopard OSX 10.5.3.
Cheers,
treaders

Visit Apple Store and replaced the Airport card.

[SOLVED kinda]Yet another Broadcom wireless problem - scanning

Use an old Gateway laptop with a wireless card to provide internet through NAT to my desktop computer that isn't nearby my switch. I was doing this for the longest time using WinXP on the Gateway, but since all my other computers are now running linux, I figured, hey, why not put a really sleek and sexy copy of Arch onto the Gateway, and free up some of that HD space for easier file sharing between the desktop and the rest of the network. So I installed Arch, and have run head first into how much Arch and Broadcom wireless devices do not play well together. Have spent all my time since then searching the forums, the wiki, etc, but to no avail. So going to just go ahead and finally make my own call for help via the forums here.
I've only ever ONCE seen a scan find a wireless network, and that was after my first reboot after installing arch. That was the only time. There are at all times 2-4 wireless networks in range of this computer. I'm currently on my netbook running Ubuntu to post this (typing everything in by hand, ugh), and can see 4 networks right now. The Arch laptop can't find any.
To start off with: I have read the wikis. I have searched the forums. I HAVE INSTALLED THE FIRMWARE. I've checked to make sure my card is supported, and the driver it uses is the b43, and is not supposed to be compatible with the wl driver. This is the cardbus Linksys WPC54G v1 card. I know the card itself works.
Here's the various data I'm sure will be requested of me at one point or another. This is all taken immediately after booting.
What can I try. I've probably already tried it, but I'm willing to walk through step by step with someone if they think they can help.
lspci -vnn
03:00.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)
Subsystem: Linksys WPC54G v1 / WPC54GS v1 802.11g Wireless-G Notebook Adapter [1737:4320]
Flags: bus master, fast devsel, latency 64, IRQ 10
Memory at 48000000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2
Kernel driver in use: b43-pci-bridge
Immediately after boot if I run
dmesg (related info)
[ 7.760803] b43-pci-bridge 0000:03:00.0: enabling device (0000 -> 0002)
[ 7.769836] b43-pci-bridge 0000:03:00.0: PCI INT A -> Link[LNKA] -> GSI 10 (level, low) -> IRQ 10
[ 7.760856] b43-pci-bridge 0000:03:00.0: settling latency timer to 64
[ 8.217173] b43-phy0: Broadcom 4306 WLAN found (core revision 5)
[ 8.276959] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 8.278657] Registered led device: b43-phy0::tx
[ 8.278721] Registered led device: b43-phy0::rx
[ 8.278788] Registered led device: b43-phy0::radio
[ 8.278831] Broadcom 43xx driver loaded [ Features: PMNLS ]
[ 43.860080] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 43.921388] ADDRCONF(NETDEV_UP): wlan0: link is not ready
uname -a
Linux oms-gateway 3.2.9-1-ARCH #1 SMP PREEMPT Thu Mar 1 09:10:44 UTC 2012 i686 Intel(R) Pentium(R) III Mobile CPU 1066MHz GenuineIntel GNU/Linux
Kernel version greater than 3.2 should be able to use the version 5.100.138 Broadcom drivers.
ifconfig wlan0
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 metric 1
ether 00:0f:66:2e:b0:83 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 btes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
iwconfig wlan0
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
lsmod | grep b43
b43 317649 0
mac80211 203227 1 b43
cfg80211 147716 2 mac80211,b43
ssb 42035 1 b43
mmc_core 71470 2 ssb,b43
pcmcia 31502 2 ssb,b43
iwlist wlan0 scan
wlan0 No scan results
Last edited by oldmansutton (2012-03-11 01:53:50)

oldmansutton wrote:
Strike0 wrote:Whether rev 3 needs legacy or not is controversial. I assume you blacklisted b43 when trying legacy?
How about any need to blacklist when you need b43. Anything suspicious around in lsmod?
with b43, you can see me previous lsmod on the original post.
with b43legacy, the only related things I see from lsmod are b43legacy, mac80211, cfg80211, and ssb.
Wait. Hmmm....
rmmod b43
modprobe b43legacy
rmmod b43legacy
modprobe b43
lsmod |grep b43
Now bcma is showing up. But it didn't before. It just started showing up with b43 since I did the compat-wireless package. But seeing as I'm getting scans SOMETIMES now, I hesitate to call it a problem. Maybe?
Any other ideas?
It can scan ONCE. The b43 driver is obviously functional at least for a bit.
Standard network service, wicd, netcfg, etc, I've tried them all. Reinstalled from scratch twice. Looking for NEW ideas basically. I've read just about every single post about every broadcom chipset out there. I just happen to have one of these rare ones apparently.
Last edited by oldmansutton (2012-03-10 17:46:59)

WRT310N v1 and MacBook Pro wireless issues

Hi all,
I've been having ongoing wireless issues with my WRT310N v1. I have a macbook pro (early 2009) with mac os 10.5.8. I have cable internet, with a DHCP connection. I have a computer and PS3 hardwired through the router, and they work flawlessly. The wireless, however, has never been what it should be. Internet loads slow, even though the connection speed is pretty good (not as fast as hardwired devices, but close).
Here are the wireless settings:
wireless config: manual
network mode: mixed (the Macbook can get wireless-n, by iPhone is only g)
Radio band: standard 20 mhZ
wide channel: 9 (can't change this with this config, unless i go wide channel at 40 mhZ)
standard channel: 11
SSID broadcast: enabled
I've got WPA2 security, with AES encryption. I've set the Beacon interval to 75, and left the Fragmentation and RTS thresholds at default. The firewall is activated, and "filter anonymous internet requests" is disabled.I'm wondering if I'm losing so much speed by broadcasting a mixed signal, instead of just G or just N. I've tried transmitting only in Wireless-N, but there's no noticeable change (and the iPhone can't connect at all).
Any input at all would be really appreciated. I'm hoping I don't have to fork over $30 to linksys just to get tech support. Thanks in advance.
Solved!
Go to Solution.

Well its not necessary to power cycle your router everytime whenever you make any changes on your Router. But if you re-configure all the settings on your from scratch, then its better to power cycle your router.

Is this a dropping connection or a wireless issue....

Hi all,
We've been having some problems with our Infinity setup for a few months now and it's getting a bit annoying, I could use some help in fixing it
So, every evening (could be daytime too, we dont use it then really) our connection seems to drop every 10 mins or so. If I'm gaming, it will drop me out of a game and I'll have to reconnect. I can usually reconnect in seconds. If we're watching Netfilx, it will stop, and restart a few minutes later...
Oddly, the blue Hub lights (HH3 I believe) never falter, solid blue throughout.
Restarting the router (and white box thingy) works pretty much everytime - and only occasionally are we disconnected for more than a few minutes.
The setup is Infinity 2 I think, into the master socket. I'm running a handful of Apple devices, a home server, a Mac and a PS3. Probably important that none of these devices have changed at all location, spec or otherwise.
Occasionally my server cannot be found on the network either, despite it running continuously - a restart usually cures this but would it point to a dodgy router? (it's a wired connection,so no wireless issue)
I'm guessing I need to run some tests but not sure what?
I did try and call BT Support a while ago, but the chap said he couldn't help me because my Mac Air has no ethernet cable, just wireless

seems to me like a faulty router or modem mate, to make sure its not actually dropping fully you will want to login to the router page using 192.168.1.254 then going to troubleshooting and then helpdesk and it will tell you the uptime. login with the password which should be on the back of your router. do this when the wireless next drops. btw dont keep resetting the white modem, it will cause your speeds to drop as it will think its a line fault, just reset the homehub. if the uptime is less then 2 mins then its dropping fully, if its more than than lets say 1 hour for example (and you reset it one hour ago before the wireless dropped) then its most likely just the router being faulty.

Broadcom Wireless issue on HP Pavilion G4 1100tx

Similar Messages

Maybe you are looking for