当前时区为 UTC + 8 小时



发表新帖 回复这个主题  [ 18 篇帖子 ]  前往页数 1, 2  下一页
作者 内容
1 楼 
 文章标题 : 神舟PCpad Plus WIFI 总是弹回输入密码BCM4356 (已解决)
帖子发表于 : 2017-03-29 12:24 

注册: 2017-03-29 12:04
帖子: 10
系统: ubuntu 16.10
送出感谢: 4
接收感谢: 0 次
先说说本人的经历,发行版的linux 我大多都安装过, kali ,ubuntu debain deepin 等等 都是一个问题,装完了系统之后WIFI连接不上, 有些 系统索性就检测不到wifi, 但是 lspci 里面却可以显示 有wifi

windows下 wifi驱动没问题,所以确定硬件是没问题的。 神舟官方也不给提供 linux的驱动, 实在是 没办法了 ,所以才来这个论坛,这个板块来求助!希望大家能帮助我解决WIFI 链接上的问题,

目前我使用的系统是ubuntu 16.10 网卡是博通BCM4356

我看了本论坛 一些关于wifi连接不上的其他帖子,网友们都列出了 如下代码, 方便查找问题所在。 我也列出以下
代码:
uname -a
lspci
sudo lshw -C network
iwconfig


代码:
uname -a
返回信息:Linux liukim-laptop 4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:15:00 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux


代码:
lspci
返回信息:00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5300 (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03)
01:00.0 Network controller: Broadcom Limited BCM4356 802.11ac Wireless Network Adapter (rev 02)


代码:
sudo lshw -C network
返回代码:  *-network                 
       description: Wireless interface
       product: BCM4356 802.11ac Wireless Network Adapter
       vendor: Broadcom Limited
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: wlp1s0
       version: 02
       serial: 94:a1:a2:85:16:26
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=brcmfmac driverversion=7.35.180.119 firmware=01-1a5c4016 latency=0 multicast=yes wireless=IEEE 802.11
       resources: irq:53 memory:f7400000-f7407fff memory:f7000000-f73fffff
  *-network
       description: Ethernet interface
       physical id: 2
       logical name: enx00e04c534458
       serial: 00:e0:4c:53:44:58
       size: 100Mbit/s
       capacity: 100Mbit/s
       capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=dm9601 driverversion=22-Aug-2005 duplex=full firmware=Davicom DM96xx USB 10/100 Ether ip=192.168.1.10 link=yes multicast=yes port=MII speed=100Mbit/s


代码:
iwconfig
返回信息:enx00e04c534458  no wireless extensions.

lo        no wireless extensions.

wlp1s0    IEEE 802.11  ESSID:off/any 
          Mode:Managed  Access Point: Not-Associated   Tx-Power=31 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
         


以上就是 所有信息了。希望神通广大的网友帮帮我!,万分感谢! 实在是没办法了 才来发帖求助!


最后由 liuki342166 编辑于 2017-03-30 11:51,总共编辑了 1 次

页首
 用户资料  
 
2 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-29 13:14 
头像

注册: 2007-12-14 13:40
帖子: 49905
地址: 志虚国乌由市
系统: Winbuntu
送出感谢: 29
接收感谢: 414
https://bbs.deepin.org/forum.php?mod=vi ... tid=134426
试试?


_________________
冷轩信

渠月 · QY

本人只会灌水,不负责回答问题

无聊可以点一下→ http://u.nu/ubuntu

安装flash 还是要用
代码:
sudo apt install adobe-flashplugin


页首
 用户资料  
 
3 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-29 13:43 

注册: 2017-03-29 12:04
帖子: 10
系统: ubuntu 16.10
送出感谢: 4
接收感谢: 0 次
正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
软件包 bcmwl-kernel-source 未安装,所以不会被卸载
升级了 0 个软件包,新安装了 0 个软件包,要卸载 0 个软件包,有 292 个软件包未被升级。
然后我尝试使用 apt install bcmwl-kernel-source
安装这个bcmwl-kernel-source,

root@liukim-laptop:~# apt install bcmwl-kernel-source
正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
将会同时安装下列软件:
dkms
下列【新】软件包将被安装:
bcmwl-kernel-source dkms
升级了 0 个软件包,新安装了 2 个软件包,要卸载 0 个软件包,有 292 个软件包未被升级。
需要下载 1,580 kB 的归档。
解压缩后会消耗 8,281 kB 的额外空间。
您希望继续执行吗? [Y/n] Y
获取:1 http://cn.archive.ubuntu.com/ubuntu yakkety/main amd64 dkms all 2.2.0.3-2ubuntu14 [66.0 kB]
获取:2 http://cn.archive.ubuntu.com/ubuntu yakkety/restricted amd64 bcmwl-kernel-source amd64 6.30.223.248+bdcom-0ubuntu11 [1,514 kB]
已下载 1,580 kB,耗时 2秒 (687 kB/s)
正在选中未选择的软件包 dkms。
(正在读取数据库 ... 系统当前共安装有 169590 个文件和目录。)
正准备解包 .../0-dkms_2.2.0.3-2ubuntu14_all.deb ...
正在解包 dkms (2.2.0.3-2ubuntu14) ...
进度:[ 86%] [###################################################........]
正准备解包 .../1-bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu11_amd64.deb ...
正在解包 bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu11) ...
正在设置 dkms (2.2.0.3-2ubuntu14) ...
正在处理用于 man-db (2.7.5-1) 的触发器 ...
正在设置 bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu11) ...
Loading new bcmwl-6.30.223.248+bdcom DKMS files...
First Installation: checking all kernels...
Building only for 4.8.0-22-generic
Building for architecture x86_64
Building initial module for 4.8.0-22-generic
Done.

wl:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.8.0-22-generic/updates/dkms/

depmod....

DKMS: install completed.
Segmentation fault
update-initramfs: deferring update (trigger activated)
正在处理用于 initramfs-tools (0.125ubuntu5) 的触发器 ...
update-initramfs: Generating /boot/initrd.img-4.8.0-22-generic
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915
root@liukim-laptop:~#

安装了apt install bcmwl-kernel-source 之后 发现 WIFI都不见了,我需要重启一下


页首
 用户资料  
 
4 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-29 13:51 

