OVH Community, your new community space.

Why are OVH still reluctant to fix this problem?


Phixion
21-03-2014, 22:59
Quote Originally Posted by ExW
I also had the same problem, it was fixed by installing a driver with the help of Myatu's instructions:

http://forum.ovh.co.uk/showthread.ph...ll=1#post47569
Been there, done that!

Just to remind this is a friends server, not mine... mine is fine since the motherboard swap.

ExW
21-03-2014, 21:26
I also had the same problem, it was fixed by installing a driver with the help of Myatu's instructions:

http://forum.ovh.co.uk/showthread.ph...ll=1#post47569

Phixion
21-03-2014, 16:56
I have a friend with an mSP (same server as I have), and he is having exactly the same issues with the Realtek NIC as I had, and I know many others have/had.

The server will go offline for a second due to the network card going down then back up.

These are the errors he is seeing, he has sent these to support and they have blindly linked him to a general network issue that supposedly going on at the moment.

Mar 20 16:29:25 debian kernel: [ 8.181187] r8169
0000:03:00.0: firmware: agent aborted loading
rtl_nic/rtl8168f-1.fw (not found?)
> Mar 20 16:29:25 debian kernel: [ 8.181321] r8169
0000:03:00.0: eth0: unable to load firmware patch
rtl_nic/rtl8168f-1.fw (-2)
> Mar 20 16:29:25 debian kernel: [ 8.191338] r8169
0000:03:00.0: eth0: link down
> Mar 20 16:29:25 debian kernel: [ 8.191346] r8169
0000:03:00.0: eth0: link down
> Mar 20 16:29:25 debian kernel: [ 8.192845]
ADDRCONF(NETDEV_UP): eth0: link is not ready
> Mar 20 16:29:25 debian kernel: [ 11.248061] r8169
0000:03:00.0: eth0: link up
> Mar 20 16:29:25 debian kernel: [ 11.249637]
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready


First off, how can a trained technician say that a problem obviously on Kernel level is a problem with the network? It's clear the NIC drivers do not work as they should, apart from all of the error messages that get kicked up about missing firmware, the NIC is going down and up all the time.

This is clearly the same problem as I had on my server and the same problem I know that 3 others have had - yet support seem to be avoiding the fix (replacing Motherboard/NIC).

I personally had this issue for a few months and tried everything to fix it, including using OVH's kernel, installing their patches, manually installing the drivers - the issue was ongoing.

I am shocked OVH are still reluctant to fix this known problem. It took me 2 months of whining to get mine fixed and I've been extremely happy ever since, please don't make more people go through that just to get a stable server.