While I could not believe this at first, it is true: this bug only happens when one restarts Windows to Linux if it is done a shutdown at Linux, or Windows is ended down to shutdown the PC, this does not happen. In case of desperation, just shutdown your system, and remove for a few seconds the electric power plug not a joke: this will release the lock windows 10 make to the ethernet hardware, and Ubuntu will have net again.Īlso, if you remember when at Windows 10, disabling the ethernet interface before rebooting will also avoid this lock at next Linux boot. Please wait about 30 seconds after this last step Then after running it: service network-manager restart #Reset the PCI Device completely (like Power-ON/Off) PCI=`/usr/bin/lspci | /bin/egrep -i 'network|ethernet' | /usr/bin/cut -d' ' -f1` #Get the PCI-Address of network card (Caution: This works ONLY with ONE NIC) This script author is jnko from an article at /viewtopic.php?pid=1575719 #!/bin/bash On an Ubuntu 16.04 with wired ethernet locked after coming from Windows 10 dual-boot, the following script/steps at command-line set it working again: This approach however did not worked with other PC with the same bug, who had kernel 4.4.0.21 before 0.72 updated so this is just informative. I could then fix it by editing /etc/grub.d/10_linux_proxy, deleting 4.4.0.72 files from /boot and using grub-mkconfig and update-grub Using the older kernel at boot made it work without any changes, at this case 4.4.0.71 was Ok, going from the boot "Advanced options for Ubuntu" menu entry. RX bytes:36090 (36.0 KB) TX bytes:36090 (36.0 KB)Īt a recent case this happened also after an update to kernel 4.4.0.72 who made the bug of after booting from a Windows 10 dual-boot, the wired network at next Ubuntu 16.04 boot did not work, even with all settings ok TX packets:463 errors:0 dropped:0 overruns:0 carrier:0 RX packets:463 errors:0 dropped:0 overruns:0 frame:0 TX packets:604 errors:0 dropped:0 overruns:0 carrier:0 RX packets:119357 errors:0 dropped:72 overruns:0 frame:0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Output of ifconfig below: eth0 Link encap:Ethernet HWaddr 98:90:96:c4:6b:06 I've tried this sequence a few times and it is consistent. ⠀Boot from disk "Try Ubuntu" 14.04.2 LTS - works ⠀Boot to Windows 7 Pro - wired internet works I updated the NIC driver e1000e to the latest version (3.1.0.2), but this did not solve the problem. I've seen numerous different problems and solutions to wired internet not working in Ubuntu 14.04, but none of them seem to apply to this case. If you still can't connect to the wireless network after completing this procedure, verify the Network name (SSID), Security type, Encryption type, and Security key are correct and repeat the procedure.Wired internet works fine in Windows 7 Pro and "Try Ubuntu" 14.04.2 LTS booted from disk and in the installed Ubuntu, but stops working after booting Windows and then Ubuntu. In the Successfully added window, click the Close button.If you're manually configuring your wireless network because the router isn't broadcasting the SSID, you must check the box next to Connect even if the network is not broadcasting.Verify the box is checked next to Start this connection automatically.The image provided is an example of the information required. If you can't find this information, contact your network administrator or the router manufacturer. If you configured the router with custom settings, you may be able to locate it by logging into the router setup page. If you're using the default configuration, this information may be listed on bottom of the router or in the manual. Note: The Network name (SSID), Security type, Encryption type, and Security key information are configured on the wireless router or access point.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |