PC Wireless card in OSX

+I know there is a list of PC cards using Broadcom chips that work in OSX+
+So let's leave that out of this discussion+
I was looking into 802.11b PC cards that work in OSX
More specifically the Proxim Skyline card (model 473a, FCC ID Number PD5LMWP100)
http://tinyurl.com/2v2rwj
It works in OS9 just fine, but I have a friend who I have to mail the Skyline card to if it does indeed work for OSX for his Lombard.
I thought this driver may work, http://wirelessdriver.sourceforge.net/ but I have no firsthand experience with it and I don't know if the Proxim card uses Prism chips. The site mentions a Skyline card but I am not sure if its an earlier version or manufacturer

Langdon,
For what it's worth, I have no experience with that card, but if it runs under 9.x with Apple's AirPort software, it indeed has the Prism chipset. The original AirPort card used the same chipset and is the only one AirPort software supports in 9.x.
The iOXperts driver lists the Proxim/Farallon Skyline 802.11b PC Card as supported along with the Lucent WaveLAN PC cards, the same card supported by AirPort's 2.0.4 software:
http://docs.info.apple.com/article.html?artnum=120120
http://www.ioxperts.com/devices/devices_80211b.html
Assuming the PC card has the Prism chipset, the Sourceforge driver should work although it has not been updated since 10.2.x; I recall a few posts long ago that it still worked under 10.3.x but don't know if that included all versions of 10.3.
Here is another reference to the card (sorry, no attribution for quote):
"WaveLAN/ORiNOCO PC Card from Lucent/Agere/Proxim - These cards go by a variety of names under a variety of brands, for $45 USD or less (as of April 2003). They're easily available new or on eBay. The cards were originally developed by Lucent Technologies as the WaveLAN series, and Apple's AirPort cards use the same technology, which is why the Lucent (etc.) cards work well with Apple hardware and software. The cards moved to Agere Systems under the ORiNOCO name, and Proxim bought Agere. Even more confusing, other companies have re-branded the cards as their own. Avaya, Buffalo, and Compaq all sell them, and the one I use is a Dell TrueMobile 1150 Gold—but it's the same old Lucent card at heart (just look for the Lucent on the back label.)"

Similar Messages

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

I need to connect a eMac - power mac 6,4 -PowerPC G4 (1.1) to the internet wirelessly running mac osx 10.4.11.

I need to connect a eMac - power mac 6,4 -PowerPC G4 (1.1) to the internet wirelessly running mac osx 10.4.11.
Can anyone advise me please. I have done some research and think a USB adapter is the best option as I doubt the eMac will be able to take a card but the software will have to be able to run on tiger.

Check this one out:
http://eshop.macsales.com/item/NewerTech/MXP3802NU2C/
Might be an idea to ask them for confirmaion that it will work with your Mac, but it should do!

Ath9k wireless card "Cannot assign requested address"

# ip link set wlan0 up
RTNETLINK answers: Cannot assign requested address
#ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> ntu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope list lo
2: wlan0 <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 01:08:ca:e6:bc:76 brd ff:ff:ff:ff:ff:ff
#iwconfig
lo no wireless extensions
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated TX-Power-0dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Please do excuse if there's a silly typo somewhere in those; not knowing how to do it any better, I've simply re-typed the terminal output into this computer, so I can't promise it free of mistakes. (There's got to be a better way to do that, right?
Asus UX31E-DH72 Zenbook
clean install of the 2011.08.19-core-x86_64 release
There is no ethernet port; only WiFi and a ASIX AX88772B USB-to-ethernet that shipped with the system. (no optical drive either; but that's not really relevant to this)
My current system has never been on the internet (well, since I wiped the Windows off of it...), and so I haven't been able to pacman properly. When I try to use makepkg, it claims it's missing a dependency on Linux-Headers. However, I do know that the wireless card works, seeing as how it had been working just fine under Windows.
If it's relevant: during install, I left the NETWORKING section of rc.conf blank (as the Beginner's Guide says to do for DHCP), like so:
HOSTNAME="zen"
interface=wlan0
address=
netmask=
broadcast=
gateway=
#NETWORKS=(main)
Disclaimer: I'm rather new to the forums here and entirely new to Arch (which is my first Linux distro after years of OSX and a few weeks of Windows). Not scared of the command-line, but you may have to spell things out. Also, I understand if you'd rather not spend time explaining yourself, but I'm a strong believer in teach-a-man-to-fish, so if you'd like to explain rather than just walk through, it'd be much appreciated. Thanks!

Welcome and congrats on your decision to grace your sleek new laptop with an equally sleek OS :-)
Just in case you have not found that yet: there is actually a wiki page on your notebook for later setup specifics: https://wiki.archlinux.org/index.php/Asus_Zenbook_UX31E
BTW: I just read there that the usb ethernet is supported in later/newer kernels out-the-box (if setting up wifi really does fail, you can get a later ISO maybe and use that for starters).
As I understand your current setup state, you have installed the system with the core August release and it boots fine? Please confirm.
Also please confirm the exact wifi card the notebook has:
lspci -nn | grep net
or
lspci -nn >> ryebookpcidevices.txt
The later pipes the output to a file. Doing the command again, appends to the file. We only need the exact PCI ID of the wifi card to double check. To save typing even that ID you can maybe copy the file you created "ryebookpcidevices.txt" to an usb stick, if that automounts under /media/...
Next, please quote here any errors you get when re-loading the ath9k module (all commands below need root/sudo):
rmmod ath9k
modprobe ath9k
If you get errors, check whether
rfkill list
gives valid output (not sure if that package is on the ISO, i doubt it actually).
If modprobe does without error, please retry your trial to connect with the card by directly issuing
iwlist wlan0 scan
Give us feedback on what happens then. If there is an error, try
ip link set down
and start from step 0 in the wireless wiki: https://wiki.archlinux.org/index.php/Wi … nual_setup
Your output says "Mode:managed", so something seems working there already..
For "makepkg" you indeed need the headers, but you dont say what you want to compile at this stage.

Problems setting up Airport Extreme w/o wireless card

I just got an airport base station to host a dialup connection for an OSX 10.4.2 G4 Quicksilver 867 and a PC running win2k. No wireless cards on any of the machines.
I cant get it setup. using the Setup assistant, it see's the station and gives it a number. Then I get a messege saying "There was an error connecting to the air port base station you selected." regardless if I choose new setup or edit setup. If I click OK, at the bottom of the main screen it says "Reading Configuration". I let it run like that for an hour. I tried the admin tool as well, "cant read configuration" error there.
I think I likely need a wireless card to even access it.
But when I access the airport setup assistant, it says something about I'd "only be able to configure the LAN only. but it ddint help. rebooted computer and airport. i have it connected via ethernet.

Thanks Duane! I was in static IP mode and had to switch to dhcp and then yeah, i used the admin utility. thanks for everything. dialup to earthlink worked and I set my router and all systems to DHCP.
is there a difference between the 10.x.x.x IP range and the normal 192.168.1.x Ip pool? I always used the later in the past but noticed a choice in the airport admin tool.

Can't get to some websites using Wireless card ?

Can soneone using a MacBook Pro 15" see if they can get to these 2 websites while using the wireless card in WINXP.
www.ntius.com
www.olofsson.info
I can get to both sites in OSX using the wireless card but not in XP. I can also get to both sites using the network card. I think its probably a driver issue but would like somone to try it also. Thanks.

Hey, pizzapie22!
In my experience with NoScript, sometimes even if you allow the main site to load JS, some blocked scripts from different domains prevent content from loading.
Does your NoScript icon have a smaller "No" symbol in its lower-right corner? If it does you may have to allow additional scripts.
Does this help?

Recommended wireless card for G3?

I have a Powerbook GS series running OS 10.2 and am looking to buy a wireless card. Any suggestions? I went to the local Mac store and the guy there suggested a card that was about $80. Is this reasonable? Thanks for your help.

Tyanlee,
To make your wireless experience as pleasant as possible, I would suggest this:
1. Download and install the Mac OS X Update Combo 10.2.8:
http://www.apple.com/support/downloads/macosxupdatecombo10_28.html
2. Download and install AirPort 3.1.1:
http://docs.info.apple.com/article.html?artnum=70176
After installing both updates, you can then buy one of the wireless PC cards below and it will be fully compatible with AirPort software.
http://www.sonnettech.com/product/aria_extreme.html
http://www.macsense.com/product/broadband/WPE800.html
http://www.buffalotech.com/wireless/products/airstation/WLICBG54A.html
I recommend downloading the standalone updates instead of using your OSX's Software Update. If you have only a slow modem connection, possibly a friend can download them or your local Mac store may burn a CD for you for a few dollars.
If you are running OSX 10.2.0 > 10.2.5, you cannot use AirPort software, but you do have other options. If you are not interested in updating to 10.2.8 (possibly you are already there), please reply.

Wireless Card Problem

Following the info found in this forum, I've been trying to use a Netgear WG511T wireless card on my Powerbook G3 OS 10.2. I downloaded and installed the Orangeware driver, but after inserting the card (the light on the card blinks) the computer freezes during reboot and I get a grey screen with lines across the screen. This driver is supposed to work with this card, but I haven't been able to get past the reboot stage. Everything works fine without the card inserted. Am I missing something? Are the Mac gods playing with my mind? I really want this to work.

Hello,
cmlle, I have exactly the same problem.
For months I have been using Orangeware wireless driver on my Pismo G3/400 OSX 10.4 in combination with Netgear WG511T card with no problems at all.
Suddenly one day a black square appeared on the grey background when booting my Pismo. I red that is something to do with Kernel Panic but I don’t know much about that.
So it took several rebooting until Pismo appeared to be OK. But then a few times the screen just went black. That eventually stopped but instead Pismo would just freeze.
I then discovered that if I take my Netgear card out my Pismo, it unfreezes and start to work normally. If I then try to insert the card again while the computer is on the card wouldn’t connect with my router but only one LED would flash.
I eventually reinstalled OS but to no avail. I am so puzzled.
I would be ever so grateful if somebody could make a logical sense of all these symptoms.
Many thanks again
Alex

