D-Link DWL 520+ ACX 100 in openSuse 11

I recently installed openSuse 11 on a Dell 8250 machine that also has Windows XP installed (dual boot) My D-Link DWL 520+ works fine under XP.

Under Yast/Network Settings I see my card with the message

“ACX 100 22Mbps Wireless Interface (Not connected)
BusID : 0000:02:09.0
Unable to configure the network card because the kernel device (eth0, wlan0) is not present. This is mostly caused by missing firmware (for wlan devices). See dmesg output for details.”

I found some stuff on google and downloaded firmware
acx-firmware-20060207.tar.bz2

I untar’d it in /lib/firmware and it created an fs directory with many subfolders in it:

ls fs -al
dr-xr-xr-x 16 root root 4096 Feb 6 2006 .
drwxr-xr-x 3 root root 4096 Nov 23 20:12 …
dr-xr-xr-x 2 root root 4096 Feb 7 2006 acx100_1.0.7-USB
dr-xr-xr-x 2 root root 4096 Feb 7 2006 acx100_1.0.9-USB
dr-xr-xr-x 2 root root 4096 Feb 6 2006 acx100_1.10.7.K
dr-xr-xr-x 2 root root 4096 Sep 27 2005 acx100_1.10.7.i
dr-xr-xr-x 2 root root 4096 Aug 13 2005 acx100_1.7.0
dr-xr-xr-x 2 root root 4096 Feb 6 2006 acx100_1.9.10.0_A4
dr-xr-xr-x 2 root root 4096 Aug 12 2005 acx100_1.9.8.b
dr-xr-xr-x 2 root root 4096 Aug 12 2005 acx111_0.1.0.11
dr-xr-xr-x 2 root root 4096 Aug 12 2005 acx111_0.4.11.4
dr-xr-xr-x 2 root root 4096 Aug 12 2005 acx111_0.4.11.9
dr-xr-xr-x 2 root root 4096 Aug 12 2005 acx111_1.2.0.30
dr-xr-xr-x 2 root root 4096 Sep 6 2005 acx111_1.2.1.34
dr-xr-xr-x 2 root root 4096 Aug 12 2005 acx111_2.3.1.31
dr-xr-xr-x 2 root root 4096 Feb 7 2006 acx111_2.4.0.70-USB

My questions include:

  1. Do I already have a driver installed??? In Yast/Hardware Information I see the device and it seems to have a driver (from when I installed openSuse 11 2 weeks ago). The driver says “.modprobe acx”.

  2. How do I get the firmware installed??? I have no idea.

Thanks.

I found this
Hardware for Linux - D-Link System (by Texas Instruments) / DWL-520+ 22Mbps PCI Wireless Adapter

and

HCL/Network Adapters (Wireless) - openSUSE

OK, based on what I said in the first page of this thread, the “Status” message off of my “Computer” button in the lower left says that my wireless network is working, and that I’m connected to my correct ssid name. So I guess putting the modules I mentioned into /lib/firmware by itself did something. This was one of my questions in the first post (how to install firmware).

I entered my WEP settings. I named my wireless network (essid or ssid). If I choose a false name for my network ID (essid) it does not work (the status is not connected).

YET, I cannot browse the web, I am not really connected unless I plug in a hard ethernet wire to my computer.

odindba wrote:
> OK, based on what I said in the first page of this thread, the “Status”
> message off of my “Computer” button in the lower left says that my
> wireless network is working, and that I’m connected to my correct ssid
> name. So I guess putting the modules I mentioned into /lib/firmware by
> itself did something. This was one of my questions in the first post
> (how to install firmware).
>
> I entered my WEP settings. I named my wireless network (essid or ssid).
> If I choose a false name for my network ID (essid) it does not work (the
> status is not connected).
>
> YET, I cannot browse the web, I am not really connected unless I plug
> in a hard ethernet wire to my computer.

It looks as if you have a connection. Please post the output from the following
commands when using the proper WEP key:

/usr/sbin/iwconfig
/sbin/ifconfig
sudo /usr/sbin/iwlist scan
route -n

Larry

