b43-fwcutter seems installed but notthing eslse

[basx]

Hi all:

I ran the sudo command and here's what I get
xavier@ordenador:~$ sudo apt-get install b43-fwcutter
[sudo] password for xavier:
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
b43-fwcutter est déjà la plus récente version disponible.
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
xavier@ordenador:~$

Basically it's telling me that the b43fwcutter is the newest available. OK but what do I do next?

Thanks!

xavier

[colyn]

Hi all:

I ran the sudo command and here's what I get
xavier@ordenador:~$ sudo apt-get install b43-fwcutter
[sudo] password for xavier:
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
b43-fwcutter est déjà la plus récente version disponible.
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
xavier@ordenador:~$

Basically it's telling me that the b43fwcutter is the newest available. OK but what do I do next?

Thanks!

xavier


That's all I have on my wireless laptop and it works fine.

You'll need to setup your routers wireless then do the below.

Go to system settings-network settings and click the wireless tab. Click the add button and setup your wireless from there.

Name your new wireless connection, check the connect automatically box then click the scan button and find your wireless then click it.

If you have setup security in your router you'll have to configure wireless security from the wireless security tab.

[basx]

Colyn:

Thanks for the message.

I went to the KDEnetwork, created the name of the wireless, checkmarked the connect automatically, then I clicked on scan and nothing shows up on the little screen. Even though I'm like 50 cms from the router.

So I'm a bit frustrated. Am I missing a step?


xavier

[colyn]

Are you sure the routers wireless is activated?

If you have not setup the router for wireless you'll need to do that before you can access the net through it. Follow the directions provided by the maker.

One problem I had was a 802.11b wireless card in my laptop that my D-Link router had problems with so I upgraded to a 802.11g wireless card. If you have an 'a' or 'b' card try upgrading to a 'g'..

[basx]

Colyn:

Thanks. The router is set up for wireless. My windows computer works perfectly fine.
My Broadcom card is b/g and others have managed to get it to work uinder LINUX

xavier

[jglen490]

Start knetworkmanager, it should show up in the tray. Click on the icon and select "Manage Connections". Inside the Configure - KDE Control Module dialog box click on the wireless taq. If you were successful in creating an connection earlier, click on its name and then click on the "Edit" button to the right. The Edit Network Connection - KDE Control Module dialog box should open. Fill in or verify all applicable input fields on each tab. Ensure your SSID and Password are correct for your router. Save any changes. See if that starts your connection.

I put mine into Kwalletmanager along with a couple of other things. Each startup it prompts me for a wallet password and starts it all. You may want to do this, or not. It's up to you.

I hope that helps. If not come back and we'll try something else, because everything is present, we just need to get it all working together.

[basx]

Jglen490:
Thanks. I tried to edit the wireless but when I add the SSID and then click on the scan button it doesn't pick up the network and it then 'erased' the SSID name

Curiously when I tried to edit it, the Wireless security tab didn't have applicable security option (I'm use WEP)

As noted earlier, I erased the wireless in the hopes that I could recreate it but because knetwork manager isn't picking up the network, I'm going around in circles.
I'm stumped as to why my computer can't pick up the wireless signal.

One last thing, my computer's a Compaq Presario R3440 and the little wireless light isn't lit. When I press the button there's still no light. Any suggestions?

Thanks!

xavier

[jglen490]

Sometimes Knetworkmanager just doesn't work. There is an alternative that a lot of people like called
"wicd". If you install wicd, you must remove knetworkmanager as the two don't play nice.

I have used wicd in the past and it is a good wireless manager, but I'm not using it right under the theory that "if it ain't broke, don't fix it", and knetworkmanager is doing well for my machine. There are a lot of people here who can help you with wicd if you have questions.

If you go with wicd, but still have questions, I would recommend starting a new topic. Good luck!!

EDIT: The light on your card NOT showing could be due to the driver not connecting with your hardware. This might be taken care of with wicd.

[basx]

Jglen:

Thanks for your message. I think I'll remove knetworkmanger and go with wicd.
At another thread, some of the participants gave me a list of files that I need for wicd. Kpackage picks all of them except for one so I might try the sudo apt-install wicd.

