A now unrecognized wireless card

I've got a wonderful little PowerBook G4, 12", and its almost 3 years old. It didn't come with wireless at that point, but I bought an Airport card in May. It worked perfectly right off the bat - the Apple guy stuck it right in and ta-dah, I had wireless!
Yesterday my computer slid off my lap and onto the floor, landing on it's right hand corner/side. The screen dimmed and told me to restart it - so I did. The computer works fine, and I praise Apple for making sturdy casing (it's the second time I've dropped it...).
But the problem is this: the computer is no longer recognizing the wireless card! So I turned off the whole thing, and tried to take out the card, jiggle it around, and get it back in. It dislodged slightly but I couldn't take it out completely because of the extra wire thing that locked it in. I put it back into place, but nothing is working. I'm wondering if maybe some of the hardware got jarred out of place inside the casing.
The question:
Is there a way I can safely unhook the wire plug thing myself?
Do I take it in to the apple store (an hour away) and is it repairable (for not a lot of money since I don't have apple care)?
Or do you think my wireless capabilities will now be just a memory for me?

Hey Techieskittles, welcome to the Apple Discussions!
Sorry for the bad news about dropping your laptop, that's never a good thing. One thing I would like to mention before I throw some tips your direction: This particular discussion board is for the Power Mac G4, not the PowerBook G4 (Power Mac = Desktop, PowerBook = Laptop in "Apple" terms). That said, any question is welcome to the boards, but you'll find more specalizied/knowledgable people if you post in the right area. So if my tips don't help, consider posting here:
http://discussions.apple.com/category.jspa?categoryID=120
Since I also own a PowerBook, can I offer some insight that might help. You could try resolving your issue from a software standpoint. I've worked with PowerBooks in the past that contained known working AirPort cards, yet OS X refused to acknowledge their existence in the system.
My first tip is to try resetting the PRAM & NVRAM. In multiple cases, that has restored recognition of AirPort cards on PowerBooks. Here's how to do it:
http://docs.info.apple.com/article.html?artnum=2238
If that doesn't work, try resetting the NVRAM via Open Firmware:
http://docs.info.apple.com/article.html?artnum=42642
Otherwise, when you say your laptop is not acknowleding the card, do you mean the AirPort menu icon is "hollowed" out? If so, click on that menu icon and make sure it's simply not turned off. If it's "hollowed" out, but clicking the menu icon doesn't provide an option to turn it on, then it could need to be reseated (see my tip below on checking your manual for AirPort installation/replacement instructions) or is damaged.
If you're showing gray bars indicating no signal strength, check out this article for a possible solution on restting your trusted networks. The kernel panic (crashing of OS X) could have corrupted the AirPort preferences file:
http://docs.info.apple.com/article.html?artnum=300342
Here are some general Apple technical articles/sites you could also read through to try and resolve your issue:
PowerBook Support:
http://www.apple.com/support/powerbook/
PowerBook Manuals (which should include a section on installing AirPort cards, which you can use to help reseat your existing AirPort card:
http://www.apple.com/support/manuals/powerbook/
AirPort Quick Assist (Includes a section titled "I'm having trouble connecting to the Internet over AirPort"):
http://docs.info.apple.com/article.html?artnum=303595#trouble
Good luck, let us know if any of these tips work (or don't work)! If they don't, re-post to the PowerBook discussion board.

Similar Messages

Configure Solaris 10 with ath wireless card

So I'm in over my head on this one. I got a new laptop to tinker with, put OpenSolaris on it - integrated Broadcom wireless card didn't work, but my old DLink wireless card did. Yay. But I didn't like OpenSolaris. Too linux-y. So I went to something more familiar: Solaris 10. Only now the wireless card (neither of them, actually) doesn't work. I've googled and tried stuff for the past several hours and all I get is this:
"ath: unable to resolve dependency, module misc/net80211"
I've installed the packages. I've installed the 80211 for amd64 (yes, I'm running on an amd64). I've tried downloading the tarballs, extracting them and manually copying the kernel modules. Nothing. I've tried everything I know of (which isn't much, admittedly). I've tried update_drv, used /usr/X11/bin/scanpci, prtconf -pv to check out what all is connected, and everything says that there is an Atheros ethernet device on pci168c ... but I always get an "unable to attach device" error. And when I reboot, I'm bombarded with the aforementioned unable to resolve dependency" harassment.
What stupid thing am I doing wrong?!
Thanks in advance for your help -
Caleb

alan.pae wrote:
Completely remove the driver
pkgrm SUNWatheros
init 6
make sure that there is no ath file in the kernel directory and the same for the net80211 file.
touch /reconfigure
re-add the driver from some as yet undetermined media.
init 6
should work.
alanGot me closer, but it didn't work. I ended up going with Solaris Express Developer edition, and it worked out of the box. I really appreciate your help, though.
Do you have any recommended reading for delving into the depths of Solaris? I know enough to get myself into trouble and that's about it. I picked up the "Unix System Administration Handbook" (by Evi Nemeth, Garth Snyder, Scott Seebass and Trent Hein). I've learned a ton from there, which has really helped me get some of the basics, but it's not necessarily Solaris specific.
Thanks again for your help!!!

Wireless-Card doesn't not work with WPA/WPA2 but with WEP [Solved]

Hello I have a MacBook (late 2007) with a wireless-card from Broadcam, the card works with WEP and the classic configuration over rc.conf very well. But I can't get the card running with WPA and the net network-profiles.
Here is the link to the driver - http://www.broadcom.com/support/802.11/linux_sta.php
eth2 = wireless-card
eth1 = firewireanything
eth0 = wired-card
rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Europe/Berlin"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
#MODULES=(sky2 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="macbook"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
eth0="eth0 192.168.1.220 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(!eth0 !eth1 eth2)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.1.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
NETWORKS=(wireless)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng network net-profiles netfs alsa crond portmap fam hal)
/etc/network.d/wireless
CONNECTION="wireless"
INTERFACE=eth2
HOSTNAME=macbook
IP="static"
IFOPTS="192.168.1.225 netmask 255.255.255.0 broadcast 192.168.1.255"
GATEWAY=192.168.1.1
DNS1=192.168.1.1
# Wireless Settings (optional)
ESSID=3Com
#KEY=
IWOPTS="mode managed essid $ESSID channel 11"
#WIFI_INTERFACE=wlan0 # use this if you have a special wireless interface
# that is linked to the real $INTERFACE
#WIFI_WAIT=5 # seconds to wait for the wireless card to
# associate before bringing the interface up
USEWPA="yes" # start wpa_supplicant with the profile
WPAOPTS="" # use "" for normal operation or specify additional
# options (eg, "-D ipw")
# see /etc/wpa_supplicant.conf for configuration
Can I set here the WPA/WPA2-Key also? Why here ESSID? Do I need still a configuration in wpa_supplicant.conf?
Thats very confusing and not explained.
WPAOPTS? Do I need to add something like "-D wext"?
/etc/wpa_supplicant.conf
# This is a network block that connects to any unsecured access point.
# We give it a low priority so any defined blocks are preferred.
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
network={
key_mgmt=NONE
priority=-9999999
network={
ssid="3Com"
proto=WPA
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="topsecret"
priority=5
# WPA2
# proto=WPA RSN
I need help. Please
Last edited by hoschi (2009-01-04 20:21:58)

fwojciec wrote:If this info is not in the wiki it might be worth it to add it -- it's all detailed in /etc/network.d/examples/complete.example though.
Thats the reason why I was so confused.
My new and well working configuration:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Europe/Berlin"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
#MODULES=(sky2 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="macbook"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
eth0="eth0 192.168.1.220 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(!eth0 !eth1 !eth2)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.1.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
NETWORKS=(3com)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng network net-profiles netfs alsa crond portmap fam hal)
CONNECTION="wireless"
DESCRIPTION="Very verbose complete wireless example"
INTERFACE=eth2
HOSTNAME=macbook
# Interface Settings (use IP="dhcp" for DHCP)
IP="static"
IFOPTS="192.168.1.225 netmask 255.255.255.0 broadcast 192.168.1.255"
GATEWAY=192.168.1.1
# DNS Settings (optional)
DOMAIN=localdomain
DNS1=192.168.1.1
DNS2=
SEARCH=
# Standard Wireless Settings
ESSID=3Com
SECURITY=wpa-config # One of wep, wpa, wpa-config, none
KEY=""
# Scans to see if network is available before connecting (reccomended)
SCAN="YES"
# Time to wait to connect to a network. Default 15.
TIMEOUT=10
# Pass *custom* options to iwconfig. Usually not needed (optional)
IWOPTS="mode managed essid $ESSID channel 6 key restricted $KEY"
# Any extra arguments for wpa_supplicant
WPA_OPTS=
# For SECURITY='wpa-config' only - filename of a wpa-supplicant config
WPA_CONF=/etc/wpa_supplicant.conf
# This is a network block that connects to any unsecured access point.
# We give it a low priority so any defined blocks are preferred.
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
network={
key_mgmt=NONE
priority=-9999999
network={
ssid="Linksys"
proto=WPA RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="areulookingatmybreasts"
priority=5
network={
ssid="3Com"
proto=WPA
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="nomam"
priority=5
# WPA2
# proto=WPA RSN
There are also profiles for the Linksys-Router and for wired cable.
Thanks for the help!
Last edited by hoschi (2009-01-04 20:21:23)

Wireless card BCM4313 no connection at boot

Hi,
I have an HP Pavilion dv6 with a Broadcom BCM4313 wireless card. I use NETCFG and before the last kernel upgrade I was able to connect to my home wireless connection at boot without troubles. Now I have to do it manually and I need to try 2 or 3 times to see my connection active.
lspci -vnn
02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:1483]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at c3400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: brcmsmac
Kernel modules: bcma, wl, brcmsmac
lsmod
Module Size Used by
cpufreq_stats 3890 0
radeon 992718 0
ttm 54360 1 radeon
ipv6 290407 22
cpufreq_ondemand 6132 4
uvcvideo 64931 0
videodev 78006 1 uvcvideo
media 10437 2 uvcvideo,videodev
usbhid 35256 0
hid 81635 1 usbhid
v4l2_compat_ioctl32 8292 1 videodev
snd_hda_codec_hdmi 22092 1
joydev 9895 0
snd_hda_codec_idt 55175 1
i915 707307 7
snd_hda_intel 22122 0
snd_hda_codec 77927 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
drm_kms_helper 25409 2 radeon,i915
lib80211_crypt_tkip 8506 0
drm 183380 5 radeon,ttm,i915,drm_kms_helper
snd_hwdep 6325 1 snd_hda_codec
snd_pcm 73856 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer 19416 1 snd_pcm
r8169 42643 0
lib80211 4158 1 lib80211_crypt_tkip
snd 57786 7 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
sg 25557 0
hp_accel 13864 0
lis3lv02d 10508 1 hp_accel
i2c_i801 8187 0
serio_raw 4294 0
iTCO_wdt 12717 0
hp_wmi 7738 0
intel_agp 10904 1 i915
arc4 1410 2
btusb 11577 0
evdev 9530 9
bluetooth 138465 1 btusb
soundcore 6146 1 snd
bcma 13762 0
i2c_algo_bit 5199 2 radeon,i915
sparse_keymap 3088 1 hp_wmi
mei 31249 0
i2c_core 20133 7 radeon,videodev,i915,drm_kms_helper,drm,i2c_i801,i2c_algo_bit
iTCO_vendor_support 1929 1 iTCO_wdt
pcspkr 1819 0
snd_page_alloc 7121 2 snd_hda_intel,snd_pcm
intel_ips 11213 0
psmouse 55224 0
intel_gtt 14423 3 i915,intel_agp
mii 3995 1 r8169
input_polldev 2882 1 lis3lv02d
battery 10905 0
wmi 8411 1 hp_wmi
ac 3265 0
button 4470 1 i915
brcmsmac 594624 0
thermal 7863 0
video 11228 1 i915
brcmutil 6563 1 brcmsmac
mac80211 215605 1 brcmsmac
cfg80211 160516 2 brcmsmac,mac80211
rfkill 15402 3 hp_wmi,bluetooth,cfg80211
crc_ccitt 1331 1 brcmsmac
acpi_cpufreq 5877 1
freq_table 2451 3 cpufreq_stats,cpufreq_ondemand,acpi_cpufreq
processor 24256 1 acpi_cpufreq
mperf 1275 1 acpi_cpufreq
ext4 369556 2
mbcache 5817 1 ext4
jbd2 71074 1 ext4
crc16 1297 2 bluetooth,ext4
sr_mod 14951 0
sd_mod 28307 4
cdrom 36329 1 sr_mod
ahci 20865 3
libahci 18885 1 ahci
libata 173297 2 ahci,libahci
ehci_hcd 39511 0
scsi_mod 131482 4 sg,sr_mod,sd_mod,libata
usbcore 142544 5 uvcvideo,usbhid,btusb,ehci_hcd
dmesg | grep wlan0
[ 11.715805] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 13.791409] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 16.885059] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
[ 16.886567] wlan0: authenticated
[ 16.890100] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
[ 16.892793] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
[ 16.892798] wlan0: associated
[ 16.894146] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 26.697130] wlan0: deauthenticating from 50:67:f0:ab:4f:d4 by local choice (reason=3)
[ 87.612906] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 89.754106] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 92.849882] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
[ 92.851661] wlan0: authenticated
[ 92.851823] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
[ 92.854142] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
[ 92.854150] wlan0: associated
[ 92.855920] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 103.719958] wlan0: no IPv6 routers present
[ 105.980215] wlan0: deauthenticating from 50:67:f0:ab:4f:d4 by local choice (reason=3)
[ 120.237260] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 122.316759] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 125.422195] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
[ 125.423760] wlan0: authenticated
[ 125.423960] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
[ 125.426083] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
[ 125.426090] wlan0: associated
[ 125.428085] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 136.398877] wlan0: no IPv6 routers present
You could see that first I get the connection and then I lost it... for 2 or 3 times, then I could connect without problems.
ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:338 errors:0 dropped:0 overruns:0 frame:0
TX packets:338 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27772 (27.1 Kb) TX bytes:27772 (27.1 Kb)
wlan0 Link encap:Ethernet HWaddr E0:2A:82:A2:B5:88
inet addr:192.168.1.33 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::e22a:82ff:fea2:b588/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12484 errors:0 dropped:0 overruns:0 frame:0
TX packets:9606 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13841736 (13.2 Mb) TX bytes:1241490 (1.1 Mb)
iwconfig
wlan0 IEEE 802.11bgn ESSID:"WLAN_A9"
Mode:Managed Frequency:2.452 GHz Access Point: 50:67:F0:AB:4F:D4
Bit Rate=54 Mb/s Tx-Power=19 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=40/70 Signal level=-70 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:82 Missed beacon:0
my wirelessCasa netcfg profile
CONNECTION='wireless'
DESCRIPTION='A simple WEP encrypted wireless connection'
INTERFACE='wlan0'
SECURITY='wep'
ESSID='WLAN_A9'
KEY='s:mykey'
IP='dhcp'
POST_UP="notify-send -u critical -i /usr/share/icons/Faenza/status/48/connect_established.png -t 15000 'Connected to WLAN_A9'"
POST_DOWN="notify-send -u critical -i /usr/share/icons/Faenza/status/48/gnome-netstatus-disconn.png -t 15000 'Connection lost'"
# Uncomment this if your ssid is hidden
#HIDDEN=yes
rc.conf
NETWORKS=(wirelessCasa)
DAEMONS=(syslog-ng dbus net-profiles net-auto-wired !network !netfs crond laptop-mode alsa slim @acpid @cups)
When I execute netcfg for the first time (after boot) I see:
#NETCFG_DEBUG=yes netcfg wirelessCasa
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
:: wirelessCasa up [BUSY] DEBUG: status reported to profile_up as:
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up Configuration generated at /run/network//wpa.wlan0/wpa.conf
DEBUG: wireless_up ifup
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up wpa_check
DEBUG: wpa_cli -p /run/wpa_supplicant -i wlan0 status
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: ethernet_iproute_up ifup
DEBUG: ethernet_up dhcpcd -qL -t 10 wlan0
DEBUG:
> DHCP IP lease attempt failed.
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: ethernet_down if_down
DEBUG: wireless_down stop_wpa wlan0
DEBUG: profile_up connect failed
[FAIL]
And the second one:
#NETCFG_DEBUG=yes netcfg wirelessCasa
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
:: wirelessCasa up [BUSY] DEBUG: status reported to profile_up as:
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up Configuration generated at /run/network//wpa.wlan0/wpa.conf
DEBUG: wireless_up ifup
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up wpa_check
DEBUG: wpa_cli -p /run/wpa_supplicant -i wlan0 status
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: ethernet_iproute_up ifup
DEBUG: ethernet_up dhcpcd -qL -t 10 wlan0
DEBUG:
DEBUG: ethernet_iproute_up hostname archlap
[DONE]
I've tried to use the wl driver but it doesn't seems to work properly.
Could anyone help me please?
Thank you,
enrico

