All,
As a continuation of the disc controller failure/system rebuild, I have the new box built and a pair of fresh drives waiting for a new Arch install. This motherboard has the Realtek 8111/8168/8411 chipset. (Gigabyte GA-990FXA-UD3 motherboard).
I am booting with the latest install medium which boots fine in legacy or EUFI mode. No matter what I do, I cannot get an IPv4 address. I have read:
https://wiki.archlinux.org/index.php/Network_configuration#Realtek_no_link_....
(that's not the problem, link light is on, activity indicator is flashing, and link is reported 'Up' by 'ip link')
I have read:
https://wiki.archlinux.org/index.php/Network_configuration#Realtek_RTL8111.2...
- installed (pacman -U r8168-8.040.00-5-x86_64.pkg.tar.xz) - blacklisted r8169 - loaded r8168 - confirmed the NIC is using r8168 w/lspci -v - systemctl restart dhcpcd (many times) - systemctl status dhcpcd reports no IPv6 Routers no IPv4 Leases request timeout
It's not the cable or my dhcpd server, I boot the box with the failed disc controller, and it is assigned an address just fine. (same cable)
I'm stuck, looking at the log on my dhcp server, the requests are never seen. It's like the card isn't sending, but the link light is fine and the activity light on the NIC is flashes when it sees traffic?
What else can I try?
Hi
On Thu, Aug 20, 2015 at 3:31 PM, David C. Rankin drankinatty@suddenlinkmail.com wrote:
All,
As a continuation of the disc controller failure/system rebuild, I have the new box built and a pair of fresh drives waiting for a new Arch install. This motherboard has the Realtek 8111/8168/8411 chipset. (Gigabyte GA-990FXA-UD3 motherboard).
I am booting with the latest install medium which boots fine in legacy or EUFI mode. No matter what I do, I cannot get an IPv4 address.
Check this thread https://bbs.archlinux.org/viewtopic.php?id=200514 is it what you see?
What happens if you downgrade to dhcpcd-6.9.0 ?
I have read:
https://wiki.archlinux.org/index.php/Network_configuration#Realtek_no_link_....
(that's not the problem, link light is on, activity indicator is flashing, and link is reported 'Up' by 'ip link')
I have read:
https://wiki.archlinux.org/index.php/Network_configuration#Realtek_RTL8111.2...
- installed (pacman -U r8168-8.040.00-5-x86_64.pkg.tar.xz)
- blacklisted r8169
- loaded r8168
- confirmed the NIC is using r8168 w/lspci -v
- systemctl restart dhcpcd (many times)
- systemctl status dhcpcd reports no IPv6 Routers no IPv4 Leases request timeout
It's not the cable or my dhcpd server, I boot the box with the failed disc controller, and it is assigned an address just fine. (same cable)
I'm stuck, looking at the log on my dhcp server, the requests are never seen. It's like the card isn't sending, but the link light is fine and the activity light on the NIC is flashes when it sees traffic?
What else can I try?
-- David C. Rankin, J.D.,P.E.
On 08/20/2015 05:56 PM, Anatol Pomozov wrote:
Check this threadhttps://bbs.archlinux.org/viewtopic.php?id=200514 is it what you see?
What happens if you downgrade to dhcpcd-6.9.0 ?
I will check, but there is something not right going on. I did manage to get an inet address assigned by dhcpcd (for a minute) when I rebooted to box, pulled the CD out, let it boot to the point of "Install System Disk and Press Any Key", put the CD back in, and booted non UEFI mode.
I was going to just assign a static address, but checked 'ifconfig' before disabling dhcpcd and BINGO there was a proper IPv4 address handed out by my dhcpd server (it handed out .166 which was correct, because it handed the broken box .165 an hour before)
However, by the time I went to ping anything, or start sshd so I could ssh into the box, the connection went dead again (meaning 'ip link' still shows Status UP; if config still shows correct IP address, but any attempt to ping results in: network not found...)
I'll read the thread and let you know if I found a solution. Any other thoughts, just let me know.
On 08/20/2015 06:42 PM, David C. Rankin wrote:
On 08/20/2015 05:56 PM, Anatol Pomozov wrote:
Check this threadhttps://bbs.archlinux.org/viewtopic.php?id=200514 is it what you see?
What happens if you downgrade to dhcpcd-6.9.0 ?
I will check, but there is something not right going on. I did manage to get an inet address assigned by dhcpcd (for a minute) when I rebooted to box, pulled the CD out, let it boot to the point of "Install System Disk and Press Any Key", put the CD back in, and booted non UEFI mode.
I was going to just assign a static address, but checked 'ifconfig' before disabling dhcpcd and BINGO there was a proper IPv4 address handed out by my dhcpd server (it handed out .166 which was correct, because it handed the broken box .165 an hour before)
However, by the time I went to ping anything, or start sshd so I could ssh into the box, the connection went dead again (meaning 'ip link' still shows Status UP; if config still shows correct IP address, but any attempt to ping results in: network not found...)
I'll read the thread and let you know if I found a solution. Any other thoughts, just let me know.
Anatol,
The symptoms sound exactly what I'm experiencing with the Realtek NIC. 1 out of 3 boots I have established a dhcpcd IPv4 address (on the r8169 module), but then the connection dies. If this is related to what is happening in the thread, then it is related to the Realtek hardware in my case. I can take the same archlinux-2015.08.01-dual.iso CD pop it into my failed box with the MSI board and get a reliable connection and address every time.
I really don't know where to go from here. I've tried a static IP with both the r8169 module and the r8168 module and the static IP can't ping the box 2 feet away. (It's not a network "unreachable" error, it's a no network/no response error -- the system thinks it has a good config with address/subnet broadcast and broadcast address -- and good default route)
What else can I try when I'm limited to booting the install media?
On 08/20/2015 07:00 PM, David C. Rankin wrote:
Anatol,
The symptoms sound exactly what I'm experiencing with the Realtek NIC. 1 out of 3 boots I have established a dhcpcd IPv4 address (on the r8169 module), but then the connection dies. If this is related to what is happening in the thread, then it is related to the Realtek hardware in my case. I can take the same archlinux-2015.08.01-dual.iso CD pop it into my failed box with the MSI board and get a reliable connection and address every time.
I really don't know where to go from here. I've tried a static IP with both the r8169 module and the r8168 module and the static IP can't ping the box 2 feet away. (It's not a network "unreachable" error, it's a no network/no response error -- the system thinks it has a good config with address/subnet broadcast and broadcast address -- and good default route)
What else can I try when I'm limited to booting the install media?
OK,
This is just plain weird. I'm beginning to think there is a problem with the new board/bus whatever carries network traffic. I have now tried the onboard NIC, and then with that disabled, tried two additional pci-NICs and all exhibited partial connect/no connect behavior. This is trying with older 100TX cards:
- Netgear (uses realtek r8169 -- of all the luck) - generic card out of an old Compaq desktop (uses tulip driver)
I was able to configure both with static IPs, but then there was a packet loss of 66%+ to other boxes on the LAN. Name resolution worked (it would show the correct IP to ping (e.g. yahoo.com/google.com), but then 3-10 packets of "Network Unreachable", followed by 5-10 good packets with normal ping times (2-60 ms) Same behavior under both the 201308 install media and the 201508 install media (eliminating the latest version of dhcpcd issue)
By this time I was convinced that my cable had gone bad, so I moved the old broken server back into place, booted the install media, and the onboard NIC came right up (forcedeath driver), obtained a dhcp address and resolution worked with 0 packet loss. So I'm at a loss.
Has anyone ever had a board or an install where the network was just flaky or dead for multiple NICs? Thoughts?
On 08/20/2015 09:34 PM, David C. Rankin wrote:
By this time I was convinced that my cable had gone bad, so I moved the old broken server back into place, booted the install media, and the onboard NIC came right up (forcedeath driver), obtained a dhcp address and resolution worked with 0 packet loss. So I'm at a loss.
Has anyone ever had a board or an install where the network was just flaky or dead for multiple NICs? Thoughts?
$#%#@%#$%... You have to enable IOMMU in the BIOS before the NIC will work! I stumbled across this obscure little tidbit on the fedora forum:
http://forums.fedoraforum.org/showthread.php?t=295616
It triggers some nasty AMD I10 Page Faults/xhci messages during boot of the 201508 install media, but the network comes right up, dhcp works, no more lost packets, etc.
I wonder if this is related to it corrupting my USB drives I plug into it? Drives work the first time, sync, then umount. Next time you plug them in, filesystem is gone?
Oh well, at least I have a network now. I'll add it to the wiki.
On 21-08-15 04:58, David C. Rankin wrote:
On 08/20/2015 09:34 PM, David C. Rankin wrote:
$#%#@%#$%... You have to enable IOMMU in the BIOS before the NIC will work! I stumbled across this obscure little tidbit on the fedora forum:
http://forums.fedoraforum.org/showthread.php?t=295616
It triggers some nasty AMD I10 Page Faults/xhci messages during boot of the 201508 install media, but the network comes right up, dhcp works, no more lost packets, etc.
I wonder if this is related to it corrupting my USB drives I plug into it? Drives work the first time, sync, then umount. Next time you plug them in, filesystem is gone?
Oh well, at least I have a network now. I'll add it to the wiki.
Blame Gigabyte, the only reason to disable IOMMU is if you run a 32-bit OS .
On all x86_64 OSes running with IOMMU disabled will degrade graphics performance A LOT. As you found , disabling IOMMU also affects other hardware badly.
TL;DR : 64-bit OS >>> ENABLE IOMMU
Some links :
https://en.wikipedia.org/wiki/IOMMU http://developer.amd.com/community/blog/2008/09/01/iommu/
Lone_Wolf
On 08/21/2015 08:10 AM, LoneVVolf wrote:
Blame Gigabyte, the only reason to disable IOMMU is if you run a 32-bit OS .
On all x86_64 OSes running with IOMMU disabled will degrade graphics performance A LOT. As you found , disabling IOMMU also affects other hardware badly.
TL;DR : 64-bit OS >>> ENABLE IOMMU
Some links :
https://en.wikipedia.org/wiki/IOMMU http://developer.amd.com/community/blog/2008/09/01/iommu/
Lone_Wolf
Thanks, and yes, so I found out. It would really be helpful if motherboard manuals were worth a crap anymore, but those days are long gone. The ONLY description concerning IOMMU in the entire manual was:
<quote (page 49)>
IOMMU Controller Enables or disables AMD IOMMU support. (Default: Disabled)
</quote>
A lot of good that does to guide someone in its use. :p
On Thu, Aug 20, 2015 at 10:34 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
Has anyone ever had a board or an install where the network was just flaky or dead for multiple NICs? Thoughts?
-- David C. Rankin, J.D.,P.E.
Eek, sorry you're having so much trouble. I may have already said this, but I'll give it another go. I'm using the same board (GA-990FXA-UD3) with the same ethernet card. I decided the onboard NIC was trash, so I installed a PCI ethernet card, installed arch, and started using it. Later, I went back to troubleshoot the NIC, and found that if I sudo pacman -Syu r8168; echo 'blacklist r8169' > /etc/modprobe.d/r8169_blacklist.conf; reboot; everything went okay, and no need for PCI card.
I'm afraid that beyond that, I don't think I can help.
Aaron
$#%#@%#$%... You have to enable IOMMU in the BIOS before the NIC will work!
Oh yeah, that, too. Mine is the last comment on https://bbs.archlinux.org/viewtopic.php?id=186503. I had to enable IOMMU in bios, then disable it in kernel using iommu=soft.
Yes, the BIOS eats up your flash drive. Maybe it only knows FAT32 or NTFS or something. Just don't have it do any reading or writing to a drive with anything important on it. It also does this to hard drives, so stay away from screenshots, etc.
I'm happy you got it worked out!
On 08/24/2015 01:26 PM, Aaron Laws wrote:
Eek, sorry you're having so much trouble. I may have already said this, but I'll give it another go. I'm using the same board (GA-990FXA-UD3) with the same ethernet card. I decided the onboard NIC was trash, so I installed a PCI ethernet card, installed arch, and started using it. Later, I went back to troubleshoot the NIC, and found that if I sudo pacman -Syu r8168; echo 'blacklist r8169' > /etc/modprobe.d/r8169_blacklist.conf; reboot; everything went okay, and no need for PCI card.
I'm afraid that beyond that, I don't think I can help.
You were a great help! What I learned is that board has gone through a lot of changes (chipset, etc.) between Version 1.0 - 4.1 (I have Ver. 4.1). What is needed to fix the issues differs depending on the chipset. Mine works fine with the native r8169 driver as long as IOMMU is enable in the bios. I'll try disabling in the kernel to kill the Page_Faults on boot.
arch-general@lists.archlinux.org