D-Link DWL-G122 v.A1 problems


Forum: Networking
Topic: D-Link DWL-G122 v.A1 problems
started by: se2schul

Posted by se2schul on Sep. 24 2006,17:14
I've been trying for 2 days to get this wireless adapter working without success. I'm pretty new to linux, so it is likely that I'm just skipping some really basic step, or that I misunderstood the steps I was supposed to take.

I've tried using ndiswrapper from DSL's command line.
1) copy NetRTUSB.inf file to /link
2) ndiswrapper -i /link/NetRTUSB.inf
3) ndiswrapper -l says: "netrtusb: invalid driver!"

I also tried using the ndiswrapper from the DSL control panel with the same results.

I've also heard that if the chipset of the wireless adapter is known, that it might be possible to download source code for a linux driver.  If this is a better alternative, I'll need help with this. I don't know the chipset.  I'm currently working on downloading the gcc compiler through mydsl.  Once this is done, it will be possible for me to compile a driver if one exists.  

If you can provide help, the more detailed your explanation, the better! I only have very basic linux knowledge.

Thanks.

Posted by ^thehatsrule^ on Sep. 24 2006,18:56
You should be able to use the native linux drivers - rev A's are supported by the prism2 chipset (from google)
It's also listed in < http://damnsmalllinux.org/wiki/index.php/Verified_Wireless_Cards > but apparently the rev B's use a different chipset.

Lucky for you, these are even included in DSL by default!  (note you can use lsusb to make sure of your USB model/chipset)

Posted by se2schul on Sep. 24 2006,21:54
This is excellent news.  I'm glad it should be easy, but I'm still having problems.

I noticed that the adapter D-Link DWL-122 USB is listed under the "Use the Prism2 Gui With These Cards" section of the "Verified Wireless Cards" wiki. Mine is actually the DWL-G122.  I wasn't sure if it was the same as the DWL-122 listed.

I'll provide a step-by-step of what I think I have to do, and hopefully someone can spot the step that I'm forgetting.

1) Boot DSL
2) Log in as root
3) Launch DSL Control Panel
4) Click the Prism2 button
5) Configure it as follows:
  device: wlan0
  channel: 6
  ssid: kats
  wep: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
6) Press the 'OK' button

At this point, I receive an error stating: "Connection Failed!"

As far as my configuration, I've configured the channel, ssid and wep as per my router setup.  I'm not sure if the device should be listed as wlan0 or if it should be something else.

If you need more information to help me solve this, please let me know.

Posted by ^thehatsrule^ on Sep. 25 2006,03:26
Ah I didn't see that, and they are probably different models, hence the wiki didn't have the different rev chipsets listed.

But your rev A seems to use prism2, from google results.  Did you check your chipset by lsusb?  I can't really help you with the wlan config since I don't use DSL+wifi myself.

Posted by se2schul on Sep. 27 2006,02:21
This one still has me stumped...

Output from lsusb is:
Bus 001 Device 003: ID 2001:3707 D-Link Corp. [hex]

I'm not sure what this means.
I don't seem to be able to configure this card using only the Prism2 interface.  Am I doing something wrong, or is there another way I should be configuring the card?

Thanks.

Posted by ^thehatsrule^ on Sep. 27 2006,13:32
Hm, according to < http://linux-wless.passys.nl/query_part.php?brandname=D-Link > its a prism gt, not a prism2 - I must've read a bad post somewhere else.  I guess you best bet would be prism54.org

So your usb is detected.. think you can use lsusb -v ?

Posted by se2schul on Sep. 27 2006,22:20
Quote (^thehatsrule^ @ Sep. 27 2006,09:32)
So your usb is detected.. think you can use lsusb -v ?

0000:00:00.0 Host bridge: Toshiba America Info Systems 601 (rev 27)
Flags: bus master, medium devsel, latency 0

0000:00:02.0 CardBus bridge: Toshiba America Info Systems ToPIC95 (rev 07)
Flags: bus master, slow devsel, latency 0, IRQ 11
Memory at 10000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=14, subordinate=14, sec-latency=0
Memory window 0: 10400000-107ff000 (prefetchable)
Memory window 1: 10800000-10bff000
I/O window 0: 00004000-000040ff
I/O window 1: 00004400-000044ff

0000:00:02.1 CardBus bridge: Toshiba America Info Systems ToPIC95 (rev 07)
Flags: bus master, slow devsel, latency 0, IRQ 11
Memory at 10001000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=15, subordinate=15, sec-latency=0
Memory window 0: 10c00000-10fff000 (prefetchable)
Memory window 1: 11000000-113ff000
I/O window 0: 00004800-000048ff
I/O window 1: 00004c00-00004cff

0000:00:04.0 VGA compatible controller: Chips and Technologies F65554 (rev c2) (prog-if 00 [VGA])
Flags: stepping, medium devsel
Memory at fe000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at <unassigned> [disabled] [size=256K]

0000:00:0b.0 USB Controller: NEC Corporation USB (rev 01) (prog-if 10 [OHCI])
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at fdfff000 (32-bit, non-prefetchable) [size=4K]

Posted by ^thehatsrule^ on Sep. 28 2006,17:21
Err.. I think you did an lspci instead of lsusb (I edited my post earlier) :P

Anyways, I looked it up, and you do have the right model you thought you did.
{USB_DEVICE(0x2001, 0x3703)}, /* DLink DWL-G122 */

And I looked into the forum and official site for prism54, and found out you're better off trying to do your first post (ndiswrapper)... as the driver only supports newer 2.6 kernels, and is incomplete.

Posted by roberts on Sep. 28 2006,17:34
When using ndiswrapper you will need both the .inf and the corresponding .sys files. Your first post seemed to indicate that only the .inf file was copied.
Posted by se2schul on Sep. 29 2006,02:05
Ah... That was one of my mistakes.

Now the driver gets installed.

When I type: "ndiswrapper -m", it says that modprobe config already contains alias directive. I tried to start it using 'modprobe ndiswrapper', but I can't tell if it's working.

I tried to configure it using Netcardconfig, WLanconfig, Ndiswrapper, and IWconfig under the DSL Control Panel, but I can't seem to get it to work.

What should I try next ??

Posted by roberts on Sep. 29 2006,04:18
$ sudo pump -i wlan0


The typical sequence of commands as root are:

# ndiswrapper -i your_cards.inf
# modprobe ndiswrapper
# iwconfig wlan0 key 99:99:99:99....  essid your_ssid_here
# pump -i wlan0


Or try the ndiswrapper GUI from the DSLpanel



Posted by se2schul on Sep. 30 2006,00:18
Quote (roberts @ Sep. 29 2006,00:18)
$ sudo pump -i wlan0


The typical sequence of commands as root are:

# ndiswrapper -i your_cards.inf
# modprobe ndiswrapper
# iwconfig wlan0 key 99:99:99:99....  essid your_ssid_here
# pump -i wlan0


Or try the ndiswrapper GUI from the DSLpanel

I couldn't get the GUI from the DSL Panel to work.
When I type the sequence of commands, this is what happens:

# ndiswrapper -l
netrtusb driver installed
# modprobe ndiswrapper
# iwconfig wlan0 key 99:99:99:99....  essid your_ssid_here
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; No such device.
# pump -i wlan0
Operation failed.

Any suggestions now?

Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.