[Bug 1547151] Re: 10ec:8168 r8169 won't connect

2017-11-11 Thread Anthony Wong
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547151 Title: 10ec:8168 r8169 won't connect To manage notifications about this bug go to:

[Bug 1547151] Re: 10ec:8168 r8169 won't connect

2016-12-18 Thread Christopher M. Penalver
Not Status In Progress as defined in https://wiki.ubuntu.com/Bugs/Status . ** Changed in: linux (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547151

[Bug 1547151] Re: 10ec:8168 r8169 won't connect

2016-12-18 Thread Christopher M. Penalver
Luca Mastromatteo, to advise, a debug beta driver isn't eligible for inclusion to any production repository (upstream, Ubuntu, etc.). They probably gave it to you to both test some new features/fixes, and capture additional information the production driver doesn't normally output. Also, when

[Bug 1547151] Re: 10ec:8168 r8169 won't connect

2016-12-17 Thread Luca Mastromatteo
Sorry for the late reply, but I reported the bug to the upstream developers (Hau, from realtek.com) and I helped them to solve the problem. Then, they finally gave me a beta debug driver, after some tests, which seems to solve the problem. I don't know if those patches are currently committed

[Bug 1547151] Re: 10ec:8168 r8169 won't connect

2016-12-17 Thread Luca Mastromatteo
Here. https://github.com/torvalds/linux/commit/f51d4a10ac39ecf06b25e7a79121b06f7ed59928 This may be the commit but I don't know honestly. The date of the commit matches the period which I was in contact with him. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1547151] Re: 10ec:8168 r8169 won't connect

2016-12-17 Thread Christopher M. Penalver
** Description changed: At school when I connect with my Ethernet cable to its network it doesn't see my cable, like it is disconnected. This occurs with a different computer using the same kernel driver with the same LAN chip. The realtek r8168 works flawlessly but it disconnects

[Bug 1547151] Re: 10ec:8168 r8169 won't connect

2016-12-07 Thread AceLan Kao
** Changed in: linux (Ubuntu) Assignee: AceLan Kao (acelankao) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547151 Title: 10ec:8168 r8169 won't connect To manage

[Bug 1547151] Re: 10ec:8168 r8169 won't connect

2016-11-20 Thread AceLan Kao
Adding "acpi_rev_override" kernel parameter can workaround it. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: kittyhawk originate-from-1605487 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1547151] Re: 10ec:8168 r8169 won't connect

2016-11-20 Thread AceLan Kao
Luca, The workaround I mention on comment #24 works on other machine. I didn't notice the machine you have is not the same as mine, so I'm not sure if the workaround works for you. Could you help to check that? Thanks. -- You received this bug notification because you are a member of Ubuntu