ubuntu15.10有线网络无法连接

包含网卡/无线网的网络问题和ADSL/校园网/宽带拨号支持及代理/共享等网络使用问题
回复
白鬼_2015
帖子: 4
注册时间: 2015-02-17 17:10
系统: win8.1+ubuntu14.10

ubuntu15.10有线网络无法连接

#1

帖子 白鬼_2015 » 2015-10-25 23:08

config.png
[
error.png
如图,升级前是15.04的系统。
刚装好时间有线能用,然后时而能用时而无法连接。(没做任何改动)
现在已经完全连不上了
困惑以久,求各位大神明示。
头像
vickycq
帖子: 4507
注册时间: 2011-03-20 13:12
系统: Debian
来自: 山东省寿光县
联系:

Re: ubuntu15.10有线网络无法连接

#2

帖子 vickycq » 2015-10-26 11:27

依次执行

断开无线
断开有线网电缆
打开终端运行

代码: 全选

sudo tail -f /var/log/syslog
插上有线网电缆 令其连接
将终端里新刷出的信息全部复制 贴上来。

保持有线网电缆连接,在终端中运行以下命令 把结果全部复制贴上来

代码: 全选

uname -a
lspci -knn
sudo lshw -C network
sudo nmcli dev show eth0
sudo ethtool eth0
Debian 中文论坛 - forums.debiancn.org
欢迎所有 Debian GNU/Linux 用户
白鬼_2015
帖子: 4
注册时间: 2015-02-17 17:10
系统: win8.1+ubuntu14.10

Re: ubuntu15.10有线网络无法连接

#3

帖子 白鬼_2015 » 2015-10-26 21:14

刚刚突然又能用了,简直不可思议


Oct 26 21:09:31 Deepblue NetworkManager[835]: <info> NetworkManager state is now DISCONNECTED
Oct 26 21:09:31 Deepblue NetworkManager[835]: <info> Device 'wlan0' has no connection; scheduling activate_check in 0 seconds.
Oct 26 21:09:31 Deepblue dbus[849]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Oct 26 21:09:31 Deepblue NetworkManager[835]: <warn> Connection disconnected (reason -3)
Oct 26 21:09:31 Deepblue NetworkManager[835]: <info> (wlan0): supplicant interface state: completed -> disconnected
Oct 26 21:09:31 Deepblue systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 26 21:09:31 Deepblue dbus[849]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 26 21:09:31 Deepblue systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 26 21:09:31 Deepblue nm-dispatcher: Dispatching action 'down' for wlan0
Oct 26 21:09:37 Deepblue wpa_supplicant[979]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 26 21:10:01 Deepblue CRON[2632]: (blue) CMD (/home/blue/clock.sh)
Oct 26 21:10:01 Deepblue CRON[2631]: (CRON) info (No MTA installed, discarding output)

Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> (eth0): link connected
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Oct 26 21:10:44 Deepblue kernel: [ 650.520230] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Oct 26 21:10:44 Deepblue kernel: [ 650.520242] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
Oct 26 21:10:44 Deepblue kernel: [ 650.520295] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> Device 'eth0' has no connection; scheduling activate_check in 0 seconds.
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> Auto-activating connection 'Home'.
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> (eth0): Activation: starting connection 'Home' (fb490ac3-3910-444d-bb21-6a56ddc2500d)
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> NetworkManager state is now CONNECTING
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> dhclient started with pid 2655
Oct 26 21:10:44 Deepblue dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xeb092750)
Oct 26 21:10:44 Deepblue dhclient: DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67 (xid=0x502709eb)
Oct 26 21:10:44 Deepblue dhclient: DHCPOFFER of 192.168.1.10 from 192.168.1.1
Oct 26 21:10:44 Deepblue dhclient: DHCPACK of 192.168.1.10 from 192.168.1.1
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> address 192.168.1.10
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> plen 24 (255.255.255.0)
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> gateway 192.168.1.1
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> server identifier 192.168.1.1
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> lease time 43200
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> hostname 'Deepblue'
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> nameserver '192.168.1.1'
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> domain name 'lan'
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> (eth0): DHCPv4 state changed unknown -> bound
Oct 26 21:10:44 Deepblue avahi-daemon[899]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.10.
Oct 26 21:10:44 Deepblue avahi-daemon[899]: New relevant interface eth0.IPv4 for mDNS.
Oct 26 21:10:44 Deepblue avahi-daemon[899]: Registering new address record for 192.168.1.10 on eth0.IPv4.
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> NetworkManager state is now CONNECTED_LOCAL
Oct 26 21:10:44 Deepblue whoopsie[827]: [21:10:44] Cannot reach: https://daisy.ubuntu.com
Oct 26 21:10:44 Deepblue whoopsie[827]: [21:10:44] Cannot reach: https://daisy.ubuntu.com
Oct 26 21:10:44 Deepblue dhclient: bound to 192.168.1.10 -- renewal in 16713 seconds.
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> NetworkManager state is now CONNECTED_GLOBAL
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> Policy set 'Home' (eth0) as default for IPv4 routing and DNS.
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> Writing DNS information to /sbin/resolvconf
Oct 26 21:10:44 Deepblue dnsmasq[1642]: setting upstream servers from DBus
Oct 26 21:10:44 Deepblue dnsmasq[1642]: using nameserver 192.168.1.1#53
Oct 26 21:10:44 Deepblue NetworkManager[835]: <info> (eth0): Activation: successful, device activated.
Oct 26 21:10:44 Deepblue dbus[849]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Oct 26 21:10:44 Deepblue systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 26 21:10:44 Deepblue whoopsie[827]: [21:10:44] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1
Oct 26 21:10:44 Deepblue whoopsie[827]: [21:10:44] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
Oct 26 21:10:44 Deepblue whoopsie[827]: [21:10:44] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
Oct 26 21:10:44 Deepblue dbus[849]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 26 21:10:44 Deepblue systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 26 21:10:44 Deepblue nm-dispatcher: Dispatching action 'up' for eth0
Oct 26 21:10:44 Deepblue whoopsie[827]: [21:10:44] online
Oct 26 21:10:45 Deepblue avahi-daemon[899]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::eef4:bbff:fe13:c53e.
Oct 26 21:10:45 Deepblue avahi-daemon[899]: New relevant interface eth0.IPv6 for mDNS.
Oct 26 21:10:45 Deepblue avahi-daemon[899]: Registering new address record for fe80::eef4:bbff:fe13:c53e on eth0.*.
Oct 26 21:10:53 Deepblue ntpdate[2815]: adjust time server 91.189.94.4 offset 0.298803 sec
Oct 26 21:11:01 Deepblue CRON[2908]: (blue) CMD (/home/blue/clock.sh)
Oct 26 21:11:01 Deepblue CRON[2907]: (CRON) info (No MTA installed, discarding output)
Oct 26 21:11:07 Deepblue ntpdate[2905]: no server suitable for synchronization found