注册: 2017-03-29 12:04
帖子: 10
系统: ubuntu 16.10
送出感谢: 4
接收感谢: 0 次
qy117121 写道:
https://bbs.deepin.org/forum.php?mod=viewthread&tid=134426
试试?


谢谢你提供的办法, 我尝试了, 没有解决问题! 还是 能链, 但是一直 练级不上WIFI ! 总是弹出输入密码界面!


页首
 用户资料  
 
5 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-29 14:01 
头像

注册: 2007-12-14 13:40
帖子: 49905
地址: 志虚国乌由市
系统: Winbuntu
送出感谢: 29
接收感谢: 414
好吧,建议多搜索下,尤其是国外的网页


_________________
冷轩信

渠月 · QY

本人只会灌水,不负责回答问题

无聊可以点一下→ http://u.nu/ubuntu

安装flash 还是要用
代码:
sudo apt install adobe-flashplugin



_________________
评价: 3.7% liuki342166
 
页首
 用户资料  
 
6 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-29 14:15 
头像

注册: 2011-03-20 13:12
帖子: 4552
地址: 山东省寿光县
系统: Debian
送出感谢: 106
接收感谢: 1009
1. 打开一个终端
2. 在打开的终端中执行 sudo journalctl --no-pager -f,不要关闭此终端
3. 连接 wifi,等待弹回输入密码界面
4. 弹回输入密码界面后,在之前的终端中按 Ctrl+C,然后将其中的内容全部复制贴上来。不要截图或节选。


_________________
Debian 中文论坛 - forums.debiancn.org
欢迎所有 Debian GNU/Linux 用户



_________________
评价: 3.7% liuki342166
 
页首
 用户资料  
 
7 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-29 16:45 

注册: 2017-03-29 12:04
帖子: 10
系统: ubuntu 16.10
送出感谢: 4
接收感谢: 0 次
vickycq 写道:
1. 打开一个终端
2. 在打开的终端中执行 sudo journalctl --no-pager -f,不要关闭此终端
3. 连接 wifi,等待弹回输入密码界面
4. 弹回输入密码界面后,在之前的终端中按 Ctrl+C,然后将其中的内容全部复制贴上来。不要截图或节选。


感谢老哥提供的办法,内容如下,您这个命令类似于抓包吧! 但是我学习不经实在是看不明白- -我把从输入 这命令 开始-链接-弹回 的内容都复制上来了!

root@liukim-laptop:~# sudo journalctl --no-pager -f
-- Logs begin at 三 2017-03-29 16:38:08 CST. --
3月 29 16:41:47 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
3月 29 16:41:57 liukim-laptop compiz[2091]: ATTENTION: default value of option force_s3tc_enable overridden by environment.
3月 29 16:42:13 liukim-laptop compiz[2091]: WARN 2017-03-29 16:42:13 unity.iconloader IconLoader.cpp:264 Unable to load icon . GThemedIcon application-x-raw-disk-image application-x-generic at size 64
3月 29 16:42:13 liukim-laptop compiz[2091]: WARN 2017-03-29 16:42:13 unity.iconloader IconLoader.cpp:264 Unable to load icon . GThemedIcon application-x-gettext-translation application-x-generic at size 64
3月 29 16:42:14 liukim-laptop dbus-daemon[1538]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service'
3月 29 16:42:14 liukim-laptop systemd[1341]: Starting GNOME Terminal Server...
3月 29 16:42:14 liukim-laptop dbus-daemon[1538]: Successfully activated service 'org.gnome.Terminal'
3月 29 16:42:14 liukim-laptop systemd[1341]: Started GNOME Terminal Server.
3月 29 16:42:19 liukim-laptop sudo[3050]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/journalctl --no-pager -f
3月 29 16:42:19 liukim-laptop sudo[3050]: pam_unix(sudo:session): session opened for user root by (uid=0)
3月 29 16:42:21 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:21 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:21 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:21 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:22 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:22 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:22 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:22 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:22 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:22 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:22 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:22 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:22 liukim-laptop gnome-terminal-[3033]: Allocating size to GtkBox 0x560e35e447b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8820] device (wlp1s0): Activation: starting connection 'UCZOON-Office' (aaec4297-f470-4135-bbe3-4acd871036cb)
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8822] audit: op="connection-activate" uuid="aaec4297-f470-4135-bbe3-4acd871036cb" name="UCZOON-Office" pid=2283 uid=0 result="success"
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8823] device (wlp1s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8828] device (wlp1s0): state change: prepare -> config (reason 'none') [40 50 0]
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8831] device (wlp1s0): Activation: (wifi) access point 'UCZOON-Office' has security, but secrets are required.
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8831] device (wlp1s0): state change: config -> need-auth (reason 'none') [50 60 0]
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8926] device (wlp1s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8932] device (wlp1s0): state change: prepare -> config (reason 'none') [40 50 0]
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8936] device (wlp1s0): Activation: (wifi) connection 'UCZOON-Office' has security, and secrets exist. No new secrets needed.
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8937] Config: added 'ssid' value 'UCZOON-Office'
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8937] Config: added 'scan_ssid' value '1'
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8937] Config: added 'key_mgmt' value 'WPA-PSK'
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8937] Config: added 'psk' value '<omitted>'
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.8959] sup-iface[0x55df5d3a2a20,wlp1s0]: config: set interface ap_scan to 1
3月 29 16:42:27 liukim-laptop NetworkManager[759]: <info> [1490776947.9464] device (wlp1s0): supplicant interface state: inactive -> scanning
3月 29 16:42:28 liukim-laptop wpa_supplicant[1010]: wlp1s0: Trying to associate with SSID 'UCZOON-Office'
3月 29 16:42:28 liukim-laptop NetworkManager[759]: <info> [1490776948.4684] device (wlp1s0): supplicant interface state: scanning -> associating
3月 29 16:42:29 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 16:42:29 liukim-laptop NetworkManager[759]: <info> [1490776949.3085] device (wlp1s0): supplicant interface state: associating -> disconnected
3月 29 16:42:29 liukim-laptop NetworkManager[759]: <info> [1490776949.4089] device (wlp1s0): supplicant interface state: disconnected -> scanning
3月 29 16:42:29 liukim-laptop wpa_supplicant[1010]: wlp1s0: Trying to associate with SSID 'UCZOON-Office'
3月 29 16:42:29 liukim-laptop NetworkManager[759]: <info> [1490776949.5181] device (wlp1s0): supplicant interface state: scanning -> associating
3月 29 16:42:30 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 16:42:30 liukim-laptop NetworkManager[759]: <info> [1490776950.2384] device (wlp1s0): supplicant interface state: associating -> disconnected
3月 29 16:42:31 liukim-laptop NetworkManager[759]: <info> [1490776951.2743] device (wlp1s0): supplicant interface state: disconnected -> scanning
3月 29 16:42:31 liukim-laptop wpa_supplicant[1010]: wlp1s0: Trying to associate with SSID 'UCZOON-Office'
3月 29 16:42:31 liukim-laptop NetworkManager[759]: <info> [1490776951.7581] device (wlp1s0): supplicant interface state: scanning -> associating
3月 29 16:42:32 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 16:42:32 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="UCZOON-Office" auth_failures=1 duration=10 reason=CONN_FAILED
3月 29 16:42:32 liukim-laptop NetworkManager[759]: <info> [1490776952.3666] device (wlp1s0): supplicant interface state: associating -> disconnected
3月 29 16:42:37 liukim-laptop NetworkManager[759]: <info> [1490776957.4073] device (wlp1s0): supplicant interface state: disconnected -> scanning
3月 29 16:42:53 liukim-laptop NetworkManager[759]: <warn> [1490776973.5102] device (wlp1s0): Activation: (wifi) association took too long
3月 29 16:42:53 liukim-laptop NetworkManager[759]: <info> [1490776973.5103] device (wlp1s0): state change: config -> need-auth (reason 'none') [50 60 0]
3月 29 16:42:53 liukim-laptop NetworkManager[759]: <warn> [1490776973.5128] device (wlp1s0): Activation: (wifi) asking for new secrets
3月 29 16:42:53 liukim-laptop nm-applet[2283]: No keyring secrets found for UCZOON-Office/802-11-wireless-security; asking user.
3月 29 16:42:54 liukim-laptop nm-applet[2283]: GtkDialog mapped without a transient parent. This is discouraged.
3月 29 16:42:54 liukim-laptop dbus[730]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
3月 29 16:42:54 liukim-laptop systemd[1]: Starting Hostname Service...
3月 29 16:42:54 liukim-laptop NetworkManager[759]: <info> [1490776974.5226] device (wlp1s0): supplicant interface state: scanning -> inactive
3月 29 16:42:54 liukim-laptop dbus[730]: [system] Successfully activated service 'org.freedesktop.hostname1'
3月 29 16:42:54 liukim-laptop systemd[1]: Started Hostname Service.
^C


