ubuntu能搜索wifi,却不能连接部分wifi

本文记录了一次解决Linux系统中无线网络连接失败的问题过程。具体表现为系统尝试连接指定的Wi-Fi网络但最终因未找到SSID而失败。通过配置网络管理器并禁用特定的11n功能解决了此问题。

使用命令查看系统日志:less /var/log/syslog

  1. May 22 16:20:04 lan-PC console-kit-daemon[7092]: console-kit-daemon[7092]: GLib-CRITICAL: Source ID 16 was not found when attempting to remove it
  2. May 22 16:20:04 lan-PC console-kit-daemon[7092]: GLib-CRITICAL: Source ID 16 was not found when attempting to remove it
  3. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) starting connection 'English'
  4. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
  5. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
  6. May 22 16:20:08 lan-PC NetworkManager[813]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
  7. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
  8. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
  9. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
  10. May 22 16:20:08 lan-PC NetworkManager[813]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
  11. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0/wireless): access point 'English' has security, but secrets are required.
  12. May 22 16:20:08 lan-PC NetworkManager[813]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
  13. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
  14. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
  15. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
  16. May 22 16:20:08 lan-PC NetworkManager[813]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
  17. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
  18. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
  19. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
  20. May 22 16:20:08 lan-PC NetworkManager[813]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
  21. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0/wireless): connection 'English' has security, and secrets exist.  No new secrets needed.
  22. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Config: added 'ssid' value 'English'
  23. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Config: added 'scan_ssid' value '1'
  24. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
  25. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Config: added 'auth_alg' value 'OPEN'
  26. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Config: added 'psk' value '<omitted>'
  27. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
  28. May 22 16:20:08 lan-PC NetworkManager[813]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
  29. May 22 16:20:08 lan-PC NetworkManager[813]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
  30. May 22 16:20:08 lan-PC NetworkManager[813]: <info> Config: set interface ap_scan to 1
  31. May 22 16:20:34 lan-PC NetworkManager[813]: <warn> Activation (wlan0/wireless): association took too long, failing activation.
  32. May 22 16:20:34 lan-PC NetworkManager[813]: <info> (wlan0): device state change: config -> failed (reason 'ssid-not-found') [50 120 53]
  33. May 22 16:20:34 lan-PC NetworkManager[813]: <warn> Activation (wlan0) failed for connection 'English'
  34. May 22 16:20:34 lan-PC NetworkManager[813]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
  35. May 22 16:20:34 lan-PC NetworkManager[813]: <info> (wlan0): deactivating device (reason 'none') [0]
  36. May 22 16:20:34 lan-PC NetworkManager[813]: <info> (wlan0): supplicant interface state: scanning -> disconnected
  37. May 22 16:20:34 lan-PC NetworkManager[813]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
解决办法:sudo gedit /etc/modprobe.d/iwlwifi.conf
在文件末尾加入:options iwlwifi 11n_disable=1即可

Ubuntu 20.04系统安装完成后如果无法连接Wi-Fi,可能是由于驱动程序缺失、网络管理器配置错误或是其他原因导致的问题。以下是几种常见的解决方法: ### 检查硬件开关和键盘快捷键 首先确认笔记本电脑上的无线功能是否已经启用。部分设备需要手动打开物理按钮或按下组合键(如Fn + F某数字键)才能激活无线网卡。 ### 更新系统软件包 运行以下命令更新您的系统到最新状态: ```bash sudo apt update && sudo apt upgrade -y ``` 接着重启计算机查看是否有改善。 ### 安装正确的内核模块及固件支持 某些较新的无线适配器需要特定的Linux内核版本以及专有firmware文件的支持。通过终端输入下面指令检查当前是否存在未满足依赖项并尝试修复它们。 ```bash lsmod | grep wifi # 列出已加载的相关模块 dmesg | grep firmware # 查找日志里提到的任何关于firmware信息 sudo lshw -class network # 获取更详细的硬件规格描述 ``` 然后依据提示下载对应的deb二进制包或者是从官方源仓库拉取资源进行安装。 例如Intel系列芯片组可以执行这条语句自动获取所需组件: ```bash sudo apt install linux-firmware intel-microcode ``` 对于Broadcom品牌产品则推荐按照这个步骤操作: 1. 打开“软体&更新”应用 -> 其他驱动选项卡; 2. 在列表中选择合适的闭源解决方案(通常会有标明bcmwl-kernel-source字样),最后点击右侧的应用更改按钮完成设置过程即可恢复联网能力。 另外还可以单独利用apt工具直接引入目标服务端口: ```bash sudo apt-get install bumblebee-nvidia primus libnvidia-ifr1-535 libnvidia-gl-535 nvidia-driver-535 ``` > **注意**:以上例子仅供参考,请根据自己实际环境调整具体数值代号! 假如上述办法依旧无效的话,那大概率是因为主板内部集成了非主流标准协议类型的发射接收单元所致,在这种情形下我们只能借助USB转接头等外部配件作为临时替代措施了。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值