I'm concerned that if I delete my Kmanager while downloading wicd, I'll lose my wired connection.

If I have any question regarding wicd, I'll start another thread.

xavier

[basx]

Hi all:
I bit the bullet and removed kde network manager and installed wicd.

I clicked on the refresh button to scan for the wireless. Didn't find it. I tried to manually enter the SSID name of the network. no luck.

What can I do next to have wicd find the wirless so I can connect?

Thanks!

xavier

[claydoh]

I think you need to keep to your previous threads and first make sure you actually have your driver loaded and working first

merging this with another thread

[basx]

claydoh:

Thanks. Soprry about the multiple posts. OK I've already checked in the Hardware drivers and the driver isn't there.

Is there a terminal command that I can use to check if indeed the driver are installed and recognized by the computer? That's the most frustrating thing. The computer doesn't seem to find the drivers and use them.

If not, then I'll ask for the steps to get the computer to find and use the driver.

Thanks again!

xavier

xavier

[claydoh]

fwe have to ensure that your card's drivers are actually loading, as you aren't seeing any wireless access points at all. This is completely independent of wicd/netwotk manager

First, we need to know what card you have: broadcom 4306? Built-in or external card? What is the make and model of your computer?

let's check:

lspci
post the results of that command . We are looking for the Networking device you have


Next, you previously said you have 'downloaded' the b43-fwcutter package - did you download from a website, or use apt-get, kpackagekit, synaptic, or the Hardware Driver manager to install it? The Hardware Manager method is best as it correctly runs the actual b43 firmware downloader correctly - I am not sure if KPackagekit works correctly for this package.

You also need to install it with an active connection to the internet as it has to download and extract the correct firmware files.

To make sure it is installed correctly, please try re-installing the b43-fwcutter package:

$ sudo apt-get remove --purge b43-fwcutter && sudo apt-get install b43-fwcutter
This will remove the package in one step, then reinstall it in another

you should get a screen asking if you want to download and extract the firmware; then you should see some download progress in your terminal (if the files haven't actually been downloaded yet previously)

now to check if the drivers have loaded:
You shouldn't have to reboot for this, but you may want to disable and re-enable wireless from within wicd/knetworkmanager (or unplug/replug the device if it is removable)

lsmod |grep b43
And post the output here

[basx]

Claydoh:

Thanks. My Broadcom is a built in one and it's the 4306 (rev 3) model. I know this because I;ve checked and rechecked it so many times. ;) I don't have my Linux machine with me but I'll re run the command and post it here.

2) The first time I used Kpackage but I don't think it extracts it properly. I then used the sudo apt-get install command. I never really saw the big text scren asking me if I wanted to extract the firmware
3) I'll purge the b43 fwcutter. Also, just to be on the safe side I'll remove the wl_asta.o and the wl_mimo.o files that I installed based on the French documentation for installing Broadcom 43xx and the wirelesslinux.org instructions
Is the command to remove sudo rm subirectory/file ?

4) I'll use the sudo apt-get install command as that seems to be the 'safest' method to use.

Thanks so much!

xavier

[basx]

Claydoh:

Sorrry for the delay. Work and family :) Here are the results of the lspci command that you asked for

avier@ordenador:~$ lspci
00:00.0 Host bridge: nVidia Corporation nForce3 Host Bridge (rev a4)
00:01.0 ISA bridge: nVidia Corporation nForce3 LPC Bridge (rev a6)
00:01.1 SMBus: nVidia Corporation nForce3 SMBus (rev a4)
00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce3 Audio (rev a2)
00:06.1 Modem: nVidia Corporation nForce3 Audio (rev a2)
00:08.0 IDE interface: nVidia Corporation nForce3 IDE (rev a5)
00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 AGP Bridge (rev a4)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 440 Go 64M] (rev a3)
02:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
02:04.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01)
02:04.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01)
02:04.2 System peripheral: Texas Instruments PCI1620 Firmware Loading Function (rev 01)
xavier@ordenador:~$


As you can see my Broadcom card is
02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

So acccording to the linuxwireless.org site, I need the b43 file.


I copied and pasted the command to purge and get b43 fw cutter.

It asked for the CD. It then asked me if I wanted to extract the firmware which I said yes.

