Lost wireless after a system upgrade. Network manager prob. (SOLVED)

whatshisname · 2010-10-31 21:30:25

Using network manager on an old Latitude D600 laptop that has been connecting just fine to my router until a recent system upgrade. This thing used to have the problem of the "wandering wireless ports" but I fixed that.

I can scan and connect to my router, a Netgear WGR614v7, when I use "/usr/sbin/iwconfig eth1 essid MYROUTERESSID"

In the list of connected devices on the router, it's showing my laptop and correct MAC Address.

When I issue: "/usr/sbin/dhclient eth1", it doesn't give me an IP address.

This is an unsecured network. (I live *way* out in the country.)

From the threads in the forum, it would appear I have an authentication problem except that the router is unsecured.

I've tried forcing this laptop to an internal IP in the network by associating an ip address, 192.168.1.11 and the laptop's MAC address. But that doesn't help.

I can connect to the router using an Ethernet cable fine.

I have Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter. I'm using the "ipw2100" driver.

I have restarted the router.

Any ideas?

Last edited by whatshisname (2010-11-25 15:55:00)

Allan · 2010-11-01 01:37:51

It always helps if we know what you upgraded before this broke....

whatshisname · 2010-11-01 02:56:27

It was a "pacman -Syu" back in the third week of September which I'm pretty sure included a kernel upgrade.

I don't use this laptop a lot so that's one reason for the delay in my posting. I was hoping the next big system/kernel upgrade would take care of it. But it didn't.

Thanks for the reply.

whatshisname · 2010-11-02 01:36:50

More information on my plight:

I went back into my router and again associated my preferred ip, 192.168.1.11, with the MAC address of my card.

I went through the Wireless Setup Wiki and tried to assign an IP from the command line per the instructions there:

# ifconfig eth1 192.168.1.11
# route add default gw 192.168.1.1

Again. My card is detected and *is* listed in the list of "Attached Devices" in my Netgear router.

But I still can't get an IP address.

I noticed that dhclient was reporting "DHCPDISCOVER on eth1 255.255.255.255 port 67 interval nn"

So I figured maybe port 67 wasn't open. I opened it using IPTABLES but no joy. Keep getting "No DHCPOFFERS received."

I installed "netcfg". After plugging in absolute path names for iwconfig, iwlist, iwscan, and ip in all the relevant scripts, I finally got it to run but it returns, surprise!, "No connection".

I've also tried getting an ip address using dhcpcd. It sits there waiting for a carrier then times out.

Again. I can connect to the router using a wired connection just fine.

So still scratching my head on this one. This is weird.

lagagnon · 2010-11-02 01:46:31

Please show us the output of the following commands run in a terminal so we can help diagnose your problem:

lsmod | grep -i ipw
cat /etc/rc.conf
ps aux | grep -i dhc
sudo ifconfig
sudo route -n

whatshisname · 2010-11-05 02:08:27

OK. Elections are over and I'm back to my laptop problem.

Figuring I was dealing with an authentication problem, I did try enabling wpa/wpa2, configuring wpa_supplicant to see if I just *had* to have an encrypted network to get this thing to work. Not sure I did everything correctly because i still have no connectivity.

Here are the commands:

[root@latlap krb]# lsmod | grep -i ipw

ipw2100                63509  0 
libipw                 22862  1 ipw2100
lib80211                3158  1 libipw
cfg80211              124335  2 ipw2100,libipw

[root@latlap krb]# cat /etc/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="America/New_York"
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

#####################  Getting wireless to work  ############3
# 1) Always load wireless before wired because this is a network.
# Ex., MODULES=(8139too e100).  
# Note: Suggested as way of keeping wired and wireless switching
# devices.  Couldn't figure out module for my Broadcom ethernet card
# So added:
# SUBSYSTEM=="net", ATTR{address}=="00:0F:1F:A1:4F:9D", NAME="eth0"
# SUBSYSTEM=="net", ATTR{address}=="00:0C:F1:37:1B:3A", NAME="eth1"
# to
# /etc/udev/rules.d/10-network.rules
#
# 2) In /etc/rc.local
# /sbin/ifconfig eth1 up
# /usr/sbin/iwconfig eth1 essid MtBoat
# /usr/sbin/dhclient eth1
#

MODULES=(ipw2100)

# 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="latlap"

# 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
#

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"

eth0="dhcp"
eth1="dhcp"
#wlan_eth0="eth0 essid MtBoat" # Unencrypted
# Not sure I need this
wlan_eth1="eth1 essid MtBoat" # Unencrypted
#INTERFACES=(!eth0 !eth1)
INTERFACES=(eth0 eth1)

# 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.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=(main)

# -----------------------------------------------------------------------
# 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 dbus @crond @alsa hal networkmanager !wicd)
DAEMONS=(@syslog-ng dbus !network @crond @alsa hal networkmanager)
#DAEMONS=(@syslog-ng @network netfs crond)

# For yaourt
# Server = [url]http://repo.archlinux.fr/i686[/url]