litemotiv wrote:
Hmm it seems your card now takes longer to connect, the 'deauthenticating by local choice' often means that the default timeout is reached and netcfg disconnects. You can try adding a specific timeout parameter to your netcfg profile:
TIMEOUT=60
That doesn't explain why it takes longer to connect than before, but at least you should be able to connect in 1 try again.
Hi,
thank you for your time!
I'v tried adding the timeout line to my profile but it doesn't change nothing
I could connect at 3rd try.
Any other idea?

Startup gets 'Network cable unplugged' on mini-PCI wireless card

I recently installed a Netgear DG834GT wireless router and now have an intermittent problem connecting my Tecra 9100 to it. If the 9100 has been shutdown for a while (like overnight), when I restart I always get 'Network cable unplugged' for the wireless connection. Rebooting a number of times (anything from 3 upwards) I eventually get connected to the router and all then works fine for hours. Even a quick restart at this point (i.e. once the wireless card has connected) does not cause a problem but as soon as I leave the machine shutdown for a length of time it fails again at reboot.
There are no errors in the Event log.
I am using the built in mini-PCI wireless card and have already upgraded to the latest driver.
Any ideas gratefully recieved, at the moment each morning is a 20-30 minute frustration of rebooting trying to get my connection working.
(Running Win2K Professional)

Checking other boards for help (Netgear etc.) it seems that the 'Network cable unplugged' is a common message when wireless connectivity is failing. However, to prove the point, I have disabled the other LAN card (for which I was also getting 'network cable unplugged' but as expected since it was). I still get the same issue with the wireless card, although now the reboots are slightly more predictable - it normally seems to succeed on the third reboot. I guess disabling the other card has changed the startup timing slightly and in that way made things slightly better.
Again, any other suggestions gratefully received. As this seems to be a timing issue at startup, I am suspicious that one of the other things that runs at that time is causing the problem.

Startup gets 'Network cable unplugged' on mini-PCI wireless card (again)

Reposting as previous topic has been locked although has not been resolved. Original post below, please see previous post for more details
I recently installed a Netgear DG834GT wireless router and now have an intermittent problem connecting my Tecra 9100 to it. If the 9100 has been shutdown for a while (like overnight), when I restart I always get 'Network cable unplugged' for the wireless connection. Rebooting a number of times (anything from 3 upwards) I eventually get connected to the router and all then works fine for hours. Even a quick restart at this point (i.e. once the wireless card has connected) does not cause a problem but as soon as I leave the machine shutdown for a length of time it fails again at reboot.
There are no errors in the Event log.
I am using the built in mini-PCI wireless card and have already upgraded to the latest driver.
Any ideas gratefully recieved, at the moment each morning is a 20-30 minute frustration of rebooting trying to get my connection working.
(Running Win2K Professional)

