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"

Similar Messages

Best practice for home setup/Roaming with built-in Dell wireless card?

I have a client with a huge house; I have done a site survey and it will require 3 APs to blanket the entire thing. I am wonderig what the best way to set this up for him would be? He would like to be able to walk around with the house and not lose connectivity. He is attempting to use his built-in Dell wireless card/client. As far as I know, these do not support Cisco roaming. What I have done is setup 3 diffrent SSIDs for each part of the house. Depending on his location he manually connects to the correct AP. Is this the best setup?
I had attempted to set all APs with the same SSIDs but found that the client would not roam and also found it difficult to connect to any of the APs at all. I believe the card was getting confused since there was overlap of the same SSID.

If he has a huge house, I don't think his laptop would be that old and also, the Dell's use the Intel wifi cards. Having all 3 ap's setup for the same SSID is what you should do and don't know why you are having so many issues. I would assume the ap's are on channel 1, 6, and 11 and how is the power setting? Do all these ap's run back to the same switch?

Broadcom Wireless Card Setup Problems

Hello there, I'm very new to Archlinux and to linux overall. Since I'm done with my classes for the summer, I had the crazy idea to setup a home web server with my old machine and at the same time use the wireless card as an acess point for my laptop. The problem is that I followed all the steps in the Archlinux wiki about the wireless setups for the B43 driver several times. However, my system seams to ignore all my efforts and keeps making fun of me. According to what I understood, it's not setting up the network interface. (Which is suposed to be done automaticly I think) So here's a bunch of troubleshooting commands results.
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
lspci | grep -e Network
01:06.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
lshw -C network
*-network
description: Network controller
product: BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 6
bus info: pci@0000:01:06.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=b43-pci-bridge latency=32
resources: irq:16 memory:40000000-40001fff
lsmod| grep -e b43 -e bcm43xx -e ssb -e ndiswrapper
b43 172775 0
ssb 44979 1 b43
mmc_core 52043 2 b43,ssb
pcmcia 29658 2 b43,ssb
mac80211 171331 1 b43
cfg80211 126817 2 b43,mac80211
led_class 2609 1 b43
Here are the links I followed to try to setup and try to troubleshoot my things
For b43 driver:
http://wiki.archlinux.org/index.php/Wireless_Setup
http://ubuntuforums.org/showthread.php?t=780692
http://linuxwireless.org/en/users/Drivers/b43
For ndiswrapper driver
http://ubuntuforums.org/showthread.php?t=780590
(There was an other one that told how to set it up but i can't find it)

Ok, I"ve done it and I got a few errors.
b43-pci-bridge 0000:01:06.0: PCI INT A disabled
cfg80211: Calling CRDA to update world regulatory domain
b43-pci-bridge 0000:01:06.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16
ssb: PCI-ID not in fallback list
ssb: CHIPID not in nrcores fallback list
ssb: Core 0 found: UNKNOWN (cc 0x8FF, rev 0x7F, vendor 0xFFFF)
ssb: WARNING: Invalid SPROM CRC (corrupt SPROM)
ssb: Unsupported SPROM revision 255 detected. Will extract v1
ssb: Sonics Silicon Backplane found on PCI device 0000:01:06.0
Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ]
So, does that mean that I don't use the proper firmware?

HWIC wireless card setup and errors

Hello all, I have a wireless card setup on my 1841 router and I am trying to get it to work with computer connected to it. I can connect fine and it routed to the internet and all of that, but the problem is that it keeps pushing out this error,
"*Jan 16 04:53:39.402: *** Not encrypted dot1x packet from 0016.6f65.b176 has been discarded"
Then after a few of those, the station gets removed from the wireless connection. Not sure where to go from here, I have WPA-psk setup on the router, the config for the interface looks like this...
interface Dot11Radio0/1/0
ip address 10.0.5.250 255.255.255.0
ip helper-address 10.0.0.1
ip nat inside
ip virtual-reassembly
encryption key 3 size 128bit ******** transmit-key
encryption mode ciphers tkip wep128
ssid ******
max-associations 20
authentication open
authentication network-eap *******
authentication key-management wpa optional
guest-mode
wpa-psk ascii 0 ****
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0
54.0
power local cck 13
station-role root
Not sure what I am doing wrong here, can anyone help me please! Thanks,
Kent

Boy I hate to sound too desperate but please can someone help me here? I have no clue what to do next, any idea's suggestions anything! Or some input telling me I am not the only guy having this issue? something please?

Linksys WMP11 Wireless Card Setup (Prism 2.5 chipset wlan-ng drivers)