[root@latlap krb]# ps aux | grep -i dhc

root      2326  0.0  0.3   4732  1884 ?        Ss   21:29   0:00 /usr/sbin/dhclient -v -s 192.168.1.1 eth1
root      2328  0.0  0.5   4728  2820 ?        S    21:30   0:00 /usr/sbin/dhclient -d -4 -sf /usr/lib/networkmanager/nm-dhcp-client.action -pf /var/run/dhclient-eth0.pid -lf /var/lib/dhclient/dhclient-b46c231b-ffd4-42f0-b991-606d7307cc94-eth0.lease -cf /var/run/nm-dhclient-eth0.conf eth0
root      2402  0.0  0.0   2056   508 pts/3    S+   21:31   0:00 grep -i dhc

[root@latlap krb]# /sbin/ifconfig

eth0      Link encap:Ethernet  HWaddr 00:0F:1F:A1:4F:9D  
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1035 errors:0 dropped:0 overruns:0 frame:0
          TX packets:909 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:812235 (793.1 Kb)  TX bytes:131186 (128.1 Kb)
          Interrupt:11 

eth1      Link encap:Ethernet  HWaddr 00:0C:F1:37:1B:3A  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:65 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)
          Interrupt:5 Base address:0x6000 Memory:fafef000-fafeffff 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  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:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@latlap krb]# sudo /sbin/route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     1      0        0 eth0
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

Thanks.
(edit 04-02-11: added "code" tags)

Last edited by whatshisname (2011-04-02 15:20:46)

whatshisname · 2010-11-20 17:27:55

Still trying to solve this problem.

After more reading on the forums, it appears several folks with Intel NIC cards have the same problem I'm having after the kernel upgrade back in October to 2.6.35-ARCH.

One person reported fixing his problem by upgrading to the kernel in "testing".

So I just tried that but I'm still having the same problem.

Is anyone out there with an Intel Wireless NIC connecting with the 2.6.35-ARCH kernel?

whatshisname · 2010-11-20 18:11:31

And again ...

I tried using a Dell Truemobile PCMCIA wireless card. Uses the orinoco driver.

Same behavior as my internal Intel NIC card.

The router lists the card as an attached device.

Can't get an IP address.

What in the holy hell is going on?

I'm now using the 2.6.36-ARCH kernel.

whatshisname · 2010-11-24 19:44:07

My "long national nightmare" has come to an end!!!

I reinstalled Arch and my wireless is working again!

Hooray!

Who knows why it went south on me to begin with but at least I have a working system again.

Thanks for all the replies and help. This one was a bear.

whatshisname · 2010-11-25 15:53:31

whatshisname wrote:

My "long national nightmare" has come to an end!!!
I reinstalled Arch and my wireless is working again!
Hooray!
Who knows why it went south on me to begin with but at least I have a working system again.
Thanks for all the replies and help. This one was a bear.

Back again with, hopefully, some insight into what went wrong.

I spent last night rebuilding my system. As I mentioned in my first post, this laptop suffers from the the wireless device switching between eth0 and eth1. While troubleshooting this the first time, one of the things I did was switch from wicd to network manager. Not sure why I did but I did.

So last night as I tackled the wandering wireless device problem again, I did all the things in the wiki, eventually stabilized the wireless device to eth1 and then tackled the problem of why I wasn't being automatically connected to my wireless network when I booted up. That's when I noticed I hadn't installed network manager. Blindly following the configuration from my last install, I installed network manager and *bam*, I couldn't get an IP address!

I uninstalled network manager and I reacquired an IP address.

So ... it appears there must have been an upgrade to network manager back in September and it was something in that program that caused this whole mess.

Sorry to bug everyone again but maybe this will help someone out there.

Last edited by whatshisname (2010-11-25 15:56:33)

Arch Linux

#1 2010-10-31 21:30:25

Lost wireless after a system upgrade. Network manager prob. (SOLVED)

#2 2010-11-01 01:37:51

Re: Lost wireless after a system upgrade. Network manager prob. (SOLVED)

#3 2010-11-01 02:56:27

Re: Lost wireless after a system upgrade. Network manager prob. (SOLVED)

#4 2010-11-02 01:36:50

Re: Lost wireless after a system upgrade. Network manager prob. (SOLVED)

#5 2010-11-02 01:46:31

Re: Lost wireless after a system upgrade. Network manager prob. (SOLVED)

#6 2010-11-05 02:08:27

Re: Lost wireless after a system upgrade. Network manager prob. (SOLVED)

#7 2010-11-20 17:27:55

Re: Lost wireless after a system upgrade. Network manager prob. (SOLVED)

#8 2010-11-20 18:11:31

Re: Lost wireless after a system upgrade. Network manager prob. (SOLVED)

#9 2010-11-24 19:44:07

Re: Lost wireless after a system upgrade. Network manager prob. (SOLVED)

#10 2010-11-25 15:53:31

Re: Lost wireless after a system upgrade. Network manager prob. (SOLVED)

Board footer