LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-17-2014, 04:47 PM   #1
nix84
Member
 
Registered: Apr 2014
Posts: 276

Rep: Reputation: Disabled
Cannot bring interface up


While testing a script which takes wlan0 up/down, I've discovered that I can no longer access that interface. Example if I try to bring it up:
ifconfig wlan0 up
I get:
wlan0: unknown interface: No such device
BTW this is 13.37 system
The only way I have rectified the problem is rebooting. Is there a more gracious way of fixing this?
 
Old 05-18-2014, 04:53 AM   #2
FeyFre
Member
 
Registered: Jun 2010
Location: Ukraine, Vinnitsa
Distribution: Slackware
Posts: 351

Rep: Reputation: 30
It seem your script unloaded kernel module(driver) of that WiFi device, so no network devices was visible to network subsystem. During reboot, kernel/udev reloaded all drivers and so you got your interface. scripts who manage interfaces up/down generally must not to do it via removing unloading drivers.
 
Old 05-18-2014, 07:10 AM   #3
nix84
Member
 
Registered: Apr 2014
Posts: 276

Original Poster
Rep: Reputation: Disabled
I do wish UR conclusion were correct but feel that is not the case. The modprobe commands to remove and replace are at the very first of the scrip and were functioning well for several iterations of the script running. Then I was getting a hesitation at that point which got progressively longer to about 5 minutes. I could see something called rescue in the ps -ely listing but my list gets cut off at the right. I was able to kill -9 based on the ps list. Now this occurred previously too.
I have since posting search it further and see that ndiswrapper on other distros have this same problem until EnableAuto...(I forget) is changed from 1 to 0. I looked thru my ndiswrapper files but was not able to grep out that phrase. Hence I am wondering if running with ndiswrapper too many times in succession is the cause or if it is within the ndiswrapper itself. BTW I did a lsmod | grep ndiswrapper when this occurred and it was found. I failed to mention that not knowing its significance at the time.
 
  


Reply



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
bring interface physically down m4rtin Linux - Networking 1 12-08-2012 11:40 AM
cannot bring up bnep interface avalonit Linux - Networking 0 10-26-2010 04:53 AM
Failed to bring up <Interface> jose_tk Linux - Networking 1 11-04-2009 07:48 AM
What does ifup do to bring up an interface? crazyjimbo Linux - Networking 1 07-04-2006 01:00 AM
pppd: how to bring up an interface? J_Szucs Linux - Networking 2 08-08-2004 08:02 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:23 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
Open Source Consulting | Domain Registration