I just finished setting up my first Arch Linux box on an ancient desktop of mine. It is running so suprisingly fast and I am loving it so far. I learned a ton working trough the guides too. Anyway, I am having issues setting up my wireless card. Currently, I am sharing my laptops wifi with my Arch desktop but I would like to use my acutal PCI card.
The card is a Linksys WMP11. I used to lspci to find that it is using the Prism 2.5 chipset. I consulted the Wireless Setup guide
https://wiki.archlinux.org/index.php/Wi … bsolete.29
This informed me that my card is supported by the wlan-ng drivers. My card is supported on the hardware list:
http://www.linux-wlan.org/docs/wlan_adapters.html.gz
I have searched around the official Arch repositories and the AUR and I can not find this package. The Wireless Wiki page states to use tools within the wlan-ng26-utils package. I can't seem to find this package. It does say wlan-ng is obselete. Is it no longer maintained?
I also downloaded the drivers directly from
http://www.linux-wlan.org/
However, I ran into issues when trying to run make configure. The value it generates for the Linux source path is invalid.
So, I am out of luck since the packages don't appear to exist, or is it possible to compile and install the drivers from source? How do I tie this into pacman?
Thanks

Hope this helps. I have the same chipset and have been searching on and off for the past three days for the answer - here's the simple thing that got mine working.
in /etc/rc.conf modify the modules line to include wpa_supplicant
MODULES=(wpa_supplicant)
in /etc/modprobe.d/blacklist.conf add the following line (create this file if it doesn't exist)
blacklist iwconfig
Now you should be able to activate and configure your card via wpa_supplicant. Here is a sample of my wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
# WEP in Shared Key mode
network={
ssid="MyRouterEssid"
scan_ssid=1
key_mgmt=NONE
wep_key0="MyCustomKey1"
wep_key1="MyCustomKey2"
wep_key2="MyCustomKey3"
wep_key3="MyCustomKey4"
wep_tx_keyidx=2
priority=5
auth_alg=SHARED
And here is the wpa_supplicant command line to start it manually
wpa_supplicant -B -c /etc/wpa_supplicant.conf -i wlan0
BTW, I also have these two lines in the /etc/modprobe.d/blacklist.conf file
blacklist orinono
blacklist orinono_pci
I have not had time yet to verify if this is not needed (was part of previous attempts to get wifi to connect) but wanted to let you know in case it is part of the stuff needed to get these cards working with the newer wpa_supplicant. Of course this configuration is for a WEP Shared Key configuration. I have also not had time yet to test whether or not this will work in WPA mode. I suspect not in my case because the firmware I have on my card is pre-wpa on the Prism 2.5 series. We'll see.
-Brian

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.

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.

Verizon Wireless installer for a wireless card not working. Help?

I have this wireless card from Verizon Wireless that lets me use internet anywhere i want. Its called the USB727 manufactured by Novatel Wireless. Bundled with this toy came a disc with the installer. When i tried to pop it into my iBook running OS X 10.4.11 it wouldn't begin the auto run. When I clicked the disc on my desktop i was given a .dmg file instead of the normal Verizon logo. When i opened it i was given two options the user manual and the actual installer. The installer logo was a piece of paper instead of the normal open-cardboard box. When i clicked it I'm given a window with the title folder actions setup, the setup doesn't show up.

Hi Eddie, and a warm welcome to the forums!
Not sure why it looks like that, I'd try this...
Not certain, but this can fix myriad problems...
Safe Boot from the HD, (holding Shift key down at bootup), it will try to repair your Disk Directory while the spinning radian is happening, so let it go, run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, then reboot & try to install.
Found this...
The main thing is, you need to install the VZaccessmonitor to get the right drivers, but after that you can connect through Internet Connect, as if it twere a regular modem. If you open internet connect, or the system prefs while configuring and setting up initially with the VZaccessmonitor, it will cause the repeating dialogues. I had to uninstall, make sure not to open system prefs while the VZ install ran, and then reboot--and the install had produced a new location for me.
http://discussions.apple.com/thread.jspa?messageID=8939370

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)

Setup wireless network for mac and pc with Airport Express?

Mac Mini/OSX/10.8.2/Airport Express
Question,
I have my AIrPort Express setup for my Mac Mini and I have dell computer that I want to share the wireless network. Is it possible to setup a wireless network with my mini and the pc using only the AirPort Express? Is the Airport Express a wireless router?
Thanks,

If your Mac Mini is connecting to the Express using wireless, then this confirms that the device is working correctly.
The Express is a wireless router that can support up to 10 wireless connections, so your Dell computer should be able to connect assuming that its wireless card is working correctly, and the Dell indentifies the network and enters the correct wireless network password.
If you are having difficulty with the Dell PC connecting, this Windows troubleshooting document might help:
http://windows.microsoft.com/en-US/windows/network-connection-problem-help#netwo rk-problems=windows-8&v1h=win8tab1&v2h=win7tab1&v3h=winvistatab1&v4h=winxptab1

Can't connect to wireless network on bootup like before

Hello all. Well, I seem to have run into some difficulties here while configuring my system. The thing is I cannot connect to my wireless network on bootup anymore. I stayed about 4 months without using Arch Linux, then I decided to reinstall it from the ground up on the SAME machine, which has suffered NO changes; it is the exact same computer. The only change since then is that I changed my WEP encryption key on my router. I had a functional rc.conf file which I keep just for taking a look at while I'm configuring the system. The Networking section follows:
# /etc/rc.conf (NETWORKING Section)
HOSTNAME="ArchPC"
wlan0="dhcp"
wlan_wlan0="wlan0 essid MySpot key 0123456789ABCDEFABCDEF1234"
interfaces=(wlan0)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
The only thing I changed from my previous rc.conf was my WEP hex key, which I have already triple-checked. I used the same hostname (which is also correctly configured in /etc/hosts) and the essid is the same. In 2 years of Arch I used this configuration file and it worked flawlessly, but now it simply does not work anymore for boot-up connection. I simply get a FAIL after about 30 sec in '::Starting Network' on bootup. Then, by issuing 'iwconfig', I can see that my interface (wlan0) is up and the ESSID is set to "MySpot", but the access point is not associated. I do not know what is going on, as it never happened before. However, it works just fine if I do the step-by-step manual configuration from command line after my system is up and I can get internet access in such a way without any problems. Never did it before (so I do not know if this was the case for my previous installations), but by running 'lspci | grep -i net' I do not see my wireless extension listed, although 'iwconfig' shows it just fine. I am trying to make it work using rc.conf just as it did before. As I mentioned, my network connection is working, but not from bootup as it did before, so I do not know what to do. Did anything on Arch radically change since then? Couldn't find anything on the wiki pages besides using another network start method. Any help is greatly appreciated...
Edit: I just found out that my wmaster0 is missing...could that have anything to do with my issue?
Last edited by gabscic (2010-04-04 06:45:23)

Just for the sake of not letting this go without any answer, I've just done a full system reinstall and now I've got back my wmaster0 (the driver module for my wireless network card is rtl8187). Searching the internet, it seems that wmaster0 is an internal master device that is to be used by the module, and not the user. The lack of wmaster0 may indicate that something is amiss on the driver installed on your system. Now that I've got it back, my rc.conf file (described on previous post) works like a charm. However, I remember I did have wmaster0 on my previous Arch installation and it just disappeared all of a sudden. So far the only thing I've done different is that I have not yet upgraded my new installation, so my guesses are that something on the upgrade procedure is breaking the driver in some way. Maybe all those package renames and such? I'll upgrade my system later (don't have the time now) and I'll get back here with any new findings. Regards...
Last edited by gabscic (2010-04-06 20:53:14)

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

