I have the same issue on Arch Linux (Antergos actually) kernel
4.4.43-1-lts.
Just wanted to add my workaround:
user@arch>$ sudo ethtool -s enp4s0f2 duplex full
Cannot advertise duplex full
And it usually works again. Sometimes I have to add the following too because
it's not always enough:
u
Sorry, Christopher. I misread a May 2015 date comment (#16) as May
2016.
There are still laptop people who have this same issue with kernel
module r8169 (Realtek Ethernet chipset or plug-in board). I don't.
I was offering two distinct work-arounds (upstart and systemd) that I
have used in the p
A couple of automated work-arounds follows, depending on which version
of the Ubuntu core you are using.
==
BEFORE systemd (earlier than Ubuntu 15.04)
==
Create the following executable Bourne shell script in /etc/pm/
This keeps happening to me occasionally, less than one out of ten times.
Over the last several Ubuntu releases, "sudo ifconfig eth0 down"
followed by "sudo ifconfig eth0 up" has always been enough to re-
establish connectivity. A long time ago, I sometimes had to unload and
reload the r8169 module.
peng, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control
team, and Ubuntu Bug Squad would like you to please file a new report by
executing the following in a terminal while booted into a Ubuntu repository
kernel (not a mainline one) via:
ubuntu-bug linux
For more on this,
It appears my problem is related to the network-manager bug other than the
kernel.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1027202
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I have the same problem once upgraded to 13.10. I have never had this
problem before. It's a gigabyte motherboard.
lspci | grep -i ethernet
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 03)
--
You received this bug no
ghomem, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control
team, and Ubuntu Bug Squad would like you to please file a new report by
executing the following in a terminal while booted into a Ubuntu repository
kernel (not a mainline one) via:
ubuntu-bug linux
For more on this
Previous comment applies to kernel
3.11.4-031104-generic
that we upgraded the system to, to check wether it would solve the
problem (it didn't).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771857
We found that after a resume / suspend cycle the interface goes back to
work if it is put in promiscuous mode. This was found by accident while
running tcpdump to see if there was traffic going through.
This can be tested afer resume with:
1.
ifconfig eth0 promisc
activate interface in Network M
Still a problem on 12.04 LTS with kernel 3.8.0-31-generic
#46~precise1-Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771857
Title:
Realtek 8168B (r8169) interface not working following suspe
iMac, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/771857/comments/7
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and t
** Changed in: linux
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771857
Title:
Realtek 8168B (r8169) interface not working following suspend
To manage not
I just retried this today (after noting a new tag upstream, I was
thinking I have not seen this in a while) and was unable to reproduce
the problem using the suspend feature.I note that I now have a 3.2
kernel and see some info on jumbo frames in my dmesg. No other notable
changes jump out at
oh i got this problems, too.
Using Gigabyte 990FXA-UD7 Mainboard with 8111 LAN-Chipset
8169 works for 2 days and dies
8168 wount work. i tried a lot of hints from ubuntu-forums but it wont works
i tried on ubuntu 11.04, 11.10 and 12.04
--
You received this bug notification because you are a mem
After suspend, network manager is doing its interface discover
animation,
I just pull up a terminal and run this little script, and Network
Manager blinks (as the interface disappears and comes back) and eth0
comes back up.
imac@repo:~$ cat /usr/local/bin/fixnet
#!/bin/sh
rmmod r8169
modprobe r
Still not working after suspend on current 12.04 Beta (3.2.0-18-generic
#29-Ubuntu)
0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 02)
Subsystem: Hewlett-Packard Company Device 30fc
Flags: bus master, fast de
No change in Oneiric Beta 1
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771857
Title:
Realtek 8168B (r8169) interface not working following suspend
To manage notifications
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771857
Title:
Realtek 8168B (r8169) interface not working following suspend
--
ubuntu-bu
** Changed in: linux
Status: Unknown => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771857
Title:
Realtek 8168B (r8169) interface not working following suspend
--
ubuntu-bugs
Rebooted into Debian Squeeze and confirmed the same problem (no NIC
connectivity) there too when suspending, so upstream seems legit. My
debian hostname is "beta" .. but it is uptodate.
Appears to be same driver version, different and earlier kernel.
beta:/home/imac# uname -a
Linux beta 2.6.32-5
** Description changed:
After suspending and resuming, the network adapter appears to be active
(Link UP) however it is not able to properly communicate data and
appears in network-manager as disconnected due to the inability to
negotiate DHCP successfully.
The workaround, in my case,
** Bug watch added: Linux Kernel Bug Tracker #12296
http://bugzilla.kernel.org/show_bug.cgi?id=12296
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=12296
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of U
23 matches
Mail list logo
