hi again,

Still no good news.

1) the process of installing the drive and then copying the files is the one described by Emanuel_UK and I cannot see other way of making it work because the drivers and the inf files come from different sources.

2) unistall everything, rename all the files to small caps and re run all steps still get the same error when running modprobe... As you can see in my previous posts, before i manage to get the card to be recoginized now not even that

if you have any other suggestion on what to do or any other way of trying to make this thing work, i am up for anything... just desperate to get internet on my linux machine.

Thanks for the time you are wasting on this

Cheers,

PA

Um, uh. Please forgive me if this is offensive, but....Huh?

I honestly don't get what you mean here. And if it means what it appears to mean, this could be the source of much trouble. The .inf and .sys files you use should (must?) come out of the same .zip or .exe archive file. Any light you could shed on this would be appreciated.
You're welcome. And just so you know, I never consider time spent helping at LQ to be wasted as I almost always learn something. In this particular thread, you pointed me to Emanuel_UK's site, which is a very fine howto I didn't know about before.

Ok,

Remember I am really new to Linux

I am following step by step the how to from Emanuel_UK in http://www.linuxquestions.org/questi...d.php?t=356315 post #13. and he followed the instructions from wiki

____________________________________________________
Card: Linksys #[WUSB54GSv2], 802.11b/g, USB 2.0 -- [link here|List#WUSB54GS]
Chipset: Broadcom - BCM4320SKFBG
usbid: 13b1:0014
Driver: You can install this driver by either of the following two methods.
Method1: The driver for this RNDIS card doesn't include two .sys files required (usb8023k.sys and rndismpk.sys or usb8023x.sys and rndismpx.sys), as they are part of Windows installation and don't need to be installed in Windows. However, other drivers for different cards based on RNDIS include these .sys files. One is Belkin F5D7051uk at [47]. You can install this driver with BCMRNDIS.INF, which installs the required .sys files. You then need to inform ndiswrapper that this driver, bcmrndis, should be used for usbid of WUSB54GSv2 (13b1:0014), by executing 'ndiswrapper -d 13b1:0014 bcmrndis'
Method2: Used the inf file from the CD, and the .SYS files from usr5420 available at www.usr.com http://www.usr-emea.com/support/s-pr...unkg&prod=5420. Used snapshot from 13/02/2006, along with the usr system files that i had to install on a windows machine to extract. Then copied the wusb54gs.inf and wusb54gsv2.inf to the folder with the sys files - the wusb54gs.inf worked seamlessly with my device on the snapshot.!
____________________________________________________

I just notice something that might be the problem. Emanuel_UK used ndiswrapper 14 and I downloaded it from the sourceforge website. but with ndiswrapper -v he gets

utils version: 1.8
driver version: 1.14 <<<<<<----------
vermagic: 2.6.11-6mdk 586 gcc-3.4

and as you can see in step 11 of my log I get

utils version: 1.8
driver version: 1.2 <<<<<----------
vermagic: 2.6.13-15-smp SMP 586 REGPARM gcc-4.0

Emanuel_UK if you read this post, where in the UK are you Maybe I can buy you a pint for you help!! )) I am at Lancaster

Thanks again.

These are the right size file. So 100% OK

The inf is from linksys. The sys from somewhere else, because 1) sys not available with linksys,
2) these sys I understand are Zindows, necessary files, 3) this the wiki advocated solution

eagleeyes,
you did not do the make uninstall for ndiswrapper

You might be using a smp kernel. I do not think you should, although, I believe
it should work ok on a single processor.

I have # ndiswrapper -v
utils version: 1.8
driver version: 1.14

Why do you have 1.2?

This is not necessary, keep the capitalisation as it is originally. ndis will recap as needed
(I found out from trial and errors)

correct about capitalisation in linux, it is actually mixed capitalisation here.
Just leave it as it is. I thought it could be a problem, but it is not here.

Modprobe error
Ok we saw utils 1.2 which is strange already. Where is the tarball from?
Redo everything from make uninstall, then delete /etc/ndiswrapper, then do the make

try modprobe -f --force

eagleeyes, thanks for your perseverance
Please nag linksys when you are finished

Good news!!!! and bad news

I followed your instructions did everything and for the first time I manage the card to show some activity, got an mac address and netwrok identified. everything look fine all detail would appear with a iwconfig... This is promising...

but then...

1) still no internet connection, I would start firefox and no connection

2) i decided to reboot the machine when shutting down the computer freeze and now if I do iwconfig the wlan0 doesn't even appear in the list. although if i do ndiswrapper -l the drivers are still installed.

so I think I was pretty pretty close, but...

BTW, I am nagging Linksys so hard that they stop replying to my emails