Then I copied and pasted the other command to see if the driver loaded and the answer is no

lsmod |grep b43

I did disconnect all connections but didn't reboot.

It still can't find any wireless network. I then clicked on find hidden network but still didn't find it. So I'll reboot and try again.

xavier

[basx]

Hi all:
I rebooted the computer but it still doesn't detect the wireless and the drivers still aren't loading.

I feel both very frustrated and hopeless about getting the wireless card to work.

I'm wondering if the fact that it's asking for the KUBUNTU CD could be the problem. If so, should I uncheck the CD as a software source?

Thanks

P.S. Happy birthday Claydoh :)

xavier

[jglen490]

Let's check to be sure about the b43-fwcutter package that you have.

Enter this:

dpkg -l b43*

The output should look like:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-====================-====================-================================================== ======
ii b43-fwcutter 1:012-1build1 Utility for extracting Broadcom 43xx firmware


Then enter:

cd /etc/network

and:

less interfaces

It should look something like:

auto lo
iface lo inet loopback



If there is more than that, comment out ALL other lines.

It is possible that wpa-supplicant is not installed, so enter:

dpkg -l wpasupplicant

The response should be something like:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-====================-====================-================================================== ======
ii wpasupplicant 0.6.9-3ubuntu3 client support for WPA and WPA2 (IEEE 802.11i)


Try the above and let us know what the responses are.

[basx]

jglen940:

Thanks for your message.
I typed the first command and got this:


xavier@ordenador:~$ dpkg -l b43*
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom Version Description
+++-=======================-=======================-================================================== ============
ii b43-fwcutter 1:012-1build1 Utility for extracting Broadcom 43xx firmware
xavier@ordenador:~$ http://www.kubuntuforums.net/


So I guess b43 fwcutter iis nstalled

As for the second command I get this


auto lo
iface lo inet loopback

#Ethernet
auto eth0
iface eth0 inet dhcp


but I can't comment out the Earthnet lines because then I'd lose my ability to connect to the net

When I type out the 3rd command, I get this result:


xavier@ordenador:~$ dpkg -l wpasupplicant
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom Version Description
+++-=======================-=======================-================================================== ============
ii wpasupplicant 0.6.9-3ubuntu3 client support for WPA and WPA2 (IEEE 802.11i)
xavier@ordenador:~$



What's the prognosis? Is everything in order?

Thanks again!

xavier

P.S On a hunch I typed lswh and I got this interesting tidbit:


*-network:1 UNCLAIMED
description: Network controller
product: BCM4306 802.11b/g Wireless LAN Controller
vendor: Broadcom Corporation
physical id: 2
bus info: pci@0000:02:02.0
version: 03
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: latency=64
resources: memory:e0104000-e0105fff


It seems that the drivers aren't loading and that's the problem that,s driven me crazy these past weeks as to why not.

[jglen490]

Normally, all that should be in the "interfaces" file is the loopback entry, when you are using a network manager. What you can do is comment out the lines for ethernet, reboot and try to start the network manager. If you run into a problem, you can always uncomment the ethernet lines to get your hard wire connection back again. When the network manager is working, it will handle either the wireless or the wired connection, based on which connection is present.

You have the correct driver for your wireless, and you have a wpa-supplicant which will make the wireless connection to your router work. It's supposed to work with either WEP or a WPA variant. WPA is always much better (more secure) than WEP. But whatever you use depends on what your router can support, and is better than no security all :)

If either knwtworkmanager or wicd is installed, you will still to do some setup work through the GUI.

[claydoh]

One thing we should figure out (and I should have done this earlier) is to get more info on the wireless card


lspci -vnn | grep 14e4

this will give better info on the id numbers, etc so we can see if it a supported chip or which driver we actually need as no driver is loading at all.

http://wireless.kernel.org/en/users/Drivers/b43

[basx]

Claydoh:

Thanks for the latest post. Sorry about the delay.#

Per your request, I copied ans pasted the commandyou gave me and this is the results


02:02.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)


According to the wireless.linux.org page it's supported through the b43file

14e4:4320 supported BCM4306/3 ? ? b43

So I have 2 obvious questions:
1)Should I build my own b43 fw cutter and extract the necessary file(s)
2) Or should I download the ndiswrapper and use the Windows driver

