Do I get a wireless card or adapter? Do I update firmware or software?

I am about to use wireless internet for the first time and I don't really know what I'm doing.
1) We have cable high-speed internet with an 11g router. I need a wireless card or adapter. (is there a difference between card and adapter?) Looking for them online, it's often hard to tell which ones will work with my system. Any suggestions will be very helpful.
2) I am also wondering if I need to update AirPort Setup Assistant. I have version 3.4. Also, do I need a firmware update and, if so, what version and where I would get it?
Any other suggestions about going wireless will be appreciated.

As for my computer model, her is everything System Profile says about the hardware:
Machine Model: Power Mac G4
CPU Type: PowerPC G4 (2.9)
Number Of CPUs: 2
CPU Speed: 450 MHz
L2 Cache (per CPU): 1 MB
Memory: 512 MB
Bus Speed: 100 MHz
Boot ROM Version: 4.2.8f1
Serial Number: XA1020G5K53
Sales Order Number: 0100339025XA1020G51234123412341234
Responding to suggestions mentioned above: From what I have read, a bridge will only work with another bridge. (and the link you provided was for a device that only worked with Windows).
I am trying to connect to a router. Surely, there is an Airport card that will work with my computer. Airport software comes with the Panther installation CD's. I just updated my Airport software to version 4.2.
As I understand it, I could also use a USB Wireless Adapter. Is this an option instead of an Airport card, or do I still need the card?
And I don't understand what Airport firmware is for. For an Airport card, or is it for an Airport router, and irrelevant unless I get an Apple router (like the Airport Express)?
Any suggestions will be appreciated.

Similar Messages

Getting a wireless card working on a G5 PowerMac.

Hello there.
I am trying to help a friend get a wireless card working on his PowerMac. So far the machine knows about the card is there but it isn't working as an Airport.
Two cards have been tested, an Apple branded one and now a generic PC one which looks to be using the same chip-set coincidentally. The PC one had some Mac drivers which my friend said he installed, but somehow he ended up with FUSE on his system. :-? I don't know why that happened as a file-system handler isn't going to help get wireless working that I know of! LOL. :-D
The driver CD is missing now so I can't check it. And the box has nothing about the card. So I wouldn't even know where to get a compatible driver. I have searched using the PCI info but no luck.
The Apple card has Apple A1027 stamped on it. And the antenna has been connected on it AFAICT. I've also read Atirport cards can't simply be plugged into the PowerMac and an Apple technician must install it. Could this be the case? And what about the generic PC wireless card then?
The end result is that the machine knows the hardware is there but it can't get any wireless communication working. Also, a Apple Base Station has now replaced a wireless router. So can that be made to run a diagnostic and see if it find the Airport itself? Or even the same on the Mac?
Here is the Mac model:
Machine Name: Power Mac G5
Machine Model: PowerMac11,2
CPU Type: PowerPC G5 (1.1)
Number Of CPUs: 2
CPU Speed: 2.3 GHz
L2 Cache (per CPU): 1 MB
Memory: 1.5 GB
Bus Speed: 1.15 GHz
Boot ROM Version: 5.2.7f1
Serial Number: YM5430AUR6V
PCI info, both cards are the same:
bcom5714:
Type: network
Bus: PCI
Slot: GIGE
Vendor ID: 0x14e4
Device ID: 0x166a
Subsystem Vendor ID: 0x106b
Subsystem ID: 0x0085
Revision ID: 0x0003
AirPort Card:
AirPort Card Information:
Wireless Card Type: AirPort Extreme
Wireless Card Locale: USA
Wireless Card Firmware Version: 405.1 (3.90.34.0.p18)
Current Wireless Network: wireless network not available

Hypex wrote:
I am trying to help a friend get a wireless card working on his PowerMac.
You might find some useful advice here:
http://www.ifixit.com/Answers/View/27758/Howdo+I+install+the+airport-bluetooth+card+in+a+late+2005model
a Apple Base Station has now replaced a wireless router. So can that be made to run a diagnostic and see if it find the Airport itself? Or even the same on the Mac?
System Profiler (Apple menu -> About This Mac -> More Info) should show if the AirPort card is recognized. I'd then try to add an AirPort connection item in the Network panel of System Preferences, enable the AirPort menu bar item, then try to turn AirPort on.

Getting message "video card full" when trying to update imovie 08 to 11...just updated to to OS X 10.7.5. What to do??

getting message 'video card full" when trying to update imover 08 to 11...I have just updated to OS X10.7.5. What to do?

getting message 'video card full" when trying to update imover 08 to 11...I have just updated to OS X10.7.5. What to do?

Going Bonkers Trying to Get Wavelan Wireless card to work on my Lombard

Have OSX 10.2. Cannot get a wireless connection. Downloaded the AIRPORT Software for MAC OS 10.2. System sees the WAVELAN and NETWORK has it as A BUILT IN ETHERNET CARD. What am I doing wrong?. Neither light on my Wavelan card works but this card works on other laptops.

I followed these instructions
http://wirelessdriver.sourceforge.net/install.html
I pinged by router using my PC and got
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.
C:\DOCUME~1\OWNER>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : james-5b00eefe4
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : myhome.westell.com
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . : myhome.westell.com
Description . . . . . . . . . . . : NETGEAR WG121 802.11g Wireless USB2.
0 Adapter
Physical Address. . . . . . . . . : 00-09-5B-A3-79-B5
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.47
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.1
Lease Obtained. . . . . . . . . . : Friday, December 29, 2006 6:55:47 PM
Lease Expires . . . . . . . . . . : Saturday, December 30, 2006 6:55:47
PM
C:\DOCUME~1\OWNER>
Only problem I am confused is on the help link above is where it says ROUTER under Subnet mask. All the WAVELAN does is blink.

Wireless card in PC slot not recognized by Airport software

Since upgrading to Tiger from 10.3.9, I have not been able to use my wireless card (MacWireless cardbus 802.11g) in my PB G4 667 after I eject the card and reinsert. The PC Card menu item recognizes the card, but not Airport. If I leave the card in and put the machine to sleep, Airport will recognize the card. It's only when I turn off Airport, power off the card, and eject it to transport my laptop that I can't get Airport to work. The only solution is a restart. This worked fine under 10.3.9, but now is broken. I have tried deleting my preferences (which MacWireless support recommended) at:
Library/Preferences/System Configuration/preferences.plist
But that does not help either.
Powerbook G4 667 Mac OS X (10.4.4)

But is there any reason that the card isnt getting power, there are no green lights on the end of the card like there was when it worked. I still do have my IOXperts driver under other. But when I click it all values in status is N/A. The diagnostics button when pushed shows ""Diagnostics: Firmware versions: (Blank). Il try what you say but I dont think the pane is the issue.

Getting WMP100N Wireless card to acquire network from a WRT54G Wireless Router

Card is version 1.0 and router =Version 6. Have had router for a while (Slaved it off a wired router and used just for laptop connectivity to the wired net.) Have moved and found that wireless connection is more advantageous here. Bought a WMP100N. Installed and ran the setup. It connects to the router with a sterling signal. However, the card can not seem to find or connect with the network. According to the FAQs, it is suggested that my firewall conflicts with the hardware firewall in the router. Well, the router worked fine with Zonealarm when it connected thru a wired Linksys network card. What's different about the wirelesss card and how do I get it to connect? By the way, I was not aware that my router came with an organic firewall. I know that it was NAT configured (which functions as a de facto firewall) but not that it specifically contained a hardware firewall. Also, I still have the wired card installed in the machine. I've disabled it. I have tried just unplugging the cable. I haven' uninstalled it. My firewall ignores the old card when I disable it (As it should.) However, it still doesn't connect with the wireless. I'm afraid to kill Zonealarm and be protected with a supposed firewall that I'm not sure exists.

