Ok, i you can't copy & paste, run this instead:

and type it on here. Capitalize the "W" in above command.

We need to know if BT4 is "seeing" the wireless card.

i tryed and nothin happened!

root@bt: lspci | grep Wireless
root@bt:

anything else?

can u please help?

I can try if you post the full output of 'lspci' and/or 'lsusb,' or can confirm that the command retrieves details about said wireless card.

I can if you install it to your Hard Drive in a dual-boot scenario.

But without your help, how am I supposed to help you? Help me help you.

If the sole reason of using BackTrack 4 is for aircrack-ng, you can install a newer Linux distro, such as Ubuntu in a dual-boot scenario, with in-house support for the card.

Virtualization, if it hasn't worked yet, should not be so reiled on to give desired performance.

Hope you can understand why I have not posted with the above information given.

i am installing is a dual boot,, thanks for your help anyway!

thanks man

Good! This will probably make it work. If it doesn't, there is many ways that it can be made to work, since we are dealing with an actual card; instead of some virtual card.

Virtualization can add such a complicated layer of compatibility, because it is no longer the actual device, but whatever the programs wishes to make it. This can cause many problems, and apparently, direct support for the card is not available in Windows VM's.

ok my card works Internet works,, but when i type sudo airodump-ng wlan0

is starts to search for networks and after 20 mins still searching, wont find any networks,, i no there is cause i can find 6 in windows including mine,

any ideas

thanks again

Hey! Hooray!

Have you put the card into monitor mode yet?

Disable the GUI network manager and do;

1 members found this post helpful.

thanks so much

No problem. Glad the issue is resolved.

If you found my post(s) helpful, you can 'Thank' me by clicking on the 'Thanks' button on my post(s).

If your issue was resolved, go to the top of the webpage, click on Thread Tools -> Mark thread as SOLVED.

If you run into any more problems, its ok to ask

Happy hacking

hi i have the same problem. I'm using virtual box and when i type lspci / grep wireless i get this

Basic display modes:
-mm Produce machine-readable output (single -m for an obsolete format)
-t Show bus tree

Display options:
-v Be verbose (-vv for very verbose)
-k Show kernel drivers handling each device
-x Show hex-dump of the standard part of the config space
-xxx Show hex-dump of the whole config space (dangerous; root only)
-xxxx Show hex-dump of the 4096-byte extended config space (root only)
-b Bus-centric view (addresses and IRQ's as seen by the bus)
-D Always show domain numbers

Resolving of device ID's to names:
-n Show numeric ID's
-nn Show both textual and numeric ID's (names & numbers)
-q Query the PCI ID database for unknown ID's via DNS
-qq As above, but re-query locally cached entries
-Q Query the PCI ID database for all ID's via DNS

Selection of devices:
-s [[[[<domain>]:]<bus>]:][<slot>][.[<func>]] Show only devices in selected slots
-d [<vendor>]:[<device>] Show only devices with specified ID's

Other options:
-i <file> Use specified ID database instead of /usr/share/misc/pci.ids.gz
-p <file> Look up kernel modules in a given file instead of default modules.pcimap
-M Enable `bus mapping' mode (dangerous; root only)

PCI access options:
-A <method> Use the specified PCI access method (see `-A help' for a list)
-O <par>=<val> Set PCI access parameter (see `-O help' for a list)
-G Enable PCI access debugging
-H <mode> Use direct hardware access (<mode> = 1 or 2)
-F <file> Read PCI configuration dump from a given file

help please