Not detecting pcmcia card

pighunter · 06-04-2009, 09:18 PM

Bruce,
Again, I appreciate the time you're taking for this, I know you must be busy.

Hate to be such a noob, but I do not know if the ath54k_pci module is loaded or even how to load it?

Yes, I know my network IP, Netmask, gateway, DNS; I have been configuring my windows network for some time.

I saved my wireless.conf as wireless.conf_old and made a new one that is blank. I did the same with the inet1.conf file but having only the following parameters:

IFRAME[0]="ath0"
IPADDR[0]="192.168.1.138"
NETMASK[0]="255.255.255.0"
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
GATEWAY="192.168.1.1"

These are the only parameters in my /etc/rc.d/inet1.conf file. I was trying to get a connection and then work on WPA security after I got the connection.

PH

Bruce Hill · 06-04-2009, 09:52 PM

Hey, you've got the right modules loaded:

Quote:

Originally Posted by pighunter

The output for lsmod | grep ath* is:

ath5k 96768 0
mac80211 150680 1 ath5k
led_class 3716 1 ath5k
cfg80211 23048 2 ath5k,mac80211

If you're wanting to use wicd, you can NOT have settings in /etc/rc.d/inet1.conf
or /etc/rc.d/rc.wireless.conf, so replace yours with the following information,
taken from a box on my LAN for use with wicd:

Code:

# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").

# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.

# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.

# =============================================================================

# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""

# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""

# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""

# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""

# Default gateway IP address:
GATEWAY=""

# Change this to "yes" for debugging output to stdout.  Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"

## Example config information for wlan0.  Uncomment the lines you need and fill
## in your info.  (You may not need all of these for your wireless network)
#IFNAME[4]="wlan0"
#IPADDR[4]=""
#NETMASK[4]=""
#USE_DHCP[4]="yes"
#DHCP_HOSTNAME[4]="icculus-wireless"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
#WLAN_ESSID[4]=BARRIER05
#WLAN_MODE[4]=Managed
##WLAN_RATE[4]="54M auto"
##WLAN_CHANNEL[4]="auto"
##WLAN_KEY[4]="D5AD1F04ACF048EC2D0B1C80C7"
##WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
#WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER[4]="ndiswrapper"

## Some examples of additional network parameters that you can use.
## Config information for wlan0:
#IFNAME[4]="wlan0"              # Use a different interface name nstead of
                                # the default 'eth4'
#HWADDR[4]="00:01:23:45:67:89"  # Overrule the card's hardware MAC address
#MTU[4]=""                      # The default MTU is 1500, but you might need
                                # 1360 when you use NAT'ed IPSec traffic.
#DHCP_KEEPRESOLV[4]="yes"       # If you dont want /etc/resolv.conf overwritten
#DHCP_KEEPNTP[4]="yes"          # If you don't want ntp.conf overwritten
#DHCP_KEEPGW[4]="yes"           # If you don't want the DHCP server to change
                                # your default gateway
#DHCP_IPADDR[4]=""              # Request a specific IP address from the DHCP
                                # server
#WLAN_ESSID[4]=DARKSTAR         # Here, you can override _any_ parameter
                                # defined in rc.wireless.conf, by prepending
                                # 'WLAN_' to the parameter's name. Useful for
                                # those with multiple wireless interfaces.
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=thekey"
                                # Some drivers require a private ioctl to be
                                # set through the iwpriv command. If more than
                                # one is required, you can place them in the
                                # IWPRIV parameter (separated with the pipe (|)
                                # character, see the example).

Code:

# Wireless LAN adapter configuration
#
# Theory of operation :
#
# The script attempts to match a block of settings to the specific wireless
# card inserted, the *first* block matching the card is used.
# The address format is "hwaddr", with * as a wildcard.
# 'hwaddr' is the unique MAC address identifier of the wireless card.
# The MAC address is usually printed on the card, or can be found via ifconfig.
# Some examples here use only half of the MAC address with a wildcard to
# match a whole family of cards...
#
# All the Wireless specific configuration is done through the Wireless
# Extensions, so we will just call 'iwconfig' with the right parameters
# defined below.
# Of course, you need to have iwconfig installled on your system.
# To download iwconfig, or for more info on Wireless Extensions :
#       http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html
#
# Note : you don't need to fill all parameters, leave them blank, in most
# cases the driver will initialise itself with sane defaults values or
# automatically figure out the value... And no drivers do support all
# possible settings...
#
# -- This is a modified '/etc/pcmcia/wireless.opts' script --
# -- I added sections for Prism/GT and Atheros based cards --
# --    (supported by the prism54 and madwifi drivers)     --
# --              16/sep/2004 * Eric Hameleers             --
#