Thanks!

xavier

[jglen490]

1) You already have the correct version of b43-fwcutter, so I don't think you can do better than that.

2) It's possible the ndiswrapper could provide a working driver, but you really should remove any evidence of b43-fwcutter before doing that. Also, make sure you follow all the instructions for ndiswrapper.

I have a feeling that there is something interfering with networkmanager, such as another network management software.

Also, did you change the interfaces file to only have the loopback device referenced?

in your settings at K -> Settings -> System Settings -> Network Settings, there should only be one connection referenced and it should have all your router settings correctly referenced.

If you enter
lsmod, the output should show only entries for b43 related to a couple of 80211 lines and b43 itself.

Beyond those few things, I don't know what else to look for.

[basx]

jglen40:
Thanks for your input.
I typed lsmod and here's what returns:


Module Size Used by
binfmt_misc 6587 1
fbcon 35102 71
tileblit 2031 1 fbcon
font 7557 1 fbcon
bitblit 4707 1 fbcon
softcursor 1189 1 bitblit
vga16fb 11385 0
vgastate 8961 1 vga16fb
pcmcia 33024 0
snd_intel8x0 25588 2
snd_ac97_codec 100646 1 snd_intel8x0
ac97_bus 1002 1 snd_ac97_codec
snd_pcm_oss 35308 0
snd_mixer_oss 13746 1 snd_pcm_oss
snd_pcm 70662 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_seq_dummy 1338 0
snd_seq_oss 26726 0
snd_seq_midi 4557 0
joydev 8708 0
snd_rawmidi 19056 1 snd_seq_midi
snd_seq_midi_event 6003 2 snd_seq_oss,snd_seq_midi
snd_seq 47263 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
nouveau 467048 2
snd_timer 19098 2 snd_pcm,snd_seq
snd_seq_device 5700 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
ttm 49943 1 nouveau
yenta_socket 20408 2
drm_kms_helper 29297 1 nouveau
snd 54148 14 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
rsrc_nonstatic 10015 1 yenta_socket
pcmcia_core 32964 3 pcmcia,yenta_socket,rsrc_nonstatic
drm 162377 4 nouveau,ttm,drm_kms_helper
i2c_algo_bit 5028 1 nouveau
ppdev 5259 0
amd64_agp 7025 1
video 17375 0
soundcore 6620 1 snd
output 1871 1 video
psmouse 63245 0
serio_raw 3978 0
k8temp 3024 0
agpgart 31724 3 ttm,drm,amd64_agp
shpchp 28820 0
snd_page_alloc 7076 2 snd_intel8x0,snd_pcm
i2c_nforce2 5199 0
parport_pc 25962 1
lp 7028 0
parport 32635 3 ppdev,parport_pc,lp
ohci1394 26950 0
8139too 18545 0
8139cp 16186 0
pata_amd 8766 2
mii 4381 2 8139too,8139cp
ieee1394 81181 1 ohci1394


If I want to make sure if I purged knetwork manager what comman should I use?

Thanks again!

xavier

[jglen490]

I don't see b43 being loaded, at all.

I do see mii at end of your list which, I believe should be for your ethernet connector (at least it is for mine).

I'm not sure why it's not being loaded. Perhaps someone else has a better idea.

[claydoh]

Have you purged and reinstalled b43-fwcutter yet? I looked back in the thread, and cannot tell if you have.