More info : I have found that this is time related rather than related to the number of reboots. It always fails on the first reboot after being shut down for a period of time. At this point, however long I wait the connection never comes up. However, if I wait a few minutes and then reboot, the second reboot will always successfully establish the connection.
On this basis, the problem has become slightly less annoying as I have a workaround - boot once, wait a few minutes and reboot. That being said, any information on how I can isolate this further (e.g. tracing what is running at startup) would be gratefully recieved.

Satellite Pro 4600 Wireless card does not work with WIN2K ?

I have a Satellite Pro 4600 with UK dealer installed PA3070U-1MPC wireless card running with Windows 2000
The wireless client manager finds the network of my wireless router and reports the signal is excellent and I see all green bars swhowing.
However I can't mske a connection, in 'connections' the wireless one says 'network cable is disconnected'
the router works ok with other laptops in my house.
I have latest version of Win2K also have downloaded and installed latest versions of client manager and WLAN card driver for win2k from toshiba website.
The 'toshiba support in Turkey' told me 'I need a different driver for Win2K for my wireless card cause the win2K driver on the toshiba website is not for 'this' wireless card'. I have waited for this for 3 weeks now and have been unable to reach the elusive UK Level 3 support who supposedly have this driver. I have seen on the internet the same wireless card is has been sold as a 'made by toshiba' accessory and it says it is compatible with Wim2K
What do I do next please ? Does this run at all with Win2K , is there 'another driver' and so on ?
Thanks

