The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Vostro Wifi LED/light blinking

    Discussion in 'Dell' started by ddicecco, Feb 24, 2008.

  1. ddicecco

    ddicecco Notebook Enthusiast

    Reputations:
    8
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    5
    I posted this question in wireless/networking but maybe this is the more appropriate forum to get an answer.

    I recently replaced my stock Dell 1390 wireless card with a sparklan wireless-N card based on the atheros ar5008 chipset. The card works fine but the wifi light (the one near the caps/number/scroll-lock LEDs and the power button) that stayed lit when the dell card was in now blinks. This blinking does not indicate traffic like the LED on a router. It's supposed to stay on.

    Now, I know this may appear to be a cosmetic thing but it's really annoying having this light blinking over and over and over again. It seems to be an issue with the motherboard not liking the non-Dell hardware. Anyone have any suggestions on how to stop the blinking? I'd like it either to stay on or stay off. Either/or. Thanks in advance.
     
  2. lambchops468

    lambchops468 Notebook Evangelist

    Reputations:
    33
    Messages:
    325
    Likes Received:
    0
    Trophy Points:
    30
    believe it or not, the light is software driven - on linux, the driver can turn off the LED, and there is code that the cpu has to run to make the light turn on, blink, etc. i don't know if you can configure with atheros on windows.
     
  3. ddicecco

    ddicecco Notebook Enthusiast

    Reputations:
    8
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    5
    Wow.. I never would have guessed that. It does make sense though. I'm guessing it's a long shot to expect someone to develop a driver that would address an issue this minor. If anyone has any success in fixing this by any method, please pass the info on.