Try uninstalling & reinstalling the adapter & it will definately work!!

Can't get Broadcom wireless card working

Hello everyone. First and foremost, I'm not a newbie to Linux, just to Arch, so I do kinda know what I'm doing
I've got my laptop with a Broadcom BCM4328. I followed the steps on the Wiki page to the letter, but I've got nothing: the wireless doesn't initialize, and I have no interface for the wireless. I've provided my output for a few commands below if it helps. I'm using the latest kernel as I just installed Arch today. Any suggestions would be greatly appreciated.
[joshua@W01-Zeus ~]$ lspci | grep Broadcom
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
0c:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)
[joshua@W01-Zeus ~]$ sudo modprobe wl
[joshua@W01-Zeus ~]$ lsmod | grep wl
wl 1287680 0
lib80211 7172 1 wl
Last edited by djbon2112 (2009-10-27 16:25:15)

the modules that i'm talking about are b43, b43legacy and ssb. but looking at your devices ssb is needed by b44(ethernet module).
your MODULES should look like this:
MODULES=(wl !b43 !b43legacy...)
not that wl is first in this array
Last edited by wonder (2009-10-27 17:20:32)

Wireless Cards and Linux

What are some wireless cards that play nice with linux? Something that works out of the box for most distros and Arch? This freaking belkin card isn't working, I'm going to sell it on eBay... Any suggestions?

After recently playing with this myself I actually have some answers... your best bet is to get a wireless card that works with the linux-wlan-ng driver. This page gives you a list of PCMCIA, USB and PCI cards that work with the driver. I got a D-Link DWL-122 802.11b 11 Mbps USB Adapter... after you find an adapter that you like (and works) the key is configuring it.
First of course you want to find the driver that works with your adapter out of the linux-wlan-ng set. My usb D-Link works with the prism2_usb module (driver). Reading the readme helps alot when trying to configure your card. So depending on if your card is USB or PCMCIA you will first have to modprobe your USB or PCMCIA module and then modprobe the corresponding linux-wlan-ng driver.
Example:
modprobe uhci_hcd
modprobe prism2_usb
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
wlanctl-ng wlan0 lnxreq_autojoin ssid=<your routers SSID name> authtype=opensystem
dhcpcd wlan0
To get all the packages you need:
pacman -S wireless_tools wlan-ng26 (or wlan-ng24 for 2.4 kernel)
and pcmcia-cs package for PCMCIA cards
All of this will get you started with using a wireless card, but each time you reboot your machine you will lose your network info. So what you probably want to do is use a init script to startup each time you boot. There is a wlan script that comes with these packages located at /etc/rc.d/wlan
I hope this helps!

Where can I find a wireless card for my early 2009 Mac Pro (MB871LL/A, MacPro4,1)?

Where on on earth can I purchase a wireless card for my Mac Pro?
Apple is of no help. Their "Geniuses" told me that it is impossible for them sell one to me because Apple will not supply wireless cards or memory for previous generation computers. That is totally absurd. If I want to get a wireless card for my 2 year young computer I can't? I have to buy a brand new computer with one previously installed. Ridiculous!
Any help or suggestions would be of great value to me.

Well I found what I think is the correct card on B&H.
Hopefully it works....
http://www.bhphotovideo.com/c/product/682954-REG/Apple_MB988Z_A_AirPort_Extreme_ Card_for.html

Setup wireless card during bootup

Hey,
It took my awhile to get my wireless card to work but I finally got it to work. In the beginning, I had to type every command to get my wireless card to work. A little later my friend made a script that runs during start up. But it encountered a problem. When the command ''dhcpcd ath0" it would just hang so I took that out. It ran fine but now I have to run "dhcpcd ath0", let it run for 4 or 5 seconds, then kill it with ctrl + c, and then finally run it again. My connection is then established. So this gets a little annoying.
Now I come to you, the community. What is the best way to setup a wireless card during boot-up? My friend (yes, its the same one as before ) said that there was a wireless script or profile that most people use. Would this help? Thanks.

