LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices



Reply
 
Search this Thread
Old 12-24-2005, 04:30 PM   #1
crouguer
LQ Newbie
 
Registered: Dec 2005
Posts: 3

Rep: Reputation: 0
belkin wireless card suddenly stops working


I've put together a computer whose function is to take an internet connection from wlan0 and broadcast it out via eth0... After a few days I got everything working with a Debian installation and all was well. I put the computer in my car and drove to my parents, where I wanted to set it up, and suddenly now that I get here, the wireless card has stopped working.

SPECIFICALLY:
Code:
#ndiswrapper -l:
rt2500 driver present, hardware present
Code:
#lsmod | grep ndis
ndiswrapper 119348 0
usbcore 104164 4 uhci_hcd,ndiswrapper
Code:
#iwconfig:
lo no wireless...
wlan0 IEEE 802.11g ESSID:off/any
      Mode: Auto Frequency:......... (you get the idea... let me know if you need more)
eth0 no wireless...
sit0 no wireless...
If I use iwconfig to try to connect to my router it doens't give any errors, but it also doesn't connect.... also, there are no lights working on the back of the wireless card... I've tried trading PCI slots with other devices... doesn't help

So does this mean that I somehow wrecked my wireless card on the way, or can anyone think of what might have happened and also, preferrably, ideas on fixing it...?

Thanks!

Nick
 
Old 12-25-2005, 02:45 AM   #2
Agentvenom
Member
 
Registered: Sep 2005
Distribution: PCLinuxOS 2007 / Suse 10.3
Posts: 228

Rep: Reputation: 30
Hummm, I bet if you ran "modprobe ndiswrapper" again as root, it would load the module again and you'd have wireless. You might have to run "ifup wlan0" right after as root to get an ip. (assuming wlan0 is your wireless) Probably the problem is that it's not loading the module on boot. When you're using ndiswrapper, "modprobe ndiswrapper" temporarily loads the module for your wireless so it works right away. However, in order for it to load after a reboot, you need to tell it to load the module you've installed on boot. I don't know exactly where to set this in Debian, but in Suse you can configure the wireless card to "start on boot" and set the eth0 or wired card to only come on "on cable connection" in the network configuration gui. I think most distibutions use /etc/modules to know what modules to load at boot. I'd check the bottom of this page: http://ndiswrapper.sourceforge.net/m...p/Installation Hope this helps!

Last edited by Agentvenom; 12-25-2005 at 02:51 AM.
 
Old 12-26-2005, 10:55 PM   #3
crouguer
LQ Newbie
 
Registered: Dec 2005
Posts: 3

Original Poster
Rep: Reputation: 0
Thanks, Agentvenom, for the reply... I'm afraid that's not it though - I believe that since ndiswrapper is listed when I give an lsmod command after startup it has indeed been loaded. Either way, I have tried rmmod'ing the ndiswrapper module and then re modprobing and it doesn't seem to help. I continue to have the sinking feeling that my hardware is to blame....
 
Old 12-27-2005, 12:54 AM   #4
Agentvenom
Member
 
Registered: Sep 2005
Distribution: PCLinuxOS 2007 / Suse 10.3
Posts: 228

Rep: Reputation: 30
Shame on me for not paying attention!!! However, it was 3 am. You are indeed correct. If lsmod shows ndiswrapper, then the module for the ndis driver should indeed be loaded. I'm not sure if faulty hardware is to blame or not. I don't know how just moving the computer could kill your hardware. In the few days that it was working, did you reboot the machine? Or the only time you shut it down was to move it?
 
Old 12-28-2005, 12:09 AM   #5
crouguer
LQ Newbie
 
Registered: Dec 2005
Posts: 3

Original Poster
Rep: Reputation: 0
I'm afraid that I rebooted the machine several times during the course of setting it up, having the network interfaces started manually at first, then testing them starting automatically. Since I was preparing this computer to be used as a router with no human intervention I was fairly thorough about testing.

I agree with you, though, I can't imagine what would have damaged only my wireless card on a trip... the card itself was new only a few days earlier though, so maybe I just got a dud. I think that I will have to return the card and try the whole thing again.
 
Old 12-28-2005, 01:59 AM   #6
Agentvenom
Member
 
Registered: Sep 2005
Distribution: PCLinuxOS 2007 / Suse 10.3
Posts: 228

Rep: Reputation: 30
If it's new, you can always return it and try again to at least eliminate one possibility. Stinks to start over though....good luck!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Network suddenly stops working, route freezes nfreeman Linux - Networking 2 10-12-2005 08:39 PM
Wireless card suddenly stops working michelbehr Linux - Wireless Networking 2 07-24-2005 02:29 PM
Java suddenly stops working Wynd Linux - Software 2 04-23-2005 02:20 PM
wireless card suddenly stoped working toships Linux - Newbie 2 03-01-2004 04:16 AM
Need help! Prism2 wireless card stops working, floods terminal with errors Electrode Linux - Wireless Networking 6 02-05-2003 11:37 PM


All times are GMT -5. The time now is 06:38 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration