Networking :: dlink dwl g122 usb not working

Hi Guys,

my system : 3.1 dsl frugal
my wireless adapter : dlink usb dwl g122 (prism 3 based)

i found a driver for it done peter mische in the "difficult to work with adapters" section

after "insmod rt73.o ( the driver meant for the adapter)"

i do lsusb. i see the wireless interface.
i do iwconfig. i see the rausb0 interface as well.

then i tried static ip with ifconfig and attempted dhcp with wlanconfig with essid name and channel. i have attempted this by stopping the dhcp daemon in the control panel also.
i have even tried pump -i rausb0

i always get a segmentation fault. after that i just have to reboot to work with the pc. according to peter his script should work.

iam i missing anything.
see my script below.

Code Sample

#!/bin/bash
/sbin/insmod /home/dsl/rt73.o
sync; sync
/sbin/ifconfig rausb0 192.168.1.102 netmask 255.255.255.0 broadcast
192.168.1.255
/sbin/route add default gw 192.168.1.1
echo nameserver 192.168.1.1 > /etc/resolv.conf
sync; sync
/sbin/iwconfig rausb0 channel 6
ifconfig rausb0 up

alternatively is there any usb adpater with current chipsets that would just work out of the box . and also would a future version like 3.3 have out of the box drivers for prism 3 ?

thanks.

Where does it segfault? You could try the script by running one line at a time manually.

Not that this should cause your problem, but I think

Code Sample

/sbin/ifconfig rausb0 192.168.1.102 netmask 255.255.255.0 broadcast
192.168.1.255

should be on one line.

Hi,

it seg faults exactly on this line

/sbin/ifconfig rausb0 192.168.1.102 netmask 255.255.255.0 broadcast 192.168.1.255

and it is one line. if just breaks when i paste it here in he forum.

thanks.

I have used a SMC usb adapter that worked out-of-box in DSL 1.x - but it wasn't wifi.

However, I just noticed you were trying to use the rt73 with a prism3 chipset... which is not the correct driver - prism54usb should be it.

Double check which g122 revision you have - each one seems to use a different chipset and requires a different driver (some can also use ndiswrapper).

original here.