页首
 用户资料  
 
8 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-29 17:00 
头像

注册: 2011-03-20 13:12
帖子: 4552
地址: 山东省寿光县
系统: Debian
送出感谢: 106
接收感谢: 1009
liuki342166 写道:
3月 29 16:42:32 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 16:42:32 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="UCZOON-Office" auth_failures=1 duration=10 reason=CONN_FAILED

从日志来看,应该是认证错误。比如密码错误,加密类型错误,认证方式错误等。
除 UCZOON-Office 外的其它热点能否连接?可用手机共享热点尝试连接。
看 SSID 名称,连接的应该是工作场所的热点,有可能不是常见的 WPA2-PSK (TKIP/AES)。建议咨询网管或同事。

另一种可能是固件问题。先撤销3楼的操作(移除 bcmwl-kernel-source),再从 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm 下载 brcmfmac4356-pcie.bin 替换 /lib/firmware/brcm/brcmfmac4356-pcie.bin


_________________
Debian 中文论坛 - forums.debiancn.org
欢迎所有 Debian GNU/Linux 用户



_________________
评价: 3.7% liuki342166
 
页首
 用户资料  
 
9 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-29 17:16 

注册: 2017-03-29 12:04
帖子: 10
系统: ubuntu 16.10
送出感谢: 4
接收感谢: 0 次
vickycq 写道:
liuki342166 写道:
3月 29 16:42:32 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 16:42:32 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="UCZOON-Office" auth_failures=1 duration=10 reason=CONN_FAILED

从日志来看,应该是认证错误。比如密码错误,加密类型错误,认证方式错误等。
除 UCZOON-Office 外的其它热点能否连接?可用手机共享热点尝试连接。
看 SSID 名称,连接的应该是工作场所的热点,有可能不是常见的 WPA2-PSK (TKIP/AES)。建议咨询网管或同事。


