Announcement

Collapse
No announcement yet.

Wireless problems

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Wireless problems

    I need to vent. Kubuntu hardy did not seem to make connecting to a wireless network any better that the convoluted painful process in previous releases.

    Settings do not stick from network manager. There are so many ways to change settings and none of them work or stick.

    What file do I edit to register WEP key, eesid, and any other obsecure parameter that will give me a connection to my router that, and I hate to say it WINDOWS VISTA just does out of the box?

    Thanks

    broden

    #2
    Re: Wireless problems

    If you need to vent, pay a psychologist. That's not what other users (that's who is on this forum) are here for.

    Goto K>System Settings>Network Settings>Administrator Mode then enter your password

    Click on your wireless interface and click Configure Interface. Make sure the Automatic button is check and dhcp is in the dropdown. Also make sure that Activate when the computer starts is checked. Enter your ESSID and WEP key and click OK. Click the X to close. You will get a box telling you that you have unsaved changes, click Apply. You should be rocking. If not, post back with the output of these commands (entered in Konsole) as a start:

    lspci -nn

    ifconfig

    iwconfig

    Good luck.

    Comment


      #3
      Re: Wireless problems

      I went through the steps you suggested. Here are the results.

      lspci -nn

      "00:00.0 RAM memory [0500]: nVidia Corporation C51 Host Bridge [10de:02f0] (rev a2)
      00:00.1 RAM memory [0500]: nVidia Corporation C51 Memory Controller 0 [10de:02fa] (rev a2)
      00:00.2 RAM memory [0500]: nVidia Corporation C51 Memory Controller 1 [10de:02fe] (rev a2)
      00:00.3 RAM memory [0500]: nVidia Corporation C51 Memory Controller 5 [10de:02f8] (rev a2)
      00:00.4 RAM memory [0500]: nVidia Corporation C51 Memory Controller 4 [10de:02f9] (rev a2)
      00:00.5 RAM memory [0500]: nVidia Corporation C51 Host Bridge [10de:02ff] (rev a2)
      00:00.6 RAM memory [0500]: nVidia Corporation C51 Memory Controller 3 [10de:027f] (rev a2)
      00:00.7 RAM memory [0500]: nVidia Corporation C51 Memory Controller 2 [10de:027e] (rev a2)
      00:02.0 PCI bridge [0604]: nVidia Corporation C51 PCI Express Bridge [10de:02fc] (rev a1)
      00:03.0 PCI bridge [0604]: nVidia Corporation C51 PCI Express Bridge [10de:02fd] (rev a1)
      00:05.0 VGA compatible controller [0300]: nVidia Corporation C51 [Geforce 6150 Go] [10de:0244] (rev a2)
      00:09.0 RAM memory [0500]: nVidia Corporation MCP51 Host Bridge [10de:0270] (rev a2)
      00:0a.0 ISA bridge [0601]: nVidia Corporation MCP51 LPC Bridge [10de:0260] (rev a3)
      00:0a.1 SMBus [0c05]: nVidia Corporation MCP51 SMBus [10de:0264] (rev a3)
      00:0a.3 Co-processor [0b40]: nVidia Corporation MCP51 PMU [10de:0271] (rev a3)
      00:0b.0 USB Controller [0c03]: nVidia Corporation MCP51 USB Controller [10de:026d] (rev a3)
      00:0b.1 USB Controller [0c03]: nVidia Corporation MCP51 USB Controller [10de:026e] (rev a3)
      00:0d.0 IDE interface [0101]: nVidia Corporation MCP51 IDE [10de:0265] (rev f1)
      00:0e.0 IDE interface [0101]: nVidia Corporation MCP51 Serial ATA Controller [10de:0266] (rev f1)
      00:10.0 PCI bridge [0604]: nVidia Corporation MCP51 PCI Bridge [10de:026f] (rev a2)
      00:10.1 Audio device [0403]: nVidia Corporation MCP51 High Definition Audio [10de:026c] (rev a2)
      00:14.0 Bridge [0680]: nVidia Corporation MCP51 Ethernet Controller [10de:0269] (rev a3)
      00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
      00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
      00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
      00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
      03:00.0 Network controller [0280]: Broadcom Corporation BCM94311MCG wlan mini-PCI [14e4:4311] (rev 01)"

      ifconfig

      "eth0 Link encap:Ethernet HWaddr 00:1b:24:12:b4:fe
      inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
      inet6 addr: fe80::21b:24ff:fe12:b4fe/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:49221 errors:231 dropped:0 overruns:0 frame:231
      TX packets:31093 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:70072665 (66.8 MB) TX bytes:2451914 (2.3 MB)
      Interrupt:20 Base address:0x6000

      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:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

      wlan0 Link encap:Ethernet HWaddr 00:1a:73:3d:60:7f
      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)

      wmaster0 Link encap:UNSPEC HWaddr 00-1A-73-3D-60-7F-00-00-00-00-00-00-00-00-00-00
      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 B) TX bytes:0 (0.0 B)"

      iwconfig

      "lo no wireless extensions.

      eth0 no wireless extensions.

      wmaster0 no wireless extensions.

      wlan0 IEEE 802.11g ESSID:""
      Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
      Tx-Power=27 dBm
      Retry min limit:7 RTS thrff Fragment thr=2346 B
      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 am connecting with a wired connection through the same linksys router. Any help appreciated.

      Thanks


      Comment


        #4
        Re: Wireless problems

        lingenfr
        I have the same problem with the same symptoms as broden including the same output from the commands you suggested. I've tried this with a fresh install of 8.04 and I've also done this with an upgrade from 7.10. Under 7,10 the wireless was flawless but under 8.04 I can't get it to work.

        In addition it appears that part of the system works. It can locate the essid from the router and displays the signal strength. The wireless light doesn't even attempt to light. Under 7.10 it would flicker until the connection was made and then it would be on full. In addition now under 8.04 none of the settings I set in system-> network settings-> network interfaces doesn't seem to stick.

        Also,
        do you think this is a bug we should report?

        Thanks for help and guidance. The experts manning this forum are doing a great job.

        John B.

        Comment


          #5
          Re: Wireless problems

          Originally posted by broden
          I went through the steps you suggested. Here are the results.

          ifconfig

          "eth0 Link encap:Ethernet HWaddr 00:1b:24:12:b4:fe
          inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::21b:24ff:fe12:b4fe/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:49221 errors:231 dropped:0 overruns:0 frame:231
          TX packets:31093 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:70072665 (66.8 MB) TX bytes:2451914 (2.3 MB)
          Interrupt:20 Base address:0x6000

          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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

          wlan0 Link encap:Ethernet HWaddr 00:1a:73:3d:60:7f
          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)

          wmaster0 Link encap:UNSPEC HWaddr 00-1A-73-3D-60-7F-00-00-00-00-00-00-00-00-00-00
          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 B) TX bytes:0 (0.0 B)"

          iwconfig

          "lo no wireless extensions.

          eth0 no wireless extensions.

          wmaster0 no wireless extensions.

          wlan0 IEEE 802.11g ESSID:""
          Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
          Tx-Power=27 dBm
          Retry min limit:7 RTS thrff Fragment thr=2346 B
          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 am connecting with a wired connection through the same linksys router. Any help appreciated.

          Thanks
          I notice that you have your Ethernet connection still active. I found that it was only after I removed this connection could I get the wireless link to work. On my notebook I get the following:

          ifconfig
          eth0 Link encap:Ethernet HWaddr 00:1b:fc:0e:cf:34
          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:251 Base address:0x4000

          eth0:avahi Link encap:Ethernet HWaddr 00:1b:fc:0e:cf:34
          inet addr:169.254.6.126 Bcast:169.254.255.255 Mask:255.255.0.0
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          Interrupt:251 Base address:0x4000

          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:76 errors:0 dropped:0 overruns:0 frame:0
          TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5764 (5.6 KB) TX bytes:5764 (5.6 KB)

          wlan0 Link encap:Ethernet HWaddr 00:1b:77:0a:5e:a4
          inet addr:192.168.10.3 Bcast:192.168.10.255 Mask:255.255.255.0
          inet6 addr: fe80::21b:77ff:fe0a:5ea4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:533 errors:0 dropped:0 overruns:0 frame:0
          TX packets:443 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:376089 (367.2 KB) TX bytes:136118 (132.9 KB)

          wmaster0 Link encap:UNSPEC HWaddr 00-1B-77-0A-5E-A4-00-00-00-00-00-00-00-00-00-00
          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 B) TX bytes:0 (0.0 B)

          With my system I can connect to the internet using eth0 and I assume that if I have both the eth0 and the wlan0 connected this causes a conflict. My assumption is that with both the eth0 and wlan0 connected, the eth0 connection is made first in the booting process and the wlan0 is then ignored.

          This is how I made sense of the problem and I hope this helps to get your wireless connection working.

          Comment


            #6
            Re: Wireless problems

            broden,

            Sorry to leave you hanging so long. I have had my own problems with broadcom in hardy. Hardy is the most dysfunctional release for me in quite a while. I tried the restricted drivers method and could not make it work. I think you will need to go the ndiswrapper route. I suggest that you follow the instructions here:

            https://help.ubuntu.com/community/Wi...eisty_No-Fluff

            I also suggest that you dump network-manager and go with wicd. You can find instructions here. Getting the tray icon set up is a little fiddly, but in the long run is worth it.

            http://wicd.sourceforge.net/download.php

            Just follow the instructions to the letter and you should be good to go. Post back if you have problems. I will try and pay closer attention over the weekend.

            beatty, I think you need to do the same.

            Comment

            Working...
            X