to have ndiswrapper added to the boot i.e to be loaded automatically
ndiswrapper -m
-m Write configuration for modprobe
then
depmod -a

Not a surprise. You still have to configure wep, the route maybe as well (see route -n),
even maybe the receiver

Once more post what you are trying.
I know little of suse wifi config tools

For the sake of knowing that the hardware is now fine post the syslog entry
after modprobe ndiswrapper
and the output of iwconfig (remove ESSID if private and the hexakey as well).

I would start config with wep 64 or 128

On my pc, 1 needed one reboot for the network to be discovered. This is
unusual. Try
service network restart

I trust you have the right ifcfg-wlan0 configured (that is IP address, dhcp if needed, ESSID and the rest)

I want to believe that I am almost there

There is activity in the card and the router already detected the card apparently.

Still cannot access internet.

here is some logs

1) the log when running YAST to configure the card:
Jun 4 13:39:01 linux gconfd (alves-11564): starting (version 2.12.0), pid 11564 user 'alves'
Jun 4 13:39:01 linux gconfd (alves-11564): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jun 4 13:39:01 linux gconfd (alves-11564): Resolved address "xml:readwrite:/home/alves/.gconf" to a writable configuration source at position 1
Jun 4 13:39:01 linux gconfd (alves-11564): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jun 4 13:41:24 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Jun 4 13:41:24 linux SuSEfirewall2: batch committing...
Jun 4 13:41:25 linux SuSEfirewall2: Firewall rules unloaded.
Jun 4 13:41:25 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Jun 4 13:41:25 linux SuSEfirewall2: batch committing...
Jun 4 13:41:25 linux SuSEfirewall2: Firewall rules set to CLOSE.
Jun 4 13:41:25 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Jun 4 13:41:25 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Jun 4 13:41:25 linux SuSEfirewall2: batch committing...
Jun 4 13:41:25 linux SuSEfirewall2: Firewall rules successfully set
Jun 4 13:41:26 linux dhcpcd[10961]: terminating on signal 15
Jun 4 13:41:26 linux dhcpcd-hook: Skipping 'ifdown $INTERFACE -o dhcp' call
Jun 4 13:41:27 linux dhcpcd[11097]: terminating on signal 15
Jun 4 13:41:27 linux dhcpcd-hook: Skipping 'ifdown $INTERFACE -o dhcp' call
Jun 4 13:41:38 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Jun 4 13:41:38 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Jun 4 13:41:38 linux SuSEfirewall2: batch committing...
Jun 4 13:41:38 linux SuSEfirewall2: Firewall rules successfully set
Jun 4 13:41:38 linux kernel: eth0: no IPv6 routers present
Jun 4 13:41:43 linux kernel: wlan0: no IPv6 routers present
Jun 4 13:42:01 linux gconfd (alves-11564): GConf server is not in use, shutting down.
Jun 4 13:42:01 linux gconfd (alves-11564): Exiting


2) The log of an ifup wlan0

linux:~ # ifup wlan0
wlan0
DHCP client is already running on wlan0


3) the log of an iwconfig
linux:~ # iwconfig
lo no wireless extensions.

sit0 no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"BTVOYAGER2110-99" Nickname:"linux"
Mode:Managed Frequency:2.462 GHz Access Point: 00:11:F5:C1:17:99
Bit Rate=54 Mb/s Tx-Power:25 dBm
RTS thr=2347 B Fragment thr=2346 B
Encryption key:A135-ACC3-024A-D3BF-61A6-F7FB-BC Security modepen
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

4) the log of an ifconfig

linux:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:76:50:C0:B6
inet6 addr: fe80::216:76ff:fe50:c0b6/64 Scope:Link
UP BROADCAST NOTRAILERS 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)
Base address:0x1000 Memory:70000000-70020000

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:284 errors:0 dropped:0 overruns:0 frame:0
TX packets:284 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:21106 (20.6 Kb) TX bytes:21106 (20.6 Kb)

wlan0 Link encap:Ethernet HWaddr 00:16:B6:5B:50:6A
inet6 addr: fe80::216:b6ff:fe5b:506a/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:20014 (19.5 Kb)

5) modprobe ndiswrapper is not producing any log at all.

6) my ifcfg-wlan0

BOOTPROTO='dhcp'
BROADCAST=''
IPADDR=''
MTU=''
NAME='Ethernet Network Card'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
WIRELESS_AP=''
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_ESSID='BTVOYAGER2110-99'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0='h:5t5968nr56qrc'
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_POWER='yes'
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK=''
_nm_name='static-0'


Please tell me I am getting there

WIRELESS_KEY_0='h:5t5968nr56qrc'
WIRELESS_KEY_LENGTH='128'