VERBOSE=1

case "$HWADDR" in

## NOTE : Comment out the following five lines to activate the samples below ...
## --------- START SECTION TO REMOVE -----------
## Pick up any Access Point, should work on most 802.11 cards
*)
    INFO="Any ESSID"
    ESSID="any"
    ;;
## ---------- END SECTION TO REMOVE ------------


# Here are a few examples with a few Wireless LANs supported...
# The matching is done on the first 3 bytes of the MAC address

# SMC2835W EZ Connect g 2.4GHz 54 Mbps Wireless Cardbus Adapter
00:04:E2:*)
    INFO="SMC2835W EZ Connect g 2.4GHz 54 Mbps Wireless Cardbus Adapter"
    # ESSID (extended network name) : My Network, any
    ESSID="any"
    # NWID/Domain (cell identifier) : 89AB, 100, off
    NWID=""
    # Operation mode : Ad-Hoc, Managed, Master, Repeater, Secondary, auto
    MODE="Managed"
    # Frequency or channel : 1, 2, 3 (channel) ; 2.422G, 2.46G (frequency)
    FREQ=""
    CHANNEL="7"
    # Sensitivity (cell size + roaming speed) : 1, 2, 3 ; -70 (dBm)
    SENS=""
    # Bit rate : auto, 1M, 11M,54M
    RATE="auto"
    # Encryption key : 4567-89AB-CD, s:password
    # Example for 40-bit encryption:
    #KEY="883e-aa67-21 [1] key 5501-d0da-87 [2] key 91f5-3368-6b [3] key 2d73-31b7-96 [4]"
    # Example for 104-bit encryption (aka 128-bit WEP):
    #KEY="d5ad2f05abd048ecf10b1c80c7"
    KEY=""
    # RTS threshold : off, 500
    RTS=""
    # Fragmentation threshold : off, 1000
    FRAG=""
    # Other iwconfig parameters : power off, ap 01:23:45:67:89:AB
    IWCONFIG=""
    # iwspy parameters : + 01:23:45:67:89:AB
    IWSPY=""
    # iwpriv parameters : set_port 2, set_histo 50 60
    IWPRIV=""
;;

# Multiband Atheros based 802.11a/b/g universal NIC cards
00:05:4E:*)
    INFO="Multiband Atheros based 802.11a/b/g universal NIC"
    # ESSID (extended network name) : My Network, any
    ESSID=""
    # Operation mode : Ad-Hoc, Managed, Master, Repeater, Secondary, auto
    MODE="Managed"
    # Frequency or channel : 1, 2, 3 (channel) ; 2.422G, 2.46G (frequency)
    FREQ=""
    CHANNEL="7"
    # Bit rate : auto, 1M, 11M,54M
    RATE="auto"
    # Encryption key : 4567-89AB-CD, s:password
    # Example for 40-bit encryption:
    #KEY="883e-aa67-21 [1] key 5501-d0da-87 [2] key 91f5-3368-6b [3] key 2d73-31b7-96 [4]"
    # Example for 104-bit encryption (aka 128-bit WEP):
    #KEY="d5ad2f05abd048ecf10b1c80c7"
    KEY=""
    # Other iwconfig parameters : power off, ap 01:23:45:67:89:AB
    IWCONFIG=""
    # iwspy parameters : + 01:23:45:67:89:AB
    IWSPY=""
    # iwpriv parameters : set_port 2, set_histo 50 60
    IWPRIV=""
    ;;

