Announcement

Collapse
No announcement yet.

b43-fwcutter seems installed but notthing eslse

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 3
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 template Next
    #31
    Re: b43-fwcutter seems installed but notthing eslse

    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

    • Top
    • Bottom

    Comment

      #32
      Re: b43-fwcutter seems installed but notthing eslse

      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

      • Top
      • Bottom

      Comment

        #33
        Re: b43-fwcutter seems installed but notthing eslse

        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
        • Top
        • Bottom

        Comment

          #34
          Re: b43-fwcutter seems installed but notthing eslse

          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
          • Top
          • Bottom

          Comment

            #35
            Re: b43-fwcutter seems installed but notthing eslse

            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
            • Top
            • Bottom

            Comment

              #36
              Re: b43-fwcutter seems installed but notthing eslse

              Hi all:

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

              Code:
              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


              • Top
              • Bottom

              Comment

                #37
                Re: b43-fwcutter seems installed but notthing eslse

                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).
                Windows no longer obstructs my view.
                Using Kubuntu Linux since March 23, 2007.
                "It is a capital mistake to theorize before one has data." - Sherlock Holmes​
                • Top
                • Bottom

                Comment

                  #38
                  Re: b43-fwcutter seems installed but notthing eslse

                  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
                  Code:
                  dmesg | grep -e ndis -e wlan
                  I get this
                  Code:
                  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
                  Code:
                  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
                  • Top
                  • Bottom

                  Comment

                    #39
                    Re: b43-fwcutter seems installed but notthing eslse

                    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
                    • Top
                    • Bottom

                    Comment

                    Previous 1 2 3 template Next
                    Working...
                    X