Hi,

I used to run ubuntu 5.10 and my wireless card is a 3 com card which is natively supported by Ubuntu.

I upgraded to dapper drake 6.06, and now I cannot connect wirelessly.

I can find my router and try to establish a connection using network manager, but it will not connect and assign an ip address.
It shows no signal strength, though I am next to the router and everything is plugged in an on.
The card works and is recognised, although I took the precaution of installing the atmel source driver and the firmware as recommended on the ubuntu forum (it's an atmel card)

I am completely stuck and have tried several commands I have seen in the official ubuntu forum, as well as trawling this one. But still no luck.

I'm really annoyed because as usual, everything works fine under Windows 2K

Can anyone help me or point me in the right direction?

Thanks in advance


Tom

Well I've looked on google and various other threads, one which was dealing with a very similar card to the one I am using.

I am using the 3 Com 3CRSHPW196 Wireless LAN PC Card

Here is what I have tried and failed:

Using wifi-radar:

Error for wireless request "Set Nickname" (8B1C) :
SET failed on device eth1 ; Operation not supported.
eth1 Failed to read scan data : Resource temporarily unavailable

??

tc10b@tc10b-175-175:~$ sudo ifconfig eth1 up
tc10b@tc10b-175-175:~$ sudo dhclient eth1
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.

Listening on LPF/eth1/00:04:75:9a:3d:51
Sending on LPF/eth1/00:04:75:9a:3d:51
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

tc10b@tc10b-175-175:~$ sudo iwconfig eth1 essid linksys
tc10b@tc10b-175-175:~$ sudo iwconfig eth1 mode managed
tc10b@tc10b-175-175:~$ sudo dhcpcd -t 10 -d eth1
dhcpcd: MAC address = 00:04:75:9a:3d:51

(at this point the card light comes on, which means the card is down)

tc10b@tc10b-175-175:~$ sudo ifconfig eth1 up

tc10b@tc10b-175-175:~$ sudo dhcpcd eth1 linksys

This just hangs the system for about a minute and then switches the light on the card on, which is rather odd as it means the card has been unloaded.

I'm going to try and compile the drivers again to see if that makes a difference

tc10b@tc10b-175-175:~$ cardctl ident
Socket 0:
product info: "3Com", "3CRSHPW_96 Wireless LAN PC Card"
manfid: 0x0101, 0x0696
function: 6 (network)
Socket 1:
no product info available

So it's already recognising it correctly.

OK I reinstalled the latest drivers, and still no luck:

tc10b@tc10b-175-175:~/Downloads/atmelwlandriver$ sudo make install
pcmcia directory already exists
usb directory already exists
pci directory already exists
bin directory already exists
x11r6 bin directory already exists
Run #depmod -aeq after installation.
OK
tc10b@tc10b-175-175:~/Downloads/atmelwlandriver$ sudo depmod -aeq

Now when I run dmesg, it reads it as an atmel card and not as a 3com card:

[17184059.696000] pccard: card ejected from slot 0
[17184063.896000] pccard: PCMCIA card inserted into slot 0
[17184063.896000] pcmcia: registering new device pcmcia0.0
[17184064.472000] eth1: Atmel at76c50x. Version 0.98. MAC 00:04:75:9a:3d:51
[17184064.928000] ADDRCONF(NETDEV_UP): eth1: link is not ready

I don't know what the last line means, can anyone shed some light?

tc10b@tc10b-175-175:~$ ifconfig
eth0 ommitted

eth1 Link encap:Ethernet HWaddr 00:04:75:9A:3D:51
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:11 errors:1 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:660 (660.0 b) TX bytes:0 (0.0 b)
Interrupt:3 Base address:0x2100

tc10b@tc10b-175-175:~$ iwconfig

eth1 IEEE 802.11-DS ESSID:"linksys"
Mode:Managed Frequency:2.437 GHz Access Point: 00:06:25:78:63:0F
Bit Rate:11 Mb/s
Retry min limit:7 RTS thrff Fragment thrff
Power Managementff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I'm now completely lost, and at my wits end I have a reliable wired connection but I would like to go wireless.

If anyone can help it would be very much appreciated.

You may indeed be having a problem with something in the DHCP request. One way to test this theory would be to set the this interface to a static address that is in the same IP address range being serviced by the wireless router.

Look for (/etc/network/interfaces), here you should have a section 'eth1', in this section you will want to enter values similar to:

auto eth0
iface eth0 inet static
address 192.168.0.92
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.0.1

---
Note I chose an IP address of '192.168.0.92' because it is unlikely to conflict with any other device on your network. Also you may need to verify that your network is currently 192.168.0.*, if not you will need to make the necessary changes.

If with these settings you are able to connect to your network, then you will have verified that you do have a problem with DHCP. You will then have to decide if you are willing to just move forward with your static address or do you have the need to hunt down and resolve the DHCP problem.

Happy Hunting!

Hi, I tried the static address and it seemed to not make a difference.

However, strangely though I encrypted the connection using WEP and DHCP, then tried to connect and now surprisingly I have a full signal bar and can ping the network, unfortunately though I can't go online with it. Which is annoying but at least I seem to be one step closer.

I would like to thank you for your help kvedaa, and anyone else who can help me to get a fully working wireless connection.

Thanks.


Tom

OK,

It is a good sign that you can ping other devices on your local network. That tells us that the basic functionality is in place.

Remember that for a static address to be functional you will need to also set your default gateway and your DNS server address (so traffic knowns how to get out of you LAN and where to find IP address for the sites that you wish to visit, respectively). Also do not forget to set your subnet mask, so that the system knows what what is part of your network and what is the rest of the world.

Once you have these settings in place try to ping a site that is likely to be up and running, such as yahoo.

Two items are of interest in this test, the obvious one being do you get a response to the ping, which would tell us that you can get out of your network successfully. Another point of interest is did the name resolve to an IP address? If not then you are not getting an answer back from DNS on the domain name.

If you did not have success in resolve the name, try instead to ping an external IP address, for instance:

ping 66.94.234.13

The IP address above is one that I recently received when resolving the name for yahoo.com. Depending on the results that are received here will help narrow down some of the options going forward.

Happy Hunting!

Hi,

This is strange, I tried to ping the address you suggested and it didn't work, now I can't ping anything

I don't really know how to adjust my DNS setting, it should be automatically finding a DNS.

I'd appreciate any further you can give me, and thanks for everything so far.


Tom

Well,

One likely possibility is that your systems effort to receive a dynamic address (via DHCP) may not be working as it should.

From a command line, you can run the command:

ifconfig

This should provide you the current configuration for you installed interfaces. You should be able to check to ensure that the address that your primary interface is using an address that is in the range that your router is communicating with. If you are not familiar with what I am talking about, go ahead and post the values and we can discuss it further.

If my hunch is correct, and you are not getting valid information via DHCP, then one option is to manually configure the interface with information that will allow your system to communicate on your network.

A general example of how you can manually configure the IP address, as well as the default gateway, and the DNS servers, I would suggest that you take a look at the following page:

http://www.cyberciti.biz/tips/howto-...iguration.html

Happy Hunting!

Hi, sorry for the long delay. I've been incredibly busy at work.

Here is the output when I do if config. Oddly now I can no longer see the signal strength again.

tc10b@tc10b-175-175:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 000:598:F8:18
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::2d0:59ff:fed8:f818/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6776 errors:0 dropped:0 overruns:0 frame:0
TX packets:4307 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8290536 (7.9 MiB) TX bytes:414172 (404.4 KiB)

eth1 Link encap:Ethernet HWaddr 00:04:75:9A:3D:51
inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:3 Base address:0x2100

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:456 (456.0 b) TX bytes:456 (456.0 b)

Argh, it seems now I'm back at step one, as I now can't get anything out of eth1.

Hi,

I went through and tried everything on that site that you mentioned and it doesn't make a difference.
I dunno what's happened but when I use the DHCP client now it doesn't even try to use eth1 by default. I have to make it do it manually.
I really want to get this to work, but everytime I seem to get closer I end up back at square one.

Thanks for the help so far kvedaa

Tom

I've managed to somehow get back what I had before.

OK, so now I have a full signal bar when I use my wireless card and a static IP address.
I can live with this provided it works, however it won't send or recieve data from the router so I can't ping anything or go online.
I dunno how I can fix this, I tried deleting the DNS servers as restarting as mentioned on the website above, but to no avail.

Any help would be gratefully recieved.

Cheers

Tom

what happens if you disable eth0 and then bring up eth1?

When I do that, I can't ping anything or use the internet not even to access the routers own HTML page.