sudo apt-get purge b43-fwcutter
then
[sudo apt-get install b43-fwcutter
while using a wired connection

this will bring up the dialog to download and extract the firmware

if you cannot access the net for this, the manual method is listed here
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx#b43%20-%20No%20Internet%20access

[basx]

Hi all:
Well I'll have to throw up my hands and give up. No matter what I try and advice I follow, the drivers simply refuse to load. I'll just have to accept the fact that for my particular notebook. if I I want to connect to the net, I have to have the cable and be near an Eartnet connection.
Bummer because that defeats having a notebook. Still, everything else works and I get my work done offline.

I'll leave it as it is unless there's some other tip or idea we haven't though of.

Thanks for all the help!

xavier

[basx]

Hi all:
Sorry to write again but I came across an important clue. I found an old book called Hacking Ubuntu (it's old because it refers to 6,06) and there's a chapter on network configuration and it mentioned that wlan0 is the name given to the driver with ndiswrapper.

Wait a minute, I've never installed ndiswrapper and that most likely explains why the driver isn't loading. In wicd, I have wlan0. So if that's the wrong name, what's the correct one? eth1 for the wireless? Or something else?

Thanks!

xavier

[claydoh]

ndiswrapper is for using a Widows driver. not for using a (not existing in 6.06) Linux native driver.

wlan0 is *usually* correct, but for some drivers/devices it can be something else

[basx]

claydoh:
Thanks. If I switched the wlan0 to eth1 in the wicd interface, how can I verify if the computer will finally recognize the wireless?

Also, I'm seriously thinking of removing the b43-fwcutter and using ndiswrapper. So I have a couple of questions

1) is there any updated documentation to install and configure ndiswrapper with 10,04? I found some French documentation on the subject but it's for the older versions and I'm a bit leery slavishly following the commands.

2) HP still has the Windows XP Broadcom drivers for my Compaq model. If I install ndiswrapper should I use the aforemention drivers? Or should I use a different one? If so which and where would I download the drivers?

3) If I use ndisgtk, would I still need to download the Windows drivers?

Thanks!

xavier

[claydoh]

in my link above
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx#b43%20-%20No%20Internet%20access
You can try manually extracting the firmaware with the fwcutter tool try this first as you already have the tool installed, and that might just work - at least we will know if it does or not very quickly

if you still need to try ndsiwrapper
https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper
has all the instructions, and looks quite thorough as to what you need to do.

You will need to get your windows driver no matter which ndiswrapper method you use, I think you can use your XP driver as you know it works, but the wiki links to a page with the known good drivers iirc

[basx]

Claydoh:
Thanks for the links. I've already tried to extract the firmware twice and each time the driver didn't load.

I'll check the instructions again to see if I missed anything. But I suspect that I'll have to use the Windows drivers for my machine.

Thanks again!

xavier

[basx]

Hi all:

OK, the ndisgtk WORKED!!!! I can now see my wireless connection and a few others.

I'm almost there. I have a password and it's WEP. But I'm confused as to which one I should use.

My password is LETTER########LETTER (LETTER 8 numbers LETTER)

When I enter the password it tries to connect but then pops up the message connection failed wrong password.

I didn't reboot the computer after I installed the driver. Should I have done that?

Thanks for any additional tips

xavier

[claydoh]

w00t!!!!


I don't think rebooting will have any effect

You have to go to your router to determine/change your encryption method, though I think that wicd, etc can determine which one your wifi is using - I am not sure though.

WPA is much more secure, WEP is not so secure but better than nothing

[basx]

Cladoh:

Well I seem to be totally stumped. I tried a longshot: I went to Kgear|computer|system configuration|Knetworkmanager and tried to configure the info and see if the computer would connect from there.