谢谢分析, 我现在尝试 使用手机热点进行链接,测试2个方案,麻烦您在给分析一下日志,辛苦了!
1.手机热点,加密方式:“无”
root@liukim-laptop:~# sudo journalctl --no-pager -f
-- Logs begin at 三 2017-03-29 16:38:08 CST. --
3月 29 17:02:55 liukim-laptop systemd[1]: snapd.refresh.timer: Adding 19min 36.990329s random time.
3月 29 17:03:43 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
3月 29 17:04:46 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
3月 29 17:05:49 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
3月 29 17:06:52 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
3月 29 17:07:55 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
3月 29 17:08:58 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
3月 29 17:10:01 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
3月 29 17:10:51 liukim-laptop sudo[3397]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/journalctl --no-pager -f
3月 29 17:10:51 liukim-laptop sudo[3397]: pam_unix(sudo:session): session opened for user root by (uid=0)
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4290] keyfile: add connection in-memory (b85324a9-b8db-45b6-aa27-0bd2a4da27a2,"k")
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4306] device (wlp1s0): Activation: starting connection 'k' (b85324a9-b8db-45b6-aa27-0bd2a4da27a2)
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4311] keyfile: update /etc/NetworkManager/system-connections/k (b85324a9-b8db-45b6-aa27-0bd2a4da27a2,"k") and persist connection
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4312] audit: op="connection-add-activate" uuid="b85324a9-b8db-45b6-aa27-0bd2a4da27a2" name="k" pid=2283 uid=0 result="success"
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4320] device (wlp1s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4327] device (wlp1s0): state change: prepare -> config (reason 'none') [40 50 0]
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4333] device (wlp1s0): Activation: (wifi) connection 'k' requires no security. No secrets needed.
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4334] Config: added 'ssid' value 'k'
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4334] Config: added 'scan_ssid' value '1'
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4334] Config: added 'key_mgmt' value 'NONE'
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4366] sup-iface[0x55df5d3a2a20,wlp1s0]: config: set interface ap_scan to 1
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.4774] device (wlp1s0): supplicant interface state: inactive -> scanning
3月 29 17:10:57 liukim-laptop wpa_supplicant[1010]: wlp1s0: Trying to associate with SSID 'k'
3月 29 17:10:57 liukim-laptop NetworkManager[759]: <info> [1490778657.9970] device (wlp1s0): supplicant interface state: scanning -> associating
3月 29 17:10:58 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 17:10:58 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="k" auth_failures=1 duration=10 reason=CONN_FAILED
3月 29 17:10:58 liukim-laptop NetworkManager[759]: <info> [1490778658.7521] device (wlp1s0): supplicant interface state: associating -> disconnected
3月 29 17:11:08 liukim-laptop NetworkManager[759]: <info> [1490778668.7952] device (wlp1s0): supplicant interface state: disconnected -> scanning
3月 29 17:11:09 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="k"
3月 29 17:11:09 liukim-laptop wpa_supplicant[1010]: wlp1s0: Trying to associate with SSID 'k'
3月 29 17:11:09 liukim-laptop NetworkManager[759]: <info> [1490778669.3120] device (wlp1s0): supplicant interface state: scanning -> associating
3月 29 17:11:09 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 17:11:09 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="k" auth_failures=2 duration=20 reason=CONN_FAILED
3月 29 17:11:09 liukim-laptop NetworkManager[759]: <info> [1490778669.8970] device (wlp1s0): supplicant interface state: associating -> disconnected
3月 29 17:11:19 liukim-laptop NetworkManager[759]: <info> [1490778679.9347] device (wlp1s0): supplicant interface state: disconnected -> scanning
3月 29 17:11:22 liukim-laptop NetworkManager[759]: <warn> [1490778682.5101] device (wlp1s0): Activation: (wifi) association took too long, failing activation
3月 29 17:11:22 liukim-laptop NetworkManager[759]: <info> [1490778682.5101] device (wlp1s0): state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
3月 29 17:11:22 liukim-laptop NetworkManager[759]: <warn> [1490778682.5107] device (wlp1s0): Activation: failed for connection 'k'
3月 29 17:11:22 liukim-laptop NetworkManager[759]: <info> [1490778682.5313] device (wlp1s0): state change: failed -> disconnected (reason 'none') [120 30 0]
3月 29 17:11:22 liukim-laptop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
3月 29 17:11:23 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
3月 29 17:11:23 liukim-laptop NetworkManager[759]: <info> [1490778683.0614] device (wlp1s0): supplicant interface state: scanning -> inactive
3月 29 17:11:23 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
^C
root@liukim-laptop:~#
最后提示的是 “断开链接”