I think WIRELESS_KEY_0 should have the value of Encryption key:A135-ACC3-024A-D3BF-61A6-F7FB-BC
and you should not publish it BTW

inet6 addr: fe80::216:b6ff:fe5b:506a/64 Scope:Link
should look like
inet addr:192.168.x.y Bcast:192.168.x.255 Mask:255.255.255.0

See if yast got some configuration menus for wlan0

Am not sure what you are missing

The keys are the same just one is a passphrase another the hexa equivalent. try to pu the hexa anf i got exactly the same results...

i can get something like
inet addr:192.168.x.y Bcast:192.168.x.255 Mask:255.255.255.0

but only if I make a static IP and still cannot access the web.

But as I said there is activity in the card and the router recognized it.

I think now is not a drivers problem anymore, just some silly mistake that my Linux lack of knowledge cannot find

Any suggestion?

Here is an experiment to try. Assign the static IP with ifconfig. Then, set your router to be the gateway:

route add default gw 192.168.x.y (use the router IP address)

Finally, add a DNS server or two to your /etc/resolv.conf file. If you check your router, you should be able to find the IP addresses for the DNS servers. For each one add a line:

nameserver xxx.xxx.xxx.xxx


If that gets you up and running, it suggests problem with DHCP.

in the same vain as Hangdog42's suggestions (once you have done all Hangdog42 suggested)
other tests you can do
ping 127.0.0.1
also ping your router
ping ip address of site you know in the format xxx.yyy.xxx.zzz
and finally ping www.google.com or whatever else you know is not down

Maybe a syntax error. For example I have
WIRELESS_ENC_KEY="restricted somehexakey"

# cat /etc/sysconfig/network-scripts/ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=static
IPADDR=192.168.x.y
NETMASK=255.255.255.0
NETWORK=192.168.x.0
BROADCAST=192.168.x.255
ONBOOT=yes
#HWADDR=youcanputonehere
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes
MS_DNS1=192.168.x.y
WIRELESS_MODE=Managed
WIRELESS_ESSID=essidname
WIRELESS_ENC_KEY="restricted somehexakey"
IPV6INIT=no
IPV6TO4INIT=no
PEERDNS=no
GATEWAY=192.168.x.y

Ok, guys.

I do not know what to do.

the command
route add default gw 192.168.x.y (use the router IP address)
returns network is unreachable

the ping 127.0.0.1 works
the ping 192.168.1.1 returns network is unreachable

the link light in the card continues to blink everytime i send a command

I cannot get the DNS server IP addresses from the router, just has the option DNS SERVER automatic yes/no.

I am quite annoyed after all this work to get the card working

I am not good at this network config. But once more we need details.
Post for iwconfig wlan0 (once you have fixed its IP address)
route -n (before and after the route add command, just to double check)
Please also double check the wep key and ESSID

Also is eth0 in use and have you got a cat5 cable there?
Did you check the receiver is configured to listen on 192.168.1.1?

Try this (google for some other nameservers just in case) for resolv.conf
nameserver 193.252.19.3
nameserver 193.252.96.4

as well supply if it changed /etc/sysconfig/network-scripts/ifcfg-wlan0

When you ping the router 192.168.1.1 please double check syslog,
you neeed to ascertain you do not have a firewall issue on the PC or on the router

Guys I start to feel guilty of all this extra work...

ok,

1) I deleted the network card from yast.
linux:~ # iwconfig
lo no wireless extensions.

sit0 no wireless extensions.

eth0 no wireless extensions.