Linux Deepblue 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
blue@Deepblue:~$ lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [8086:0c04] (rev 06)
Subsystem: Dell Device [1028:05cd]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06)
DeviceName: Onboard IGD
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: i915
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: snd_hda_intel
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 04)
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: mei_me
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 04)
DeviceName: Onboard LAN
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 04)
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 04)
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d4)
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 [8086:8c14] (rev d4)
Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 [8086:8c16] (rev d4)
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 [8086:8c18] (rev d4)
Kernel driver in use: pcieport
00:1c.6 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 [8086:8c1c] (rev d4)
Kernel driver in use: pcieport
00:1c.7 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 [8086:8c1e] (rev d4)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 04)
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: ehci-pci
00:1f.0 ISA bridge [0601]: Intel Corporation QM87 Express LPC Controller [8086:8c4f] (rev 04)
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 04)
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 04)
Subsystem: Dell Device [1028:05cd]
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Saturn XT [FirePro M6100] [1002:6640]
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: radeon
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:aac0]
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: snd_hda_intel
03:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)
Subsystem: Dell Device [1028:0017]
Kernel driver in use: wl
11:00.0 SD Host controller [0805]: O2 Micro, Inc. SD/MMC Card Reader Controller [1217:8520] (rev 01)
Subsystem: Dell Device [1028:05cd]
Kernel driver in use: sdhci-pci
blue@Deepblue:~$ sudo lshw -C network
[sudo] blue 的密码:
*-network
description: Ethernet interface
product: Ethernet Connection I217-LM
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 04
serial: ec:f4:bb:13:c5:3e
size: 100Mbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.5-k duplex=full firmware=0.13-3 ip=192.168.1.10 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
resources: irq:29 memory:f7f00000-f7f1ffff memory:f7f3d000-f7f3dfff ioport:f080(size=32)
*-network
description: Wireless interface
product: BCM4352 802.11ac Wireless Network Adapter
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 03
serial: 40:f0:2f:ed:ea:6b
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=wl0 driverversion=6.30.223.248 (r487574) latency=0 multicast=yes wireless=IEEE 802.11abg
resources: irq:18 memory:f5e00000-f5e07fff memory:f5c00000-f5dfffff
blue@Deepblue:~$ sudo nmcli dev show eth0
GENERAL.设备: eth0
GENERAL.类型: ethernet
GENERAL.硬盘: EC:F4:BB:13:C5:3E
GENERAL.MTU: 1500
GENERAL.状态: 100 (连接的)
GENERAL.CONNECTION: Home
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.容器: 开
IP4.地址[1]: 192.168.1.10/24
IP4.网关: 192.168.1.1
IP4.ROUTE[1]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.DNS[1]: 192.168.1.1
IP4.DOMAIN[1]: lan
IP6.地址[1]: fe80::eef4:bbff:fe13:c53e/64
IP6.网关:
blue@Deepblue:~$ sudo ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
头像
photor
论坛版主
帖子: 11004
注册时间: 2008-04-26 12:41