2.手机热点,加密方式:”WPA2 PSK“
root@liukim-laptop:~# sudo journalctl --no-pager -f
-- Logs begin at 三 2017-03-29 16:38:08 CST. --
3月 29 17:14:08 liukim-laptop dbus[730]: [system] Successfully activated service 'org.freedesktop.hostname1'
3月 29 17:14:08 liukim-laptop systemd[1]: Started Hostname Service.
3月 29 17:14:10 liukim-laptop NetworkManager[759]: <warn> [1490778850.6722] device (wlp1s0): User canceled the secrets request.
3月 29 17:14:10 liukim-laptop NetworkManager[759]: <info> [1490778850.6723] device (wlp1s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
3月 29 17:14:10 liukim-laptop NetworkManager[759]: <warn> [1490778850.6734] device (wlp1s0): Activation: failed for connection 'k 1'
3月 29 17:14:10 liukim-laptop NetworkManager[759]: <info> [1490778850.6971] device (wlp1s0): state change: failed -> disconnected (reason 'none') [120 30 0]
3月 29 17:14:10 liukim-laptop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
3月 29 17:14:16 liukim-laptop sudo[3460]: pam_unix(sudo:session): session closed for user root
3月 29 17:14:19 liukim-laptop sudo[3546]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/journalctl --no-pager -f
3月 29 17:14:19 liukim-laptop sudo[3546]: pam_unix(sudo:session): session opened for user root by (uid=0)
3月 29 17:14:23 liukim-laptop NetworkManager[759]: <info> [1490778863.6589] device (wlp1s0): Activation: starting connection 'k 1' (464a4638-2d71-4e61-8154-e3cdcbd8a737)
3月 29 17:14:23 liukim-laptop NetworkManager[759]: <info> [1490778863.6591] audit: op="connection-activate" uuid="464a4638-2d71-4e61-8154-e3cdcbd8a737" name="k 1" pid=2283 uid=0 result="success"
3月 29 17:14:23 liukim-laptop NetworkManager[759]: <info> [1490778863.6595] device (wlp1s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
3月 29 17:14:23 liukim-laptop NetworkManager[759]: <info> [1490778863.6603] device (wlp1s0): state change: prepare -> config (reason 'none') [40 50 0]
3月 29 17:14:23 liukim-laptop NetworkManager[759]: <info> [1490778863.6609] device (wlp1s0): Activation: (wifi) access point 'k 1' has security, but secrets are required.
3月 29 17:14:23 liukim-laptop NetworkManager[759]: <info> [1490778863.6610] device (wlp1s0): state change: config -> need-auth (reason 'none') [50 60 0]
3月 29 17:14:23 liukim-laptop nm-applet[2283]: No keyring secrets found for k 1/802-11-wireless-security; asking user.
3月 29 17:14:24 liukim-laptop nm-applet[2283]: GtkDialog mapped without a transient parent. This is discouraged.
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.2445] keyfile: update /etc/NetworkManager/system-connections/k 1 (464a4638-2d71-4e61-8154-e3cdcbd8a737,"k 1")
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.2476] device (wlp1s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.2485] device (wlp1s0): state change: prepare -> config (reason 'none') [40 50 0]
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.2492] device (wlp1s0): Activation: (wifi) connection 'k 1' has security, and secrets exist. No new secrets needed.
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.2496] Config: added 'ssid' value 'k'
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.2500] Config: added 'scan_ssid' value '1'
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.2503] Config: added 'key_mgmt' value 'WPA-PSK'
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.2504] Config: added 'auth_alg' value 'OPEN'
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.2504] Config: added 'psk' value '<omitted>'
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.2515] sup-iface[0x55df5d3a2a20,wlp1s0]: config: set interface ap_scan to 1
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.3024] device (wlp1s0): supplicant interface state: disconnected -> scanning
3月 29 17:14:31 liukim-laptop wpa_supplicant[1010]: wlp1s0: Trying to associate with SSID 'k'
3月 29 17:14:31 liukim-laptop NetworkManager[759]: <info> [1490778871.8253] device (wlp1s0): supplicant interface state: scanning -> associating
3月 29 17:14:32 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 17:14:32 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="k" auth_failures=1 duration=10 reason=CONN_FAILED
3月 29 17:14:32 liukim-laptop NetworkManager[759]: <info> [1490778872.4100] device (wlp1s0): supplicant interface state: associating -> disconnected
3月 29 17:14:42 liukim-laptop NetworkManager[759]: <info> [1490778882.4462] device (wlp1s0): supplicant interface state: disconnected -> scanning
3月 29 17:14:42 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="k"
3月 29 17:14:42 liukim-laptop wpa_supplicant[1010]: wlp1s0: Trying to associate with SSID 'k'
3月 29 17:14:42 liukim-laptop NetworkManager[759]: <info> [1490778882.9675] device (wlp1s0): supplicant interface state: scanning -> associating
3月 29 17:14:43 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 17:14:43 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="k" auth_failures=2 duration=20 reason=CONN_FAILED
3月 29 17:14:43 liukim-laptop NetworkManager[759]: <info> [1490778883.4476] device (wlp1s0): supplicant interface state: associating -> disconnected
3月 29 17:14:53 liukim-laptop NetworkManager[759]: <info> [1490778893.4849] device (wlp1s0): supplicant interface state: disconnected -> scanning
3月 29 17:14:56 liukim-laptop NetworkManager[759]: <warn> [1490778896.5111] device (wlp1s0): Activation: (wifi) association took too long
3月 29 17:14:56 liukim-laptop NetworkManager[759]: <info> [1490778896.5111] device (wlp1s0): state change: config -> need-auth (reason 'none') [50 60 0]
3月 29 17:14:56 liukim-laptop NetworkManager[759]: <warn> [1490778896.5147] device (wlp1s0): Activation: (wifi) asking for new secrets
3月 29 17:14:56 liukim-laptop nm-applet[2283]: No keyring secrets found for k 1/802-11-wireless-security; asking user.
3月 29 17:14:57 liukim-laptop nm-applet[2283]: GtkDialog mapped without a transient parent. This is discouraged.
3月 29 17:14:57 liukim-laptop dbus[730]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
3月 29 17:14:57 liukim-laptop systemd[1]: Starting Hostname Service...
3月 29 17:14:57 liukim-laptop NetworkManager[759]: <info> [1490778897.5250] device (wlp1s0): supplicant interface state: scanning -> inactive
3月 29 17:14:57 liukim-laptop dbus[730]: [system] Successfully activated service 'org.freedesktop.hostname1'
3月 29 17:14:57 liukim-laptop systemd[1]: Started Hostname Service.
3月 29 17:15:01 liukim-laptop NetworkManager[759]: <warn> [1490778901.7718] device (wlp1s0): User canceled the secrets request.
3月 29 17:15:01 liukim-laptop NetworkManager[759]: <info> [1490778901.7719] device (wlp1s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
3月 29 17:15:01 liukim-laptop NetworkManager[759]: <warn> [1490778901.7728] device (wlp1s0): Activation: failed for connection 'k 1'
3月 29 17:15:01 liukim-laptop NetworkManager[759]: <info> [1490778901.7736] device (wlp1s0): state change: failed -> disconnected (reason 'none') [120 30 0]
3月 29 17:15:01 liukim-laptop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
3月 29 17:15:02 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
3月 29 17:15:06 liukim-laptop wpa_supplicant[1010]: wlp1s0: Failed to initiate sched scan
^C


页首
 用户资料  
 
10 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-29 18:02 

注册: 2017-03-29 12:04
帖子: 10
系统: ubuntu 16.10
送出感谢: 4
接收感谢: 0 次
vickycq 写道:
liuki342166 写道:
3月 29 16:42:32 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 16:42:32 liukim-laptop wpa_supplicant[1010]: wlp1s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="UCZOON-Office" auth_failures=1 duration=10 reason=CONN_FAILED

从日志来看,应该是认证错误。比如密码错误,加密类型错误,认证方式错误等。
除 UCZOON-Office 外的其它热点能否连接?可用手机共享热点尝试连接。
看 SSID 名称,连接的应该是工作场所的热点,有可能不是常见的 WPA2-PSK (TKIP/AES)。建议咨询网管或同事。

另一种可能是固件问题。先撤销3楼的操作(移除 bcmwl-kernel-source),再从 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm 下载 brcmfmac4356-pcie.bin 替换 /lib/firmware/brcm/brcmfmac4356-pcie.bin


关于您说的第二种方法,我理解为 先安装 bcmwl-kernel-source 然后再替换brcmfac4356pcie.bin

有一个现象,就是我安装了 bcmwl-kernel-source 之后WIFI 就关闭了,无法打开, 重启也没用。 想链接WIFI 必须卸载 bcmwl-kernel-source 这个程序,

然后下面是 替换了 4356pcie.bin 的 一个截图 您帮忙看一我, 我能保证密码 没问题。是正确的, 关键是前面手机热点没密码, 也无法连接上,说不通呀,我开考虑可能是主板bios的问题, 我也看不太明白,把wlress有关的选项都打开了,最后还是 连不上wifi的结果, 我曾怀疑是驱动问题, 但现在也不知道是什么问题了。
root@liukim-laptop:~# sudo journalctl --no-pager -f
-- Logs begin at 三 2017-03-29 17:55:04 CST. --
3月 29 17:59:38 liukim-laptop unity-scope-loa[2959]: protocol-scope-discovery.vala:543: Number of elements of OptionIDs doesn't match OptionNames (7 vs 14)
3月 29 17:59:38 liukim-laptop unity-scope-loa[2959]: protocol-scope-discovery.vala:543: Number of elements of OptionIDs doesn't match OptionNames (18 vs 36)
3月 29 17:59:38 liukim-laptop unity-scope-loa[2959]: protocol-scope-discovery.vala:543: Number of elements of OptionIDs doesn't match OptionNames (4 vs 8)
3月 29 17:59:40 liukim-laptop dbus-daemon[1369]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service'
3月 29 17:59:40 liukim-laptop systemd[1343]: Starting GNOME Terminal Server...
3月 29 17:59:40 liukim-laptop dbus-daemon[1369]: Successfully activated service 'org.gnome.Terminal'
3月 29 17:59:40 liukim-laptop systemd[1343]: Started GNOME Terminal Server.
3月 29 17:59:42 liukim-laptop wpa_supplicant[977]: wlp1s0: Failed to initiate sched scan
3月 29 17:59:43 liukim-laptop sudo[3025]: root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/journalctl --no-pager -f
3月 29 17:59:43 liukim-laptop sudo[3025]: pam_unix(sudo:session): session opened for user root by (uid=0)
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7430] device (wlp1s0): Activation: starting connection 'UCZOON-Office' (aaec4297-f470-4135-bbe3-4acd871036cb)
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7431] audit: op="connection-activate" uuid="aaec4297-f470-4135-bbe3-4acd871036cb" name="UCZOON-Office" pid=2001 uid=0 result="success"
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7433] device (wlp1s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7439] device (wlp1s0): state change: prepare -> config (reason 'none') [40 50 0]
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7443] device (wlp1s0): Activation: (wifi) access point 'UCZOON-Office' has security, but secrets are required.
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7443] device (wlp1s0): state change: config -> need-auth (reason 'none') [50 60 0]
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7490] device (wlp1s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7499] device (wlp1s0): state change: prepare -> config (reason 'none') [40 50 0]
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7505] device (wlp1s0): Activation: (wifi) connection 'UCZOON-Office' has security, and secrets exist. No new secrets needed.
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7509] Config: added 'ssid' value 'UCZOON-Office'
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7512] Config: added 'scan_ssid' value '1'
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7515] Config: added 'key_mgmt' value 'WPA-PSK'
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7518] Config: added 'psk' value '<omitted>'
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.7530] sup-iface[0x55ac753c5890,wlp1s0]: config: set interface ap_scan to 1
3月 29 17:59:46 liukim-laptop wpa_supplicant[977]: wlp1s0: Trying to associate with SSID 'UCZOON-Office'
3月 29 17:59:46 liukim-laptop NetworkManager[723]: <info> [1490781586.8065] device (wlp1s0): supplicant interface state: inactive -> associating
3月 29 17:59:47 liukim-laptop wpa_supplicant[977]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 17:59:47 liukim-laptop wpa_supplicant[977]: wlp1s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="UCZOON-Office" auth_failures=1 duration=10 reason=CONN_FAILED
3月 29 17:59:47 liukim-laptop NetworkManager[723]: <info> [1490781587.2853] device (wlp1s0): supplicant interface state: associating -> disconnected
3月 29 17:59:49 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:49 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:49 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:49 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:50 liukim-laptop gnome-terminal-[3004]: Allocating size to GtkBox 0x55f6a36df7b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3月 29 17:59:57 liukim-laptop NetworkManager[723]: <info> [1490781597.3217] device (wlp1s0): supplicant interface state: disconnected -> scanning
3月 29 17:59:57 liukim-laptop wpa_supplicant[977]: wlp1s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="UCZOON-Office"
3月 29 17:59:57 liukim-laptop wpa_supplicant[977]: wlp1s0: Trying to associate with SSID 'UCZOON-Office'
3月 29 17:59:57 liukim-laptop NetworkManager[723]: <info> [1490781597.4092] device (wlp1s0): supplicant interface state: scanning -> associating
3月 29 17:59:57 liukim-laptop wpa_supplicant[977]: wlp1s0: CTRL-EVENT-ASSOC-REJECT status_code=16
3月 29 17:59:57 liukim-laptop wpa_supplicant[977]: wlp1s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="UCZOON-Office" auth_failures=2 duration=20 reason=CONN_FAILED
3月 29 17:59:57 liukim-laptop NetworkManager[723]: <info> [1490781597.9690] device (wlp1s0): supplicant interface state: associating -> disconnected
3月 29 18:00:08 liukim-laptop NetworkManager[723]: <info> [1490781608.0049] device (wlp1s0): supplicant interface state: disconnected -> scanning
3月 29 18:00:12 liukim-laptop NetworkManager[723]: <warn> [1490781612.4809] device (wlp1s0): Activation: (wifi) association took too long
3月 29 18:00:12 liukim-laptop NetworkManager[723]: <info> [1490781612.4810] device (wlp1s0): state change: config -> need-auth (reason 'none') [50 60 0]
3月 29 18:00:12 liukim-laptop NetworkManager[723]: <warn> [1490781612.4835] device (wlp1s0): Activation: (wifi) asking for new secrets
3月 29 18:00:12 liukim-laptop nm-applet[2001]: No keyring secrets found for UCZOON-Office/802-11-wireless-security; asking user.
3月 29 18:00:13 liukim-laptop nm-applet[2001]: GtkDialog mapped without a transient parent. This is discouraged.
3月 29 18:00:13 liukim-laptop dbus[699]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
3月 29 18:00:13 liukim-laptop systemd[1]: Starting Hostname Service...
3月 29 18:00:13 liukim-laptop dbus[699]: [system] Successfully activated service 'org.freedesktop.hostname1'
3月 29 18:00:13 liukim-laptop systemd[1]: Started Hostname Service.
3月 29 18:00:13 liukim-laptop NetworkManager[723]: <info> [1490781613.4941] device (wlp1s0): supplicant interface state: scanning -> inactive
^C


