I have downloaded and installed ndiswrapper v.1.58 and the appropriate driver neti2220 for my InProComm wireless card.

and from sudo lshw -C network the following partial output:

Then:
Followed by:

I felt discouraged by this result but I pressed ahead and attempted to create a connection using network-manager from terminal, and then using wpa_supplicant from terminal, in both cases without success. I have many details of these attempts if needed.

Perhaps the zero scan result is pointing to the problem.
Is there a way to cause the machine to see the modem?

I'm not sure if I can help you with this but, judging from this thread and perhaps others, you're not the only one who has experienced problems with this adapter using ndiswrapper.

As mentioned in that thread, check your kernel logs to see what ndiswrapper is reporting. Using the "dmesg" in a terminal command might give you the same information. I also found some other pages that might be of help....

Please see the post by frederik1975 (at the bottom) here.

I also found this blog.

Finally, make sure the EULA for the Windows driver permits its use in Linux.

Thanks!

What is the precise chipset in the card? The command lspci should reveal that information.

lspci shows the following:
02:02.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
02:04.0 Ethernet controller: InProComm Inc. IPN 2220 802.11g

Thanks aardvark71. The first link confirms that others have had a similar problem with the InProComm device.
The link to frederick1975 was instrumental a few days ago in pointing out my then current version of ndiswrapper v.1.57 wasn't compatible with 12.04. I deleted 1.57 and installed 1.58. The previous problems with 1.57 disappeared and I was able to install the recommended drivers, neti2220. See this:
The blog link describes a process of activating the device and driver that has not been successful on my machine.
It looks like my wireless card is not seeing the modem.

Just as an idea, have you tried different versions of the driver? The OP on this thread mentioned the drivers on the bottom of this thread worked for him.

If you are unable to get it to work at all, how about getting a USB adapter like this one? Just make sure you contact them first to see how much shipping would be to your country before you order, if you get this model from them.

Regards...

Thanks aardvark71. The first link confirms that others have had a similar problem with the InProComm device.
The link to frederick1975 was instrumental a few days ago in pointing out my then current version of ndiswrapper v.1.57 wasn't compatible with 12.04. I deleted 1.57 and installed 1.58. The previous problems with 1.57 disappeared and I was able to install the recommended drivers, neti2220. See this:
The blog link describes a process of activating the device and driver that has not been successful on my machine.
It looks like my wireless card is not seeing the modem.

Thanks aardvark71 for your research and effort. I continue to be impressed with help available at one's finger tips!

The drivers suggested on your pages are the same InProComm driver that I am using. The process of configuration using <iwconfig> is compatible only with wep security type modems. My modem is wpa security type. This obliges me to use either checkbox with gnome to configure network-manager (ref: askubuntu.com/questions/16584/...), or alternatively, to use wpa_supplicant (ref: askubuntu.com/questions/138472/...) to do the job. I tried both.

The checkbox genome method uses this command: sudo user/share/checkbox/scripts/create_connection -S [SECURITY_TYPE] -K [password] [SSID]. Plugging in the values for my system produces the following result:
Connection rafaswifi registered
Error: Connection activation failed
Failed to activate rafaswifi
I searched the error, "connection activation failed," and found many posts all dealing with virtual machines and problems stemming from password related issues. I did not see anything applicable to my simple problem.

Some people had reported problems using the checkbox-gnome method. I moved to the wpa_supplicant method hoping for a better result.

The wpa_supplicant method uses this command: sudo wpa_passphrase rafaswifi idontenter > /etc/network/wpa.conf. This command had to be run as root at the terminal. The output from the pass_phrase command was silent, indicating a successful action. I entered the following:
To see if the device was communicating with the modem, I entered:
rafael@RafasTravelMate:/var/log$ sudo iwlist wlan0 s
password for rafael:
wlan0 No scan results

Out of desperation I pressed ahead despite this negative result to the next step in the wpa_supplicant process:
So that's where I'm at.
Why can't I pick up the router on a scan?
Thanks for any help.

I have to get on another learning curve here. I cannot kill the wpa_supplicant process. I issue the following commands: kill [PID], or kill -1 [PID], or kill -15 [PID], or killall [PID], and every time the process wpa_supplicant only changes its PID, it does not stop (according to ps -A output.)??

If I can't kill this process, then I cannot initiate a new attempt using different parameters. I found a site that says the drivers choice in wpa_supplicant, "wext", has been deleted and in its place one must use nl80211. I want to try this parameter but cannot until I kill the currently running process. Re-boot did not end the process.

The culprit is likely the Broadcom chipset. You shouldn't need ndiswrapper for that. See this post:

http://www.linuxquestions.org/questi...ux-4175434970/

The wireless chipset is not broadcom, it is InProComm. Output from lshw -C network:
The driver appears to be successfully installed.

