Re: rt73.ko fail to build
The DWL-G122 has some rev and each one has different chipset:
DWL-G122 rev A2 = chipset Intersil
DWL-G122 rev B1 = Ralink 2571
DWL-G122 rev C1 = Ralink 2571W
DWL-G122 rev D1 = marvel
DWL-G122 rev F1 = Realtek
You need to be more specific..Also post the driver used by kernel and the device discovered by udev (lspci | grep -i network)
Luck.
Re: rt73.ko fail to build
Thanks for reminding me there are different versions of my usb.
It should be rev F1 and I was cheated by the seller who claimed that it is rev C1. So, is my usb compatible?
Besides, there is no output of the command "lspci | grep -i network". Is it normal? I don't even have a directory "drivers" in /usr/src.
Re: rt73.ko fail to build
Sorry, I forgot it was usb device, very sorry, it should be: lsusb | grep -i network.
Post output..
Re: rt73.ko fail to build
I have typed this command but there is still no output.
wlan0 is still shown when I type ifconfig -a and iwconfig
Re: rt73.ko fail to build
Strange, type lsusb and see if device is listed.
The F1 version has a realtek chipset, please read here: http://www.wikidevi.com/wiki/D-Link_DWL-G122_rev_F1 and it has a RTL8188SU chipset.
According to the link above, you can use 2 drivers: the open driver (r8712u) or the propietary from realtek (http://www.realtek.com.tw/downloads/...true#RTL8188SU)
But you need to make sure if it is F1 revision. Again, try: lsusb and see if device is listed.
Re: rt73.ko fail to build
Here is the output
Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 2001:3306 D-Link Corp.
Bus 001 Device 002: ID 05ac:8509 Apple, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
the device "D-Link Crop" is listed
I am sure it is F1 revision as I have installed it in my windows 8 and saw the name of this device
By the way, can this usb be used in aircrack-ng as these 2 drivers are not listed in aircrack-ng.org?