amunimanghi wrote:
# Network Profile
DESCRIPTION="Default Network Profile"
# Network Settings
INTERFACE=ath0
HOSTNAME=manghi
# Interface Settings (use IFOPTS="dhcp" for DHCP)
IFOPTS="dhcp"
GATEWAY=192.168.0.1
# DNS Settings (optional)
DOMAIN=localdomain
DNS1=192.168.0.1
DNS2=
# Wireless Settings (optional)
ESSID=FMang
KEY=**********(inputed key)
#IWOPTS="mode managed essid FMang channel 6 key restricted A16B61B296"
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
#AUTOWPA="yes" # automatically configure WPA
#PASSKEY="" # wpa passkey/phrase. for use with AUTOWPA
Is this correct?
Not entirely.
Comment everything in the DNS section , it's not used with dhcp and could cause conflicts
In wireless settings
- uncomment the line for IFOPTS
- comment the line WIFI_INTERFACE (iirc it's only needed with ndiswrapper)
Change the DESCRIPTION field to something appropriate like "Wlan at home"

Firewire card or adapter for g7 1237dx

I have a G7-1237dx. Can I get a firewire card or adapter to allow me to run pro tools? Need a 6pin firewire solution.
thanks
Steve

If the "dual mirror" Power Mac G4 is the model immediately before the last one with FireWire 800, then it has FireWire 400. You need an cable like this one with FireWire 400 (6-pin) on one end and FireWire 800 (9-pin) on the other end
http://eshop.macsales.com/item/Newer%20Technology/1394B96036/
Will also be moving data from a Lacie d2 external hard drive to the imac
Again, it depends on the type of connector it has. If it has FireWire 400, then that same cable will work. If it has FireWire 800, the you need a regular FireWire 800 cable with a 9-pin connector at both ends.
http://eshop.macsales.com/item/Newer%20Technology/1394B99036/

Pcmcia wireless card

Hi all!
I have just installed arch and I'm trying to get my wireless card (DWL 650+) running. I followed the wireless instructions on the site but I can't get it to work. Can anyone help?
$ lspcmcia
Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:00:0a.0)
CardBus card -- see "lspci" for more information
Socket 1 Bridge: [yenta_cardbus] (bus ID: 0000:00:0a.1)
$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
00:07.4 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50)
00:07.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 30)
00:0a.0 CardBus bridge: Texas Instruments PCI1420
00:0a.1 CardBus bridge: Texas Instruments PCI1420
00:0e.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link)
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
02:00.0 Network controller: Texas Instruments ACX 100 22Mbps Wireless Interface
$ ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:46:70:B4:FC
inet addr:192.168.1.183 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::a00:46ff:fe70:b4fc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6221 errors:0 dropped:0 overruns:0 frame:0
TX packets:6465 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4714153 (4.4 Mb) TX bytes:1817155 (1.7 Mb)
Interrupt:10 Base address:0xa800
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:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:600 (600.0 b) TX bytes:600 (600.0 b)

I followed this guide. But nothing the interface doesn't show up in iwconfig
http://wiki.archlinux.org/index.php/Wir … X100.2F111
I took a quick look at messages.log and these messages seem relevant
Jun 27 05:51:25 myhost pccard: CardBus card inserted into slot 0
Jun 27 05:51:25 myhost PCI: Enabling device 0000:02:00.0 (0000 -> 0003)
Jun 27 05:51:25 myhost ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKA] -> GSI 9 (level, low) -> IRQ 9
Jun 27 05:51:25 myhost acx: found ACX100-based wireless network card at 0000:02:00.0, irq:9, phymem1:0x24010000, phymem2:0x24000000, mem1:0xd0a66000, mem1_size:4096, mem2:0xd0a80000, mem2_size:65536
Jun 27 05:51:25 myhost initial debug setting is 0x000A
Jun 27 05:51:25 myhost using IRQ 9
Jun 27 05:51:25 myhost acx: need to load firmware for acx100 chipset with radio ID 0d, please provide via firmware hotplug:
Jun 27 05:51:25 myhost acx: either one file only (<c>ombined firmware image file, radio-specific) or two files (radio-less base image file *plus* separate <r>adio-specific extension file)
Jun 27 05:51:25 myhost requesting firmware image 'tiacx100c0D'
Jun 27 05:51:25 myhost acx_write_fw (main/combined): 0
Jun 27 05:51:25 myhost acx_validate_fw (main/combined): 0
Jun 27 05:51:25 myhost acx: timeout waiting for eCPU. reset_dev() FAILED
Jun 27 05:51:25 myhost ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jun 27 05:51:25 myhost acx_pci: probe of 0000:02:00.0 failed with error -5
Last edited by dTr (2007-06-27 15:47:10)

