After discovering the following in the sticky for this forum, I initially thought my wireless card would be trash:
“If you cannot find a wireless device in either step (a) or step (b), your
hardware is broken. It may be the motherboard or the wireless device. In either
case, until the device is seen by either lsusb or lspci, we will not be able to
help you.”
However, 11.1 does indeed see my device. It just cannot retrieve the hardware address, thus, the card device wlan0 cannot be brought up.
See below…
linux-xoc2:/home/radams1 # ifstatus wlan0
wlan0 device: D-Link
DWL-650 Wireless PC Card RevP
ISL37101P-10
A3
DHCP4 client NOT running
autoip not running
wlan0 not up
wlan0 is down
linux-xoc2:/home/radams1 # ifup wlan0
wlan0 device: D-Link
DWL-650 Wireless PC Card RevP
ISL37101P-10
A3
wlan0 warning: wpa_supplicant already running on interface
Starting DHCP4 client on wlan0. . . .
wlan0 DHCP4 client NOT running
Starting autoip on wlan0… failed
interface wlan0 is not up
linux-xoc2:/home/radams1 #
…and yes, I have used Yast2 in attempts to configure the device. Please see output below:
linux-xoc2:/etc/sysconfig/network # cat ifcfg-wlan0
BOOTPROTO=‘dhcp+autoip’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IFPLUGD_PRIORITY=‘10’
IPADDR=’’
MTU=’’
NAME=‘DWL-650 Wireless PC Card RevP’
NETMASK=’’
NETWORK=’’
REMOTE_IPADDR=’’
STARTMODE=‘hotplug’
USERCONTROL=‘yes’
WIRELESS_AP=’’
WIRELESS_AUTH_MODE=‘psk’
WIRELESS_BITRATE=‘auto’
WIRELESS_CA_CERT=’’
WIRELESS_CHANNEL=’’
WIRELESS_CLIENT_CERT=’’
WIRELESS_CLIENT_KEY=’’
WIRELESS_CLIENT_KEY_PASSWORD=’’
WIRELESS_DEFAULT_KEY=‘0’
WIRELESS_EAP_AUTH=’’
WIRELESS_EAP_MODE=’’
WIRELESS_ESSID=‘339eks-bel-3’
WIRELESS_FREQUENCY=’’
WIRELESS_KEY=’’
WIRELESS_KEY_0=’’
WIRELESS_KEY_1=’’
WIRELESS_KEY_2=’’
WIRELESS_KEY_3=’’
WIRELESS_KEY_LENGTH=‘128’
WIRELESS_MODE=‘Managed’
WIRELESS_NICK=’’
WIRELESS_NWID=’’
WIRELESS_PEAP_VERSION=’’
WIRELESS_POWER=‘yes’
WIRELESS_WPA_ANONID=’’
WIRELESS_WPA_IDENTITY=’’
WIRELESS_WPA_PASSWORD=’’
WIRELESS_WPA_PSK=’**********’
linux-xoc2:/etc/sysconfig/network #
So, the purpose of this post is to determine if the inability to obtain the HW address indeed classifies my card as “broken”? Please advise.
rkahn2007 wrote:
> After discovering the following in the sticky for this forum, I
> initially thought my wireless card would be trash:
>
> “If you cannot find a wireless device in either step (a) or step (b),
> your
> hardware is broken. It may be the motherboard or the wireless device.
> In either
> case, until the device is seen by either lsusb or lspci, we will not
> be able to
> help you.”
– snip –
> So, the purpose of this post is to determine if the inability to obtain
> the HW address indeed classifies my card as “broken”? Please advise.
I DID not see the output of either lspci or lsusb. The line quoted
above is pretty clear.
Larry
Thanks for the reply. The output of the lspci was not provided because no listing was found for the wireless card, other than that for he cardbus, however, I have provided it below for your review:
linux-xoc2:/home/radams1 # lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:0a.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller
00:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] (rev 10)
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1e)
00:11.4 Bridge: VIA Technologies, Inc. VT8235 ACPI (rev 10)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 40)
00:11.6 Communication controller: VIA Technologies, Inc. AC’97 Modem Controller (rev 20)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 51)
01:00.0 VGA compatible controller: S3 Inc. VT8636A [ProSavage KN133] AGP4X VGA Controller (TwisterK) (rev 01)
linux-xoc2:/home/radams1 #
…and output from the lspci -n command:
linux-xoc2:/home/radams1 # lspci -n
00:00.0 0600: 1106:0305 (rev 80)
00:01.0 0604: 1106:8305
00:0a.0 0607: 1217:6972
00:0c.0 0c00: 104c:8026
00:11.0 0601: 1106:8231 (rev 10)
00:11.1 0101: 1106:0571 (rev 06)
00:11.2 0c03: 1106:3038 (rev 1e)
00:11.4 0680: 1106:8235 (rev 10)
00:11.5 0401: 1106:3058 (rev 40)
00:11.6 0780: 1106:3068 (rev 20)
00:12.0 0200: 1106:3065 (rev 51)
01:00.0 0300: 5333:8d02 (rev 01)
linux-xoc2:/home/radams1 #
Naturally, I was not able to find the matching lines mentioned in the sticky.
Your wireless adapter is not found in the PCI list. You need to use
the lsusb command. If you get a “command not found” message, you need
to install the usbutilities package.
Larry
Way ahead of you on that one. The PCMCIA card is not a USB device. The output of the lsbusb command merely shows the connected USB mouse that I am using.
Please see below:
linux-xoc2:/home/radams1 # lsusb
Bus 001 Device 002: ID 047d:1037 Kensington
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
linux-xoc2:/home/radams1 #
Next?
rkahn2007 wrote:
> Way ahead of you on that one. The PCMCIA card is not a USB device. The
> output of the lsbusb command merely shows the connected USB mouse that I
> am using.
>
> Please see below:
> linux-xoc2:/home/radams1 # lsusb
> Bus 001 Device 002: ID 047d:1037 Kensington
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> linux-xoc2:/home/radams1 #
>
> Next?
Duh. I need to read your title!
You need to run the ‘lspcmcia ident’ command.
Obviously, your card is 16-bit. If the card that plugs into the PCMCIA
slot is 32-bit, it is connected to the PCI system, but yours is not.
Larry
Larry, you are a funny guy. Now we are covering new ground. Please see below the output of the lspcmcia ident command:
linux-xoc2:/home/radams1 # lspcmcia ident
Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:00:0a.0)
Socket 0 Device 0: [hostap_cs] (bus ID: 0.0)
linux-xoc2:/home/radams1 #
I do know that the d-link dwl-650 card is using the hostap_cs driver.
Your thoughts?
rkahn2007 wrote:
> Larry, you are a funny guy. Now we are covering new ground. Please see
> below the output of the lspcmcia ident command:
>
> linux-xoc2:/home/radams1 # lspcmcia ident
> Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:00:0a.0)
> Socket 0 Device 0: [hostap_cs] (bus ID: 0.0)
> linux-xoc2:/home/radams1 #
>
> I do know that the d-link dwl-650 card is using the hostap_cs driver.
>
> Your thoughts?
Does the command ‘dmesg | grep host’ show anything?
Nothing…see below:
linux-xoc2:/home/radams1 # dmesg | grep host
linux-xoc2:/home/radams1 #
rkahn2007 wrote:
> Nothing…see below:
>
> linux-xoc2:/home/radams1 # dmesg | grep host
> linux-xoc2:/home/radams1 #
You need to issue the command ‘dmesg | less’ and page through the
output. To see how to use less, enter ‘man less’. Typing a q will quit
man or less.
Larry
Ok, got a lot of stuff from the dmesg command, but the following is bascially what is repeated:
wlan0: cannot get RID fd42 (len=6) - no PRI f/w
wlan0: cannot get RID fc84 (len=2) - no PRI f/w
wlan0: cannot get RID fdc6 (len=12) - no PRI f/w
wlan0: cannot get RID fdc1 (len=2) - no PRI f/w
wlan0: cannot get RID fd41 (len=34) - no PRI f/w
wlan0: cannot get RID fdc6 (len=12) - no PRI f/w
Your thoughts?
Anybody, any thoughts? The only item not detected is the hardware address.
rkahn2007 wrote:
> Ok, got a lot of stuff from the dmesg command, but the following is
> bascially what is repeated:
>
> wlan0: cannot get RID fd42 (len=6) - no PRI f/w
> wlan0: cannot get RID fc84 (len=2) - no PRI f/w
> wlan0: cannot get RID fdc6 (len=12) - no PRI f/w
> wlan0: cannot get RID fdc1 (len=2) - no PRI f/w
> wlan0: cannot get RID fd41 (len=34) - no PRI f/w
> wlan0: cannot get RID fdc6 (len=12) - no PRI f/w
>
> Your thoughts?
Do you think that f/w means firmware? I do.
You need to obtain and install the correct files. Doesn’t the dmesg
output say what file it is looking for?
Larry Finger wrote:
> rkahn2007 wrote:
>> Ok, got a lot of stuff from the dmesg command, but the following is
>> bascially what is repeated:
>>
>> wlan0: cannot get RID fd42 (len=6) - no PRI f/w
>> wlan0: cannot get RID fc84 (len=2) - no PRI f/w
>> wlan0: cannot get RID fdc6 (len=12) - no PRI f/w
>> wlan0: cannot get RID fdc1 (len=2) - no PRI f/w
>> wlan0: cannot get RID fd41 (len=34) - no PRI f/w
>> wlan0: cannot get RID fdc6 (len=12) - no PRI f/w
>>
>> Your thoughts?
>
> Do you think that f/w means firmware? I do.
>
> You need to obtain and install the correct files. Doesn’t the dmesg
> output say what file it is looking for?
The firmware you need is found at
http://acx100.sourceforge.net/wiki/Firmware.
Larry