View previous topic :: View next topic |
Author |
Message |
markan n00b
Joined: 11 Aug 2013 Posts: 20
|
Posted: Sun Aug 11, 2013 7:58 pm Post subject: interface doesnt support scanning |
|
|
hi all
my network card was regonized and started
ifconfig -a and ifconfig shows it up
but "iwlist (interface) scanning" tells me that interface doesnt support scanning
maybe that is not problem, my biggest problem is when i run wicd it says:
no network interface found |
|
Back to top |
|
|
The Doctor Moderator
Joined: 27 Jul 2010 Posts: 2678
|
Posted: Sun Aug 11, 2013 8:23 pm Post subject: |
|
|
the output of ifconfig -a would be helpful.
If it has been detected, that suggests to me that you have the kernel module, but you don't have firmware. You can correct that using emerge -av linux-firmware. Indecently, as a general rule if it requires firmware it should be built as a module since some firmware is required to be loaded before the kernel module. _________________ First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
Back to top |
|
|
Princess Nell l33t
Joined: 15 Apr 2005 Posts: 916
|
Posted: Mon Aug 12, 2013 9:48 pm Post subject: |
|
|
Can you be more specific? I have the same problem as the OP.
In my case, the kernel config includes CONFIG_FIRMWARE_IN_KERNEL=y, but I just realised that I also have CONFIG_PREVENT_FIRMWARE_BUILD=y. However, the /lib/firmware directory looks nicely populated.
Wireless interface is working fine for connections. Abbreviated lspci/lsmod/equery:
Code: |
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
cfg80211 263800 3 iwlwifi,mac80211,iwldvm
sys-firmware/iwl6005-ucode-18.168.6.1
|
|
|
Back to top |
|
|
The Doctor Moderator
Joined: 27 Jul 2010 Posts: 2678
|
Posted: Tue Aug 13, 2013 2:12 am Post subject: |
|
|
If I recall correctly, /lib/firmware is where portage installs the firmware and the kernel looks for it, not where a kernel build puts it. In fact, I am fairly sure that that is where I pointed my kernel .config to look for the firmware to build in.
A kernel build includes it directly in the kernel. This is advantageous if your video requires firmware (lets say a radeon card) and your disks are fully encrypted. I don't know how those options interact, but quite probably you don't actually have the firmware built in.
As for why some modules need firmware first, I have no good explanation. I just know it is true. This is not the case with every driver, but enough so that it is a safer bet. _________________ First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
Back to top |
|
|
markan n00b
Joined: 11 Aug 2013 Posts: 20
|
Posted: Wed Aug 14, 2013 5:19 pm Post subject: |
|
|
thank you for help
i was have firmware, i dont know why then my device wasnt support scanning, it doesnt support it again
but iw connected to wireless via wicd preferences and than editi wired and wireless interfaces name there, after that wicd was found available networks |
|
Back to top |
|
|
Princess Nell l33t
Joined: 15 Apr 2005 Posts: 916
|
Posted: Fri Sep 27, 2013 11:01 pm Post subject: |
|
|
CONFIG_CFG80211_WEXT=y seems to have done the trick here. I probably didn't have it set because of the comment.
Quote: |
Enable this option if you need old userspace for wireless
extensions with cfg80211-based drivers.
|
|
|
Back to top |
|
|
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
Posted: Fri Sep 27, 2013 11:35 pm Post subject: |
|
|
Yeah, wicd is among the few things that still need the legacy cfg80211 option. wpa_supplicant on its own would've probably worked, though. |
|
Back to top |
|
|
|