Wireless Works during install.... Does not work after install.

Hiya!
I just finally finished semi-installing from live. it's exciting. I'm stuck at cli trying to get wireless to work.
it's really weird. First- I only have wireless (it's from my downstairs neighbors). I used it DURING the install process- downloaded all of the packages, etc etc.
But when I start up my computer, I get a [FAIL] by network (it does not start up). However, if i # ifconfig wlan0 up, the wireless turns on.
iwconfig does not work
and I cannot scan for networks...
During install, I was able to see the names of every network.
There isn't any sort of password for the router I would like to connect to (and connected to before); it's just a linksys.
My wireless card is intel 5300 and I'm almost certain I installed the 5000 driver package.
Thoughts?
Perhaps I should go to sleeeeeeep..
IT"S JUST SO ADDICTING

zee wrote:IT"S JUST SO ADDICTING
You've just been sucked into the world of Arch Linux! Watch as your skin becomes pale, your eyes turn square and you suddenly feel compelled to run "pacman -Syu" every 10 minutes
Must...... keep....... up...... to......date....

[SOLVED]Arch not acknowledging wireless card.

So Im a returning user, feel like a total newb again.
I recently purchased an "Asus k53sv-xr1"
The wireless card inside is "Intel Centrino Wireless-N 100," I determined this by installing the proper driver in windows and checking the device manage (as asus could not answer my question as to the model number and the spec indicate "integrated blahblahblah"
Following the "Wireless Setup Instructions" I did the following (filling the xs' with their respective version numbers)
"Installing Firmware (Microcode)
Important: Installing these firmware packages is not required since the 2.6.34 kernel update, when the firmware files were moved to the linux-firmware package.
If you need wireless connectivity to access pacman's repositories, the firmware files are also available direct from Intel. See this page, select and download the archive.
$ wget http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-XXXX-ucode-XXX.XX.X.XX.tgz"
After downloading, you must extract and copy the *.ucode file to the firmware directory, commonly /lib/firmware
# tar zxvf iwlwifi-XXXX-ucode-XXX.XX.X.XX.tgz
# cd iwlwifi-XXXX-ucode-XXX.XX.X.XX/
# cp iwlwifi-XXXX-X.ucode /lib/firmware/"
The wireless setup manual goes on to say that
"If MOD_AUTOLOAD is set to yes in /etc/rc.conf (it is by default) that should be all that is required. Simply check for the presence of the drivers by running ip addr from a terminal. There should be a listing for wlan0."
My outputs are the following
lspci | grep -i net
03:00:0 Network controller: Intel Corporation Decive 08ae
04:00:0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/816B PCI Express Gigabit Ethernet controller (rev06)
lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 001 Device 003: ID 058f:a014 Alcor Micro Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
iwconfig
lo no wireless extentions
eth0 no wireless extentions
Thank you in advance!
Last edited by Stromblad (2011-08-16 02:13:50)

If anything I have (re)learned some things about whats going on, which...ultimately led to more questions.
First these two snippets led me to some interesting ideas.
"Installing Firmware (Microcode)
Important: Installing these firmware packages is not required since the 2.6.34 kernel update, when the firmware files were moved to the linux-firmware package.
If you need wireless connectivity to access pacman's repositories, the firmware files are also available direct from Intel. See this page, select and download the archive."
From the "Wireless Setup" Wiki
and
"Using kernels 2.6.24 and up
These kernels have the iwlwifi driver included and the released drivers (available from this site under download page) do not work with these kernels. If you want to run the latest (or very close to it) development code with your kernel then you should use the compat-wireless project that retrieves the latest driver development code from the upstream repository. We do push our changes to this repository very frequently."
Which means that the firmware I downladed from http://intellinuxwireless.org/?p=iwlwifi, would not work.
I reinstalled, this time including the all the "iwl" packages from the "dev" section of the packages.
The result was the same.
dmesg | grep -i iw
would report nothing at all
until i input the command
modprobe iwlagn
then dmesg | grep -i iw would report
iwlagn: Intel(r) Wireless WiFi Link AGN driver for linux, 2.6.33-ARCH-ks
iwlagn: Copyright(c) 2003-2009 Intel Corporation
I really wanted to figure this out the arch way, but I can find little to no threads on my specific card.."Intel Centrino N-100 Wireless"
If anyone can help, it would be greatly appreciated. In the meantime, I will boot the ubuntu live cd and hope that wireless is automatically configured, that way I can at the very least, attempt to figure out what model card it reports and try again with that information.
My question, other than "can anyone provide some insight as to why the system can detect the card, but not be able to bring wlan0 up", is can modprobe insert modules that do not correspond with what is actually in the machine?
Thank you

Attempting to connect daughter's laptop with a Neatgear wireless card

I am trying to connect my daughter's laptop to my network. I have downloaded Network Magic, etc. Is there an easy step-by step tutorial or checklist I can access to connect her to my router? Network Magic is telling me that I have other network connection software and it has to be disabled before continuing (**bleep**?). I am being driven mad. Just need to have a step by step list to get it connected. If necessary, I can delete everything (Network Magic, etc,. and the like) and start fresh if that is necessary. Any experts available to help? Thanks in advance,
Forgot to mention that she is using a Netgear MA 401 wireless card. Router is the WRG54S Version 7.
Message Edited by poopoohead on 10-27-2009 08:44 AM

Which operating system you are using on the computer...?
Are you able to connect other wireless computer to your network..?
First of all make sure that your adapter is installed properly on the wireless computer..Go to the linksys setup page by typing 192.168.1.1 in the address bar from the wired computer and change the wireless channel to 11-2.462GHz.Change the SSID (network name) to some unique name(not linksys)...Confirm the Network/Security key.Now,locate and try to connect the wireless network on the wireless computer.

Setup wireless card during bootup

Similar Messages

Maybe you are looking for