Fix Ubuntu 13.10 Ethernet after Suspend/Resume

Thanks to http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html
Find the network driver using the command 



$ lshw -C network




which gives something like:




  *-network               
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: eth0
       version: 06
       serial: 90:2b:34:12:e0:14
       size: 100Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168e-3_0.0.4 03/27/12 ip=192.168.1.20 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
       resources: irq:46 ioport:d000(size=256) memory:f0004000-f0004fff memory:f0000000-f0003fff



So in my case r8169


Then edit (or create as it might be empty) the unload_modules file




$ gksu gedit /etc/pm/config.d/unload_modules




to add







SUSPEND_MODULES="$SUSPEND_MODULES r8169"




The simply suspend and resume again, network should work again!



















































Popular posts from this blog









Fixing "DerInputStream.getLength(): lengthTag=109, too big" in Android Studio





















This happened to me in Android Studio after AndroidX migration and using the new testing framework. Even deleting the existing ~/.android/debug.keystore was failing for me   The solution was regenerate it manually (accept all questions as empty and say yes at the last one)   $ keytool -genkey -v -keystore debug.keystore -storepass android -alias androiddebugkey -keypass android -keyalg RSA -keysize 2048 -validity 10000   And copy it   $ rm ~/.android/debug.keystore $ cp debug.keystore ~/.android/debug.keystore   








Read more










Simple Samba setup on Lubuntu





















I have a simple lubuntu server where I setup a ssh server. While it is sufficient to access a driver/folder from another linux machine using sftp, it is a pain from Windows & Mac, so unfortunately, samba is still needed here.   For simplicity I needed only one samba user that I could map to a single user on my lubuntu machine   Following the various tutorial I ended up doing this with simple commands   Install samba  $ sudo apt-get install samba  Add myuser to the samba  $ sudo smbpasswd -a myuser  Export the drive I needed (no guest user)  $ sudo vi /etc/samba/smb.conf  to add the following export (no real option needed here)  [files] path = /media/music/files writeable = yes  save and Restart samba  $ sudo service smbd restart  








Read more










Solving: insufficient permissions for device: user in plugdev group; are your udev rules wrong





















This happens on Ubuntu almost each time I add a new device:   Check that your are in plugdev group   $ id   uid=1000(alex) gid=1000(alex) groups=1000(alex),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare),127(kvm),129(libvirt),134(chrome-remote-desktop)   If not (i.e. plugdev not displayed), add it:   $ sudo usermod -aG plugdev alex   If you get 'insufficient permissions for device: user in plugdev group; are your udev rules wrong' when trying to debug, you'll need to add your device:   First i used lsusb to find my vendor id (here I guess google)   $ lsusb  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub  ...  Bus 001 Device 025: ID 18d1:4ee7 Google Inc.  ..  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub .. Bus 001 Device 020: ID 05e0:2106 Symbol Technologies USB2.1 Hub    As suggested in https://developer.android.com/studio/run/device.html the solution was to   sudo gedit /etc/udev/rules.d/51-android.rules   Add th...








Read more