** Description changed:
- UPDATE: This is most likely fixed in 14.04, but it likely to remain non-
- functional in 13.10.
+ UPDATE: This is fixed in 14.04.
Following an upgrade from 13.04 to 13.10, gigabit card stopped working
(100Mbps ethernet working fine on the motherboard still - KN9 Ul
** Description changed:
+ UPDATE: This is most likely fixed in 14.04, but it likely to remain non-
+ functional in 13.10.
+
Following an upgrade from 13.04 to 13.10, gigabit card stopped working
(100Mbps ethernet working fine on the motherboard still - KN9 Ultra).
dmesg gives a load of w
Cocodude, thank you for your comments. Regarding them :
>"However, is Invalid the correct status considering it is a valid bug
report?"
Yes.
>" It just happens to be fixed upstream."
if it's fixed in Trusty, it's fixed downstream as well.
>"I guess if you don't have any other suitable statuses
As I have a spare Ethernet card (albeit slower) I can live with this
until Trusty.
However, is Invalid the correct status considering it is a valid bug
report? It just happens to be fixed upstream. I guess if you don't have
any other suitable statuses it's fine, but I can see this being
confusing
Cocodude, thank you for testing Trusty. Would you need a backport to a
release prior to Trusty, or may this be closed as Status Invalid?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Hi,
I confirm that the r8169 ethernet driver in the latest Trusty build
works just fine with my hardware.
thanks,
Marc
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Cocodude, ok. Given the fix is available in mainline, could you please
confirm this issue exists with the latest development release of Ubuntu?
ISO images are available from http://cdimage.ubuntu.com/daily-
live/current/ . If the issue remains, could you please just make a
comment to this.
** Chan
I tested this with v3.13-rc3-trusty but r8169 worked just fine along
with DHCP and I was able to ping the outside world. So, it's some commit
inbetween 3.11.0-14-generic and 3.13-rc3-trusty that's caused the issue.
I don't think I'll have time to do a full bisect but I might be able to
try and nar
Cocodude, could you please test the latest mainline kernel via
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc1-trusty/ and
advise to the results?
If reproducible with it, the next step is to fully commit bisect from
13.04 to 13.10, in order to identify the offending commit following
https:
Hi,
I just tried with 3.12.0-031200-generic and although I don't get the
dmesg errors, it doesn't detect the Ethernet cable or does DHCP client
work. So, the evidence suggests this isn't entirely fixed upstream yet.
uname -a: Linux flibble 3.12.0-031200-generic #201311071835 SMP Thu Nov
7 23:36:0
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.12 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
11 matches
Mail list logo