# Lucent Wavelan IEEE (+ Orinoco, RoamAbout and ELSA)
# Note : wvlan_cs driver only, and version 1.0.4+ for encryption support
00:60:1D:*|00:02:2D:*)
    INFO="Wavelan IEEE example (Lucent default settings)"
    ESSID="Wavelan Network"
    MODE="Managed"
    #RATE="auto"
    KEY="s:secu1"
    # To set all four keys, use :
    #KEY="s:secu1 [1] key s:secu2 [2] key s:secu3 [3] key s:secu4 [4] key [1]"
    # For the RG 1000 Residential Gateway: The ESSID is the identifier on
    # the unit, and the default key is the last 5 digits of the same.
    #ESSID="084d70"
    #KEY="s:84d70"
    ;;

# Cisco/Aironet 4800/3x0
# Note : MPL driver only (airo/airo_cs), version 1.3 or later
00:40:96:*|00:02:8A:*)
    INFO="Cisco/Aironet example (Cisco default settings)"
    ESSID="any"
    # To set all four ESSID, use iwconfig v21 and the same trick as above
    MODE="Managed"
    #RATE="11M auto"
    #KEY="d5ad2f05abd048ecf10b1c80c7"
    KEY="off"
    ;;

# Samsung MagicLan (+ some other PrismII cards)
# Note : Samsung binary library driver, version 1.20 or later
00:00:F0:*|00:02:78:*)
    INFO="Samsung MagicLan example (Samsung default settings)"
    ESSID="any"
    MODE="Managed"
    CHANNEL="4"
    RATE="auto"
    #KEY="883e-aa67-21 [1] key 5501-d0da-87 [2] key 91f5-3368-6b [3] key 2d73-31b7-96 [4]"
    #IWCONFIG="power on"
    ;;

# Raytheon Raylink/WebGear Aviator2.4
# Note : doesn't work yet, please use for debugging only :-(
00:00:8F:*|00:00:F1:*)
    INFO="Raylink/Aviator2.4 example (Aviator default ad-hoc setting)"
    ESSID="ADHOC_ESSID"
    MODE="Ad-Hoc"
    RATE="auto"
    IWPRIV="set_framing 1"
    ;;

# Old Lucent Wavelan
08:00:0E:*)
    INFO="Wavelan example (Lucent default settings)"
    NWID="0100"
    MODE="Ad-Hoc"
    FREQ="2.425G"
    KEY="off"
    ;;

# Netwave (Xircom Netwave/Netwave Airsurfer)
00:80:C7:*)
    INFO="Netwave example (Netwave default settings)"
    NWID="100"
    KEY="00"
    ;;

# Proxim RangeLan2/Symphony (what is the MAC address ???)
XX:XX:XX:*)
    INFO="Proxim RangeLan2/Symphony example"
    NWID="0"
    MODE="Master"
    CHANNEL="15"
    IWPRIV="setsubchan 1"
    ;;

# No Wires Needed Swallow 550 and 1100 setting (what is the MAC address ???)
XX:XX:XX:*)
    INFO="NWN Swallow example"
    ESSID="session"
    KEY="0000-0000-00 open"
    ;;

# Symbol Spectrum24 setting (what is the MAC address ???)
XX:XX:XX:*)
    INFO="Symbol Spectrum24 example"
    ESSID="Essid string"
    ;;

# Generic example (decribe all possible settings)
*)
    INFO="Fill with your own settings..."
    # ESSID (extended network name) : My Network, any
    ESSID=""
    # NWID/Domain (cell identifier) : 89AB, 100, off
    NWID=""
    # Operation mode : Ad-Hoc, Managed, Master, Repeater, Secondary, auto
    MODE=""
    # Frequency or channel : 1, 2, 3 (channel) ; 2.422G, 2.46G (frequency)
    FREQ=""
    CHANNEL=""
    # Sensitivity (cell size + roaming speed) : 1, 2, 3 ; -70 (dBm)
    SENS=""
    # Bit rate : auto, 1M, 11M
    RATE=""
    # Encryption key : 4567-89AB-CD, s:password
    KEY=""
    # RTS threshold : off, 500
    RTS=""
    # Fragmentation threshold : off, 1000
    FRAG=""
    # Other iwconfig parameters : power off, ap 01:23:45:67:89:AB
    IWCONFIG=""
    # iwspy parameters : + 01:23:45:67:89:AB
    IWSPY=""
    # iwpriv parameters : set_port 2, set_histo 50 60
    IWPRIV=""
    ;;
