Everybody should have a quick look at this:
Everybody should have a quick look at this:
I'm making another post and unmarking this as solved because my solution appears to have undone itself (I suppose this may have happened while updating?). I noticed I was getting the slow speeds again and I ran the same commands as before and I noticed it's using the r8169 driver again. How do I get it to stick? edit: There was a "blacklist" step in the post that I followed to downgrade to the r8168 driver but I suppose it didn't work for some reason?
Most recent information:
Code:keegan@keegan-Z68XP-UD3P:~$ uname -mr 3.0.0-15-generic x86_64 keegan@keegan-Z68XP-UD3P:~$ lspci -nnk | grep -iA2 net 07:00.0 Ethernet controller : Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06) Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard [1458:e000] Kernel driver in use: r8169 keegan@keegan-Z68XP-UD3P:~$ lsmod Module Size Used by parport_pc 36962 0 ppdev 17113 0 bnep 18436 2 rfcomm 47946 0 bluetooth 166112 10 bnep,rfcomm snd_hda_codec_hdmi 32040 5 snd_hda_codec_realtek 330769 1 binfmt_misc 17540 1 snd_hda_intel 33390 3 snd_hda_codec 104931 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 13668 1 snd_hda_codec snd_pcm 96714 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec snd_seq_midi 13324 0 snd_rawmidi 30547 1 snd_seq_midi snd_seq_midi_event 14899 1 snd_seq_midi snd_seq 61896 2 snd_seq_midi,snd_seq_midi_event snd_timer 29991 2 snd_pcm,snd_seq snd_seq_device 14540 3 snd_seq_midi,snd_rawmidi,snd_seq snd 68266 16 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 12680 1 snd nvidia 11713772 40 snd_page_alloc 18529 2 snd_hda_intel,snd_pcm mxm_wmi 12979 0 serio_raw 13166 0 mei 41480 0 wmi 19256 1 mxm_wmi i915 567092 1 drm_kms_helper 42558 1 i915 drm 236290 2 i915,drm_kms_helper i2c_algo_bit 13423 1 i915 video 19412 1 i915 lp 17799 0 parport 46562 3 parport_pc,ppdev,lp usbhid 47198 0 hid 95463 1 usbhid firewire_ohci 40722 0 firewire_core 63626 1 firewire_ohci crc_itu_t 12707 1 firewire_core r8169 52788 0 xhci_hcd 82820 0 keegan@keegan-Z68XP-UD3P:~$ ifconfig eth0 Link encap:Ethernet HWaddr 50:e5:49:49:fa:5c inet addr:18.104.22.168 Bcast:22.214.171.124 Mask:255.255.255.0 inet6 addr: fe80::52e5:49ff:fe49:fa5c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:113155 errors:0 dropped:113155 overruns:0 frame:113155 TX packets:30013 errors:0 dropped:106 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:44210883 (44.2 MB) TX bytes:4644698 (4.6 MB) Interrupt:42 Base address:0xe000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:240 (240.0 B) TX bytes:240 (240.0 B) keegan@keegan-Z68XP-UD3P:~$ cat /etc/network/interfaces auto lo iface lo inet loopback keegan@keegan-Z68XP-UD3P:~$ cat /etc/resolv.conf # Generated by NetworkManager domain resnet.ubc.ca. search resnet.ubc.ca. nameserver 126.96.36.199 nameserver 188.8.131.52
Last edited by Paperypip; February 10th, 2012 at 04:57 AM. Reason: adding a little more description
Firstly, thanks for the valuable feedback, it is important and appreciated.
Now about the problem-
What happens if you do:
Does it give any errors? Does it make things normal again (temporarily of-course)?Code:sudo modprobe -rfv r8169 sudo modprobe -v r8168
Didn't get the chance to do this till now. Last night Ubuntu updated itself from 3.0.0-15 to 3.0.0-16 and since then my Internet connection hasn't worked at all on that half of the machine (currently posting while using the Windows half).
I tried what varunendra just suggested (admittedly after the update and so after I lost my Internet connection) and got this:
Code:keegan@keegan-Z68XP-UD3P:~$ sudo modprobe -rfv r8169 [sudo] password for keegan: keegan@keegan-Z68XP-UD3P:~$ sudo modprobe -v r8168 FATAL: Module r8168 not found.
Just like I mentioned in post #8, it'll break with every kernel update, requiring you to compile it again. So keep the original downloaded source (unless you get a newer and better one), and run the same installation procedure with each kernel upgrade.
You are completely disconnected because, I guess, the r8168 driver is broken with the kernel upgrade and the native r8169 is blacklisted. Although your previous outputs showed it being loaded, I don't know how it could despite being blacklisted. I have at least one more thread at hand where it happened, but the OP there hasn't posted for a while. So couldn't figure out why it got loaded even with blacklisting.
However, I myself tried recently to compile the r8168 driver, downloaded from realtek's site, using their recommended method in the readme file (just run ./autorun.sh), and it compiled like a charm. Just make sure all the support packages are preinstalled (current kernel headers, dkms, build essential).
To see whether a driver is currently associated or not, please check(before compiling the 8168 driver):
If it shows r8169, please also post the out put of,Code:lspci -nnk | grep -iA2 RTL8111
As for re-compiling and loading the r8168 driver, the procedure should be:Code:cat /etc/modprobe.d/blacklist.conf | grep r81
Code:sudo modprobe -rfv r8169 (then compile the r8168 driver as per instructions in readme file- which is just running sudo ./aururun.sh from within extracted directory) sudo modprobe -v r8168
I have the same problem and using this method it solves it. However every time I restart I get back that r8169 driver even though it is in the blacklist. How can i make it permanently r8186?
I noticed that the r8186 driver is still there and I do not have to make it again I just need to disable the bad one and activate the new one with:
sudo modprobe -rfv r8169
sudo modprobe -v r8168
But I have to do this at every restart. How can I make it permanent at least when no updates have been done.
OK at last I found the solution. I just needed to add the last 2 lines to the original ones in terminal. So for the benefit of people having this same problem here are all the lines you need to enter to solve this bug.
apt-get install --reinstall linux-headers-$(uname -r) build-essential dkms
tar xvf r8168-8.026.00.tar.bz2
modprobe -rfv r8169
cp src/r8168.ko /lib/modules/$(uname -r)/kernel/drivers/net/
modprobe -v r8168
echo "blacklist r8169" | tee -a /etc/modprobe.d/blacklist.conf
mkinitramfs -o /boot/initrd.img-`uname -r` `uname -r`
echo “r8168″ >> /etc/modules
Thanks for the input ercolesptr, I'm sure this would help others too. I'm going to simply link to your post in another thread with similar problem and am quite hopeful it would work the same way for the poster there.