Thanks Much! I entered the first 3 of your 4 commands (what is “route -n”???) see results below I needed 2 posts because the forum poster thought I had images in this post (hex data???):
/usr/sbin/iwconfig
/sbin/ifconfig
sudo /usr/sbin/iwlist scan
route -n

/usr/sbin/iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11b+ ESSID:“odindba” Nickname:“linux-rvf8”
Mode:Managed Frequency:2.452 GHz Access Point: 00:22:6B:79:A3:61
Bit Rate:11 Mb/s Tx-Power=18 dBm Sensitivity=187/255
Retry min limit:7 RTS thr:off
Power Management:off
Link Quality=100/100 Signal level=100/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

/sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:07:E9:C6:D2:C4
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::207:e9ff:fec6:d2c4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1624 errors:0 dropped:0 overruns:0 frame:0
TX packets:1647 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:948258 (926.0 Kb) TX bytes:312322 (305.0 Kb)

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:707 errors:0 dropped:0 overruns:0 frame:0
TX packets:707 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:60559 (59.1 Kb) TX bytes:60559 (59.1 Kb)

wlan0 Link encap:Ethernet HWaddr 00:40:05:C5:C9:20
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::240:5ff:fec5:c920/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:328 errors:0 dropped:0 overruns:0 frame:0
TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:95715 (93.4 Kb) TX bytes:8166 (7.9 Kb)
Interrupt:18 Base address:0xec40

/usr/sbin/iwlist scan

lo Interface doesn’t support scanning.

eth0 Interface doesn’t support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:0D:72:5A:6A:B1
ESSID:“2WIRE723”
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=47/100 Signal level=40/100 Noise level=5/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
Cell 02 - Address: 00:0C:41:86:E1:C6
ESSID:“Heitzinger”
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/100 Signal level=29/100 Noise level=5/100
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Cell 03 - Address: 00:22:6B:79:A3:61
ESSID:“odindba”
Mode:Master
Frequency:2.452 GHz (Channel 9)
Quality=34/100 Signal level=100/100 Noise level=33/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Cell 04 - Address: 00:1E:52:78:A3:BE
ESSID:“P/P network”
Mode:Master
Frequency:2.452 GHz (Channel 9)
Quality=39/100 Signal level=14/100 Noise level=0/100
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb

Well, here’s where I’m at right now:

  1. my setup works when I boot XP.

but from openSuse 11:

  1. when I click the “computer” button in the lower left of Gnome, I see my wireless network connected (with the correct name of the network)

  2. I can see/update my wireless router config from a browser (firefox) by entering http://192.168.1.1

  3. I cannot get to any web site, or ping the ip addresses of oracle.com or google.

Can anyone out there see what is going on from the command output I posted above???

Thanks.

odindba wrote:
> Thanks Much! I entered the first 3 of your 4 commands (what is “route
> -n”???) see results below I needed 2 posts because the forum poster
> thought I had images in this post (hex data???):
> /usr/sbin/iwconfig
> /sbin/ifconfig
> sudo /usr/sbin/iwlist scan
> route -n
>
> wlan0 Link encap:Ethernet HWaddr 00:40:05:C5:C9:20
> inet addr:192.168.1.101 Bcast:192.168.1.255
> Mask:255.255.255.0
> inet6 addr: fe80::240:5ff:fec5:c920/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:328 errors:0 dropped:0 overruns:0 frame:0
> TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:95715 (93.4 Kb) TX bytes:8166 (7.9 Kb)
> Interrupt:18 Base address:0xec40

You do have a connection via wireless. One thing - if you don’t need IPV6 then
you should turn it off using YaST => Network Devices => Network Settings =>
Global Options.

The route command shows the routing tables. If they are wrong, you won’t get to
the Internet.

Larry

