LinuxQuestions.org - DWL-G520+ & Suse 9.2 pro problem

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - DWL-G520+ & Suse 9.2 pro problem (https://www.linuxquestions.org/questions/linux-hardware-18/dwl-g520-and-suse-9-2-pro-problem-281947/)

DWL-G520+ & Suse 9.2 pro problem

Hi everyone, I'm totally new in linux & I've no experience with it. First I installed mandrake 10.1 but my wireless card, a D-Link DWL-G520+ 54Mbps, was not work. I spend 12 hours into forums thread but nothing. After I installed suse 9.2 pro and it recognised my card but it doesn't work. I can't use linux without internet but I don't want to use anymore winzozz xp...anyone can send me a step by step instruction on how to install my wireless card? Thanks in advance and sorry for my english but I don't speak english very well.

Please help me! I want to start using linux but whitout internet I can't! If anyone want to help me I have so many gmail invites (1Gb with webmail & pop3 access free!!!) Please reply. Thanks.

I have the same card - and to be honest it was harder to get it to work with XP that SuSE!!!

Anyway, there are two options available for this card:

1. The first is a set of drivers originally written for the ACX100 chipset but also compatible with the ACX111 chipset (that the DWL-G520+ uses). However the catch with these drivers is that WEP doesn't work on the ACX111 chipset at the moment (although they are updated fairly frequently and judging by the comments I think WEP support will be soon. Check out either sourceforge (the projects original home - search for the ACX100 project) or http://lisas.de/~andi/acx100/
for a direct link to the drivers (the author hasn't been updating the sourceforge stuff).

2. The second is something call NDISWrapper which (as I understand it) effectively provides a layer between the Linux kernel (I'm sure somebody will correct me and tell me it's not the kernel but the network layer or something - I'm not that technical ;) ) and the API that the drivers provide to the Windows layer. Again, find this on SourceForge by doing a project search for NDISWRAPPER.

At the moment I'm using the ACX100 drivers but I'm am planning on trying out the NDIS drivers as the G support isn't as good as the B support with ACX100 (I stream lots of TV shows and Film to the TV via my Xbox and sometimes see glitches with the ACX100 drivres) and the lack of WEP support on that LAN makes me nervous.

Hopefully I'll have time to try the NDIS drivers over the next couple of weeks - let me know if you try them before then and how you get on.

Ndis doesn't work!

Well, first of all thanks to have answered. Second, sorry for my english. I tried to install ndiswrapper but I failed. I'm a total newbie and I will be so happy if anyone post me an <how to install> step-by-step. However I tried to use the acx100 but it doesn't work. Please help a total noobs as me that want to leave winzozz!Thanks.

Long time since replying to this post. Anyway...

Finally got round to upgrading to 9.2 and installing NDISWrapper. The only problem I had was that there was still a copy of an old ndiswrapper.ko in the /lib/modules/<kernel>/extras directory. What error were you getting when trying to install ndiswrapper??

ACX100 doesn't support wep and only ever worked with low connection speeds. I'd recommend concentrating on ndiswrapper rather than acx100.

step by step, but...

You can read this link: http://www.houseofcraig.net/acx100_howto.php

I personally finished at this step: ping -c 4 -I ath0 192.168.1.1
is OK, but
ping -c 4 -I "my IP 192.168.1.125" 192.168.11
host is unreachable...
and I've no idea how to improve my setting. For detail of my setting please go to http://www.volny.cz/slymak/wifi.htm
I'm run at Mandrake 10.1 kernel 2.6.11

Hi slymak

Firstly, having used both I'd strongly recommend using the NDISWrapper drivers for this card in preference to the ACX100 drivers.

Anyway, on to your difficulties...

Looking at the screenshots you have a very small subnet - just you! Have you checked the settings (subnet mask) on the router that's allocating the IP addresses?

In your case you have a network of just you with no default gateway - your routing table is kind of empty and should look something like (from netstat -r):

Code:

===========================================================================

Interface List

0x1 ........................... MS TCP Loopback interface

0x2 ...00 0f 3d 58 0b 9d ...... D-Link AirPlus G+ DWL-G520+ Wireless PCI Adapter - Packet Scheduler Miniport

0x3 ...00 02 e3 18 5d ab ...... NETGEAR FA311 Fast Ethernet Adapter - Packet Scheduler Miniport

0x4 ...00 0d 61 0e d2 cd ...... Realtek RTL8139/810x Family Fast Ethernet NIC - Packet Scheduler Miniport

===========================================================================

===========================================================================

Active Routes:

Network Destination        Netmask          Gateway      Interface  Metric

          0.0.0.0          0.0.0.0      82.44.216.1  82.44.218.167          20

      82.44.216.0    255.255.248.0    82.44.218.167  82.44.218.167          20

    82.44.218.167  255.255.255.255        127.0.0.1      127.0.0.1          20

  82.255.255.255  255.255.255.255    82.44.218.167  82.44.218.167          20

        127.0.0.0        255.0.0.0        127.0.0.1      127.0.0.1          1

      192.168.1.0    255.255.255.0      192.168.1.1    192.168.1.1          20

      192.168.1.1  255.255.255.255        127.0.0.1      127.0.0.1          20

    192.168.1.255  255.255.255.255      192.168.1.1    192.168.1.1          20

      192.168.3.0    255.255.255.0      192.168.3.1    192.168.3.1          25

      192.168.3.1  255.255.255.255        127.0.0.1      127.0.0.1          25

    192.168.3.255  255.255.255.255      192.168.3.1    192.168.3.1          25

        224.0.0.0        240.0.0.0    82.44.218.167  82.44.218.167          20

        224.0.0.0        240.0.0.0      192.168.1.1    192.168.1.1          20

        224.0.0.0        240.0.0.0      192.168.3.1    192.168.3.1          25

  255.255.255.255  255.255.255.255    82.44.218.167  82.44.218.167          1

  255.255.255.255  255.255.255.255      192.168.1.1    192.168.1.1          1

  255.255.255.255  255.255.255.255      192.168.3.1    192.168.3.1          1

Default Gateway:      82.44.216.1

===========================================================================

Persistent Routes:

  None



Route Table

That's from my Windows box (and has 3 network adapters so is a bit cumbersome) rather than Linux but the principle is the same. You should have one entry for the current subnet (192.168.1.0) from for the local host (127.0.0.1) and one for everything else (0.0.0.0 - also known as the default gateway).

Another advantage to the NDISWrapper drivers is that they will pick up the ifcfg settings from /etc/sysconfig/network- rather than having everything scripted as ACX100 does.