hello
please be more scpecific - what do you mean by 'disconnect the LAN' - I have nothing conneced there anyway ? do you mean 'disable' the LAN even though there is nothing plugged in ? can you please post the exact sequence of this so I can try ir too.
In the meantime my laptop has been to Toshiba for them to sort out at their highest level UK support base. I was hoping my troubles would be over - but no, read below what happened. They are basically saying my win2k is not in order but I had just installed and updated it so right now I haven't a clue what to do next.
START QUOTE of Toshiba Support response:
Sat Pro 4600
Serial No: 31474181G
Windows 2000 SP4 (customers build not recovery CD)
BIOS V1.80 not current therefore updated to V2.60
The notebooks wireless card is functional and has the correct driver installed, it also has the correct and latest version of the Wireless Client Manager. The wireless function appears to see the router but will not connect and obtain an IP address. Irrespective of the settings applied within Internet Explorer or the Wireless client manager you cannot obtain a connection. The customer did not have any Toshiba utilities installed such as, Power Saver, Common Modules, Chipset drivers, network device switch, I therefore installed these missing components and updated the BIOS to the most current revision. However despite this the unit will still not connect to the wireless.
I therefore removed the customers HDD and replaced his HDD with a Toshiba loan HDD with a fresh build that I had created. When using the machine with this build the wireless connected without issue and I was able to browse the internet etc. I placed the customers HDD into our machine and the problem with the wireless was replicated on our machine here, therefore the problem is not with the wireless card or any hardware aspect of the machine, the problem lies with the customer's build of Win 2000. I examined for anything obvious but could not find anything, therefore I'm sending this machine back to customer with the advice that his build needs addressing or he needs to reload Win 2000 his machine.
As you can see from the above comments, the machine performs as per specification with loan HDD and fresh build of Win 2000 installed, the problem is only present with you HDD and build in the machine. In addition to this I have replaced the missing screws on the base of the machine ensuring the machine is structure is maintained.
5 x B16 Screws
1 x B6 Screw
1 x Memory Cover Screw
END QUOTE

Can I put an Intel Advanced-N 6230 wireless card into my Pavilion dm4-3050us laptop?

I have been having problems with the wireless connection on my dm4-3050us laptop for several months now and am hoping to replace the wireless card in order to solve these issues.
Will I be able to put an Intel Advanced-N 6230 adapter into my machine?
If so, is there anything special I will need to do in order to make it work as it normally would? (i.e. special adapters to make it fit into the machine, driver updates, etc.)

You can use one of these:
Intel Centrino Advanced-N 6230 WLAN module 631956-001
Intel Centrino Ultimate-N 6300 WLAN module 572511-001
It HAS to be an HP branded card with the HP number. It is not good enough if it is another card with the same wifi chip. Only HP branded and numbered cards will allow the system to POST.
Here is the Service Manual:
Manual
See page 41. You may find that you need 3 antenna leads and the laptop only has 2. It is very hard to string another antenna lead but it can be done.
Here is the Advanced-N card on eBay which appears to have only 2 leads:
http://www.ebay.com/itm/GENUINE-OEM-HP-Pavilion-DV6-6000-WIFI-Wireless-Board-631956-001-/36077457082...
You will need to load the correct Intel driver and I would just have it downloaded to the laptop before you do the swap:
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-104707-1&cc=us&dlc=en&lc=en...
Link to the Windows 7 driver above. Good luck. This should be pretty much plug and play for you but post back if you need more help.
If this is "the Answer" please click "Accept as Solution" to help others find it.

