netopia usb wireless card

mp22

I have a p4 desktop running on ubuntu 9. I can connect to my eircom router using a cable.Got my hands on a usb wireless card and i cannot get it set up
any advice would be much appreciated
thanks

bman

Any idea what model the card is?

Run

sudo tail -f /var/log/syslog

from a terminal and plug in your card. Once it finishes outputting stuff copy and paste that up here for us to take a look.

mp22

Wireless usb card model TER/GUS-E P/N 8961185-00-01
FCC ID RC6AWU-902W
is this what your after? I wont be at the ubuntu pc till later ill run the code then. ta

bman

mp22 wrote: »

Wireless usb card model TER/GUS-E P/N 8961185-00-01
FCC ID RC6AWU-902W
is this what your after? I wont be at the ubuntu pc till later ill run the code then. ta

I'd say you're missing a 'B' in the above, i.e. TER/GUSB-E.

Anyways, this is likely a Ralink card. Shouldn't have too much bother getting it going.

When you get a chance try my suggestion re /var/log/syslog.

mp22

your spot on B it is
dad@dad-desktop:~$ sudo tail -f /var/log/syslog
[sudo] password for dad:
Sep 11 20:17:25 dad-desktop avahi-daemon[2630]: New relevant interface eth0.IPv4 for mDNS.
Sep 11 20:17:25 dad-desktop avahi-daemon[2630]: Registering new address record for 192.168.1.13 on eth0.IPv4.
Sep 11 20:17:25 dad-desktop dhclient: bound to 192.168.1.13 -- renewal in 1721 seconds.
Sep 11 20:17:26 dad-desktop NetworkManager: <info> (eth0): device state change: 7 -> 8
Sep 11 20:17:26 dad-desktop NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
Sep 11 20:17:26 dad-desktop NetworkManager: <info> Activation (eth0) successful, device activated.
Sep 11 20:17:26 dad-desktop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Sep 11 20:17:26 dad-desktop avahi-daemon[2630]: Registering new address record for fe80::201:6cff:fea0:aa43 on eth0.*.
Sep 11 20:17:12 dad-desktop ntpdate[3296]: step time server 91.189.94.4 offset -14.175148 sec
Sep 11 20:17:21 dad-desktop kernel: [ 69.460018] eth0: no IPv6 routers present




results with card plugged in before code was run

bman

mp22 wrote: »

your spot on B it is
dad@dad-desktop:~$ sudo tail -f /var/log/syslog
[sudo] password for dad:
Sep 11 20:17:25 dad-desktop avahi-daemon[2630]: New relevant interface eth0.IPv4 for mDNS.
Sep 11 20:17:25 dad-desktop avahi-daemon[2630]: Registering new address record for 192.168.1.13 on eth0.IPv4.
Sep 11 20:17:25 dad-desktop dhclient: bound to 192.168.1.13 -- renewal in 1721 seconds.
Sep 11 20:17:26 dad-desktop NetworkManager: <info> (eth0): device state change: 7 -> 8
Sep 11 20:17:26 dad-desktop NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
Sep 11 20:17:26 dad-desktop NetworkManager: <info> Activation (eth0) successful, device activated.
Sep 11 20:17:26 dad-desktop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Sep 11 20:17:26 dad-desktop avahi-daemon[2630]: Registering new address record for fe80::201:6cff:fea0:aa43 on eth0.*.
Sep 11 20:17:12 dad-desktop ntpdate[3296]: step time server 91.189.94.4 offset -14.175148 sec
Sep 11 20:17:21 dad-desktop kernel: [ 69.460018] eth0: no IPv6 routers present




results with card plugged in before code was run

Okay, is this with your network cable plugged in or not? You've got an IP address from your router but the interface is called eth0 which usually means wired rather than wireless.

So ensure your network cable is unplugged. Run

tail -f /var/log/syslog

in a terminal. Plug in your wireless card. Give it about 10 seconds and post the output up here.

Also, with the card plugged in, run

ifconfig