Here is more information for someone who understands the language of scripts. To connect to a wpa router with network-manager from terminal (askubuntu.com/questions/16584/...) use the following command:
<sudo usr/share/checkbox/scripts/create_connection -S [SECURITY_TYPE] -K [PASSWORD] [SSID_NAME]>. For my computer security type = wpa; password = idontenter; ssid name = rafaswifi. Therefore:

Therefore:
<sudo usr/share/checkbox/scripts/create_connection -S wpa -K idontenter rafaswifi>
gives a print-out:
"Connection rafaswifi registered
Error: Connection activation failed
Failed activate rafaswifi

The new file "create_connection" may contain the information needed to bring this to a conclusion (I hope!) :-)
Enter the command:
<cd /usr/share/checkbox/scripts>

Followed by:
rafael@RafasTravelMate:/usr/share/checkbox/scripts$ cat create_connection
#!/usr/bin/env python

import sys
import os
import time

from subprocess import Popen, PIPE
from uuid import uuid4
from optparse import OptionParser

CONNECTIONS_PATH='/etc/NetworkManager/system-connections/'

def connection_section(ssid, uuid):

if not uuid: uuid = uuid4()

connection = """
[connection]
id=s
uuid=%s
type=802-11-wireless
""" % (ssid, uuid)

wireless = """
[802-11-wireless]
ssid=%s
mode=infrastructure""" % (ssid)

return connection + wireless

def security_section(security, key):
# Add security field to 802-11-wireless section
wireless_security = """
security=802-11-wireless-security

[802-11-wireless-security]
"""

if security.lower() == 'wpa':
wireless_security += """
key-mgmt=wpa-psk
auth-alg=open
psk=%s
""" % key

elif security.lower() == 'wep':
wireless_security += """
key-mgmt=none
wep-key=%s
""" % key

return wireless_security

def ip_sections():
ip = """
[ipv4]
method=auto

[ipv6]
method=auto
"""

return ip

def block_until_created(connection, retries, interval):

while retries > 0:
nmcli_con_list = Popen(['nmcli','con','list'], stdout=PIPE)
(stdout, stderr) = nmcli_con_list.communicate()

if connection in stdout:
print("Connection %s registered" % connection)
break

time.sleep(interval)
retries = retries - 1

if retries <= 0:
print("Failed to register %s." % connection)
sys.exit(1)
else:
nmcli_con_up = Popen(['nmcli','con','up','id', connection], stdout=PIPE)
(stdout, stderr) = nmcli_con_up.communicate()

if 'state: activated' in stdout:
print("Connection %s activated." % connection)
else:
print("Failed to activate %s." % connection)
sys.exit(1)


def main():
parser = OptionParser()

parser.add_option('-S', '--security',
help="""The type of security to be used by the connection.
One of wpa and wep. No security will be used if
nothing is specified.""")
parser.add_option('-K', '--key',
help="The encryption key required by the router.")
parser.add_option('-U', '--uuid',
help="""The uuid to assign to the connection for use by
NetworkManager. One will be generated if not
specified here.""")
parser.add_option('-R', '--retries',
help="""The number of times to attempt bringing up the
connection until it is confirmed as active.""",
default=5)
parser.add_option('-I', '--interval',
help="""The time to wait between attempts to detect the
registration of the connection.""",
default=2)

(options, args) = parser.parse_args()

if len(args) < 1:
print("Must specify an SSID to connect to.")
sys.exit(1)

connection_info = connection_section(args[0], options.uuid)

if options.security:
# Set security options
if not options.key:
print "You need to specify a key using --key if using wireless security."
sys.exit(1)

connection_info += security_section(options.security, options.key)
elif options.key:
print "You specified an encryption key but did not give a security type using --security."
sys.exit(1)

connection_info += ip_sections()

try:
connection_file = open(CONNECTIONS_PATH + args[0], 'w')
connection_file.write(connection_info)
os.fchmod(connection_file.fileno(), 0600)
connection_file.close()
except IOError:
print "Can't write to " + CONNECTIONS_PATH + args[0] + ". Is this command being run as root?"
sys.exit(1)

block_until_created(args[0], options.retries, options.interval)

if __name__ == "__main__":
main()

With this information, can anyone see what may be going wrong?

This thread is leading nowhere and my frustration with the process has reached a limit. I will take aarvark71's advice and purchase an external device. I am disappointed that ubuntu has such an arcane process for simply connecting to a wireless network. My computer has no PAE capacity, so I am limited to 12.04-nonPAE-beta. I cannot test newer versions of ubuntu. I do hope that this issue has been resolved if only for the sake of world-wide users of ubuntu linux. I will mark the thread as solved not because it has been solved, but because I will purchase an external device.

Hi...

I'm sorry you couldn't get it to work. Wireless on Linux can still be difficult because of the continuing issue with drivers.

Let us know how the external adapter works...

Regards...