joelones Posted August 9, 2015 Share Posted August 9, 2015 I'm trying to get one of my boxes up and running with 6.1-rc2, however, I'm encountering erratic NIC behaviour on boot up, first with the r8169 onboard LAN and now my dual e1000 NIC. Don't know what to make it, whether it's kernel related or not. Occassionally it would boot up with no network connectivity despite me logging on via console and seeing an IP address. Board: ASRock 970 Extreme4 Log: http://pastebin.com/urdg9DXa Thoughts? Thanks Link to comment
SnickySnacks Posted August 13, 2015 Share Posted August 13, 2015 I had something similar with a test system I was setting up. Seemed to be a faulty AMD Vi (IOMMU) implementation on the MB or something. Disabling it in the bios seemed to correct the issue. Perhaps try that? Link to comment
joelones Posted August 14, 2015 Author Share Posted August 14, 2015 I rather not disable IOMMU, if that's what you mean. I'd like to run some VMs. Instead I chose to work around the issue by disabling the onboard NIC and luckily enough I have a dual intel NIC that I have installed. However, I really wanted to have a total of three NICs though, one for unRAID adminstration and two for bridges (in/out) for pfsene really. I haven't seen the issue now that I disabled the onboard LAN and some other stuff in the BIOS, hopefully I could go on with using the Intel NICs - knock on wood.... Link to comment
SnickySnacks Posted August 14, 2015 Share Posted August 14, 2015 So the IOMMU problem is just with the onboard nic? Good to know. On the MB we were using we didn't have another way to check so only option was to just disable IOMMU. Link to comment
joelones Posted August 15, 2015 Author Share Posted August 15, 2015 I'm hoping it's only related to the onboard nic. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.