[SOLVED]iwl4965 + dhcp + wpa2 = Lost!

LeoSolaris · 2008-08-21 03:13:28

To solve... as wierd as it is to say this, it is the same way that I have to use to connect in Ubuntu. appearently the little applet I always used is called wicd.

Just

pacman -S wicd

Then set it up the way it tells ya, and restart.

Poof.

Done.

Old "problem" notes so I can look back and laugh at myself:

On the bright side, I have a comforting little blue wifi light now!

I followed all of the steps in the wireless network set up wiki.

Here is the relivant parts of my rc.conf:

MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(b44 mii iwl4965 snd-mixer-oss snd-pcm-oss snd-hwdep
snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore
acpi-cpufreq)

HOSTNAME="LeoArch"  (yes, it's the same in the /etc/hosts. Got that warning loud and clear!)

eth0="dhcp"
INTERFACES=(eth0)

gateway="default gw 192.168.0.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='menu' <-(changed from (main) which was default as I am typing this.)

DAEMONS=(syslog-ng @network netfs crond dhcp @alsa @hal @fam
@gdm laptop-mode)

here is ifconfig wlan0:

wlan0     Link encap:Ethernet  HWaddr 00:1D:E0:50:46:ED  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Here is iwconfig:

wlan0     IEEE 802.11  ESSID:"Paranoid Guy's Network"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:1A:70:FD:0B:7B   
          Bit Rate=54 Mb/s   Tx-Power=14 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Encryption key:'mypassphrase'
          Link Quality=100/100  Signal level=-25 dBm  Noise level=-97 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

dmesg:

iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.26ks
iwl4965: Copyright(c) 2003-2008 Intel Corporation
ACPI: PCI Interrupt 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:0c:00.0 to 64
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
phy1: Selected rate control algorithm 'iwl-4965-rs'
input: 4965AGN as /class/input/input12
ACPI: PCI Interrupt 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17
firmware: requesting iwlwifi-4965-1.ucode
Registered led device: iwl-phy1:radio
Registered led device: iwl-phy1:assoc
Registered led device: iwl-phy1:RX
Registered led device: iwl-phy1:TX
ADDRCONF(NETDEV_UP): wlan0: link is not ready
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:1a:70:fd:0b:7b
wlan0: RX authentication from 00:1a:70:fd:0b:7b (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:1a:70:fd:0b:7b
wlan0: RX AssocResp from 00:1a:70:fd:0b:7b (capab=0x411 status=0 aid=1)
wlan0: associated
wlan0: CTS protection enabled (BSSID=00:1a:70:fd:0b:7b)
wlan0 (WE) : Wireless Event too big (342)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
b44: eth0: Link is down.
wlan0: CTS protection disabled (BSSID=00:1a:70:fd:0b:7b)
wlan0: switched to short barker preamble (BSSID=00:1a:70:fd:0b:7b)
wlan0: CTS protection enabled (BSSID=00:1a:70:fd:0b:7b)
wlan0: switched to long barker preamble (BSSID=00:1a:70:fd:0b:7b)

It sort of appears like I am doing it right, but I still do not get a working net connection.

My laptop does not freeze like other users have reported.

I have to reboot, however, in order to get my wired netword to reattach after pulling it out to plug in the wireless router.

I am thinking about stealing the kernel from Ubuntu to see if that works, but my contacts are itching, so I think I will not have the time for that tonight.

I hope someone out there can tell me what is happening, or what I am missing. This is probibly a newbie's mistake.

(Arch is sweet by the way, bloody fast, and when I can get this wireless part licked, I will be a happy camper.)

Edit: I jsut tired to install the tarball of iwlwifi from LinuxWireless.org and recieved a few errors. Unfortunately, I rebooted to get my ethernet connection back before copying the errors to post here.

Last edited by LeoSolaris (2008-08-21 05:14:46)

vogt · 2008-08-21 05:36:41

Your wireless appears up, so it's not the driver's fault. You don't have an ip address. You can probably get one with

dhcpcd wlan0

. In your /etc/network.d/theProfileYouChoseOnBoot, you've set IP="dhcp", or you are using the older, less flexible /etc/conf.d/wireless configuration instead of netcfg2?

Instead of rebooting to get your network to restart, look into ifplugd, which can automatically restart your network when you plug in a cable.

LeoSolaris · 2008-08-21 16:53:07

vogt wrote:

Your wireless appears up, so it's not the driver's fault. You don't have an ip address. You can probably get one with
dhcpcd wlan0
. In your /etc/network.d/theProfileYouChoseOnBoot, you've set IP="dhcp", or you are using the older, less flexible /etc/conf.d/wireless configuration instead of netcfg2?
Instead of rebooting to get your network to restart, look into ifplugd, which can automatically restart your network when you plug in a cable.

I will have to install ifplugd. Definitely sounds useful. I did finally get the blasted thing to work, with wicd. Apparently wicd is that little network applet in gnome's notification area. It was the only way I ever got Ubuntu to connect, so I am glad I found it.

Thank you! Now, if I could just get synaptics to stop allowing mouse selections when I type... found the how to, and it's not working yet. More experimentation needed.

vogt · 2008-08-21 18:43:46

Isn't it just enough to run syndaemon in the background to make the touchpad not respond when you type? Where is this howto, and why is it so complicated?

LeoSolaris · 2008-08-21 19:57:05

vogt wrote:

Isn't it just enough to run syndaemon in the background to make the touchpad not respond when you type? Where is this howto, and why is it so complicated?

Because it was 4am and my mind was nearly dead. (crammed a lot of new stuff in while installing and configuring Arch last night.) LOL

I am not sure how to set a daemon in the background with little command tags like -i etc. I know how to get it started at start up in rc.conf... maybe putting it in the start up for gnome... hmmm

I will use syndaemon as you and the how to suggest, it is just currently low on the priorities till I get awn-bzr working from the AUR. (this is a lot of fun, no joke!)

Arch Linux

#1 2008-08-21 03:13:28

[SOLVED]iwl4965 + dhcp + wpa2 = Lost!

#2 2008-08-21 05:36:41

Re: [SOLVED]iwl4965 + dhcp + wpa2 = Lost!

#3 2008-08-21 16:53:07

Re: [SOLVED]iwl4965 + dhcp + wpa2 = Lost!

#4 2008-08-21 18:43:46

Re: [SOLVED]iwl4965 + dhcp + wpa2 = Lost!

#5 2008-08-21 19:57:05

Re: [SOLVED]iwl4965 + dhcp + wpa2 = Lost!

Board footer