Airport wireless card not installed

Hi everybody, just wondering if anyone has suffered the same problem as i have...any help would be appreciated.
Basically, late 2007 120GB white macbook, bought new. i also run windows xp on it in bootcamp.
a few months ago the laptop started freezing up completely in both OSX and XP and would need a hard restart, on restart there would be no recognition of airport or wireless internet. when looking at airport in OS X it would say that there is no wireless card installed.
however, after a few restarts and resetting the PRAM, the wireless would cough back into life for a bit before freezing completely again and the same process encountered.
for about a month now though there seems to be no way of getting recognition of a wireless card at all, but the laptop is not freezing anymore.
any one had this problem and managed to resolve it?
ive had a bit of a poke around using google but havent really found out much about it....
just to complicate matters, my OS X disks that came with the macbook cant be recognised by it! (with no scratches or marks on them) but my OSX snow leopard disks that came with my 2010 imac do. ive done the system analysis thing with them and nothing showing.
cheers for any help.

Take it in for repair. You may not be able to use the installer discs that came with your iMac to reinstall OS X on the MB because the OEM discs are usually machine dependent. Also, you cannot install on more than one CPU at a time. It would violate your software license to install from the same installer DVD on two machines.

One card for OSX and one for windows...

OK, I've been following the ongoing debate regarding the choice of graphics cards for the Mac Pro. I think saying that it's limited would be putting it mildly.
Now, I really wish for a few more horsepower for when I'm playing Warcraft in Bootcamp but I really don't want to fork out £270 for the 1900XT just for apple to come along and update the range in x months and as I only really need the extra oomph in windows I wouldnt really see any benefit in OSX from the new card. Some people have touched on the idea of perhaps using a seperate card for when using windows. This would be great as I can get a better card for use in windows for a fraction of the price of a new apple card. What are the pro's and con's of doing this? Would the non-apple card confuse OSX and vica-versa would windows see both cards? Would I need to specify in windows which card I want to use? Would I have to remove a card each time I booted in the 'other' OS?
Educate me a little please :O)
Mac Pro 2.66GHz / iMac DV Graphite Edition / Colour Classic Mac OS X (10.4.9)

I left WoW with over 200 days played and moved from a G4 to a Mac Pro with a 1900 during that time. I also ended up having my x1900 card replaced by Apple. According to many sources there is now a Rev2 card being shipped. I can't confirm it but I can confirm that fewer people seem to be having problems, and if you use SMC FanControl while playing WoW it will keep things cool and you'll be assured of no over heating issues. Personally I would not be concerned if I used SMC Fan Control, and in fact after getting the new card and beginning to use SMC Fan Control I had no further issues of any kind. The issue was with overheating. WoW runs just fine in OSX using the x1900 card. FPS over 100 is not uncommon and even in the Suppression room in BWL (still the most intense graphic area I can recall...nothing like it in Kara or anywhere else I've seen in the new content) I'd get 40-80fps. It's no SLI super high end, but very, very playable with a Mac Pro.
My buddy came over the other day to use my WiFi for a battle with our guild in Karazhan. I felt like a crack wh_ore next to a pipe out of reach....

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)

PCI-e wireless card causes lock ups Z87 MPower MAX

I've already asked this question once, but was part of an epic essay that I've decided to break down into smaller more manageable chunks (as unsurprisingly that one got no replies).
I've got an ASUS PCE-A66 wireless ac pci-e card. Had absolutely no issues with it in my old Z77 board, but I seem to be having a lot of issues with it in my new Z87 MPower MAX. System was locking up like mad when I was trying to install the drivers at first. Had to rip out the WiFi/Bluetooth/WiDi module to get the drivers installed but the system randomly hangs on boot up? Don't get the issues with the card unplugged and don't always get it with it plugged in, but there seems to be some form of conflict with it that I can't resolve. Has anyone else had any such issues with any PCI-e add in cards on this motherboard?
Specs are:
i7 4770k
MSI MPower MAX using .128 bios (will try the .131 later)
2x4GB Corsair Dominator Platinum 2400
Coolermaster Silent Pro Hybrid 1050w
EVGA NVidia GTX 780 SC ACX
Windows 8 Pro 64bit

Yes, old system was Win8 Pro 64 bit too and the drivers are Windows 8 certified. As I say though, I had no issues with it on the old build? Even got a replacement sent out by Amazon in case the card itself was damaged Did initially try to do a warm update of the hardware into the same OS installation but didn't play well so did a full re-install in the end. Tried standard and UEFI installs (just in case) and after a problem with my OCZ Vector 2 not being recognised I bought a new Samsung 840 Pro so was a virgin SSD installed on to as well.
I'll raise it directly with MSI but just wanted to know if anyone else had experienced anything similar with any wireless cards in this mobo.
Cheers for the reply though

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.

PC Wireless card in OSX

Similar Messages

Maybe you are looking for