Can't create a wireless network without a wireless card on my Mac

Help!
O.k. I tried searching the forums for an answer but the odd nature of my problem, and the immense database of topics made it very difficult to find a similar post.
The general issue/idea:
Run a wireless network using Airport Extreme - Connect desktop mac via ethernet and Roku player via wi-fi. Can't get the desktop mac to connect via ethernet when I restart the network/Airport Extreme.
My Father in law has my old computer; It's a PowerMac G5 (Dual 1.8GHz CPUs) running OS 10.5.8), connected to internet via cable (TimeWarner) modem. It does NOT have an Airport or Airport Extreme card installed. The computer works fine, and I don't believe that I 'need' an Airport Card in order to use the Airport Extreme (it's a brand new/refurbished model) in the manner described below.
I would like to use the Airport Extreme to generate/run a wireless network (Do I need an Airport Card in order to generate/run a wireless network? Doesn't the AE actually do that?), connect the desktop Mac to the network via Ethernet (I shouldn't need an Airport Card to do that, should I?) and connect a 'Roku Player (802.11g capable) to the network via wi-fi.
As far as I know, this should be possible.
Basic steps/as I understand them:
A. Connect ethernet from cable modem to AE.
B. Connect ethernet from AE to desktop Mac.
C. Create the wireless network using desktop Mac and Airport Utility.
D. Restart AE to start the wireless network running.
E. Connect Roku to wireless network over wi-fi.
I have no problems with A & B. Once the AE is connected to the desktop Mac, I'm able to get internet via ethernet as it passes through the AE. I can then create a wireless network (step C.) using the Airport Utility (and setup assistant). The problem starts after I've configured the wireless network.
Once I've configured the wireless network, the Airport Utility software prompts me to restart the AE in order to start the wireless network.
As soon as I restart the AE, my desktop Mac tries to connect to the 'wireless' network, even though it's already connected via ethernet. I don't have a wireless card in the Mac, and I don't want to connect the desktop using wi-fi/wireless. It's connected via ethernet, works fine during configuration, and I don't ever anticipate a desire to connect the desktop via wi-fi.
No matter what I do, I can't get the desktop to connect via ethernet. The only network connection option I'm offered is 'Rescan'. O.k. the desktop can't find the wireless network (because it doesn't have a wireless card), and I'm unable to continue with the Airport Utility. I can't make any further changes to the network (the options to manually change the network configuration are not available as the desktop Mac cannot currently talk to the AE - It's still trying to connect wirelessly), and the desktop has no internet connection as it's trying to connect wirelessly.
*How can I...*
*Setup/run a wireless network, while keeping the desktop Mac connected via ethernet?*
I'm perfectly willing to factory reset the AE and start over.
Any help appreciated.
Thwarted by the network.
- Robert

My Father in law has my old computer; It's a PowerMac G5 (Dual 1.8GHz CPUs) running OS 10.5.8), connected to internet via cable (TimeWarner) modem. It does NOT have an Airport or Airport Extreme card installed. The computer works fine, and I don't believe that I 'need' an Airport Card in order to use the Airport Extreme (it's a brand new/refurbished model) in the manner described below.
That is correct, you could connect the PowerMac G5, via Ethernet, to the AirPort Extreme Base Station (AEBS) or any other wired router for Internet access. You do NOT need an AirPort Card for wired access ... ONLY if you want the G5 to connect to a wireless network.
I would like to use the Airport Extreme to generate/run a wireless network (Do I need an Airport Card in order to generate/run a wireless network? Doesn't the AE actually do that?)
That is correct, the AEBS is a wireless router that can provide a wireless network. The AirPort Card, on the other hand is a wireless adapter used to allow a Mac to connect to a wireless network, created by any wireless router ... not just those provided by Apple.
As far as I know, this should be possible.
Basic steps/as I understand them:
A. Connect ethernet from cable modem to AE.
B. Connect ethernet from AE to desktop Mac.
C. Create the wireless network using desktop Mac and Airport Utility.
D. Restart AE to start the wireless network running.
E. Connect Roku to wireless network over wi-fi.
Yes, these are all good assumptions.
As soon as I restart the AE, my desktop Mac tries to connect to the 'wireless' network, even though it's already connected via ethernet. I don't have a wireless card in the Mac, and I don't want to connect the desktop using wi-fi/wireless.
Do you actually have an AirPort Card installed in the G5 now? If so, then it might be possible that the "firing order" for network connectivity has AirPort at the top of the list under System Preferences > Network. Just change the order to have Ethernet at the top and disable AirPort to ensure that the G5 connects by Ethernet only.

Wireless card seems to be not working

Hello everyone,
I haven't had any problems with my wireless card for my Macbook Pro since I purchased it, but something seems to be acting up now. Here's the situation...I went away for the weekend, took my laptop with me, didn't use the internet at all. Then I came back to my wireless card not working. It has a self-assigned IP address of 169.254.183.17. I did some reading on it and what people of said is that when you have this particular address your computer can't access the internet. I have power cycled both the router and modem correctly without any success.
I have another laptop that is windows based that can connect wirelessly so I've identified that it isn't a router problem. The thing that baffles me is that I can hard wire my Macbook into the router and achieve a connection...any suggestions on what I should try next?
Thanks in advance.
Message was edited by: Jaden Pretzlaw

Thanks for replying,
I did go into advanced settings to see what was up. And the TCP/IP tab was the area that I was focusing on. Okay...I did try renewing the DHCP lease and it keeps giving me the unusable IP address. One potential problem that may be contributing to this fiasco is that I think the modem in my household is also a router (which we're just using as a modem). The modem isn't mine so I'm not sure how it was setup. I don't believe that modem is activated to give off a wireless connection. I don't know why it would be a problem because I was connecting to the router just fine before. If the windows based laptop can connect just fine, it wouldn't be the router...(just thinking out loud here).
I was given an option by one of our IT personal at the office that I work at...he said that I could completely remove the network from my saved list and re-enter it. He also said that I would have to delete some temporary files that are saved in a hidden folder that are "preference" files for that specific network. I wasn't able to find that folder, and I did try deleting the network but it didn't seem to fix the situation. If I could simply just go back to square one, as I did when I first connected to the network I'm sure it would fix everything.
I hope this wasn't too long to read, hopefully it gives good insight.
Regards
Message was edited by: Jaden Pretzlaw

MBP having Kernel Panic (Crash) all the time due to Wireless card firmware.

Hi all,
I am desperately needing helps from the experts here now. I have the latest santa rosa Macbook Pro. It has been crashing on me lately due to the wireless card firmware. I have run all the latest updates from software update including the AirPort.Atheros firmware update. I have tried to reformat the hard drive and installed a fresh and clean Mac OSX. The crash still persists before AND after the AirPort.Atheros firmware update. I mean I was not having this issue when I first bought the computer while others were whining all over the internet about this problem. When the fix came out, everyone
s problems seem to be solved but my problem arose . A recent Kernel panic crash log is as following:
panic(cpu 1 caller 0x0035D113): freeing free mbuf
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x364539f8 : 0x128d08 (0x3cc0a4 0x36453a1c 0x131de5 0x0)
0x36453a38 : 0x35d113 (0x3ecf98 0x0 0x10 0x0)
0x36453a58 : 0x35d4b3 (0x4884fe00 0x0 0x246 0x1)
0x36453a78 : 0x51b56695 (0x4884fe00 0x0 0x20 0x4ee1d00)
0x36453be8 : 0x51b569d4 (0x3493c2c8 0x3493e148 0x36453c58 0x1416ad)
0x36453d38 : 0x51b62d85 (0x3493f004 0x0 0x4b285c 0x4c2ec070)
0x36453eb8 : 0x51b33d9a (0x3493c4c0 0x51bb8da4 0x36453ed8 0x19e23a)
0x36453f48 : 0x51b324a9 (0x4ce1004 0x0 0x36453fc8 0x19a001)
0x36453f78 : 0x13d7d9 (0x4ce1494 0x4ce1004 0x0 0x0)
0x36453fc8 : 0x19ad2c (0x0 0x0 0x19e0b5 0x5b3b3e0) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPort.Atheros(235.9.3)@0x51b31000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x4c63c000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x465e6000
dependency: com.apple.iokit.IO80211Family(162.1)@0x4c73b000
Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386
A way to know that the crash is gonna happen is that the internet stops working and as long as I click on the wifi icon on the menu bar, The crash occurs. Could someone please help to put me out of misery please . Thank you so much for reading this and any suggestions are greatly appreciated.
Thank you
Have a nice day.

i would try this in a test user to see if the issue occurs (more than likely it will)also i would reset the smc and the pram
(test user) go to the apple then system preferences then accounts then in the bottom right hand corner you will see there is a lock click it and put in the password for the computer then click ok then click the plus sign and create the test user make sure that you check the box that says allow user to admin the account then click create account (if a message says something about automatic login click keep) then click the apple and log out then login to the other user.
(smc) you shut the computer down then you unplugg all the cables from the computer then you take the battery out with the battery out you hold the power button down for five seconds then you put the battery back then plug in the ac adapter then start the comptuer up and then plug everything else back in
(pram) you restart the computer holding down the apple option P and R keys till you hear the start up chime twice
if that does not work i would boot to the install disk one holding c and then click utilites from the top and select the mac hd and then verify disk and repair disk
if the issue still occurs then i would back all of the information on the computer up and erase and install
hope this helps

Can i install a wireless card in my Satellite P30-141 's wireless bay?

The P30-141 doesn't come with wireless functionality and i can't track any wireless antennae cables which should reside within the top casing of the machine, but i'd like to know if it's possible to undertake my own installation of a toshiba wireless card? Would anyone out there know of a specific wireless card model / part number which could be used to do this? I'm quiet happy to tinker around inside the machine as it's four years past the warranty i believe and i've already replaced the LCD once, so i'm pretty familiar with the guts of it, just can't find any documentation on getting this component into this particular machine.
Any advice would be a great help!

Hi Simon,
Sure if you have the relevant PC slot inside, i'm checking a P30 - 131 (which i can't even find in the db here, think its foreign spec but a uk board) for one after telling my client it was easy. If you peek under the keyboard you can see a wire trench running from where the screen cable comes in to the main body. If its empty you need to fit the antenna cable, if present awesome just put in the relevant wireless card and clip on the antenna plugs. If the wires aren't present, simples.
They're quite cheap on everyones favourite auction site, you just need to get in under the screen bezel/surround and lay them down. They lay around the screen itself under the bezel. You'll find simple pictorials not necessarily for your specific laptop but they are mostly the same. Then bnring them through and lay them through the trench under the keyboard and clip into the wireless card. Well obviously you now have to set up the relevant drivers, curse a few times as it doesn't connect, wonder furiously at what is going wrong and then bing it'll suddenly connect although you've done nothing different over the past couple of days.......... The biggest issue you'll find is not to damage your bezel.
Anyway good luck, i'm gonna now try to work out if this model (see above) will do this.
peter

PCI wireless card does not work after restart - FM2-A55M-E33

Installed TP-LINK WN751ND wireless PCI card onto FM2-A55M-E33 motherboard. The card works fine after cold start, but does not work after restart. Windows recognises the card, but it gets code 10, cannot start.
BIOS is updated (v.11.1), as well as drivers and Windows 7 64.
I suspect that this might be the issue: Incorrect ASPM Transitions on the GPP Interface as found in ChipsetMotherboard_TechDocs/48671.pdf on AMD's official support site.
Does anyone know more about this issue?

Great! I've done that and now my card shows up. Thing is, when I try to get an IP address, it won't work. Here is the command output:
ieee80211 phy0: wl_ops_config: change monitor mode: false (implement)
ieee80211 phy0: wl_ops_config: change power-save mode: false (implement)
ieee80211 phy0: wl_ops_bss_info_changed: qos enabled: false (implement)
And then it times out and no IP is assigned. The thing is, wpa_supplicant stays alive after this time out, and I am unable to kill it (killall -9 wpa_supplicant won't kill it). At this point if I try to reboot the machine, it will stop at 'Rebooting' and won't go anywhere. If I turn off the wireless card in its switch Linux crashes. If I try to get an ip again (by running dhcpcd) the command will hang and not return to the shell anymore.
I am unable to find any useful information in the logs.
Got any more suggestions?
Thanks! (And sorry to disturb so much)

I have a 2009 Mac mini and the wireless card has never worked, would I be able to cover it with my three year extended warranty?

I have a 2009 Mac mini and the wireless card has never worked, would I be able to cover it with my three year extended warranty?

matthewfromwhangarei wrote:
I have a 2009 Mac mini and the wireless card has never worked, would I be able to cover it with my three year extended warranty?
If you mean AppleCare, then I would believe the answer will be yes.
First make sure you have a full backup of everything on your Mac, then run, don't walk to your nearest Apple store.
Note: Due to your Mac now being in computer years, somewhat elderly, Apple may not have the require parts in stock. This will either mean you might have to leave it with them for a number of days, or maybe they will offer you a new Mac mini. While a new Mac mini (if offered) might be a welcome possibility be aware that the new Mac mini no longer has a CD/DVD drive and it comes with Mac OS X Lion and as a result might not run some of your old software.

Airport Wireless Card not connecting to ABS

I updated my ABS firmware a few weeks back when many people did and had issues with the update, no wireless connection. I rolled back to the previous ABS firmware version with no luck. I went thru several hard resets and go nothing. So I just went ahead and updated to the current ABS firmware version. I have no problem using the internet over the lan and other computers can connect wirelessly, but the wireless on the G4 Ti won't connect. It shows and error window. I thought the wireless card went dead, but it works just fine on other wireless networks. Any thoughts would be great.
Powerbook G4 Ti OS X 10.4

ok i'm back again. so now i'm on to the internet but my connection is really weak, 1 bar. i talked to the guy who installed the wireless router and he said that its because the aerial is in the base and has to receive the signal through my desk. but he also said that he didn't know much about Mac's. so i'm not to sure he knows what he's talking about. is there any other reason why i'm getting a weak connection. i tried moving my mac around but that did not help.
Mac OS X (10.4.7)

A now unrecognized wireless card

Similar Messages

Maybe you are looking for