esac

If you prefer NOT to use wicd, setup /etc/rc.d/rc.inet1.conf like this:

Code:

# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").

# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.

# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.

# =============================================================================

# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""

# Config information for ath0:
IPADDR[1]="192.168.1.138"
NETMASK[1]="255.255.255.0"
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""

# Default gateway IP address:
GATEWAY="192.168.1.1"

# Change this to "yes" for debugging output to stdout.  Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="yes"

You don't need any other settings atm to check without encryption.

Are you sure your wireless card is ath0, and not wlan0? Make sure
to put the proper one in that file. You can find out by issuing:

Code:

iwconfig

and see what APs it sees by issuing:

Code:

iwlist ath0 scan

or

Code:

iwlist wlan0 scan

whichever shows up from iwconfig.

Edit: You also need DSN server(s) in /etc/resolv.conf

pighunter · 06-04-2009, 10:24 PM

OK, my inet1.conf file is identical to yours, and I opted to use wicd. Also, my wireless card is wlan0 not ath0. The wireless.conf file is blank.

For the etc/resolve.conf file do I enter only the DNS IP addresses, do they need labels?

PH

Bruce Hill · 06-04-2009, 10:51 PM

I don't know if it matters, but /etc/rc.d/rc.wireless.conf should not
be blank, it should be as I posted.

Your /etc/resolv.conf file should look like this:

Code:

nameserver 222.172.200.68
nameserver 61.166.150.123

except that it should have YOUR DNS servers, not those ^^ which are
for China Telecom.