页首
 用户资料  
 
11 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-29 19:15 

注册: 2017-03-29 12:04
帖子: 10
系统: ubuntu 16.10
送出感谢: 4
接收感谢: 0 次
而且这个bcm4356在我的pcpadplus平板上还很难用,我在windows环境下只能使用官方提供的无线网卡驱动,如果用鲁大师之类的驱动更新软件,就会出现现在这个问题,链接wifi一直断,联想的电脑也有使用bcm4356这块网卡的安装linux.就没问题,所以我怀疑是bios有问题。而且从这款平板处理器型号来讲是支持安卓的。。bios里面一大堆设置。我都看不懂...回家以后我打算把windows的驱动发上来研究一下。。


页首
 用户资料  
 
12 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-29 21:51 
头像

注册: 2011-03-20 13:12
帖子: 4552
地址: 山东省寿光县
系统: Debian
送出感谢: 106
接收感谢: 1009
liuki342166 写道:
有一个现象,就是我安装了 bcmwl-kernel-source 之后WIFI 就关闭了,无法打开, 重启也没用。 想链接WIFI 必须卸载 bcmwl-kernel-source 这个程序

bcmwl-kernel-source 提供的是官方私有驱动 wl,可能不支持 BCM4356。

liuki342166 写道:
关于您说的第二种方法,我理解为 先安装 bcmwl-kernel-source 然后再替换brcmfac4356pcie.bin

