Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Confused by wireless signal strength

Confused by wireless signal strength

Scheduled Pinned Locked Moved The Lounge
cssdata-structurestoolsarchitecturehelp
13 Posts 9 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D dandy72

    I have a WMP54G wireless PCI NIC made by Linksys in one of my PCs. This PC dual-boots between XP 32-bit and 64-bit. Out of preference, I spend 99% of my time under the x64 version. The NIC doesn't come with 64-bit drivers; however after doing a bit of research, the 64-bit Ralink RT2500 drivers reportedly work great as an alternative for this card. Indeed, as far as drivers go, they seem to work fine. Here's the problem. While under x64, the signal strength is constantly fluctuating (wildly)--it can range from "excellent" to completely dropped within a few seconds. It'll spend some moments at "low", and eventually come back to "excellent". Lather, rinse, repeat. Things seem to get progressively worse with time. The router broadcasting the signal is in the next room, less than 20 feet away, and I have a laptop sitting next to this machine (inches apart) that has a constant, rock-solid connection. I also have another PC much farther away, sitting in the basement (the router and the other PCs are on the second floor), and it also has a good constant connection. So, you'd think that PCI NIC is simply defective... The strangest thing is that this very same machine, simply rebooted to run under XP x86, gets a constant and reliable connection just like all the other systems in the house. I've let Netstumbler run for half an hour--the signal strength graph was straight as an arrow. Unfortunately, Netstumbler doesn't run under x64, but as mentioned, while under x64, the systray utility is telling me that the signal is low one second, excellent the next, then back to low again, etc. I find it hard to blame the driver. Suggestions and wild speculation welcomed.

    R Offline
    R Offline
    Rob Graham
    wrote on last edited by
    #2

    Since only two things are different under 64 bit (the OS and the driver) and the driver isn't really for that NIC, I'd put my money on a (slightly) defective driver.

    R 1 Reply Last reply
    0
    • R Rob Graham

      Since only two things are different under 64 bit (the OS and the driver) and the driver isn't really for that NIC, I'd put my money on a (slightly) defective driver.

      R Offline
      R Offline
      Ryan Binns
      wrote on last edited by
      #3

      Agreed

      Ryan

      "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

      1 Reply Last reply
      0
      • D dandy72

        I have a WMP54G wireless PCI NIC made by Linksys in one of my PCs. This PC dual-boots between XP 32-bit and 64-bit. Out of preference, I spend 99% of my time under the x64 version. The NIC doesn't come with 64-bit drivers; however after doing a bit of research, the 64-bit Ralink RT2500 drivers reportedly work great as an alternative for this card. Indeed, as far as drivers go, they seem to work fine. Here's the problem. While under x64, the signal strength is constantly fluctuating (wildly)--it can range from "excellent" to completely dropped within a few seconds. It'll spend some moments at "low", and eventually come back to "excellent". Lather, rinse, repeat. Things seem to get progressively worse with time. The router broadcasting the signal is in the next room, less than 20 feet away, and I have a laptop sitting next to this machine (inches apart) that has a constant, rock-solid connection. I also have another PC much farther away, sitting in the basement (the router and the other PCs are on the second floor), and it also has a good constant connection. So, you'd think that PCI NIC is simply defective... The strangest thing is that this very same machine, simply rebooted to run under XP x86, gets a constant and reliable connection just like all the other systems in the house. I've let Netstumbler run for half an hour--the signal strength graph was straight as an arrow. Unfortunately, Netstumbler doesn't run under x64, but as mentioned, while under x64, the systray utility is telling me that the signal is low one second, excellent the next, then back to low again, etc. I find it hard to blame the driver. Suggestions and wild speculation welcomed.

        D Offline
        D Offline
        Daniel Turini
        wrote on last edited by
        #4

        Daniel Desormeaux wrote:

        I find it hard to blame the driver.

        Those software guys, always find a way of blaming the hardware... :) Actually, for me, it seems pretty obvious that the drivers are the problem here...

        1 Reply Last reply
        0
        • D dandy72

          I have a WMP54G wireless PCI NIC made by Linksys in one of my PCs. This PC dual-boots between XP 32-bit and 64-bit. Out of preference, I spend 99% of my time under the x64 version. The NIC doesn't come with 64-bit drivers; however after doing a bit of research, the 64-bit Ralink RT2500 drivers reportedly work great as an alternative for this card. Indeed, as far as drivers go, they seem to work fine. Here's the problem. While under x64, the signal strength is constantly fluctuating (wildly)--it can range from "excellent" to completely dropped within a few seconds. It'll spend some moments at "low", and eventually come back to "excellent". Lather, rinse, repeat. Things seem to get progressively worse with time. The router broadcasting the signal is in the next room, less than 20 feet away, and I have a laptop sitting next to this machine (inches apart) that has a constant, rock-solid connection. I also have another PC much farther away, sitting in the basement (the router and the other PCs are on the second floor), and it also has a good constant connection. So, you'd think that PCI NIC is simply defective... The strangest thing is that this very same machine, simply rebooted to run under XP x86, gets a constant and reliable connection just like all the other systems in the house. I've let Netstumbler run for half an hour--the signal strength graph was straight as an arrow. Unfortunately, Netstumbler doesn't run under x64, but as mentioned, while under x64, the systray utility is telling me that the signal is low one second, excellent the next, then back to low again, etc. I find it hard to blame the driver. Suggestions and wild speculation welcomed.

          K Offline
          K Offline
          krism42
          wrote on last edited by
          #5

          Are you really having connection problems, or is the driver misreporting signal strength? (e.g. does ping -t .... abort/change when the signal appears to be low?)

          1 Reply Last reply
          0
          • D dandy72

            I have a WMP54G wireless PCI NIC made by Linksys in one of my PCs. This PC dual-boots between XP 32-bit and 64-bit. Out of preference, I spend 99% of my time under the x64 version. The NIC doesn't come with 64-bit drivers; however after doing a bit of research, the 64-bit Ralink RT2500 drivers reportedly work great as an alternative for this card. Indeed, as far as drivers go, they seem to work fine. Here's the problem. While under x64, the signal strength is constantly fluctuating (wildly)--it can range from "excellent" to completely dropped within a few seconds. It'll spend some moments at "low", and eventually come back to "excellent". Lather, rinse, repeat. Things seem to get progressively worse with time. The router broadcasting the signal is in the next room, less than 20 feet away, and I have a laptop sitting next to this machine (inches apart) that has a constant, rock-solid connection. I also have another PC much farther away, sitting in the basement (the router and the other PCs are on the second floor), and it also has a good constant connection. So, you'd think that PCI NIC is simply defective... The strangest thing is that this very same machine, simply rebooted to run under XP x86, gets a constant and reliable connection just like all the other systems in the house. I've let Netstumbler run for half an hour--the signal strength graph was straight as an arrow. Unfortunately, Netstumbler doesn't run under x64, but as mentioned, while under x64, the systray utility is telling me that the signal is low one second, excellent the next, then back to low again, etc. I find it hard to blame the driver. Suggestions and wild speculation welcomed.

            R Offline
            R Offline
            Roger Wright
            wrote on last edited by
            #6

            Daniel Desormeaux wrote:

            I find it hard to blame the driver.

            Why? It's not the correct driver for the card. :doh: The important question is, does the connection work? Who cares what signal strength it's reporting if the functional part of the driver works?:-D

            "...a photo album is like Life, but flat and stuck to pages." - Shog9

            D 1 Reply Last reply
            0
            • D dandy72

              I have a WMP54G wireless PCI NIC made by Linksys in one of my PCs. This PC dual-boots between XP 32-bit and 64-bit. Out of preference, I spend 99% of my time under the x64 version. The NIC doesn't come with 64-bit drivers; however after doing a bit of research, the 64-bit Ralink RT2500 drivers reportedly work great as an alternative for this card. Indeed, as far as drivers go, they seem to work fine. Here's the problem. While under x64, the signal strength is constantly fluctuating (wildly)--it can range from "excellent" to completely dropped within a few seconds. It'll spend some moments at "low", and eventually come back to "excellent". Lather, rinse, repeat. Things seem to get progressively worse with time. The router broadcasting the signal is in the next room, less than 20 feet away, and I have a laptop sitting next to this machine (inches apart) that has a constant, rock-solid connection. I also have another PC much farther away, sitting in the basement (the router and the other PCs are on the second floor), and it also has a good constant connection. So, you'd think that PCI NIC is simply defective... The strangest thing is that this very same machine, simply rebooted to run under XP x86, gets a constant and reliable connection just like all the other systems in the house. I've let Netstumbler run for half an hour--the signal strength graph was straight as an arrow. Unfortunately, Netstumbler doesn't run under x64, but as mentioned, while under x64, the systray utility is telling me that the signal is low one second, excellent the next, then back to low again, etc. I find it hard to blame the driver. Suggestions and wild speculation welcomed.

              M Offline
              M Offline
              mgama
              wrote on last edited by
              #7

              I'm thinking the fluctuation may be caused by some compatibility issue with another piece of hardware or driver. I have two of the same WMP54G cards for my PCs, well technically one is a v4.0 and the other is a v4.1. My main PC had the same fluctuation problem (in addition to losing it's connection every ~3 hours). The other MCE PC had a rock solid signal strength & speed. After swapping the cards, and wiping both machines, the main PC still has the fluctuation & slow speeds (without the connection loss problem) while the MCE is still rock solid. I've seen similar problems with a video card - it ran really hot in one PC, and perfectly cool in another. Could be a motherboard issue, or something else completely. I'm glad my connection isn't going down every 3 hours, but still dreaming of reliable connections. I may end up running CAT5 around my house. I've had it with Linksys (don't get me started on the WRT54G-v5). [edit] I ended up using the Ralink driver on the MCE machine which has the rock solid connection since there weren't Vista drivers put out by Linksys. Ralink is the maker of the chipset used in the card, so I think you are safe there.

              D V 2 Replies Last reply
              0
              • R Roger Wright

                Daniel Desormeaux wrote:

                I find it hard to blame the driver.

                Why? It's not the correct driver for the card. :doh: The important question is, does the connection work? Who cares what signal strength it's reporting if the functional part of the driver works?:-D

                "...a photo album is like Life, but flat and stuck to pages." - Shog9

                D Offline
                D Offline
                dandy72
                wrote on last edited by
                #8

                > Why? It's not the correct driver for the card. If I remember correctly, according to the forum discussions I was reading before deciding to try that driver, the chipset on that card is actually made by Ralink, not Linksys... > The important question is, does the connection work? Who cares what signal strength it's > reporting if the functional part of the driver works? The connection is up and down--not just the signal strength reported.

                M 1 Reply Last reply
                0
                • M mgama

                  I'm thinking the fluctuation may be caused by some compatibility issue with another piece of hardware or driver. I have two of the same WMP54G cards for my PCs, well technically one is a v4.0 and the other is a v4.1. My main PC had the same fluctuation problem (in addition to losing it's connection every ~3 hours). The other MCE PC had a rock solid signal strength & speed. After swapping the cards, and wiping both machines, the main PC still has the fluctuation & slow speeds (without the connection loss problem) while the MCE is still rock solid. I've seen similar problems with a video card - it ran really hot in one PC, and perfectly cool in another. Could be a motherboard issue, or something else completely. I'm glad my connection isn't going down every 3 hours, but still dreaming of reliable connections. I may end up running CAT5 around my house. I've had it with Linksys (don't get me started on the WRT54G-v5). [edit] I ended up using the Ralink driver on the MCE machine which has the rock solid connection since there weren't Vista drivers put out by Linksys. Ralink is the maker of the chipset used in the card, so I think you are safe there.

                  D Offline
                  D Offline
                  dandy72
                  wrote on last edited by
                  #9

                  > I've had it with Linksys (don't get me started on the WRT54G-v5). Sounds like we've both been at the same place! :-D > Ralink is the maker of the chipset used in the card, Yes, according to the posts I found before using their driver. > so I think you are safe there Others in this thread would disagree. I'll look for an alternate driver. Please keep me posted if the situation changes on your end.

                  M 1 Reply Last reply
                  0
                  • M mgama

                    I'm thinking the fluctuation may be caused by some compatibility issue with another piece of hardware or driver. I have two of the same WMP54G cards for my PCs, well technically one is a v4.0 and the other is a v4.1. My main PC had the same fluctuation problem (in addition to losing it's connection every ~3 hours). The other MCE PC had a rock solid signal strength & speed. After swapping the cards, and wiping both machines, the main PC still has the fluctuation & slow speeds (without the connection loss problem) while the MCE is still rock solid. I've seen similar problems with a video card - it ran really hot in one PC, and perfectly cool in another. Could be a motherboard issue, or something else completely. I'm glad my connection isn't going down every 3 hours, but still dreaming of reliable connections. I may end up running CAT5 around my house. I've had it with Linksys (don't get me started on the WRT54G-v5). [edit] I ended up using the Ralink driver on the MCE machine which has the rock solid connection since there weren't Vista drivers put out by Linksys. Ralink is the maker of the chipset used in the card, so I think you are safe there.

                    V Offline
                    V Offline
                    Vivek Rajan
                    wrote on last edited by
                    #10

                    If two cards have the same chipset, it does not mean their drivers are interchangeable. You are missing the most important part in the picture - the firmware. Most wireless cards are based on just a 2-3 chipsets (atheros/ lucent/ conexant). In some cases the drivers kinda of work because they usually write their firmware from a reference design, so they are similar.

                    D 1 Reply Last reply
                    0
                    • D dandy72

                      > I've had it with Linksys (don't get me started on the WRT54G-v5). Sounds like we've both been at the same place! :-D > Ralink is the maker of the chipset used in the card, Yes, according to the posts I found before using their driver. > so I think you are safe there Others in this thread would disagree. I'll look for an alternate driver. Please keep me posted if the situation changes on your end.

                      M Offline
                      M Offline
                      mgama
                      wrote on last edited by
                      #11

                      Daniel Desormeaux wrote:

                      Others in this thread would disagree.

                      Yeah, I'm sure they know more about drivers/firmware than me. I think for me, I had to install the Ralink software (whatever it was) then Vista could successfully install the Linksys driver. Without thw Ralink software, Vista failed to install the Linksys driver (which obviously sent me to the internet to find a solution that worked).

                      1 Reply Last reply
                      0
                      • D dandy72

                        > Why? It's not the correct driver for the card. If I remember correctly, according to the forum discussions I was reading before deciding to try that driver, the chipset on that card is actually made by Ralink, not Linksys... > The important question is, does the connection work? Who cares what signal strength it's > reporting if the functional part of the driver works? The connection is up and down--not just the signal strength reported.

                        M Offline
                        M Offline
                        Matt Newman
                        wrote on last edited by
                        #12

                        Just because Ralink made the chipset doesn't mean the card is exactly the same as their reference board.

                        Matt Newman
                        Even the very best tools in the hands of an idiot will produce something of little or no value. - Chris Meech on Idiots

                        1 Reply Last reply
                        0
                        • V Vivek Rajan

                          If two cards have the same chipset, it does not mean their drivers are interchangeable. You are missing the most important part in the picture - the firmware. Most wireless cards are based on just a 2-3 chipsets (atheros/ lucent/ conexant). In some cases the drivers kinda of work because they usually write their firmware from a reference design, so they are similar.

                          D Offline
                          D Offline
                          dandy72
                          wrote on last edited by
                          #13

                          The thing I probably should've mentioned was that those who made the initial suggestion claimed the driver worked fine with that card...hence my reluctance to simply blame the driver.

                          1 Reply Last reply
                          0
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • World
                          • Users
                          • Groups