odindba wrote:
> /sbin/ifconfig
> eth0 Link encap:Ethernet HWaddr 00:07:E9:C6:D2:C4
> inet addr:192.168.1.100 Bcast:192.168.1.255
> Mask:255.255.255.0
> inet6 addr: fe80::207:e9ff:fec6:d2c4/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1624 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1647 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:948258 (926.0 Kb) TX bytes:312322 (305.0 Kb)
>
>
> wlan0 Link encap:Ethernet HWaddr 00:40:05:C5:C9:20
> inet addr:192.168.1.101 Bcast:192.168.1.255
> Mask:255.255.255.0
> inet6 addr: fe80::240:5ff:fec5:c920/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:328 errors:0 dropped:0 overruns:0 frame:0
> TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:95715 (93.4 Kb) TX bytes:8166 (7.9 Kb)
> Interrupt:18 Base address:0xec40

I missed something the first time. You have IP addresses for both eth0 and
wlan0. On my computer, that has confused networking. You should issue a ‘sudo
ifdown eth0’ command before trying to use the wireless. Alternatively, you could
unplug the ethernet cable.

Larry

Larry, I have been unplugging the ethernet cable before rebooting and testing new settings. Turning off IVP6 did not fix the problem.

Thanks again.

odindba wrote:
> Larry, I have been unplugging the ethernet cable before rebooting and
> testing new settings. Turning off IVP6 did not fix the problem.

Are you manually setting an IP for eth0?

I still have not seen the output of ‘/sbin/route -n’.

Larry

Linux people,

Here’s the output from route:

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 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

I am not setting a manual IP for anything, including eth0.

OK, here’s where I’m at, can anyone help me???

  1. I have openSuse 11 32 bit on Dell 8250 with dual boot to XP (where my wireless card works fine).

  2. I downloaded acx-firmware-20060207.tar.bz2

  3. in /lib/firmware, I xvf’d it to create an fw directory of many firmware sets.

  4. I copied tiacx100, tiacx100r0D, and tiacx100r11 to /lib/firmware from the fw/acx100_1.10.7.K directory of the firmware downloaded above.

  5. I configured card in Yast network services, and the message off of the “computer” button in gnome’s lower left said "wireless network - connected to “mynetworkname” was working. I was using wep encription.

  6. I could get to 192.168.1.1 (my Linksys WRT54GL wireless router’s admin stuff) through Firefox, but cannot see any web sites at all , even hard coded ip addresses.

  7. If I changed network name in Yast config to a network name of “doesnotexist” or entered wrong WEP keys, no network was found (off of “computer” button), and I could not even get to my wireless router.

Someone out there must have an idea what the above facts mean. openSuse 11 found is using it’s acx driver. Any ideas? I have hwinfo data below: Thanks.

>hwinfo --wlan
02: PCI 209.0: 0282 WLAN controller
[Created at pci.310]
UDI: /org/freedesktop/Hal/devices/pci_104c_8400
Unique ID: y9sn.xfSSjzfMUh1
Parent ID: 6NW+.eDbWAYN5SdB
SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:09.0
SysFS BusID: 0000:02:09.0
Hardware Class: network
Model: “D-Link DWL-520+ 22Mbps PCI Wireless Adapter”
Vendor: pci 0x104c “Texas Instruments”
Device: pci 0x8400 “ACX 100 22Mbps Wireless Interface”
SubVendor: pci 0x1186 “D-Link System Inc”
SubDevice: pci 0x3b01 “DWL-520+ 22Mbps PCI Wireless Adapter”
Driver: “acx_pci”
Driver Modules: “acx”
Device File: wlan0
Features: WLAN
I/O Ports: 0xec40-0xec5f (rw)
Memory Range: 0xfe1fd000-0xfe1fdfff (rw,non-prefetchable)
Memory Range: 0xfe1e0000-0xfe1effff (rw,non-prefetchable)
IRQ: 18 (no events)
HW Address: 00:40:05:c5:c9:20
Link detected: yes
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462
WLAN bitrates: 1 2 5.5 11 22
WLAN encryption modes: WEP40 WEP104 WEP232
WLAN authentication modes: open sharedkey
Module Alias: “pci:v0000104Cd00008400sv00001186sd00003B01bc02sc80i00”
Driver Info #0:
Driver Status: acx is active
Driver Activation Cmd: “modprobe acx”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #15 (PCI bridge)

It turned out that the default gateway in the Yast Network Config was blank, and everything worked if I set it to 192.168.1.1