Re: ubuntu15.10有线网络无法连接

#4

帖子 photor » 2015-10-26 23:10

vickycq 写了:依次执行

断开无线
断开有线网电缆
打开终端运行

代码: 全选

sudo tail -f /var/log/syslog
插上有线网电缆 令其连接
将终端里新刷出的信息全部复制 贴上来。

保持有线网电缆连接,在终端中运行以下命令 把结果全部复制贴上来

代码: 全选

uname -a
lspci -knn
sudo lshw -C network
sudo nmcli dev show eth0
sudo ethtool eth0
顶爱因斯坦 :em09
头像
vickycq
帖子: 4507
注册时间: 2011-03-20 13:12
系统: Debian
来自: 山东省寿光县
联系:

Re: ubuntu15.10有线网络无法连接

#5

帖子 vickycq » 2015-10-27 0:26

系统: win8.1+ubuntu14.10
product: Ethernet Connection I217-LM
driver=e1000e
刚装好时间有线能用,然后时而能用时而无法连接。
刚刚突然又能用了,简直不可思议
你是双系统?
若是双系统,猜测你也是下面的情况

I217-LM + e1000e 这个组合 在双系统下容易出现此类问题
前几天刚出现一例 viewtopic.php?f=116&t=473460
主板的某些功能会使网卡无法彻底断电,使得关机时设置无法重置,从而使Windows 驱动和 Linux 驱动的设置相互影响。

vickycq 写了: 双系统网卡设置相互影响的问题,有用户报告关闭主板的网络唤醒功能 (WoL, Wake-on-LAN) 可缓解。
poloshiao 写了: 3. 雙系統 或 多重系統 開機
最好把所有關機還耗用電源的設定 全部排除
否則問題可能一大堆
LaoAnchor 写了: 的确是双系统网卡设置相互影响的问题,在windows和主板上关闭网络唤醒功能后,回到UBUNTU有线联网功能就正常了。
需要在 BIOS 和 Windows 驱动中都设置关闭。包括 网络唤醒、PCI-E唤醒 和 PXE boot 等等等等

