Не могу включить wi-fi в Ubuntu/Mint
Ноутбук Asus X550C, просто не нажимается кнопка включить. Пробовал разные дистрибутивы в Debian и ElementaryOS все работает отлично, ставлю Ubuntu или Mint начинаются проблемы.
Странно что в ElementaryOS все работает ведь он тоже вроде основан на Ubuntu.
Скорее всего проблема в драйверах, что делать? Доступ к интернету есть прямую через сетевой рабоет.
iwconfig
eth0 no wireless extensions.
lo no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=off
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
2: asus-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
3: asus-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev a1)
03:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5289 (rev 01)
04:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a)
ifconfig
eth0 Link encap:Ethernet HWaddr ac:22:0b:1e:26:d8
inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::ae22:bff:fe1e:26d8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:183073 errors:0 dropped:0 overruns:0 frame:0
TX packets:99347 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:271035040 (271.0 MB) TX bytes:7158789 (7.1 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:330 errors:0 dropped:0 overruns:0 frame:0
TX packets:330 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:49444 (49.4 KB) TX bytes:49444 (49.4 KB)
iwconfig
eth0 no wireless extensions.
lo no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=off
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Чтобы убедиться, что проблема не в драйверах, настройте сеть вручную help.ubuntu.ru/wiki/%D0%BD%D0%B0%D1%81%D1%82%D1%80.
iwconfig indicates «no wireless extensions» for a working wifi card
I was trying to set-up a virtual wifi access point. To find my interface name I used iwconfig and it showed no wireless extensions even though I am able use my wifi card. using : Dell 1540 vostro Driver: Broadcom STA wireless driver (its an additional driver) iwconfig result:
lo no wireless extensions. eth1 IEEE 802.11abg ESSID:off/any Mode:Managed Access Point: Not-Associated Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off eth0 no wireless extensions. 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) 00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05) 00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 05) 00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) 12:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01) 13:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02) ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02) ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02) What is meant by no wireless extension?
Whenever I type iwconfig. Some of the network interface cards show no wireless extension. What does it possibly mean ?
It means that some of your network cards are not WiFi cards. If you have an ordinary Ethernet (i.e. cabled) network card, it would show up as having no wireless extension. Only your WiFi card(s) would give details.
2 Answers 2
Back in the 1990s, there wasn’t much of a standard about how the operating system and those new-fangled wireless networking devices were supposed to interact. Because of that, the operating system needed to «talk» to every device in a «different language», so to speak. Often, that was even true for different variations of the same device. So people needed to develop separate drivers for each and every wireless networking device.
At some point, a developer named Jean Tourrilhes decided to develop an interface, an API. With that, the operating system could address any wireless networking device (or at least, many devices) in an uniform manner. The API would then handle how the specific device would like to be «talked to». This API was named Wireless Extensions:
It all started when I tried to install a Wavelan network on Linux computers. I was having a ISA and a PCMCIA versions of the Wavelan, and the two drivers were using totally different methods for the setup and collection of statistics (and in fact fairly incomplete. ). (. ) I decided to define a wireless API which would allow the user to manipulate any wireless networking device in a standard and uniform way.
So, if iwconfig tells you there are «no wireless extensions» for a specific device, it means that this specific device cannot be addressed via the Wireless Extensions API. This may be because the device isn’t a wireless device, but a wire-bound device. This may be because the device is «virtual», like for example the loopback device. Or it may be because the wireless device in question isn’t compatible with the Wireless Extensions API.
The Wireless Extensions API isn’t being developed any more, but it’s superseded by newer approaches. So maybe your wireless networking device isn’t «covered» by the WE API, but will work with one of those newer technologies (and a different tool than iwconfig ).
iwconfig: wlan0 no wireless extensions
I’ve some problems with the wlan0 interface on an embedded linux distro (compiled with yocto). The problem is that when I use the command:
it works correctly! And it also works well if I use connman as connection manager instead of iwconfig . I’ve tried to get up the interfaces with the follow commands:
but when I checked the status of the file in /sys/class/net/wlan0/operstate the result is always «down». How can I solve this problem? i want that iwconfig recognize the wlan0 interface.
1 Answer 1
It sounds like either your kernel or the driver for the wireless interface will only support the newer cfg80211 configuration interface used by the iw tool, not the older wireless-extensions interface used by iwconfig .
Does your kernel configuration enable the CONFIG_WIRELESS_EXT option, and/or the CONFIG_CFG80211_WEXT option? The latter option will enable a compatibility layer that will allow old userspace programs like iwconfig to access the configuration of newer-style drivers.
Note that when you use ip link set wlan0 up or ifconfig wlan0 up you’ll be setting the administrative state of the interface, or basically the state the interface will want to be in. The /sys/class/net/wlan0/operstate tells you about the operational state of the interface, i.e. what state the interface has actually managed to achieve.
For a wired interface, the operational state changes to up basically reflects the state of the link LED of the interface: when the interface detects the link pulses from the other end (and successfully negotiates the connection speed and other parameters, if applicable), the link LED will light, and the operational state will change to up .
A wireless interface has no cable to plug in, so the equivalent task is associating with a wireless network (and completing any necessary authentication, if applicable). So you should first configure the wireless interface with a network with an ESSID and any necessary network passwords or authentication keys. If the wireless interface is out of range of the wireless AP or the authentication settings are not correct, the wireless interface won’t be able to actually transfer packets — and that’s what the operational state «down» means.