2) I add it back with a fixed IP
The log of adding it
Jun 5 09:47:54 linux kernel: ndiswrapper: module not supported by Novell, setting U taint flag.
Jun 5 09:47:54 linux kernel: ndiswrapper version 1.14 loaded (preempt=no,smp=yes)
Jun 5 09:47:54 linux kernel: ndiswrapper: driver wusb54gsv2 (Linksys,01/25/2005, 4.01.20.0) loaded
Jun 5 09:47:55 linux kernel: wlan0: vendor: 'Linksys Wireless-G USB Network Adapter with SpeedBooster'
Jun 5 09:47:55 linux kernel: wlan0: ndiswrapper ethernet device 00:16:b6:5b:50:6a using driver wusb54gsv2, 13B1:0014.F.conf
Jun 5 09:47:55 linux kernel: wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
Jun 5 09:47:55 linux kernel: usbcore: registered new driver ndiswrapper
Jun 5 09:47:56 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Jun 5 09:47:56 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Jun 5 09:47:56 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Jun 5 09:47:56 linux SuSEfirewall2: Another SuSEfirewall2 with PID 8505 found, waiting ...
Jun 5 09:47:56 linux SuSEfirewall2: batch committing...
Jun 5 09:47:56 linux SuSEfirewall2: Firewall rules successfully set
Jun 5 09:47:58 linux SuSEfirewall2: batch committing...
Jun 5 09:47:58 linux SuSEfirewall2: Firewall rules unloaded.
Jun 5 09:47:58 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Jun 5 09:47:58 linux SuSEfirewall2: batch committing...
Jun 5 09:47:58 linux SuSEfirewall2: Firewall rules set to CLOSE.
Jun 5 09:47:58 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Jun 5 09:47:58 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Jun 5 09:47:58 linux SuSEfirewall2: batch committing...
Jun 5 09:47:58 linux SuSEfirewall2: Firewall rules successfully set
Jun 5 09:48:00 linux dhcpcd[7769]: terminating on signal 15
Jun 5 09:48:00 linux dhcpcd-hook: Skipping 'ifdown $INTERFACE -o dhcp' call
Jun 5 09:48:05 linux SuSEfirewall2: Warning: ip6tables does not support state m
Jun 5 09:48:05 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfi
Jun 5 09:48:06 linux SuSEfirewall2: batch committing...
Jun 5 09:48:06 linux SuSEfirewall2: Firewall rules successfully set
Jun 5 09:48:06 linux kernel: wlan0: no IPv6 routers present
Jun 5 09:48:11 linux kernel: eth0: no IPv6 routers present

lo no wireless extensions.

sit0 no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"BTVOYAGER2110-99" Nickname:"linux"
Mode:Managed Frequency:2.462 GHz Access Point: 00:11:F5:C1:17:99
Bit Rate=54 Mb/s Tx-Power:25 dBm
RTS thr=2347 B Fragment thr=2346 B
Encryption key:A135-ACC3-024A-D3BF-61A6-F7FB-BC Security modepen
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

linux:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:76:50:C0:B6
inet6 addr: fe80::216:76ff:fe50:c0b6/64 Scope:Link
UP BROADCAST NOTRAILERS 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)
Base address:0x1000 Memory:70000000-70020000

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:55 errors:0 dropped:0 overruns:0 frame:0
TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3936 (3.8 Kb) TX bytes:3936 (3.8 Kb)

wlan0 Link encap:Ethernet HWaddr 00:16:B6:5B:50:6A
inet addr:192.168.1.25 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::216:b6ff:fe5b:506a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:2564 (2.5 Kb)


3) run the route -n
linux:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo

4) add the gateway
linux:~ # route add default gw 192.168.1.1
linux:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0

5) Ping the 169.254.0.1
linux:~ # ping 169.254.0.1
PING 169.254.0.1 (169.254.0.1) 56(84) bytes of data.
From 192.168.1.25: icmp_seq=2 Destination Host Unreachable
From 192.168.1.25 icmp_seq=2 Destination Host Unreachable
From 192.168.1.25 icmp_seq=3 Destination Host Unreachable
From 192.168.1.25 icmp_seq=4 Destination Host Unreachable
From 192.168.1.25 icmp_seq=6 Destination Host Unreachable
From 192.168.1.25 icmp_seq=7 Destination Host Unreachable

6) ping the router
linux:/etc # ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.25: icmp_seq=1 Destination Host Unreachable
From 192.168.1.25 icmp_seq=1 Destination Host Unreachable
From 192.168.1.25 icmp_seq=2 Destination Host Unreachable
From 192.168.1.25 icmp_seq=3 Destination Host Unreachable
From 192.168.1.25 icmp_seq=5 Destination Host Unreachable
From 192.168.1.25 icmp_seq=6 Destination Host Unreachable
From 192.168.1.25 icmp_seq=7 Destination Host Unreachable

7) tried an ifup wlan0
linux:/etc # ifup wlan0
wlan0
SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
SuSEfirewall2: batch committing...
SuSEfirewall2: Firewall rules successfully set
linux:/etc #

8) everytime I do anything on the card, it blinks like hell. before all the ndiswrapper problems it was completely dead.

9) after adding the server to resolv.conf I do not get any more errors, it just waits... no surprise here.

10) I double check and triple check ESSID and password

11) the computer has a Lan card, but no cable there is not being used.

12) And the card is fine, in windows it works, so my guess is that it is just a stupid configuration issue.

Thanks a million.

at this stage Hangdog42' expertise will be neeeded, as I said
I am poor at this config game.

You can try to allow everything in/out firewall to check that this
is not where the issue is.
You can also try without wep, without any encryption.

you can do ping -c2
does anything show up in the syslog (do a tail -f /var/log/syslog) when you do the pings

This is quite general, http://www.linuxhomenetworking.com/w...ess_Networking I am not sure it will help that much, but this my stab in the dark. You will learn something out of that link.