是先卸载 bcmwl-kernel-source (即保证这个包没有安装) 然后再替换 brcmfmac4356-pcie.bin。
卸载 bcmwl-kernel-source 后,会自动恢复到自带的开源驱动 brcmfmac,正好配合固件 brcmfmac4356-pcie.bin 使用。而 bcmwl-kernel-source 提供的是官方私有驱动 wl,与此固件没关系。

liuki342166 写道:
所以我怀疑是bios有问题

也可能是 BCM4356 较新,驱动不完善。可以试试其它版本的固件。
https://mirrors.tuna.tsinghua.edu.cn/ubuntu/pool/main/l/linux-firmware/ 下载 1.149 以后(1.149 ~ 1.164)的 deb 包。下载之后解压,找到 lib/firmware/brcm/brcmfmac4356-pcie.bin,替换系统中的 /lib/firmware/brcm/brcmfmac4356-pcie.bin。重新启动计算机。重新启动计算机后可立刻执行以下指令看有无与固件有关的错误信息。
代码:
sudo dmesg | grep brcm


_________________
Debian 中文论坛 - forums.debiancn.org
欢迎所有 Debian GNU/Linux 用户



_________________
评价: 3.7% liuki342166
 
页首
 用户资料  
 
13 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-30 9:52 

注册: 2017-03-29 12:04
帖子: 10
系统: ubuntu 16.10
送出感谢: 4
接收感谢: 0 次
vickycq 写道:
liuki342166 写道:
有一个现象,就是我安装了 bcmwl-kernel-source 之后WIFI 就关闭了,无法打开, 重启也没用。 想链接WIFI 必须卸载 bcmwl-kernel-source 这个程序

bcmwl-kernel-source 提供的是官方私有驱动 wl,可能不支持 BCM4356。

liuki342166 写道:
关于您说的第二种方法,我理解为 先安装 bcmwl-kernel-source 然后再替换brcmfac4356pcie.bin

是先卸载 bcmwl-kernel-source (即保证这个包没有安装) 然后再替换 brcmfm啊ac4356-pcie.bin。
卸载 bcmwl-kernel-source 后,会自动恢复到自带的开源驱动 brcmfmac,正好配合固件 brcmfmac4356-pcie.bin 使用。而 bcmwl-kernel-source 提供的是官方私有驱动 wl,与此固件没关系。

liuki342166 写道:
所以我怀疑是bios有问题

也可能是 BCM4356 较新,驱动不完善。可以试试其它版本的固件。
https://mirrors.tuna.tsinghua.edu.cn/ubuntu/pool/main/l/linux-firmware/ 下载 1.149 以后(1.149 ~ 1.164)的 deb 包。下载之后解压,找到 lib/firmware/brcm/brcmfmac4356-pcie.bin,替换系统中的 /lib/firmware/brcm/brcmfmac4356-pcie.bin。重新启动计算机。重新启动计算机后可立刻执行以下指令看有无与固件有关的错误信息。
代码:
sudo dmesg | grep brcm


昨天晚上我在神舟官方提供的驱动(实测是windows8、8.1、10通用的)里面找到 “4356a2rtecdc.bin” 这个文件,我用winhex加载了一下文件,发现和 “brcmfmac4356-pcie.bin” 相同,我急中生智,把“4356a2rtecdc.bin”文件改名成brcmfmac4356-pcie.bin ,并且替换到系统 目录里“/lib/firmware/brcm/” 重启计算机后,还是 出现回弹问题。
我的平板,正面用吸盘 吸出来屏幕就可以, 我看到 无线网卡是焊接 在主板上的, 还有2个 NGFF 2242 规格的插槽, 一个插入的是威刚256SSD,一个是空的/。 我索性科普里一下 NGFF 规格相关知识,发现大部分的NGFF网卡都是2230规格的,而我的预留ngff插槽应该是插入SSD的,因为有块SSD装载上面,我是这样推测的。 本想花200块钱买一快好点的免驱动网卡来解决linux 驱动问题,现在主板接口上不给我这个机会,那我还得再研究一下。

我现在打算使用您提供的办法, “是先卸载 bcmwl-kernel-source (即保证这个包没有安装) 然后再替换 brcmfmac4356-pcie.bin。” 因为 我装了这个驱动以后 无线模块都不工作了- -!
然后再去您给的链接里面 尝试一些其他版本的驱动,看看wifi能不能成功链接。
感谢!
下图是我用免费图床“极简图床”上传的文件,不知道能不能打开
图片
图片
附件为:神舟官方提供的BCM4356 wifi驱动


附件:
Broadcom 802.11 Network Adapter.zip [3.05 MiB]
被下载 14 次
页首
 用户资料  
 
14 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-30 10:19 

注册: 2017-03-29 12:04
帖子: 10
系统: ubuntu 16.10
送出感谢: 4
接收感谢: 0 次
vickycq 写道:
liuki342166 写道:
有一个现象,就是我安装了 bcmwl-kernel-source 之后WIFI 就关闭了,无法打开, 重启也没用。 想链接WIFI 必须卸载 bcmwl-kernel-source 这个程序

bcmwl-kernel-source 提供的是官方私有驱动 wl,可能不支持 BCM4356。

liuki342166 写道:
关于您说的第二种方法,我理解为 先安装 bcmwl-kernel-source 然后再替换brcmfac4356pcie.bin