参考
https://bbs.archlinux.org/viewtopic.php?id=191981
https://bbs.archlinux.org/viewtopic.php ... 7#p1491387
上次由 vickycq 在 2015-10-27 0:33,总共编辑 2 次。
Debian 中文论坛 - forums.debiancn.org
欢迎所有 Debian GNU/Linux 用户
头像
vickycq
帖子: 4507
注册时间: 2011-03-20 13:12
系统: Debian
来自: 山东省寿光县
联系:

Re: ubuntu15.10有线网络无法连接

#6

帖子 vickycq » 2015-10-27 0:31

photor 写了: 顶爱因斯坦 :em09
这是什么典故?... :Faint
Debian 中文论坛 - forums.debiancn.org
欢迎所有 Debian GNU/Linux 用户
白鬼_2015
帖子: 4
注册时间: 2015-02-17 17:10
系统: win8.1+ubuntu14.10

Re: ubuntu15.10有线网络无法连接

#7

帖子 白鬼_2015 » 2015-10-31 21:02

最后我把 Enable w/PXE给禁用了。。。
integrated NIC里只选了Enable一项。
结局是一开始用的很开心,然后现在又连不上了。。。。

PS:这论坛加载速度真是感人泪下。。。
头像
vickycq
帖子: 4507
注册时间: 2011-03-20 13:12
系统: Debian
来自: 山东省寿光县
联系:

Re: ubuntu15.10有线网络无法连接

#8

帖子 vickycq » 2015-11-01 12:50

白鬼_2015 写了:最后我把 Enable w/PXE给禁用了。。。
integrated NIC里只选了Enable一项。
结局是一开始用的很开心,然后现在又连不上了。。。。
是否为双系统?若不是双系统,可能有另外的原因。
看你没提到网络唤醒。若为双系统,最关键一点关闭网络唤醒(Wake on LAN)。

若还有问题,重新执行一遍二楼的指令,把结果发上来。

依次执行

断开无线
断开有线网电缆
打开终端运行

代码: 全选

sudo tail -f /var/log/syslog
插上有线网电缆 令其连接
将终端里新刷出的信息全部复制 贴上来。

保持有线网电缆连接,在终端中运行以下命令 把结果全部复制贴上来

代码: 全选

sudo lshw -C network
sudo nmcli dev show eth0
sudo ethtool eth0
Debian 中文论坛 - forums.debiancn.org
欢迎所有 Debian GNU/Linux 用户
白鬼_2015
帖子: 4
注册时间: 2015-02-17 17:10
系统: win8.1+ubuntu14.10

Re: ubuntu15.10有线网络无法连接

#9

帖子 白鬼_2015 » 2015-11-18 21:39

vickycq 写了:
白鬼_2015 写了:最后我把 Enable w/PXE给禁用了。。。
integrated NIC里只选了Enable一项。
结局是一开始用的很开心,然后现在又连不上了。。。。
是否为双系统?若不是双系统,可能有另外的原因。
看你没提到网络唤醒。若为双系统,最关键一点关闭网络唤醒(Wake on LAN)。

大神明鉴,系统是win10+U 15.04
以前win8.1+U时没有这个问题。
BIOS里面的选项我已经关闭了。
我正在找win10的WOL这个选项在哪里。。。。
谢谢大神的指教。
多谢
头像
vickycq
帖子: 4507
注册时间: 2011-03-20 13:12
系统: Debian
来自: 山东省寿光县
联系:

Re: ubuntu15.10有线网络无法连接

#10

帖子 vickycq » 2015-11-18 22:25

白鬼_2015 写了: 大神明鉴,系统是win10+U 15.04
以前win8.1+U时没有这个问题。
BIOS里面的选项我已经关闭了。
我正在找win10的WOL这个选项在哪里。。。。
谢谢大神的指教。
多谢
Windows 下安装 Intel 的专有驱动后,有专门的设置工具:
voOsrOJ.png
Debian 中文论坛 - forums.debiancn.org
欢迎所有 Debian GNU/Linux 用户
回复