Well it didn't work. Wicd stated that I'm using WEP but when I enter the password ( I choose WEP HEX (A-F/0-9) BUT WHEN i ENTER THE PASSWORD, wicd tries to connect I eventually get a message that the password's wrong.
It's not since the Windows computer connect just fine.

Any ideas how to get wicd to accept the password?

Thanks again!

xavier

[basx]

Hi all:

Sorry to write again. I was reading some troubleshooting documentation from another LINUX distribution and it mentioned the iwscan command. It shows the WEP key.

Is the iwscan command valid for someone who uses a Windows drivers under ndiswrapper?

Thanks!

xavier

[basx]

Hi all:

Ok iwscan isn't recognized by KUBUNTU so I ran dmesg and here's the output:


26.483265] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 26.632891] eth0: link down
[ 26.633259] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 26.671077] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 28.873838] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 29.330894] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 34.434510] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 39.672022] wlan0: no IPv6 routers present
[ 41.263633] CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold
[ 44.988068] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 50.546074] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 56.110136] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 61.667292] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 67.228029] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 72.450656] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 74.456533] eth0: link down
[ 74.456911] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 74.475205] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 75.495596] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 76.616398] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 76.845747] eth0: link down
[ 76.846490] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 77.066924] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 82.172191] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 87.344018] wlan0: no IPv6 routers present
[ 87.727475] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 93.283501] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 98.840970] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 104.406849] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 114.976304] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 120.479282] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 120.724249] eth0: link down
[ 120.724962] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 120.753885] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 121.817484] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 121.943274] eth0: link down
[ 121.943651] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 122.890493] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 123.358692] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 128.464200] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 133.984022] wlan0: no IPv6 routers present
[ 134.020305] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 139.577837] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 145.135299] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 150.707968] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 156.265721] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 165.381435] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 165.548678] eth0: link down
[ 165.549048] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 165.566463] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 166.618275] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 166.817474] eth0: link down
[ 166.817808] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 167.702161] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 168.151439] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 173.254405] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 178.596023] wlan0: no IPv6 routers present
[ 178.818161] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 184.379987] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 189.942243] ndiswrapper (iw_set_auth:1602): invalid cmd 12
26.483265] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 26.632891] eth0: link down
[ 26.633259] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 26.671077] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 28.873838] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 29.330894] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 34.434510] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 39.672022] wlan0: no IPv6 routers present
[ 41.263633] CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold
[ 44.988068] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 50.546074] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 56.110136] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 61.667292] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 67.228029] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 72.450656] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 74.456533] eth0: link down
[ 74.456911] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 74.475205] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 75.495596] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 76.616398] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 76.845747] eth0: link down
[ 76.846490] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 77.066924] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 82.172191] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 87.344018] wlan0: no IPv6 routers present
[ 87.727475] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 93.283501] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 98.840970] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 104.406849] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 114.976304] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 120.479282] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 120.724249] eth0: link down
[ 120.724962] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 120.753885] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 121.817484] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 121.943274] eth0: link down
[ 121.943651] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 122.890493] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 123.358692] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 128.464200] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 133.984022] wlan0: no IPv6 routers present
[ 134.020305] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 139.577837] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 145.135299] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 150.707968] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 156.265721] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 165.381435] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 165.548678] eth0: link down
[ 165.549048] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 165.566463] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 166.618275] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 166.817474] eth0: link down
[ 166.817808] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 167.702161] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 168.151439] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 173.254405] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 178.596023] wlan0: no IPv6 routers present
[ 178.818161] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 184.379987] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 189.942243] ndiswrapper (iw_set_auth:1602): invalid cmd 12
26.483265] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 26.632891] eth0: link down
[ 26.633259] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 26.671077] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 28.873838] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 29.330894] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 34.434510] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 39.672022] wlan0: no IPv6 routers present
[ 41.263633] CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold
[ 44.988068] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 50.546074] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 56.110136] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 61.667292] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 67.228029] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 72.450656] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 74.456533] eth0: link down
[ 74.456911] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 74.475205] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 75.495596] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 76.616398] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 76.845747] eth0: link down
[ 76.846490] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 77.066924] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 82.172191] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 87.344018] wlan0: no IPv6 routers present
[ 87.727475] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 93.283501] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 98.840970] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 104.406849] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 114.976304] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 120.479282] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 120.724249] eth0: link down
[ 120.724962] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 120.753885] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 121.817484] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 121.943274] eth0: link down
[ 121.943651] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 122.890493] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 123.358692] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 128.464200] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 133.984022] wlan0: no IPv6 routers present
[ 134.020305] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 139.577837] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 145.135299] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 150.707968] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 156.265721] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 165.381435] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 165.548678] eth0: link down
[ 165.549048] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 165.566463] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 166.618275] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 166.817474] eth0: link down
[ 166.817808] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 167.702161] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 168.151439] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 173.254405] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 178.596023] wlan0: no IPv6 routers present
[ 178.818161] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 184.379987] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 189.942243] ndiswrapper (iw_set_auth:1602): invalid cmd 12


Any suggestions as to how I can get wicd to accept the WEP password? The Windows computers have no problem
Thanks!

xavier

[Snowhog]

From the wicd wiki:

Configuration