[SOLVED] Broadcom wireless card behaving very strangely

My wireless card has become unusable in an obscure fashion after a reboot. It may have been due to the recent kernel update, but I rebooted once after that update and the card was fine, so I'm not sure. Wireless was working without a hitch for months before this.
I have a Macbook Pro 9,1 with a Broadcom BCM4331 wireless card. I use the b43 firmware.
The firmware is being loaded on boot, but that vague "link is not ready" error appears every time the system attempts to load the firmware:
[ 12.263906] b43-phy0: Broadcom 4331 WLAN found (core revision 29)
[ 12.264337] b43-phy0: Found PHY: Analog 9, Type 7 (HT), Revision 1
[ 12.264864] Broadcom 43xx driver loaded [ Features: PMNLS ]
[ 12.728423] systemd-udevd[210]: renamed network interface wlan0 to wlp3s0
[ 15.801790] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 15.888891] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 186.474169] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 186.561426] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 326.465714] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 326.552778] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 683.592477] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 683.679541] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 1350.060493] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1350.147545] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 1474.360067] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1474.447162] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 1667.887393] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1667.967795] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 2110.770119] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 2110.857285] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
When I try to use netctl to connect to my home network, I get the same error:
-- Unit [email protected] has begun starting up.
Jan 22 18:36:40 tenfoxes network[3072]: Starting network profile 'home'...
Jan 22 18:36:41 tenfoxes kernel: b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jan 22 18:36:41 tenfoxes kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Jan 22 18:36:56 tenfoxes network[3072]: WPA association/authentication failed for interface 'wlp3s0'
Jan 22 18:36:56 tenfoxes network[3072]: Failed to bring the network up for profile 'home'
Jan 22 18:36:56 tenfoxes systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
Jan 22 18:36:56 tenfoxes systemd[1]: Failed to start Networking for netctl profile home.
If I scan for networks using iw dev wlp3s0 scan, I get no output. Here's the debug output from that if it means anything to anyone—from the docs on netlink I read it doesn't seem to show anything unusual:
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 26 <0x1a>
.flags = 5 <REQUEST,ACK>
.seq = 1390438118
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 33
.version = 0
.unused = 0
[PAYLOAD] 16 octets
08 00 03 00 03 00 00 00 08 00 2d 00 04 00 01 00 ..........-.....
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 2 <ERROR>
.flags = 0 <>
.seq = 1390438118
.port = 3698
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.type = 26 <0x1a>
.flags = 5 <REQUEST,ACK>
.seq = 1390438118
.port = 3698
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438119
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 1
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 116
.type = 16 <genl/family::nlctrl>
.flags = 0 <>
.seq = 1390438119
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 1
.version = 2
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
[ATTR 01] 2 octets
10 00 ..
[PADDING] 2 octets
00 00 ..
[ATTR 03] 4 octets
02 00 00 00 ....
[ATTR 04] 4 octets
00 00 00 00 ....
[ATTR 05] 4 octets
07 00 00 00 ....
[ATTR 06] 20 octets
14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
0e 00 00 00 ....
[ATTR 07] 24 octets
18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
6e 6f 74 69 66 79 00 00 notify..
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 2 <ERROR>
.flags = 0 <>
.seq = 1390438119
.port = 3698
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.type = 16 <0x10>
.flags = 5 <REQUEST,ACK>
.seq = 1390438119
.port = 3698
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438120
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 0
.unused = 0
[ATTR 02] 8 octets
6e 6c 38 30 32 31 31 00 nl80211.
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438121
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 1
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 116
.type = 16 <genl/family::nlctrl>
.flags = 0 <>
.seq = 1390438121
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 1
.version = 2
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
[ATTR 01] 2 octets
10 00 ..
[PADDING] 2 octets
00 00 ..
[ATTR 03] 4 octets
02 00 00 00 ....
[ATTR 04] 4 octets
00 00 00 00 ....
[ATTR 05] 4 octets
07 00 00 00 ....
[ATTR 06] 20 octets
14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
0e 00 00 00 ....
[ATTR 07] 24 octets
18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
6e 6f 74 69 66 79 00 00 notify..
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 2 <ERROR>
.flags = 0 <>
.seq = 1390438121
.port = 3698
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.type = 16 <0x10>
.flags = 5 <REQUEST,ACK>
.seq = 1390438121
.port = 3698
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438122
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 0
.unused = 0
[ATTR 02] 8 octets
6e 6c 38 30 32 31 31 00 nl80211.
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438123
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 1
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 116
.type = 16 <genl/family::nlctrl>
.flags = 0 <>
.seq = 1390438123
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 1
.version = 2
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
[ATTR 01] 2 octets
10 00 ..
[PADDING] 2 octets
00 00 ..
[ATTR 03] 4 octets
02 00 00 00 ....
[ATTR 04] 4 octets
00 00 00 00 ....
[ATTR 05] 4 octets
07 00 00 00 ....
[ATTR 06] 20 octets
14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
0e 00 00 00 ....
[ATTR 07] 24 octets
18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
6e 6f 74 69 66 79 00 00 notify..
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 2 <ERROR>
.flags = 0 <>
.seq = 1390438123
.port = 3698
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.type = 16 <0x10>
.flags = 5 <REQUEST,ACK>
.seq = 1390438123
.port = 3698
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438124
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 0
.unused = 0
[ATTR 02] 8 octets
6e 6c 38 30 32 31 31 00 nl80211.
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438125
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 1
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 116
.type = 16 <genl/family::nlctrl>
.flags = 0 <>
.seq = 1390438125
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 1
.version = 2
.unused = 0
[ATTR 02] 7 octets
6e 6c 63 74 72 6c 00 nlctrl.
[PADDING] 1 octets
00 .
[ATTR 01] 2 octets
10 00 ..
[PADDING] 2 octets
00 00 ..
[ATTR 03] 4 octets
02 00 00 00 ....
[ATTR 04] 4 octets
00 00 00 00 ....
[ATTR 05] 4 octets
07 00 00 00 ....
[ATTR 06] 20 octets
14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
0e 00 00 00 ....
[ATTR 07] 24 octets
18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
6e 6f 74 69 66 79 00 00 notify..
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 36
.type = 2 <ERROR>
.flags = 0 <>
.seq = 1390438125
.port = 3698
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.type = 16 <0x10>
.flags = 5 <REQUEST,ACK>
.seq = 1390438125
.port = 3698
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 32
.type = 16 <genl/family::nlctrl>
.flags = 5 <REQUEST,ACK>
.seq = 1390438126
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 3
.version = 0
.unused = 0
[ATTR 02] 8 octets
6e 6c 38 30 32 31 31 00 nl80211.
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 172
.type = 26 <0x1a>
.flags = 0 <>
.seq = 0
.port = 0
[GENERIC NETLINK HEADER] 4 octets
.cmd = 34
.version = 1
.unused = 0
[PAYLOAD] 152 octets
08 00 01 00 00 00 00 00 08 00 03 00 03 00 00 00 ................
0c 00 99 00 01 00 00 00 00 00 00 00 08 00 2d 00 ..............-.
04 00 00 00 74 00 2c 00 08 00 00 00 6c 09 00 00 ....t.,.....l...
08 00 01 00 71 09 00 00 08 00 02 00 76 09 00 00 ....q.......v...
08 00 03 00 7b 09 00 00 08 00 04 00 80 09 00 00 ....{...........
08 00 05 00 85 09 00 00 08 00 06 00 8a 09 00 00 ................
08 00 07 00 8f 09 00 00 08 00 08 00 94 09 00 00 ................
08 00 09 00 99 09 00 00 08 00 0a 00 9e 09 00 00 ................
08 00 0b 00 a3 09 00 00 08 00 0c 00 a8 09 00 00 ................
08 00 0d 00 b4 09 00 00 ........
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 28
.type = 26 <0x1a>
.flags = 773 <REQUEST,ACK,ROOT,MATCH>
.seq = 1390438127
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 32
.version = 0
.unused = 0
[PAYLOAD] 8 octets
08 00 03 00 03 00 00 00 ........
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 20
.type = 3 <DONE>
.flags = 2 <MULTI>
.seq = 1390438127
.port = 3698
[GENERIC NETLINK HEADER] 4 octets
.cmd = 0
.version = 0
.unused = 0
--------------------------- END NETLINK MESSAGE ---------------------------
If I try to use wpa-supplicant, it will say "Successfully initialized wpa_supplicant" as if it had properly made a connection, but it hasn't. Running iw dev wlp3s0 link will show that the card isn't connected to anything, and of course the internet still doesn't work.
I know it's not a hardware problem because the wireless works fine in Mac OS.
What gives? Is there a way I can investigate this further? It seems like a driver and/or kernel issue but I'm not really sure how to nail that down with confidence. I couldn't find any reports in the kernel bug tracker about this or anything, so maybe it's just me and I'm doing something wrong.
Thanks!
Last edited by tenfoxes (2014-01-24 02:44:16)

Yay, that worked!
I guess I really should've tried that initially, huh? Since the wiki said not to use it unless you had an unsupported wireless card, I figured I shouldn't (b43 officially supports mine). Still, considering that it's easy to install/uninstall drivers, my caution was obviously unwarranted.
Thanks for your help!

WIreless Card for G5?

Hey guys, I have one of the older Powermac G5's with a dual 2.3 processor running OS 10.3 Panther (I think from 2004). I was looking to get a wireless card that would work in the computer. Any suggestions?

LouisB,
Is your daughter's G5 the one listed in your signature? If so, you can use Apple's Airport Extreme card, or you can go with various USB solutions. The Airport Extreme cards are available here and you may need the antenna if you can't find the original (her G5 would have shipped with both the Airport and Bluetooth antennas, even if the requisite cards weren't inside the computer).

Compatible Wireless Card

Hey all!
I have a question, I bought a G4 Power Book in March 2004, prior till the Air Port Extremes release. I'm only wired for an Airport Card. I didn't buy one at the time because my college campus (Ithaca College) wasn't yet wired for wireless. I know live off campus and the campus has gone wireless, as has my house. I'd really like to get a wireless card, but I cannot seem to find the regular Airport card anywhere, and I can't find a third party wireless card either. I know of the D-Link DWL 122 that works, however, they no longer ship that one and I found it on Ebay but I'd prefer not to go that route, any ideas please?

http://www.smalldog.com/product/32833
It may seem a bit expensive, but the internal AirPort card has several benefits, such as being totally enclosed in your computer. The AirPort card is fully compatible with all of Apple operating systems. If you go the D-Link route, be advised that several people have had some difficulties configuring it properly, the device is external and you would have to drag it around with you when you travel, and it relies on separately installed drivers which may require updating (by D-Link) whenever Apple releases a new OS update. Caveat Emptor.

Do I get a wireless card or adapter? Do I update firmware or software?

Similar Messages

Maybe you are looking for