Thanks for your bug report. Could you please also add the output of ethtool after you have connected the cable? Thanks in advance.
I'm seeing what appears to be the same problem on my Asus A6T laptop.
Please let me know if there's any other information that I could provide that might be useful. Thanks.
Same thing here. Asus A6Tc laptop on both i386 and x86_64 versions.
so the only thing that "fix" the problem is to rmod r8169 and modprobe r8169.
have you checked this with the latest version of feisty?
I have an Realtek 8169 and I don't experience the bug with the latest version from http://cdimage.ubuntu.com/ .
Same problem with Compal HEL81 reviewed here https://wiki.ubuntu.com/LaptopTestingTeam/CompalHEL81 .
I have the same problem n a Zepto Znote 6615WD (the same laptop as Kaare Baastrup).
was complete GUI freeze. I'll check and report behavior.
Yep. It handles cable plug-in/out, but still provides hang-ups while uploading data.
Reloading the module seems to work fine.
Same problem in Toshiba A135-S4487... reloading the module doens't work to me. See https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/79626 .
can confirm this problem on Asus A8F with lan cable.
Same problem on Asus F3JV AS022P , on Ubuntu Feisty 64bits, and kernel 2.6.20-16-generic.
I'm a Wifi user, but when I want to use Ethernel, I must rmmod/modprobe r8169.
When the connection is up, it's not perfect, large file transfert fails (over smb or over ssh) when I use Ethernet, but works fine with Wifi.
It's a good news if Gusty havn't this problem.
Looks like #79626 may be a duplicate of this.
I tried it, but didn't worked. Those changes seems to be relevant only for suspend/resume. Anyway, thanks.
I compiled the new module from the link provided by apollo13, but it didn't loaded, giving an "Unknown symbol in module, or unknown parameter" error message. So I did the patch modifications by hand on the r8169.c source, compiled and loaded the module successfully. But it worked like the old module. Good to know that it will work fine on gutsy.
Don't load the iee1384 modules and it works fine... I figured out today about that conflict, I will research deeply "why" and post the info. Two lappys different hardware - same module... same solution. At least it works for me.
do you mean ieee1394 ? There isn't a module called iee1384 for the 2.6.20-16-generic kernel. I'll try removing the ieee1394 and see if it works.
Nope, removing ieee1394 has no effect on my laptop.
Oh, sorry to hear that gborzi... anyone else ?
BTW: Just don't load the modules at boot time or you will have to do the same procedure at the bug report, the modprobe -r and modprobe r8169 stuff after unloading the modules with the cable disconnected, etc. I think that the one messing all the stuff is the eth1394 module but yesterday i didn't have the time to do deeper research.
Same on Asus A6Tc - no effect.
> Nope, removing ieee1394 has no effect on my laptop.
well, maybe my problem its not related, but the bug report solution helped me at the beginning. I thought it was related.
I have the same problem with my asus A8JS laptop. Tried ubuntu, knoppix, slackware, and freeBSD. All have the same problem, the link is'nt detected if you dont do a bounch of remove and re-add of the module.
The strange thing is that the knoppix live dvd I got, find's the link stight away (while booted from DVD). But after installing it onto the harddrive and booting from the harddrive, you have to do the "remove and re-add" procedure.
Not sure if its because you remove the 8169 module and then load the "realtec" 8168 module ..
I can imagine that the problem has something to do with the fact that this network card has the ability to "sense" if it being connected to devices with a regular or a crossed TP cable. (It just a feeling, probably not right).
Seems that every one with this problem has a laptop. Maby theres an difference between the pci version and the laptop version?
I have this same problem only if i start my laptop (V6j) without network cable. At this point that rmmod/modprobe even doesnt work.
Only fix what i have found is just restart my laptop with network cable connected. After this cable unplug/plug works fine.
I'm also concern by this bug.
I'm using gutsy tribe 5 and I have a MotherBoard MSI P35 NEO-F with Realtek 8111b chipset.
I got the similar problem on my desktop also.
But it cannot be solved even rmmod/modprobe r8169. I even tried to install r6186-8.003.00 from official website.
Could anyone help to solve the problem??
Michael: Did you recently install Windows (dual boot)? I had this problem because Windows XP was enabling "power save" for my network card when I powered off. Disabling the power save option in the network preferences of Windows fixed the problem completely.
Yup, my desktop is dual boot and installed with XP. However, after following ur suggestion, the problem still exists.
seems to be working ok in gutsy.
Thanks for the update. Per Kalyan and Pleban's (the original bug reporter) last comment, this appears to be fixed in Gutsy so this report is being closed against linux-source-2.6.22. Against linux-source-2.6.20 this bug does not meet the criteria for a stable release update and will also be closed. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!
You may also want to download the driver and recompile if nothing works.
Diogenes - "What I like to drink most is wine that belongs to others."
I still have this problem with Ubuntu 8.04.1 on Dell Vostro 1510 booted from live CD right after I brought it from store.
We have resolved clearing the CMOS. It seems if you purchase a motherboard with Windows preinstalled, the windows driver sets some strange flags inside the ethernet card memory that only clearing the CMOS solve it.
Alternative: on dual boot systems, use windows advanced driver panel to remove the stupid flag.
I also believe recent Linux kernels has added the feature to remove the card flag when initializing the card.
I tested Ubuntu 9.04, and I still have the same problem with my ethernet card. What info do you need?, so I can post it and help to solve the problem.
I also see the same problem, on a newly built box which has never run windows. Connectivity seems intermittent - the network cable is plugged in all the time, and sometimes it will boot up with a working network, other times nothing. Unloading and reloading r8139 fixes the problem.
Asus P5Q SE motherboard, with built in RTL8111/8168 B PCI Express Gigabit Ethernet Controller.
And as expected the r8168 driver from realtek works fine.
please do not reopen closed bugs. If you are affected by an issue, then please open a new bug.