Configuration of Wicd is extremely simple, and automatic for wired clients. To configure a wireless connection:
1. Open the Wicd network manager in Applications > Internet > Wicd Network Manager (you may also click the tray icon if present).
2. See if the wireless network you're looking for shows on the list. If it is a hidden network, click the down arrow next to the Network button, and type in the ESSID of the network.
3. If the network you want to connect to is listed, press the "Connect" button next to it.
4. If you get the message "This network requires encryption to be enabled." hit OK, then click the arrow next to the network name.
5. Hit the "Advanced Settings" button.
6. Check the "Use Encryption" checkbox, choose your encryption type and type in the key. You may also assign a static IP or DNS in here, but most users will not need to.
7. Hit OK.
8. Now hit connect again. This time the connection should come up relatively quickly.
9. If you plan to use this connection all the time, consider pressing the "Automatically connect to this network" checkbox. You have to open the arrow next to the network name to choose it.

Once a connection is configured, there is no need to open Wicd again unless you need to set up a connection for a different location or did not chose an automatic connection. If configured, Wicd will connect to the network before the desktop has even loaded (this is unlike Network-Manager, which will wait for a GUI).

[basx]

Snowhog:
Thanks for the wiki link. I've come across the forums and the bug reports which might help me track down my problem

You see, the problem is that the authentification process fails. For some reason, my Kubuntu notebook doesn't accept the WEP password while the Windows machine connect just fine.

I've been doing some dective work and I came across 2 interesting outputs. If I use
dmesg | grep -e ndis -e wlan
I get this
xavier@ordenador:~$ dmesg | grep -e ndis -e wlan
[ 16.471082] ndiswrapper version 1.55 loaded (smp=yes, preempt=no)
[ 17.118921] ndiswrapper: driver bcmwl5 (Broadcom,07/21/2005, 3.140.16.0) loaded
[ 17.121664] ndiswrapper 0000:02:02.0: PCI INT A -> Link[LNK3] -> GSI 17 (level, low) -> IRQ 17
[ 17.133930] ndiswrapper: using IRQ 17
[ 17.356927] wlan0: ethernet device 00:90:4b:a3:0b:7f using NDIS driver: bcmwl5, version: 0x38c1000, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4320.5.conf
[ 17.356988] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
[ 17.976489] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 18.420930] usbcore: registered new interface driver ndiswrapper
[ 326.481246] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 348.377578] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 348.584387] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 350.754299] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 351.214286] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 356.317381] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 361.504016] wlan0: no IPv6 routers present
[ 361.870462] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 367.427499] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 372.979400] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 378.534459] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 384.086507] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 386.359654] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 420.139664] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 420.161510] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 420.383855] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 422.574152] ndiswrapper (add_wep_key:841): adding encryption key 1 failed (C0010015)
[ 422.574258] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 423.031738] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 428.134309] ndiswrapper (add_wep_key:841): adding encryption key 1 failed (C0010015)
[ 428.134399] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 433.688960] ndiswrapper (add_wep_key:841): adding encryption key 1 failed (C0010015)
[ 433.689048] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 433.700012] wlan0: no IPv6 routers present
[ 439.242653] ndiswrapper (add_wep_key:841): adding encryption key 1 failed (C0010015)
[ 439.242753] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 444.800943] ndiswrapper (add_wep_key:841): adding encryption key 1 failed (C0010015)
[ 444.801040] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 450.353127] ndiswrapper (add_wep_key:841): adding encryption key 1 failed (C0010015)
[ 450.353227] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 455.910404] ndiswrapper (add_wep_key:841): adding encryption key 1 failed (C0010015)
[ 455.910494] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 458.176280] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 476.474034] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 476.496376] ADDRCONF(NETDEV_UP): wlan0: link is not ready

Then when I run this command
sudo cat /var/log/wicd/wicd.log

I get output that tells me: wpa_supplicant authentication may have failed.

So with this information, I'll search for invalid cmd 12 errors in the forums as well as looking for info on wpa_supplicant failures.

Thanks again!

xavier

[basx]

Hi all:
I'm now connected wirelesly!!!!! Thanks to Grey geek for suggestion in another thread to purge all instances of Knetwork manager! As soon as I got rid of every trace, the wireless connected automatically without a reboot.

Hopefully when I start the computer again tomorrow, I'll still be able to connect

Thanks everyone for your help. I really learnt alot and I'm excited to dive into LINUX once again!

xavier