How to get Asus XG-C100C 10G ethernet card working on Ubuntu 18.04
Is there anything you need to do to get this network card working in 18.04? It was working fine in 16.04 with the “atlantic” driver built from sources provided by Asus. After upgrading to 18.04, I can see that driver now seems to be included in Ubuntu, and I can see the card using lshw -class network
, but syslog shows the ethernet link is down.
There were bigger issues with networking. It wouldn’t work with the built in gigabit ethernet port either. I had to setup netplan to get that working. However, for the 10G card, running “networkctl” it shows “no-carrier” / “configuring” for this interface, even if the ethernet cable is connected.
So I'm not sure if I@m missing something? Are there more steps to take to get it working? or is there a bug in the 18.04 atlantic driver?
Also, do I now need to remove any packages to get rid of the old style “ifup / ifdown” and avoid any conflicts with netplan?
cheers
Edit: I tried a fresh install of Ubuntu 18.04 Server, and the installer has the same problem (i.e. shows 'no-link' for this NIC).
As pointed out in the comments below by @binaryanomaly, there's a bug in the kernel supplied with 18.04 for this NIC. It's fixed in kernel 4.16.6.
Edit: added the /etc/netplan/01-network-manager-all.yaml
file
# Let NetworkManager manage all devices on this system
network:
version: 2
# renderer: NetworkManager
renderer: networkd
ethernets:
enp1s0:
dhcp4: no
dhcp6: no
addresses: [192.168.0.12/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.2,192.168.0.1]
enp5s0:
dhcp4: no
dhcp6: no
addresses: [192.168.0.11/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.2,192.168.0.1]
networking drivers ethernet netplan
|
show 6 more comments
Is there anything you need to do to get this network card working in 18.04? It was working fine in 16.04 with the “atlantic” driver built from sources provided by Asus. After upgrading to 18.04, I can see that driver now seems to be included in Ubuntu, and I can see the card using lshw -class network
, but syslog shows the ethernet link is down.
There were bigger issues with networking. It wouldn’t work with the built in gigabit ethernet port either. I had to setup netplan to get that working. However, for the 10G card, running “networkctl” it shows “no-carrier” / “configuring” for this interface, even if the ethernet cable is connected.
So I'm not sure if I@m missing something? Are there more steps to take to get it working? or is there a bug in the 18.04 atlantic driver?
Also, do I now need to remove any packages to get rid of the old style “ifup / ifdown” and avoid any conflicts with netplan?
cheers
Edit: I tried a fresh install of Ubuntu 18.04 Server, and the installer has the same problem (i.e. shows 'no-link' for this NIC).
As pointed out in the comments below by @binaryanomaly, there's a bug in the kernel supplied with 18.04 for this NIC. It's fixed in kernel 4.16.6.
Edit: added the /etc/netplan/01-network-manager-all.yaml
file
# Let NetworkManager manage all devices on this system
network:
version: 2
# renderer: NetworkManager
renderer: networkd
ethernets:
enp1s0:
dhcp4: no
dhcp6: no
addresses: [192.168.0.12/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.2,192.168.0.1]
enp5s0:
dhcp4: no
dhcp6: no
addresses: [192.168.0.11/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.2,192.168.0.1]
networking drivers ethernet netplan
I suggest that you configure the needed details in netplan and see if it works. Possibly helpful: ubuntuforums.org/showthread.php?t=2371148 In this case, also only the compiled version works.
– chili555
May 10 '18 at 23:23
I added mynetplan
config file. It's the enp1s0 adapter. I'm not sure it's the same issue as the link you provided, as they're talking about 16.04 and 'ifconfig'. The card was working fine for me in 16.04. It's 18.04 and netplan, that I can't get it working on.
– Musaul
May 10 '18 at 23:37
Any clues in the log?dmesg | grep -e atl -e enp1
– chili555
May 10 '18 at 23:52
For your 16.04 to 18.04 upgrade question, I just posted this: askubuntu.com/a/1034754/7056. But, first you should figure out if your card is recognized by the kernel as chili has suggested.
– dpb
May 11 '18 at 4:31
2
It is a Bug in the drivers introduced with Kernel 4.16 seems to be fixed with 4.16.6: bugzilla.kernel.org/show_bug.cgi?id=199177
– binaryanomaly
May 15 '18 at 12:24
|
show 6 more comments
Is there anything you need to do to get this network card working in 18.04? It was working fine in 16.04 with the “atlantic” driver built from sources provided by Asus. After upgrading to 18.04, I can see that driver now seems to be included in Ubuntu, and I can see the card using lshw -class network
, but syslog shows the ethernet link is down.
There were bigger issues with networking. It wouldn’t work with the built in gigabit ethernet port either. I had to setup netplan to get that working. However, for the 10G card, running “networkctl” it shows “no-carrier” / “configuring” for this interface, even if the ethernet cable is connected.
So I'm not sure if I@m missing something? Are there more steps to take to get it working? or is there a bug in the 18.04 atlantic driver?
Also, do I now need to remove any packages to get rid of the old style “ifup / ifdown” and avoid any conflicts with netplan?
cheers
Edit: I tried a fresh install of Ubuntu 18.04 Server, and the installer has the same problem (i.e. shows 'no-link' for this NIC).
As pointed out in the comments below by @binaryanomaly, there's a bug in the kernel supplied with 18.04 for this NIC. It's fixed in kernel 4.16.6.
Edit: added the /etc/netplan/01-network-manager-all.yaml
file
# Let NetworkManager manage all devices on this system
network:
version: 2
# renderer: NetworkManager
renderer: networkd
ethernets:
enp1s0:
dhcp4: no
dhcp6: no
addresses: [192.168.0.12/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.2,192.168.0.1]
enp5s0:
dhcp4: no
dhcp6: no
addresses: [192.168.0.11/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.2,192.168.0.1]
networking drivers ethernet netplan
Is there anything you need to do to get this network card working in 18.04? It was working fine in 16.04 with the “atlantic” driver built from sources provided by Asus. After upgrading to 18.04, I can see that driver now seems to be included in Ubuntu, and I can see the card using lshw -class network
, but syslog shows the ethernet link is down.
There were bigger issues with networking. It wouldn’t work with the built in gigabit ethernet port either. I had to setup netplan to get that working. However, for the 10G card, running “networkctl” it shows “no-carrier” / “configuring” for this interface, even if the ethernet cable is connected.
So I'm not sure if I@m missing something? Are there more steps to take to get it working? or is there a bug in the 18.04 atlantic driver?
Also, do I now need to remove any packages to get rid of the old style “ifup / ifdown” and avoid any conflicts with netplan?
cheers
Edit: I tried a fresh install of Ubuntu 18.04 Server, and the installer has the same problem (i.e. shows 'no-link' for this NIC).
As pointed out in the comments below by @binaryanomaly, there's a bug in the kernel supplied with 18.04 for this NIC. It's fixed in kernel 4.16.6.
Edit: added the /etc/netplan/01-network-manager-all.yaml
file
# Let NetworkManager manage all devices on this system
network:
version: 2
# renderer: NetworkManager
renderer: networkd
ethernets:
enp1s0:
dhcp4: no
dhcp6: no
addresses: [192.168.0.12/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.2,192.168.0.1]
enp5s0:
dhcp4: no
dhcp6: no
addresses: [192.168.0.11/24]
gateway4: 192.168.0.1
nameservers:
addresses: [192.168.0.2,192.168.0.1]
networking drivers ethernet netplan
networking drivers ethernet netplan
edited May 18 '18 at 21:11
Musaul
asked May 10 '18 at 22:18
MusaulMusaul
1064
1064
I suggest that you configure the needed details in netplan and see if it works. Possibly helpful: ubuntuforums.org/showthread.php?t=2371148 In this case, also only the compiled version works.
– chili555
May 10 '18 at 23:23
I added mynetplan
config file. It's the enp1s0 adapter. I'm not sure it's the same issue as the link you provided, as they're talking about 16.04 and 'ifconfig'. The card was working fine for me in 16.04. It's 18.04 and netplan, that I can't get it working on.
– Musaul
May 10 '18 at 23:37
Any clues in the log?dmesg | grep -e atl -e enp1
– chili555
May 10 '18 at 23:52
For your 16.04 to 18.04 upgrade question, I just posted this: askubuntu.com/a/1034754/7056. But, first you should figure out if your card is recognized by the kernel as chili has suggested.
– dpb
May 11 '18 at 4:31
2
It is a Bug in the drivers introduced with Kernel 4.16 seems to be fixed with 4.16.6: bugzilla.kernel.org/show_bug.cgi?id=199177
– binaryanomaly
May 15 '18 at 12:24
|
show 6 more comments
I suggest that you configure the needed details in netplan and see if it works. Possibly helpful: ubuntuforums.org/showthread.php?t=2371148 In this case, also only the compiled version works.
– chili555
May 10 '18 at 23:23
I added mynetplan
config file. It's the enp1s0 adapter. I'm not sure it's the same issue as the link you provided, as they're talking about 16.04 and 'ifconfig'. The card was working fine for me in 16.04. It's 18.04 and netplan, that I can't get it working on.
– Musaul
May 10 '18 at 23:37
Any clues in the log?dmesg | grep -e atl -e enp1
– chili555
May 10 '18 at 23:52
For your 16.04 to 18.04 upgrade question, I just posted this: askubuntu.com/a/1034754/7056. But, first you should figure out if your card is recognized by the kernel as chili has suggested.
– dpb
May 11 '18 at 4:31
2
It is a Bug in the drivers introduced with Kernel 4.16 seems to be fixed with 4.16.6: bugzilla.kernel.org/show_bug.cgi?id=199177
– binaryanomaly
May 15 '18 at 12:24
I suggest that you configure the needed details in netplan and see if it works. Possibly helpful: ubuntuforums.org/showthread.php?t=2371148 In this case, also only the compiled version works.
– chili555
May 10 '18 at 23:23
I suggest that you configure the needed details in netplan and see if it works. Possibly helpful: ubuntuforums.org/showthread.php?t=2371148 In this case, also only the compiled version works.
– chili555
May 10 '18 at 23:23
I added my
netplan
config file. It's the enp1s0 adapter. I'm not sure it's the same issue as the link you provided, as they're talking about 16.04 and 'ifconfig'. The card was working fine for me in 16.04. It's 18.04 and netplan, that I can't get it working on.– Musaul
May 10 '18 at 23:37
I added my
netplan
config file. It's the enp1s0 adapter. I'm not sure it's the same issue as the link you provided, as they're talking about 16.04 and 'ifconfig'. The card was working fine for me in 16.04. It's 18.04 and netplan, that I can't get it working on.– Musaul
May 10 '18 at 23:37
Any clues in the log?
dmesg | grep -e atl -e enp1
– chili555
May 10 '18 at 23:52
Any clues in the log?
dmesg | grep -e atl -e enp1
– chili555
May 10 '18 at 23:52
For your 16.04 to 18.04 upgrade question, I just posted this: askubuntu.com/a/1034754/7056. But, first you should figure out if your card is recognized by the kernel as chili has suggested.
– dpb
May 11 '18 at 4:31
For your 16.04 to 18.04 upgrade question, I just posted this: askubuntu.com/a/1034754/7056. But, first you should figure out if your card is recognized by the kernel as chili has suggested.
– dpb
May 11 '18 at 4:31
2
2
It is a Bug in the drivers introduced with Kernel 4.16 seems to be fixed with 4.16.6: bugzilla.kernel.org/show_bug.cgi?id=199177
– binaryanomaly
May 15 '18 at 12:24
It is a Bug in the drivers introduced with Kernel 4.16 seems to be fixed with 4.16.6: bugzilla.kernel.org/show_bug.cgi?id=199177
– binaryanomaly
May 15 '18 at 12:24
|
show 6 more comments
2 Answers
2
active
oldest
votes
You do not need to remove any packages to eliminate ifup and ifdown from your system. These commands will only have an effect for network interfaces configured in /etc/network/interfaces. You can even have some interfaces managed through /etc/network/interfaces and some managed through netplan on the same system.
If your interface is showing as "no carrier", this is most likely a driver issue, not a netplan issue. You can rule out netplan by removing the interface from your yaml and attempting to configure it directly using ifconfig or ip.
add a comment |
Musaul had good information
in Kernel 4.15 and 14.16 you may encounter instability due to Debian kernel incompatibility with dirty wake WOL feature in the firmware of XG-C100C.
Details in comment 41 of kernel bug #199177
Workaround might be included with Kernel 4.16.6 in release app june 2018, so make sure you avoid kernel between 4.15.16 and 4.16.5 with your network card.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034687%2fhow-to-get-asus-xg-c100c-10g-ethernet-card-working-on-ubuntu-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You do not need to remove any packages to eliminate ifup and ifdown from your system. These commands will only have an effect for network interfaces configured in /etc/network/interfaces. You can even have some interfaces managed through /etc/network/interfaces and some managed through netplan on the same system.
If your interface is showing as "no carrier", this is most likely a driver issue, not a netplan issue. You can rule out netplan by removing the interface from your yaml and attempting to configure it directly using ifconfig or ip.
add a comment |
You do not need to remove any packages to eliminate ifup and ifdown from your system. These commands will only have an effect for network interfaces configured in /etc/network/interfaces. You can even have some interfaces managed through /etc/network/interfaces and some managed through netplan on the same system.
If your interface is showing as "no carrier", this is most likely a driver issue, not a netplan issue. You can rule out netplan by removing the interface from your yaml and attempting to configure it directly using ifconfig or ip.
add a comment |
You do not need to remove any packages to eliminate ifup and ifdown from your system. These commands will only have an effect for network interfaces configured in /etc/network/interfaces. You can even have some interfaces managed through /etc/network/interfaces and some managed through netplan on the same system.
If your interface is showing as "no carrier", this is most likely a driver issue, not a netplan issue. You can rule out netplan by removing the interface from your yaml and attempting to configure it directly using ifconfig or ip.
You do not need to remove any packages to eliminate ifup and ifdown from your system. These commands will only have an effect for network interfaces configured in /etc/network/interfaces. You can even have some interfaces managed through /etc/network/interfaces and some managed through netplan on the same system.
If your interface is showing as "no carrier", this is most likely a driver issue, not a netplan issue. You can rule out netplan by removing the interface from your yaml and attempting to configure it directly using ifconfig or ip.
answered May 12 '18 at 0:05
slangasekslangasek
2,46311419
2,46311419
add a comment |
add a comment |
Musaul had good information
in Kernel 4.15 and 14.16 you may encounter instability due to Debian kernel incompatibility with dirty wake WOL feature in the firmware of XG-C100C.
Details in comment 41 of kernel bug #199177
Workaround might be included with Kernel 4.16.6 in release app june 2018, so make sure you avoid kernel between 4.15.16 and 4.16.5 with your network card.
add a comment |
Musaul had good information
in Kernel 4.15 and 14.16 you may encounter instability due to Debian kernel incompatibility with dirty wake WOL feature in the firmware of XG-C100C.
Details in comment 41 of kernel bug #199177
Workaround might be included with Kernel 4.16.6 in release app june 2018, so make sure you avoid kernel between 4.15.16 and 4.16.5 with your network card.
add a comment |
Musaul had good information
in Kernel 4.15 and 14.16 you may encounter instability due to Debian kernel incompatibility with dirty wake WOL feature in the firmware of XG-C100C.
Details in comment 41 of kernel bug #199177
Workaround might be included with Kernel 4.16.6 in release app june 2018, so make sure you avoid kernel between 4.15.16 and 4.16.5 with your network card.
Musaul had good information
in Kernel 4.15 and 14.16 you may encounter instability due to Debian kernel incompatibility with dirty wake WOL feature in the firmware of XG-C100C.
Details in comment 41 of kernel bug #199177
Workaround might be included with Kernel 4.16.6 in release app june 2018, so make sure you avoid kernel between 4.15.16 and 4.16.5 with your network card.
edited Jan 3 at 4:13
Pablo Bianchi
2,4451530
2,4451530
answered Jan 2 at 20:21
rhummierhummie
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034687%2fhow-to-get-asus-xg-c100c-10g-ethernet-card-working-on-ubuntu-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I suggest that you configure the needed details in netplan and see if it works. Possibly helpful: ubuntuforums.org/showthread.php?t=2371148 In this case, also only the compiled version works.
– chili555
May 10 '18 at 23:23
I added my
netplan
config file. It's the enp1s0 adapter. I'm not sure it's the same issue as the link you provided, as they're talking about 16.04 and 'ifconfig'. The card was working fine for me in 16.04. It's 18.04 and netplan, that I can't get it working on.– Musaul
May 10 '18 at 23:37
Any clues in the log?
dmesg | grep -e atl -e enp1
– chili555
May 10 '18 at 23:52
For your 16.04 to 18.04 upgrade question, I just posted this: askubuntu.com/a/1034754/7056. But, first you should figure out if your card is recognized by the kernel as chili has suggested.
– dpb
May 11 '18 at 4:31
2
It is a Bug in the drivers introduced with Kernel 4.16 seems to be fixed with 4.16.6: bugzilla.kernel.org/show_bug.cgi?id=199177
– binaryanomaly
May 15 '18 at 12:24