是先卸载 bcmwl-kernel-source (即保证这个包没有安装) 然后再替换 brcmfmac4356-pcie.bin。
卸载 bcmwl-kernel-source 后,会自动恢复到自带的开源驱动 brcmfmac,正好配合固件 brcmfmac4356-pcie.bin 使用。而 bcmwl-kernel-source 提供的是官方私有驱动 wl,与此固件没关系。

liuki342166 写道:
所以我怀疑是bios有问题

也可能是 BCM4356 较新,驱动不完善。可以试试其它版本的固件。
https://mirrors.tuna.tsinghua.edu.cn/ubuntu/pool/main/l/linux-firmware/ 下载 1.149 以后(1.149 ~ 1.164)的 deb 包。下载之后解压,找到 lib/firmware/brcm/brcmfmac4356-pcie.bin,替换系统中的 /lib/firmware/brcm/brcmfmac4356-pcie.bin。重新启动计算机。重新启动计算机后可立刻执行以下指令看有无与固件有关的错误信息。
代码:
sudo dmesg | grep brcm



linux-firmware_1.149.3_all.deb 24-Nov-2015 19:07 29754558
linux-firmware_1.149_all.deb 07-Oct-2015 18:09 29123454
linux-firmware_1.157.8_all.deb 13-Jan-2017 13:13 37717566
linux-firmware_1.157_all.deb 21-Mar-2016 15:53 32601468
linux-firmware_1.161.1_all.deb 07-Dec-2016 14:33 33053630
linux-firmware_1.161_all.deb 14-Sep-2016 15:02 33139906
linux-firmware_1.164_all.deb 20-Mar-2017 22:40 34169962

我把这些deb文件都列出来了, 我一个一个尝试去替换系统驱动,然后然后重启计算机,不进行WIFI链接操作,
执行sudo dmesg | grep brcm 命令

先站一个楼 ,一会回来编辑添加命令结果
官方驱动“brcmfac4356pcie.bin” sudo dmesg | grep brcm 命令结果如下
代码:
root@liukim-laptop:~# sudo dmesg | grep brcm
[    2.639291] usbcore: registered new interface driver brcmfmac
[    2.639438] brcmfmac 0000:01:00.0: enabling device (0000 -> 0002)
[    2.762098] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4356-pcie.txt failed with error -2
[    3.020069] brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 22 2015 06:16:41 version 7.35.180.119 (r594535) FWID 01-1a5c4016
[    3.040918] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)
[    3.054009] brcmfmac 0000:01:00.0 wlp1s0: renamed from wlan0
root@liukim-laptop:~#

linux-firmware_1.149.3_all.deb 24-Nov-2015 19:07 29754558
代码:
XX


linux-firmware_1.149_all.deb 07-Oct-2015 18:09 29123454
代码:
XX


linux-firmware_1.157.8_all.deb 13-Jan-2017 13:13 37717566
代码:
XX


linux-firmware_1.157_all.deb 21-Mar-2016 15:53 32601468
代码:
XX


linux-firmware_1.161.1_all.deb 07-Dec-2016 14:33 33053630
代码:
XX


linux-firmware_1.161_all.deb 14-Sep-2016 15:02 33139906
代码:
XX


linux-firmware_1.164_all.deb 20-Mar-2017 22:40 34169962
代码:
XX


根据
我查寻到这个帖子“https://bugzilla.kernel.org/show_bug.cgi?id=185661”
英文我也看不太明白,我理解大概意思为缺少brcm/brcmfmac4356-pcie.txt 这个文件,才会连不上,
然后他从“https://chromium.googlesource.com/chromiumos/third_party/linux-firmware/+/f151f016b4fe656399f199e28cabf8d658bcb52b/brcm/brcmfmac4356-pcie.txt ”这里下载里一下txt文件,拷贝到into /lib/firmware/brcm 这个位置,他的网卡就可以正常工作了!我也想效仿他的办法尝试解决问题,但现在我无法 下载那个txt文件,因为我的VPN不太好用了,您能帮我下载么?


页首
 用户资料  
 
15 楼 
 文章标题 : Re: 神舟PCpad Plus WIFI 总是弹回输入密码,BCM4356
帖子发表于 : 2017-03-30 11:50 

注册: 2017-03-29 12:04
帖子: 10
系统: ubuntu 16.10
送出感谢: 4
接收感谢: 0 次
已经成功解决问题,我把这个问题理解成有驱动模块,但是缺少配置文件。

我整理一下解决方法! 还有电脑环境!

UEFI+GPT 安装的Ubuntu16.10

在保证卸载bcmwl-kernel-source 的前提下!

使用神舟官方提供的(windows)驱动楼上我有提供压缩包,找到里面的2个文件

“4356a2rtecdc.bin” 改名为 “brcmfmac4356-pcie.bin”

“bcm94356z_p101.txt” 改名为“brcmfmac4356-pcie.txt”

然后将这两个文件复制到,系统目录“/lib/firmware/brcm” 若提示替换,请执行替换。

然后重启电脑,WIFI可以正常工作了!

下图为成功链接WIFI时候的屏幕截图。
图片

最后十分感谢@vickycq 和 @qy117121 给予我莫大的帮助! 这两天研究问题,到最后解决问题。对我学习linux非常非常有帮助。学到了很多不同 的思路,尝试的去看代码分析问题、国外网站的搜索帮助,感觉我也成长里好多!。最后再次非常感谢热心的帮助!谢谢!
(其实还有触摸屏、重力传感器、蓝牙适配器等等都没有正常工作!没有解决),十分感谢你们的帮助,我也会加强自身的学习争取能靠自己的力量解决问题。


页首
 用户资料  
 
显示帖子 :  排序  
发表新帖 回复这个主题  [ 18 篇帖子 ]  前往页数 1, 2  下一页

当前时区为 UTC + 8 小时


在线用户

正在浏览此版面的用户:没有注册用户 和 3 位游客


不能 在这个版面发表主题
不能 在这个版面回复主题
不能 在这个版面编辑帖子
不能 在这个版面删除帖子
不能 在这个版面提交附件

前往 :  
本站点为公益性站点,用于推广开源自由软件,由 DiaHosting VPSBudgetVM VPS 提供服务。
我们认为:软件应可免费取得,软件工具在各种语言环境下皆可使用,且不会有任何功能上的差异;
人们应有定制和修改软件的自由,且方式不受限制,只要他们自认为合适。

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
简体中文语系由 王笑宇 翻译