OpenWrt Forum Archive

Topic: File wireless missing

The content of this topic has been archived on 12 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Where do I download this file.

Thanks

/etc/config

nitroshift

no such file at that location

Just execute "wifi detect".

@eduperez

no effect

This, although there is a recent change which changes things to wifi config. If no output check for installed wifi driver(s).

Perhaps you should give us more information, like what device you own, which OpenWrt version you have installed, how did that file got lost, ...

@ Villeneuve

That was it, needed to find the right driver.

Thanks for the help smile

@ eduperez

I've solved the problem with the help I received from the form and you. It was a driver issue.

I was unable to post more verbose info on my problem, every time I tried to cut and paste command line output from my ssh terminal to this form I got this message.

"Warning! The following errors must be corrected before your message can be posted:
Too more links in message. Allowed 0 links. Reduce number of links and post it again."

Therefore cutting and pasting for example "lsmod | grep rtl" and it's output was not permitted for some reason. This slowed down the process of resolving this problem greatly.

This is an anti-spam feature.  New members can't post anything that starts with http.  But if you put code tags around it, which you should with any listing, it should be ok.

http://openwrt.org

Note that this is a URL, but it is not live and clickable because it is in a code block.

(Last edited by mk24 on 19 Feb 2017, 17:06)

@ mk24

Thanks that explains it, (palm to forehead).

mk24 wrote:

This is an anti-spam feature.  New members can't post anything that starts with http.  But if you put code tags around it, which you should with any listing, it should be ok.

http://openwrt.org

Note that this is a URL, but it is not live and clickable because it is in a code block.

That never worked for me... I still had to put ht.tp instead...

The discussion might have continued from here.