in a terminal and post that up. And

iwconfig

mp22

dad@dad-desktop:~$ tail -f /var/log/syslog
Sep 12 10:28:47 dad-desktop NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready
Sep 12 10:28:48 dad-desktop nm-system-settings: Added default wired connection 'Auto eth0' for /org/freedesktop/Hal/devices/net_00_01_6c_a0_aa_43
Sep 12 10:30:01 dad-desktop console-kit-daemon[2404]: WARNING: Couldn't read /proc/2403/environ: Failed to open file '/proc/2403/environ': No such file or directory
Sep 12 10:30:01 dad-desktop /USR/SBIN/CRON[2938]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
Sep 12 10:33:44 dad-desktop anacron[2769]: Job `cron.daily' started
Sep 12 10:33:44 dad-desktop anacron[3101]: Updated timestamp for job `cron.daily' to 2009-09-12
Sep 12 10:34:55 dad-desktop pulseaudio[3203]: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 48000 Hz.
Sep 12 10:34:55 dad-desktop pulseaudio[3203]: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 48000 Hz.
Sep 12 10:35:02 dad-desktop pulseaudio[3203]: module-x11-xsmp.c: X11 session manager not running.
Sep 12 10:35:02 dad-desktop pulseaudio[3203]: module.c: Failed to load module "module-x11-xsmp" (argument: ""): initialization failed.




dad@dad-desktop:~$ ipconfig
bash: ipconfig: command not found
dad@dad-desktop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:01:6c:a0:aa:43
UP BROADCAST RUNNING 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 TX bytes:0 (0.0
Interrupt:19 Base address:0xe800

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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:440 (440.0 TX bytes:440 (440.0

wlan0 Link encap:Ethernet HWaddr 00:d0:41:a6:34:76
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

dad@dad-desktop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=20 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
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

pan0 no wireless extensions.

dad@dad-desktop:~$

bman

You're almost there. Card is recognized and initialised fine from what I can see.

From one of your previous logs you seem to be using NetworkManager. Check your Panel for the NetworkManager icon (if on Ubuntu then top right corner). It'll show a network icon of two monitors or a monitor with an 'X' through it (iirc). Click there, see if you can configure your card to connect to your router.

mp22

thanks for your help so far I have got to the stage of beening asked for password for a network manager thing see attached screen shot my wep key is entered allready

bman

mp22 wrote: »

thanks for your help so far I have got to the stage of beening asked for password for a network manager thing see attached screen shot my wep key is entered allready

The keyring password is not the same as your WEP key. It's like an extra security mechanism. You would have set up a password for it the first time it was invoked, and now it's looking for the same password again.

The keyring password service is pretty annoying and I usually just disable it.

System -> Preferences -> Startup Applications -> Startup Programs Tab
Uncheck "GNOME Keyring Daemon"
Close.

Restart your X server (= log out & log back in).

Try reconnecting to your wireless.

mp22

tried to disable that keyring service not going according to plan!
found this for the keyring password http://davestechsupport.com/blog/2009/01/16/how-to-remove-ubuntus-password-keyring/
no wireless signal now!!!
thanks again

bman

No problem.

Okay. So after you've tried configuring and connecting to your network, try ifconfig and iwconfig again and paste it here.

Is your wireless network even visible in the NetworkManger?

mp22

no sign of it in the network manager
sorted I cleaned my reading glasses and entered the correct wep key and were sucking diesel:o

bman

mp22 wrote: »

no sign of it in the network manager
sorted I cleaned my reading glasses and entered the correct wep key and were sucking diesel:o

Haha. Often the simplest and easiest path is the correct one!

Support for wireless cards and Network Manager have improved an huge amount in the past few years. Unless it's very new hardware you usually won't have any issues getting it going.

Good luck with your OS.

An Fear Aniar

mp22 wrote: »

no sign of it in the network manager
sorted I cleaned my reading glasses and entered the correct wep key and were sucking diesel:o

That's funny.:) Been there, done that myself!

.