I got info you wanted into black box. How do I transfer it to post? It wont copy and paste..Do I need to cut and paste? If so don't know how CB

I assume by the "black box", you are referring to the "terminal", or "console" or whatever it's called in the windows world? If I recall correctly it's a pain in the **** to do this in windows as you have to select "mark" then "copy" from the menu.

Code:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Raymond solema>ipconfig/all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : COMPZILLA
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : domain_not_set.invalid

Wireless LAN adapter Wireless Network Connection 9:

   Connection-specific DNS Suffix  . : domain_not_set.invalid
   Description . . . . . . . . . . . : NETGEAR WNA1100 Wireless-N 150 USB Adapte
r
   Physical Address. . . . . . . . . : 30-46-9A-23-75-0A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::c116:2909:b005:f98b%31(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.68(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, February 01, 2011 5:58:08 PM
   Lease Expires . . . . . . . . . . : Wednesday, February 02, 2011 5:58:08 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 607143578
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-BE-3F-0D-70-71-BC-5D-9D-78

   DNS Servers . . . . . . . . . . . : 192.168.1.1
                                       68.238.64.12
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.domain_not_set.invalid:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::3030:ee6:b59b:a664%33(Preferred)
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 570425344
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-BE-3F-0D-70-71-BC-5D-9D-78

   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Reusable ISATAP Interface {8FF5AACF-7F5F-4055-8520-3814E38B1885}:


   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : domain_not_set.invalid
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Sure hope this helps the situation CB

Thanks. Sorry I didn't know how to send it .I wasted a lot of your time. CB

I thought it was supposed to show up. I know it's at least somewhat recognized
. I have an icon for it in the task bar by the clock
I'll try the reinstall. But wont be able to get to it until tomorrow. should I disable my Netgear before I start? So Ubuntu wont find it right off and stop searching for the other?

New ones already hooked up.Has been since I reinstalled it a while back. Iv'e got a good feeling about this. Let you know how it turns out tomorrow CB


Well it's Wed. evening. Reinstalling Ubuntu didn't work.I even made a brand new boot cd,and this one installed Ubuntu a lot more completely than the first one. (actually I didn't know the first install wasn't complete,until I saw all the things this install included.) When I saw it going through it's configuring hardware phase I thought sure it had found the wireless card No such luck.,

Now I have my choice of 2 Umbuntu's both of which are useless. Maybe I jinxed it when I said " I had a good feeling."

If you have run out of ideas and just want to forget it . I understand. But if you still have other ideas I'm willing to try

As I said earlier in thread: you will need to install over a wired connection. It's likely that your wireless needs proprietary firmware. You can easily fetch this from the repos once everything is installed.

There are other distributions which you can try that ship with the proprietary firmware included. I believe Linux Mint ships with some of this firmware on the installation media. Personally though I think installing over a wired connection is still the best option.

Like I said in a much earlier post.It would be next to impossible for me to run a wire from my PC to the router.in the living room.It would have to go all the way down the hall and across the living room rug.That's an awful lot of wire,or I guess I should say cable.,and I'm sure it's not cheap.If I tried to hide the cable by running it down one side of the hall,and up and over the bedroom doors it would even cost more,and if I ran it around the walls in the living room.Instead of straight across that would be close to the length of the hall again..
What exactly is proprietary firmware? Is that something that would help me make a wireless connection with the wireless card I'm using now.Or would it be a completely new piece of equipment? CB

You only need the wired connection for the initial install. So why not "take Mahomet to the mountain"? Once that's done, the wireless NIC and firmware installed you can take it back.

Firmware may be required for some of your hardware devices to work correctly,

To find out for sure you would need to physically install your wireless devices, boot up a live session (boot up 'buntu from the livecd) and then run these two commands from the terminal and post the output here:

Code:

lspci
lsusb

So I would hook it up wired.Let the computer recognize the wireless card.then when I set it up wireless again the computer would still recognize the card. Right?

If it doesn't recognize the wireless card while hooked up wired.I would run the commands from the terminal. To see if it's a firmware problem.Right?

If it still doesn't work after using the firmware. I'm probably looking at a faulty Wireless card. Right?

O.K. Thanks. I wont badger you and Leeky any more until after I've tried the wired hook up.Unless I need to ask some questions about the firmware. CB

Putting in a permanent wired connection is ideal as per leeky's suggestion, though it's not needed. You should be able to get away with taking your PC to the same room as the router and connecting it up with a 2 metre drop cable (a length of Cat 5E stranded with connectors at each end).

Once connected you can install Linux, connect to the repos, update, fetch the firmware get the wireless working and then take the PC back to the room it belongs in.

I had a different problem with Ubuntu Maverick. My ethernet connection worked just fine before upgrading. Then I had to reboot my PC multiple times to make Internet work. But it seems everything is fine after installing the latest updates.

When using wireless DSL you really need to make sure that there are Linux drivers.

I would try to ask here
forums.verizon.com/

I know i said I wouldn't badger you and Leeky until after I tried the Wired connection.
But I need to ask a question. Please look at Stream Recorders post .
Do I need to check and see if I need to download any drivers?

Oh by the way I went to a site that showed all wireless cards that are compatible with Ubuntu.Mine is one of them.
I'd hate to go through all this just to find out my wireless card wouldn't work anyway.

Did you do this:

?