Need Help With Wireless D-Link DWL-g510

For the device you have, you may need to use ndiswrapper and the original windows driver to get the device functioning.

Look up ndiswrapper under the mepis community pages to get a howto if you're not familiar with the procedure. You may need to blacklist the marvel drivers

Use the Mepis Network Assistant and click on the wireless tab to see if the device is functioning. If it is, you will see something like Wireless on wlan0
Type in your ssid, encryption type and password if required, then click on the interfaces tab and set the device to start at boot.

If the wireless on ___ line is blank (under the wireless tab), your device driver is not functioning. Keep at it until it is listed.

You might get better help from the Mepislovers site. This site is geared more towards the devs, but it is very good for documentation.

Mike P

--------------------
Life may not be the party we thought, but while we're here, we may as well dance.
Break M$'s shackles from your feet and free yourself with Mepis

Windows Drivers for your card are available here, or you can get them from your CD or Windows installation

ftp://ftp.dlink.com/Wireless/dwlg510/Drivers/dwlg510_driver_100.zip

Unzip these to a folder in Linux, and follow the instructions here:

http://www.mepis.org/docs/en/index.php/Using_Ndiswrapper

Mike

If your card is like my Netgear WG311v3 card that uses a Marvell chipset, you'll need to remove the mrv8k51 driver that ndiswrapper has installed showing driver and hardware present.

With my card, this mrv8k51 driver doesn't actually work (even though ndiswapper is happy). So, you'll probably need to remove it. See if you have a wireless connection for wlan0 shown when you type this from a console:

iwconfig

If so, use the Mepis Network Assistant to configure it. Otherwise, keep reading.

I'd copy the drivers from the CD that came with the card. Or, try the drivers at the link already posted to this thread. If you use the ones from the CD, I'd probably try drivers from the Win98/Win 2000 folder (if it has drivers for both XP and older Windows versions). You'll see a folder that has about 4 files in it (yourdriver.inf, yourdriver.cat, yourdriver.sys, etc.).

Just copy those files to your desktop and do this (substituting your driver's .inf file name for WG311v3.INF, pressing enter each line.

Note that the commands are case sensitive, and you'll need to pay attention to mixed case driver names (as in the WG311v3.INF driver that I use with ndiswrapper), substituting the name of the .inf file that you copied to your Desktop. Note that your driver may or may not need a valid ESSID (you'll need to know your routers ESSID and substitute it for myessid if it does). You may want to try it without that line first (iwconfig wlan0 ESSID myessid)

su
cd Desktop
ndiswrapper -e mrv8k51
ndiswrapper -i WG311v3.INF
ndiswrapper -m
modprobe -r ndiswrapper
modprobe ndiswrapper
iwconfig wlan0 ESSID myessid
dhclient wlan0

You should now be connected if your router is setup for dhcp with no encryption. Then, just go to the Mepis Network Assistant and enter any parameters needed.

If you make a mistake (not in the same directory as the driver files, wrong case, etc.), remove the driver like this and start over at the beginning. You must be in the same folder as the drivers when installing them with ndiswrapper. Removing the driver is not case sensitive and you don't include the .inf extension.

su
ndiswrapper -e wg311v3

As before, substitute your driver's actual name versus the wg311v3 used in the above examples.

Jim C.

Jin,
I followed your directions but it didn't work. Ironicly each driver (Win 98, Win Me and Win XP) is named mrv8k51 I started with Win Xp but the system complained a lot about that one. I then used the one for Win 98.

Your procedure worked with no complaints until I got to;
# ndiswrapper -m
Response was "module configuration already contains alias directive

# iwconfig wlano ESSID YoderHome
Response "Error for wireless request "Set ESSID" (8B1A)) :
SET failed on device wlan0; No such device"S

# dhclient wlan0
Response "SIOSIFADDER: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device.

It appears that the interface "wlan0" is not active. How do you do that?

Rony

Are you sure iwconfig didn't show wlan0 to begin with?

What do you get when you type this now:

iwconfig

What do you get when you type this:

ndiswrapper -l

Jim C.

No, iwconfig did not show "wlan0" to begin with.

iwconfig responds "lo no wireless extensions

ndiswrapper responds that a device is present for driver mrv8k51

Rony

Did you finish the rest of the steps in the list (even though it said that an alias for wlan0 was already there)?

What do you get if you try this (making sure your doing it as root by entering the password when prompted). Edited -- forget to put su at the beginning of the list).

su
ndiswrapper -m
modprobe -r ndiswrapper
modprobe ndiswrapper
iwconfig

Try rebooting and do it again if you still don't see wlan0 show up.

Are you sure it's not seeing more than one driver for it when you type ndiswrapper -l (with one of them showing bad from an install somewhere)? Or, does it look exactly the same way as it did the first time you posted it above?

Jim C.

Yes I finished all steps regardless of response

#ndiswrapper -m
module configuration already contains alias directive

#modprobe -r ndiswrapper
no response

modprobe ndiswrapper
no response

#iwconfig
lo no wireless extensions

I did this twice, rebooting after each.

mrv8k51 is the only driver with a device present.

I have no idea what I'm talking about but, is it possible that wireless extensions are not configured on my download?

Rony

In the "Debugging Wireless Extensions" section of "Wireless Tools for Linux" it states that if;
iwconfig responds "no wireless extensions"
you should
1. Enable the config option CONFIG_NET_RADIO in your kernal setup.
2. Recompile and reinstall this kernal.
3. Recompile and reinstall the kernal modules.
4. Do cat/proc/net/wireless. If the command returns an error, you are using the wrong kernal. Try again.

HOW DO I DO THIS??? How do I check to see if this is even my problem?

I really don't want to give up on Linux but if getting connected to a network is this much trouble, what else can I expect?

The Mepis kernel is compiled with the correct options / modules already, so you shouldn't have to do any of that.

I have a Marvell based PCCard adapter and I had to use the Windows 2000 drivers in ndiswrapper to get it to work. XP & 98 drivers failed. Remove the Win98 drivers (ndiswrapper -e mrv8k51) and try again with the Win2k drivers.

Good Luck!

Thanks to all. Davo from Mepislovers provided the solution. I had to blacklist "mvr8k" in the /etc/modprobe.d/blacklist file.Then run iwconfig. After doing this it immediately came to life. Thanks again.
Rony