However, if you run wicd without giving any advanced settings, iirc
it will use the DHCP server from your router (if it's on) and set all
that for you.

pighunter · 06-04-2009, 11:04 PM

Bruce,

OK, my wireless.conf file is now default. Also, I entered my DNS ip addresses in the resolv.conf file.

PH

Bruce Hill · 06-05-2009, 12:30 AM

Well, are you surfing the net?

pighunter · 06-05-2009, 12:54 AM

I wish. I ran wicd, but nothing happens, get an hour-glass for about 20 sec. then stops. Since I had no success with wicd I again attempted to edit the inet1.conf file. I took the security off the router and tried to connect. Firefox opened but said it could not find the server, so....

By the way, yes, I have been reading the docs and I have Alien Bobs wiki in front of me, but it really does not say much about wicd. I'm close, I think, but this is like reaching into a bucket of worms looking for the one that will catch the fish.

PH

Bruce Hill · 06-05-2009, 03:28 AM

How did you "run wicd"? It sounds to me like the binary is not executable.

Don't forget you can check for running processes with "ps". Issue:

Code:

ps aux | grep wicd

and you should get something such as:

Code:

mingdao@jeremiah:~$ ps aux | grep wicd
root      3682  0.0  0.4  78632  8532 ?        S    08:03   0:02 python -O /usr/lib/wicd/wicd-daemon.py
root      3780  0.0  0.4  77232  8452 ?        S    08:03   0:09 python /usr/lib/wicd/monitor.py
mingdao   7288  0.0  1.8 207932 38204 tty1     S    11:49   0:00 python -O /usr/lib/wicd/wicd-client.py

What's the output of "ls -l /etc/rc.d/rc.wicd"? If it's not this:

Code:

mingdao@jeremiah:~$ ls -l /etc/rc.d/rc.wicd
-rwxr-xr-x 1 root root 913 2009-05-01 18:31 /etc/rc.d/rc.wicd

then, as root, issue:

Code:

chmod +x /etc/rc.d/rc.wicd

to make it executable. Then issue:

Code:

chmod +x /etc/rc.d/rc.wicd start

and that should start the service. And you might want to reboot the box,
just to check that wicd starts and the settings are okay we've changed.
Granted, I'm not a fan of rebooting, but in this case I'd recommend it.

pighunter · 06-05-2009, 12:55 PM

Bruce,

I run wicd from KDE. I startx which takes me to KDE and one of the menu choices is wicd.

The output from ps aux | grep wicd is:
root 2507 0.0 0.5 2084 636 tty1 S+ 10:32 0:00 grep wicd

The output from ls -l /etc/rc.d/rc.wicd
-rwxr-xr-x 1 root root 1204 2008-12-06 20:36 /etc/rc.d/rc.wicd*

note: the /etc/rc.d/rc.wicd is green in color, other lines are white, and followed by an asterisk.

I don't know what this means but on start up I see the message:
Error for wireless request "Set Nickname" (8b1C): SET failed on device wlan0; operation not supported.

I issued the /etc/rc.d/rc.wicd start just to see what would happen and I get "Starting wicd daemon...

I don't really need wicd but so far have not been successful in editing the inet1.conf file. All I really need is a web connection with WPA and a TKIP key.

Also, the LEDs on the pcmcia card have never lighted, under windows, they worked normally, so if the card is being detected wouldn't the LED's light. I just removed and replaced the card and the activity light blinked, so that has to be a good thing.
PH

onebuck · 06-05-2009, 06:52 PM

Hi,

You probably missed this from the wiki (note the bold);

Quote:

excerpt from 'Configuring your network in Slackware';
wicd

Wicd (pronouced as wicked) aims to provide a simple interface to connect to networks with a wide variety of settings. Some of Wicd's features include:

*
Ability to connect to wired and wireless networks
*
Profiles for each wireless network and wired network
*
Many encryption schemes, some of which include WEP/WPA/WPA2
*
Remains compatible with wireless-tools
*
Tray icon showing network activity and signal strength

Read more about it here: http://wicd.net/

Wicd installs a daemon which talks to your computer's dbus messagebus to detect network connects/disconnects. Configuration of your wireless as well as wired interfaces requires that you run X Window so you can use the graphical wicd-client.

If you want to use wicd, you will have to remove any network interface configuration information from /etc/rc.d/rc.inet1.conf in order to prevent a struggle for power between wicd and Slackware's rc.inet1 script.

You need to revert the '/etc/rc.d/rc.inet1.conf' to the original state without any network configuration.

You should have the '/etc/rc.d/rc.wicd' as executable then when you either re-boot or restart the service then the daemon should be running.

I'm curious? Post the output of 'ifconfig -a' and 'route-n'.

pighunter · 06-05-2009, 07:48 PM

Onebuck,

Thanks for the help.

ifconfig -a outputs:
irda0 Link encap:IrLAP HWaddr 00:00:00:00
NOARP MTU:2048 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:8
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

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:236 errors:0 dropped:0 overruns:0 frame:0
TX packets:236 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19092 (18.6 KiB) TX bytes:19092 (18.6 KiB)

Output for route -n:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo

As far as I know I am running X Window in an attempt to use the wicd client. I enter "startx" from the command prompt and it opens KDE. "Nework Manager - wicd" is one of the menu choices. Is this what you mean when you say run wicd from X Window.

I have returned inet1.conf to default values and wireless.conf to default values. I have attempted to use wicd in the above mentioned manner 3-4 times and apparently I continue to miss something.

I so appreciate all the help I have received.

Jim

Bruce Hill · 06-06-2009, 12:11 AM

I'm just about at the "grasping for straws" stage, because from here we
can not see your files. Please post the output of the following as root:

Code:

less /etc/wicd/wireless-settings.conf 
less /etc/rc.d/rc.inet1.conf
less /etc/rc.d/rc.wireless.conf
less /etc/wpa_supplicant.conf
iwconfig

And please use code tags to post your output so that we can easily read it.

pighunter · 06-06-2009, 01:14 AM

Bruce,

Thanks for hanging in there with me. Just at this moment connected and am browsing. I have not set up security yet but I think I can do it.

I didn't use wicd, never could get it to work. I just manually configured the inet1.conf and the resolv.conf files and it worked!

I couldn't have done this without your help!

God bless,

Jim

Bruce Hill · 06-06-2009, 03:34 AM

Okay, glad you're on the net without a wired.

Might I suggest that you read Alien Bob's WPA encryption information?

If you need help afterwards, we're here...

God bless you, Jim. He's the only reason for living.

onebuck · 06-06-2009, 07:46 AM

Hi,

I believe your 'wicd' problem was that you never really start the daemon. Once you start the daemon then you should be able to work around any network as long as the configs are proper. I never rely on 'KDE' tools for any system configuration. You should get in the habit of doing configuration from the 'cli' as root.

Glad to hear your on.